Outbound BPEL Message Handler

Guys,
I am successfull in implementing the Inbound Message Handler for security and other stuff, but the outbound message handler in a similar fashion isn't working...
Any clue on it....here is the configuration...
<bpel-message-handlers>
<message-handler id="out_interception">
</message-handler>
     <outbound-flow>
          <message-handler id="out_interception" />
     </outbound-flow>
</bpel-message-handlers>
I am using Oracle BPEL PM 10.1.2.0.2 on Oracle AS in Windows/AIX platforms.
Thanks,
- Soumen.

Hi Soumen,
this is not supported. :-(
But you can use requestHeaderHandlers and responseHeaderHandlers. Disadvantage is that you have to define it for each partnerlink. But is works.
Have a look here for example http://www.oracle.com/technology/products/ias/bpel/htdocs/callingstatefulwsfrombpel.html
Peter

Similar Messages

Any API to get handle to Outbound BPEL process endpoint activation?

Hi,
we are developing both inbound and outbound BPEL processes using a custom JCA 1.5 based adapter. For the inbound BPEL process deployment/undeployment, we have the ResourceAdapter's endpointActivate() endpointDeactivate() methods called in and so we can post process, like clean up endpoints when these methods get called. Is there somethign simillar that we can use as an API to get a handle to the outbound process endpoints deactivate/activate, so that we can clean up these too, or does the oracle adapter framework internally clean these up?
Also even though we undeploy all processes before stopping the adapter (from the bpel console), after that if we redeploy the adapter rar, from then on any new BPEL process deployment (through jdeveloper) always throws a "500 Internal Server Error". Only after restarting the SOA, then on any new deployments go through fine. This is a serious limitation for us.. Any idea why this is happening and how to resolve this?
Thanks
Pramodh

Hi Pramodh,
That's a nice requirement.
The inbound (ActivationSpec) properties can only be set dynamically (typically via the BPEL console) if their values are bound via property values defined in bpel.xml for the particular JCA Activation Agent in question. This is fundamentally as per the JCA 1.5 design where EndpointActivation (which receives an instance of ActivationSpec) takes place when the BPEL process starts up, i.e. only once. More often than not the BPEL process will have to be bounced (Off/On) for ActivationSpec attribute changes to take effect (thereby allowing the JCA 1.5 inbound message endpoint to be restarted/reinitialized). Some adapters do look dynamically for changes to bpel.xml bound values (subscribed to via the adapter framework) and will react appropriately without the need for bumping the process (e.g. adjusting a timeout or retryCount or other secondary attribute which doesn't change the first order attributes of the endpoint, such as e.g. the database host name etc). An example of an activation property which requires the adapter to restart is the JMS adapter MessageSelector property.
Having said that, please try using the activation agent properties set in the outbound PL and see if that works!
Cheers
A

Outbound BPEL Process deployment Issue in SOA (binding.jca-12600)

Hi,
I have Designed an Outbound BPEL Process for Siebel CRM Service Integration using Jdeveloper (11.1.1.3.0). After that I am facing the deployment issue of this application in SOA suite (11.1.1.6.0). Following is the deployment.log status in jdeveloper:-
[10:57:54 AM] ---- Deployment started. ----
[10:57:54 AM] Target platform is (Weblogic 10.3).
[10:57:54 AM] Running dependency analysis...
[10:57:54 AM] Building...
[10:57:58 AM] Deploying profile...
[10:57:58 AM] Wrote Archive Module to C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Deploying sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:57:58 AM] Processing sar=/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Adding sar file - C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Preparing to send HTTP request for deployment
[10:57:59 AM] Creating HTTP connection to host:10.10.22.81, port:7001
[10:57:59 AM] Sending internal deployment descriptor
[10:57:59 AM] Sending archive - sca_QueryWithView_Invoke_rev1.0.jar
[10:58:00 AM] Received HTTP response from the server, response code=500
[10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:58:00 AM] HTTP error code returned [500]
[10:58:00 AM] Error message from server:
#;There was an error deploying the composite on AdminServer: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
#;Generic error.
#;Cause: Unable to find suitable outbound binding.
#;Please create a Service Request with Oracle Support.
#;: Generic error.
#;Generic error.
#;Cause: Unable to find suitable outbound binding.
#;Please create a Service Request with Oracle Support.
[10:58:00 AM] Check server log for more details.
[10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:58:00 AM] #### Deployment incomplete. ####
[10:58:00 AM] Error deploying archive file:/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
And the following is the SOA Server Side log file status:-
####<Jun 3, 2013 10:36:05 AM AST> <Info> <Health> <HOSADDAT02> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-00000000000000f4> <1370244965280> <BEA-310002> <36% of the total memory in the server is free>
####<Jun 3, 2013 10:36:12 AM AST> <Error> <ServletContext-/soa-infra> <HOSADDAT02> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-000000000000182b> <1370244972343> <BEA-000000> <Error during deployment
oracle.fabric.common.FabricException: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
     at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:64)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
     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:301)
     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:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     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:139)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
     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:2273)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.fabric.common.FabricDeploymentException: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
{rootCauses=[]}
     at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:458)
     at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy314.load(Unknown Source)
     at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
     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:301)
     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:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     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:139)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
     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:2273)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: BINDING.JCA-12600
Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
     at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterBindingConfig.addAdapterReference(AdapterBindingConfig.java:206)
     at oracle.integration.platform.blocks.adapter.AdapterReference.setupAdapterReference(AdapterReference.java:506)
     at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:425)
     at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
     at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
     at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
     at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
     at $Proxy314.load(Unknown Source)
     at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
     at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
     at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
     at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
     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:301)
     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:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     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:139)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
     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:2273)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Kindly help me in this regard

Solution:
Workaround the issue immediately by removing the "ns1:" qualification on the operation for the binding.jca entry in the composite.xml and redeploying.
For example:
From:
<binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
operation="ns1:BAPI_COMPANYCODE_GETDETAIL"/>
To:
<binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
operation="BAPI_COMPANYCODE_GETDETAIL"/>
Regards,
Shaheer Badar

Did anyone tried Rejection Message Handler via Queue based method?

Dear All,
I am presently doing a Rejected Message Handler process and successfully implemented with File based and Web Service based. But I am not getting the clue for Queue based. We can enqueue the rejected message into queue as a JMS message via this method. But the URI format they have given is *"jdbc:oracle:thin:@<host>:<port>:<sid>#<un>/<pw>#queue"*. Format includes jdbc connection string along with queue name. For this I have created JMS module with JDBC Persistent store and created queue in it. But still I am not able to enqueue the message inside the queue. Also, is there anyway to see the queue names inside the DB. Did anyone tried this method? Could you please share the info??

WL JMS Queue consume>BPEL1 (One way) invoke>Mediator service (one way) route> BPLE2 (one way). Also I have added transaction properties in BPEL1 and 2 + References + Services.
Now, if there is a fault in BPEL2 the transaction should be rolled back in BPEL1 and the message should be seen in the WL queue itself. But that is not happening in my case. Everything is getting rolled back upto a point just after the >recieve activity in BPEL1 except the message is not getting rolled back to queue.There will be 2 transactions in this scenario : 1) jms queue to soa hydration store 2) soa-hydration to bpel execution.
This is the behaviour for 1 way or async interfaces , jms adapter thread completes its transaction work after persisitng to dehydration store and another bpel system thread starts work executing the bpel code after retrieving the message off the db in a separate transaction. So the rollback you are seeing is only applicable for 2nd transaction which roll backs to the dehydration store instead of the queue.
For synchronous interfaces, the same adapter thread will be involved for complete message processing including bpel code execution. So I think if you want to get the jms queue within the same transaction you can try set up the interfaces to be sync, even with dummy responses. This might make jms adapter thread to start a transaction --> read message off queue within the same transaction --> execute bpel code within same transaction --> complete/rollback transaction based on bpel code execution.

ORABPEL-05002 - Message handle error - Session has timed out or was invalid

In our production environment we are facing this issue.
We are trying to find the root cause to fix the issue.
My Understanding:*
In the below error message,
we are able to see the Session has timed out or invalidated.
Also we are able to see the Non-fatal connection error. I believe that when the MDB trying to process the dispatched message, it will invoke the message from invoke_message table of dehydration store. At this point of time it gets non-fatal connection error so we are gettign this error.
I need to know the difference between fatal and non-fatal connection error. Is my understanding correct or not ?
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message *"com.collaxa.cube.engine.dispatch.message.system.RemoveMessage"; the exception is: Session has timed out or was invalidated*
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:207)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:619)
<2010-08-11 23:05:10,131> <ERROR> <WorkExecutorWorkerThread-129> <engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
java.rmi.NoSuchObjectException: Session has timed out or was invalidated
at com.evermind.server.ejb.StatefulSessionEJBObject.throwPassivisationException(StatefulSessionEJBObject.java:335)
at com.evermind.server.ejb.StatefulSessionEJBObject.remove_X(StatefulSessionEJBObject.java:174)
at com.evermind.server.ejb.StatefulSessionEJBObject.remove_X(StatefulSessionEJBObject.java:159)
at com.evermind.server.ejb.LocalStatefulSessionEJBObject.remove(LocalStatefulSessionEJBObject.java:25)
at com.collaxa.cube.engine.util.EngineBeanCache.releaseMessageBean(EngineBeanCache.java:293)
at com.collaxa.cube.engine.dispatch.message.system.RemoveMessageHandler.handle(RemoveMessageHandler.java:36)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:142)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:619)
<2010-08-11 23:05:10,132> <ERROR> <WorkExecutorWorkerThread-129> <engine.dispatch> *<DispatchHelper::handleMessage> Not fatal connection error ... not retrying: class com.oracle.bpel.client.ServerException: Session has timed out or was invalidated*
<2010-08-11 23:05:10,132> <ERROR> <WorkExecutorWorkerThread-129> <engine.dispatch> *<BaseScheduledWorker::process> Failed to handle dispatch message ... exception ORABPEL-05002*
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.system.RemoveMessage"; the exception is: Session has timed out or was invalidated
-----

I'm having the same problem. I posted to VSM sample and Pooled ApplicationModule Maximum Inactive Age
which seems to be a similar situation.
Does anyone have any information on where this time out parameter is set on either the app module or OAS and how to handle this error correctly?
Thanks,
Brian

Error message handling in BAPI...

Hi Guys,
I am working on documentation of a BAPI used SAP insurance module. Now I want to see all the error messages associated/ handled in that BAPI. How can I do that ? Is there a table in data dictionary where I can see error messages handled by a given Function module/ BAPI?
Any inputs will be highly appreciated.
Thanks.
Regards,
Tushar.

Hi,
here´s one possible solution:
CALL FUNCTION 'MESSAGES_INITIALIZE'.
LOOP AT it_return_bapi.
    CALL FUNCTION 'MESSAGE_STORE'
         EXPORTING
              arbgb          = it_return_bapi-id
              exception_if_not_active = ' '
              msgty                = it_return_bapi-type
              msgv1          = it_return_bapi-message_v1
              msgv2          = it_return_bapi-message_v2
              msgv3          = it_return_bapi-message_v3
              msgv4          = it_return_bapi-message_v4
              txtnr          = it_return_bapi-number
              zeile          = ' '
         EXCEPTIONS
              message_type_not_valid = 1
              not_active              = 2
              OTHERS                  = 3.
ENDLOOP.
CALL FUNCTION 'MESSAGES_STOP'
       EXCEPTIONS
            a_message = 04
            e_message = 03
            i_message = 02
            w_message = 01.
IF NOT sy-subrc IS INITIAL.
    CALL FUNCTION 'MESSAGES_SHOW'
         EXPORTING
              i_use_grid         = 'X'
              i_amodal_window    = i_amodal_window
         EXCEPTIONS
              inconsistent_range = 1
              no_messages        = 2
              OTHERS             = 3.
ENDIF.
ENDFUNCTION.
Best regards

Possibility to transfer additional parameters in outbound XML message

Hi,
is there any possibility to transfer additional parameters in outbound XML message using (BADI: BBP_SAPXML1_OUT_BADI).
Additional parameters are,
1. Communication Method for the Business Partner
2. R/3 Vendor # & logical system for Business Partner
3. Relationship between Business Partner Number and R/3 Vendor Number is BP GUID.
How can we extended the structure in the BADI.
Please give me qucik response.
Thanks & Regards.
Surya

Look for structure which the interface parameters are referring, there you should see some dummy structures referring to INCL_EEW* for e.g. in PO header INCL_EEW_PD_HEADER_SSF_PO. Add additional fields and pass the data accordingly.
Regards, IA

Receiver File adapter - 'Empty Message Handling' option to ignore not worki

Hi,
I am trying to create the Files in receiver based on condition.But I am gettiung error in communication channel when there is no payload. Receiver I am usuing FCC and processing tab I selected -'Empty Message Handling' option to ignore .
one source -> Target 1 (0..1 occurance in signature tab changed, message mapping and operation mapping)
and Target 2 (0..1 occurance in signature tab changed)
and I put the message type level condition. While creating first message If did not create the Message type in my maaping still my Receiver File communication channel is giving error. even thow I my receiver interface occurance is 0..1
Right now I am in PI7.1 and SP7 is the bug for support pack do I am missing any thing. and do I need to upgrade any nwe patch. appreciate your help.
Regards,
Venu.

Hi,
here is the my requirment one source -> two target interfacess (0..1)
If u have 2 target interfaces,then this is not suffice..... u should make it as 0..unbounded both in operation mapping and message mapping.
But based on ur requirements posted above i guess u have only one inbound interface at a time based on some conditions....
But,
<messages>
<messages1>
based on condition first message type not created in mapping.
<messgaes2>
The error u r getting is because.... u want only one interface in target at a time....
Then u should not generate Message1 also in the target.
So avoid mapping to message1 if u want only message2.
If both message1 and message2 are created in target means... it is triggering for two interfaces.... so avoid one message1 or message2... based on some conditions u have..
Still nt solved do post...
Babu

Receiver file adapter creates empty files, Empty-Message Handling SP19

Hello,
We have just upgraded the system to SP19.
One of the new features is that it should be possible to determine how XI messages with an empty main payload are to be handled in the receiver file adapter.
If the parameter Empty-Message Handling is set to 'Ignore' no file should be created if the main payload is empty. In our case an empty file (size 0 kb) is still created even though the main payload is empty and the flag is set to 'Ignore'.
Has anybody experienced the same problem?
// Best regards Hans

