BPEL process Deployment from DEV to PRD

Hi,
I have a question on how to move deployment from one DEV to PRD. I have BPEL subprocess in my process and calling them WSDL. Every subprocess is exposed as webservice. When i move main process to PRD/QA, the main process points DEV WSDL. How to change the main process to point to subprocess.
Could you advise me how to deploy BPEL process form DEV to QA/PRD ?
Thanks,

Asuming you are using 10.1.2.0.2
When developing BPEL processes, make sure your partner-links to other BPEL processes are using the same host name. From JDeveloper it will use your workstation name. CHange this to "localhost". Furthermore JDeveloper is using 9700 as port number, whil ethe application server is using 7777. CHange the OC4J configuration of JDev that it will use port 7777 instead of 9700.
Now you can basicly deploy your BPEL processes to other environments. If you are using adapters make sure that the JNDI naming is implemented on all the environments, (oc4-ra.xml file).

Similar Messages

  • Process flow of bpel process deployment in production server

    Hi,
    Can anyone please explain me the process flow of bpel process deployment in prodcution server . I mean the procedure that we follow for deployment in productions server , what are the steps that we follow , approval from any teams? .....
    Thanks,
    Beginner.

    A quick answer is:
    1. make sure you defined the Application/Integration Server in your developer (user/pass you have - if not oc4jadmin then one the IT gave you).
    2. Deploy your project to that server.
    3. Choose the correct domain in the Console when deploying.
    Is this what you wanted to know???

  • Transporting active version of datasource from DEV to PRD

    Hi,
    When I transport a 3.x datasource from DEV to PRD, the version I am getting in PRD is 'modified'. In DEV we have both modified and active versions and there's no difference between them. When I try to activate the modified version, it says that I have to maintain the transfer rules associated with the datasource. Then it takes me to the transfer rules display but I am not sure what to do next...how to activate the datasource. How do I get the active version from DEV to PRD?
    Thanks

    Hi,
    Pls Refer this link for details about transporting BI Objects
    http://help.sap.com/saphelp_nw04s/helpdata/en/0b/5ee7377a98c17fe10000009b38f842/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/224381ad-0701-0010-dcb5-d74236082bff
    Hope this helps,
    Regards
    CSM Reddy

  • 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

  • Where (which folder) are BPEL processes deployed?

    As far as I know BPEL processes are deployed into the folder
    <APPSERVERHOME>\bpel\domains\default\deploy
    But much to my surprise there are NO processes inside.
    On the contrary I found my searched process in the folder
    <APPSERVERHOME>\bpel\domains\default\tmp
    What is the difference between these folders?
    Can I just delete singel processes from these folders in order to manually undeploy them?
    Or is there no such "hot undeployment" but only the official one through
    the BPEL console?
    Peter

    Hi,
    The deploy directory is used only to deploy the BPEL process. Then the deployment is finished, the jar file is removed.
    The tmp directory is used to store local copy of the build BPEL process. It contains all the bpel source and class files of your BPEL process.
    If you delete the process from the tmp directory (.bpel_xxxx), the bpel engine will create it again at the next startup of your domain (when all the processes are loaded).
    You have two ways to undeploy processes.
    - The first one is from the BPEL console, but it is bit tricky when you have lots of processes.
    - The second is from the BPEL API. Check the API for the IBPELDomainHandle Interface (http://download.oracle.com/docs/cd/E11036_01/integrate.1013/b28986/com/oracle/bpel/client/IBPELDomainHandle.html).
    There is an undeployProcess() method which takes an IBPELProcessHandle. You can get this handle by using the listProcesses() method.
    Hope this can help.
    Raphaël
    http://bpelsoa.blogspot.com/

  • BPEL Control in SOA Suite 10g doesn't display BPEL Process deployed in jdev

    Hello,
    I've created a directory in C:\ as Examples for my demo BPEL Projects.
    After deployment is successful using Jdeveloper, BPEL Control in Oracle Application Server 10g doesn't display the BPEL process in Dashboard. This is possible only if I have my BPEL Projects placed under /jdev/mywork folder or I have to click on "Deploy New Process" and select the jar file from /bpel/output directory.
    How do I make BPEL control to look for the deployed bpel jars by default in C:\Examples folder?
    Help appreciated!

    bpel control won't look at those locations when you have deployed a bpel process
    after deployment it will unpack the jar in some tmp location in your domain
    i'm sure what you mean with those 2 locations, they both have nothing to do with a deployed version of your bpel.
    jdev will generate the jar for you and after that it will be deployed to the application server. After that the jar isnt needed anymore in your jdev workspace, it's already on the server itself

  • URGENT!! HelloWorld.bpel process Deployment Error

    Hi bpel gurus,
    I am new to BPEL. I tried to deploy sample HelloWorld tutorial process with no real luck..
    What i am doing is using obant (also tried equivalent "ant deploy" ) command to deploy the process. I am using BPEL PM for developer on windows XP.
    The following is the gist of the long exception/error I got.
    "C:\product\10.1.3.1\OraBPEL_2\bpel\samples\tutorials\101.HelloWorld\build.xml:79
    : A problem occured while connecting to server "ashdesai.corio.com" using port "
    9700": bpel_HelloWorld_1.0.jar failed to deploy. Exception message is: ORABPEL-04096
    Cannot update process metadata.
    The process domain was unable to insert/update the process metadata for process
    "HelloWorld" with revision tag "1.0" in the datastore. The exception reported is
    : javax.resource.ResourceException: RollbackException: Transaction has been mark
    ed for rollback: Timed out
    Please check that the machine hosting the datasource is physically connected to
    the network. Otherwise, check that the datasource connection parameters (user/p
    assword) is currently valid.
    sql statement: SELECT process_guid, process_id, revision_tag, suitcase_id, state
    , lifecycle, deploy_user, deploy_timestamp FROM process WHERE domain_ref = ? AN
    D process_id = ? AND revision_tag = ? FOR UPDATE ...
    Can anyone tell what setup/config is missing here..?
    Thanks in anticipation!!
    Ashish.

    Ashish:
    If your going to deploy a BPEL process using ant from the command line, you need to make sure that you set up your environment correctly. I've made a few blog posts on the subject of the ANT - environment.
    One of the key files that the ant deploy needs to have access to is the "ant-orabpel.properties" file located in your $BPEL_HOME/utilities directory. If Ant isn't able to get to this file, it will not have the BPEL environment settings for your installation.
    Ben

  • BPEL process deployment

    What is required to deploy a BPEL process on another machine (or oracle home)?
    Here is my current list in order, let me know if there is anything additional or if there are any short cuts/wizards to make doing this easier. Also if you don’t need to be able to recompile the program, are any of the steps (b – e) not needed / changed if you just copy over and manually deploy the jar file?
    a) Copy the workspace folder to the new machine/oracle home and then add it to the application navigator.
    b) Re-add or copy entries in the email/JMS/FTP adapter config files.
    c) Re-add task users. (Can there entries be copied from one file to the other?)
    d) Make sure all referenced local folders exist and are accessible.
    e) Make sure all referenced BPEL processes are deployed.
    This includes the User task services, they seem to be deployed when a user task is added but not when a BPEL process they include is deployed in a new environment.
    f) Compile/deploy the process.
    Thanks,
    Craig

    Hi Craig -
    Your list of steps will certainly work. However, as you suggest, you don't need to recompile the BPEL process on the new machine. You can just copy the jar (what we call the "BPEL suitcase" that is created when you compile the BPEL process. For more information on this, and the different mechanisms for deploying BPEL suitcases, see the technote at:
    http://www.oracle.com/technology/products/ias/bpel/htdocs/orabpel_technotes.tn002.html
    Regarding the user task services, these should just "do the right thing". If you are finding that you deploy a process to a new domain that uses the task service and the task service itself is not automatically deployed by the server, send us the steps to reproduce - this would be a bug (though your workaround of manually deploying the task service would be fine in the meantime).
    Beyond that, there are a few best practices that we have which may eliminate steps (c) and (d) in your list (task users and referenced local folders). We would recommend avoiding local folder references that go outside of the BPEL suitcase when possible and using URL references for things like XSDs. This way you can have a central repository that is available from all the pertinent servers.
    Alternatively, you can include the necessary files with your process in a higher level directory and have an Ant build.xml which copies them to the appropriate locations. We try to do this with our samples, so that there is a single directory (typically called xxxDemo, e.g. LoanFlowDemo) that has a master build.xml that builds all the sub-directories (which typically include a BPEL process, xxxFlow, a UI, dependent services, etc). See the samples in the orabpel\samples\demos directory for several examples of this approach that you may be able to leverage.
    Finally, regarding task users, I'm not sure if there is a simple mechanism for copying them over with our default developer install authentication. I'll check on this however - the question makes sense and we should both make this possible and ship an example where the appropriate users are created as part of the umbrella build.xml for a project. I suspect this will require a simple SQL script, but again I'll check. However, in many cases, again the best practice would be to use an LDAP or similar, globally accessible directory. Then any deployments which have access to the directory service would not require this additional step.
    Let me know if any of this doesn't make sense.
    Dave
    David Shaffer
    Dir Product Mgmt, Oracle BPEL Process Mgr
    [email protected]
    W: 650.506.1729
    http://otn.oracle.com/bpel

  • Can not transport from DEV to PRD (Hang up)

    Hi Experts,
    Please help.. I have this problem, was not able to transport from Dev to Prod, it just hang up.. I've read a lot in web how to solve this problem and did the following:
       ==> Stop all TP running in OS level
       ==> Delete all pending job in Import Monitor (with truck logo)
       ==> and the last to be done is to delete the data from table TRBAT, but it took so long to delete the data in that table.. What I've noticed is that the data left in table TRBAT is the transport number wherein user was log-off during transport execution (as in the middle of the process)..
    What should be the solution of this problem, as we can not proceed with the transport of our changes made in DEV system, as it just hang up in there.. and I'm also having this problem in deleteing data from TRBAT table.
    Thanks.
    Edited by: Deo Pasion on Feb 20, 2010 7:25 AM

    Hi,
    Its well known problem which is discussed many times in many threads.
    Did you check TP System Log and TMS Alert of the System ?
    Execute RSTPTEST report to check the STMS configuration. Also check the existence/status of RDDIMPDP Background Job.
    Please refer these useful threads with similar symptoms.
    [Transport (STMS) issue + Hang|Transport (STMS) issue + Hang]
    [regarding STMS_IMPORT Transport Hang.|regarding STMS_IMPORT Transport Hang.]
    Also check this SAP  Note 71353 - Transports hang during background steps.
    Regards
    Bhavik G. Shroff

  • Invoking BPEL Process problem from Tomcat

    Hi, I got a problrm to invoke BPEL process through JSP.
    I think it's caused from BPEL Library.
    Where can i find com.evermind.server.rmi.RMIInitialContextFactory ?
    the error messages are below.
    javax.naming.NoInitialContextException: Cannot instantiate class: com.evermind.server.rmi.RMIInitialContextFactory [Root exception is java.lang.ClassNotFoundException: com.evermind.server.rmi.RMIInitialContextFactory]
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.oracle.bpel.client.util.BeanRegistry.lookupDeliveryBean(BeanRegistry.java:277)
         at com.oracle.bpel.client.delivery.DeliveryService.getDeliveryBean(DeliveryService.java:250)
         at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:174)
         at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:149)
         at org.apache.jsp.invokeBPEL_jsp._jspService(invokeBPEL_jsp.java:80)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    Caused by: java.lang.ClassNotFoundException: com.evermind.server.rmi.RMIInitialContextFactory
    Thanx.
    jean.

    Hi Rajesh,
    Please refer \bpel\samples\tutorials\102.InvokingProcesses\jsp.
    BPEL Tutorial 7: Invoking BPEL Processes through SOAP and Java : Reference: 2004/06/14/orabpel/d5/1.0
    Hope this helps!
    Regards
    Anirudh Pucha

  • Problem when calling BPEL process (WS) from APEX

    I am trying to add a web service call to a BPEL process I have created (tried a few others aswell), but every time I try to add the WDSL file I get the following error:
    *1 error has occurred*
    The WSDL document contains multiple SOAP bindings. Application Express only supports WSDL's with one SOAP binding. Click Create Web Service Reference Manually to continue creating a reference for this service.
    It is a simple BPEL process which works fine when called from the BPEL Console, however I have no success when calling it from APEX.
    Am I doing something wrong, or is there a bug in BPEL/APEX?
    Oracle BPEL Console v10.1.3.1.0
    Apex: 3.2
    The WDSL looks like this:
    <definitions name="BPELProcess9" targetNamespace="http://xmlns.oracle.com/BPELProcess9">

    <types>

    <schema>
    <import namespace="http://xmlns.oracle.com/BPELProcess9" schemaLocation="BPELProcess9.xsd"/>
    </schema>

    <schema>
    <import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://xxx:8888/orabpel/xmllib/ws-addressing.xsd"/>
    </schema>
    </types>

    <message name="BPELProcess9ResponseMessage">
    <part name="payload" element="tns:BPELProcess9ProcessResponse"/>
    </message>

    <message name="BPELProcess9RequestMessage">
    <part name="payload" element="tns:BPELProcess9ProcessRequest"/>
    </message>

    <message name="WSAReplyToHeader">
    <part name="ReplyTo" element="wsa:ReplyTo"/>
    </message>

    <message name="WSARelatesToHeader">
    <part name="RelatesTo" element="wsa:RelatesTo"/>
    </message>

    <message name="WSAMessageIDHeader">
    <part name="MessageID" element="wsa:MessageID"/>
    </message>

    <portType name="BPELProcess9Callback">

    <operation name="onResult">
    <input message="tns:BPELProcess9ResponseMessage"/>
    </operation>
    </portType>

    <portType name="BPELProcess9">

    <operation name="initiate">
    <input message="tns:BPELProcess9RequestMessage"/>
    </operation>
    </portType>

    <binding name="BPELProcess9Binding" type="tns:BPELProcess9">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>

    <operation name="initiate">
    <soap:operation style="document" soapAction="initiate"/>

    <input>
    <soap:header message="tns:WSAReplyToHeader" part="ReplyTo" use="literal" encodingStyle=""/>
    <soap:header message="tns:WSAMessageIDHeader" part="MessageID" use="literal" encodingStyle=""/>
    <soap:body use="literal"/>
    </input>
    </operation>
    </binding>

    <binding name="BPELProcess9CallbackBinding" type="tns:BPELProcess9Callback">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>

    <operation name="onResult">
    <soap:operation style="document" soapAction="onResult"/>

    <input>
    <soap:header message="tns:WSARelatesToHeader" part="RelatesTo" use="literal" encodingStyle=""/>
    <soap:body use="literal"/>
    </input>
    </operation>
    </binding>

    <service name="BPELProcess9">

    <port name="BPELProcess9Port" binding="tns:BPELProcess9Binding">
    <soap:address location="http://xxxx:8888/orabpel/default/BPELProcess9/1.1"/>
    </port>
    </service>

    <service name="BPELProcess9CallbackService">

    <port name="BPELProcess9CallbackPort" binding="tns:BPELProcess9CallbackBinding">
    <soap:address location="http://set.by.caller"/>
    </port>
    </service>

    <plnk:partnerLinkType name="BPELProcess9">

    <plnk:role name="BPELProcess9Requester">
    <plnk:portType name="tns:BPELProcess9Callback"/>
    </plnk:role>

    <plnk:role name="BPELProcess9Provider">
    <plnk:portType name="tns:BPELProcess9"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>

    Allow me to reply to my own thread, for the benefit of any others who might want to invoke a BPEL WS from APEX facing the same problem:
    Apex does not seem to like asynchronous BPEL processes so the trick is to make a synchronous BPEL process call the asynchronous BPEL process.

  • To move Interfaces from dev to prd/qas

    Hi Experts,
    I have created interfaces in XI developement system  and now want to move it QAS and PRD system
    How should  i go for that....do we need to define business system for QAS and PRD and make all the configuration in ID  again ?
    Thanks in advance.
    Vishal

    Vishal,
    Check this documents for help on this transition:
    /people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
    and also this for more info:
    /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
    /people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
    /people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
    Regards,
    ---Satish

  • Transporting SQ01 Customer Query from DEV to PRD

    Hi All,
    I am not sure whether I am in the right forum, but maybe you still can help me.
    I created SQ01 for Customer Master query in our DEV environment, and i assigned t-code for the query.
    Can i transport it in our PRD? Or it is more advisable to create the t-code in PRD directly?
    Please note that the query is both existing in DEV and PRD.
    Hoping for your positive feedback.
    Thank you.

    Hai TINA,
    Hope you would have created T code using SE93 for your query program.
    and your SQ01 program may be like this, and in the program the bold letter differs from client to client.
    AQ    FU  SYSTQV000003XXXXXXX===
    AQ    IC   SYSTQV000003XXXXXXX===
    So while transporting it may give error that the program is not in the client, or while executing the T CODE it may give dump.
    Hence create the query in production client and create the T code for the program and assign to the users.
    Some tips may be helpful:
    1. Always Use T code : SQVI to create the ALV report, user friendly that SQ01.
    2. In case if you are making Customer master details report, if you are include all customer master tables, in case for some customer if some details were not maintained then the details will not displayed.
    In that case, in the joint between two respective tables, right click and change it to Left Outer join.
    3. If some data is replicated, then need to change the table path, like in case of billing always start from Biling item then to Billing header.
    Regards,
    Mani

  • Change PowerPivot data source when deploying from Dev - Staging - Production

    We have PowerPivot workbooks we store in SharePoint 2013 Libraries. 
    We have a powershell script which automates the deployment of sites and pages. Is there a way using PowerShell (or any scripting language really) to look into the workbook and change the PowerPivot data source when deployment from one environment to
    another? (Dev -> Stage -> Prod) We need to update the workbooks to point to our SSAS cubes Dev -> Stage -> Prod respectively.
    Thank you for any expert advice you may offer,
    Sincerely,
    -Craig

    Basically, it's an excel file (XLSX) file and you can use excel OM for this.
    A simple program (in C# or any language of your choice) can be written to do the following and achieve what you need.
    using XLS = Microsoft.Office.Interop.Excel;
    string info = null;
    XLS.Application application = null;
    try
     application = new XLS.Application();
     var book = application.Workbooks.Open(filepath);
     foreach (XLS.WorkbookConnection wc in book.Connections)
      switch (wc.Type)
       case XLS.XlConnectionType.xlConnectionTypeOLEDB:
        info = wc.Name + " " + wc.OLEDBConnection.Connection.ToString() + "\r\n";
        break;
     book.Close();
    finally
     if (application != null)
      application.Quit();
    Hopefully, this was helpful.

  • Asynchronous BPEL Process called from an empty BPEL process getting lost.

    Hi
    I have an empty BPEL process calling an asynchronous BPEL process. The empty process is triggered by a read file activity. It finishes successfully and even calls the asynchronous process. There is no error thrown but the called asynchronous process does not show up in the dashboard.
    When this asynchronous process is manually run from the console I get the page stating 'Cannot find the specified instance'.
    I am using Jdev 10.1.3.2 and SOA Suit 10.1.3.1.
    Any suggestion as to why this is happening and what is the remedy?
    Buddhadev.

    Check your log as soon as you find that the parent process has found its way into the console. More information on logging can be found here - http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28982/logging.htm
    Not quite sure why its so, but since 10.1.3, I've observed that the console simply doesn't show errored processes at times. So, checking the log can be a starting point in diagnosing the real issue.
    HTH
    Antony

Maybe you are looking for