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 V8.2.03 REST API: Secured Port prevents ZMF variable & EVTNOxx from being set to “Y”.
V8.2.03 REST API: Secured Port prevents ZMF variable & EVTNOxx from being set to “Y”.
CMS-XML How to change the port number in scheduled reports URL from port 80 if using SSL on a secure port
How to change the port number in scheduled reports URL from port 80 if using SSL on a secure port
CMS-XML Dim: Build: Specify an alternative HTTP port for Build communcation to a remote build agent
Running Build fails with Start timeout error Tomcat is configured to use port 8443 for secure communication 8080 is blocked for external communcation, user confirms that it works when 8080 is not blocked.
CMS-XML Authentication to Secure LDAP causes Operations Error after upgrading to Business Mashups 2008 R2.02
When you have a Business Mashups 7.0.0 (GA) release which is using LDAP authentication on the Secure port 636 and if you upgrade to Business Mashups 2008 R2.02, you may receive a Bind Authentication...Operations Error when trying Authenticate. No other changes to the system are made.
CMS-XML Trying to test connection in Composer and get Connection attempt failed when "Use Secure Connection" is selected.
Make sure the Port value is the jboss https port as specified in the Configurator tool. By default this is set to 8243
CMS-XML Trying to connect Composer using Secure SSL Connection get error "The request was aborted: Could not create SSL/TLS secure channel"
If you try to connect Composer to the repository using a secure connection, you may get the following errors when it tries to connect. This would by default try to use the 8243 JBoss/Tomcat port .
CMS-XML Composer cannot connect to the Repository - Error: ... Failed to retrieve valid security token ... could not establish trust relationship for the SSL/TLS secure channel with authority
If you are not using SSL then in Configurator deselecct the SSL configuration for Tomcat. Untick "Use HTTPS on Port " and Apply.
CMS-XML SBM Port Usage List
IIS HTTPS Used for secure access to Application Engine and Web services Serena License Manager Ports
CMS-XML Installing a Secure Version of the ChangeMan ZMF REST API-Jenkins Integration
- Jenkins is running on jenkins-server.microfocus.com secure port 9070.
CMS-XML Tips for Securing SBM Server
For Tomcat, we have both HTTP, HTTPS, and an AJP port open by default. However, you utilize IIS to proxy all connections to SBM (see the Component Servers section), you will effectively shutdown HTTP(S) ports in Tomcat, thus eliminating a possible attack vector. In this case, all calls to Tomcat go through IIS and get proxied to Tomcat via AJP[2]
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs