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 ALM Connector: RestGrid using /almzmfws/services/SernetProxyHttpServer gives: Unknown error received 500
ALM Connector: RestGrid using /almzmfws/services/SernetProxyHttpServer gives: Unknown error received 500
CMS-XML Approval ID is set incorrectly in the Approval Screen in ZMF when using ARM to integrate with SBM.
Approval ID is set incorrectly in the Approval Screen in ZMF when using ARM to integrate with SBM.
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 updatePartPackages web service fails
Attempts to execute the updatePartPackages ARM-ZMF Web Service fail with the following error message: Please implement com.serena.zmf.service.ZMFPackageServicesSkeleton#updatePartPackages
CMS-XML updateDescriptions web service failure
Attempts to execute the updateDescriptions ARM-ZMF Web Service fail with the following error message: Please implement com.serena.zmf.service.ZMFPackageServicesSkeleton#updateDescriptions
CMS-XML Troubleshooting communication among SBM Components using Wireshark
SBM consists of components which can be installed on one or more servers. For example, SBM components include the Application Engine (or IIS component), the Orchestration Engine, Application Repository and Common Services the last three components all running under JBOSS and Java . At times, it is necessary to capture communications between these components for troubleshooting purposes.
CMS-XML ARM: Release Calendar must be created before redeploying Release Packages mashup
When installing ARM 1.1 for the first time or configuring a new ARM environment, Section 5 - Setting Up a Release Calendar (Page 54 of the ARM 1.1 Getting Started Guide) needs to be executed before Section 4 - Configure and Redeploy Release Package (Page 39). Failure to do so will result in various errors being encountered attempting to redeploy the Release Package mashup
CMS-XML getComponents Web Service failing for packages containing new components
Attempts to use the getComponents ARM-ZMF Web Service against packages that contain new components (i.e. components that do not exist in the CMN ZMF baseline library) are failing with the following error : GetComponents Service Error .
CMS-XML ARM-ZMF login web service insisting on secToken being supplied
2. In ARM 1.1 it fails with the following error : java.lang.RuntimeException: secToken cannot be null!!
CMS-XML Unable to execute a command line using Ext.CmdLineWait() function
While testing implementation, it is good practice to have CmdLineWait() call a batch file. From the batch file, it is possible to setup the command line environment, PATH and other variables and output DOS error messages to a text file. This will give you much more visibility in terms of errors.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs