Creating an Installation Manager on z/OS for installing IBM HTTP Server
You can create one or more Installation Managers on your z/OS® system to install and maintain software products.
Before you begin
In order to install WebSphere Application Server Version 8.5, your Installation Manager must be at Version 1.5.2 or later.
Install the fix for z/OS APAR OA34228 on each z/OS system that will run IBM Installation Manager to allow the copying of files with extended attributes.
- user mode
- In user mode (also called nonAdmin mode), the Installation Manager can be invoked only by the user that installed it. There can only be one user-mode Installation Manager for a user.
- group mode
- In group mode, the Installation Manager can be invoked by any user ID that is connected to the owning group for the Installation Manager (the default group of the user ID that creates it). There is no limit to the number of group-mode Installation Managers that you can have on a system.
The Installation Manager will consist of two sets of files—a set of executable files that are copied or updated from the installation kit, and a set of runtime data files that describe the products installed by this Installation Manager. Both sets of files must be writeable by the Installation Manager. You must select locations for both the executable and runtime data for each Installation Manager.
Files | Admin or group mode | User mode |
---|---|---|
Binaries | /InstallationManager/bin |
$HOME/InstallationManager/bin |
Runtime data (also called agent data) | /InstallationManager/appdata |
$HOME/InstallationManager/appdata |
These locations are assumed in the Installation Manager documentation and sample jobs. If these names are not appropriate for your system or if you choose to have several Installation Managers, you can choose different names and specify them when you create the Installation Manager.
Procedure
What to do next
cd /InstallationManager/bin/eclipse/tools
imcl -version
You are now ready to install products using IBM® Installation Manager.
CONNECT user2 GROUP(IMGROUP)
To create an additional
Installation Manager, follow the steps in the procedure described in the previous section, selecting
a new user ID and group (if appropriate) and new binaries and runtime data locations. Do not share
binaries or runtime data locations between separate Installation Managers.chown IMADMIN:IMGROUP /InstallationManager/bin
chmod 775 /InstallationManager/bin
chown IMADMIN:IMGROUP /InstallationManager/appdata
chmod 775 /InstallationManager/appdata
If the users of a group-mode Installation Manager
do not have umask
set to allow group-write permission on created files, you might
also have to perform this step when switching from one user ID to another. You might also need to
set permissions and owners for the product files that you install with the Installation Manager to
ensure that maintenance can be performed from other user IDs in the group.Upgrading the Installation Manager: To upgrade an Installation Manager to a new level of the Installation Manager product, download or install the new level of the IBM Installation Manager installation kit and mount it on your system. Then, change directory to the new level of the installation kit and reissue the same installc, userinstc, or groupinstc command that you used to create the Installation Manager. This will update the Installation Manager's binaries from the new installation kit.