This should work:
Use your own adapter module that parses incoming message and checks if it has any record sets in the document. If it does not have any record sets, then set the message to empty and then give this modified message to File receiver.
For example, see the example code below:
Module imports..
Audit log import..
DOM imports/SAX imports..
public ModuleData process(ModuleContext moduleContext, ModuleData inputModuleData) throws ModuleException {
          try {
               // get the XI message from the environment
               Message msg = (Message) inputModuleData.getPrincipalData();
               AuditMessageKey amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.INBOUND);
               Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"RemoveRootTag: Module called");
               XMLPayload payLoad = msg.getDocument();
               Document doc = parseXmlFile(payLoad.getInputStream());
               if(doc != null){
                    if(!doc.getDocumentElement().hasChildNodes()){
                         Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS, "Document is empty!!");
                         payLoad.setContent("".getBytes());
                         msg.setDocument(payLoad);
               // provide the XI message for returning
               inputModuleData.setPrincipalData(msg);
               } catch (Exception e) {
               // raise exception, when an error occurred
               ModuleException me = new ModuleException(e);
               throw me;
               // return XI message
          return inputModuleData;
     private Document parseXmlFile(InputStream xmlpayload) {
          try {
               DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
               factory.setValidating(false);
               //        Create the builder and parse the file
               Document doc = factory.newDocumentBuilder().parse(xmlpayload);
               return doc;
          } catch (SAXException e) {
          } catch (ParserConfigurationException e) {
          } catch(IOException e){
          return null;

MESSAGE HANDLER OF CLASS if_hrpa_message_handler IS NOT WORKING

WE HAVE WRITTEN THIS CODE AS BELOWS INSIDE BL BADI....THE ERROR MESSAGE IS GETTTING POPULATED IN THE MESSAGE_LIST BUT DOESN'T GET DISPLAYED WHILE CHECKING AND SENDING THE FORM FROM THE FRONT END.
THE BELOW CODE IS JUST A SAMPLE CODE IN OUT BADI METHOD THERE ARE SEVERAL VALIDATIONS ON THE FAILURE OF EACH OF THEM A ERROR MESSAGE SHOULD GET TRIGERRED FROM THE FRONT END.MESSAGE_HANDLER IS ALREADY AVAILABLE INSIDE INITIAL COMPUTATIONS SO THERE IS NO REASON TO CREATE OBJECT BADI MESSAGE HANDLER
[[ IF sy-uname = 'PGOSH' OR SY-UNAME EQ 'CGHOSH'.
   DATA badi_message_handler   TYPE REF TO cl_hrpa_message_list.
     DATA message_handler        TYPE REF TO if_hrpa_message_handler.
     DATA is_ok   TYPE boole_d.
    CREATE OBJECT badi_message_handler.
      message_handler = badi_message_handler.
        message-msgid = 'ZHPA'.
        message-msgty = 'E'.
       message-msgno = '010'.
       message-msgv1 = c_none_plans. "'Invalid Plan'(z09).
         CALL METHOD message_handler->add_message
            EXPORTING
              message = message
              cause   = space . "message_handler->ERROR . "infotype_specific . "unknown.
              is_ok = 'X' ."space.
         badi_message_handler->add_messages( message_handler ).
         RAISE error_with_message.
ENDIF.]]
PLS PROVIDE YOUR INPUTS REGATRDING THE REASION WHY THE CODE IS NOT GETTING TRIGERRED.
Edited by: PRIYANKUSH GHOSH on Jun 18, 2010 4:01 PM

Moderator message - Welcome to SCN.
Please do not use all caos in your posts. It makes it hard to read..
Also, Please read Please read "The Forum Rules of Engagement" before posting! HOT NEWS!! and How to post code in SCN, and some things NOT to do... and [Asking Good Questions in the Forums to get Good Answers|/people/rob.burbank/blog/2010/05/12/asking-good-questions-in-the-forums-to-get-good-answers] before posting again.
Rob

Message handling with multiple lines to display

We have a requirement to issue an error message during dialog processing (PAI) and I'd like to use standard message handling if possible. The syntax
MESSAGE W008(ZTM) DISPLAY LIKE 'I'.
gives me a dialog box but handles the message as an error hence processing stops and the user returns to the screen. I want this functionality but with the ability to display several lines in the message pop up box. I've looked at the function modules POPUP_DISPLAY_MESSAGE but this displays only 1 line and POPUP_TO_CONFIRM which handles multiple lines but doesn't stop processing (unless further code is added to handle the response). Can someone suggest a standard of way of achieving this requirement or how to handle a response as an error in the subsequent processing after a call to function module POPUP_TO_CONFIRM.

hi,
you can handle like this.
call function 'POPUP_TO_CONFIRM'
        exporting
          titlebar                    = text-000
DIAGNOSE_OBJECT             = ' '
          text_question               = v_text
          text_button_1               = 'YES'
ICON_BUTTON_1               = ' '
          text_button_2               = 'NO'
ICON_BUTTON_2               = ' '
          default_button              = '1'
          display_cancel_button       = 'X'
USERDEFINED_F1_HELP         = ' '
         start_column                 = 25
         start_row                    = 6
POPUP_TYPE                  =
IV_QUICKINFO_BUTTON_1       = ' '
IV_QUICKINFO_BUTTON_2       = ' '
       importing
         answer                      = v_ans
TABLES
PARAMETER                   =
       exceptions
         text_not_found              = 1
         others                      = 2
      if sy-subrc <> 0.
        message id sy-msgid type sy-msgty number sy-msgno
                with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      endif.
      case v_ans.
        when '1'.
          leave program.
        when '2'.
          call screen 100.
        when others.
          call screen 100.
      endcase.
endcase.
Here : 1 means yes,
          2 means no.
Regards
Sandeep Reddy

Advantages of Using Queued Message Handler vs. Standard State Machine

Hello,
What are the advantages of using a Queued Message Handler? Also, why are they more powerful than using Standard State Machines?
Thanks!

They are really just sort of an extension of a state machine. The general idea is that you have one loop doing a specific job. You then use a queue to tell it how/when to do this job. For instance, I might have a log file loop. I will send it commands to open a file, write some data, write some more data, and finally close the file. Each of those commands are coming from the queue. The beauty with this setup is that anybody that can get a reference to that queue can send the command to that loop.
So the QMH is "better" than a state machine mostly because of the decoupling of functions. In a given application, I will have a loop for log file writing, GUI updates, reading of a DAQ, instrumenet communications, server communications, etc. Trying to do all of that in a single loop state machine is a major pain in the rear end. Seperating them out makes life so much easier.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Empty-Message Handling is not working in receievr File Adapter

Hi All,
I have selected "Empty-Message Handling" = 'Ignore'in Receiver File adapter, but still empty files are creating in target directory.
Message mapping generates output based on the conditon, if the condition is 'false' mapping will generate empty file (no data is being mapped).
Why Receiver file adapter is processing empty fiels even i set 'ignore' empty fiels in configuration (ID)?
Hoe can i manage not to place empty fiels in target directory?
File type is '.txt'
Your help would be appreiciated greatly.
Thanks,
Rajesh

Not sure why is it not working. Make sure the channel is activated and cache is refreshed properly. But as a workaround you may use OS script checking for size of message and deleting it or configure a BPM to avoid the file creation. Or else an adapter module as shown
/people/gowtham.kuchipudi2/blog/2006/01/13/stop-creation-of-an-empty-file-from-file-adapter-using-module
Regards,
Prateek

Recevier adapter empty message-handling ignore

Hi all,
I configured file receiver adapter with file content conversion (comma separated).
In processing parameters Empty-message handling is set to Ignore.
Payload that is in message generated from SAP is:
<?xml version="1.0" encoding="utf-8" ?>
<mt_ap_invoice xmlns:prx="urn:sap.com:proxy:DES:/1SAI/TAS128FC2C2C3C8E901DC22:700:20 08/06/25" />
There are no any data that is filling structure (structure main node is defined as 0...unbounded) and still empty file with 0 bytes is created.
Please can you tell what is wrong in this setup as In case of empty message I don't want that file is generated?
Regards,
Nenad

- open Integration Builder
- open your file receiver adapter
- go to tab Processing
- change Empty Message-Handling to 'Ignore'
Cheers,
André

Outbound SOAP Message with Attachment

The requirement is to invoke a web service by sending attachments in the outbound SOAP message. The attachment body needs to be assigned in the message flow, using an element E1 extracted from the message incoming into the flow.
I am trying to use attachments variable to set content-type (text/xml) and body using E1. However, these are not getting assigned to attachments variable, as seen by logging the variable.
I was told that $attachments cannot be changed inside the flow (it is marked black in the console unlike the header and body that are marked green). If that is the case, how do we invoke services using attachments from a message flow?
Any pointers would be appreciated.

Hi,
A SOAP message may need to be transmitted together with attachments of various sorts, ranging from facsimile images of legal documents to engineering drawings. Such data are often in some binary format. For example, most images on the Internet are transmitted using either GIF or JPEG data formats. In this document we describe a standard way to associate a SOAP message with one or more attachments in their native format in a multipart MIME structure for transport.
yes it is possible to send attachment with the SOAP.
SOAP Message Packages
A "SOAP message package" contains a primary SOAP 1.1 message. It may also contain additional entities that are not lexically within the SOAP message but are related in some manner. These entities may contain data in formats other than XML. The primary SOAP 1.1 message in a message package may reference the additional entities. Such additional entities are often informally referred to as "attachments." This section describes how to construct SOAP message packages and how SOAP processors will process them.
A SOAP message package is constructed using the Multipart/Related media type, which is defined in RFC 2387. The rules for the construction of SOAP message packages are as follows:
The primary SOAP 1.1 message must be carried in the root body part of the Multipart/Related structure. Consequently the type parameter of the Multipart/Related media header will always equal the Content-Type header for the primary SOAP 1.1 message, i.e., text/xml.
The MIME Multipart/Related encapsulation of a SOAP message is semantically equivalent to a SOAP protocol binding in that the SOAP message itself is not aware that it is being encapsulated. That is, there is nothing in the primary SOAP message proper that indicates that the SOAP message is encapsulated .
For more details you can refer these links
http://www.w3.org/TR/SOAP-attachments
http://www.w3.org/TR/soap12-af/
regards
Aashish Sinha
PS : reward points if helpful

Outbound BPEL Message Handler

Similar Messages

Maybe you are looking for