Chapter 8. Integration using WebSphere Business Integration Adapters 231
Figure 8-22 Generate Deploy code for StockQuoteInfo service
Configuring StockInfo service session bean JNDI bindings
You configure the JNDI name for the STOCKINfoHubRequest session bean. You
also configure the JNDI bindings for the WebSphere MQ connection factory and
queue that are used by the service.
1. Switch to the J2EE perspective.
2. Double-click the EJB deployment descriptor in the JDBCAdapterEJB project.
3. Select the References tab.
4. Expand the StockINFOHubRequestService and select the ResourceRef
item. Enter wbia/ibm/com/JDBCAdapterQCF as the JNDI name in the
WebSphere Bindings section as shown in Figure 8-23 on page 232.
232 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
Figure 8-23 StockInfo Service EJB bindings
5. Select the ResourceEnvRef item. Enter
wbia/ibm/com/JDBCAdapterJDBCADAPTER/REQUESTQUEUE as the JNDI name in
the WebSphere Bindings section for the queue as shown in Figure 8-24
Figure 8-24 ResourceRef JNDI name
6. Press Ctrl+S to save the EJB Deployment Descriptor.
Chapter 8. Integration using WebSphere Business Integration Adapters 233
8.5.6 Creating and configuring the integrated test environment
This step create the integrated test environment (ITE) for WebSphere Business
Integration Server Foundation Version 5.1. You enable the administration console
so that you can do some configuration.
1. Using the servers view, right-click an empty area and choose New
→ Server
and Server Configuration.
2. Expand the WebSphere Version 5.1 folder, and select the Integration Test
Environment. Name the server TEST. Click Finish.
3. In the server tab, double-click the TEST server to open the server
configuration.
4. Select the Configuration tab, and click Enable administration console as
shown in Figure 8-25.
Figure 8-25 Enable administration console
5. Press Ctrl+S to save the configuration.
Now that the server is configured for administration, you can configure the
queues and environment to run the service and projects.
Note: You can reuse an existing Integration Test Environment if you created
one earlier.
234 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
Configuring WebSphere MQ JMS providers
Next, you create the WebSphere MQ JMS providers. You also create the queue
connection factory and the queue that the WebSphere Business Integration
adapter requires.
1. Start the test server to begin the configuration and administration tasks.
2. Right-click the server and choose Run Admin Console.
3. Login then, choose Resource
→ WebSphere MQ JMS Providers .
4. Click the WebSphere MQ Queue Connection Factories link to begin the
process of creating the queue connection factory that you created earlier.
5. Click New to create a new queue connection factory.
6. Enter the details shown in Table 8-2.
Table 8-2 Values for the queue connection factory
7. Click OK to save the configuration.
8. Click Save and then click Save again at the Save to Master Configuration
screen.
Enabling client authentication for a remote queue manager
If your queue manager is not on the same machine as the machine with
WebSphere Business Integration Server Foundation or the ITE, you need to
enable client authentication.
Configuration Property Name Value
Name JDBCAdapterQCF
JNDI Name wbia/ibm/com/JDBCAdapterQCF
Queue Manager ITF
Host <ip address of queue manager host>
Port <listener port for queue manager>
Channel <server connection channel for QM>
Chapter 8. Integration using WebSphere Business Integration Adapters 235
Creating J2C authentication data
A J2C authentication entry allows you to specify the user ID and password to be
used when connecting to the queue connection factory. Using the administration
console, configure the authentication entry:
1. Choose Security
→ JAAS Configuration.
2. Click the J2C Authentication Data link. Select New to create a new J2C
authentication data entry.
3. Enter the details shown in Table 8-3.
Table 8-3 J2C authentication data entry properties
User ID is the user ID that you used for the queue manager, the login user of
the machine where the queue manager is running.
4. Click OK. Remember to save the changes that you have made to the master
configuration.
Configuring the queue connection factory for authentication
Now, you set the queue manager to use container-managed authentication using
the J2C authentication alias. You also need to change the transport type from
interprocess bindings to client, because the queue manager is remote.
1. Select Resource
→ WebSphere MQ JMS Providers.
2. Click the WebSphere MQ Queue Connection Factories link.
3. Click the JDBCAdapterQCF link to edit the properties of the queue
connection factory.
4. Enter the details shown in Table 8-4.
Table 8-4 J2C connection factory remote properties
Configuration Property Name Value
Alias JDBCAdapterQCF
User ID Queue Manager User ID
Password Password for user id
Configuration Property Name Value
Container-managed Authentication Alias localhost/JDBCAdapterQCF
Mapping-Configuration Alias ClientContainer
Tran s por t Type CLIENT
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.