Install component integrators - Linux
This topic provides instructions and guidelines for installing component integrators on Linux.
For details on how to run component integrators after the installation, see Start and stop a component integrator.
Installation guidelines
When preparing to install a component integrator, take into account:
-
Component integrators require JRE/JDK 17.0.14 or later. Before installing a component integrator, make sure you have a supported version of Java on the target machine.
Version 24.3: Component integrators require JRE/JDK 11. - You can install a component integrator by running the command-line installer or using a .properties file for silent installation.
Install from command prompt on UNIX/Linux
Run the UNIX/Linux command-line installer and provide connection details for the component integrator and the server.
To install a component integrator from a command line:
-
Download and extract the appropriate installation files from the Software Licensing and Downloads portal (requires login).
-
As a user with full access rights to the installation location, run:
install-component-integrator.sh
-
Enter the path to the directory where to install the component integrator, or accept the default location:
/opt/OpenText/component-integrator
If the directory doesn't exist, confirm that you want to create it.
-
Enter the path to the directory where Java 17.0.14 is installed. This JRE/JDK will run the component integrator.
Version 24.3: Enter the path to the directory where Java 11 is installed. This JRE/JDK will run the component integrator.By default, the installer uses the JRE/JDK path defined in the JAVA_HOME system environment variable.
-
Enter the host name or IP address of the Deployment Automation server to which to connect this component integrator, for example:
serverName
-
Enter the port to use for JMS communication with the server. Default JMS port: 7918.
-
Enter a name for the component integrator.
Note: If another component integrator with the same name already exists, Deployment Automation adds a numeric suffix to the conflicting name to allow the component integrator to connect. You can then change the name in the user interface.
-
Enter the component integrator's web URL, for example:
https://my-ci.example.com
-
Enter the component integrator's HTTP(S) port. Default HTTP(S) port: 8991.
-
Specify whether the Deployment Automation server and component integrator use SSL mutual authentication (Y/N). By default, SSL mutual authentication is disabled.
-
Enter the UNIX/Linux username under which to run the component integrator.
-
Enter the UNIX/Linux group name under which to run the component integrator.
Install in silent mode on UNIX/Linux
You can install a component integrator in silent mode using a file with configuration properties.
To prepare a .properties file, edit the example.install.properties file supplied in the installation bundle.
To install a component integrator in silent mode:
- Download and extract the component integrator installation files for your platform from the Software Licensing and Downloads portal (requires login).
- In the directory with the installation files, open the example.install.properties file in a text editor.
-
Edit the following properties, and save the file:
Property Description component-integrator/java.home Enter the path to the directory where Java 17.0.14 is installed. This JRE/JDK will run the component integrator.
Version 24.3: Enter the path to the directory where Java 11 is installed. This JRE/JDK will run the component integrator.By default, the installer uses the JRE/JDK path defined in the JAVA_HOME system environment variable.
locked/component-integrator.home Enter the path to the directory where to install the component integrator.
If the directory doesn't exist, specify one to create, for example:
/opt/OpenText/component-integrator
locked/component-integrator.name Enter a name for the component integrator.
Default name: component-integrator
Note: If another component integrator with the same name already exists, Deployment Automation adds a numeric suffix to the conflicting name to allow the component integrator to connect. You can then change the name in the user interface.
locked/component-integrator.external.url Enter the component integrator's web URL, for example:
https://my-ci.example.com
locked/component-integrator.http.server.port Enter the component integrator's HTTP(S) port.
Default HTTP(S) port: 8991
locked/component-integrator.jms.remote.host Enter the host name or IP address of the Deployment Automation server to which to connect the component integrator, for example:
serverName
locked/component-integrator.jms.remote.port Enter the port to use for JMS communication with the server.
Default JMS port: 7918
locked/component-integrator.ssl.enabled.protocols By default, Deployment Automation allows the use of TLSv1.2, TLSv1.1, and TLSv1 protocols.
To improve security, you can change the defaults to allow TLSv1.3 and TLSv1.2 only:
TLSv1.3,TLSv1.2
Note: All your system components must use the same protocols.
locked/component-integrator.ssl.enabled.ciphers By default, Deployment Automation supports all SSL ciphers.
To enable only specific ciphers, enter a comma-separated list of ciphers.
locked/component-integrator.mutual_auth Specify whether the Deployment Automation server and component integrator use SSL mutual authentication (Y/N).
By default, SSL mutual authentication is disabled.
owner.user Enter the UNIX/Linux username under which to run the component integrator. owner.group Enter the UNIX/Linux group name under which to run the component integrator. -
Save the .properties file.
-
As a user with full access rights to the installation location, run:
Copy codeinstall-component-integrator-from-file.sh example.install.properties
Use the name of your .properties file instead of example.install.properties.
Upgrade component integrators
To upgrade your component integrators to the latest Deployment Automation version, see Upgrade component integrators.
Uninstall component integrators
To uninstall a component integrator, manually delete the installed files and folders. You need full access rights to the installation location.
See also: