OWSM GATEWAY VIRTUALIZED BPEL PROCESS INVOCATION PROBLEM

Hi
This is the error i am getting when i try to invoke the VIRTUALIZED BPEL process from test page of OWSM. i have created a component and added service to it. But this error surfaced when i try to invoke the service. I can see the virtualized WSDL in internet explorer though.
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">null
<env:Body>
<env:Fault
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>env:Server</faultcode>
<faultstring>ORABPEL-08021 Cannot find partner wsdl. parnterLink "OWSM_SYNC_BPEL_PROCESS" is not found in process "OWSM_SYNC_BPEL_PROCESS" (revision "1.0") Please check the deployment descriptor of the process to find the correct partnerLink name. </faultstring>
null</env:Fault>
</env:Body>
</env:Envelope>

Hi Gurus,
Any update on the issue???
Regards,
Dev

Similar Messages

OWSM EMPTY BPEL PROCESS VIRTUALIZATION PROBLEM!!!!!!!!!!

Hi,
I developed an EMPTY BPEL PROCESS which gets instantiated by a FILE ADAPTER . I am trying to virtualize the process by using OWSM GATEWAYS, but get error when i test it in the test page option unders tools link in OWSM MONITOR.
I am also not sure about the efficacy of using gateways to virtualize an EMPTY BPEL PROCESS.
CAN WE USE GATEWAYS TO VIRTUALIZE AN EMPTY BPEL PROCESS INITIATED BY A FILE ADAPTER???????
Regards,
Vishnu

Hi,
I developed an EMPTY BPEL PROCESS which gets instantiated by a FILE ADAPTER . I am trying to virtualize the process by using OWSM GATEWAYS, but get error when i test it in the test page option unders tools link in OWSM MONITOR.
I am also not sure about the efficacy of using gateways to virtualize an EMPTY BPEL PROCESS.
CAN WE USE GATEWAYS TO VIRTUALIZE AN EMPTY BPEL PROCESS INITIATED BY A FILE ADAPTER???????
Regards,
Vishnu

Async BPEL Process Invocation...

We have a business process, which when invoked from BPEL console works fine, however, when we invoke it from an web application of ours, it does gets initiated, but fails later.
We have Apache Axis deployed in the same OC4J server as the Oracle BPEL PM(10.1.2.0.2), which exposes few EJBs as SOAP Services.
The Business Process invokes couple of SOAP Services and then creates a Task and then waits for task completion and based on task action invokes two other SOAP services.
When we invoke it from the BPEL Console, everything works fine. It also works fine, if we invoke it first (after startup) from BPEL Console and then through our web application.
However, if we invoke it first through our web application, then it does initiates, but fails at the Task creation. If we try to hit the BPEL Console, we get this error
Oracle BPEL Process Manager Full Cycle
An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
Attachments:
Build Information:
Oracle BPEL Server version 10.1.2.0.2
Build: 2196
Build time: Tue Jan 10 12:31:53 UTC 2006
Build type: release
Source tag: BPEL_10.1.2.0.2_GENERIC_060110.1200
Exception Message:
[java.lang.Exception]
Failed to create "ejb/collaxa/system/ServerBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/ServerBean not found
     at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:164)
     at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:333)
     at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:120)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
<b>Nothing works after that, unless we re-start.</b>
Once we re-start, BPEL Console works fine.
Investigating the flow of the business process, we find the "initiateTask" of the workflow is fine, but it failed at "initiateTaskActionHandler" with the following error:
<remoteFault>
<part name="code" >
<code>WSDLReadingError</code>
</part>
<part name="summary" >
<summary>Failed to read wsdl. Failed to read wsdl at "http://Uranus:9700/orabpel/default/TaskActionHandler/TaskActionHandler?wsdl", because "WSDLException: faultCode=INVALID_WSDL: The document: http://Uranus:9700/orabpel/default/TaskActionHandler/TaskActionHandler?wsdl is not a wsdl file or does not have a root element of "definitions" in the "http://schemas.xmlsoap.org/wsdl/" namespace or the "http://www.w3.org/2004/08/wsdl" namespace.". Make sure wsdl is valid. You may need to start the OraBPEL server, or make sure the related bpel process is deployed correctly. </summary>
</part>
</remoteFault>
<b>Below is the code as to how we are invoking the Business Process...using orabpel taglibs...</b>
<orabpel:locator domainId="default" password="bpel" contextEnv="jndi">
<orabpel:deliveryService processId="ApprovalProcess">
<orabpel:post title="ApprovalProcess">
<orabpel:part name="payload">
<customerObj xmlns="http://xmlns.misys.com/ApprovalProcess/approval">
<applicationNo><%= customer.getApplicationNo() %></applicationNo>
<customerId><%= customer.getCustomerId() %></customerId>
<primaryFirstName><%= customer.getPrimaryFirstName() %></primaryFirstName>
<primaryLastName><%= customer.getPrimaryLastName() %></primaryLastName>
<primaryCardName><%= customer.getPrimaryCardName() %></primaryCardName>
<primaryDay><%= customer.getPrimaryDay() %></primaryDay>
<primaryMonth><%= customer.getPrimaryMonth() %></primaryMonth>
<primaryYear><%= customer.getPrimaryYear() %></primaryYear>
<primaryDob><%= customer.getPrimaryDob() %></primaryDob>
<primarySex><%= customer.getPrimarySex() %></primarySex>
<primaryPanNo><%= customer.getPrimaryPanNo() %></primaryPanNo>
<accountType><%= customer.getAccountType() %></accountType>
<cardType><%= customer.getCardType() %></cardType>
<primaryStreet1><%= customer.getPrimaryStreet1() %></primaryStreet1>
<primaryStreet2><%= customer.getPrimaryStreet2() %></primaryStreet2>
<primaryLandmark><%= customer.getPrimaryLandmark() %></primaryLandmark>
<primaryCity><%= customer.getPrimaryCity() %></primaryCity>
<primaryState><%= customer.getPrimaryState() %></primaryState>
<primaryCountry><%= customer.getPrimaryCountry() %></primaryCountry>
<primaryPinCode><%= customer.getPrimaryPinCode() %></primaryPinCode>
<primaryOffPhoneNo><%= customer.getPrimaryOffPhoneNo() %></primaryOffPhoneNo>
<primaryOffExtnNo><%= customer.getPrimaryOffExtnNo() %></primaryOffExtnNo>
<primaryResPhoneNo><%= customer.getPrimaryResPhoneNo() %></primaryResPhoneNo>
<primaryMobileNo><%= customer.getPrimaryMobileNo() %></primaryMobileNo>
<primaryEmailId><%= customer.getPrimaryEmailId() %></primaryEmailId>
<productInterest><%= customer.getProductInterest() %></productInterest>
<sourceReferral><%= customer.getSourceReferral() %></sourceReferral>
<channel><%= customer.getChannel() %></channel>
<accountNo><%= " " %></accountNo>
<documentsSubmitted><%= customer.getDocumentsSubmitted() %></documentsSubmitted>
<creditRating><%= 0.0 %></creditRating>
<eligibleCustomer><%= false %></eligibleCustomer>
<segment><%= " " %></segment>
<action><%= " " %></action>
<remarks><%= " " %></remarks>
<approverEmail><%= customer.getApproverEmail() %></approverEmail>
<bPELProviderUrl><%= customer.getBPELProviderUrl() %></bPELProviderUrl>
</customerObj>
</orabpel:part>
</orabpel:post>
</orabpel:deliveryService>
</orabpel:locator>
<b>We also tried this way...same result</b>
Properties jndi = new Properties();
jndi.put(Context.PROVIDER_URL,"ormi://localhost:23791/orabpel");
jndi.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
jndi.put(Context.SECURITY_PRINCIPAL, "admin");
jndi.put(Context.SECURITY_CREDENTIALS, "welcome");
jndi.put("dedicated.connection", "true");
String xml = "....";
NormalizedMessage input = new NormalizedMessage( );
input.addPart("payload", xml);
String conversationId = String.valueOf(System.currentTimeMillis());
input.setProperty(NormalizedMessage.TITLE, "Dynamic CustomerRegistration Invocation");
input.setProperty(NormalizedMessage.CONVERSATION_ID, conversationId);
input.setProperty(NormalizedMessage.CREATOR, "Oracle BPEL");
Locator locator = new Locator("default","bpel",jndi);
IDeliveryService deliveryService = (IDeliveryService)locator.lookupService(IDeliveryService.SERVICE_NAME);
deliveryService.post("ProductRegistration", "initiate", input );
<b>The entry in application.xml for the web application is as follows:</b><br/>
<web-module id="registration" path="../../home/applications/registration.war"/>
The entry in http-web-site.xml for the web application is as follows:<br/>
<web-app application="orabpel" name="registration" load-on-startup="true" root="/registration"/>
<web-app application="default" name="registration"      root="/registration"/>
I have tried to provide all possible relevant info, if you need more, do reply back to me.
Thanks in advance for helping us to resolve this issue.
|Soumen|

We have a business process, which when invoked from BPEL console works fine, however, when we invoke it from an web application of ours, it does gets initiated, but fails later.
We have Apache Axis deployed in the same OC4J server as the Oracle BPEL PM(10.1.2.0.2), which exposes few EJBs as SOAP Services.
The Business Process invokes couple of SOAP Services and then creates a Task and then waits for task completion and based on task action invokes two other SOAP services.
When we invoke it from the BPEL Console, everything works fine. It also works fine, if we invoke it first (after startup) from BPEL Console and then through our web application.
However, if we invoke it first through our web application, then it does initiates, but fails at the Task creation. If we try to hit the BPEL Console, we get this error
Oracle BPEL Process Manager Full Cycle
An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
Attachments:
Build Information:
Oracle BPEL Server version 10.1.2.0.2
Build: 2196
Build time: Tue Jan 10 12:31:53 UTC 2006
Build type: release
Source tag: BPEL_10.1.2.0.2_GENERIC_060110.1200
Exception Message:
[java.lang.Exception]
Failed to create "ejb/collaxa/system/ServerBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/ServerBean not found
     at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:164)
     at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:333)
     at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:120)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
<b>Nothing works after that, unless we re-start.</b>
Once we re-start, BPEL Console works fine.
Investigating the flow of the business process, we find the "initiateTask" of the workflow is fine, but it failed at "initiateTaskActionHandler" with the following error:
<remoteFault>
<part name="code" >
<code>WSDLReadingError</code>
</part>
<part name="summary" >
<summary>Failed to read wsdl. Failed to read wsdl at "http://Uranus:9700/orabpel/default/TaskActionHandler/TaskActionHandler?wsdl", because "WSDLException: faultCode=INVALID_WSDL: The document: http://Uranus:9700/orabpel/default/TaskActionHandler/TaskActionHandler?wsdl is not a wsdl file or does not have a root element of "definitions" in the "http://schemas.xmlsoap.org/wsdl/" namespace or the "http://www.w3.org/2004/08/wsdl" namespace.". Make sure wsdl is valid. You may need to start the OraBPEL server, or make sure the related bpel process is deployed correctly. </summary>
</part>
</remoteFault>
<b>Below is the code as to how we are invoking the Business Process...using orabpel taglibs...</b>
<orabpel:locator domainId="default" password="bpel" contextEnv="jndi">
<orabpel:deliveryService processId="ApprovalProcess">
<orabpel:post title="ApprovalProcess">
<orabpel:part name="payload">
<customerObj xmlns="http://xmlns.misys.com/ApprovalProcess/approval">
<applicationNo><%= customer.getApplicationNo() %></applicationNo>
<customerId><%= customer.getCustomerId() %></customerId>
<primaryFirstName><%= customer.getPrimaryFirstName() %></primaryFirstName>
<primaryLastName><%= customer.getPrimaryLastName() %></primaryLastName>
<primaryCardName><%= customer.getPrimaryCardName() %></primaryCardName>
<primaryDay><%= customer.getPrimaryDay() %></primaryDay>
<primaryMonth><%= customer.getPrimaryMonth() %></primaryMonth>
<primaryYear><%= customer.getPrimaryYear() %></primaryYear>
<primaryDob><%= customer.getPrimaryDob() %></primaryDob>
<primarySex><%= customer.getPrimarySex() %></primarySex>
<primaryPanNo><%= customer.getPrimaryPanNo() %></primaryPanNo>
<accountType><%= customer.getAccountType() %></accountType>
<cardType><%= customer.getCardType() %></cardType>
<primaryStreet1><%= customer.getPrimaryStreet1() %></primaryStreet1>
<primaryStreet2><%= customer.getPrimaryStreet2() %></primaryStreet2>
<primaryLandmark><%= customer.getPrimaryLandmark() %></primaryLandmark>
<primaryCity><%= customer.getPrimaryCity() %></primaryCity>
<primaryState><%= customer.getPrimaryState() %></primaryState>
<primaryCountry><%= customer.getPrimaryCountry() %></primaryCountry>
<primaryPinCode><%= customer.getPrimaryPinCode() %></primaryPinCode>
<primaryOffPhoneNo><%= customer.getPrimaryOffPhoneNo() %></primaryOffPhoneNo>
<primaryOffExtnNo><%= customer.getPrimaryOffExtnNo() %></primaryOffExtnNo>
<primaryResPhoneNo><%= customer.getPrimaryResPhoneNo() %></primaryResPhoneNo>
<primaryMobileNo><%= customer.getPrimaryMobileNo() %></primaryMobileNo>
<primaryEmailId><%= customer.getPrimaryEmailId() %></primaryEmailId>
<productInterest><%= customer.getProductInterest() %></productInterest>
<sourceReferral><%= customer.getSourceReferral() %></sourceReferral>
<channel><%= customer.getChannel() %></channel>
<accountNo><%= " " %></accountNo>
<documentsSubmitted><%= customer.getDocumentsSubmitted() %></documentsSubmitted>
<creditRating><%= 0.0 %></creditRating>
<eligibleCustomer><%= false %></eligibleCustomer>
<segment><%= " " %></segment>
<action><%= " " %></action>
<remarks><%= " " %></remarks>
<approverEmail><%= customer.getApproverEmail() %></approverEmail>
<bPELProviderUrl><%= customer.getBPELProviderUrl() %></bPELProviderUrl>
</customerObj>
</orabpel:part>
</orabpel:post>
</orabpel:deliveryService>
</orabpel:locator>
<b>We also tried this way...same result</b>
Properties jndi = new Properties();
jndi.put(Context.PROVIDER_URL,"ormi://localhost:23791/orabpel");
jndi.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
jndi.put(Context.SECURITY_PRINCIPAL, "admin");
jndi.put(Context.SECURITY_CREDENTIALS, "welcome");
jndi.put("dedicated.connection", "true");
String xml = "....";
NormalizedMessage input = new NormalizedMessage( );
input.addPart("payload", xml);
String conversationId = String.valueOf(System.currentTimeMillis());
input.setProperty(NormalizedMessage.TITLE, "Dynamic CustomerRegistration Invocation");
input.setProperty(NormalizedMessage.CONVERSATION_ID, conversationId);
input.setProperty(NormalizedMessage.CREATOR, "Oracle BPEL");
Locator locator = new Locator("default","bpel",jndi);
IDeliveryService deliveryService = (IDeliveryService)locator.lookupService(IDeliveryService.SERVICE_NAME);
deliveryService.post("ProductRegistration", "initiate", input );
<b>The entry in application.xml for the web application is as follows:</b><br/>
<web-module id="registration" path="../../home/applications/registration.war"/>
The entry in http-web-site.xml for the web application is as follows:<br/>
<web-app application="orabpel" name="registration" load-on-startup="true" root="/registration"/>
<web-app application="default" name="registration"      root="/registration"/>
I have tried to provide all possible relevant info, if you need more, do reply back to me.
Thanks in advance for helping us to resolve this issue.
|Soumen|

