L.4 Changes in version 09-00

• Event levels of events received from JP1/Base can now be changed according to predefined conditions, and the events can be managed by JP1/IM - Manager under the new event level (function for changing the severity level of JP1 events).

• A dedicated database for JP1/IM - Manager (the IM database) can now be created.

• A maximum of 1,500,000 events can now be managed (when using the IM database).

• Memo entries can now be added to events (when using the IM database) (addition of memo entries).

• An event can be issued when a correlation event fails to establish a correlation (event generation).

• Action definitions can now be set from a GUI (Action Parameter Detailed Definitions window) (simplified automatic action function).

• By specifying a date and time or by moving the slider, users can limit the range of events displayed in the event list (addition of event display start-time specification area).

• Managed hosts can now be registered, deleted, and viewed in list form from IM Configuration Management - View, allowing centralized management of information related to registered hosts (host management).

• The system hierarchy can be centrally managed from IM Configuration Management - View (system hierarchy management).

• IM Configuration Management - View can be used to centrally manage the profiles in JP1/Base on the hosts (profile management).

• Activity information about the JP1/Base services running on each host can be checked from IM Configuration Management - View (management of service activity information).

• Commands are now available for exporting and importing management information associated with IM Configuration Management (import and export of IM Configuration Management information).

• System hierarchies that incorporate virtual hosts can now be managed in IM Configuration Management - View. Also, information about a system hierarchy that has virtual hosts can be imported and used in the Central Scope (virtualization configuration management).

• Troubleshooting data can be collected by the data collection tool.

• Actions can now be performed locally by JP1/Base on a stand-alone basis.

• JP1/IM can be linked with JP1/AJS3.

• NNMi incidents generated by HP NNMi can now be converted into JP1 events by JP1/IM - EG for NNMi and be monitored by JP1/IM.

• Messages can now be displayed in a unified format by the linkage with JP1/IM - MO.

• Messages have been added, deleted, and changed.

• JP1 events have been added.

• The JP1/IM - Manager manuals have been reorganized.

• Windows Server 2008 is now supported.

• JP1/Integrated Management - Service Support has been added to the integrated management software products that can link with JP1/Integrated Management.

• Windows 2000 has been removed as a prerequisite operating system for JP1/Base.

• Common exclusion-conditions have been added to the event acquisition filter to temporarily prevent the system from acquiring JP1 events issued by hosts under maintenance.

• Exclusion-conditions which exclude JP1 events from display (or acquisition) have been added to the following filters and as conditions for event searches:

  • Event acquisition filter

  • Event receiver filter

  • Severe events filter

  • View filter

• A function has been added for making status change conditions for monitoring objects resident in memory.

• A function has been added for automatically setting a monitoring object to Initial status on receipt of a specific JP1 event.

• A function has been added for automatically deleting status change events when the response status of a JP1 event changes to Processed.

• The method of specifying the source host for the event service in FQDN format has been changed.

• A function has been added for monitoring and responding to response-waiting events issued by uCosminexus Batch Job Execution Server.

• Cautionary notes associated with the setup for linking with HP NNM System Observer have been amended.

• The following files have been added to the list of log files and directories:

  Installation log file, event console log file, file for accumulated response-waiting events, and plug-in log file

• The file count for event flow control trace logs, the maximum disk usage, and the timing when the file is switched have been changed.

• The maximum disk usage of the action hosts file has been changed.

• The maximum length of an event acquisition filter has been changed.

• The Central Scope button and menu command become unavailable in the Event Console window when the Central Scope service is inactive.

• The number of entries saved in the Target host and Command fields in the Execute Command window has been augmented.

• A description of the title bar has been added to the description of the elements in the Monitoring Tree window.

• Because the JP1/Base commands described in this manual apply to manager hosts, a note has been added to direct readers to the JP1/Base manuals for details of agent host commands.

• Users must now have superuser permission to execute the jcocmddef command.

• A note about the message output when the jcocmddef command is executed has been added.

• The values specifiable in the -runevinterval option of the jcocmddef command have been changed (interval for issuing elapsed time events).

• The triggers for JP1 events have been changed.

• The arrival time attribute has been renamed.

• Some product names have changed.

• The event log has been added as an output destination for messages.

• A Source field has been added to the list of Windows event log entries output by JP1/Integrated Management.

• User-specified images of any size can now be used as icons representing monitoring nodes (Visual Icon).

• JP1/Integrated Management - View is now supported on Windows Vista.

• A feature for copying information to the clipboard has been added.

• There are now additional files that need to be backed up:

  • Guide information file (jcs_guide.txt)

  • Action profiles (actprofile2_JP1-user-name)

  • Files under View-path\image\icon\

  • Files under View-path\image\visual\

  • Files under View-path\image\map\

• The list of files has been updated.

• The list of limits has been updated.

• Connectivity with previous versions has been updated.

• In a non-cluster environment, a method of configuring and operating logical hosts that are not subject to failover has been added.

• An explanation of the integrated trace log has been added.

To Page Top