IBM Support

ISM config GUI does not show all of the ISM profiles

Technote (FAQ)


How can you get the ISM config GUI to show all of the active ISM profiles?


The absence of existing active profiles in the ISM config GUI is usually caused by switching back and forth between the ismbatch utility and the ISM config GUI to create and edit ISM profiles.

The profiles and monitors that you create and edit in the ISM config GUI are written to the TEPS database. When you open the ISM config GUI, the utility populates the workspace with the profile records that exist on the TEPS database.

In comparison, when you use the ismbatch command to create and edit profiles, the profiles and changes are not written to the TEPS database. Consequently, this information does not display in the ISM config GUI.

You can use the new ismconfig command, in conjunction with the ISM config GUI, to create and edit profiles. These profiles and changes are written to the TEPS database. Consequently, there is no conflict with the ISM config GUI.

In order to maintain synchronization with the TEPS database, stop using the ismbatch command.


ISM (Internet Service Monitoring) provides a feature for recreating the ISM profile database from the existing profile XML files. Use the xml2cli and ismconfig commands to add profiles to the TEPS database.

First, you use the xml2cli command on each of the ISM agent servers to create an intermediate file. Then, you copy these intermediate files to the TEPS server. On the TEPS server, you use the ismconfig command to add the profiles to the TEPS database from these intermediate files.

Conversion Process

1) Backup the ISM_HOME directory on each ISM agent server.

2) Apply the following interim fixes to resolve known issues related to this conversion process.

_ ISM 7.4 -- Apply ISM 7.4 Interim Fix 3 ( or later

3) Use the xml2cli command on each of the ISM servers to copy the active profiles to an intermediate processing file.


%ISMHOME%\platform\win32\bin\xml2cli.exe > output.txt


$ISMHOME/bin/xml2cli > output.txt

4) Copy these intermediate files to the TEPS server.

Note: Under Windows, the intermediate output file must reside in the same directory where the ismconfig command resides. On Unix/Linux, the intermediate file may reside in a different directory.

5) Use the ismconfig command on the TEPS server to recreate the ISM profiles on the TEPS database from the intermediate file that the xml2cli command generated.

Note: In order to run the ismconfig command, you must be logged on as the Administrator or as a member of the Administrators group (Windows), and your Windows user ID must be defined locally (that is, not defined by an application like Microsoft's Active Directory). Under Unix and Linux, your user ID must have root authority.

The ismconfig command resides in the following directories on the TEPS server. The location depends on which application package has been installed on the TEPS. You can run the ismconfig command from either directory if the command has been installed in both directories. The command name is ismconfig.cmd on Windows and on Unix/Linux.

_ For the Tivoli Enterprise Portal desktop client:

o For Unix/Linux systems, $CANDLE_HOME/$ARCH/cj/lib

o For Windows systems, %CANDLE_HOME%\CNP

_ For the Tivoli Enterprise Portal Server support package:

o For Unix/Linux systems, $CANDLE_HOME/$ARCH/cw/classes

o For Windows systems, %CANDLE_HOME%\CNB\classes

The ismconfig.props file resides in the same directory as the ismconfig command. Primarily, the ismconfig.props file identifies the TEPS server, and the user ID, password, and port you use to log onto the TEP console.

When you run the ismconfig command, the ismconfig.log file is created in the ITM_HOME\logs directory (Windows) or ITM_HOME/logs (Unix/Unix). The ismconfig.log file identifies the actions that the command has completed.



%CANDLE_HOME%\CNB\classes\ismconfig -config -file output.txt


%CANDLE_HOME%/aix536/cw/classes/ -config -file /tmp/output.txt

6) Resync the agents to replace the existing profiles with the current copy of those profiles from the TEPS database.

Detailed Instructions
Refer to the Related URL section for detailed instructions.

Related information

Converting profiles 7.4 created with ismbatch
Avoiding KFWITM393E when running the ismconfig command
Resynching ISM Profiles

Product Alias/Synonym

ISM 7.4

Document information

More support for: Tivoli Composite Application Manager for Transactions

Software version: 7.4

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Reference #: 1591933

Modified date: 11 November 2015

Translate this page: