Datasource Configuration on server

To Create DB datasource in weblogic server Console

Part 1: Create DataSource

S1: Services -> Data sources -> new -> Genric Data Source

Ex: Name: testDS

    JNDI Name: jdbc/testDS

Database Driver

S2: Create new JDBC Data Source: (based on DB connection)

Database Name: XE (SID of database)

host name : localhost

port: 1521

Database User Name : hr  

password: hr  

password: hr 

Test Configuration

S3 : Target on server 

S4: Finish (Datasource is created: you can check by clicking again datasource.)

Part 2: Creating connection Pool

S1: Go to deployment -> DB Adapter -> Configuration -> Outbound Connection 

pools -> clickOn plus button or new

S2: JNDI Name: eis/db/test

Note: This JNDI name is for connection pool

This JNDI name only we give into DB Adapter while configure in composite in SOA.

"Now check in + button of connectionFactory (we can find JNDI name of 

connection pool)"

Part 3: Connecting connection pool with datasource 

S1: Click on created JNDI (eis/db/test) of connection pool, 

It will show the outbound connection properties"

S2: Give the JNDI name of datasource:

jdbc/testDS  and press enter and save

Part 4: Update Changes

go to deployment -> check DB Adapter -> Update.

OracleDBAdapter Configuration:

Oracle JCA adapter for DB enables a BPEL process to communicate with Oracle databases or third party databases through JDBC. 

The Oracle Database Adapter service is defined within a BPEL process partner link by using the Adapter Configuration Wizard of Oracle BPEL Process Manager (Oracle BPEL PM).

DB Adapter Configuration in weblogic server

In weblogic server console

o   Create JDBC Data Source

o   Set JDBC data Source Properties.

o   Configure transaction options- XA or Non-XA

o   Configure connection  properties

o   Test Connections

-          Deploy new JDBC Data Sources by selecting target server

-          Create an outbound connection pool for DB adapter.

-          Add JNDI name of new JDBC data source in properties values of outbound connection pool.

How the Oracle Database Adapter Works:

The Oracle Database Adapter is a JCA 1.5 connector, which is deployed to the application server during installation.

The Oracle Database Adapter consists of multiple instances; each instance represents a connection to a database end point. Different SOA processes may point to the same adapter instance (database), while different service endpoints in a SOA process may point to different adapter instances (databases).

Because each adapter instance points to a single database, there is a one-to-one correspondence from adapter instances to application server data sources. Out of the box there is a single Oracle Database Adapter instance named eis/DB/SOADemo, which points to the data source jdbc/SOADataSource.

The list of adapter instances is stored in a deployment descriptor file, weblogic-ra.xml on Oracle WebLogic Server. (It is inside of DbAdapter.rar, which contains also the Java class files in DBAdapter.jar). Configuring an Oracle Database Adapter instance is more about creating the underlying data source: getting the correct JDBC driver and connection URL.

WLDatabaseConfiguration

Persistence Store: Permanent storage.

2 types of persistence store: FileStore and databaseStore(i.e JDBCStore)

File Store: Storing file.

Resource Manager: manage the resource.

While creating File store:

-> Give the directory of selected server.

ex: ms1 then path will be wls1. At this directory it will store file.

log rotational policy doesnt take place in development mode(It only created when server is rebooted)

In Production mode each log is created of size 500KB each time .

we can see t count by default.

we can also rotate based on time.

repeted= true for cluster

Domain is server configuration file.

server read the weblogic.xml

Application can be deployed anywhere, doesnt matter manage server is part of cluster or not.

cluster is mainly used for avavbility for server.