Creating Topics and the Connection Factory

Under Resources/JMS on the left side of the console, click Topics.
From the All scopes list, select Cell=<server_name><node_number>Cell.
Click New.
Verify that Default messaging provider is selected.
Click OK.
Type the following information in the corresponding text boxes to create a new Topic (any settings not listed below should be left at the default WebSphere value):

Name: fiper station

JNDI name: fiper/jms/station

Topic name: station
From the Bus name list, select Fiper Bus.
From the Topic space list, select Default.Topic.Space.
Click OK.

The topic is created.
Click New.
Verify that the Default messaging provider is selected.
Click OK.
Type the following information in the corresponding text boxes to create a new topic (any settings not listed below should be left at the default WebSphere value):

Name: job monitor

JNDI name: fiper/jms/jobmonitor

Topic name: jobmonitor
From the Bus name list, select Fiper Bus.
From the Topic space list, select Default.Topic.Space.
Click OK.
Under Resources/JMS on the left side of the console, click Connection factories.

Important: Be careful to select Connection factories and not other similar options located near it.
From the All scopes list, select Cell=<server_name><node_number>Cell.
Click New.
Verify that Default messaging provider is selected.
Click OK.
Type the following information in the corresponding text boxes to create a new Connection Factory:

Name: Fiper CF

JNDI name: fiper/jms/connectionfactory
From the Bus name list, select Fiper Bus.
In the Target inbound transport chain text box, type the following entry:

InboundBasicMessaging
In the Provider endpoints text box, type the following entry, substituting the server’s host name and the endpoint address noted in Starting WebSphere and Determining Server Port Numbers.

For example:
```
seecomputer:7276:BootstrapBasicMessaging
```
Note: This port number (7276) is the SIB_ENDPOINT_ADDRESS that you noted previously.
From the Nonpersistent message reliability list, verify that Express nonpersistent is selected .
Type the following information in the corresponding text box:

Client identifier: fiper
Select <Node_name>.server1-FiperBus as the Durable Subscription home.
From the Persistent message reliability list, select Assured persistent.
From the Authentication alias for XA recovery list, select the appropriate alias.

Your option should appear similar to one of the following examples:
- acscomputerNode01/fiperOracleAuth
- acscomputerNode01/fiperDB2Auth
Note: This setting is necessary if security will be enabled on your SIMULIA Execution Engine, but it will not impact a non-secure SIMULIA Execution Engine.
From the Mapping-configuration alias list, select DefaultPrincipalMapping.
From the Container-managed authentication alias list, select the appropriate alias.

Note: This setting is necessary if security will be enabled on your SIMULIA Execution Engine, but it will not impact a non-secure SIMULIA Execution Engine.
Click Apply.
In the Additional Properties area on the right side of the console, click Connection pool properties.
In the Connections timeout text box, verify that 180 appears.
Type the following information in the corresponding text boxes:

Maximum connections: 100
Minimum connections: 25
Click OK.