2.4 Creating IM databases (for UNIX)
You use IM databases to monitor events that occur in the system. The two types of IM databases are the integrated monitoring database and the IM Configuration Management database. The integrated monitoring database is used when Central Console or the Intelligent Integrated Management Base are being used. The IM Configuration Management database is used with IM Configuration Management to manage the system hierarchy. For details about the functions available when the integrated monitoring database and the IM Configuration Management database are used, see 2.6 Functions provided by the IM database in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.
During system configuration or after operations have started, you can create either or both the integrated monitoring database and the IM Configuration Management database.
JP1 events obtained from the event database after the JP1/IM3 - Manager service has started are stored in the integrated monitoring database. For details, see 4.1.3(2) JP1 event control when using the integrated monitoring database in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.
This section explains how to create an IM database.
- Important
-
When operating in an Amazon EC2 instance environment, the host name can exceed 32 characters (for example, ip-xx-xx-xx-xx.ap-northeast-1.compute.internal(where xx-xx-xx-xx is the IP address)). When setting up an IM database, if the host name of the IM database exceeds the upper limit (32 characters), the setup fails with an KNAN11141-E error message. Therefore, follow the method of permanently assigning a static host name to an Amazon EC2 instance published by AWS and change it to a host name that does not exceed the upper limit (32 characters).