Show Table of Contents
3.4. Configuring Java Message Service (JMS)
Oracle WebLogic Server must be configured to send and receive JMS messages through Red Hat JBoss BPM Suite. This requires a JMS Server. Follow the steps below to create a JMS Server.
- Navigate to → → .
- Click New to start creating a new JMS Server.
- Provide your JMS Server with a Name. Click Next to advance to the next configuration screen.
- Select the Target server chosen for the Business Central deployment. Click Finish to complete the JMS Server creation.
Create JMS Module
A JMS Module stores your JMS resources, such as connection factories and queues. Use the following steps to create a new JMS Module.
- Navigate to → → .
- Click New to start creating a new module.
- Provide your module with a Name and click Next to advance to the next configuration screen.
- Select the Target server chosen for the Business Central deployment. Click Finish to complete the JMS Module creation.
- Click on the newly created module's name, then click on .
- Click New to create a subdeployment for your module.
- Provide your subdeployment with a Name and click Next to advance to the next configuration screen.
- Choose the previously created JMS Server by marking the checkbox. Click Finish to complete the Module's subdeployment configuration.
Create JMS Connection Factories
To send and receive messages from Red Hat JBoss BPM Suite, you will need to create the JMS connection factories - one for receiving messages and one for sending them. The following connection factories are required:
KIE.RESPONSE.ALL- For receiving all responses produced by Red Hat JBoss BPM Suite. The default value isjms/cf/KIE.RESPONSE.ALLKIE.SESSION- For sending messages to the process engine. The default value isjms/cf/KIE.SESSIONKIE.TASK- For sending messages to the task service. The default value isjms/cf/KIE.TASKKIE.AUDIT- For sending messages with audit trail. The default value isjms/cf/KIE.AUDITKIE.SERVER.REQUEST- For all requests to the decision server. The default value isjms/cf/KIE.SERVER.REQUESTKIE.SERVER.RESPONSE- For receiving all responses produced from the decision server. The default value isjms/cf/KIE.SERVER.RESPONSE
Use the following procedure to create each connection factory.
- If you are not there already, navigate to → → to see your list of JMS Modules.
- Click on your previously created module, then click New to start creating a new JMS resource.
- Select Connection Factory and click Next.
- Enter the Name of the connection factory (for example,
KIE.RESPONSE.ALL) and the JNDI Name (for example,jms/cf/KIE.RESPONSE.ALL).Click Next to advance to the next configuration screen. - The connection factory automatically selects the servers assigned to the JMS Module as the default. Click Finish to complete the connection factory creation.
Repeat the above procedure for each connection factory.
Create JMS Queues
You will now need to create the JMS Queues. These queues are the destination end points for point-to-point messaging. You will create:
KIE.RESPONSE.ALL- For Red Hat JBoss BPM Suite responses. The default value isjms/KIE.RESPONSE.ALLKIE.SESSION- For ksession based operations. . The default value isjms/KIE.SESSIONKIE.TASK- For task based operations. The default value isjms/KIE.TASKKIE.AUDIT- For asynchronous audit logs. The default value isjms/KIE.AUDITKIE.SERVER.REQUEST- For all requests to the decision server. The default value isjms/KIE.SERVER.REQUESTKIE.SERVER.RESPONSE- For decision server responses. The default value isjms/KIE.SERVER.RESPONSE
Use the following procedure to create each queue.
- If you are not there already, navigate to → → to see your list of JMS Modules.
- Click on your previously created module, then click New to start creating a new JMS resource.
- Select Queue and click Next.
- Enter the Name of the queue (for example,
KIE.RESPONSE.ALL) and the JNDI Name (for example,jms/KIE.RESPONSE.ALL).Click Next to advance to the next configuration screen. - Choose the JMS Module's subdeployment that connects to the JMS Server. Click Finish to complete the queue creation.
Repeat the above procedure for each queue.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.