Utilities

Utilities

Installing Utilities (Windows)

---

Installing Utilities (UNIX)

This document guides you through the new installation of the utilities for UNIX.

A three-figure code has been supplied for each supported UNIX platform because the utilities for UNIX are available for different platforms. The codes are described in the Terminology. This document replaces the specific codes with the characters "???."

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

Requirements

• Valid user ID for installation (UC4)

Supplied Files

Utility files are supplied in compressed tar-file format (util???.tar.gz), and can be found in subdirectories of IMAGE:UTILITIES\UNIX. The subdirectory names indicate the supported platforms.

*.sh: normal utility start
without file ending: programs for batch call

As of version 8.0, the file names of all utilities have been changed to lowercase letters. For compatibility reasons, binary links are supplied for UNIX utilities of version 8.0. They link the program calls from old file names to the new ones. These links are only supplied in version 8.0 and no longer appear in later versions.

Procedure

	1.	Installing the Java Runtime Environment (JRE)

This installation step can be ignored if the required version of JRE is already installed.

• Admin computer
• Use the following command to check which version of the Java Virtual Machine (VM) is currently installed:

java -version

If several JRE or Java SDK versions are installed on your computer, make sure that the specified directories are in the proper order in the settings of %PATH% and $PATH. The Java Runtime Environment that is found first in the list of directories is used.

• Download the required Java Runtime Environment from http://java.sun.com and install it.

	2.	Unpacking theTAR file and setting up the system environment

• Admin computer
• Copy the TAR file util???.tar.gz to a directory (such as UC4/utility) via FTP.
• Log on using the user ID UC4.
• Switch to the directory used for the utilities:
  cd utility
• Unpack the tar file:
  gzip -d util???.tar.gz or gunzip util???.tar.gz
  tar xvfo util???.tar
• The files are created in their corresponding directories as the file is unpacked. The tar file can be deleted after unpacking.
•  Pay special attention to tar messages, which can result from different owners, and verify that all files are correctly unpacked.
• Check whether all files show the correct owner and group entries. AE must be the owner and the group must correspond to the identification "UC4. Modifications can only be made by a privileged user (such as root).
  chown UC4 * changes the owner of all files to UC4.
  chgrp Group name * changes the user group of all files.

• Setting environment variables in $HOME/.profile. For Oracle:
  
  Sample for AIX:

• ORACLE_HOME=/usr/oracle; export ORACLE_HOME
  UC4=/opt/uc4/utility; export UC4
  PATH=.:$ORACLE_HOME/bin[:$PATH]; export PATH
  LIBPATH=.:$UC4/bin:$ORACLE_HOME/lib:/usr/lib:/lib[:$LIBPATH]; export LIBPATH

Sample for HP-UX:

• ORACLE_HOME=/opt/Oracle; export ORACLE_HOME
  UC4=/opt/uc4/utility; export UC4
  PATH=.:$ORACLE_HOME/bin[:$PATH]; export PATH
  SHLIB_PATH=.:$UC4/bin:$ORACLE_HOME/lib:/usr/lib:/lib[:$SHLIB_PATH]; export SHLIB_PATH

Sample for Linux, Solaris and zLinux:

• ORACLE_HOME=/oracle/product/9.0.1; export ORACLE_HOME
  UC4=/opt/uc4/utility; export UC4
  PATH=.:$ORACLE_HOME/bin[:$PATH]; export PATH
  LD_LIBRARY_PATH=.:$UC4/bin:$ORACLE_HOME/lib:/usr/lib:/lib[:$LD_LIBRARY_PATH]; export LD_LIBRARY_PATH

• Set environment variables in $HOME/.profile. For DB2:
  
  Sample for AIX:

• DB2DIR=/usr/lpp/db2_06_01;export DB2DIR
  DB2INSTANCE=db2inst1;export DB2INSTANCE
  UC4=/opt/uc4/utility; export UC4
  PATH=.:$DB2DIR/bin[:$PATH]; export PATH
  LIBPATH=$UC4/bin:$DB2DIR/lib:usr/lib:/lib[:$LIBPATH]; export LIBPATH

Sample for HP-UX:

• DB2DIR=/opt/IBMdb2/V6.1; export DB2DIR
  UC4=/opt/uc4/utility; export UC4
  PATH=.:$DB2DIR/bin[:$PATH]; export PATH
  SHLIB_PATH=$UC4/bin:$DB2DIR/lib:/usr/lib:/lib[:$SHLIB_PATH]; export SHLIB_PATH

Sample for Linux, Solaris and zLinux:

• DB2DIR=/opt/IBMdb2/V7.1;export DB2DIR
  DB2INSTANCE=db2inst1;export DB2INSTANCE
  UC4=/opt/uc4/utility; export UC4
  PATH=.:$DB2DIR/bin[:$PATH]; export PATH
  LD_LIBRARY_PATH=$UC4/bin:$DB2DIR /lib:/usr/lib:/lib[:$LD_LIBRARY_PATH]; export LD_LIBRARY_PATH

	3.	Adjusting the INI Files to the System Environment

• Admin computer
• The INI files and the corresponding utilities share the same name. Adjust the INI file entries as needed.
  
  
  • AE DB Archive (UCYBDBAR.ini)
  • AE DB Client Copy (UCYBDBCC.ini)
  • AE DB Load (UCYBDBLD.ini)
  • AE DB Reorg (UCYBDBRE.ini)
  • AE DB Revision Report (UCYBDBRR.ini)
  • AE DB Unload (UCYBDBUN.ini)
  • AE DB Reporting Tool (UCYBDBRT.INI)
    

	4.	Starting the Utilities

• Admin computer
• The utilities can be called as follows:
  • *.sh: Regular utility start
  • Without file ending: Program to which start parameters can be assigned for batch calls.

Use the following command to process the start scripts:

For example:
chmod +x UCYBDBar.sh

Note that starting this utility's graphical interface on the platform HP Itanium requires the library "libstdc++.so.6" to be loaded with the environment variable LD_PRELOAD. 

Example of a command loading the library:

export LD_PRELOAD=/uc4/utility/bin/libstdc++.so.6

You can insert this command in the Shell scripts. The library will then automatically be loaded whenever a utility's GUI is opened.

Shell-script example "ucybdbld.sh" for opening the graphical user inferface of the utility AE DB Load:

export LD_PRELOAD=./libstd++.so.6

java -jar ucybdbld.jar