IBM Tivoli Composite Application Agent for J2EE, Version 7.1.1

Additional procedure for Security Enhanced Linux (SELinux)

After installing ITCAM Agent for J2EE on SELinux, for example Red Hat Enterprise Linux Version 5 or SUSE Linux Enterprise Server Version 11, you must perform an additional procedure to identify the Data Collector shared libraries.

To identify the Data Collector shared libraries on SELinux, run the following command as root, substituting the installation directory for ITM_HOME and the Tivoli® Monitoring architecture identifier for TEMA_architecture_code and DC_architecture_code:

chcon -R -t texrel_shlib_t 
  ITM_HOME/TEMA_architecture_code/yn/wasdc/7.1.0.2/toolkit/lib/DC_architecture_code

The architecture code identifiers for Linux systems are:

li6263: Linux Intel R2.6 (32 bit)
lx8266: Linux x86_64 R2.6 (64 bit)
lpp263: Linux ppc R2.6 (32 bit)
lpp266: Linux ppc R2.6 (64 bit)
ls3263: Linux S390 R2.6 (32 bit)
ls3266: Linux S390 R2.6 (64 bit)

For 32-bit systems, use the architecture code for the system for both TEMA_architecture_code and DC_architecture_code.

For 64-bit systems, you need to run the command two times in order to identify shared libraries for both 32-bit and 64-bit versions of the Data Collector.

For 64-bit ppc systems, the Monitoring Agent is always 32-bit. Therefore, use lpp263 as TEMA_architecture_code. For example:

chcon -R -t texrel_shlib_t /opt/ibm/itm/lpp263/yn/wasdc/7.1.0.2/toolkit/lib/lpp263
chcon -R -t texrel_shlib_t /opt/ibm/itm/lpp263/yn/wasdc/7.1.0.2/toolkit/lib/lpp266

For 64-bit S390 systems, the Monitoring Agent is always 32-bit. Therefore, use ls3263 as TEMA_architecture_code. For example:

chcon -R -t texrel_shlib_t /opt/ibm/itm/ls3263/yn/wasdc/7.1.0.2/toolkit/lib/ls3263
chcon -R -t texrel_shlib_t /opt/ibm/itm/ls3263/yn/wasdc/7.1.0.2/toolkit/lib/ls3266

For x86_64 systems, the Monitoring Agent might be either 32-bit or 64-bit. Therefore, you need to use li6263 or lx8266 as TEMA_architecture_code, depending on which directory exists: ITM_HOME/li6263 or ITM_HOME/lx8266. You can safely try both sets of commands; the commands applying to a non-existent directory will fail. For example:

chcon -R -t texrel_shlib_t /opt/ibm/itm/li6263/yn/wasdc/7.1.0.2/toolkit/lib/li6263
chcon -R -t texrel_shlib_t /opt/ibm/itm/li6263/yn/wasdc/7.1.0.2/toolkit/lib/lx8266

chcon -R -t texrel_shlib_t /opt/ibm/itm/lx8266/yn/wasdc/7.1.0.2/toolkit/lib/li6263
chcon -R -t texrel_shlib_t /opt/ibm/itm/lx8266/yn/wasdc/7.1.0.2/toolkit/lib/lx8266

Feedback