Untitled

Management Server, Session Server and Host Emulator use JMX/RMI for configuration and management. By default, these components use specific, documented ports. Management server uses 33000-33001; Session Server uses 35000-35001; Host Emulator uses 36000-36001.

Changing RMI/JMX Port Numbers

To change Management Server RMI and JMX ports, see KB 7021327 or documentation. To change Session Server RMI/JMX ports, see KB 7021307.

Secure vs. Non-Secure Ports

The ports used by VHI are secure. If you need to connect to these JMX/RMI configuration services with a non-secure client (not recommended), you can enable non-secure ports by editing conf/container.properties for the server in question.

The property rmi.port sets the base port for non-secure connections to the service. It is set to 0 (disabled) by default.

The property rmi.export.port sets the port that non-secure clients call back on to use the service. It can be set to 0, to tell VHI to use an arbitrarily assigned port at runtime, or you may choose a fixed port.

Save your changes to container.properties and restart the service.

Related:

  • No Related Posts

Untitled

Management Server, Session Server and Host Emulator use JMX/RMI for configuration and management. By default, these components use specific, documented ports. Management server uses 33000-33001; Session Server uses 35000-35001; Host Emulator uses 36000-36001.

Changing RMI/JMX Port Numbers

To change Management Server RMI and JMX ports, see KB 7021327 or documentation. To change Session Server RMI/JMX ports, see KB 7021307.

Secure vs. Non-Secure Ports

The ports used by VHI are secure. If you need to connect to these JMX/RMI configuration services with a non-secure client (not recommended), you can enable non-secure ports by editing conf/container.properties for the server in question.

The property rmi.port sets the base port for non-secure connections to the service. It is set to 0 (disabled) by default.

The property rmi.export.port sets the port that non-secure clients call back on to use the service. It can be set to 0, to tell VHI to use an arbitrarily assigned port at runtime, or you may choose a fixed port.

Save your changes to container.properties and restart the service.

Related:

  • No Related Posts

Untitled

Management Server, Session Server and Host Emulator use JMX/RMI for configuration and management. By default, these components use specific, documented ports. Management server uses 33000-33001; Session Server uses 35000-35001; Host Emulator uses 36000-36001.

Changing RMI/JMX Port Numbers

To change Management Server RMI and JMX ports, see KB 7021327 or documentation. To change Session Server RMI/JMX ports, see KB 7021307.

Secure vs. Non-Secure Ports

The ports used by VHI are secure. If you need to connect to these JMX/RMI configuration services with a non-secure client (not recommended), you can enable non-secure ports by editing conf/container.properties for the server in question.

The property rmi.port sets the base port for non-secure connections to the service. It is set to 0 (disabled) by default.

The property rmi.export.port sets the port that non-secure clients call back on to use the service. It can be set to 0, to tell VHI to use an arbitrarily assigned port at runtime, or you may choose a fixed port.

Save your changes to container.properties and restart the service.

Related:

  • No Related Posts

Untitled

Management Server, Session Server and Host Emulator use JMX/RMI for configuration and management. By default, these components use specific, documented ports. Management server uses 33000-33001; Session Server uses 35000-35001; Host Emulator uses 36000-36001.

Changing RMI/JMX Port Numbers

To change Management Server RMI and JMX ports, see KB 7021327 or documentation. To change Session Server RMI/JMX ports, see KB 7021307.

Secure vs. Non-Secure Ports

The ports used by VHI are secure. If you need to connect to these JMX/RMI configuration services with a non-secure client (not recommended), you can enable non-secure ports by editing conf/container.properties for the server in question.

The property rmi.port sets the base port for non-secure connections to the service. It is set to 0 (disabled) by default.

The property rmi.export.port sets the port that non-secure clients call back on to use the service. It can be set to 0, to tell VHI to use an arbitrarily assigned port at runtime, or you may choose a fixed port.

Save your changes to container.properties and restart the service.

Related:

  • No Related Posts

Untitled

Management Server, Session Server and Host Emulator use JMX/RMI for configuration and management. By default, these components use specific, documented ports. Management server uses 33000-33001; Session Server uses 35000-35001; Host Emulator uses 36000-36001.

Changing RMI/JMX Port Numbers

To change Management Server RMI and JMX ports, see KB 7021327 or documentation. To change Session Server RMI/JMX ports, see KB 7021307.

Secure vs. Non-Secure Ports

The ports used by VHI are secure. If you need to connect to these JMX/RMI configuration services with a non-secure client (not recommended), you can enable non-secure ports by editing conf/container.properties for the server in question.

The property rmi.port sets the base port for non-secure connections to the service. It is set to 0 (disabled) by default.

The property rmi.export.port sets the port that non-secure clients call back on to use the service. It can be set to 0, to tell VHI to use an arbitrarily assigned port at runtime, or you may choose a fixed port.

Save your changes to container.properties and restart the service.

Related:

  • No Related Posts

Untitled

Management Server, Session Server and Host Emulator use JMX/RMI for configuration and management. By default, these components use specific, documented ports. Management server uses 33000-33001; Session Server uses 35000-35001; Host Emulator uses 36000-36001.

Changing RMI/JMX Port Numbers

To change Management Server RMI and JMX ports, see KB 7021327 or documentation. To change Session Server RMI/JMX ports, see KB 7021307.

Secure vs. Non-Secure Ports

The ports used by VHI are secure. If you need to connect to these JMX/RMI configuration services with a non-secure client (not recommended), you can enable non-secure ports by editing conf/container.properties for the server in question.

The property rmi.port sets the base port for non-secure connections to the service. It is set to 0 (disabled) by default.

The property rmi.export.port sets the port that non-secure clients call back on to use the service. It can be set to 0, to tell VHI to use an arbitrarily assigned port at runtime, or you may choose a fixed port.

Save your changes to container.properties and restart the service.

Related:

  • No Related Posts

Untitled

Management Server, Session Server and Host Emulator use JMX/RMI for configuration and management. By default, these components use specific, documented ports. Management server uses 33000-33001; Session Server uses 35000-35001; Host Emulator uses 36000-36001.

Changing RMI/JMX Port Numbers

To change Management Server RMI and JMX ports, see KB 7021327 or documentation. To change Session Server RMI/JMX ports, see KB 7021307.

Secure vs. Non-Secure Ports

The ports used by VHI are secure. If you need to connect to these JMX/RMI configuration services with a non-secure client (not recommended), you can enable non-secure ports by editing conf/container.properties for the server in question.

The property rmi.port sets the base port for non-secure connections to the service. It is set to 0 (disabled) by default.

The property rmi.export.port sets the port that non-secure clients call back on to use the service. It can be set to 0, to tell VHI to use an arbitrarily assigned port at runtime, or you may choose a fixed port.

Save your changes to container.properties and restart the service.

Related:

  • No Related Posts

Untitled

Management Server, Session Server and Host Emulator use JMX/RMI for configuration and management. By default, these components use specific, documented ports. Management server uses 33000-33001; Session Server uses 35000-35001; Host Emulator uses 36000-36001.

Changing RMI/JMX Port Numbers

To change Management Server RMI and JMX ports, see KB 7021327 or documentation. To change Session Server RMI/JMX ports, see KB 7021307.

Secure vs. Non-Secure Ports

The ports used by VHI are secure. If you need to connect to these JMX/RMI configuration services with a non-secure client (not recommended), you can enable non-secure ports by editing conf/container.properties for the server in question.

The property rmi.port sets the base port for non-secure connections to the service. It is set to 0 (disabled) by default.

The property rmi.export.port sets the port that non-secure clients call back on to use the service. It can be set to 0, to tell VHI to use an arbitrarily assigned port at runtime, or you may choose a fixed port.

Save your changes to container.properties and restart the service.

Related:

  • No Related Posts

Untitled

Management Server, Session Server and Host Emulator use JMX/RMI for configuration and management. By default, these components use specific, documented ports. Management server uses 33000-33001; Session Server uses 35000-35001; Host Emulator uses 36000-36001.

Changing RMI/JMX Port Numbers

To change Management Server RMI and JMX ports, see KB 7021327 or documentation. To change Session Server RMI/JMX ports, see KB 7021307.

Secure vs. Non-Secure Ports

The ports used by VHI are secure. If you need to connect to these JMX/RMI configuration services with a non-secure client (not recommended), you can enable non-secure ports by editing conf/container.properties for the server in question.

The property rmi.port sets the base port for non-secure connections to the service. It is set to 0 (disabled) by default.

The property rmi.export.port sets the port that non-secure clients call back on to use the service. It can be set to 0, to tell VHI to use an arbitrarily assigned port at runtime, or you may choose a fixed port.

Save your changes to container.properties and restart the service.

Related:

  • No Related Posts

Untitled

Management Server, Session Server and Host Emulator use JMX/RMI for configuration and management. By default, these components use specific, documented ports. Management server uses 33000-33001; Session Server uses 35000-35001; Host Emulator uses 36000-36001.

Changing RMI/JMX Port Numbers

To change Management Server RMI and JMX ports, see KB 7021327 or documentation. To change Session Server RMI/JMX ports, see KB 7021307.

Secure vs. Non-Secure Ports

The ports used by VHI are secure. If you need to connect to these JMX/RMI configuration services with a non-secure client (not recommended), you can enable non-secure ports by editing conf/container.properties for the server in question.

The property rmi.port sets the base port for non-secure connections to the service. It is set to 0 (disabled) by default.

The property rmi.export.port sets the port that non-secure clients call back on to use the service. It can be set to 0, to tell VHI to use an arbitrarily assigned port at runtime, or you may choose a fixed port.

Save your changes to container.properties and restart the service.

Related:

  • No Related Posts