This document describes procedures for installing the Borland Enterprise Server on IBM AIX.
Before installing on IBM AIX you should:
For the latest platform information and system requirements for installing Borland Enterprise Server on IBM AIX, go to http://www.borland.com/techpubs/bes/platforms.
Browsers
To use the Web engine and Web Administration Tool included with the Borland Enterprise Server, you need one of the following Web browsers:
You must have an existing IBM AIX Java Development Kit (JDK) 1.3 and JDK 1.4 in your environment before installing Borland Enterprise Server . You need the full JDKs installed, not just the Java Runtime Environments (JRE). The JDK 1.4 is used for Borland Enterprise Server's internal tooling. Configuring any Partition to use JDK 1.4 is not supported in AIX, Partitions must use JDK 1.3.x.
The Borland Enterprise Server installation package for IBM AIX does not ship any version of the Java Development Kit (JDK). For information on Java products for IBM AIX go to http://www.ibm.com/develperworks/tools.
Make sure to update the JAVA_HOME environment variable to reflect the JDK installation directory. Also, update the PATH environment variable to include your JAVA_HOME/bin.
The total amount of disk space required to install the Borland Enterprise Server depends on which components you install. For more information, see "Planning your network" in the Borland Enterprise Server Installation Guide on the Borland web site http://www.borland.com/techpubs/bes.
The Apache Web Server 2.0 is included with this version of Borland Enterprise Server.
For information about the Apache Web Server, refer to Borland Enterprise Server Developer's Guide online Help Topics or PDF. Also, refer to the Apache documentation in the <install_dir>\bin\apache2\ included with Borland Enterprise Server.
The messaging core service product, SonicMQ, is bundled with the Borland Enterprise Server installation. It installs automatically (requires no user intervention), and does not allow configuration. For more detailed information on the SonicMQ product, refer to the SonicMQ documentation included with the Borland Enterprise Server in <install_dir>\SonicMQ\sonicmq-docs\.
Before installing the Borland Enterprise Server, make sure you have the license keys to run the Borland Enterprise Server edition you have purchased and its related components. If you have not received a license for the Borland Enterprise Server, contact your Borland sales representative.
If you do not provide license information during the installation process, you will be able to complete the installation. However, you are required to enter license information later using the Management Console.
For more information on using the Borland Management Console to license and register your server, go to the Borland Enterprise Server online Help Topics or PDF: Installation Guide "Licensing and registering using the Borland Management Console".
Note: If you are installing only a client, you must provide license information during the installation process.
Important: If the following file exists you must delete it prior to installing:
/usr/lib/objrepos/vpd.propertiesRefer to the following section on Uninstalling the Borland Enterprise Server for more information on uninstalling.
To install the Borland Enterprise Server on IBM AIX:
root. To run the install file, invoke the following shell script:
sh <file_name>.bin <file_name> is the name of the installer.Important: Please read the following section, File ownership and the iaschangeowner scripton on changing file permissions using the iaschangeowner script.
BES52_AIX64/32.tar.chmod to run the install script.bin (32 or 64 bit) file, you can then run it to launch the installer.$ cd /mnt/cdrom$ /AIX64/InstallAIX_64/32.binWhen the installer launches, follow the onscreen installation panels.
Full BES installation: On the JDK panel you must enter the path of your JDK 1.4 and JDK 1.3. The installer will not let you proceed without this correct information.
VisiBroker standalone installation: VisiBroker standalone versions do not require a JDK 1.4, therefore it is not necessary to have both JDKs 1.3 and 1.4 for VisiBroker standalone installations on AIX. If you do not have a JDK 1.4 installed, you can point that selection box to the same JDK selection as the JDK 1.3.
Borland Enterprise Server 5.2.x supports both JDK 1.4 and JDK 1.3, however, AIX does not support JDK 1.4 at this time. For components that host user code, such as Partitions or a client, the default version you specify must be JDK 1.3.x.
Some files and directories, such as log files, properties, and realms are not created when the Borland Enterprise Server is installed. Instead, they are created by the server at runtime, the first time the server is started. Permissions on these files and directories are granted based on the user running the server at this initial time. For example, if you run the server for the first time as usernameA, some files or directories will be owned by usernameA. Any subsequent running of the server by any other user (including root) will result in error due to permission problems. File ownership must be changed in order to allow any other users to write to these files.
To change ownership use the iaschangeowner script (UNIX only) in the /bin directory of the installed Borland Enterprise Server. The script changes the ownership of files such as logs and properties to allow writing by another owner.
The following directories (and their contents) are affected by the iaschangeowner script:
<BES_INSTALLATION>/var/defaults<BES_INSTALLATION>/var/bms<BES_INSTALLATION>/var/servers/<servername (*)><BES_INSTALLATION>/SonicMQNote: This version of Borland Enterprise Server includes a new iaschangeowner option, the <new group>.
When a Borland Enterprise Server installation has multiple server instances defined, the ownership of each instance can be set to different, or the same users.
Usage: iaschangeowner -r <install dir> [-s <server name> | -d] -o <new owner> -g <new group> [-a]
When a Borland Enterprise Server installation has multiple server instances defined, the ownership of each instance can be set to different, or identical users.
-r <install dir>: The root directory of the Borland Enterprise Server installation. -d Defaults (templates): Change the ownership of future servers. -d and -s cannot be specified at the same time. -s <server name>: The name of the server instance to change ownership of. This is not required if the server only contains one server instance. -d and -s cannot be specified at the same time. -o <new owner>: The user id of the new owner, e.g.; nobody, root, etc.-g <new group>: The group id of the new group.-a: If owner is root, set Apache to run as root. Otherwise, set Apache to run as the user who starts it (or the Borland Enterprise Server).The following rules apply:
-s or -d are specified, and only one server was created, ownership of that server will be changed. An error will be generated if more than one server exists.-s <server_name> is specified, only that server's files will be changed. -d cannot be specified at the same time.-d is specified, all the files in /var/default will be updated and therefore any new server will be owned by the new user. -s cannot be specified at this time.iaschangeowner script to change the user name and group for any servers started from the /usr/BES installation:
% iaschangeowner -r /usr/BES -d -o jsmith -g adminFailure to change permissions prior to changing server owners will result in errors similar to the following:
bin/ias: server_root/sk.txt: cannot createTo uninstall the Borland Enterprise Server:
osagent running during the uninstall.<install_root>/UninstallerData/uninstall. <install_root>.It is not necessary to uninstall SonicMQ using the SonicMQ uninstaller. But, you can if you wish, access the SonicMQ uninstaller using the shell script <install_root>/SonicMQ/uninstall.sh.
The SonicMQ uninstaller will ask you about deleting a large number of files. It is recommended you choose "yes" for these prompts.