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 Readme for SBM as of 12th April 2012
SBM supports upgrades from any release after 2009 R1. SBM supports the following two different upgrade paths : • If you have already installed SBM 2009 R3 or later, follow the steps in Minor Upgrades to upgrade to SBM • If you have not yet upgraded to at least 2009 R3, follow the steps in solution S138037 to perform the upgrade to SBM
CMS-XML The service cannot be found for the endpoint reference when running orchestration and the orchestration doesn't run after upgrading to SBM 11+
This error is a little different from past versions of SBM. If you see this path in the error /ode/processes ( ode is part of moving to Tomcat in SBM 11.+
CMS-XML SBM 10.x database upgrade to SBM 11.x: ZMFPackageServices.wsdl gives error "s4s-att-not-allowed: Attribute 'defaut' cannot appear in element 'element' "
Find the current copy of the WSDL under your ZMF Connector installation. By default, the path is:
CMS-XML After upgrade to SBM 10.1.4.x, login screen gives "Transport Error: 403 Error: Forbidden"
Restore prior versions of the SSO key stores from back up. Doing this will ensure that SBM uses the version of SSO certificates that were used prior to upgrade. The SBM install will backup all old files in the directory located at the same level as the SBM Install Directory: [backup]\[same SBM path structure exists as in the SBM install directory].
CMS-XML SBM Upgrades from Versions Prior to 2009 R4
Reconfigure the log paths for your license, mail, and notification servers. The LDAP update and import log file path may also need to be reconfigured (if you use LDAP with SBM). These configuration parameters are not changed during the upgrade, even though your installation path has changed.
CMS-XML Email templates missing after upgrade and notifications are sending out emails as though no template exists - Subject: TeamTrack Notification
SBM synchronizes templates from the hard drive with templates from TS_TEMPLATES data.Templates folder path by default is C:\Program Files\Micro Focus\ SBM \Application Engine\emailtemplate.
CMS-XML Old directory recreated after upgrade
After upgrading from SBM 2009 R1 to SBM 2009 R4 where the Serena program directory changed from Business Mashups to SBM, he removed the Business Mashups directory. However, SBM recreates this directory path with the following file:
CMS-XML SBM Installer rolls back after a certain point and SBM 2009 R4 x64 is not installed
This is because there is no valid upgrade path from any previous version of SBM running on a 64 bit OS.
CMS-XML SBM 2009 R3.01 and R3.02 are both a patch and a GA release.
Serena Business Mashups 2009 R3.02 also supports two different upgrade paths . If you have installed Business Mashups 2009 R3, follow the steps in 2009 R3 to 2009 R3.02 Upgrades to upgrade to 2009 R3.02. If you have not upgraded to 2009 R3 yet, you can upgrade directly to 2009 R3.02 from most previous versions.
CMS-XML Cannot install Serena Business Mashups due to an error saying you must uninstall TeamTrack first.
The reason the installer cannot find the 6.6.1.x installation is due to a registry key under HKEY_LOCAL_MACHINE\SOFTWARE\TeamShare\TeamTrack called Root Directory. Remove the \TeamTrack directory from the end of this key (setting this path to <Drive>\Program Files\Serena, instead of <Drive>\Program Files\Serena\TeamTrack). This will allow you to upgrade to Serena Business Mashups 2008.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs