Chapter 3. The Trader applications 47
Figure 3-11 Importing ECI J2C connector to WebSphere Studio Integration Edition
c. Click Finish.
5. In the case of the TraderIMS application, do the same step for IMS connector.
You have to choose ims.rar as the connector file name and specify
IMSConnector as the new project name.
6. If any tasks or errors remain in the Tasks field, you have to rebuild project,
then the tasks go away. You can do this step from the Project
→ Rebuild All
menu. If you get a broken link message, make sure that the Web project
references the lib project. Right-click the Web project and select Properties.
Select the Java build path
→ Order and Export tab and select TraderLib.
Then rebuild the project.
3.2.1 Configuring the test server in WSAD.IE
This section shows how to configure the test environment to run the Trader
application. We provide server definitions in the workspace; however, you have
to verify that the resource definitions in the server projects match your
In case you want to use your own server definitions, follow the instructions
To configure the test environment, do the following steps:
1. Open Server Perspective. As shown in Figure 3-12, at first you click (1) to
open a new perspective, and choose Server. Now you can see the Server
Perspective and you can go directly to Server Perspective by clicking (2).
48 WebSphere for z/OS V5 Connector Handbook
Figure 3-12 Opening Server Perspective
2. At the lower left of the window, you can see the Server Configuration panel.
Right-click Servers, and proceed with New
→ Server and Server
Configuration. Specify TraderServer in the Server name field, and other
options are left as defaults. Then click Finish.
3. Double-click TraderServer, and the configuration panel opens. First you
have to change to Security tab, and create three JAAS authentrication
– LocalUser: Specify your local administrator ID and password. This is used
as a JMS user authentication alias.
– TraderDB2User: Specify your DB2 user ID and password to get to DB2.
– TraderUser: Specify your CICS and IMS user ID and password. This alias
is used as authentication in the connection factory of J2C.
As a result, you can see the aliases as shown in Figure 3-13.
Figure 3-13 JAAS authentication alias
Setting up CICS/IMS connection factories
These activities depend on which Trader application you try to set up.
In case of TraderCICS create CICS ECI J2C connection factory on the J2C
tab. In the Node setting, you can see J2C Resource Adapters. Choose Add...
and you can select ECIConnector in Resource adapter name field, then click
Chapter 3. The Trader applications 49
Next you have to add connection factory. At first you select ECIConnector.
Second, you click the Add... button in the J2C Connection Factory field, as
shown below, to Resource adapter settings. The Name and JNDI name fields
should be specified as follows:
The container-managed authentication alias should be TraderUser. Then
Now you can see the Resource properties of the CICS ECI connector. As
shown in Figure 3-14 on page 50, specify server definitions if you have a
CICS Trader application. We specified Server name, connection URL, and
In the case of TraderIMS you have to add IMSConnector in the same way. In
case of TraderRRS, you have to add both.
In case of the TraderIMS application do the same steps 5 and 6 as for the
IMS Connector. The Name and JNDI name fields of J2C connection factory
should be specified as follows:
For Resource properties, we specified the values HostName, PortNumber,
50 WebSphere for z/OS V5 Connector Handbook
Figure 3-14 J2C connection factory settings
Setting up DB2 datasources
To do this?
In the case of the TraderDB application switch to the Datasource tab. Now
you have to configure the datasource to connect to DB2. Select Default DB2
JDBC Provider and Add new datasource. The important thing in this wizard
is checking on how to use this datasource from container-managed
persistence (CMP) field.
We used the following parameters to configure the DB2 datasource:
– Name: TraderDB2.
– JNDI name: jdbc/TraderDB2.
– Container-managed authentication alias: DB2User.
You may use any defined name here. Go to the Security tab and define an
alias that is valid for the given system you want to access.
– We checked the “Use this datasource from container-managed
persistence (CMP)” field.
– Database name: DB4B (in resource properties).