Process Deployment

I have a processflow, which has been deployed and working.
Now I have created another one process and trying to deploy that, where I am getting this following error message,
RPE-02002: The Database Link DEV10G.aaa.bbbb@WB_LK_PF_P cannot be created or updated to reference schema runtime_rep_owner using (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=heaven.aaa.bbbb)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=DEV10G.aaa.bbbb))). This may be due to invalid content or insufficient privileges. The associated exception trace may give more details
Any Idea what went worng over here with this message

I'm experiencing the same error. I have some questions for clarification...
1) I am using OWF_MGR (user/schema created by the OWF setup script) as the deployment location for my process module.
- a) Is this the user that needs the DBA privilege?
- b) If so, does it needs privileges to the runtime repository user or owner?
- c) Am I way off track?
2) Do you know where TNS string comes from that's shown in the error message? Mine seems to have the wrong host address in it, it should be an IP, but it has the [machine_name].[router_domain] there.
Thanks!

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???

  • 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

  • Why can not I see the process deployed to the server in workspace?

    As captioned, After I deploy the BPM project to server, why cannot i see it in the workspace?

    It can be because the user that you are using for log-in to Workspace is not mapped to the Initiator role for ur process.
    Check the role mapping for your process either by going to BPM Workspace --> Administration --> Organization --> Roles
    OR
    OEM --> Application Deployments --> Right Click on any application --> Security --> Application Roles --> BPMProcessRolesApp
    HTH...

  • Exception on process deployment leads to unability to start process

    Dear BPMers,
    <br><br>
    when I try to deploy my BPM process with a custom message for start, I get the following exception:
    <br><br>
    Interface Definition : sap.com_DynamicWSProxies_proxyName_{http://www.sap.com}proctest_demo.sap.com~proctest~BPMcomponent_03eac373-70c3-46e7-8650-5df83af53088_WS
    [EXCEPTION]
    com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException: Interface Definition : sap.com_DynamicWSProxies_proxyName_{http://www.sap.com}proctest_demo.sap.com~proctest~BPMcomponent_03eac373-70c3-46e7-8650-5df83af53088_WS
    at com.sap.esi.esp.lib.mm.config.profiles.SingleService.createRuntimeService(SingleService.java:272)
    at com.sap.esi.esp.service.server.WSConfigurationImpl.createSingleServiceLocal(WSConfigurationImpl.java:943)
    at com.sap.esi.esp.service.server.WSConfigurationImpl.onCommitStart(WSConfigurationImpl.java:777)
    at com.sap.esi.esp.service.server.ESPDeploymentInterface.onCommitStart(ESPDeploymentInterface.java:180)
    at com.sap.engine.services.webservices.server.deploy.wsclients.notification.WSClientsStartNotificationHandler.onCommitPhase(WSClientsStartNotificationHandler.java:46)
    at com.sap.engine.services.webservices.server.deploy.wsclients.notification.WSClientsAbstractDNotificationHandler.onShortPhases(WSClientsAbstractDNotificationHandler.java:110)
    at com.sap.engine.services.webservices.server.deploy.wsclients.notification.WSClientsAbstractDNotificationHandler.onShortPhases(WSClientsAbstractDNotificationHandler.java:50)
    at com.sap.engine.services.webservices.server.deploy.WSBaseAbstractDNotificationHandler.onCommitPhase(WSBaseAbstractDNotificationHandler.java:46)
    at com.sap.engine.services.webservices.server.deploy.wsclients.WSClientsStartProcess.commitProcess(WSClientsStartProcess.java:123)
    at com.sap.engine.services.webservices.server.deploy.WebServicesDeployManager.commitStart(WebServicesDeployManager.java:844)
    at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.commitStart(ContainerWrapper.java:485)
    at com.sap.engine.services.deploy.server.application.StartTransaction.commonCommit(StartTransaction.java:332)
    at com.sap.engine.services.deploy.server.application.StartTransaction.commit(StartTransaction.java:315)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:718)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:755)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesSequentially(ParallelAdapter.java:382)
    at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhases(StartTransaction.java:673)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2980)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceWait(DeployServiceImpl.java:3439)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceAndWaitAuth(DeployServiceImpl.java:3587)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2907)
    at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:112)
    at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:76)
    at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:42)
    at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:105)
    at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:69)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:1131)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:1020)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:808)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deployInternal(DeployerImpl.java:443)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:217)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:904)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:456)
    at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
    at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
    at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
    at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
    at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
    at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)
    <br><br>
    The web service accepting the start message is created (I used an asynchronous web service). I can execute it but the process is not started. If I try to start it via the process repository, I get the following error:
    <br><br>
    Nachricht:  Failed to start the process; Process manager adapter may not be started
    Datum:  2010-04-16
    Zeit:  18:56:34:893
    Kategorie:  /Applications
    Ort:  com.sap.tc.bpem.wdui.procstarter.procstarter.comp.ProcStarterComp
    Applikation:  sap.com/tc~lm~itsam~ui~mainframe~wd
    <br><br>
    Any ideas?

    Hi Patrick
    How did you fixed it?
    Greets from switzerland
    Alex

  • 정상 Build인 Process의 Deploy 시 오류

    흠... 제가 이 포럼을 전세내서 질문 던지고 있네요.
    일종의 '도배'를 하게 되어 죄송합니다.
    다름이 아니라 개발한 프로세스를 Deploy를 하는데 아래와 같은 오류가 발생하고 있습니다. Build 자체는 Warning 하나 없이 깨끗하게 되는데 Deploy를 하면 Apache Ant에서 아래와 같은 오류를 발생시키고 있습니다. 뭔가가 꼬인 것 같은데 원인을 모르겠네요. T_T
    [오류 메시지 in JDeveloper]
    BUILD FAILED
    C:\jdevstudiobase10133\jdev\mywork\MyCVS\Hansol_IS\IF_SKK_IS_Sell\build.xml:79: "7777" 포트를 사용하여 "nrap2dev" 서버에 접속하는 중 오류 발생: bpel_IF_SKK_IS_Sell_1.0.jar failed to deploy. Exception message is: ORABPEL-09903
    Could not initialize activation agent.
    An error occured while initializing an activation agent for process "IF_SKK_IS_Sell", revision "1.0".
    Please ensure that the activation agents are configured correctly in the bpel deployment descriptor (bpel.xml).
    oracle.tip.adapter.fw.agent.jca.JCAActivationAgent: java.lang.reflect.InvocationTargetException
    at com.collaxa.cube.engine.core.BaseCubeProcess.startAllActivationAgents(BaseCubeProcess.java:370)
    at com.collaxa.cube.engine.deployment.DeploymentManager.activateDefaultRevision(DeploymentManager.java:1577)
    at com.collaxa.cube.engine.deployment.DeploymentManager.setDefaultRevision(DeploymentManager.java:1536)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deployProcess(DeploymentManager.java:886)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(DeploymentManager.java:728)
    at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:445)
    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:585)
    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.JAASInterceptor$1.run(JAASInterceptor.java:31)
    at com.evermind.server.ThreadState.runAs(ThreadState.java:646)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
    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.InvocationContextPool.invoke(InvocationContextPool.java:55)
    at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
    at DomainManagerBean_RemoteProxy_4bin6i8.deploySuitcase(Unknown Source)
    at com.oracle.bpel.client.BPELDomainHandle.deploySuitcase(BPELDomainHandle.java:319)
    at com.oracle.bpel.client.BPELDomainHandle.deployProcess(BPELDomainHandle.java:341)
    at deployHttpClientProcess.jspService(_deployHttpClientProcess.java:376)
    at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
    at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
    at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
    at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
    at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:396)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
    at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:410)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
    at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
    at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
    at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
    at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:595)
    이 현상에 대해 취해본 조치는 아래와 같습니다.
    1.개발한 인터페이스를 다시 작성 (2회, 서로 컴퓨터에서)
    - 결과는 동일합니다. Build 는 정상, Deploy시 오류
    2.서로 다른 3대의 컴퓨터에서 Deploy 시도
    - 마찬가지로 계속 오류 발생
    3.WSDL cache 삭제 후 Server restart 뒤 deploy
    - 동일한 오류 발생
    메시지 보면 activation agent 초기화하다가 발생했다고 되어 있는데 bpel.xml 에 나와있는 아래의 내용처럼 특별히 값을 준 것이 없이 기본으로 설정이 되어 있습니다..
    [bpel.xml 내용]
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <BPELSuitcase>
    <BPELProcess id="IF_SKK_IS_Sell" src="IF_SKK_IS_Sell.bpel">
    <partnerLinkBindings>
    <partnerLinkBinding name="T_SALE_IF_P">
    <property name="wsdlLocation">T_SALE_IF_P.wsdl</property>
    </partnerLinkBinding>
    <partnerLinkBinding name="T_SALE_IF_U">
    <property name="wsdlLocation">T_SALE_IF_U.wsdl</property>
    <property name="retryInterval">60</property>
    </partnerLinkBinding>
    <partnerLinkBinding name="PartnerLink_1">
    <property name="wsdlLocation">PartnerLink_1.wsdl</property>
    </partnerLinkBinding>
    </partnerLinkBindings>
    <activationAgents>
    <activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="T_SALE_IF_P">
    <property name="portType">T_SALE_IF_P_ptt</property>
    </activationAgent>
    </activationAgents>
    </BPELProcess>
    </BPELSuitcase>
    혹시 이런 비슷한 상황을 아시는 분 계시면 힌트 부탁 드립니다.
    즐거운 하루 보내세요.

    개발자로부터 오전에 Deploy가 정상으로 되었다는 얘기를 들었습니다.
    바뀐 것 없이 갑자가 되니 원인이 뭔지 감이 안 잡힙니다. T_T
    어찌됐건 돌아가니 기뻐해야할 것 같은데 음... 찜찜함은 어쩔 수가 없네요... -_-;                                                                                                                                                                                                                                                               

  • Like in LC7.x, how to create process template in LiveCycle ES2? would process deployment create it?

    I created a long-lived process  and linked a form to a manual process. I deployed and invoked the  process from Workspace. Like in 7.x, I looked for the process template  in TB_PROCESS_TEMPLATE table and its empty. should I do anything more to  create it?
    Thank you.
    --Shiva.

    I'm sure that someone at the NetBeans website mailing list knows how to do that. Do note that these are Java forums, not NB support.

  • 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 using ant

    Hi,
    I am trying to deploy a simple BPEL process using ant and Jdev created build.xml. I am getting the following error:
    "Could not create task or type of type: validateTask"
    Can anyone please tell me what I am mising here? I have ORACLE_HOME variable set to right location and using version 10.1.3.1.0.
    Thanks,
    AP

    HI ,
    Have a look at below link
    http://biemond.blogspot.com/2009/09/deploy-soa-suite-11g-composite.html

  • 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

  • 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).

  • BPEL Process Deployment Issue: ORABPEL-05205

    I am trying to deploy HelloWorld process from tutorial.
    i am deploying through the console.
    The Deployment is sucessful, but i am not able to see the process in the BPEL console dashboard.
    "bpel_HelloWorld_v2007_01_04__49421.jar" file is located in C:\oracle\oracleAS\integration\orabpel\domains\default\deploy directory.
    Oracle BPEL Server version 10.1.2.0.2
    Following is the error log
    ORABPEL-05205
    Missing BPEL archive file.
    The process domain cannot locate the BPEL archive for process "HelloWorld ", revision "v2007_01_04__49421".
    If you have deployed the process please check that it is located in the directory "C:\oracle\oracleAS\integration\orabpel\domains\default\deploy".
         at com.collaxa.cube.engine.deployment.CubeProcessLoader.extract(CubeProcessLoader.java:265)
         at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(CubeProcessHolder.java:877)
         at com.collaxa.cube.engine.deployment.CubeProcessHolder.getProcess(CubeProcessHolder.java:789)
         at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAll(CubeProcessHolder.java:361)
         at com.collaxa.cube.engine.CubeEngine.loadAllProcesses(CubeEngine.java:914)
         at com.collaxa.cube.admin.ServerManager.loadProcesses(ServerManager.java:284)
         at com.collaxa.cube.admin.ServerManager.loadProcesses(ServerManager.java:250)
         at com.collaxa.cube.ejb.impl.ServerBean.loadProcesses(ServerBean.java:219)
         at IServerBean_StatelessSessionBeanWrapper14.loadProcesses(IServerBean_StatelessSessionBeanWrapper14.java:2399)
         at com.collaxa.cube.admin.agents.ProcessLoaderAgent$ProcessJob.execute(ProcessLoaderAgent.java:401)
         at org.quartz.core.JobRunShell.run(JobRunShell.java:141)
         at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:281)
    <2007-01-04 14:44:34,687> <ERROR> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::loadAll> Error while loading process 'HelloWorld ', rev 'v2007_01_04__50399': Missing BPEL archive file.
    The process domain cannot locate the BPEL archive for process "HelloWorld ", revision "v2007_01_04__50399".

    .. and NOW .. this !! :-(
    00:31:28,608 INFO [STDOUT] <2007-01-19 00:31:28,607> <ERROR> <default.collaxa.cube.engine.deployment> <CubeProcessLoader::create> Unknown process classname.
    The process "HelloBoy" (revision "1.0") is missing its classname; this element cannot be created without its classname.
    00:31:28,608 INFO [STDOUT] <2007-01-19 00:31:28,608> <ERROR> <default.collaxa.cube.engine.deployment> Process "HelloBoy" (revision "1.0") load FAILED!!
    00:31:28,609 ERROR [LogInterceptor] RuntimeException in method: public abstract void com.oracle.bpel.client.ejb.interfaces.IBPELDomainManagerBean.loadProcessArchive(java.lang.String,com.oracle.bpel.client.auth.DomainAuth) throws com.oracle.bpel.client.ServerException,java.rmi.RemoteException
    java.lang.NullPointerException
         at java.util.Hashtable.put(Hashtable.java:398)
         at com.collaxa.cube.engine.deployment.CubeProcessHolder.addStatus(CubeProcessHolder.java:275)
         at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:1240)
         at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(CubeProcessHolder.java:882)
         at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadArchive(CubeProcessHolder.java:824)
         at com.collaxa.cube.engine.CubeEngine.loadProcessArchive(CubeEngine.java:939)
         at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.loadProcessArchive(BPELDomainManagerBean.java:390)
         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:324)
         at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:683)
         at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:186)
         at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:72)
         at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:84)
         at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:282)
         at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:148)
         at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:111)
         at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
         at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
         at org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionContainer.java:331)
         at org.jboss.ejb.Container.invoke(Container.java:709)
         at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
         at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:197)
         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
         at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:97)
         at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:90)
         at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
         at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55)
         at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:100)
         at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85)
         at $Proxy146.loadProcessArchive(Unknown Source)
         at com.collaxa.cube.engine.deployment.CubeProcessMonitorWork.run(CubeProcessMonitorWork.java:130)
         at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
         at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
         at java.lang.Thread.run(Thread.java:534)

  • BPEL Process Deployment Descriptor needs to be fixed.

    I made a simple hello world BPEL Process i made it using Bpel Designer for eclipse. I have BPEL Manager 10.1.3.1.0 version when i build bpel project its gives me following error kindly help me out of this problem.
    deployment descriptor format error.
    Error when parsing the deployment descriptor "bpel.xml", because "org.apache.xerces.parsers.XML11Configuration"
    Fix the deployment descriptor.
    here is my ant script
    <?xml version="1.0"?>
    <project name="SyncHelloWorld" default="main" basedir=".">
    <property name="deploy" value="default"/>
    <property name="rev" value="1.0"/>
    <target name="main">
    <bpelc input="${basedir}/bpel.xml"
    rev="${rev}"
    deploy="${deploy}"
    />
    </target>
    </project>
    Here is my bpel.xml
    <?xml version="1.0"?>
    <BPELSuitcase>
         <BPELProcess id="SyncHelloWorld" src="SyncHelloWorld.bpel">
              <configurations/>
              <partnerLinkBindings>
                   <partnerLinkBinding name="client">
                        <property name="wsdlLocation">SyncHelloWorld.wsdl</property>
                   </partnerLinkBinding>
              </partnerLinkBindings>
         </BPELProcess>
    </BPELSuitcase>
    Thanks in advance help me out its urgent. I need to move on.

    IS ESB/BPEL LISTENING on 127.0.0.1:8888 ?

Maybe you are looking for