Error: The JCA Binding Component is unable to startup the Resource Adapter specified in the element: location='eis/DB/soademo'

Facing the following error while testing the CreditCardValidation composite from the activity guide:

BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'CreditCardDBServiceSelect' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. CreditCardValidation:CreditCardDBService [ CreditCardDBService_ptt::CreditCardDBServiceSelect(CreditCardDBServiceSelect_inputParameters,CreditcardsCollection) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element  The JCA Binding Component is unable to startup the Resource Adapter specified in the  element: location='eis/DB/soademo'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '' element in weblogic-ra.xml has not been set to eis/DB/soademo. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. 

Issue is with the JCA Adapter setting, follow the below steps to create new:

Creating a Data Source

•  Login to weblogic console - http://localhost:7001/console
• GOTO Domain -> Services -> Data Sources
• Click New, and enter the following values to the properties
• Name: soademoDatabase
• JNDI Name: jdbc/soademoDatabase
• Database Type: Oracle
• Click Next, and then Next
• Enter the connection properties details in the Connection properties page, then click Next
• Click Test Configuration to test the data base connection properties
• Click Next, and select the targets and then click Finish

Creating a Connection Pool

• GOTO Domain -> Deployments
• Click on DBAdapter in deployments page
• Click Configuration tab, and then click Outbound Connection Pools tab.
• Click New, Select javax.resource.cci.ConnectionFactory, and then click Next.
• Provide JNDI Name: field, enter eis/DB/soademoDatabase.
• Note: The JNDI value that you enter in this step is not the same value that you entered in create data source. The JNDI name specified in this step must match the value you enter in your database connection you create when building your application
• Click Finish.
• In the Path field, select or enter the path of a deployment plan file. The path must end with ".xml".
• In the Properties field, enter the value for xADataSourceName as jdbc/soademoDatabase.
• Note: Tricky part is to modify the Datasource name for xADataSourceName, please click on the corresponding row for column PropertyValue and then use "EnterKey from Key borad"

Ref: http://docs.oracle.com/cd/E12839_01/integration.1111/e10231/life_cycle.htm#BABBEDBF