Configuration

The Configuration tab has the following fields.

Field

Global Var?

Description

Name

No

This name appears as the label for the resource.

Description

No

Short description of the shared resource.

User Name

Yes

User name to use when logging into the JMS server.

If the JMS provider does not require access control, this field can be empty.

Not all JMS servers require user names and passwords. Refer to your JMS provider documentation and consult your system administrator to determine if your JMS server requires a user name and password.

Password

Yes

Password to use when logging into the JMS server.

If the JMS provider does not require access control, this field can be empty.

Auto-Generate Client ID

Yes

Checking this field specifies that you want to automatically generate the client ID if no client ID is specified or if the specified ID is already in use. When this field is checked, if a value is specified in the Client ID field, an attempt is made to use the specified value. However, if the specified value is already in use, a new client ID is generated.

When an automatically generated client ID is required, the following format is used for the client ID:

BW-<projectName>-<topic or queue>-<engineName>-<timestamp>

If this field is not checked, then the value specified in the Client ID field is used. If no value is specified in the Client ID field, then no client ID is set. If the value specified in the Client ID field is already in use, an exception is thrown.

Client ID

Yes

Client ID for the connection. Typically JMS providers have a provider-specific format for client IDs. For more information about client IDs, see your JMS provider’s documentation. Each connection must use a unique Client ID. If you do not specify a value in this field, ActiveMatrix BusinessWorks ensures the uniqueness of the client ID for each connection.

SSL

No

Specifies whether you want to use SSL for the connection to the JMS server. SSL is used when the Use SSL? check box is selected. Click the Configure SSL button to configure the SSL connection parameters.

Note: SSL is supported only when using TIBCO Enterprise Message Service.

For more information, see SSL Configuration.

Use JNDI for Connection Factory

Yes

Specifies whether JNDI should be used to look up the ConnectionFactory object. If this field is unchecked, the Provider URL and Use XA Connection Factory fields appear. If this field is checked, JNDI configuration fields appear.

Provider URL

Yes

This field is only available when the Use JNDI for Connection Factory field is unchecked.

This is the URL to use to connect to the JMS server.

Use XA Connection Factory

No

When checked, this field specifies that an XA connection factory is to be used. This is useful if you want activities that use this connection to participate in an XA transaction.

Note: This field appears only when the Use JNDI for Connection Factory field is unchecked.

For more information about transactions, see TIBCO ActiveMatrix BusinessWorks Process Design.

Note: If this field is selected, the "Use UFO Connection Factory" field cannot be used.

Use UFO Connection Factory

Yes

Use this check box when using EMS Unshared State Failover factories. For more information about Unshared State Failover, see TIBCO Enterprise Message Service User’s Guide .

This field appears only when the Use JNDI for Connection Factory field is unchecked.

Note: If this field is selected, the Use XA Connection Factory field cannot be used.

When using Unshared Failover setup, if a connection loss is detected to server (A), ActiveMatrix BusinessWorks will try to connect to server (B) as defined in the connection factory configuration. For more information about Unshared Failover, see TIBCO Enterprise Message Service User’s Guide.

After enabling this check box you can pass the provider URL in the form of UFO. For example: "tcp://serverA:7222+tcp://serverB:7222" where serverA and serverB are two EMS servers configured for the Unshared State Failover.

Unsupported Features and Activities

  • JMS Palette

    • JMS Queue Requestor

    • JMS Topic Requestor

    • Any other Requestor activity

  • SOAP Palette

    • All activities

  • Service Palette

    • All activities

  • AE Adaptor

    • All activities

 

 

Looking up factories using JNDI is not supported because:

  • UFO factories cannot be retrieved through JNDI directly.

Use Shared JNDI Configuration

No

When this field is checked, the JNDI Configuration field appears that allows you to choose a JNDI Configuration shared configuration resource.

When this field is unchecked, the JNDI Context Factory, JNDI Context URL, JNDI User Name, and JNDI Password fields appear.

JNDI Configuration

No

This field only appears when the Use Shared JNDI Configuration field is checked.

This field allows you to choose a JNDI Configuration shared configuration object that specifies the JNDI connection information. For more information, see JNDI Configuration.

JNDI Context Factory

Yes

This field appears only when the Use Shared JNDI Configuration field is unchecked. It is the initial context factory class for accessing JNDI. (javax.naming.Context.INITIAL_CONTEXT_
FACTORY
). You can choose from the drop-down list of supported classes, or you can type in a different InitialContextFactory class name.

When using IBM WebSphere, you should use the JNDI Configuration resource instead of specifying the JNDI configuration on this resource. For more information, see IBM WebSphere and JNDI Context Caching.

Note: ActiveMatrix BusinessWorks attempts to find the class. However, you may need to add the Java file supplied by your JNDI service provider to the CLASSPATH environment variable to use JNDI.

JNDI Context URL

Yes

This field only appears when the Use Shared JNDI Configuration field is unchecked. This is the URL to the JNDI service provider (javax.naming.Context.PROVIDER_URL). An example URL is provided when one of the supported JNDI context factory classes is selected.

For the syntax of the URL, see your JNDI provider documentation.

JNDI User Name

Yes

This field only appears when the Use Shared JNDI Configuration field is unchecked. User name to use when logging into the JNDI server (javax.naming.Context.SECURITY_
PRINCIPAL
). If the JNDI provider does not require access control, this field can be empty.

JNDI Password

Yes

This field only appears when the Use Shared JNDI Configuration field is unchecked. Password to use when logging into the JNDI server (javax.naming.Context.SECURITY_
CREDENTIALS
). If the JNDI provider does not require access control, this field can be empty.

Connection Factory SSL Password

Yes

This field is only available when the SSL and the Use JNDI for Connection Factory fields are checked and the Use Shared JNDI Configuration field is unchecked.

The SSL configuration is specified in the ConnectionFactory object, except for the client SSL password.

You can specify your client SSL password in this field, or you can leave this field empty. If your password is not specified, the private key password is used.