Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Cannot deploy Orchestration - [ERROR] META-INF/bpel-definition.xml could not read wsdl document
SBM 2009 R4.02
CMS-XML Unable to deploy process app with orchestrations
SBM 10.1.2.1
CMS-XML Not able to delete an Orchestration Link nor Deploy
SBM 10.1.5.2
CMS-XML Event map and orchestration links that are deleted do not actually get removed when deployed
SBM 2009 R1
CMS-XML Mashups containing orchestrations cannot be run or deployed on machines that are not connected to the Internet
Mashups containing orchestrations cannot be run or deployed on machines that are not connected to the Internet
CMS-XML Import of sample database in 11.0 does not include orchestration tables i.e. BPEL or ODE tables other than ODE_WORKFLOW must deploy
SBM 11.0
CMS-XML Cannot deploy orchestration - org.apache.axis2.AxisFault: First Element must contain the local name, Envelope , but found html - com.serena.core.runtime.CoreException: Failed to deploy event map
Cannot deploy orchestration - org.apache.axis2.AxisFault: First Element must contain the local name, Envelope , but found html - com.serena.core.runtime.CoreException: Failed to deploy event map
CMS-XML SBM ERROR -- Cannot deploy BPEL definition for process model alf/38efa375-98dc-4985-b825-cf5825c45879/ - 500: could not parse upload request.
This error message is caused by the BPEL server (i.e. the Orchestration Engine) cannot access the temporary .zip file on the server's file system. In some instances this was caused by the antivirus software on the OE server blocking the java.exe
CMS-XML Get error "couldn't parse jbpm configuration from resource 'jbpm.cfg.xml'" in server.log file. Also orchestrations don't run and you can't deploy an application that has an orchestration in it.
In order to fix this open the following file in notepad. C:\Program Files\Serena\ SBM \Common\jboss405\server\default\conf\jboss-service.xml Search for "8083"
CMS-XML SBM 10.x database upgrade to SBM 11.x gives error "Cannot deploy BPEL definition for process model alf/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/" and "Deploy failed; error: [BpelParseErr] Error parsing BPEL process: the BPEL is either malformed or is invalid"
During the Orchestration Engine Database upgrade all of the process apps are redeployed. (See KB S142694 for details.) In this document, we will talk about the failure caused by this error:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Title: Dimensions CM: Deploying Emergency Fixes (demonstration)
This demonstration shows you how to deploy an emergency fix to a live production environment in Dimensions CM. You will learn how to promote requests to any stage in the Global Stage Lifecycle, promote and deploy in the same operation, and browse deployment areas.
Title: Dimensions CM: Deploying Requests (demonstration)
This demonstration shows you how to deploy requests in Dimensions CM. You will learn how to promote requests to the next stage in the Global Stage Lifecycle, deploy requests by
Title: Dimensions CM: Scheduling Deployment (demonstration)
This demonstration shows you how to schedule a deployment in Dimensions CM. You will learn how to set a deployment sequence, schedule a deployment, and use the Queue tab in the Deployment view

Additional Assistance

  • Submit a Case Online
  • FAQs