Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Copying Mashups, Applications or Orchestrations
Problem 1 - I have a Mashup that I want to copy but it is clashing with one that already exists. This might occur because you are sharing an on-demand system and want to import a mashup that someone has already imported.
CMS-XML Mashups containing orchestrations cannot be run or deployed on machines that are not connected to the Internet
To work around this problem: In Mashup Composer, export the mashup . Unzip the exported mashup.
CMS-XML SBM: Access Denied and crash when closing a process app in Composer
When closing a process app in Composer, Composer lists processes that have the name "" or "". If there are multiple instances of Composer on the server, Composer may try to access process information from a Composer run as another user. This would cause the access denied error as seen in the Composer log.
CMS-XML SBM: How to copy a global process app into a new, empty environment
In this use case, you have a global process app with customer tables, triggers, etc. and you want to copy that global to a new, empty environment. The global is a special process app, and you can't just import it like you might with other process apps. Instead, you must follow specific steps.
CMS-XML Sample SBM process applications (previously from AppCentral)
Previously, we had several sample process apps stored on our AppCentral server. We have now created a new interactive Serena community for process apps and plug-ins, blogs, forums and videos. To access the new site, go to . The
CMS-XML Issues with pre-built SBM mashups using SFDC.
Issues with pre-built SBM mashups using SFDC.
CMS-XML SBM 2008 - Cannot get mashup from Application Engine
Customer logs in to Mashup Manager and goes to Environments > Default Environment > Mashups and he is selecting a Mashup from the Sample DB, e.g. Incident Management.
CMS-XML How to Delete the Mashup2009 DSN Manually After SBM Uninstall
System DSNs that use the "Oracle for SBM " driver cannot be deleted after SBM is uninstalled. To work around this issue, delete all DSNs that use the “Oracle for SBM" driver before you uninstall SBM. If you have already uninstalled SBM and you still need to delete a DSN that uses this driver, you must delete the DSN from the registry. The Mashup2009 DSN can be found here:
CMS-XML "Request to Test" mashup - the installation of QC requires SQL Server Express Advanced and will not work with version delivered with SBM
Please note that step 2 of the "Request to Test" Mashup requires that you create new field in Quality Center. This step will fail if QC is installed on the SQL Server Express database supplied with SBM. It requires the Advanced Edition which is freely downloadable instead.
CMS-XML Change to inclusion of Global Application in Mashups in SBM 2008 R3 and later
If a user had explicitly included the "Global Application" in a mashup other than the "Global Mashup", this relationship will be changed to a reference when upgraded to SBM 2008 R3 or later. If the user was expecting to be able to deploy/promote changes to the Global Application as part of the non-global mashup , this will not occur.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs