Communication Between Synapta Services Builder Components

This table provides a simplified view of the communication protocols and ports used in interactions between components of the Synapta Services Builder with the default installation. More detailed explanation follows.

This component When communicating with Uses this protocol On this port Configured in
Designer Host Host protocol over TCP/IP Default port number is 23 for 3270, 5250, T27, and VT connections; 102 for UTS. Host connection configuration, except for UTS which is not configurable.
Designer Management server (MCS) HTTP/TCPIP 8086* Installation
Runtime engine Client interface (task interface object) RMI 6700 and a random port screen.properties
Runtime engine Host Host protocol over TCP/IP Default port number is 23 for 3270, 5250, T27, and VT connections; 102 for UTS. Session pool configuration and registered runtime configuration in management server.
Runtime engine Management server SOAP/HTTP/TCPIP 8086* Installation
Management server Runtime engine SOAP/HTTP/TCPIP 2000 agent.properties
Management server Client interface (task interface object) SOAP/HTTP/TCPIP 2000 agent.properties
Management server user interface (MCS console) Management server HTTP or HTTPS 8086* or 8447 Installation and security services

* The default installation uses the Attachmate HTTP servlet engine. If you install MCS into a different application server environment, the default port may be different. For example, with WebLogic, the default port is 7001.

Communication Between Components at Design-time

The designer communicates with the host when recording host screens and when testing tasks. In addition, the designer communicates with the management server when publishing tasks. The management server acts as a central repository for tasks.

Communication between the designer and the host is through the host port, which is different depending on the host type and communication protocol. For most host types, the port is configurable in the host connection options in the designer, and can be changed at any time. For UTS hosts, the port is not configurable. For more information about configuring host connections, see Connecting to a Host, Overview.

Communication between the designer and the management server is HTTP over TCP/IP. Although you can change the server to which you publish, the HTTP port used for the management server is configurable only at installation time.

The MCS service agent is not used in communication between the designer and MCS.

Communication Between Components at Run-time

At runtime, communication is between the client interface and the runtime engine, and between the runtime engine and the host. In addition, the runtime engine communicates with the management server through the MCS agent. The management server downloads task interface objects and NavMaps to the runtime server, manages configuration of the runtime server's session pools, and monitors events.

The client application makes reference to the downloaded task interface objects (such as Web services, XML files, or beans) to call for tasks and access data on the host. NavMaps provide the necessary host navigation information and task inputs and outputs.

Communication between the runtime engine and the client application is through an RMI registry, which by default uses port 6700. The runtime service creates an object called Configuration Server. By default, this object reports the random port used for the runtime engine to the RMI registry, which then directs communication between the runtime engine and the client application through that port. Both the port used for the RMI registry and the port reported by Configuration Server are configurable in the screen.properties file.

If you run more than one instance of the runtime engine on a single computer, each instance must use a unique RMI port. If you use a firewall, you may need to specify a value for the Configuration Server port. For information about changing the values for either of these ports, see Run-time Server Properties. For information about using more than one runtime engine on a single computer, see Replicating Runtime Servers.

Communication between the runtime engine and the host is through the port used in the host connection configuration supplied by the session pool configuration. For information about updating your session pool configuration, see Modifying Session Pools.

In communication between the runtime engine and MCS, and the client interface and MCS, the runtime engine communicates through the MCS service agent. The MCS service agent is automatically installed on the runtime computer when you install the Runtime Service. MCS uses port 8086, depending on the servlet engine you use and your selections during installation. The runtime engine port is reconfigurable through the agent.properties file. The MCS port cannot be changed after installation.

Communication Between the System Administrator and the Management Server

The system administrator interacts with the management server through the MCS console to configure MCS services and runtime server pools. The MCS console can be displayed through a supported browser on the local computer or from a remote location.

Depending on your connection type, one of two ports is used. The HTTP port, by default 8086, is specified during installation and cannot be changed. The secure HTTPS port, by default 8447, is also specified at installation time but can be changed later through the MCS user interface (the MCS console). For instructions on displaying the MCS console, see Accessing the MCS Console. For instructions on changing the secure port, see Configuring Security Services.

Related Topics
Bullet Synapta Services Builder, Overview
Bullet Connecting to a Host, Overview
Bullet Run-time Server Properties
Bullet Replicating Runtime Servers
Bullet Modifying Session Pools
Bullet Accessing the MCS Console
Bullet Configuring Security Services
  Attachmate