Changes in the behavior of the autostart scripts

• In V6.1 fix pack 3, the installation process produced an autostart script with only one entry using a generic CandleAgent start all command. Users modified this file as needed.
• In V6.1 fix pack 4, the installation process generated individual entries for each application in a particular installation, but the values captured in the file could not be overridden.
• In V6.1 fix pack 5, the multiple entries remain, and an override capability has been added.
• In V6.2.2 fix pack 2 and later, the multiple entries remain, and the override capability has been significantly enhanced.

The autostart script generated by an installation, upgrade, or configuration and named ITMAgentsN or rc.itmN (depending on the UNIX platform) contains an entry for each application in a particular installation. The entries look similar to this:

su - USER -c "ITM_Install_Home/bin/itmcmd agent start product_code"

Or:

su - USER -c "ITM_Install_Home/bin/itmcmd agent –o Instance start product_code"

Where:

USER

Is the ID that the application will be started as. By default, USER is the owner of the bin directory for the application. For the UNIX Log Alert agent, USER is the owner of the ITM_Install_Home/PLAT/ul/bin directory.

N

Is an integer specific to each installation on a system.

ITM_Install_Home

Is the full path to the IBM® Tivoli® Monitoring version 6.x installation directory.

product_code

Is the two-character code for this application. See IBM Tivoli product, platform, and component codes for a list of the codes for the common components and the base agents. See the product documentation for other product codes.

instance

Is the instance name required to start this application.

PLAT

Is the platform directory where the application is installed.

For remote deployment usage, you can modify the kcirunas.cfg file in the root directory of the media. You can also modify the kcirunas.cfg file in the Tivoli Enterprise Monitoring Server depot after populating the depot from this image. If you have set the DEPOTHOME variable in the tables/TEMS_NAME/KBBENV file, you must use that value as the base when searching for the depot location. To determine if you have set DEPOTHOME, run the following commands:

cd ITM_Install_Home
DEPOTHOME=`find tables -name KBBENV -exec grep DEPOTHOME {} \; 2> /dev/null | cut -d= -f2`
echo $DEPOTHOME

If DEPOTHOME is not empty, run the following commands to locate kcirunas.cfg in the monitoring server depot:

cd ITM_Install_Home
DEPOTHOME=`find tables -name KBBENV -exec grep DEPOTHOME {} \; 2> /dev/null | cut -d= -f2`
find $DEPOTHOME -name kcirunas.cfg -print

If DEPOTHOME is empty, run the following commands instead:

cd ITM_Install_Home
find tables -name kcirunas.cfg -print

The file kcirunas.cfg contains a superset of the XML syntax and structure in the ITM_Install_Home/config/HOST_kdyrunas.cfg file (where HOST is the short hostname for this system) produced by remote configurations, such as remote deployment or Tivoli Enterprise Portal-based agent configuration.

The following is the default kcirunas.cfg file with all <productCode> entries commented:

<agent>

  <!productCode>ux</productCode>
  <instance>
   <user>itmuser</user>
  </instance>

  <!productCode>ul</productCode>
  <instance>
   <user>root</user>
  </instance>

  <!productCode>lz</productCode>
  <instance>
   <user>itmuser</user>
  </instance>

  <!productCode>ud</productCode>
  <instance>
   <name>db2inst1</name>
   <user>db2inst1</user>
  </instance>
  <instance>
   <name>db2inst2</name>
   <user>root</user>
  </instance>

  <!productCode>ms</productCode>
  <instance>
   <name>HUB17</name>
   <user>itmuser</user>
  </instance>

  <!productCode>cq</productCode>
  <instance>
   <user>itmuser</user>
  </instance>

  <!productCode>cj</productCode>
  <instance>
   <user>itmuser</user>
  </instance>

 </agent>

By default, each <productCode> section in the kcirunas.cfg file is disabled by making the product code a comment, such as <!productCode>. To activate a section, do the following:

1. Remove the comment indicator (the exclamation point, !) so that the <!productCode> item looks like <productCode>.
2. Copy a <productCode> section.
3. Rather than creating new sections from scratch, customize each <productCode> section, and activate it.

Commented, or deactivated, sections are ignored. Uncommented, or activated, sections for applications that are not installed are ignored. For agents that do not require an instance value, specify only:

<productCode>product_code</productCode>
  <instance>
   <user>USER</user>
  </instance>

For agents that do require an instance value, like the DB2® monitoring agent (product code ud), specify the product_code, instance, user, and name:

  <productCode>ud</productCode>
  <instance>
   <name>db2inst1</name>
   <user>db2inst1</user>
  </instance>
  <instance>
   <name>db2inst2</name>
   <user>root</user>
  </instance>

Two items that are supported in the kcirunas.cfg file that are not supported in the HOST_kdyrunas.cfg file are the <default> section and the <autoStart> flag. The <autoStart> flag can be used in the <default> section and in the <instance> section. The <default> section is specified as follows:

  <productCode>product_code</productCode>
  <default>
   <user>db2inst1</user>
  </default>

  <productCode>product_code</productCode>
  <default>
   <autoStart>no</autoStart>
  </default>

  <productCode>product_code</productCode>
  <default>
   <user>db2inst1</user>
   <autoStart>no</autoStart>
  </default>

The <autoStart> flag is specified as follows:

  <productCode>product_code</productCode>
  <default>
   <autoStart>no</autoStart>
  </default>

  <productCode>product_code</productCode>
  <instance>
   <autoStart>no</autoStart>
  </instance>

A section similar to the following can be used to not automatically start the default MQ Monitoring instance and to automatically start all other instances as the mqm user:

  <productCode>mq</productCode>
  <default>
   <user>mqm</user>
  </default>
  <instance>
   <name>None</name>
   <autoStart>no</autoStart>
  </instance>

A set of sections similar to the following can be used to avoid automatically starting the set of installed agents and servers. You need one section for each agent or server component installed:

  <productCode>product_code</productCode>
  <default>
   <autoStart>no</autoStart>
  </default>

Where product_code is the two-character product code for the individual agent or server component (See IBM Tivoli product, platform, and component codes).