Installing the Automation Engine

Installing the Automation Engine

Installing the Automation Engine for Windows

---

Installing the Automation Engine for UNIX

This document guides you through the new installation of a Automation Engine for UNIX.

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 and are described in the terminology. 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.

Automic strongly recommends installing the Automation Engine in a separate directory (such as /opt/uc4/server).

Requirements

General:

• Root authorization during the installation. Not required for operating the Automation Engine.
• After installation, rebooting the UNIX System is NOT necessary.
• Own UNIX user ID for the Automation Engine (default: uc4, Home = /opt/uc4, Shell: ksh). The shell is only necessary during installation.
• For Solaris: The most current patch cluster for Sun OS has been installed.
•  The file syntax.bin must be stored in the same directory as the INI file.
•  Adhere to the note that describes processes on AIX.
•  Keep in mind that the size of Core files on AIX must be extended.

When using an Oracle Database:

• Functioning Oracle installation (sqlplus access to the databaseA database is an organized collection of data including relevant data structures. 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 click "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.

Supplied Files

Data for the Automation Engine for UNIX is supplied in compressed form. The relevant tar file can be found in one of the appropriate UNIX platform subdirectories: IMAGE:AUTOMATIONENGINE\UNIX\.
UCS???.tar.gz ( Automation Engine files).

Procedure

	1.	Installing the Automation Engine

• Server computer used with an Oracle database
• Log on as "AE".
• Create the directory /opt/uc4/server.
• Transfer file ucs???.tar.gz from /cdrom/cdrom0/<version>/AutomationEngine/unix/<platform> with ftp (binary) to the created directory.
• Unpack the tar file using one of the following commands:
  gzip -d ucs???.tar.gz
  gunzip ucs???.tar.gz
  tar xvf ucs???.tar
•  Set the environment variables in $HOME/.profile  if the Automation Engine does not run on the same computer as the utilities. Further details, including an example, are available in the  installation guide for the utilities.
• Rename the file ucsrv.ori.ini to ucsrv.ini:
  mv ucsrv.ori.ini ucsrv.ini
• Adjust the INI file ucsrv.ini 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.
• 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= )
• Remove the AE IMAGE:
  umount /cdrom or eject cdrom
• Check the libraries:
  AIX:
  

• Check the Oracle library libclntst9.a (see setting up an Oracle database).
• Library check:
  dump -H ucsrvcp > wk.txt (use a blank after "dump").
• Open the created file with a text editor (sed or vi). Verify that all libraries were found.
• 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:

• Check the Oracle library libclntsh.so.9.0 (see Setting up an Oracle database).
• Library check:
  ldd -r ucsrvcp > wk.txt
  The option -s can be used instead of -r for ldd.
• Open the created file with a text editor (sed or vi). Verify that all libraries were found.
• 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:

• Check the Oracle library libclntsh.so.9.0 (see Setting up an Oracle database).
• Library check:
  ldd -r ucsrvcp > wk.txt
  The option -s can be used instead of -r for ldd.
• Open this file with a text editor (sed or vi). Verify that all libraries were found.
• 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.

• Server computer used with a DB2 database
• Log on as "AE."
• Create the directory /opt/uc4/server.
• Transfer the file ucs???.tar.gz from /cdrom/cdrom0/<version>/AutomationEngine/unix/<platform> with ftp (binary) to the created directory.
• Unpack the transferred TAR file:
  gzip -d ucs???.tar.gz
  gunzip ucs???.tar.gz
  tar xvf ucs???.tar
•  Set the environment variables in $HOME/.profile if the Automation Engine does not run on the same computer as the utilities. More details, including an example, are available in the installation guide for the utilities.
• Rename the file ucsrv.ori.ini to ucsrv.ini:
  mv ucsrv.ori.ini ucsrv.ini
• Adjust the INI file ucsrv.ini 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.
• 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= )
• Remove the AE IMAGE:
  umount /cdrom or eject cdrom
• DB2 library check:

AIX:

• AE uses $DB2DIR/lib/libdb2.a.
• Library check:
  dump -H ucsrvcp > wk.txt
• Open the created file with a text editor (sed or vi). Verify that all libraries were found.
• 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:

• AE uses $DB2DIR/lib/libdb2.sl.
• Library check:
  ldd -r ucsrvcp > wk.txt
  The option -s can be used instead of -r for ldd
• Open this file with a text editor (sed or vi). Verify that all libraries were found.
• 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:

• AE uses $DB2DIR/lib/libdb2.so.
• Library check:
  ldd -r ucsrvcp > wk.txt
  The option -s can be used instead of -r for ldd
• Open the created file with a text editor (sed or vi). Verify that all libraries were found.
• 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.

	2.	Installing the AE SNMP subagent (optional)

• Server computer
• Install the AE SNMP subagent if you intend to use its functions.

	3.	Starting the Automation Engine

Manually start the Automation Engine for a test.

• Server computer
• Log on with the AE User ID.
• Change to the installation directory of the executable programs:
  cd $UC4/bin
• Start the communication process in the background:
  ./ucsrvcp &
• Start the work process in the background:
  ./ucsrvwp &
• Verify that the Automation Engine is running:
  ps -ef|grep ucsrv or ps -fu uc4
• It should now be possible to log on to the active Automation Engine with a UserInterface. The relevant information about the running Automation Engine is available in the System Overview.

	4.	Shutting down the Automation Engine

• Server computer

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

Use the ServiceManager to start and end server processes.

Possible Problems

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.
  Use
  truss -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 file truss.out.
• Remove <CR> (^M) from the text files:
  vi Text file 
  %s/<Ctrl-V><Ctrl-M>$//g
  :wq!

See also:

Number of Server Processes
Installing the AE SNMP Subagent (UNIX)