Install Java RCS

The Java RCS is supported on the following Java versions:

Java version support
Java RCS version	Supported Java version
1.5.20.22 and earlier	Java 11 or 17
1.5.20.23 through 1.5.20.31	Java 17
1.5.20.32 and later	Java 17 or 21

Disk space, memory, and CPU requirements depend on the number of connectors you’re using and the volume of traffic through the RCS.

You can also deploy Java RCS in a Docker container.

Install a Java RCS on Unix/Linux

Download and extract the Java RCS from the Backstage download site.
Change to the openicf directory:
```
cd /path/to/openicf
```
Review the ConnectorServer.properties file in the /path/to/openicf/conf directory, and adjust it to suit your deployment. For a complete list of properties in that file, refer to RCS Properties.
- In server mode, the RCS uses a connectorserver.key property to authenticate the connection. The default value of the key is a hashed value of the string changeit. You cannot set this property directly in the configuration file. To change its value, use the command ConnectorServer.sh /setKey. This example sets the key value to Passw0rd:
  /path/to/openicf/bin/ConnectorServer.sh /setKey Passw0rd Key has been successfully updated.
  In client mode, this isn’t necessary and can be skipped. Learn more about the differences between client mode and server mode in Configure a remote connector server (RCS).
Start the Java RCS:
```
/path/to/openicf/bin/ConnectorServer.sh /run
```
By default, the RCS is now running and listening on port 8759.

Log files are available in the /path/to/openicf/logs directory.
```
ls logs/
Connector.log  ConnectorServer.log  ConnectorServerTrace.log
```
To stop the Java RCS, press CTRL+C or q in the terminal where you started the server.

Install a Java RCS on Windows

Download and extract the Java RCS from the Backstage download site.
In a Command Prompt window, change to the openicf directory:
```
C:\> cd C:\path\to\openicf
```

Review the ConnectorServer.properties file in the \path\to\openicf\conf directory, and adjust it to suit your deployment. For a complete list of properties in that file, refer to RCS Properties.

In server mode, the RCS uses a connectorserver.key property to authenticate the connection. The default value of the key is a hashed value of the string changeit. You cannot set this property directly in the configuration file. To change its value, use the ConnectorServer.bat /setKey command. This example sets the key value to Passw0rd:

c:\path\to\openicf> bin\ConnectorServer.bat /setKey Passw0rd
Key has been successfully updated.

If you use an exclamation mark (!) with the ConnectorServer.bat /setKey command, you must escape the character according to your Windows Server version:

For Windows Server 2012 R2, escape the character with double quotes:
```
ConnectorServer.bat /setKey "changeit"!""
```
For Windows Server 2016 and later, escape the character with a caret (^):
```
ConnectorServer.bat /setKey changeit^!
```

In client mode, this isn’t necessary and can be skipped. Learn more about the differences between client mode and server mode in Configure a remote connector server (RCS).

You can either run the Java RCS as a Windows service or start and stop it from the command line.

If you previously started the RCS using /run, the user account that entered the command owns the log files in openicf\logs\. When you install and start the RCS as a Windows service, the Windows service account doesn’t have write access to those log files. The service starts without error but produces no log output.

To avoid this issue, use one of the following workarounds before running /install:

Delete the openicf\logs\ directory. The RCS recreates it with the correct permissions when the service starts.
In the Windows Services management console, open the RCS service properties, click the Log On tab, and select Local System Account.

The Local System Account has broad local system privileges. For production deployments, grant the existing service account write access to openicf\logs\ instead.

To install the Java RCS as a Windows service, run the following command:
```
c:\path\to\openicf> bin\ConnectorServer.bat /install
```
If you install the RCS as a Windows service, you can use the Microsoft Services console to start, stop, and restart the service. The Java Connector Service is named OpenICFConnectorServerJava.

To uninstall the Java RCS as a Windows service, run the following command:
```
c:\path\to\openicf> bin\ConnectorServer.bat /uninstall
```
To start the Java RCS from the command line, enter the following command:
```
c:\path\to\openicf> bin\ConnectorServer.bat /run
```

The RCS is now running, and listening on port 8759, by default.

Log files are available in the \path\to\openicf\logs directory.
To stop the Java RCS, press CTRL+C.

Run Java RCS as a service

The Java RCS can run as a service on a standard systemd-based Linux distribution. Once you have configured the RCS as a service, you can stop and start the RCS using systemd.

Configure RCS as a service

Create a service file using your preferred text editor:
```
sudo vim /etc/systemd/system/rcs.service
```

Add the following content to this file, update the paths as needed, and save:

[Unit]
SourcePath=/path/to/openicf/bin
Description=Remote Connector Server (systemd init)
After=network.target
Conflicts=shutdown.target

[Service]
Type=simple
Restart=always
RestartSec=5sec
IgnoreSIGPIPE=no
KillMode=process
Environment="OPENICF_OPTS=-Xmx1024m"
ExecStart=/path/to/openicf/bin/ConnectorServer.sh /start

[Install]
WantedBy=multi-user.target

Make the new service launch on startup:
```
sudo systemctl enable rcs.service
```
Check the service is enabled:
```
systemctl is-enabled rcs.service
```
This command returns enabled or disabled as appropriate.

Use systemctl commands to manage the RCS service

Once you’ve configured RCS as a service and checked it’s enabled, use systemctl commands to manage the RCS service:

Start the service:
```
sudo systemctl start rcs.service
```
Stop the service:
```
sudo systemctl stop rcs.service
```
Restart the service:
```
sudo systemctl restart rcs.service
```
Check the service status:
```
sudo systemctl status rcs.service
```
This command returns the service state (whether the service has started or stopped as expected) and the first few entries of the RCS log file.

ICF 1.5.20.34

Install Java RCS

Install a Java RCS on Unix/Linux

Install a Java RCS on Windows

Run Java RCS as a service

Configure RCS as a service

Use systemctl commands to manage the RCS service