Event Management › Integration with External Event Collection Systems › Interfacing with CA NSM › Using the CA NSM Command Environment

Using the CA NSM Command Environment

Through its WorldView Map, CA NSM provides a new mechanism for the high-level management of complex enterprise environments. CA Automation Point can directly participate in this process from the interface through the methods described below.

The ADDRESS TNG environment provides a REXX-based programming interface to the objects contained in the Common Object Repository. This interface enables you to do the following:

• Create new objects
• Read and write values into properties of existing objects
• Set a color associated with an object based on the severity level of the problem
• List all objects that belong to a specific class
• Delete existing objects
• Place objects that represent resources monitored by CA Automation Point into the CA NSM Business Process Views

Using the ADDRESS TNG environment, you can graphically depict the activity that is being conducted by CA Automation Point on the WorldView Map. For example, you could create an object to represent each system that is being monitored by CA Automation Point and, using a combination of rules and REXX, turn an icon different colors based on various changes in the state of the managed session-such as a communication failure turning the icon red.

In this discussion, a system is referred to as both an object and an icon. When referred to as an object, the system relates to the Common Object Repository, or database. When referred to as an icon, the system relates to the WorldView Map.

New CA Automation Point users may want to use the ADDRESS TNG environment to place system icons on the WorldView Map and to update their statuses. When applications gain sophistication, CA Automation Point and CA NSM provide greater flexibility in the extent of monitoring and follow-up actions for items placed on the map.