Configuring VHI to use separate network interfaces for management and session server communication

  • 7022970
  • 16-May-2018
  • 07-Aug-2018

Environment

Verastream Host Integrator (VHI) 7.7 and later
Windows 2008 R2
Windows 2012 R2

Situation

You are attempting to configure VHI server with multiple network interfaces, where one interface is used for management, and the second interface is used for communication between VHI servers.

The interface used for communication between VHI servers does not have any knowledge or access to the management interface.

Resolution

Before making any changes, it is recommended systems be backed up.

Below are instructions for configuration changes to servers to force which interface VHI will use for communication.

If a cluster is not being used then the parts about breaking and creating a cluster can be skipped.

 

1.       Remove the servers from the Management Cluster and make sure they are completely separated.

2.       Remove the Load Distribution Domain and the second session server from the Host Integrator.

3.       Add the session server that was removed, back into its Host Integrator Session Server installation via the Administrative Console.

4.       Steps 5 through 27 need to be done on both servers.

5.       Open the “Verastream Administrative Console” on either server.

6.       Select the menu item “Perspective/Host Integrator/Session Servers”

7.       Right click on the server name under “Installation/Servers” and select “Properties”

8.       Change the “Address:” to the IP address of the local production interface.  On host “TestServer1” you would change the entry to “Address:192.168.1.1” and on host “TestServer2” would be “Address:192.168.1.2”.

9.       Select “OK” and close the “Verastream Administrative Console”.

10.   Stop the “Verastream Host Integrator Session Server” and “Verastream Management Server” services on both servers.

11.   Open the file “sesssrvr.config” which is by default located at “C:\Program Files\Attachmate\Verastream\HostIntegrator\etc” in a text editor.

12.   At the top of the file, change the “Server” entry to the fully qualified server name.  For example: “testserver1.company.com”

13.   Save the file and close it.

14.   Open the file “container.properties” located by default in “C:\Program Files\Attachmate\Verastream\ManagementServer\conf” in a text editor.

15.   On the first line append the IP address of the local production interface you want to use to the “host=” entry.  On host “TestServer1” you would change the entry to “host=192.168.1.1” and “TestServer2” would be “host=1192.16.1.2”.

16.   Save the file and close it.

17.   Open the file “container.properties” located by default in “C:\Program Files\Attachmate\Verastream\HostIntegrator\sesssrvr\conf” in a text editor.

18.   On the first line append the IP address of the local production interface you want to use to the “host=” entry.  On host “TestServer1” you would change the entry to “host=192.168.1.1” and “TestServer2” would be “host=1192.16.1.2”.

19.   Save the file and close it.

20.   Open the file “container.conf” located by default in “C:\Program Files\Attachmate\Verastream\ManagementServer\conf” in a text editor.

21.   Add the following line after the entry “wrapper.java.additional.5=-Duser.country=US”.  On host “TestServer1” you would change the entry to “-Djava.rmi.server.hostname=192.168.1.1” and “TestServer2” it would be “-Djava.rmi.server.hostname=192.168.1.2”

wrapper.java.additional.6=-Djava.rmi.server.hostname=172.168.xxx.xxx

22.   Save the file and close it.

23.   Open the file “sesssrvr.conf” located by default in “C:\Program Files\Attachmate\Verastream\HostIntegrator\etc” in a text editor.

24.   Add the following line after the entry “scriptmgr.java.additional.6=-Dcom.attachmate.integration.container.BSAFE.SSL-J.enabled=false”.  On host “TestServer1” you would change the entry to “-Djava.rmi.server.hostname=192.168.1.1” and “TestServer2” it would be “-Djava.rmi.server.hostname=192.168.1.1”

scriptmgr.java.additional.7=-Djava.rmi.server.hostname=192.168.xxx.xxx

25.   Save the file and close it.

26.   Start the “Verastream Host Integrator Session Server” and “Verastream Management Server” services on both servers.

27.   Verify the Management Server and Host Integrator Sever are working. (i.e. Try deploying a model to the session server, execute a web service procedure, confirm no new errors in the logs, etc)

28.   Please recreate your Load Distribution Domain and Management Cluster

 

 


Cause

Since there is no routing between the interfaces, VHI needs to be told which interface to communicate on between servers.  VHI will try to use the first interface identified by Windows, and that could be an unknown interface between servers.

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