Hi, I go to http://localhost:7001/em and click on SOA folder in the left panel. I can clearly see the soa_infra(soa_server1) under the SOA folder. There is a default partition under the soa_infra on which I deploy a BPEL application as a jar file (This jar file is generated by the JDeveloper.) The BPEL deploys successfully on the soa_server1 without any issues or error messages. The log file confirms that the BPEL got deployed successfully. Under the default partition on the left panel I can see the name of the BPEL now. I click on the BPEL name and look at the detail page. Over there, the "Test" tab is disabled. There are no instances or faults. Also under the "component Metrics" section, I don't see anything but a message: "Unavailable". I am already spending 3 days trying to find out what may be wrong and resolve the issue but I haven't been successful. Please help! Thanks.
It is a simple BPEL process Arik. I have just started this process and currently it is not hooked into external services and it doesn't use any resources. I t has one operation that gets a message and replies with a simple string.
Hi 952205, I start the soa_server1 manually right after I bring up the weblogic. In EM console (localhost:7001/em), I can see the soa_server1 is in "Running" state. There is an error message that comes up when I start the weblogic. It says something about the messaging server and I am not sure if it is related to the problem that I have: "<Error> <oracle.sdp.messaging.client> <SDP-25503> <Unable to connect to the messaging server.
javax.naming.NameNotFoundException: While trying to lookup 'OraSDPM.ejb/sdpmessagingserver/MessagingStoreRemote' didn't find subcontext 'OraSDPM'. Resolved ''; remaining name 'OraSDPM/ejb/sdpmessagingserver/MessagingStoreRemote'"
I basically need to test the BPEL and currently the "Test" tab is disabled.
I resolved this issue. The problem was that the deployable jar file was somehow defected. A new project was deployed successfully and I could see the components and test the BPEL. I thank you for your replies.