/ Installation  

The OTDS installation survival guide

Hi there AppWorks fans,

Welcome to a new installment of AppWorks tips.

This guide will help you installing OpenText Directory Services on the supported CentOS VM image. This service will handle the authentication for the AppWorks platform.

This is the list of ingredients we are going to use:

  • Our supported CentOS VM image with AppWorks installed from the installation series in the top menu.
  • OpenText Directory Services (will be downloaded from OpenText support)
  • 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 ‘OTDS’. You will get the one result we are looking for…This is the direct link

From here you can download the file ‘OTDS-1661-LNX.tar’. Upload it to the VM with WinSCP or MobaXTerm using the already available ‘otadmin’ administrator. Then extract with tar xvf otds-1661-lnx.tar -C ~/otds-1661 when you created a new directory mkdir ~/otds-1661

Make sure you DISPLAY variable point to the correct IP export DISPLAY=IP:0.0

And make sure you have a directory available for OTDS sudo mkdir /opt/opentext/otds

Also make ‘otadmin’ the owner of it sudo chown otadmin:otadmin /opt/opentext/otds/

Then start the OTDS setup sudo ~/otds-1661/setup -l otds-installer.log -debug

  • Give an n to continue

  • Now give an e to go to the end of the agreement

  • Then give an a to accept it all

  • Give an m to modify the group name selection

    • Update it to otadmin and give an n to continue
  • And again, for the username selection. Give an m to modify

    • Update it to otadmin and give an n to continue
  • Do an m for the modification on the installation directory

    • Update the location to /opt/opentext/otds
  • Give an n to continue with the changed directory

  • We installed Tomcat. So, an n will work here.

  • It’s not (by default) a replication server. So, an n

  • Aha…there it is…the Tomcat location /opt/tomcat/apache-tomcat-8.5.43

    • And give an n to use it

    When you get an error that tomcat can’t be found you need the check the otds-installer.log in the installation directory (as passed with the -l parameter during setup)

  • Then for the LDAP administrator port hit n to keep the default 4440 port

  • Same for the LDAP communication port (1389). Give it an n to continue

  • Pass in the FQDN hostname: WIN-5SKKMBURVO7.mydomain.com (in my case!)

  • Give the OTDS administrator password. We use ‘admin’ for all users at the moments.

    • And confirm it
    • Also give an n that you know it is a weak password. Good for us!
  • Next is the import from other OTDS service. We don’t need it. So, an n

  • Then there is the final step where we can continue with a best-of-all hit in the i button

Time for coffee…

When #$&^$ hits the fan check the otds-installer.log or I also found an otdsDeploy.log: cat /opt/opentext/otds/install/otdsDeploy.log

In the end you should see something like this:


Now what…?

Let’s see if tomcat is running?

What is the OTDS logging telling me: tail -f /opt/tomcat/latest/logs/otds.log

Looks nice…


Should we try it?…Lets just do it!

Nicely rising on top of the Tomcat instance…Great stuff!


And the login with the default account ‘otadmin@otds.admin’ and password ‘admin’…

Will it happen…Will it…


Touch down!!!

Another greatly earned ‘DONE’ to complete the OTDS installation…What a day!

Enjoy it and I see you in the next post where we start to use OTDS for authentication and start pushing users to the AppWorks platform.

Ohw…And don’t forget to subscribe to get updates on the activities happening on this site.