ICM Administration

Procedure

The following functions for starting, stopping, and managing the ICM are available from the administration menu in the ICM monitor (transaction SMICM):

• Exiting the ICM

  Choose Administration   ICM   Exit Soft or Hard Exit to soft-terminate (signal 2) or hard-terminate (signal 9) the ICM. With a soft termination, the ICM still tries to send responses to its existing clients, but does not accept any new connections. With a hard termination, the process is simply terminated at operating system level. All existing connections and, of course, all requests are lost.

• Maintenance Mode

  If the ICM has the status running, you can put in into maintenance mode. Choose Administration   ICM   Maintenance Mode   Activate. You can leave the maintenance mode in the same menu by choosing (Deactivate). The ICM will then have the normal running status again.

• Reload Configuration.

  While the ICM is running you can get it to reload configuration data that can otherwise only be updated periodically or when the ICM is started. Choose Administration   ICM   Configuration  Reload.

  Reloading configuration data means:

  • Invalidates the host name buffer; more information: Host name buffer

  • Invalidates the server cache.

  • Updates information from the message server and application servers (Web dispatcher only).

  • Exits from the maintenance mode if this was active.

  • Reloads filter rules; more information: Template, section: Initialization of the Content Filter

• Setting Start Options

  Choose Administration  ICM  Start Options  Set, to set the trace file and the trace level of the ICM. Standard is dev_icm and 1.

• Restart

  If the ICM is terminated (due to an error or by the administrator), it is automatically restarted by the dispatcher. You can control this behavior by choosing Administration  ICM Local   Restart  Yes or No. If you deactivate the restart and exit the ICM, it will not be restarted.

• Administration of the AS Java

  The functions under Administration  J2EE Instance (local) / J2EE Cluster (global) are used to manage AS Java (JEE Engine). The functions are described in Administration of the AS Java.