Error Configuring Web Services in Verastream Administrative Console

  • Document ID:7021307
  • Creation Date:19-May-2015
  • Modified Date:19-Dec-2019
    • Micro Focus Products:
      Verastream Host Integrator (VHI)

Environment

Verastream Host Integrator version 7.1 SP1 through 7.7 SP2

Situation

If your Verastream Host Integrator (VHI) environment consists of multiple servers with firewalls, you may see errors when attempting to configure web services in Administrative Console.

If you have a multi-server firewalled environment, and run Administrative Console to access Session Server Properties > Web Services on a different session server, you may see the following errors:

View Full Size
Figure 1. Error Configuring Session Server Web Services: The web services properties are not valid nor editable because there was a communication problem with the server...
Figure 1. Error Configuring Session Server Web Services: The web services properties are not valid nor editable because there was a communication problem with the server...

 View Full Size
Figure 1. Error Configuring Session Server Web Services: The web services properties are not valid nor editable because there was a communication problem with the server...
Figure 2. Could Not Accept Changes: The currently displayed page contains invalid values.

Resolution

Complete the following steps to configure the session server to use a fixed port number for JMX communication:

  1. Locate the container.properties file located in the %VHI_ROOT%/sesssrvr/conf directory. Note: You are modifying the session server configuration, not the management server configuration.
  2. In a text editor, on the rmi.export.port.ssl line, set a desired port number for encrypted RMI communications. (The default value 0 indicates use of arbitrary ephermeral ports.)
  3. Important: After saving the modified file, restart the management server as described in KB 7021352.
  4. Configure your firewall to allow communications on the port you specified in step 2.

Note: When you upgrade your product installation in the future (major release, service pack, or hotfix), the container.properties file may revert to new defaults. After upgrading, the above steps may need to be repeated.

Cause

For web services management, the management server component communicates with the session server using encrypted JMX/RMI (not WCP). After a request comes into port 35000, another port (specified by rmi.export.port.ssl property) is used to handle the request and send back the response. By default, the property is configured to use any available arbitrary ports, which is problematic for firewalls.

Additional Information

Legacy KB ID

This document was originally published as Attachmate Technical Note 10160.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.