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 Configurator does not set non-proxy hosts
To work around the issue, find and edit the file COMMON_CONFIG.BAT located in [SBM]\COMMON\ TOMCAT \BIN Find this Section
CMS-XML How to setup Tomcat / JBoss to make endpoint requests via a proxy
In the Proxy Server dialog box, we ask for information for HTTP or HTTPS connections. The settings used depends on the endpoint or target server that is listed in the Application Repository. HTTP endpoints use the information in the HTTP section.
CMS-XML HTTP 404 error occurs on Tomcat cluster
When setting SBM up to cluster Tomcat on the same server as IIS, the Configurator incorrectly tries to proxy the following URIs using IIRF. Doing this results in loop ending in an HTTP 404. Sometimes Configurator dos not add the settings below. Key Aspects of Configuration Tomcat is running on IIS server for both servers
CMS-XML Clustered Tomcat causes common services errors in Work Center
If we cluster Tomcat, we need to enforce stickiness with Tomcat. This KB handles the case where the Application Engine and Tomcat components are installed on the same server , and we are using IIS to proxy all connections.
CMS-XML VMINET: Setting up VM Server in a DMZ (across a firewall)
VM Server 6.7.10 and later consists of two main components, a Java Servlet container / server ( Tomcat ) and a proxy connector. By design both components are installed on same server. However, in some situations there is a need to install these components on separate machines to facilitate load balancing and tighter security.
CMS-XML uriworkermap.properties for tomcat cluster incorrectly set to worker1 instead of worker-local
When using Tomcat clustering with all components installed on two servers using IIS to proxy Tomcat requests and an external load balancer, some of the uriworkermap.properties are incorrectly set to worker1 instead of worker-local. Specifically the following are not be set worker-local when they should be (all the mappings in this file should be worker-local for this configuration):
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]
CMS-XML Enabling Proxy Server Support
4) Navigate to Common\jboss405\ server \default\deploy\jbossweb- tomcat 55.sar and note the Connector port used. For example:
CMS-XML Suggestions for placing SBM server in the cloud
This option turns off all HTTP(S) ports for Tomcat. It then enables IIS to proxy all connections to Tomcat using the AJP protocol. The AJP protocol is an unencrypted binary protocol used to route packets from IIS to Tomcat. SBM will send those packets to localhost when all components are installed on the same server.
CMS-XML Logging in gives error "The proxy server isn’t responding" and server.log gives "Error creating bean with name 'liquibase' defined in class path resource"
Run the SQL script located at C:\Program Files\Serena\Solutions\RLC\rlc\WEB-INF\classes\db\releaselocks.sql Restart the Release Control java server (Jboss/ tomcat ). For additional details, see KB S142885 .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs