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 Invalid characters being passed in ZMF REST Service HTTP headers
in the HTTP header data when executing ZMF REST Services. For example :
CMS-XML ChangeMan ZMF REST Services 8.2 Patch 2 Hotfix 1
by manually updating them after transmission or by a suitably authorized user submitting something similar to the following, sample FTP script: open <ipOrHost
CMS-XML ZMF REST-API missing service delete component from package.
ZMF REST -API missing service delete component from package.
CMS-XML ZMF REST Services polling function issuing erroneous error messages (CMNs544I & CMNs540I)
ZMF REST Services polling function issuing erroneous error messages (CMNs544I & CMNs540I)
CMS-XML Installing a Secure Version of the ChangeMan ZMF REST API-Jenkins Integration
10. Verify Installation After taking all of the steps documented above, ensure that you can access the REST API services in a secure manner. For example , as we have configured a secure set of 8.2 Patch 4 REST services to run on port 9992, using the Chrome browser, navigate to the following address:
CMS-XML SBM: Rest Grid connecting to ZMF Connector returns error 500
... /almzmfws/ services /SernetProxyHttpServer With the ZMF Connector 6. ... /almsernet/ services /SernetProxyHttpServer Verify the ZMF Started Task Setup: Look at the SERPRINT for the ZMF started task, and verify the CMN port number given. ... For example , if there are two ZMF started tasks that are both using the same CMN port number, the second one started will have these errors in the SERPRINT:
CMS-XML REST Services: German characters causing data translation errors in Tomcat server output
ChangeMan ZMF 8.2 Patch 3
CMS-XML Attempts to create package using REST Services prototyping tool fail
A customer is attempting to prototype a ZMF package create (POST /zmfrest
CMS-XML ZMF REST API – misaligned component/browse output
Running the component browse REST service from the test function for a card image component returns the data. However, the first line is returned in column 1 of the data and all subsequent lines are indented approximately 8 characters.
CMS-XML REST Services – Tomcat Log shows SEVERE error (tomcat-users.xml could not be found)
Customer is on ZMF 8.2 Patch 3 and has the REST Services Tomcat server up. They noticed in the Tomcat log the SEVERE error message listed below. The customer confirmed the file does exist using ISPF option 3.17.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs