Installing on Red Hat Enterprise Linux
Introduction
This document describes how to run Composable Agentic Platform using the Tomorrow-Software-Server-2021-noJRE-10.0.0.zip distribution for a Red Hat Enterprise Linux environment. This example is using IBM Cloud, with a virtual server instance server instance launched with a Red Hat Enterprise Linux 7.x - Minimal Install (amd64) image.
Requirements:
Red Hat Enterprise Linux 7.2 (HVM) – (RHEL)
JRE 11 or above
Tomorrow-Software-Server-2021-noJRE-10.0.0.zip (or other approved) distribution for Composable Agentic Platform
A suitable Linux terminal client and SSH connection to the server established
Root user access permissions
Useful things to know
Composable Agentic Platform requires Java v11+ JDK Runtime Environment to run so check if Java is installed and the Java running version.
The Composable Agentic Platform installation uses the open source Jetty application server.
Check Java installation and version
java –versionWill either return “command not found” when no Java installation has been installed or display the current Java installation details.
e.g., Java version details
java –version
openjdk version "1.8.0_65"
OpenJDK Runtime Environment (build 1.8.0_65-b17)
OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)Install or modify Java
If you have an older Java version, then you’ll need to upgrade with the following Java installation commands
sudo su root
yum install java-11-openjdk-develAfter the yum installation has completed, set the default JDK to be java-11 by using this command:
update-alternatives --config java
There is 1 program that provides 'java'.
Selection Command
-----------------------------------------------
*+ 1 java-11-openjdk.x86_64 (/usr/lib/jvm/java-11-openjdk-11.0.6.10-3.el7.x86_64/bin/java)
Enter to keep the current selection[+], or type selection number: 1
If there are multiple alternatives, enter the number in front of the java-11 entry, and the correct Java version is now configured.
Download, upload, unzip, run.
Download the Composable Agentic Platform distribution zip file and upload to the RHEL instance.
There are many ways to upload a file over to a Linux environment. Here is an example using the secure copy command “scp”.
A temporary directory could also be used or created to upload the file e.g. /tmp and then move the package to the correct location.
Example:
scp -i [YOUR KEY NAME] Tomorrow-Software-Server-2021-noJRE-10.0.0.zip root@[YOUR SERVER NAME]:~
Tomorrow-Software-Server-2021-noJRE-10.0.0.zip 12% 28MB 88.1KB/s 37:36 ETAUnzip the package under the
/opt/localdirectory.
Note: root permissions may be required to create the local folder so switch to root if needed.
Unzip may need to be installed, do so using this command.
yum install unzipThen unzip to /opt/local
unzip Tomorrow-Software-Server-2021-noJRE-10.0.0.zip -d /opt/localThe unzipped contents of Tomorrow-Software-Server-10.0.0.zip will extract, then rename the directory to “Tomorrow” using “mv” command.
mv Tomorrow-Software-Server-10.0.0 Tomorrow
ls
BaseApp Certificates Demonstration Documentation Education HOME jetty9 jre Multi-Protocol server Stress Tomorrow.bat Tomorrow.command Tomorrow.sh Tryout files WinServiceNote: the location of the file named Product Reference.pdf is in the Documentation folder. This is the comprehensive document for the entire Composable Agentic Platform.
Important: Don’t refer to Product Reference.pdf until the latest updates have been applied via console updates after installation, as there may be an update available.
Copy the tomorrowstart script file to the directory where running services are located by using this command:
cp /opt/local/Tomorrow/server/bin/tomorrowstart /etc/init.d/Modify permissions to the user account to execute the scripts. The tomorrowstart and tomorrow.sh files must have read, write and execute permissions set. Switch to a root user if required to be able to change the file permissions.
chmod 755 /opt/local/Tomorrow/server/bin/tomorrow.sh
chmod 755 /etc/init.d/tomorrowstartNow add the executable script under the startup services. Run the below commands to run Composable Agentic Platform as a service. In a RHEL environment use only the chkconfig command. For example, in an Ubuntu environment the update-rc.d command can be used.
cd /etc/init.d
chkconfig --add tomorrowstartCheck tomorrowstart script as service is set correctly with the correct levels.
chkconfig tomorrowstart --list
tomorrowstart 0:off 1:off 2:on 3:on 4:on 5:on 6:offNow start the Composable Agentic Platform service.
Useful things to know before launching
When launching the console application, there may be other demo applications and a built-in proxy server that will also launch at the same time. Default ports 80 and 443 are used to run the console application, and therefore must be available before launching. To modify default ports, refer Product Reference.pdf section: Port numbers and how to change them.
Port
Use
80
HTTP port for the console, demo applications and the built-in proxy
443
HTTPS port for the console, demo applications and the built-in proxy
service tomorrowstart startThe following output example should be seen:
Starting Jetty: 2020-04-17 05:40:35.142:INFO::main: Logging initialized @826ms to org.eclipse.jetty.util.log.StdErrLog
2020-04-17 05:40:35.768:INFO::main: Console stderr/stdout captured to /opt/local/Tomorrow/server/logs/stderrout-2020_04_17.log
. . . . OK Fri Apr 17 05:40:54 CDT 2020Note: To stop Composable Agentic Platform use:
service tomorrowstart stopIt is good practice to now reboot of the RHEL server to verify Composable Agentic Platform restarts as a service at startup.
rebootComposable Agentic Platform is now running as a service in RHEL.
Launch the Composable Agentic Platform console application via a compatible browser at this URL: http://[YOUR SERVER NAME]/console
Default administrator credentials:
Username: admin
Password: admin
Last updated