Hi there AppWorks fans,
Welcome to a new installment of AppWorks tips.
This guide will help you installing ‘Cordys Administration Repository Server’ (CARS) on the TomEE and PostgreSQL supported CentOS VM image. AppWorks requires a system to store information about all kind of created objects by the system or by the user. CARS in the supported and required system to store all this information.
This post is part of the series for ‘AppWorks installation in 10 great steps’.
This is the list of ingredients we are going to use:
- The already installed ‘Oracle Virtual Box’ software from the previous post
- Our supported CentOS VM image from the previous posts
- OpenText Appworks Platform (will be downloaded from OpenText support)
- Includes the OpenText documentation
- MobaXterm (X server and SSH client). Downloaded from mobatek.net
Let get right into it…
First things first…That will be downloading the correct software package from the OpenText support site on your local machine. So, login to OpenText support
In the top bar go to ‘Resources’ > ‘Downloads’ and start looking for ‘AppWorks’. You will get 3 results:
- AppWorks (This is the full suite. The platform incl. the OpenTextDirectoryServices installation files)
- AppWorks Gateway (The software from where you can host your created AppWorks solutions)
- AppWorks Platform (This is the one we need…only the platform without the OTDS files)
This is the direct link
From here you can download the file ‘opentext-appworks-platform-16.6-linux.zip’. Extract it to your local machine and upload it to the VM with WinSCP or MobaXTerm using the already available ‘otadmin’ administrator.
Before we start the installation, we will do some pre-checks and pre-setup
Get yourself the installation PDF ‘AppWorks Platform 16.6 Installation Guide for Linux’ and open it.
- Make sure to meet the system requirements as mentioned in chapter 2. You should be fine on a laptop with 16Gb of memory, 4 cores CPU and 320Gb SSD.
- Meet the checklist on chapter 3.
- We have the ‘otadmin’ user as our administrator account.
- The server has a Fully Qualified Domain Name like: appworks.mydomain.com. Check this with
- Correct Java version is available:
java -version. Should be fine if you followed the ‘Java installation…’ post on this series.
- Correct database version and it’s running:
sudo -u postgres psql. Should be fine if you followed the ‘PostgreSQL installation…’ post on this series.
- Correct TomEE version and it’s running:
ps aux | grep tomee. Should be fine if you followed the ‘TomEE installation…’ post on this series.
It’s fine that TomEE is running on post 8080. The documentation is telling you to change it to post 81, but the first 1024 ports on Linux are reserved to the ‘root’ account
Now let’s get ready to rumble with the installation of AppWorks…Finally! 😊
For this one we really need to make connection with MobaXterm because this tool has a build in X-server that is needed to run a GUI from an installer. You can test this by running the
xclock command that will give you a small clock app:
Make sure the send it to the correct DISPLAY variable:
The IP can be found on top of your SSH session
Also this can be done to enable a GUI to your X11 Server:
sudo vi sshd_config
- Uncomment and update line with in
- Save and close with
- Restart sshd service:
systemctl restart sshd
- Login again, and start an application
- Check for an xauth entry:
- Copy the Xauthority to ‘root’ to make it also work for sudo commands:
sudo cp ~/.Xauthority /root/
Now you go to your uploaded installation files:
And update the execution option in the .bin files
chmod +x OpenText_CARS_2.6.bin and
chmod +x OpenText_AppWorks_Platform_16.6.bin
And now you are really, really ready to start with the installation of … No, first we install the required CARS:
Accept the license and hit ‘Next’
Leave the default instance name and click ‘Next’
Leave the default folder location and click ‘Next’
Again…Leave the basic setting and hit ‘Next’…Never been so easy! 😊
Leave the username as is and provide it with a password for example ‘admin’. Hit ‘Next’
Hit the bright and shining ‘Install’ button to let the magic start doing its thing…
And hit ‘Done’ to finalize and to get back to your terminal session.
To see what was done to the system check the log files:
DATE is the date of your installation!
To see if CARS is running fine:
ps aux | grep cars
root 4883 0.0 0.1 499372 10284 ? Ssl 10:59 0:00 /opt/opentext/cars/defaultInst/sbin/slapd -f /opt/opentext/cars/defaultInst/sbin/slapd.conf -h ldaps://WIN-5SKKMBURVO7.mydomain.com:6366
To stop and start CARS you can use these commands:
/etc/init.d/cars-slapddefaultInst stop or
systemctl stop cars-slapddefaultInst.service
/etc/init.d/cars-slapddefaultInst start or
systemctl start cars-slapddefaultInst.service
The status call can be done with
systemctl status cars-slapddefaultInst.service
For some extra logging you need to pass extra parameters (
-d -1) to the service startup:
sudo vi /etc/init.d/cars-slapddefaultInst
OPTIONS="-f /opt/opentext/cars/defaultInst/sbin/slapd.conf -h ldaps://WIN-5SKKMBURVO7.mydomain.com:6366 -d -1"
Reload the deamon
systemctl daemon-reload and restart CARS.
The debug logging can then be monitored with
tail -f /opt/opentext/cars/defaultInst/sbin/openldap.log
And that is a ‘DONE’ for the first step on the AppWorks installation itself. Great stuff and you see how smooth it went. Have a nice day and we’ll continue our journey with the series of ‘AppWorks installation in 10 great steps’. The next step in the installation of AppWorks itself.