Date post: | 08-Jan-2016 |
Category: |
Documents |
Upload: | saileshan-subhakaran |
View: | 32 times |
Download: | 0 times |
of 10
Prepared by Abhishek Ajral
Configuring Database DataSource and JNDI Name in Weblogic
"please note this document is generic please follow the name and other details as per as your configuration or
requirement following proper naming convention. ; for example soa_server1 is used as soa server name in
this docs if in your configuration soa server name is wls_soa1 than consider the same and for all"
There are basically 3 steps inorder to setup and configure a DBAdapter in a SOA Application.
1.Configure a datasource for the underlying database, associate a JNDI name to it.
2.Configure an outbound connection pool, and link it with the datasource using the same JNDI name.
3. Redeploying the resource adapter (DB adapter) for the server to accommodate the reflected changes.
Start :-
1) Login to Weblogic server console using - http://:7001/console. (please provide the host
name and other details as per as your configuration)
2) Go to the Domain structure as shown in the screen print
Prepared by Abhishek Ajral
3) In order to enable the buttons click on the Lock & Edit button under Change Center on the top left
corner.
Step 1 : Configure a Datasource for the underlying Database, associate a JNDI name to it
This step is done using the Weblogic Admin Console. Please make sure your database is up and running
before this step.
Soa_domain --> Services --> Data Sources --> New --> Generic Data Source -->
Prepared by Abhishek Ajral
Prepared by Abhishek Ajral
Standard naming convention for database sources would have a JNDI name prefixed with "jdbc/". You will
use this name later to associate a connection pool to this datasource.
Select the appropriate driver
Give the underlying Database details, test the connection in the next screen
Prepared by Abhishek Ajral
Make sure that you are able to test the configuration by clicking on the Test Configuration tab as shown
below:
Select the server that is running the SOA infrastructure. This makes this datasource to run on that particular
server, making this available to all the apps running on that server
Prepared by Abhishek Ajral
Click on finish. After this, one should see this newly configured datasource in the Data Sources summary
screen.
Now that the datasource is setup, and a JNDI name associated to it,it is required to create connections to this
database.
Step 2 : Configure an outbound connection pool, link it to the datasource using the JNDI name
In Weblogic Admin Console, soa_domain --> Deployments --> dbAdapter --> Configuration --> Outbound Connection Pools --> New
Prepared by Abhishek Ajral
Specify the name connection JNDI name as shown below and click on finish:
Note:
The connection JNDIs created for the DB adapter should be of the following naming convention: eis/DB/
In the above screen, we are giving a new JNDI name, and this will be used in the SOA Suite's DBAdapter configuration wizard to obtain reference to this connection pool. Now, we can see the newly configured JNDI name in the list of Outbound Connection Pools. This new connection pool has to be linked to the datasource that we've created before.
Prepared by Abhishek Ajral
Note:
1. Make sure that you are entering the JNDI name of the data source. 2. Also make sure there are not spaces.
3. Ensure you press the enter key after entering the value for the xaDataSourceName for the property.
Step 3: Redeploying the resource adapter (DB adapter) for the server to accommodate the reflected
changes.
Select the DBAdapter in deployments, Update-->Redeploy
Go to the Deployments link as shown below:
Prepared by Abhishek Ajral
Scroll down and check the DbAdapter applications check box as shown below:
Scroll up and click on update as shown below:
Make sure you see a message at the top of the screen saying, Selected Deployments were updated.
Prepared by Abhishek Ajral
In the Change Center panel in the upper left corner of your screen, click Activate Changes
Again, ensure that the message that the top of the screen reads, All changes have been activated. No restarts
are necessary.
End