Open topic with navigation

TIBCO iProcess® Engine 11.10.0

# Default Java Message Service

The Default Java Message Service dialog box, along with two subsequent dialog boxes, allows you to configure the necessary Java Message Service (JMS) parameters to enable Activity Monitoring and Work Queue Delta publication on the iProcess Engine.

For more information about using these parameters, see Administering Activity Monitoring in TIBCO iProcess Engine Administrator’s Guide.

To configure the default JMS parameters, complete the following steps:

| 1. | Select one JMS provider that the iProcess Engine will publish messages to in the Default Java Message Service dialog box, as shown in Default Java Message Service Dialog Box.

Note | If you select the `Other` option for the JMS Provider, no defaults are entered. You must supply appropriate values for the other menu items. The JMS provider software does not need to be installed on the same machine as the iProcess Engine.

Figure 98: Default Java Message Service Dialog Box

| 2. | Click the Next button. The JAR Files For JMS Connectivity dialog box appears. Configure the items listed in Configuration Options in the JAR Files For JMS Connectivity Dialog Box.

Configuration Options in the JAR Files For JMS Connectivity Dialog Box

Configuration Option | Description
Base | In the Default Java Message Service dialog box shown in Default Java Message Service Dialog Box, if you select: IBM Websphere 8.x
| • | You must specify the location of Java 17 compatible Websphere client jars.
Oracle WebLogic
| • | Oracle WebLogic is validated with `wlthint3client.jar`(14.1.2 version). You must specify the location of the client jar.
JBOSS
| • | JBOSS is validated with `wildfly-client-all-26.0.0.Final.jar`. You must specify the location of the client jar.
anything else
| • | Specify the full path (or comma-separated paths) of the JAR files required by this JMS provider.
| • | When specifying the path, make sure that you use the forward slash character (`/`) as the path separator, rather than the backslash character (`\`). For example, specify `e:/tibco/ems/clients/java/jms-2.0.jar` not `e:\tibco\ems\clients\java\jms-2.0.jar`.
| • | The installer writes this value to the IAPJMS configuration file: `SWDIR``\etc\iapjms_classpath.properties.`
Additional | Specify the full path (or comma-separated paths) of any additional JAR files that are required for your JMS configuration. When specifying the path, make sure that you use the forward slash character (`/`) as the path separator, rather than the backslash character (`\`). The installer writes this value to the IAPJMS configuration file: `SWDIR``\etc\iapjms_classpath.properties.`

Note: After installation, verify that the jars names and paths are reflected in `iapjms_classpath.properties` file.

Warning | If you are using a Microsoft Windows Cluster, the `Base` and `Additional` paths must be accessible to every physical machine in the cluster.

| 3. | Click the Next button. The IAPJMS Properties dialog box appears. Configure the items listed in Configuration Options in IAPJMS Properties Dialog Box.

Configuration Options in IAPJMS Properties Dialog Box

Configuration Option | Description
Context | Specify the name of the context factory that produces context instances for the selected JMS Provider. The installer writes this value to the `IAPJMSConnect.InitialContextFactory` property in the IAPJMS configuration file: `SWDIR``\etc\iapjms_classpath.properties.`
URL | Specify the URL that the iProcess Engine uses to connect to the selected JMS Provider. The installer writes this value to the `IAPJMSConnect.InitialURL` property in the IAPJMS configuration file: `SWDIR``\etc\iapjms_classpath.properties.`
Connection | Specify the name of the object that iProcess Engine uses to create a connection to the selected JMS Provider. The installer writes this value to the `IAPJMSConnect.TopicConnectionFactory` property in the IAPJMS configuration file: `SWDIR``\etc\iapjms_classpath.properties.`

| 4. | Click the Next button to continue with the installation.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2025. Cloud Software Group, Inc. All Rights Reserved.