How to install or upgrade agents on AS400/i5 (iSeries) operating systems in TMTM.

Below are the steps to be followed while upgrading agents.

Make sure AGENT is ended before starting the installation. The folder that you have decided to install TMTM into (i.e TMTM)

• From within the native job scheduler run the job for ending AGENT.
• In the same folder, save/copy the agent directory.
• And remove all the objects except for the saved filed in the above step.

In the root directory, remove the following objects:

checkpoint.bin;eaa.xml;QPCONF.DEF;QPTTAB.DAT;pkg_bmmtm*.zip;pkg_os400*.zip; qplog.ini;QPLog_pase.ini;QPTTAB_pase.DAT;qpea.log;qpmon.log;qpcfg.lo

To install/update the agent:

To obtain the relevant bootstrap package for your system:
1. Open your web browser.
2. Enter http://hostname:15007 in the URL field, where: ( hostname is the hostname or IP address of the computer running the BMC MTM Application Service ; 15007 is the default port used by the BMC MTM Application Service )
3. From the displayed page, click Download Agents. A list of all the supported agent platforms is displayed, with links to download the package in zip, tar, and tgz formats.
4. Choose the Agent Configuration.
5. Optionally enter a description for the agent. This description can be used with Policies to have certain actions performed when this agent first connects to the services.
6. Locate the required agent platform and file compression type to download.
7. If a command line tool is unavailable you may download the package to the machine from which you launched your browser and then transfer it to the agent machine. For example, using FTP in a binary mode.
 

The bootstrap package contains the following folders:
► agent - contains the basic files needed for the qpea agent
► agentpref - contains the agentpref utility files
► bmmtm_agent - contains the files for the BMTM Configuration Agent which are used for BTM model and package deployment 
► qpmon - contains the qpmon and qpcfg extension file

Note : The contents of the bootstrap package will vary by agent platform. To determine the expected content, review http://hostname:15007/agentdist/platforms.jsp.

To transfer the relevant bootstrap package to your system:
1. Create a directory where the agent installation will reside (agent installation directory), if it does not already exist. The directory must be a directory solely for use by TrueSight Middleware and Transaction Monitor.
2. Transfer and unpack the bootstrap package in the agent installation directory, using a tool appropriate for the format of archive downloaded (e.g. unzip, tar, gunzip). You may choose to use ftp to transfer the bootstrap package, or iSeries Navigator (example : Using iSeries Navigator, copy pkg-i502-bootstrap.tar to the target system: <path/directory as defined in the 1st step>.

• In the PACE environment, cd to the agent install directory.
• To access PACE: Call qp2term ( CD QBMC ; CD BMM ; Type: tar xvf pkg-i5os-bootstrap.tar )

To configure the MQS_HOME system environment variable on i5/OS: 
1. Type WRKENVVAR and press F4. You'll create a new system environment variable (*SYS)  named MQS_HOME. It must be located in the IFS. In the Variable Value field, enter the full path to the agent installation directory.
2. Establish a new command environment, in PASE, to ensure the system environment variable is set. echo $MQS_HOME.
3. Set MQS_HOME to a location that want the logs and config files to go. I.e. /home/bmtm/logs

Before you begin :

To properly install and configure the WebSphere MQ monitoring extension on i5/OS, the installing user must have the following permissions:

► Authority to use the RSTLIB command
► Membership in the QMQMADM group
► Special authorities to IOSYSCFG and JOBCTL

Before you begin, check that library QPASA exists in the  Library File System, this library will be used during the installation. Type the command WRKLIB LIBR.  The sample commands in these steps assume QPASA as the name of the library, but this is not a requirement. The bootstrap package is installed in the IFS (Integrated File System) and then certain components are transferred and installed on LFS.
 

MOTE: For the i5/OS platform, you must choose the bootstrap download file format in .zip format, and unpack the file on the i5/os machine using the Java jar command "jar xvf pkg-i5os-bootstrap.zip".

If you do not have access to Java on your i5/OS machine, you should use FTP to transfer the qpagent.savf from the AGENT_DIST directory on the server machine, as described in the i5/OS sections under Installing agents and extensions in the Flat Directory layout.
 

To install the bootstrap package on PASE:
Note that the following steps should be executed in a PASE environment unless otherwise indicated.
1. Change to the agent directory.
2. Copy QPLog_pase.ini and QPTTAB_pase.DAT to the directory you defined by the MQS_HOME system environment variable. Ensure QPLog_pase.ini and QPTTAB_pase.DAT are readable by all users.
( Type:
cp QPLog_pase.ini ..
cp QPTTAB_pase.DAT .. )

• Change the authorities:

chmod 777 ../QPLog_pase.ini
chmod 777 ../QPTTAB_pase.DAT
3. Copy eaa_dist.xml from the <agent installation directory>/agent directory to the HOMEDIR of the user that will run the TrueSight Middleware and Transaction Monitor jobs.

To install the Save File:
The agent for i5/OS must be installed in a library, which for default purposes is named QPASA.
1.Open an FTP session to the i5/OS agent machine.
2. To create the LIBR library (if it does not already exist):

• To create a QPASA library from an FTP prompt, type: quote rcmd crtlib qpasa
• To create a QPASA library from an i5/OS prompt, type: crtlib lib(qpasa)
• IF the library exists, save contents to a save file and then delete it's contents

3. To create the savefile (if it does not already exist):

• To create a savefile from an FTP prompt, type: quote rcmd crtsavf qpasa/qpagent
• To create the savefile from an i5/OS prompt, type: crtsavf qpasa/qpagent

4. To transfer the agent file in the IFS to the agent SAVF in library QPASA, use the following i5OS command:
CPYFRMSTMF FROMSTMF('<directry defined>/agent/qpagent.savf') TOMBR('/QSYS.LIB/QPASA .LIB/QPAGENT.FILE') MBROPT(*REPLACE) 
5. In the i5/OS command prompt, enter the following:
RSTLIB SAVLIB(MQSW) DEV(*SAVF) SAVF(QPASA/QPAGENT) RSTLIB(QPASA)

A message informs you that eight objects were restored and one object was not restored. Go to the QPASA library and verify that the following objects were restored:
QPCFG *PGM ; QPEA *PGM ; QPMON *PGM ; QPMONSUB *PGM ; QPREG *PGM ; BTMMQ *SRVPGM ; BTMMQ_R *SRVPGM ; QPASA *FILE

6. In the i5/OS command prompt, use CPYTOSTMF (Copy to Stream File) command as follows. Note that these files will be created in the HOMEDIR of the user running the commands. If the user is other than the user that will start the TrueSight Middleware and Transaction Monitor jobs, then you must move the files to the HOMEDIR of the user that will start the TrueSight Middleware and Transaction Monitor jobs. Note that QPCDEF becomes qpconf.def, and QPTTAB becomes QPTTAB.DAT
To allow the commands below to fit in the command line type: Call qcmd

CPYTOSTMF FROMMBR('/QSYS.LIB/QPASA.LIB/QPASA.FILE/QPCDEF.MBR') TOSTMF(QPCONF.DEF)

CPYTOSTMF FROMMBR('/QSYS.LIB/QPASA.LIB/QPASA.FILE/QPTTAB.MBR') TOSTMF(QPTTAB.DAT)

CPYTOSTMF FROMMBR('/QSYS.LIB/QPASA.LIB/QPASA.FILE/QPLOGSAMP.MBR') TOSTMF('QPLogSample.ini')

7. To enable putting messages to a queue, give the QPTTAB.DAT file permission to a user who runs the BMTM Extensible Agent. Enter WRKAUT QPTTAB.DAT, WRKAUT QPCONF.DEF, and add a user authorized to run the BMTM Extensible Agent. Give the user the Data and Object authorities listed in the table below. *RWX

User authorities for the BMTM Extensible Agent :

8.  In the i5/OS command prompt use WRKLNK to copy QPLogSample.ini and QPTTAB.DAT to the IFS directory you defined by the MQS_HOME system environment variable. QPTTAB.DAT is in the save file and is distributed with the BMTM Extensible Agent. When the save file is restored, the file is in the same library as the BMTM Extensible Agent. Ensure QPTTAB.DAT is readable by all users.

Give authorities to the users created to the files below:

9. Note that the secure tunnel, firewall rules,  and service connection information were pre-configured in the bootstrap and the Extensible Agent should connect unless additional Secure Tunnel certificate configuration is required. 

10. (Optional) Configure the BMTM Extensible Agent start automatically when the system is restarted.