/ Installation  

The AppWorks installation survival guide

Hi there AppWorks fans,

Welcome to a new installment of AppWorks tips.

This guide will help you installing AppWorks on the supported CentOS VM image. AppWorks requires an instance of CARS.

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 license information requested at OpenText support!
  • The already installed ‘Oracle Virtual Box’ software from the previous post
  • Our supported CentOS VM image with CARS installed from the previous posts
  • OpenText Appworks Platform (will be downloaded from OpenText support)
    • Includes the OpenText documentation
  • JDBC driver for TomEE. Downloaded from postgresql.org
  • MobaXterm (X server and SSH client). Downloaded from mobatek.net

Let get right into it…Get your license file ready!


Make the JDBC driver available for TomEE and AppWorks installation

Go to postgresql download site and download the latest version for our version 11 of Java! In this post we used: https://jdbc.postgresql.org/download/postgresql-42.2.5.jar

Once downloaded upload it to the VM with WinSCP or MobaXTerm using the already available ‘otadmin’ administrator.

In the VM we move the file to the correct TomEE location: sudo cp /home/otadmin/postgresql-42.2.5.jar /opt/tomee/latest/lib/

And restart TomEE systemctl restart tomee

To make it nicer and smoother we will update the otadmin bash_profile. So, edit the ~/.bash_profile of the ‘otadmin’ user: vi ~/.bash_profile

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi

# User specific environment and startup programs

CLASSPATH=$CLASSPATH:/opt/tomee/apache-tomee-plus-8.0.0-M2/lib/postgresql-42.2.5.jar:/opt/opentext/AppWorksPlatform/defaultInst/cordyscp.jar
export CLASSPATH

JAVA_HOME=/usr/lib/jvm/java-11-openjdk
export JAVA_HOME

PATH=$PATH:$HOME/.local/bin:$HOME/bin
export PATH

LIB_PATH=/usr/lib/jvm/java-11-openjdk/lib/server/

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$LIB_PATH::/opt/opentext/AppWorksPlatform/defaultInst/lib
export LD_LIBRARY_PATH

CATALINA_HOME=/opt/tomee/apache-tomee-plus-8.0.0-M2
export CATALINA_HOME

The two OpenText folder locations in the CLASSPATH and LD_LIBRARY_PATH are there to optimize the installation in the rest of this post!

When done reload your profile via the command: source ~/.bash_profile

Check if it’s all OK via: env | grep PATH


Before we continue our ‘AppWorks installation journey’ we first create a table space for our PostgreSQL database instance that we can use for our installation.

Let’s us first create a nice location folder and own it by the ‘postgres’ user that was created during the installation of PostgreSQL.

sudo mkdir /usr/data

sudo mkdir /usr/data/appworks_ts

sudo chown postgres /usr/data/appworks_ts/

Now enter the psql CLI: sudo -u postgres psql

And create a tablepace with this SQL statement: CREATE TABLESPACE appworks_ts LOCATION '/usr/data/appworks_ts';

To see the result, execute this query: select * from pg_tablespace;

\q to quit psql


Now the major step of this blog post series. The installation of AppWorks.

Go to your uploaded installation files: cd ~/opentext-appworks-platform-16.6-linux

And execute the magic command: sudo CATALINA_HOME=$CATALINA_HOME CLASSPATH=$CLASSPATH ./OpenText_AppWorks_Platform_16.6.bin

Graphical installers are not supported by the VM. The console mode will be used instead…You need to make sure your DISPLAY variable is correct! export DISPLAY=IP:0.0

install_appworks_001

Hit ‘Next’

install_appworks_002

Accept the license and hit ‘Next’

install_appworks_003

Accept more licenses and hit ‘Next’

install_appworks_004

CARS is already installed and running so the information should be fine. Provide the CARS password. We used for the example ‘admin’. Hit ‘Next’.

install_appworks_005

Leave as default and continue by hitting ‘Next’

install_appworks_006

Also leave as is and click ‘Next’.

Now it’s time to get a hand on your new requested license file!

How to get one is described on top of this post.

install_appworks_007

Fill in the data from your license file and click ‘Next’.

install_appworks_008

Unmark the ‘Fetch’ option and type in the license key from your local license file. Click ‘Next’

If you get error on the next screen make sure your hostname is proper FQDN and that it matches the HOST in the license file!

install_appworks_009

Leave the default folder location and click ‘Next’

install_appworks_010

If the field are not filled in already point it to the correct location and give the proper service name. Click ‘Next’

install_appworks_011

Provide a password for the sysadmin account. For example, ‘admin’ and click ‘Next’

install_appworks_012

Now make sure to fill in the correct information for the Database connection:

  • Database type: PostgreSQL (The screenshot is wrong!)
  • Server name: your FQDN
  • Default Port: 5432
  • Username: postgres
  • Password: admin (as we changed during the PostgreSQL installation post in this site)
  • Database name: appworks_db
  • Mark the ‘Create Database’ option
  • DBA username: postgres
  • DBA password: admin

Now click ‘Next’

install_appworks_013

Click ‘Next’

install_appworks_014

Point the tablespace to our own create tablespace as described before the installation started. Click ‘Next’

If you get connection errors to the database make sure the information is correct and the JDBC driver ‘postgresql-42.2.5.jar’ is available on the CLASSPATH

install_appworks_015

Also, this can happen for the table spacing. Just click ‘OK’

install_appworks_016

install_appworks_017

Give a password with the JMX admin user. For example, ‘admin’ and click ‘Next’

install_appworks_018

Almost there…The magic ‘Install’ button….Hit it like a bro!! 💪

Time for a beer…

install_appworks_019

install_appworks_020

install_appworks_021

There it is…Our well-earned ‘Done’ button!

Can take some time when the screen is gone, but it’s done…done!

To see what was done to the system check the log files:

cat /tmp/cordys_custom_log.log

cat /opt/opentext/AppWorksPlatform/defaultInst/install_log/AppWorks\ Platform\ installation.Log

cat /opt/opentext/AppWorksPlatform/defaultInst/install_log/configureapplicationserver.log

sudo cat /opt/opentext/AppWorksPlatform/defaultInst/Logs/Monitor.xml

To see if AppWorks is running fine: ps aux | grep cordys

1
tomcat    3816  2.1  2.5 3942488 234160 ?      Sl   10:27   0:23 /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.212.b04-0.el7_6.x86_64/jre/bin/java -Xrs -XX:+HeapDumpOnOutOfMemoryError -cp :/opt/opentext/AppWorksPlatform/defaultInst/cordyscp.jar:/opt/opentext/AppWorksPlatform/defaultInst/cordyscp.jar::/opt/tomee/latest/lib/postgresql-42.2.5.jar:/opt/opentext/AppWorksPlatform/defaultInst/cordyscp.jar:/opt/tomee/apache-tomee-plus-7.0.5/lib/postgresql-42.2.5.jar:/opt/opentext/AppWorksPlatform/defaultInst/cordyscp.jar:: -Dbus.xml.vm.maxsize=1024 -Xmx256M -Dfile.encoding=UTF-8 com.eibus.soap.Processor -name system#cap#cap@win-5skkmburvo7

To stop and start AppWorks you can use these commands:

/etc/init.d/wcpddefaultInst stop or systemctl stop wcpddefaultInst.service

/etc/init.d/wcpddefaultInst start or systemctl start wcpddefaultInst.service

The status call can be done with systemctl status wcpddefaultInst.service


And this again gives us a big ‘DONE’ we can be proud off. Let me know what you think of this post in the comments. And as always ‘have a good one for today’ and see you on the next installment of ‘Appworks Tips’. The final step in our series ‘AppWorks installation in 10 great steps’ is the deployment of the ‘ready packages’ from the installation.