BPEL Process migration problems from 10.1.2. to 10.1.3(SOA)

Hi,
I am migrating the BPEL Project which was desinged for the BPEL(10.1.2) using BPEL Designer to SOA Suite using the JDeveloper 10.1.3.1 Developer Preview version.
The taken the project which is deploying&working perfectly in the BPEL Desg&serv (10.1.2).
But the same project is not compiling in the newer preview version.i got invalid xpath exception.
my xpath is like
bpws:getVariableData('inputVariable','payload','/client:commonProjectProcessRequest/client:input/ns1:listOfProducts')
if i change like this xpath, woking fine...
bpws:getVariableData('inputVariable','payload','/client:commonProjectProcessRequest/client:input')
The input element defined as string in wsdl.However am expecting in runtime process will recive an proper xml string as a value of input element so the xpath will work fine..
Is the any configuration property to turn of xpath validation & variable not initialized warning while compile and building bpel project in the jdevstudio10.1.3.1. preview as well as in SOASuite server.
I would be happy on any reply.
Thanks
bogi

Hi,
Bogiraja and me work on the same team... this is a follow up we noticed today. As part of the deployment descriptors of a BPEL, one can set the configuration property "xpathValidation" to False (it is by default True going by 10.1.2 documentation). The documentation says that this would make the compiler not to validate the xpath queries.
When we tried this in 10.1.3, it did not seem to make any difference and the compiler still did not allow a xpath query which contained a node name which was not defined in the WSDL (bpws:getVariableData('inputVariable','payload','/client:commonProjectProcessRequest/client:input/ns1:listOfProducts') in Bogiraja's mail above)
Basically, the problem is like this.
a. The WSDL for the BPEL process defines the input variable as a "string"
b. When this BPEL process is invoked, we read the content of this variable which is an XML and assign that to a variable of a defined type in the BPEL.
c. For this purpose, we used to use the syntax as mentioned by Bogiraja in 10.1.2 which does not seem to work on 10.1.3.
A further observation is that if we define a dummy variable of xsd:any and copy the content of the input into that variable and then apply a similar xpath ('/client:dummyXSDAnyVar/ns1:listOfProducts') on that resultant variable then it seems to work!!
Expected functionality? Anything we seem to be missing out here?
Would highly appreciate any responses.
Thanks in advance.

BPEL Process migration problem.from 10.1.2. to 10.1.3(SOA)

Hi,
I am migrating the BPEL Project which was desinged for the BPEL(10.1.2) to SOA Suite using the JDeveloper 10.1.3.1 Developer Preview version.
The taken the project which is buildin and deploying correctly in the BPEL Desg&ser (10.1.2).
But the same project is not compiling in the newer preview version.i got invalid xpath exception.
my xpath is like
bpws:getVariableData('inputVariable','payload','/client:commonProjectProcessRequest/client:input/ns1:listOfProducts')
if i change like this xpath, woking fine...
bpws:getVariableData('inputVariable','payload','/client:commonProjectProcessRequest/client:input')
the element defined as string in wsdl.however am expecting in runtime process will recive an proper xml string as a value of input element so the xpath will work fine..
is the any configuration property to turn of xpath validation & variable not initialized warning while compile and building bpel project in the jdev10.1.3.1. preview version.
could you please any one give me solution ?
Thanks
bogi

Hi,
Bogiraja and me work on the same team... this is a follow up we noticed today. As part of the deployment descriptors of a BPEL, one can set the configuration property "xpathValidation" to False (it is by default True going by 10.1.2 documentation). The documentation says that this would make the compiler not to validate the xpath queries.
When we tried this in 10.1.3, it did not seem to make any difference and the compiler still did not allow a xpath query which contained a node name which was not defined in the WSDL (bpws:getVariableData('inputVariable','payload','/client:commonProjectProcessRequest/client:input/ns1:listOfProducts') in Bogiraja's mail above)
Basically, the problem is like this.
a. The WSDL for the BPEL process defines the input variable as a "string"
b. When this BPEL process is invoked, we read the content of this variable which is an XML and assign that to a variable of a defined type in the BPEL.
c. For this purpose, we used to use the syntax as mentioned by Bogiraja in 10.1.2 which does not seem to work on 10.1.3.
A further observation is that if we define a dummy variable of xsd:any and copy the content of the input into that variable and then apply a similar xpath ('/client:dummyXSDAnyVar/ns1:listOfProducts') on that resultant variable then it seems to work!!
Expected functionality? Anything we seem to be missing out here?
Would highly appreciate any responses.
Thanks in advance.

BPEL Process transporting problem.from 10.1.2. to 10.1.3(SOA)

Hi,
When i move the project to new SOASuite designer, the transformation activity is showing as assign activity.. and its not moving the imported xsd folders from project root folder to the bpel folder.So while building, it's not able to find the xsd in the relative path what is there in the wsdl.
Thanks,
Bogi.

Hi,
Bogiraja and me work on the same team... this is a follow up we noticed today. As part of the deployment descriptors of a BPEL, one can set the configuration property "xpathValidation" to False (it is by default True going by 10.1.2 documentation). The documentation says that this would make the compiler not to validate the xpath queries.
When we tried this in 10.1.3, it did not seem to make any difference and the compiler still did not allow a xpath query which contained a node name which was not defined in the WSDL (bpws:getVariableData('inputVariable','payload','/client:commonProjectProcessRequest/client:input/ns1:listOfProducts') in Bogiraja's mail above)
Basically, the problem is like this.
a. The WSDL for the BPEL process defines the input variable as a "string"
b. When this BPEL process is invoked, we read the content of this variable which is an XML and assign that to a variable of a defined type in the BPEL.
c. For this purpose, we used to use the syntax as mentioned by Bogiraja in 10.1.2 which does not seem to work on 10.1.3.
A further observation is that if we define a dummy variable of xsd:any and copy the content of the input into that variable and then apply a similar xpath ('/client:dummyXSDAnyVar/ns1:listOfProducts') on that resultant variable then it seems to work!!
Expected functionality? Anything we seem to be missing out here?
Would highly appreciate any responses.
Thanks in advance.

Error while invoking the WSDL service of EBS from BPEL process

Hi Team,
when we are calling webservice client to call WSDL service which is published in Oracle EBS integrated SOA Gateway from BPEL process.
After invoking, we are getting the below error
<bpelFault><faultType>0</faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>FND_SOA_SERVICE_EXECUTION_ERR:oracle.apps.fnd.soa.util.SOAException: ServiceExecutionError: Error while executing the service Exception returned from JCA Service Runtime. Exception returned from JCA Service Runtime. null :Please see service monitor logs for full error trace</summary></part><part name="detail"><detail>oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : FND_SOA_SERVICE_EXECUTION_ERR:oracle.apps.fnd.soa.util.SOAException: ServiceExecutionError: Error while executing the service Exception returned from JCA Service Runtime. Exception returned from JCA Service Runtime. null :Please see service monitor logs for full error trace</detail></part><part name="code"><code>{http://schemas.xmlsoap.org/soap/envelope/}Server</code></part></remoteFault></bpelFault>
API Name : OE_ORDER_PUB.PROCESS_ORDER
could you please let me know the exact problem and provide the solution.
Thanks
Phani Ch.

Hi Phani,
Are you able to reproduce issue as below:
1. Login to Application as sysadmin.
2. Navigate to Intergrated SOA Gateway > Integration Repository.
3. Click on search on right hand side of the page.
4. In the Internal Name type "FND_USER_PKG" and click Go.
5. Click on the User link.
6. Under the "Web Service - SOA Provider", click in the "View WSDL". Copy the complete URL "http://test:8003/webservices/SOAProvider/plsql/fnd_user_pkg/?wsdl"
7. Open the soapUI.
8. Click File > new soapUI Project.
9. Test the web service.
If yes,
I think you might be need to execute a patch:
solution:
To implement the solution, please execute the following steps:
1. Download and review the readme and pre-requisites for iAS Patch 18855074.
Note: Above Merge Label Request (MLR) is build for EBS 12.1.3 having OC4J 10.1.3.5.
2. Enable the profile option "EBS Adapter for BPEL, Function Security Enabled".
a. Login as SYSADMIN user and Navigate to System >Profile and Search for "EBS Adapter for BPEL, Function Security Enabled" (Internal name :EBS_ADAPTER_FUNCTION_SEC_ENABLED)
b. Set the Value to 'Y' at SITE level . This means function security feature is enabled and all API calls for PL/SQL APIs, Oracle e-Commerce Gateway, and concurrent programs will be checked for user security before they are invoked.
3. Retest the issue by Generating and Deploying the required package.
4. Migrate the solution as appropriate to other environments.
Thanks
Ranjan

Authorization Error While Invoking BPEL Process Via RMI

Hi All,
I have been trying to invoke BPEL Process via RMI client.
I use the following piece of code for BPEL Process Invocation...
public class RMIClient {
public RMIClient() {
public static void main(String[] args){
Hashtable jndi = new Hashtable ();
jndi.put (Context.PROVIDER_URL, "opmn:ormi://host:6010:oc4j_soa/orabpel");
jndi.put (Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
jndi.put (Context.SECURITY_PRINCIPAL,"oc4jadmin"); // username of Bpel Manager
jndi.put (Context.SECURITY_CREDENTIALS,"welcome1"); //password of BPEL Manager
Locator locator=null;
try {
locator = new Locator("default",jndi);
} catch (ServerException e) {
e.printStackTrace();
IDeliveryService deliveryService =
(IDeliveryService)locator.lookupService
(IDeliveryService.SERVICE_NAME );
// construct the normalized message and send to oracle bpel process
NormalizedMessage nm = new NormalizedMessage( );
String xml = "<ns1:MyFirstBPELProjectProcessRequest xmlns:ns1=\"http://xmlns.oracle.com/MyFirstBPELProject\">\n" +
" <ns1:input></ns1:input>\n" +
" </ns1:MyFirstBPELProjectProcessRequest>";
nm.addPart("payload", xml );
NormalizedMessage res=null;
try {
res = deliveryService.request("MyFirstBPELProject", "process", nm);
} catch (ServerException e) {
e.printStackTrace();
} catch (RemoteException e) {
e.printStackTrace();
Map payload = res.getPayload();
When I try to connect to my locally deployed BPEL process Manager and Invoke the same process (MyFirstBPELProjectProcess ) it works fine and creates an Instance on BPEL Process Manager Console.
When I tried Invoking the same BPEL process (MyFirstBPELProjectProcess ) deployed on a Remote machine ,it doesnt create an Instance.
I believe my connections settings are all correct ,since it doesnt give me an connection issue on my standalone client.
I tried looking at the following file default_group~oc4j_soa~default_group~1.log available opmn folder under SOA Suite OAS and there
are no errors.
Could some body point the log files that I need to look at.
I am sort of clueless...
Regards
Harish

CAn you post the error. HAve you made sure that the remote machine has connection on the port 6010. You can test this with the folloing command from the remote machine
telnet host 6010
obviously replace host with the fully qualified host name of the SOA machine.
cheers
James

Creating simple Business Rules in BPEL process

Hi,
I have an environment consisting of SOA Suite 11g running on Weblogic Server. I'm using JDeveloper 11g for development.
Scenario
I have a BPEL process which starts off by polling a DB table and I then assign the input to a Recieve activity's InputVariable. I have a 'Number' column which will contain a number between 1 and 3. I then require Business Rules (BR) to be set up which read this value, and based on the number, assign a 'Name' string (which is to be the output variable from the business rules) to be used later on in BPEL process.
Problem - I have followed the basic tutorials available in order to set up the business rules, but am getting numerous errors. Firstly, I sometimes find that my input/output variables created during setup of BR component and the XSD based on this, does not have XML Faces automatically created for it (therefore have to create it myself by clicking on the + button and doing this for each element of XSD). When I do get this working, I then double-click on my Business Rules activity in my BPEL process, only to find that the input/output variables here no longer are assignable to my BR input/output variables as I get the following error "Exception: Problem Building Schema!".
I am not sure why this is, but suspect that my XSD (which is very simple anyway) or the setup steps I follow to define the link to my XSD, are wrong.
I have taken the following steps so far:
1. Create empty BPEL process
2. Set up polling adapter to poll DB table
3. Create Receive activity and assigned polled input to created variable
4. Add Business Rules component to composite and set up and create dictionary here. Also set up inputs/outputs to be in form of my XSD elements.
5. Add Business Rules component to my BPEL process and configure this to include input/output variables (*This is where error occurs*)
6. Go back to .rules component in composite to define rule and define rule
Upon deployment, I get many errors most of which pertain to "Unresolved XML element... make sure XML element +xxxxx+ is defined in one of WSDL's that are referenced by the deployment descriptor."
I have only imported a simple XSD containing two elements to this project. The other XSD is the one of my polling adapter. I've not created any input/output variables for the overall BPEL process as didn't think I was required to.
Can you please help in getting this process doing the simple activities described at the top.
I appreciate your help.
Edited by: user10248308 on 10-Mar-2010 11:49

Hi,
Create a project with BPEL composite
Now drag a business rule
Now create input variable of type ur requestelement
and output variable of type response element
Now in rules designer page take decision table
and then craete a condition (inputelement.input > 1000) and in the rule select true
now create another rule select false
Npw create an action with assertion and select the parameterized box there
now in designer page for first rule assign some value (say 500) and for second rule some value(100)
Now in bpel u have to assign a value to input var of BR
Deploy the process
If u supply 10000 u will get 500
if u supply 100 u will get 100
In the same way u can do by using If-Then
You can use facts and bucketsets according to ur requirement
Regards
PavanKumar.M
PavanKumar.M

E-mail invoking BPEL process

Hello guys,
Can I invoke a BPEL process throught a E-mail or a JMS message?
Thank for answer

I solved it very siply:
I prepared a simple Java adapter for RMI BPEL process invocation and for work with TaskManager. As I said the adapter is based on RMI as described in tutorial:
samples\tutorials\102.InvokingProcesses\rmi\
this adapter i used in my application.
Or you can call process as WebService - for example in WebLogic Workshop is very simple to prepare JCX and proxy object based on process WSDL.
JM

OWSM problems while associating clientAgent with BPEL process

Hi All,
Refering to the PDF *"Securing Oracle SOA Applications by Using Oracle Web Services Manager (Oracle WSM) Agents.pdf"* we made an clientAgent and associated that with a simple BPEL process. After that we did the following:
1) Change the Configuration Directory (with the component id of the clientAgent)
2) Enable Web Services Agent (which was not mentioned in the pdf).
3) Restart the SOA server.
At the time of executing the BPEL process it is giving an error like "internal server error". Log is not being generated for clientAgent. At BPEL domaim log it is giving the following error:
ORABPEL-02152
Instance not found in datasource.
The process domain was unable to fetch the instance with key "0ec681d22ef098ba:-529c35a1:1220cecf7e4:-7fcf" from the datasource.
Please check that the instance key "0ec681d22ef098ba:-529c35a1:1220cecf7e4:-7fcf" refers to a valid instance that has been started and not removed from the process domain.
Please reslove as early as possible.
Thanks in Advance.
Chandra.

There are a few things you can do when trying to troubleshoot this kind of problem:
1) tunnel the interaction between the BPEL server and the web service to see what SOAP messages are exchanged.
2) try to turn debugging of the ws layer on: BPEL Console>Manage Domain>Logging
2) email us your project, including the WSDL of your service so that we can take a look at it.
Finally, one best practice is to never think in terms of Java object. Instead always start by designing your WSDLs and XSDs thinking of ports and XML documents and then generate the stubs. This will guaranty that your service is interoperable.
Edwin

OWSM GATEWAY PROBLEM .xsd error

Hi,
I am working on OWSM gateways.I deployed a mail web service and tried to virtualise it using OWSM gateways. I have registered the service . When i use the link for service wsdl generated by OWSM in internet explorer i can see the wsdl file but when do the same using test page in OWSM i get the following error.
java.io.IOException: The document 'http://localhost:8888/gateway/services/alshirawiMail.xsd' contains HTML tags.
Also i have only tried with web services but when i try to virtualise THE WHOLE BPEL PROCESS i get error like
java.io.IOException: The document 'http://localhost:8888/gateway/services/rule_doesnot_work.xsd' contains HTML tags.
Please reply.
Thanks and regards.
Vishnu
Message was edited by:
user607746

Hi
The problem with xsd resolved but now when i invoke the service from test page i am getting this error.
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">null
<env:Body>
<env:Fault
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>env:Server</faultcode>
<faultstring>ORABPEL-08021 Cannot find partner wsdl. parnterLink "OWSM_SYNC_BPEL_PROCESS" is not found in process "OWSM_SYNC_BPEL_PROCESS" (revision "1.0") Please check the deployment descriptor of the process to find the correct partnerLink name. </faultstring>
null</env:Fault>
</env:Body>
</env:Envelope>

OWSM: Gateway is not ready to process requests

OWSM: Gateway is not ready to process requests
After I registered a service in a gateway with OWSM and when I intialize a client call using gateway virtualized URL fro BPEL, the first time call I always get the following fault. It is like a "wake-up" call. I had to initialize second call imediately following the first call get through gateway.
Can anyone help me to figure out how to keep the OWSM Gateway "awake" all the time and avoid first call gateway failure?
Thanks
<fault>
-<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="code">
<code>Client.GenericFault
</code>
</part>
-<part name="summary">
<summary>Gateway is not ready to process requests
</summary>
</part>
-<part name="detail">
<detail>
<detail/>
</detail>
</part>
</remoteFault>
</fault>

Can anyone post any help from Oracle?

Unable to acess BPEL WSDL from OWSM Gateway

Hello all,
I'm trying to register a BPEL Process as a service on a OWSM gateway.
The BPEL WSLD is as follows:
<definitions name="WR01" targetNamespace="http://xmlns.oracle.com/WR01">
−
     <types>
−
     <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/WR01">
−
     <element name="WR01ProcessRequest">
−
     <complexType>
−
     <sequence>
<element name="input" type="string"/>
</sequence>
</complexType>
</element>
−
     <element name="WR01ProcessResponse">
−
     <complexType>
−
     <sequence>
<element name="result" type="string"/>
</sequence>
</complexType>
</element>
</schema>
−
     <xsd:schema>
<xsd:import namespace="http://xmlns.oracle.com/pcbpel/adapter/db/top/WR01" schemaLocation="WR01.xsd"/>
</xsd:schema>
</types>
−
     <message name="WR01RequestMessage">
<part name="payload" element="ns1:Input"/>
</message>
−
     <message name="WR01ResponseMessage">
<part name="payload" element="ns1:Input"/>
</message>
−
     <portType name="WR01">
−
     <operation name="process">
<input message="tns:WR01RequestMessage"/>
<output message="tns:WR01ResponseMessage"/>
</operation>
</portType>
−
     <binding name="WR01Binding" type="tns:WR01">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
−
     <operation name="process">
<soap:operation style="document" soapAction="process"/>
−
     <input>
<soap:body use="literal"/>
</input>
−
     <output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
−
     <service name="WR01">
−
     <port name="WR01Port" binding="tns:WR01Binding">
<soap:address location="http://dcmsinusapp02.dc.local:7780/orabpel/default/WR01/1.0"/>
</port>
</service>
−
     <plnk:partnerLinkType name="WR01">
−
     <plnk:role name="WR01Provider">
<plnk:portType name="tns:WR01"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
The WSDL generated from the service registation on the gateway is as follows:
<definitions name="WR01" targetNamespace="http://xmlns.oracle.com/WR01">
−
     <types>
−
     <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/WR01">
−
     <element name="WR01ProcessRequest">
−
     <complexType>
−
     <sequence>
<element name="input" type="string"/>
</sequence>
</complexType>
</element>
−
     <element name="WR01ProcessResponse">
−
     <complexType>
−
     <sequence>
<element name="result" type="string"/>
</sequence>
</complexType>
</element>
</schema>
−
     <xsd:schema>
<xsd:import namespace="http://xmlns.oracle.com/pcbpel/adapter/db/top/WR01" schemaLocation="WR01.xsd"/>
</xsd:schema>
</types>
−
     <message name="WR01RequestMessage">
<part name="payload" element="ns1:Input"/>
</message>
−
     <message name="WR01ResponseMessage">
<part name="payload" element="ns1:Input"/>
</message>
−
     <portType name="WR01">
−
     <operation name="process">
<input message="tns:WR01RequestMessage"/>
<output message="tns:WR01ResponseMessage"/>
</operation>
</portType>
−
     <binding name="WR01Binding" type="tns:WR01">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
−
     <operation name="process">
<soap:operation style="document" soapAction="process"/>
−
     <input>
<soap:body use="literal"/>
</input>
−
     <output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
−
     <service name="WR01">
−
     <port name="WR01Port" binding="tns:WR01Binding">
<soap:address location="http://dcmsinusapp02.dc.local:7780/gateway/services/SID0003002"/>
</port>
</service>
−
     <plnk:partnerLinkType name="WR01">
−
     <plnk:role name="WR01Provider">
<plnk:portType name="tns:WR01"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
When i test the acess using OWSM console or try and consume it on JDeveloper I get the following error:
java.io.IOException: The document 'http://dcmsinusapp02.dc.local:7780/gateway/services/WR01.xsd' contains HTML tags.
Reason is:
404 Not Found
OracleJSP: java.io.FileNotFoundException:
Set the init-param debug_mode to "true" to see the complete exception message
This file not found exception is related to /gateway/services/WR01.xsd of course.
I've mostly followed the OWSM documentation in order to register the service.
Am I doing anything wrong referencing xsd's or something similar?
Thanks in advance

Answer to my own question:
BPEL processes exposed via OWSM can't be used from JDEV ws proxy generator
But the real question is: how do I prevent relative paths to xsd's on bpel wsdl?
Any pointers?
Thanks

Problem starting BPEL Process Manager

When starting the BPEL Process Manager, the second window that is spawned to run the start_olite.bat throws a hotspot error as shown below. This happens each time and causes the PM not to start. Anyone had this problem ?.
Thanks
Andrew
C:\OraBPELPM\bin>call C:\OraBPELPM\bin\olsv2040.exe /debug
Debugging Oracle Lite Multiuser Service.
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7c92ae22, pid=3268, tid=1948
# Java VM: Java HotSpot(TM) Client VM (1.4.2_12-b03 mixed mode)
# Problematic frame:
# C [ntdll.dll+0x2ae22]
# An error report file with more information is saved as hs_err_pid3268.log
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#

It couldn't be such difficult.
I have the jar's, the drivers in, the jdbc url connection as
url="jdbc:oracle:thin:[USERNAME/PASSWORD]@IP:PORT:SID"/>
Also I can connect via sqlplus with this string conn.
The main error I get is
"Cannot lookup jdbc datasource.
The process domain was unable to lookup the TX datasource "jdbc/BPELServerDataSource"."

OWSM GATEWAY VIRTUALIZED BPEL PROCESS INVOCATION PROBLEM

Similar Messages

Maybe you are looking for