System Administration Guide
Connecting to Remote Servers
You can control remote instances from a Telnet session, from the
submenu on the InterSystems IRIS™ launcher on Windows, or from a URI generated from the web server and instance information.
To use the utilities on the
submenu for a remote instance:
Click the InterSystems IRIS launcher and point to
Point to a launcher utility and then click the server name.
You may also connect to a remote instance of InterSystems IRIS from a Telnet session:
Click the InterSystems IRIS launcher and point to
, connect to the remote server, and log on to the InterSystems IRIS system with your username and password. Alternatively, if the server is on the preferred server list, point to
and then click the server name.
You can remotely log into an InterSystems IRIS instance on any supported platform from a terminal running on a PC or from any workstation client capable of running Telnet. This client may have only utilities and not an InterSystems IRIS server instance. The version of InterSystems IRIS on the client machine in most cases, must be the same or a later version of the InterSystems IRIS system it manages.
On the macOS platform you can also use SSH
from a command prompt on Windows to connect to your macOS machine and then connect with the following command:
sudo /sbin/service telnet start
You can also use Web Server Pages (CSP) with a remote web server. This can be used to manage an InterSystems IRIS instance using the Management Portal.
When connecting to the
choices on the
menu, you can bookmark the generated URIs and return to these pages on your web server as long as the remote instance is running.
If you are using the Internet Explorer web browser you may need to adjust the Local intranet security settings to properly connect to remote servers.
Define a Remote Server Connection
To use the InterSystems IRIS launcher utilities or other InterSystems IRIS applications on a remote server, the server must be on the connection list in the InterSystems IRIS Server Manager. This is a list of remote servers you have previously defined to which you can quickly connect. A remote server is defined with an IP address for a unique server and a TCP port, which is an instance of InterSystems IRIS on that server.
The InterSystems IRIS superserver must be running on the remote machine and its port must be open on your firewall to use the InterSystems IRIS launcher utilities on that system.
For security reasons, username and password are not stored with the remote connection information.
To define the remote server:
From the InterSystems IRIS launcher menu, point to
, and click
to open the InterSystems IRIS Server Manager. (On Windows systems, you must have Administrator privileges to take this step.)
Fill in the fields as described in the following table and click OK
. Each field is required unless otherwise indicated.
Add Connection Input Fields
||A descriptive phrase that identifies the server; it is what appears as a selection in the InterSystems IRIS launcher.
||The IP address, host name (if you have a DNS server) or the fully qualified domain name (FQDN) of the remote server. InterSystems IRIS accepts any legitimate name reference for the remote server.
||The port number of the superserver. The default port number is 1972.
||The port number of the telnet connection. The default port number is 23.
|Web Server IP Address
||Optional The IP address of the web server you wish to use to manage this InterSystems IRIS instance. Defaults to IP Address if not specified. See Using Optional Server Fields for more information.
|Web Server Port
||The port number of the web server. The default port number is 57772.
|CSP Server Instance
||Optional The InterSystems IRIS instance name to which you want to connect if you are configuring one web server to connect to multiple InterSystems IRIS instances. See Using Optional Server Fields for more information.
||Optional A description of the remote server.
|Connection Security Level
||For Kerberos 1 only. Choose either Kerberos, Kerberos with Packet Integrity, or Kerberos with Encryption.
|Windows InterSystems IRIS Telnet Server
||For Kerberos 1 only. Select this check box if you are defining a connection to a Windows server.
|Service Principal Name
||For Kerberos 1 only. This field is pre-filled with the recommended service principal name format cache/<FQHN> (FQHN is the fully qualified host name) for the IP address you enter.
Using Optional Server Fields
Web Server IP Address
If you plan to use a web server that exists on a separate machine from the InterSystems IRIS instance you are managing, enter the IP address of the web server machine in this field. Defaults to IP Address
if not specified.
CSP Server Instance
If you are configuring one web server to connect to multiple InterSystems IRIS instances, enter the InterSystems IRIS instance name to which you want to connect in the CSP Server Instance
For example, if you have an IIS web server installed on a Windows machine and you also install two instances of InterSystems IRIS, cache1
, by default you manage each instance with its own private Apache web server that is installed as part of InterSystems IRIS.
However, you can also manage both instances from the public IIS web server by changing the Web Server Port
by default for IIS) and specifying cache1
in the CSP Server Instance
field when creating a server definition for each instance. This automatically creates virtual directories /cache1
on the public web server that point to the corresponding InterSystems IRIS instances.
When you enter a value in the CSP Server Instance
field and select the Management Portal on the launcher for this server, the URI is formed as follows:
http://<web srvr addr>:<web srvr port>/<csp srvr inst>/csp/sys/UtilHome.csp
This places the instance name before the /csp/sys/UtilHome.csp
portion of the URI and generates the following URIs for the two instances in the example.
Advanced Web Server Configuration
For some InterSystems IRIS features to function properly on a remote connection, you must configure some additional web server settings on the remote instance.