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 SBM 11.1 upgrade overwrites the cert2user_mapping_keys.xml configuration file
The SBM 11.1 upgrade overwrites the "\Program Files\Serena\SBM\Common\Tomcat 7.0\server\default\webapps\idp\ WEB - INF \ conf \cert2user_mapping_keys.xml" file which contains user specific mappings performed by the IDP service.
CMS-XML KM-Dim7: Where is the INET configuration file under Dimensions 7?
Where is the INET configuration file under Dimensions 7? The file can be found under the following directory structure: DimINET\jakarta-tomcat-3.2.1\webapps\dimensions\ WEB - INF \classes\merant\adm\dimensions
CMS-XML File Server configuration file server-config.wsdd gets replaced by 0 byte file if disk volume run out of space
If the disk volume containing the Version Manager installation runs out of space, the Version Manager File Server configuration may be lost because the file containing this configuration ( vm/common/tomcat/webapps/serenafs/ WEB - INF /server-config.wsdd ) could get replaced by an empty (0 byte) file.
CMS-XML Configuration Files, Web Interface Templates, JavaScript Files, and String Changes That Have Changed in 2009 R3.01
The following files are not upgraded (configuration changes you have made in earlier versions are not brought forward when you upgrade to 2009 R3.01). You must manually re-apply any configuration changes you made to the following files: Common\jboss405\server\default\deploy\ALFSSOLogin.war\ WEB - INF \ conf \truststore.jks Common Use Cases that Require Manual Upgrade:
CMS-XML List of Configuration Files Not Automatically Preserved by the 2009 R2 Installer
3 - The following file is backed up to: \Business Mashups\Manager\BackupPatch \Business Mashups\Common\jboss405\server\default\deploy\mashupmgr.war\ WEB - INF \mashupmgr.cfg
CMS-XML List of Configuration Files Not Automatically Preserved by the Patch Installer
\Business Mashups\Manager\BackupPatch \Business Mashups\Common\jboss405\server\default\deploy\mashupmgr.war\ WEB - INF \web.xml \Business Mashups\Common\jboss405\server\default\deploy\mashupmgr.war\WEB-INF\mashupmgr.cfg
PDF Configuration Files, Web Interface Templates, JavaScript Files, and String Changes That Have Changed in 2009 R3
The following files are upgraded (configuration changes you have made in earlier versions are brought forward when you upgrade to 2009 R3): Common\jboss405\server\default\deploy\ALFSSOLogin.war\ WEB - INF \web.xml Common\jboss405\server\default\deploy\ALFSSOLogin.war\WEB- INF\conf\fedsvr-core-config.xml
CMS-XML Web services invocation timeout values are not synchronized between AE and OE on distributed system
To work around this issue, you will need to modify the "mex.timeout" setting in the "Tomcat 7.0\server\default\webapps\ ode \ WEB - INF \ conf \ ode .endpoint" file on the Orchestration Engine to match the setting on the Application Engine server.
CMS-XML Configuring SBM Orchestration Engine Timeouts
On the Orchestration Engine server, navigate to the following: Tomcat 7.0\server\default\webapps\ ode \ WEB - INF \ conf \ ode .endpoint Adjust the following timeout settings as necessary:
CMS-XML Every hour SBM database gives: Error: 8623, Severity: 16, State: 1. The query processor ran out of internal resources and could not produce a query plan.
If you do not want to use this feature at all, you can disable it from collecting this data by editing SBM\Common\tomcat\server\default\webapps\ ode \ WEB - INF \ conf \ ode -runtime.properties. Set the option to “oe.stat.enabled=false”. Tomcat restart is NOT needed.
Pages [Next]

Welcome kb sso

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs