Tuesday, December 08, 2009

Creating connection with jdev to Process Server

You need to download jdeveloper 10131 from the oracle site.

Once donwloaded.

YOu need to copy the bpm-services.jar from SOA_HOME\bpel\system\services\lib to \integration\lib

Restart the jedeveloper.

The bpm-services.jar contains changes to java-wsdl-mapping and DecisionServiceInfoTemplate, which are required for DecisionServices to run on WebSphere.


Ensure that bpelPlatform is set to WebSphere_5 in the ORACLE_HOME\bpel\system\config\collaxa-config.xml file


Ensure that platform is set to WebSphere_5 in the ORACLE_HOME\bpel\utilities\ant-orabpel.properties file

check the SOA_HOME\bpel\utilities\ant-orabpel.properties

file to get the admin user password details,rmi number and other necessary details.


Then go to jdeveloper

Create an application server connection of the Standalone OC4J 10.1.3 type.

You might get some error while testing the conenction.IT occurs because of the absense of opmn in websphere.


Create an Integration Server connection to hostname:port. The default port is as mentioned in the constants.properties file.

Choose the above-created AppServer connection and test the connection.

BPEL and ESB should pass when this connection is tested.


Now create a simple bpel process and deploy it in the bpel process deployer to verify if the process exist in bpel console.

Since the application server connection is not running successfully.The process gets deployed in BPEL Server but it does not get deployed in websphere.


When you initiate a BPEL process, you could encounter the WSDL not found error. Something like this

Failed to read WSDL from http://ARAHI-PC1:7200/orabpel/arpit/BPELProcess1/1.0/BPELProcess1?wsdl:WSDL not found


To resolve this error, ensure that the proxy settings have been configured correctly

do the following steps:-

Log in to the IBM Admin console.

Navigate to Servers, Application Servers. The Application Servers page is displayed.

Click Java and Process Management, Process Definition, Java Virtual Machine, and Custom Properties.

Verfiy the values for the following custom properties


http.proxySet: Set to true if using a proxy server, else false

http.proxyHost: URL of the proxy server

http.proxyPort: Port of the proxy server

http.nonProxyHosts: Pipe(|) separated list of addresses for which proxy will be bypassed.


Since i am not using a proxy server i will set the http.proxtSet to false

Restart SOAServer and check the wsdl again in bpel console.YOu should be able to initiate the bpel process.


To change logging level to get more details about the issue.

Do the following


Log in to WebSphere Administrative Console through the URL http://[hostname]:9060/admin.


In the WebSphere Administrative Console navigation tree, in the Troubleshooting section, select Logging and Tracing > Change Log Detail Levels.

On the Configuration tab, type the following string:
*=info:com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl=severe


Click OK.

Select Save changes to master configuration.

Restart OracleBPELServer.

No comments: