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
Article Support Platform Matrix for Serena Products
The Supported Platform Matrix outlines the supported client-side and server-side information, including supported operating systems, browser, third party plugins, Serena product integrations, character sets, and upgrade paths.
CMS-XML How to install two versions of Serena Common Tomcat on the same server
Reboot the server for a fresh start. ... (by default in C:\Program Files\Common\tomcat\6.0\ bin ). ... On the Java tab, uncheck the “use default” box and change the JVM path to point to: C:\Program Files\Common\jre\6.0\ bin \ server \jvm.dll
CMS-XML SLM: How to consolidate multiple license keys for one Host ID into a single license file
... the "License Hosts " values match ... From the summary, review the information is correct and then check the box to the far left. ... default location on a Windows-based system is “C:\Program Files\Serena\License Manager” or may be C:\Program Files (x86)\Serena\License Manager if the OS is a 64-bit system. For a UNIX/Linux system, look first for /usr/serena/license_manager. When installed, someone may have
CMS-XML Mainframe Connector Extensions: Mainframe Configuration for accessing ChangeMan ZMF from SBM
... the z/ OS mainframe as follows ... ... SERNET through the server . ... the RLM HTTP server ; this is the server SBM uses to ... ... the RLM HTTP Server . ... new RLM HTTP server is a drop ... used SERNET HTTP server . ... the z/ OS mainframe as follows ... ... SERNET through the server . ... the RLM HTTP server ; this is the server SBM uses to ... ... the RLM HTTP Server . ... new RLM HTTP server is a drop ... used SERNET HTTP server . Configuring the Notification URL ... on z/ OS . is the server name where SBM ... ... number for that server . ... the z/ OS mainframe as follows ... ... SERNET through the server . ... the RLM HTTP server ; this is the server SBM uses to ... ... the RLM HTTP Server . ... new RLM HTTP server is a drop ... used SERNET HTTP server . ... the z/ OS mainframe as follows ... ... SERNET through the server . ... the RLM HTTP server ; this is the server SBM uses to ... ... the RLM HTTP Server . ... new RLM HTTP server is a drop ... used SERNET HTTP server . Configuring the Notification URL ... on z/ OS . is the server name where SBM ... ... number for that server . Configuring the RLM HTTP Server ... The RLM HTTP Server provides an HTML ... ... attached RLM HTTP Server Configuration PDF. ... the SERNET HTTP Server and want information ... attached SERNET HTTP Server PDF, ZMFSernetHTTPforSBMCfg ... ... The RLM HTTP Server is recommended for ... ... The RLM HTTP server MUST be used ...
CMS-XML RLC Release Package deployment fails with a Server Unavailable error if a pre-plan step takes longer than the connection timeout value configured in the Nolio plugin configuration.
RLC Release Package deployment fails with a Server Unavailable error if a pre-plan step takes longer than the connection timeout value configured in the Nolio plugin configuration.
CMS-XML Dim: Z/oS Agent error: +MDHFVS1600001E The local meta data server is not optional.
After upgrading a z/ OS integration for Dimensions CM to version 12.2 or higher, customers may experience the following errors:
CMS-XML Release Package gives error "RequestTimeout: The orchestration request was submitted but the server timed out waiting for the response"
When editing a Release Package and attaching a Dimensions Baseline or a ZMF Package , the system make give error: Error occurred during web service invocation: SOAP Fault Code: env:Server
PDF RLM HTTP Server Overview:
The RLM HTTP Server is a Java based solution that provides ZMF and Z/ OS services to RLM clients. It is distributed as 5 war files and may be installed and configured on any Java Servlet Container such as Tomcat or WebSphere. The 5 Servlet names and a general description are listed below:
CMS-XML Submitting a new Release Packages gives error "SOAP Fault String: Could not send Message"
Error occurred during web service invocation: SOAP Fault Code: soap: Server SOAP Fault String: Could not send Message.
CMS-XML z/os build : incorrect data format picked up
it is reproducible here with a demo db in 12.2.2.3, server and z/ os both scenario : - To reproduce it is supposed to get set-up a z/os build environement
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs