Fault error framework for synchronous Bpel process

Hi all,
Do fault policies work for synchronous Bpel processes? I am using a synchronous bpel process which invokes JMS service. I have used fault policies and bindings for this , when the instance fails due to binding fault the instance gets timed out and it neither goes to catch block nor fault policies.Is it normal behaviour or am i doing wrong anywhere. please help
Regards
Raju.

Hello Raju,
yes fault policies absolutely work for sync Bpel processes, please check if you have defined the Binding fault in your fault policy and also in your bindings.
if you have defined them in your policies then the control will jump to the policies first do the respective action defined.
so do check again...
Good luck..
vny.

Similar Messages

Fault framework for synchronous Bpel process

Hi all,
Do fault policies work for Synchronous Bpel process? I have created a Synchronous Bpel process which invokes a JMS service. In this case if the process errors out due to binding fault, my instance is getting timed out and it's neither going to fault policies nor CatchAll block. Is it normal behaviour oris it happening only in this case? please help.
Regards
Raju

Hello Raju,
yes fault policies absolutely work for sync Bpel processes, please check if you have defined the Binding fault in your fault policy and also in your bindings.
if you have defined them in your policies then the control will jump to the policies first do the respective action defined.
so do check again...
Good luck..
vny.

Unable to get Fault in reply from Synchronous BPEL Process

Hi All,
I am using a synchronous BPEL process which always throws a fault. The structure of this fault message is added to <bpel_process_name>.xsd.
For WSDL faults I have added the following in .wsdl file:
</wsdl:message>
<wsdl:message name="BusinessFault">
<wsdl:part name="payload" element="client:faultarea"/>
</wsdl:message>
<wsdl:portType name="FaultBPELProcess">
<wsdl:operation name="process">
<wsdl:input message="client:FaultBPELProcessRequestMessage"/>
<wsdl:output message="client:FaultBPELProcessResponseMessage"/>
<wsdl:fault message="client:BusinessFault" name="BusinessFault" />
</wsdl:operation>
</wsdl:portType>
Now when I invoke this BPEL process, the fault is thrown and caught by the catch block at main scope. this catch assigns some values to the fault message and returns it back to the calling party.
Fault QName is defined in the reply activity of catch block.
On testing it, the reply never comes back and I can see the following error message in the logs:
[2011-08-09T09:47:01.001+05:30] [soa_server1] [NOTIFICATION] [] [oracle.wsm.agent.WSMAgent] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 11d1def534ea1be0:53ccedc:131a8598fc1:-8000-0000000000000ed1,0:3] [WEBSERVICE_PORT.name: FaultBPELProcess_pt] [APP: soa-infra] [J2EE_MODULE.name: fabric] [WEBSERVICE.name: faultbpelprocess_client_ep] [J2EE_APP.name: soa-infra] Message Type is normalized, exiting agent.processFault()
[2011-08-09T09:47:01.001+05:30] [soa_server1] [NOTIFICATION] [] [oracle.wsm.agent.WSMAgent] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 11d1def534ea1be0:53ccedc:131a8598fc1:-8000-0000000000000ed1,0:3] [WEBSERVICE_PORT.name: FaultBPELProcess_pt] [APP: soa-infra] [J2EE_MODULE.name: fabric] [WEBSERVICE.name: faultbpelprocess_client_ep] [J2EE_APP.name: soa-infra] Message Type is normalized, exiting agent.processFault()
[2011-08-09T09:47:01.060+05:30] [soa_server1] [ERROR] [OWS-04086] [oracle.webservices.service] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 11d1def534ea1be0:53ccedc:131a8598fc1:-8000-0000000000000ed1,0:3] [APP: soa-infra] javax.xml.rpc.soap.SOAPFaultException[[
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.generateSoapFaultException(WebServiceEntryBindingComponent.java:1094)
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.processIncomingMessage(WebServiceEntryBindingComponent.java:887)
at oracle.integration.platform.blocks.soap.FabricProvider.processMessage(FabricProvider.java:113)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1187)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1081)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:581)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:232)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:192)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:459)
at oracle.integration.platform.blocks.soap.FabricProviderServlet.doPost(FabricProviderServlet.java:507)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
[2011-08-09T09:47:01.061+05:30] [soa_server1] [ERROR] [OWS-04115] [oracle.webservices.service] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 11d1def534ea1be0:53ccedc:131a8598fc1:-8000-0000000000000ed1,0:3] [APP: soa-infra] An error occurred for port: FabricProvider: javax.xml.rpc.soap.SOAPFaultException.
If I try to invoke the endpoint uri, it gets invoked and returns the response.
Any pointers will be appreciated!!

I tried the same scenario which you told and it's working for me...I'll paste the contents for your reference...
BPELProcess.bpel
<?xml version = "1.0" encoding = "UTF-8" ?>

<process name="BPELProcess1"
targetNamespace="http://xmlns.oracle.com/Test_jws/TestSync/BPELProcess1"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:client="http://xmlns.oracle.com/Test_jws/TestSync/BPELProcess1"
xmlns:ora="http://schemas.oracle.com/xpath/extension"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/">

<partnerLinks>

<partnerLink name="bpelprocess1_client" partnerLinkType="client:BPELProcess1" myRole="BPELProcess1Provider"/>
</partnerLinks>

<variables>

<variable name="inputVariable" messageType="client:BPELProcess1RequestMessage"/>

<variable name="outputVariable" messageType="client:BPELProcess1ResponseMessage"/>
<variable name="FaultVar_2" messageType="client:BusinessFault"/>
<variable name="FaultVar" messageType="client:BusinessFault"/>
</variables>
<faultHandlers>
<catch faultName="client:BusinessFault" faultVariable="FaultVar">
<reply name="Reply_1" variable="FaultVar"
partnerLink="bpelprocess1_client" portType="client:BPELProcess1"
operation="process" faultName="client:BusinessFault"/>
</catch>
</faultHandlers>

<sequence name="main">

<receive name="receiveInput" partnerLink="bpelprocess1_client" portType="client:BPELProcess1" operation="process" variable="inputVariable" createInstance="yes"/>

<assign name="Assign_1">
<copy>
<from expression="'A business fault occured'"/>
<to variable="FaultVar_2" part="payload"
query="/client:processResponse/client:result"/>
</copy>
</assign>
<throw name="Throw_1" faultName="client:BusinessFault"
faultVariable="FaultVar_2"/>
<reply name="replyOutput" partnerLink="bpelprocess1_client" portType="client:BPELProcess1" operation="process" variable="outputVariable"/>
</sequence>
</process>
BPELProcess1.wsdl
<?xml version= '1.0' encoding= 'UTF-8' ?>
<wsdl:definitions
name="BPELProcess1"
targetNamespace="http://xmlns.oracle.com/Test_jws/TestSync/BPELProcess1"
xmlns:ns1="http://schemas.oracle.com/bpel/extension"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:client="http://xmlns.oracle.com/Test_jws/TestSync/BPELProcess1"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>
<plnk:partnerLinkType name="BPELProcess1">
<plnk:role name="BPELProcess1Provider">
<plnk:portType name="client:BPELProcess1"/>
</plnk:role>
</plnk:partnerLinkType>
<wsdl:import namespace="http://schemas.oracle.com/bpel/extension" location="RuntimeFault.wsdl"/>
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/Test_jws/TestSync/BPELProcess1" schemaLocation="xsd/BPELProcess1.xsd"/>
</schema>
</wsdl:types>
<wsdl:message name="BPELProcess1RequestMessage">
<wsdl:part name="payload" element="client:process"/>
</wsdl:message>
<wsdl:message name="BPELProcess1ResponseMessage">
<wsdl:part name="payload" element="client:processResponse"/>
</wsdl:message>
<wsdl:message name="BusinessFault">
<wsdl:part name="payload" element="client:processResponse"/>
</wsdl:message>
<wsdl:portType name="BPELProcess1">
<wsdl:operation name="process">
<wsdl:input message="client:BPELProcess1RequestMessage"/>
<wsdl:output message="client:BPELProcess1ResponseMessage"/>
<wsdl:fault message="client:BusinessFault" name="BusinessFault" />
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
Hope that helps you...
Thanks,
N

Transaction Error In Synchronous BPEL Process

Hi All,
The Bpel Component makes a synchronous call to webservice , at few occurences response from
webservice delays to 50 secs .
The default time out of Synchronous Bpel Process is 45 secs, so when response from webservice takes more than 45 secs, the expected behaviour of BPEL
component should get faulted and control should go to catch all block
Issue
But instead, the Invoke activity in BPEL component gets rolled back, and control did not go to catch all block and complete instance goes into running state.
And after 50 secs, once webservice response back , a new instances gets automitically created .
Can anyone, Please help me to resolve the issue, i do not want the instances to go into running state .

What I would do is, have the timeout settings as follows.
syncMaxWaitTime < EJB Timeout < JTA timeout
Then, as Vijay pointed in "http://technology.amis.nl/2011/11/18/timeouts-in-oracle-soa-suite-11g/" link, you should add the httpConnTimeout property and httpReadTimeout property to be set less than syncMaxWaitTimeout, so that those timeout will kick in before the syncMaxWaitTime and throw the exception and you can catch it in the catchall block.
HTH.
Hruthayah

Sequential Instantiation of BPEL instances for a BPEL process

Hi,
We are using Oracle SOA 10.1.3.4 & AIA2.5. We have a situation where the instances of a particular bpel process have to be executed in sequence. Also, the new instance should NOT be instantiated unless the previous instance is completed.
For example.. Lets say a SyncBPELReqABCS is invoking SyncBPELProvABCS via ESB. SyncBPELReqABCS is looping and spawning multiple instances of SyncBPELProvABCS in a certain sequential order in Asynchronous Fire-and-Forget model. Lets say bpel-instance#1, bpel-instance#2 and bpel-instance#3 are instances of SyncBPELProvABCS process. Even though SyncBPELReqABCS invokes (spawns) SyncBPELProvABCS in a fire and forget model, the bpel-instance#2 should not begin unless bpel-instance#1 is completed and bpel-instance#3 shuld not begin unless bpel-instance#2 is completed. This is because there is a dependancy between instacnes of SyncBPELProvABCS process.
Can this be achieved in Oracle SOA?? Can we restrict the instacnes of SyncBPELProvABCS to be created in this manner?
This is similar to "incompatability" of concurrent programs in ORACLE EBusiness Suite where one concurrent program waits till another concurrent program completes.
Please let me know if I am not clear. Appreciate an immediate help!
Thanks,

Hello,
Now that I look back at this tread, I can see that the questions I was asking and those of the original poster were somewhat different.
But they both fall under the heading of "Sequential Instantiation of BPEL instances for a BPEL process", and so I thought I would post some findings we've come across regarding that topic here.
There were a couple steps that helped us achieve the behavior we were looking for, and the were...
1) Change the BPEL oneWayDeliveryPolicy from "async.persist" to "sync"
This can be done in a couple locations. The first is within the EM application that comes bundled with SOA 11g, and the place to go is:EM > [farm name] > SOA > soa-infra (right click) > SOA Administration > BPEL Properties > More BPEL Configuration Properties > OneWayDeliveryPolicyOnce that value has been changed to "sync" (without the quotes), you'll need to stop and start the managed servers that run your SOA instance(s).
As you might expect, making a change at the "server level" like this impacts the default behavior of all composites deployed within your SOA instance. The second place to make this change - within the deployment descriptors for your BPEL process - impacts only the BPEL process that is being modified. To make the change at this level, you would edit your project's composite.xml file and, for each BPEL component, specify: <component name="BPELProcess1" version="2.0">
    <implementation.bpel src="BPELProcess1.bpel"/>
    <property name="bpel.config.oneWayDeliveryPolicy">sync</property>
    <property name="bpel.config.transaction">required</property>
</component>What does this change do? Well, I don't claim to have a complete understanding, but in theory it prevents a thread handoff from taking place between the service that is initiates your BPEL process (like a receive) and the actual BPEL engine thread that processes the request.
In our case, where calls between (and within) composites were all of the synchronous "fire and forget" variety, this change also caused the entire processing of a message (across three different composites) to happen in a single thread (each message handoff was one-way, and with the oneWayDeliveryPolicy set to "sync", each was handled in a synchronous manner).
This also seemed to have the effect of serializing our message processing. For example, in a test case where a BPEL process reads from a JMS queue and 250 messages are enqueued, with the oneWayDeliveryPolicy set to "async.persist", I'd typically go in to EM and, on each refresh, find 5-8 instances of the composite that processes those messages to be in a "Running" state. Once the change to "sync" was made, I'd only see at most only 2 (where one had actually already finished; the audit system just hadn't yet caught up to that fact yet).
This also means that, with a "sync" delivery policy, messages (at least in our environment) are processed more slowly, but that was ok with us as we were more concerned with the behavior than the speed.
For details on this and other BPEL deployment descriptor properties, see:
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10224/bp_app_deploydesc.htm
Also, it's important to note that making the above change will alter the boundaries of your transactions as well as how faults are propagated. For more details, see:
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10224/soa_transactions.htm
2) Front BPEL process with a Mediator object and enable message resequencing
While we're using the above change as a standard practice in our environment, this second change has only been nominally tested - but it could be of interest and so I'll mention it here.
Once you've updated your composite to include a mediator object in front of your BPEL process (if there isn't one there already), edit the .mplan for your mediator and change the "Resequence Level" from the default value of "operations" to "component". Then change the "Resequence Mode" from "off" to "FIFO" and specify an X-Path expression by which the mediator will be able to group your messages. This will help ensure that the messages are being processed in the order you expect.
More information about resequencing within the mediator component can be found:
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/med_resequencer.htm
Hopefully the above information is useful - if not for the original poster, then for someone who comes along later with similar questions.
- Nathan

Reply component on synchronous BPEL process in Oracle SOA

if there any possibility for returning the result to the client in the middle of a synchronous BPEL process?
I put the reply component in the middle of BPEL process, but the client still will wait for the whole process completed. I am wondering how the reply mechanism works in BPEL for synchronous.

Hi,
You should build your process in a way that the reply activity should be in the end.
Meaning, add the relevant activities - scopes, catch (fault handling - system & business), switch etc...
If, from some reason, you don't want to continue with the process,at any stage then go to the end.
Arik

BUSINESS RULES WITH SYNCHRONOUS BPEL PROCESS

Hi
I want to know whether i can use Business Rules with Synchronous BPEL process. Actually i developed an example synchronous BPEL process but while invoking decision service it generated an error stating RECEIVE TIMEOUT fault. But when i created identical process in ASYNCHRONOUS mode it went through without any error.
Thanks and Regards
Vishnu

Just in case, here is some documentation about changing the syncMaxWaitTime
http://download-east.oracle.com/docs/cd/B31017_01/integrate.1013/b28980/bpel_install.htm
Jan Kettenis

Repeat executed of synchronous bpel process

Repeat call in synchronous bpel process
The BPEL PM Server Version is as follows:
Oracle BPEL Server 版本 10.1.3.1.0
构建: 0
构建时间: Mon Oct 09 08:44:49 PDT 2006
构建类型: release
源标记: PCBPEL_10.1.3.1.0_GENERIC_061009.0802
When I run a synchronous bpel process which may run about 4 hours,the process was executed twice .
But when I design this process using asynchronous method, it does not happen.
Does anyone encounter this case and how it was resolved?
Or this is a bug of Oracle BPEL Server ?
Thanks for your answer.
Jiucai.
null

HI
Please describe your issue clearly and also the opmn log error trace here !

RequestTimeoutException error while invoking a BPEL process using RMI

Hi,
I am getting RequestTimeoutException error while invoking a BPEL process using this code:
Locator locator = LocatorFactory.createLocator(jndiProps);
String compositeDN = "default/"+processName+"!1.0";
Composite composite = locator.lookupComposite(compositeDN);
String serviceName = "client";
Service deliveryService = composite.getService(serviceName);
NormalizedMessage nm = new NormalizedMessageImpl();
nm.getPayload().put("payload", requestXml);
NormalizedMessage res = deliveryService.request("process", nm);
responseMap = res.getPayload();
The error stack trace is
weblogic.rmi.extensions.RequestTimeoutException: RJVM response from 'weblogic.rjvm.RJVMImpl@604f2d14 - id: '-361032376059206
2776S:10.67.232.164:[8001,-1,-1,-1,-1,-1,-1]:emaar_domain:soa_server1' connect time: 'Mon Jan 18 11:34:41 GST 2010'' for 'executeServiceMethod
(Loracle.soa.management.CompositeDN;Ljava.lang.String;Ljava.lang.String;[Ljava.lang.Object;) 'timed out after: 60000ms.
oracle.fabric.common.FabricInvocationException: weblogic.rmi.extensions.RequestTimeoutException: RJVM response from 'weblogic.rjvm.RJVMImpl@60
4f2d14 - id: '-3610323760592062776S:10.67.232.164:[8001,-1,-1,-1,-1,-1,-1]:emaar_domain:soa_server1' connect time: 'Mon Jan 18 11:34:41 GST 20
10'' for 'executeServiceMethod(Loracle.soa.management.CompositeDN;Ljava.lang.String;Ljava.lang.String;[Ljava.lang.Object;) 'timed out after: 6
0000ms.
        at oracle.soa.management.internal.facade.ServiceImpl.request(ServiceImpl.java:135)
        at com.gss.common.bo.BpelUtil.invokeBPELProcess(BpelUtil.java:81)
To add to it the BPEL process is executing successfuly and RMI call timeout is happening.
Can I know how to increase the related timeout value?

Have got the same problem. Scenario at my end is little different though.
I am trying to invoke a BPEL process from an ESB Service.
I am trying to look into it..
However, would be grateful, if someone can give some insight into this since many are running into this issue without being able to fix.
Ashish.

Error While Deploying the BPEL Process using obant script

Hi All,
I am getting the following error while deploying the BPEL Process using obant script. we are using the BPEL Version 10.1.2.0.2.Any information in this regard will be really helpful.
Buildfile: build.xml
main:
[bpelc] file:/home5102/dibyap/saravana/Test/CreditRatingService.wsdl
[bpelc] validating "/home5102/dibyap/saravana/Test/CreditRatingService.bpel" ...
BUILD FAILED
/home5102/dibyap/saravana/Test/build.xml:15: ORABPEL-01002
Domain directory not found.
The process cannot be deployed to domain "default" because the domain directory "/opt02/app/ESIT/oracle/esit10gR2iAS/BPEL10gR2/iAS/integration/orabpel/domains/default/deploy" cannot be found or cannot b
e written to.
Please check your -deploy option value; "default" must refer to a domain that has been installed locally on your machine.
Total time: 23 seconds
dibyap@ios5102_ESIBT:/home5102/dibyap/saravana/Test>
Thanks,
Saravana

In 10.1.2.0.2 you need to create your own build.xml
I have found an example, it may be of some help. This does call a property file
cheers
James
<?xml version="1.0" ?>

<project name="ASB_EFT" default="main" basedir=".">

<property name="deploy" value="default" />

<property name="rev" value="1.0" />


<property file="ebusd.properties"/>
<property name="env" value="${env.name}"/>
<property name="current.project.name" value="${project.name}"/>
<property name="target.project.name" value="${project.name}_${env}"/>
<property name="deployment.profile" value ="${env}.properties"/>
<property name="source.development.directory" location="${basedir}"/>
<property name="target.env.directory" location="${basedir}/deploy/${project.name}_${env}"/>
<property file="${deployment.profile}"/>
<property name="build.fileencoding" value="UTF-8"/>

<target name="print.env" description="Display environment settings">
<echo message="Base Directory: ${basedir}"/>
<echo message="Deployment Profile: ${deployment.profile}"/>
<echo message="target.env.directory: ${target.env.directory}"/>
<echo message="Deploy to Domain: ${deployToDomain}"/>
<echo/>
<echo message="os.name: ${os.name}"/>
<echo message="os.version: ${os.version}"/>
<echo message="os.arch: ${os.arch}"/>
<echo/>
<echo message="java.home: ${java.home}"/>
<echo message="java.vm.name: ${java.vm.name}"/>
<echo message="java.vm.vendor: ${java.vm.vendor}"/>
<echo message="java.vm.version: ${java.vm.version}"/>
<echo message="java.class.path: ${java.class.path}"/>
<echo/>
<echo message="env: ${env}"/>
<echo message="current.project.name: ${current.project.name}"/>
<echo message="target.project.name: ${target.project.name}"/>
<echo message="server.name: ${server.name}"/>
</target>

<target name="create.environment">
<copy todir="${target.env.directory}">
<fileset dir="${basedir}"/>
<filterset begintoken="@" endtoken="@">
<filtersfile file="${deployment.profile}"/>
</filterset>
</copy>
<move file="${target.env.directory}/${current.project.name}.jpr" tofile="${target.env.directory}/${target.project.name}.jpr"/>
</target>
<target name="main">

<bpelc input="${basedir}/bpel.xml" rev="${rev}" deploy="${deploy}" />
</target>
</project>
here is a property file
project.name=ASB_EFT
env.name=ebusd
deployToDomain=default
server.name=[server]
server.port=7788
ebusd\:7788=http://[server]:7788/
IntegrationMailAccount=OracleBPELTest
IntegrationMailAddress=[email]
IntegrationMailPassword=[password]
archivedir=[directory]
inbounddir=/[directory]
errordir=[directory]
outbounddir=[directory]
bpelpw=bpel
dbhost1=[dbserver]
dbhost2=[dbserver]
dbport=1523
dbservice=bpel
dbconnstr=jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=[server])(PORT=1523))(ADDRESS=(PROTOCOL=tcp)(HOST=[server])(PORT=1523)))(CONNECT_DATA=(SERVICE_NAME=ebusd)))

Error while deploying the BPEL process

Hi All,
I’m getting the following error while deploying the BPEL process.
“Error:
[Error ORABPEL-10903]: failed to read wsdl
[Description]: in "bpel.xml", Error loading schemas from wsdl.
Error while loading schemas from wsdl file at location "http://ios0501e.idc.ikon.org:7720/vertex-ws/calculate-tax-wsdl.jsp?WSDL". The reason is .
Please verify the schemas defined in wsdl.
[Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
Kindly let me know if you have any pointers on the above.
Thanks in Advance.
Regards
Sravana

Check you proxy settings. Disable them in your deployment tool / JDeveloper

Synchronous BPEL process calling apache soap 2.3.1 service(s) on jboss

I have a problem that is quite frustratiing. I have a very simple synchronous BPEL process and I am trying to invoke some legacy services we have deployed using Apache soap 2.3.1 running on jboss. The process executes, the service executes, but the return value is not received by the BPEL process.
I used obtunnel to capture the data flow and everything seems fine from that perspective. The problem is, if you watch the monitor, the status says active, but the BPEL process returns immediately. It does not wait for the response, so the return value winds up being null. I have tried this numerous times with several services and the result is always the same. This is a serious problem for us. Any suggestions/insight would be very much appreciated.
Ina case there are any doubts as to whether or not it is actually a synchronous process, from the BPEL code:

Below is an example from obtunnel:
==============
Listen Port: 5678
Target Host: pian.wlgore.com
Target Port: 8080
==== Request ====
POST /soap/servlet/rpcrouter HTTP/1.1
Host: pian.wlgore.com:5678
Connection: TE
TE: trailers, deflate, gzip, compress
User-Agent: Oracle HTTPClient Version 10h
SOAPAction: "http://vitalstream.com/webservices/Authenticate"
Accept-Encoding: gzip, x-gzip, compress, x-compress
Content-type: text/xml; charset=UTF-8
Content-length: 829
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<ns0:Authenticate xmlns:ns0="http://vitalstream.com/webservices">
<strAccount xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string">testvar3</strAccount>
<strToken xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string">testvar1</strToken>
<strReferrer xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string">testvar4</strReferrer>
<strSourceURL xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string">testvar</strSourceURL>
<strClientIP xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string">testvar2</strClientIP>
</ns0:Authenticate>
</env:Body>
</env:Envelope>==== Response ====
HTTP/1.1 200 OK
X-Powered-By: Servlet 2.4; Tomcat-5.0.28/JBoss-4.0.1sp1 (build: CVSTag=JBoss_4_0_1_SP1 date=200502160314)
Set-Cookie: JSESSIONID=C656EEE6B641F23F02D6E5BE79CD2A4D.ajp13w; Path=/soap
Content-Type: text/xml;charset=utf-8
Content-Length: 480
Date: Wed, 18 Apr 2007 18:34:19 GMT
Server: Apache-Coyote/1.1
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Body>
<ns1:AuthenticateResponse xmlns:ns1="http://vitalstream.com/webservices" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<return xsi:type="xsd:int">1</return>
</ns1:AuthenticateResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
==============
As you can see, the value is indeed returned from the service, but BPEL indicates a null value for the return:
<messages><Invoke_1_Authenticate_InputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="strSourceURL"><strSourceURL xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">testvar</strSourceURL>
</part><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="strToken"><strToken xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">testvar1</strToken>
</part><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="strAccount"><strAccount xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">testvar3</strAccount>
</part><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="strClientIP"><strClientIP xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">testvar2</strClientIP>
</part><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="strReferrer"><strReferrer xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">testvar4</strReferrer>
</part></Invoke_1_Authenticate_InputVariable><Invoke_1_Authenticate_OutputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Result">null</part></Invoke_1_Authenticate_OutputVariable></messages>

Did you specify the correct message type for your return variable?
<Invoke_1_Authenticate_OutputVariable>
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Result">
null
</part>
</Invoke_1_Authenticate_OutputVariable>
As is returns:
<ns1:AuthenticateResponse
xmlns:ns1="http://vitalstream.com/webservices" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<return xsi:type="xsd:int">1</return>
</ns1:AuthenticateResponse>
Regards,
Marc

When to use Synchronous BPEL process.....??

I know the difference between Asynchronous and Synchronous BPEL process... BUt can any body tell me exactly when to use synchronous BPLE process... it will be great if anybody can give me some example..??

If caller needs to receive output from processing immediately then use sync.
For instance give me get customer details and display immediately on screen
If processing is taking longer time more than fewl seconds use async
Example:
Submit order for processing

Synchronous BPEL processes and dehydration

Hi all,
I am confused about dehydration behaviour of synchronous BPEL processes.
The BPEL Developer's Guide says:
"Dehydration enables the states of long-running processes to be automatically maintained in a database and correlation of asynchronous messages"
IMHO this means that dehydration is applied to asynchronous BPEL processes only - not to synchronous processes.
On the other hand I found a forum entry Re: dehydration ï¼ saying the following:
"Dehydration can optionally be disabled for synchronous flows"
which means that by default synchronous processes will be dehydrated(?).
Can anyone clarify the dehydration behaviour and configuration of synchronous BPEL processes?
Thanks in advance
Ingo

Hi Ingo,
The BPEL Developer's Guide says:
"Dehydration enables the states of long-running processes to be automatically maintained in a database and correlation of asynchronous messages"
This is true, as well as adding a checkpoint() in the Java Embedding Activity will force hydration.
Cheers
Pucha Anirudh

Run queries against system tables for oracle BPEL processes

I want to run queries against system tables for oracle BPEL processes. It is becoming very difficult for me to us EM as it is very slow,
and not all the time, it is sufficient for our needs.
We are doing load testing and we want find out info like how many requests came in and how many faulted and what time is taken by each request...
So do any of you have the query that I can use and tables that I need to go against?

Use the BPEL hydration database table "cube_instance".
There should be plenty of example in the forum regarding this table.

Fault error framework for synchronous Bpel process

Similar Messages

Maybe you are looking for