Job Management Partner 1/Integrated Management - Manager Administration Guide

2.2.3 Tasks that become necessary as a result of a system date/time change

This subsection explains the procedure for changing the system date/time while JP1/IM is running, and provides related notes.

If you set the server's system clock using a method that does not let the time revert to a past time, such as the NTP (Network Time Protocol) server, you can change the system clock without following the procedure described below. In such a case, there is no need to stop JP1/Base.

Organization of this subsection

(1) Returning the system time to a past date/time

(2) Setting forward a system clock that is slower than the current time

(1) Returning the system time to a past date/time

When you change the system time, avoid changing it to a past date/time.

Even when you are correcting a system clock that is too fast or slow, setting the system time back may disrupt the order in which the execution results of automated actions are displayed, or it may cause a problem in the way the monitoring tree status change date/time is displayed. Such problems occur when resetting the system time causes inconsistencies in the data managed by JP1/IM - Manager and JP1/Base. JP1/IM - View is not affected.

Furthermore, if the system time is set back, events may not be correctly searched when you search for events by specifying the arrival time.

If you need to set the system date/time back to the original date/time after having intentionally set it forward to a future date/time for testing purposes, use the following procedure.

(a) Resetting the manager's system date/time back to the original date/time

Steps 7 and 8 are required only if you are using the Central Scope functions.

To reset the date/time back to the original date/time:

1. Stop JP1/IM - Manager.
2. Stop JP1/Base.
3. Reset the system date/time to the current date/time.
4. Delete the action information file, action hosts file, event database, and command execution log file.
   The tables below show where the files to delete are stored.
   

   In Windows:

   Table 2-1 Files to delete (Windows)

   File name	Storage location
   Action information file	Console-path\log\action\actinf.log
   	shared-folder\jp1cons\log\action\actinf.log
   Action hosts file	Console-path\log\action\acttxt{1|2}.log
   	shared-folder\jp1cons\log\action\acttxt{1|2}.log
   Command execution log file	All files under Base-path\log\COMMAND\
   	All files under shared-folder\jp1base\log\COMMAND\
   Event database	IMEvent*.* files under Base-path\sys\event\servers\default\#
   	IMEvent*.* files under shared-folder\jp1base\event\ #

   #: If a different path was specified in the event server index (index) file, the files under the specified path need to be deleted.

   
   

   In UNIX:

   Table 2-2 Files to delete (UNIX)

   File name	Storage location
   Action information file	/var/opt/jp1cons/log/action/actinf.log
   	shared-directory/jp1cons/log/action/actinf.log
   Action hosts file	/var/opt/jp1cons/log/action/acttxt{1|2}.log
   	shared-directory/jp1cons/log/action/acttxt{1|2}.log
   Command execution log file	All files under /var/opt/jp1base/log/COMMAND/
   	All files under shared-directory/jp1base/log/COMMAND/
   Event database	IMEvent*.* files under /var/opt/jp1base/sys/event/servers/default/ #
   	IMEvent*.* files under shared-directory/jp1base/event/ #

   #: If a different path was specified in the event server index (index) file, the files under the specified path need to be deleted.

   
   

5. Start JP1/Base.
6. Start JP1/IM - Manager.
7. From JP1/IM - View, log on to JP1/IM - Manager (JP1/IM - Central Scope).
8. From the Monitoring Tree window, choose the highest-order monitoring group and set its state to the initial state.
   Resetting all monitored nodes to their initial states eliminates inconsistencies in the data managed by Central Scope.
   

(b) Resetting the agent's system date/time back to the original date/time

When you reset the agent's system date/time back to the original date/time, you must delete both the event database of the JP1/Base on the applicable host and the event database of the JP1/Base on the host at the event forwarding destination. For details such as the relevant procedure, see the explanation on necessary tasks when the system date/time is changed in the chapter about changing settings during operation of JP1/Base in the Job Management Partner 1/Base User's Guide.

(2) Setting forward a system clock that is slower than the current time

Unlike in the case of resetting the system clock back, there is no need to stop JP1/IM or delete files in order to set the system clock forward.

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.