Prerequisite
WebShpere Application Server 6.1.0.13
Oracle 10g with CDM schemas on it
Steps
1. Login to WAS admin console (http://localhost:9060/admin)
2. Create J2C Authentication Entries
2.1. Go to Security >> Secure administration, applications, and infrastructure >> Java Authentication and Authorization Service >> J2C authentication data
2.2. Click on New, and create the following authentication entities
2.2.1. ADS authentication alias
2.2.1.1.Alias Name: ads
2.2.1.2.User Name: ads user name
2.2.1.3.Password: ads user’s password
2.2.2. DMA authentication alias
2.2.2.1.Alias Name: dma
2.2.2.2.User Name: dma user name
2.2.2.3.Password: dma user’s password
2.2.3. DMO authentication alias
2.2.3.1.Alias Name: dmo
2.2.3.2.User Name: dmo user name
2.2.3.3.Password: dmo user’s password
2.2.4. RTDS authentication alias
2.2.4.1.Alias Name: rtds
2.2.4.2.User Name: rtds user name
2.2.4.3.Password: rtds user’s password
2.2.5. IS authentication alias
2.2.5.1.Alias Name: is
2.2.5.2.User Name: is user name
2.2.5.3.Password: is user’s password
2.2.6. RA authentication alias
2.2.6.1.Alias Name: ra
2.2.6.2.User Name: is user name
2.2.6.3.Password: is user’s password
2.3. Click Apply >> Ok.
2.4. Save the changes to master configuration
3. Create JDBC Provider
3.1. Go to Resources >> JDBC >> JDBC Providers >> Select the scope as server1 >> Click on New >> Select the following …
3.1.1. Database type : Oracle
3.1.2. Provider type : Oracle JDBC Driver
3.1.3. Implementation type : Connection pool data source
3.1.4. Name : Oracle JDBC Driver ( you can give any name )
3.1.5. Description : You can give any description
3.2. Click Next
3.3. Specify the path of “ojdbc14.jar” in the text box labeled ${ORACLE_JDBC_DRIVER_PATH} and click >> Next
3.4. Click Finish
3.5. Save the changes to master configuration
4. Create JDBC Data Sources
4.1. Go to Resources >> JDBC >> Data Sources >> Select the scope as server1 >> Click on New
4.2. Create the following data sources
4.2.1. ADS Data source
4.2.1.1.Data source name: adsDataSource
4.2.1.2.JNDI Name: jdbc/adsDataSource
4.2.1.3.Authentication Alias: ads
4.2.2. DMA Data source
4.2.2.1.Data source name: dmaDataSource
4.2.2.2.JNDI Name: jdbc/dmaDataSource
4.2.2.3.Authentication Alias: dma
4.2.3. DMO Data source
4.2.3.1.Data source name: dmoDataSource
4.2.3.2.JNDI Name: jdbc/dmoDataSource
4.2.3.3.Authentication Alias: dmo
4.2.4. RTDS Data source
4.2.4.1.Data source name: rtdsDataSource
4.2.4.2.JNDI Name: jdbc/rtdsDataSource
4.2.4.3.Authentication Alias: rtds
4.2.5. IS Data source
4.2.5.1.Data source name: isDataSource
4.2.5.2.JNDI Name: jdbc/isDataSource
4.2.5.3.Authentication Alias: is
4.2.6. RA Data source
4.2.6.1.Data source name: raDataSource
4.2.6.2.JNDI Name: jdbc/raDataSource
4.2.6.3.Authentication Alias: ra
4.3. Select JDBC provider
4.3.1. Select an existing JDBC provider
4.3.2. And Select Oracle JDBC Driver from the dropdown
4.3.3. Click Next
4.4. Enter the following details
4.4.1. URL: jdbc:oracle:thin:@ Database server IP : DB server port : SID where Database server IP is the IP of database server, port is the port on which Database is running ideally 1521 or 1522 and SID is database name.
4.4.2. Data store helper class name: Oracle10g data store helper
4.5. Click Next
4.6. Click Finish
4.7. Repeat step 4c to 4f.
4.8. Save the changes to master configuration
5. Create & Configure Service Integration Buses
5.1. Go to System Integration >> Buses >> Click on New
5.1.1. Bus name: ADS Bus
5.1.2. Uncheck “Bus Security” option
5.1.3. Click Next
5.1.4. Click Finish
5.2. Go to System Integration >> Buses >> Click on New
5.2.1. Bus name: RTDS Bus
5.2.2. Uncheck “Bus Security” option
5.2.3. Click Next
5.2.4. Click Finish
5.3. Save the changes to master configuration
5.4. Go to System Integration >> Buses >> Select ADS Bus
5.4.1. Click Bus members
5.4.2. Click Add
5.4.3. Click on option button labeled Server and select server1
5.4.4. Click Next
5.4.5. Select the type of message store as “Files store”
5.4.6. Click Next
5.4.7. Keep default settings and click Next
5.4.8. Click Finish
5.5. Go to System Integration >> Buses >> Select RTDS Bus
5.5.1. Click Bus members
5.5.2. Click Add
5.5.3. Click on option button labeled Server and select server1
5.5.4. Click Next
5.5.5. Select the type of message store as “Files store”
5.5.6. Click Next
5.5.7. Keep default settings and click Next
5.5.8. Click Finish
5.6. Save the changes to master configuration
5.7. Go to System Integration >> Buses >> Select ADS Bus
5.7.1. Click Destinations
5.7.2. Click New
5.7.3. Select destination type: Topic Space
5.7.4. Click Next
5.7.5. Identifier: ADS Topic
5.7.6. Click Next
5.7.7. Click Finish
5.7.8. Save the changes to master configuration
5.8. Go to System Integration >> Buses >> Select RTDS Bus
5.8.1. Click Destinations
5.8.2. Click New
5.8.3. Select destination type: Queue
5.8.4. Click Next
5.8.5. Identifier: RTDS
5.8.6. Click Next
5.8.7. Bus member: Select server1
5.8.8. Click Next
5.8.9. Click Finish
5.8.10. Save the changes to master configuration
6. Define the Connection Factories
6.1. Define a Queue Connection Factory
6.1.1. Go to Resources >> JMS >> JMS providers
6.1.2. Select scope as server1 >> Default Messaging Provider
6.1.3. Click on Queue Connection Factories
6.1.4. Click New
6.1.4.1.Name: rtdsQueueConnectionFactory
6.1.4.2.JNDI Name: jms/RTDSQueueConnectionFactory
6.1.4.3.Select bus type: RTDS Bus
6.1.4.4.Click Ok
6.1.4.5.Save the changes to master configuration
6.2. Define a Topic Connection Factory
6.2.1. Go to Resources >> JMS >> JMS providers
6.2.2. Select scope as server1 >> Default Messaging Provider
6.2.3. Click on Topic Connection Factories
6.2.4. Click New
6.2.4.1.Name: adsTopicConnectionFactory
6.2.4.2.JNDI Name: jms/ADSTopicConnectionFactory
6.2.4.3.Bus name: ADS Bus
6.2.4.4.In the provider endpoints: host_name/hostIP:SIB_ENDPOINT_ADDRESS:BootstrapBasicMessaging
6.2.4.5.Click Ok
6.2.4.6.Save the changes to master configuration
7. Define the Queue & topic
7.1. Define Queue
7.1.1. Go to Resources >> JMS >> JMS providers
7.1.2. Select scope as server1 >> Default Messaging Provider
7.1.3. Click on Queues
7.1.4. Click New
7.1.4.1.Name: RTDS Request Queue
7.1.4.2.JNDI Name: queue/DecisionRequestQueue
7.1.4.3.Bus Name: RTDS Bus
7.1.4.4.Queue Name: RTDS
7.1.4.5.Click Ok
7.1.4.6.Save the changes to master configuration
7.1.5. Click New
7.1.5.1.Name: RTDS Reply Queue
7.1.5.2.JNDI Name: queue/DecisionReplyQueue
7.1.5.3.Bus Name: RTDS Bus
7.1.5.4.Queue Name: RTDS
7.1.5.5.Click Ok
7.1.5.6.Save the changes to master configuration
7.2. Define Topic
7.2.1. Go to Resources >> JMS >> JMS providers
7.2.2. Select scope as server1 >> Default Messaging Provider
7.2.3. Click on Topics
7.2.4. Click New
7.2.4.1.Name: ADS Topic
7.2.4.2.JNDI Name: jms/ADSTopic
7.2.4.3.Bus Name: ADS Bus
7.2.4.4.Topic Space: ADS Topic
7.2.4.5.Click Ok
7.2.4.6.Save the changes to master configuration
8. Set Activation specifications
8.1.1. Go to Resources >> JMS >> JMS providers
8.1.2. Select scope as server1 >> Default Messaging Provider
8.1.3. Click on Activation specifications
8.1.4. Click New
8.1.4.1.Name: RTDS Queue
8.1.4.2.JNDI Name: eis/RTDSQueue
8.1.4.3.Destination type: Queue
8.1.4.4.Destination JNDI Name: queue/DecisionRequestQueue
8.1.4.5.Bus Name: RTDS Bus
8.1.4.6.Authentication Alias: node_name/rtds
8.1.4.7.Click Ok
8.1.4.8.Save the changes to master configuration
8.1.5. Click New
8.1.5.1.Name: ADS Topic
8.1.5.2.JNDI Name: eis/ADSTopic
8.1.5.3.Destination type: Topic space
8.1.5.4.Destination JNDI Name: jms/ADSTopic
8.1.5.5.Bus Name: ADS Bus
8.1.5.6.Authentication Alias: node_name/ads
8.1.5.7.Click Ok
8.1.5.8.Save the changes to master configuration
Posts
