Ports Used by Verastream Host Integrator 7.x

  • 7021229
  • 17-Jun-2010
  • 02-Mar-2018

Environment

Verastream Host Integrator version 7.0 or higher

Situation

This technical note lists the ports that are used by Verastream Host Integrator (VHI) version 7.0 and higher. This information may be helpful if you are configuring your firewall to allow VHI access.

Resolution

The following table provides more details on how ports are used by the server runtime components and development tools:

Component
Listens on port number
From/Purpose
Management Server
9641 (WCP)
- Client connector, connecting via load distribution domain
- Session server (for authentication and authorization, on behalf of clients)
- Deployment tools (
activatemodel, deactivatemodel, Design Tool)
Management Server
33000 (SSL JMX)
Administrative Console (JConsole API for configuration and monitoring)
Management Server
33001 (version 7.0 non-SSL JMX)
JConsole API (Note: To enable in version 7.1, see KB 7021327)
Management Server
Arbitrary (to configure, see KB 7021327)
Administrative Console (RMI)
Management Server
8095 (HTTP)
Web Services Explorer (Jetty/JSP) web application for testing web services (version 7.1+)
Management Server
7846
Peer management servers in cluster (for data replication)
Management Server
1636 (LDAPS)
Administrative Console (for authorization profile configuration; aggregates user data from all configured directory servers)
Management Server
48620 and higher (WCP)
From client connector (connecting “via domain”) to domain server function in Management Server (one port used per load distribution domain; see also KB 7021566)
Management Server
32000
Wrapper service for JVM
Management Server
Varies (UDP)
Session server (notification of activity; to display in Administrative Console)
Session Server
9623 (WCP)
- Client connector (requesting session; connecting to requested initialized session)
- Deployment tools (
activatemodel, deactivatemodel, Design Tool)
- Management Server (configuration; monitoring; domain server requesting session)

Session Server
9680 (HTTP)
Web services clients, including Web Services Explorer (See also Changing Web Service Ports)
Session Server
9681 (HTTPS)
Web services clients, with SSL encryption (See also Changing Web Service Ports)
Session Server
35000 (SSL JMX)
Management server (web services management)
Session Server
Arbitrary (to configure, see KB 7021307)
Management server (web services management)
Session Server
9653
Script engine for model Java event handlers (on local system)
Session Server
9662
Script engine for model .NET event handlers (on local system)
Session Server
5005, or next available
External debugger for Java event handler scripting (if enabled)
Log Manager
9640 (WCP)
- Session Server (adding messages)
- Management Server (querying messages)
- LogExport utility (querying messages)

Host Emulator
9670-9671, 1096-1099
Default "master" models, for demo connections from Session Server
Host Emulator
36000 (secure JMX/RMI)
Management Server (JConsole API for configuration)
Host Emulator
36001 (JMX)
JConsole API
Design Tool (Windows Development Kit only)
5006, or next available
External debugger for Java event handler scripting
Design Tool (Windows Development Kit only)
9654 through 9661
Script manager for Java event handlers (one port per Design Tool instance)
Design Tool (Windows Development Kit only)
9663 through 9669
Script manager for .NET event handlers (one port per Design Tool instance)
Web Server (not on UNIX/Linux in pre-7.5)
8081 (HTTP)—See also KB 7021314 to disable, and KB 7021533 regarding conflicts
HTML5/Java web application projects generated in Web Builder
Web Server (additional port in version 7.5+)
8443 (HTTPS) —See also KB 7021533 regarding conflicts
HTML5 web application projects generated in Web Builder, with encrypted communications
Your hosts
23 (Telnet, default)
992 (Telnet SSL, default)
1570 (HP NS/VT, default)

Session Server
Your network monitoring system (optional)
161 UDP (SNMP)
Log Manager (notifications)
Your e-mail server (optional)
25 (SMTP, default)
Log Manager (notifications)
Your directory server (optional)
636 (LDAPS, default)
389 (LDAP, default)

Management Server (authentication requests for Administrative Console, deployment tools, and client connector)

Note: Some components may use additional ephemeral ports. When configuring Windows Firewall exceptions, in addition to specifying port numbers, it is recommended you add program C:\Program Files\Attachmate\Verastream\java\jdk<version>\bin\java.exe.

Additional Information

Basic Server Communication

The following graphic summarizes port communications with the server core runtime components.


Configuring Port Numbers

For information about changing ports used by various components, refer to the following resources:

Changing Web Service Ports

To change the ports used for web services (SOAP, and REST beginning in version 7.7):

  1. Edit the appropriate configuration file, depending on your VHI version and platform:

Version 7.1.1142 or higher: service-cfg.xml file in %VHI_ROOT%\sesssrvr\services\ws\META-INF Note: This file is created after web services are configured in Administrative Console.

Version 7.0 through 7.1.221 on Windows: service-ctx.xml file in %VHI_ROOT%\sesssrvr\services\ws\META-INF

Version 7.0 through 7.1.221 on UNIX/Linux: service-ctx.xml file in %VHI_ROOT%/lib/container/services/ws/META-INF

  1. Add or modify the appropriate value:
    Description
    Key
    Default
    SOAP HTTP
    hostPort
    9680
    SOAP HTTPS
    secureHostPort
    9681

In service-cfg.xml, add lines as displayed in red below:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties>
       <comment>com.attachmate.ws.impl.ServiceMainConfigImpl</comment>
       <entry key="hostPort">9666</entry>
       <entry key="secureHostPort">9644</entry>
</properties>

  1. After saving changes to this file, you must restart the session server service to for changes to take effect. For information on manually restarting the service, see KB 7021352.

Note: When you upgrade to a later version (hotfix or major release) in the future, the file may revert to defaults.

Legacy KB ID

This document was originally published as Attachmate Technical Note 10105.