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:
- Configure the service bus
- Configure the bus members
- Configure the destinations
- Verify the messaging engine startup
- Configure JMS connection queue factory
- 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:
- SIB will be pointed to a Cycle server which should be up and running.
- The property dataIntake.enabled should be set to true on server side of Cycle.
- Need to provide Customer Name, Intake Profile name, and Class Name (In case of Enrollment) in the loading file, which should be created on OIPA side prior to Data Intake. The steps to be followed on OIPA side can be found in Data Intake Guide.
The following steps are done in the WebSphere Application Console, beginning with the left-hand navigation menu.
Configure the service bus
- From the WebSphere Administrative Console, select Service integration > Buses.
- Click New.
- Enter the following and then click OK:
- Name: DataIntakeJMSServer
- Uncheck Bus Security
- 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:
- Select Service integration > Buses.
- Click the DataIntakeJMSServer created in the previous section.
- Under Topology on right hand side click on Bus members
- On the next page select the cycle server for Server:
- Click Next and in the next window select File Store
- 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:
- Select Service integration > Buses.
- Click the DataIntakeJMSServer.
- Under Destination Resources, click Destinations.
- Click on New and select Queue and give the Queue Name as DIQueue as shown below
- Click on Next and select the Bus member that is created earlier.
- 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:
- Display the default messaging provider:
- Select Resources > JMS Providers.
- In the opened window, select Default Messaging Provider as shown below
- In the opened window select Queue Connection Factory
- Click on New
- 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
- 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
- Select Resources > JMS Providers
- Click on Default messaging provider and click on Queues under the Additional Properties. Click on New
- 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:
- Ensure the application server has been restarted.
- Start the WebSphere Administrative Console.
- Select Service integration > Buses.
- Click DataIntakeJMSServer.
- Under Toplology click on Messaging engines.
- 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,
- Go to Security -> Global Security (in the left side menu)
- Under Authentication panel -> Expand RMI/IIOP security
- Click on CSIv2 inbound communications ->
- CSIv2 Transport Layer ->
- set Transport : SSL-supported
- Similarly, for CSIv2 outbound communications ->
- CSIv2 Transport Layer ->
- set Transport : SSL-supported
- Apply and Save the configuration settings. Restart the Cycle Server.
Configuration on the DI Client side.
- 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)
- 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