Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# 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 want to use TIBCO EMS, select TIBCO EMS 8.0 if you are using TIBCO EMS version 8.0, otherwise select `TIBCO EMS` if you are using TIBCO EMS other supported versions. If you want to use JBoss 4.0.0, you need to select the JBoss radio button. If you want to use any other version of JBoss or JBoss Messaging, you need to select the Other radio button instead. If you want to use IBM Websphere 7.x, you need to select the IBM Websphere 8.x button. If you are using IBM Websphere 8.x, SSL will be enabled by default. Since SSL is disabled by default in TIBCO iProcess Engine, you should either disable SSL in IBM Websphere 8.x or enable SSL in TIBCO iProcess Engine. Similarly, if you want to use Oracle WebLogic Server Version, you should select the Oracle WebLogic Server radio button. If you want to use any other version of WebLogic Server, select the Other radio button instead.

Figure 58: 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 6.x Specify the full path of the directory containing the IBM Client for JMS on J2SE with WebSphere Application Server. The iProcess Engine IAPJMS process must use this client to communicate with the WebSphere 6.x Application Server. If you do not already have this client installed on this computer, TIBCO recommends that you use the default location (`SWDIR``\jmsclient`). You must then install this client into the specified directory after you have installed iProcess Engine. See Installing the IBM Client for JMS on J2SE with IBM WebSphere Application Server for more information about how to do this. IBM Websphere 8.x You must specify the `websphere_home` directory where IBM Websphere 8.x is installed and make sure the following files are saved in the `websphere_home``\runtimes` directory:
| • | `com.ibm.ws.sib.client.thin.jms_``versionnumber``.jar`
| • | `com.ibm.ws.ejb.thinclient_``versionnumber``.jar`
| • | `com.ibm.ws.orb_``versionnumber``.jar`
JBoss 6.x Specify the full path of the directory containing the following files:
| • | `jboss-jms-api_1.1_spec.jar`
| • | `jnp-client.jar`
| • | `hornetq-core-client.jar`
| • | `hornetq-jms-client.jar`
| • | `netty.jar`
| • | `jboss-logging.jar`
Note: In JBoss 6.x, JMS service is provided by HornetQ. So you need to install HornetQ. On the other hand, you can find the listed `.jar` files either in HornetQ or in JBoss 6.x final installation directory.
Base | 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.jar` not `e:\tibco\ems\clients\java\jms.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.`

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-2024. Cloud Software Group, Inc. All Rights Reserved.