Error on Deploying BPEL: java.lang.NoClassDefFoundError: com/collaxa/cube/util/JavaHelper

The following error occurred while deploying the BPEL composite:

[05:11:07 PM] HTTP error code returned [500]
[05:11:07 PM] Error message from server:
There was an error deploying the composite on soa_server1: Deployment Failed: Error occurred during deployment of component: Fulfillment to service engine: implementation.bpel, for composite: POProcessing: ORABPEL-05250

Error deploying BPEL suitcase.
error while attempting to deploy the BPEL component file "C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\dc\soa_4f56ee57-8dc4-401a-8267-3b8fed1bb15f"; the exception reported is: java.lang.NoClassDefFoundError: com/collaxa/cube/util/JavaHelper

This error contained an exception thrown by the underlying deployment module.
Verify the exception trace in the log (with logging level set to debug mode).
.
 
[05:11:07 PM] Check server log for more details.
[05:11:07 PM] Error deploying archive sca_POProcessing_rev1.0.jar to partition "default" on server soa_server1 
[05:11:07 PM] ####  Deployment incomplete.  ####
[05:11:07 PM] Error deploying archive file:/C:/JDeveloper/mywork/POApplication/POProcessing/deploy/sca_POProcessing_rev1.0.jar 
 (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)

Sol: Trying to get the solution for this issue.

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

Unable to start SOA Managed server - Server is Running in Development Mode and Native Library(terminalio) to read the p assword securely from commandline is not found.

When I tried to start SOA Managed server, it prompted for username. Once I entered the username it is throwing the following below error and terminated

<Jun 16, 2016 3:30:32 PM IST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:weblogic
<Jun 16, 2016 3:30:38 PM IST> <Error> <Security> <BEA-090783> <Server is Running in Development Mode and Native Library(terminalio) to read the p
assword securely from commandline is not found.>
<Jun 16, 2016 3:30:38 PM IST> <Notice> <WebLogicServer> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
<Jun 16, 2016 3:30:38 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Solution: Problem with the JRE path Please look at the reference  https://community.oracle.com/thread/934173?tstart=0

As an alternative you can provide username and password in startManagedWebLogic.cmd file
As
set WLS_USER=weblogic

set WLS_PW=weblogic1

Jdeveloper hangs on wsil connection creation

In JDeveloper 11g if we try to create of test the WSIL connection with wrong detail of URL, username or password, JDeveloper hangs.

Make sure that to provide the correct details of URL, username and password while creating the WSIL connection

To verify the URL, access the same URL in a browser. Provide username and password when it prompts. If you see the response then the URL works fine.

You can see the result like this:

WSIL result when you browse

Note: The URL http://localhost:7001/inspection.wsil is a path that works for the Oracle
SOA Suite 11g environment

JDeveloper will not start and hungs

One of the best solution for this to get resolved..
When you have problem with JDeveloper like not starting or crashing
Delete JDeveloper's system directory from JDeveloper home directory

The default location for JDeveloper home directory will be:
 XP; C:\Documents and Settings\username\Application Data\JDeveloper\
 Windows 7: C:\Users\<username>\AppData\Roaming\JDeveloper\

 Under the JDeveloper home directory you can see a directory named as systemxx.x.x.xx...
Ex : system11.1.1.7.40.64.93 (for JDeveloper 11.1.1.7.0)

First close the JDeveloper and delete the system directory. then after start JDeveloper again, JDeveloper will recreate a new fresh one.
Note: All your JDeveloper settings will be lost on deleting the system directory !!!!

System directory contains the JDeveloper custom settings, if you delete this directory it wont impact your work folder (projects).