To install the eSuite code on an OS/390 server, follow the instructions provided below.
Note: The software contained in this package applies only to OS/390 Version 2
Release 4 or later. It is not supported on earlier versions. The user who installs the code needs WRITE privileges to be able to create files and subdirectories under /usr/lpp/eSuite and /etc/eSuite. Also, a configuration file under
/etc/nstation must be updated.
A.6.1 OS/390 Server Prerequisites
Release 3.0 of IBM NSM Code (base, Java, ibmlogin and NSM) JDK 1.1.4 (or higher) for OS/390 needs to be installed before you install the eSuite code. The following amounts of space are required:
• 26MB of HFS data set space on the OS/390 system under /tmp for the pax file. • 45MB of HFS data set space on the OS/390 system under /usr/lpp/eSuite for
the exploded directory structure.
• 250KB of HFS data set space on the OS/390 system under /etc/eSuite for the eSuite directory structure. In addition, approximately 1.5KB of additional space is required per user and group. This additional space will vary, depending upon the tailoring that is performed in the eSuite WorkPlace Administrator for the users, groups and system preferences.
A.6.2 Installation Instructions
To install eSuite on an OS/390 server, follow these steps:
1. FTP the eSuite10.pax file from the CD to the /tmp directory of OS/390 system. The file should be transferred in binary. You will need space for a 26MB file. 2) Create the /usr/lpp/eSuite directory.
cd /usr/lpp/eSuite
pax -pe -rvf /tmp/eSuite01.pax
4) Create the directory structure that contains the read/write eSuite registry at /etc/eSuite.
mkdir /etc/eSuite
cp -Rp /usr/lpp/eSuite/registry/ /etc/eSuite/registry/
5) Your NFS server is probably configured to use an exports file. You will need to update the exports file to list the eSuite code as a read only directory structure.
/hfs/usr/lpp/eSuite -ro
6) The Network Stations need to know that they should create a mount point for the eSuite code. You need to update the defaults.dft file in
/etc/nstation/StationConfig/ to contain the necessary file system mount command. This file is in ASCII. The simplest way to update the file is to download it to an ASCII-based system (that is, a PC) as a binary file so that no translation occurs then edit it on the system and upload it back to OS/390 as a binary file.
The following line should be appended to the defaults.dft file. Change the hostname value to be the host name of the OS/390 system (for example, st.clair.shores.ibm.com).
set file-service-table[-1]= { "/netstation/prodbase/eSuite/" nil hostname nfs "/hfs/usr/lpp/eSuite/" unix 3 30 8192 8192 }
Note: The data is shown on multiple lines in this document only for clarity. It must
be added to the defaults.dft file as a single line.
A.6.3 Starting the RMI Registry and eSuite Registry Server
It is recommended that the RMI registry and eSuite registry be set up to
automatically start when OS/390 is IPLed. Consult the OS/390 manuals and your local operational guidelines for this procedure.
You can verify the registries are running by issuing the OMVS ps and grep commands.
ps -ef | grep NCS ps -ef | grep rmi
These commands should return with PIDs for each process.
To manually start the registries, execute the /usr/lpp/eSuite/eSuite.sh script. This shell script uses three environment variables as overrides for the location of the Java, eSuite code, and eSuite registry directories.
• $JAVA_HOME is the location of JAVA. It currently defaults to /usr/lpp/java/J1.1.
• $eSuiteRootPath is the location of the eSuite code which you installed at /usr/lpp/eSuite. It currently defaults to this path. You should not change this value.
• $eSuiteRegistryPath is the location of the eSuite registry data. This is the directory structure that you created at /etc/eSuite/registry.
A.6.4 Create a User Called admin on the Server
Later in the process, we will need to use a user called admin in order to initially access a configuration application called the eSuite WorkPlace Administrator. It is therefore probably a good time now to create this user ID on the server.
Since we may want to also use that user ID to log on to a Network Station, and use the WorkPlace Administrator from a Network Station instead of from the server (optional), make the user admin a member of the NSMUser group on the server.
This admin ID is only required during the initial configuration and may be removed once the WorkPlace Administrator has assigned another OS/390 user ID as an administrator for eSuite.
A.6.5 Create a New Group on the Server (Optional)
If all the Network Station users that are served by this server are also all eSuite users, then creating a new group on the server to identify the eSuite users may not be necessary.
That is, if all users are eSuite users, you can define all the eSuite-related settings at the system defaults level in Network Station Manager and these settings then apply to all users. Another option is to use the existing NSMUser group to define the eSuite settings.
However, since it is likely that not all Network Station users are eSuite users, and the non-eSuite users do not require the eSuite WorkPlace desktop to come up automatically after logging on, it is preferable to define a group on the server to represent only the eSuite users, which is the method we use in the example given here.