JMS Setup for Data Intake - WebSphere Configuration

1. Introduction and Definitions

A JMS queue in WebSphere Server is associated with a number of additional resources:

The high-level configuration steps are as follows to configure messaging within WebSphere Application Server for the MDB sample:

  1. Configure the service bus
  2. Configure the bus members
  3. Configure the destinations
  4. Verify the messaging engine startup
  5. Configure JMS connection queue factory
  6. Configure the destination JMS queue

A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of one or more interconnected servers or server clusters that are members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members.

 

db2Object Name Type JNDI Name
DataIntakeJMSServer SIB (BUS Name)  
IntakeConnectionFactory Queue Connection Factories IntakeConnectionFactory
DIQueue JMS Queue DIQueue

2. Configuration Steps

Pre-requisites for running Data Intake:

The following steps are done in the WebSphere Application Console, beginning with the left-hand navigation menu.

Configure the service bus
  1. From the WebSphere Administrative Console, select Service integration > Buses.
  2. Click New.
  3. Enter the following and then click OK:
    • Name: DataIntakeJMSServer
    • Uncheck Bus Security

  1. Click on Next and Click on Finish on the next Screen. On successful creation. You can see the Bus as shown below:
Configure the bus members

To configure the Bus members, do the following:

  1. Select Service integration > Buses.
  2. Click the DataIntakeJMSServer created in the previous section.
  3. Under Topology on right hand side click on Bus members

  1. On the next page select the cycle server for Server:

  1. Click Next and in the next window select File Store

  1. Click on Next > Next > Finish. After successful creation you should be seeing the bus member i.e added
Configure the destinations

To configure the destinations for messaging, do the following:

  1. Select Service integration > Buses.
  2. Click the DataIntakeJMSServer.
  3. Under Destination Resources, click Destinations.

  1. Click on New and select Queue and give the Queue Name as DIQueue as shown below
  2. Click on Next and select the Bus member that is created earlier.

  1. Click on Next > Finish. After succesful creation of Queue you should be seeing it as shown below.

Configure JMS connection queue factory

To configure the JMS connection queue factory, do the following:

  1. Display the default messaging provider:
    • Select Resources > JMS Providers.
  2. In the opened window, select Default Messaging Provider as shown below

  1. In the opened window select Queue Connection Factory

  1. Click on New
  2. Enter the Connection factory Details as
    • Name : IntakeConnectionFactory
    • JNDI Name : IntakeConnection Factory
    • Bus : DataIntakeJMSServer
    • Provider End Point : <host> PortNumber
      • port number above will be the server end point address and can be checked at Server > Ports

Provider Endpoint above will be <host>:<SIB end point port Address>

SIM end point can be seen by clicking on Server > Ports >

Default will be localhost:7276

  1. Click on Apply and save to master configuration.

Note: After successful creation of Queue Connection factory, you should be seeing it under Queue Connection factories.

Configure JMS Queue
  1. Select Resources > JMS Providers
  2. Click on Default messaging provider and click on Queues under the Additional Properties. Click on New
  3. Give the Queue Details as mentioned below
    • Name: DIQueue
    • JNDI Name: DIQueue
    • Bus Name: DataIntakeJMSServer
    • Queue : DIQueue
    • Apply and save to master configuration.

Verify the messaging engine startup

To verify the messaging engine startup, do the following:

  1. Ensure the application server has been restarted.
  2. Start the WebSphere Administrative Console.
  3. Select Service integration > Buses.
  4. Click DataIntakeJMSServer.
  5. Under Toplology click on Messaging engines.
  6. You should see the green arrow under Status to note the Node.server-DataIntakeJMSServer Messaging Engine has been started.

Update Global Security Settings

In Application Server Admin Console,

  1. Go to Security -> Global Security (in the left side menu)
  2. Under Authentication panel -> Expand RMI/IIOP security
  3. Click on CSIv2 inbound communications ->
    • CSIv2 Transport Layer ->
    • set Transport : SSL-supported
    • Similarly, for CSIv2 outbound communications ->
    • CSIv2 Transport Layer ->
    • set Transport : SSL-supported
  4. Apply and Save the configuration settings. Restart the Cycle Server.

Configuration on the DI Client side.

  1. Update the below parameters in CycleClient.properties file on the DI client/conf folder
    • contextFactory=com.ibm.websphere.naming.WsnInitialContextFactory
    • provider.url=iiop://slc03sue.us.oracle.com:2812 (port number should match with the Boot strap address on WebSphere application server ports)
  2. The below mentioned jars should be provided on the client side lib directory. These are available in the WebSphere libraries
    • com.ibm.ws.ejb.thinclient_9.0.jar
    • com.ibm.ws.orb_9.0.jar
    • com.ibm.ws.sib.client.thin.jms_9.0.jar

 

 

 

 

 

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us