Installing the AE - UNIX

The following steps will help you install the Automation Engine on UNIX.

Notes:

• The Automation Engine for UNIX is available for different platforms; a three-figure code is supplied for each supported UNIX platform. The codes are the same as for agents. In this document, the specific code is replaced by the characters "???". This document describes the installation of the Automation Engine for Oracle and DB2 databases. Specific differences are described in the individual processing steps. MS SQL Server is not supported.

• It is best to install the Automation Engine in a separate directory (such as /opt/automic/server).

Requirements

• Information security services, such as the TLS implementation of the ServiceManager, require features provided by the CAPKI package. You need to install CAPKI on all computers in which the Automation Engine Server Processes or the ServiceManager and any of its clients will run. For more information, see CAPKI - Securing the ServiceManager, Server Processes and ServiceManager.

• After installation, rebooting the UNIX System is NOT necessary.

• Own UNIX user ID for the Automation Engine (default: uc4, Home = /opt/uc4).

• For Solaris: The most current patch cluster for Sun OS has been installed.

Important! Adhere to the note that describes processes on AIX. For more information, see AIX Processes Abort Due to Lack of Memory.

When using an Oracle Database

• Functioning Oracle installation (access to the database must be possible)
• User ID for the Oracle database

When using a DB2 Database

• Functioning DB2 installation
• User ID for the DB2 database
• Check or assign authorizations:
  Open the Control Center and select the right host. Select the database for AE and select User and Group objects.Selecting User lists all users in the window on the right. Use the context menu to open the authorization window of the required user.
  At least the following options should be activated in the Database tab:
• Connect database
• Create tables
• Create packages
• Create schemas implicitly.
• The LANG variable of the user who starts the Automation Engine should be identical to the variable DB2CODEPAGE in order to avoid problems at Server start.

Install the AE

Oracle Databases

1. Log on as AE.
2. Create a new directory: /opt/automic/server.
3. Transfer the ucs???.tar.gz file from /cdrom/cdrom0/<version>/AutomationEngine/unix/<platform> with ftp (binary) to the created directory.
4. Unpack the tar file using one of the following commands:
gzip -d ucs???.tar.gz
gunzip ucs???.tar.gz
tar xvf ucs???.tar
5. Set the environment variables in $HOME/.profile  if the Automation Engine does not run on the same computer as the utilities. For more information, see Installing the Utilities - UNIX.
6. Rename the ucsrv.ori.ini file to ucsrv.ini:mv ucsrv.ori.ini ucsrv.ini
7. Adjust the INI file of the Automation Engine to your system environment ,see Automation Engine. The following list shows the INI file entries which must be adjusted in all cases. All other parameters can be configured as needed.
• Name of the AE system (system= )
• Activate the SNMP connection (snmp= ) if used.
• Port number of the primary work process (pwpport= )
  As of version 12.3, the assignment of process numbers has changed, see Types of Server Processes.
• Connection for the database (SQLDRIVERCONNECT= )
  
8. Remove the AE IMAGE:
   umount /cdrom or eject cdrom
9. Check the libraries:

   • AIX:

     1. Check the Oracle library libclntst*.a.
     2. Library check:
        dump -X64 -H ucsrvcp > wk.txt (use a blank after "dump").
     3. Open the created file with a text editor (sed or vi). Verify that all libraries were found.
     4. Repeat the above procedure with ucuoci.a and ucsrvwp. Some missing entries might be reported that refer to the file ucuoci.a, because it is a library instead of a main program. If these messages refer to the libraries ucuoci.a, libzu00132.a and libucudb32.a, they can be disregarded. If an entry cannot be found in a different library (Oracle, for example), this is an error.

   • HP-UX:

     1. Check the Oracle library libclntsh.so.*.0.
     2. Library check:
        ldd -r ucsrvcp > wk.txt
        The option -s can be used instead of -r for ldd.
     3. Open the created file with a text editor (sed or vi). Verify that all libraries were found.
     4. Repeat the above procedure with ucuoci.sl and ucsrvwp. Some missing entries might be reported that refer to the file ucuoci.sl, because it is a library instead of a main program. If these messages refer to the libraries ucuoci.sl, libzu00132.sl, or libucudb32.sl, they can be disregarded. If an entry cannot be found in a different library (Oracle, for example), this is an error.

   • Linux, Solaris and zLinux:

     1. Check the Oracle library libclntsh.so.*.0.
     2. Library check:
        ldd -r ucsrvcp > wk.txt
        The option -s can be used instead of -r for ldd.
     3. Open this file with a text editor (sed or vi). Verify that all libraries were found.
     4. Repeat the above procedure with ucuoci.so and ucsrvwp. Some missing entries might be reported that refer to the file ucuoci.so, because it is a library. If these messages refer to the libraries ucuoci.so, libzu00132.so, or libucudb32.so, they can be disregarded. If an entry cannot be found in a different library (Oracle, for example), this is an error.

     For more information, see Preparing the AE Database - Oracle).

DB2 Databases

1. Log on as "AE".
2. Create a new directory: /opt/automic/server.
3. Transfer the ucs???.tar.gz file from /cdrom/cdrom0/<version>/AutomationEngine/unix/<platform> with ftp (binary) to the created directory.
4. Unpack the transferred TAR file:
   gzip -d ucs???.tar.gz
   gunzip ucs???.tar.gz
   tar xvf ucs???.tar
5. Set the environment variables in $HOME/.profile if the Automation Engine does not run on the same computer as the utilities. For more information, see Installing the Utilities - UNIX.
6. Rename the file ucsrv.ori.ini to ucsrv.ini:
   mv ucsrv.ori.ini ucsrv.ini
7. Adjust the INI file of the Automation Engine to your system environment. The following list shows the INI file entries which must be adjusted in all cases. All other parameters can be configured as needed. For more information, see Automation Engine.
• Name of the AE system (system= )
• Activate the SNMP connection (snmp= ) if used.
• Port number of the primary work process (pwpport= )
• Assignment of communication processes and port numbers (cp1= ... cpn= )
• Assignment of work processes and port numbers (wp1= ... wpn= )
• Connection for the database (SQLDRIVERCONNECT= )
8. Remove the AE IMAGE:
   umount /cdrom or eject cdrom
9. Check the libraries:

   • AIX:

     1. AE uses $DB2DIR/lib/libdb2.a.
     2. Library check:
        dump -H ucsrvcp > wk.txt
     3. Open the created file with a text editor (sed or vi). Verify that all libraries were found.
     4. Repeat the above procedure with ucucli.so and ucsrvwp. Some missing entries might be reported that refer to the file ucucli.so, because it is a library instead of a main program. If these messages refer to the libraries ucucli.a, libzu00132.a, or libucudb32.a, they can be disregarded. If an entry cannot be found in a different library (DB2, for example), this is an error.

   • HP-UX:

     1. AE uses $DB2DIR/lib/libdb2.sl.
     2. Library check:
        ldd -r ucsrvcp > wk.txt
        The option -s can be used instead of -r for ldd
     3. Open this file with a text editor (sed or vi). Verify that all libraries were found.
     4. Repeat the above procedure with ucucli.so and ucsrvwp. Some missing entries might be reported that refer to the file ucucli.so, because it is a library instead of a main program. If these messages refer to the libraries ucucli.sl, libzu00132.sl, or libucudb32.sl, they can be disregarded. If an entry cannot be found in a different library (DB2, for example), this is an error.

   • Linux, Solaris and zLinux:

     1. AE uses $DB2DIR/lib/libdb2.so.
     2. Library check:
        ldd -r ucsrvcp > wk.txt
        The option -s can be used instead of -r for ldd
     3. Open the created file with a text editor (sed or vi). Verify that all libraries were found.
     4. Repeat the above procedure with ucucli.so and ucsrvwp. Some missing entries might be reported that refer to the file ucuoci.so, because it is a library instead of a main program. If these messages refer to the libraries ucucli.so, libzu00132.so, or libucudb32.so, they can be disregarded. If an entry cannot be found in a different library (DB2, for example), this is an error.

Install the AE SNMP Subagent (Optional)

(Server computer). You may want to install the AE SNMP subagent to monitor the various conditions which occur within an AE system (e.g. availability of the Automation Engine and agents, active notifications or blocking tasks). For more information, see Installing the Automation Engine SNMP Subagent (UNIX).

Start the Automation Engine

Manually start the Automation Engine for a test. (Server computer).

1. Log on with the AE User ID.

2. Change to the installation directory of the executable programs:
   cd $UC4/bin

3. Start the communication process in the background:
   ./ucsrvcp &

4. Start the work process in the background:
   ./ucsrvwp &

5. Verify that the Automation Engine is running:
   ps -ef|grep ucsrv or ps -fu uc4

6. It should now be possible to log on to the active Automation Engine with an AWI. The relevant information about the running Automation Engine is available in the Administration perspective.

Shut Down the Automation Engine

(Server computer). Use the ServiceManager to start and end server processes. For more information, see ServiceManager and Start Parameters - ServiceManager.

Shutdown

• Find out the Process ID pid:ps -ef|grep ucsrv

• End a server process:kill -TERM pid

Cancel

• Find out the Process ID pid:

• End a server process:kill -KILL pid

Possible Issues

At program start:

• Automation Engine ends when starting up:
  Activate traces (the database trace is the most important).

Missing libraries or other errors are best found by starting the Automation Engine using:
truss 2>truss.out -f ucsrvcp
The resulting file, truss.out, contains all system calls of the Automation Engine and all attempts to load shared objects.

If a library is missing, the problem can be that it exists in the system, but its path has not been specified in the environment variable (LIBPATH, SHLIB_PATH or LD_LIBRARY_PATH). Search the library as "root" by using:
find / -name 'library' -print
(wildcard characters are allowed).
Add the located path to the environment variable. If the library cannot be found, it has not been installed on this system or it has been deleted. Search the library to check whether it is available:
AIX, Linux, Solaris and zLinux: /var/sadm/install/contents
HP-UX: /var/adm/sw/ sw install.log and /var/adm/sw/ sw remove.log

• If it cannot be found here, it has been deleted. The names of the packages in which the libraries are available are found at the end of the relevant lines. The best solution in this case is to install the package again.
• Automation Engine drags and/or hangs.
  Usetruss -f -p pid 2>&1 | tee -a truss.out
  to trace the system calls of a running process. "tee" makes the output available on the screen and in the truss.out file.
• Remove <CR> (^M) from the text files:
  vi Text file 
  %s/<Ctrl-V><Ctrl-M>$//g
  :wq!

Next step:

• Installing the ServiceManager (recommended)

• Setting Up a Distributed Server Environment if you are using more than one server

• Installing the JWP