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 Unable to deploy process app with orchestrations
SBM 10.1.2.1
CMS-XML Icons are grey in the orchestration in Mashup Composer
SBM 2009 R2
CMS-XML IE 9 64 bit crashes when selecting Process Apps in SBM Application Repository
SBM 10.1.1.2
CMS-XML SCCM Adapter requires new process app deployment with SBM 10.1.1.2 and 10.1.1.3
file into SBM Composer. Deploy the process app . Note:
CMS-XML SBM: Notifications for newly added mashup not working
SBM
CMS-XML Using the Dimensions CM 10.1.3 Mashup Tool with Business Mashups 2009
SBM 2009 R2
CMS-XML The MergeGetParentResolution orchestration is not working to specification
The MergeGetParentResolution orchestration workflow of the SSM-Incident Management process app is not working to specification. On execution the child items get resolved but field values from the parent such as that of the 'Resolution' field do not get updated.
CMS-XML Problem to deploy the latest Process apps after the upgrade
After upgraded SBM 2009 R4.05 to SBM 11 it was not possible to deploy some process app which contains orchestration . This is happened because a defect in SBM 11 and also Oracle privileges were configured wrong.
CMS-XML What are the exact privileges needed for the SSM orchestration user?
In the SSM Installation and Configuration Guide, there is a section called "Setting Authentication for Orchestrations". The first paragraph says "For on-premise SBM installations that are not running with Single Sign-On (SSO), you must configure the orchestrations in the listed process apps to run under a user account that is authorized to run orchestrations ." The documentation does not explain exactly what permissions are needed.
CMS-XML Deploy "500: null" error when deploying orchestration should return actual error
When deploying a process app that has an orchestration that makes a web service call to a web service that has a WSDL with a problem in it, the deploy failure should return the actual error that is causing the deploy to fail rather than a "500: null" error. Main error server log is similar to: Cannot deploy DPEL definition for process model alf... 500 : null
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs