APM - 9.5 NSM Integration Guide

Integration for CA NSM Guide
Release 9.5
CA Application Performance
Management

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to
as the Documentation) is for your informational purposes only and is subject to change or withdrawal by CA at any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without
the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed
by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing
your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and
CA.
Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may
print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your
employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced
copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY
KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,
DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions
set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or
their successors.
Copyright 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.

CA Technologies Product References
This document references the following CA Technologies products and features:
CA Application Performance Management (CA APM)
CA Application Performance Management ChangeDetector (CA APM
ChangeDetector)
CA Application Performance Management ErrorDetector (CA APM ErrorDetector)
CA Application Performance Management for CA Database Performance (CA APM
for CA Database Performance)
CA Application Performance Management for CA SiteMinder (CA APM for CA
SiteMinder)
CA Application Performance Management for CA SiteMinder Application Server
Agents (CA APM for CA SiteMinder ASA)
CA Application Performance Management for IBM CICS Transaction Gateway (CA
APM for IBM CICS Transaction Gateway)
CA Application Performance Management for IBM WebSphere Application Server
(CA APM for IBM WebSphere Application Server)
CA Application Performance Management for IBM WebSphere Distributed
Environments (CA APM for IBM WebSphere Distributed Environments)
CA Application Performance Management for IBM WebSphere MQ (CA APM for
IBM WebSphere MQ)
CA Application Performance Management for IBM WebSphere Portal (CA APM for
IBM WebSphere Portal)
CA Application Performance Management for IBM WebSphere Process Server (CA
APM for IBM WebSphere Process Server)
CA Application Performance Management for IBM z/OS (CA APM for IBM z/OS)
CA Application Performance Management for Microsoft SharePoint (CA APM for
Microsoft SharePoint)
CA Application Performance Management for Oracle Databases (CA APM for Oracle
Databases)
CA Application Performance Management for Oracle Service Bus (CA APM for
Oracle Service Bus)
CA Application Performance Management for Oracle WebLogic Portal (CA APM for
Oracle WebLogic Portal)
CA Application Performance Management for Oracle WebLogic Server (CA APM for
Oracle WebLogic Server)
CA Application Performance Management for SOA (CA APM for SOA)

CA Application Performance Management for TIBCO BusinessWorks (CA APM for
TIBCO BusinessWorks)
CA Application Performance Management for TIBCO Enterprise Message Service
(CA APM for TIBCO Enterprise Message Service)
CA Application Performance Management for Web Servers (CA APM for Web
Servers)
CA Application Performance Management for webMethods Broker (CA APM for
webMethods Broker)
CA Application Performance Management for webMethods Integration Server (CA
APM for webMethods Integration Server)
CA Application Performance Management Integration for CA CMDB (CA APM
Integration for CA CMDB)
CA Application Performance Management Integration for CA NSM (CA APM
Integration for CA NSM)
CA Application Performance Management LeakHunter (CA APM LeakHunter)
CA Application Performance Management Transaction Generator (CA APM TG)
CA Cross-Enterprise Application Performance Management
CA Customer Experience Manager (CA CEM)
CA Embedded Entitlements Manager (CA EEM)
CA eHealth Performance Manager (CA eHealth)
CA Insight Database Performance Monitor for DB2 for z/OS
CA Introscope
CA SiteMinder
CA Spectrum Infrastructure Manager (CA Spectrum)
CA SYSVIEW Performance Management (CA SYSVIEW)

Contact CA Technologies
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the
information that you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following
resources:
Online and telephone contact information for technical assistance and customer
services
Information about user communities and forums
Product and documentation downloads
CA Support policies and guidelines
Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about CA Technologies product documentation, you
can send a message to techpubs@ca.com.
To provide feedback about CA Technologies product documentation, complete our
short customer survey which is available on the CA Support website at
http://ca.com/docs.

Contents 7

Contents

Chapter 1: Introduction 11
How Integration Works .............................................................................................................................................. 11
Architecture Diagram ................................................................................................................................................. 12
Benefits ...................................................................................................................................................................... 12
Chapter 2: Installing CA Introscope Integration for CA NSM 15
Remove CA Introscope to Unicenter NSM Integration Release 1.x ......................................................................... 15
Remove the Integration Pack from the Enterprise Manager ..................................................................................... 16
Remove the Integration Pack from the NSM Bridge Proxy ........................................................................................ 16
Remove the Integration Pack from Unicenter WorldView ........................................................................................ 16
Remove the Integration Pack from Unicenter Management Portal .......................................................................... 17
Remove Objects from the WorldView Repository ..................................................................................................... 17
Remove the Introscope Web Services API/SDK 7.2 ................................................................................................... 18
Pre installation Requirements .................................................................................................................................... 18
Feature Prerequisites ................................................................................................................................................. 19
Installation Archives ................................................................................................................................................... 20
Installation Sets .......................................................................................................................................................... 21
Features of CA Introscope Integration for CA NSM ................................................................................................. 21
User Rights ................................................................................................................................................................. 22
Installation Scenarios ................................................................................................................................................. 22
Installation Modes ...................................................................................................................................................... 22
Install using the GUI Installer ..................................................................................................................................... 23
Use the Integration Pack Configuration UI ......................................................................................................... 24
Install using Silent Mode ............................................................................................................................................ 25
Silent Installer Properties .................................................................................................................................... 25
Install Using the Console Mode .................................................................................................................................. 27
Re-install CA Introscope Integration for CA NSM ..................................................................................................... 27
Install on a Machine with an Existing Integration ...................................................................................................... 28
Verify the Installation ................................................................................................................................................. 29
Uninstall CA Introscope Integration for CA NSM ..................................................................................................... 29
Remove CA Introscope Objects ......................................................................................................................... 30
Chapter 3: Configuring and Managing Whats Monitored 33
Overview .................................................................................................................................................................... 33
Required Configurations ..................................................................................................................................... 33
Configure the Alternate Bind Address ....................................................................................................................... 34

8 Integration for CA NSM Guide

Configure the Unicenter Management Portal ............................................................................................................ 34
Using the CA NSM Configuration UI ........................................................................................................................... 35
Access the CA Introscope Integration for CA NSM Configuration UI ................................................................ 35
Configure Introscope Enterprise Manager Host ................................................................................................. 36
Configure CA NSM ...................................................................................................................................................... 39
Edit the NSM WorldView Repository .................................................................................................................. 39
Edit the NSM Enterprise Manager Host .............................................................................................................. 39
Configure Monitoring .......................................................................................................................................... 40
Configure Message Formatting ........................................................................................................................... 41
Configure Status Mapping ................................................................................................................................... 41
(Optional) Enable DEBUG logging in the Introscope-NSM bridge ....................................................................... 43
Chapter 4: Using CA Introscope Integration for CA NSM 45
View CA Introscope objects in Management Command Center .............................................................................. 45
View Introscope Objects in the Management Command Center Tree Hierarchy............................................... 46
View Dashboards of CA Introscope Objects in the Management Command Center ........................................ 46
View CA Introscope Alerts in the Management Command Center Event Console ........................................... 47
View CA Introscope Objects in the Unicenter Management Portal ......................................................................... 47
View CA Introscope Objects in CA NSM WorldView 2D Map ................................................................................... 48
View CA Introscope Alerts in the CA NSM Event Console ........................................................................................ 49
Chapter 5: Integrating CA NSM with CA CEM 51
About CA NSM with CA CEM ...................................................................................................................................... 52
CA NSM Integration Overview ................................................................................................................................... 53
CA NSM to CA CEM Integration Terminology ............................................................................................................. 53
CA NSM Terms .................................................................................................................................................... 54
CA NSM to CA CEM Term Mapping ..................................................................................................................... 55
Chapter 6: Installing CA CEM Integration for CA NSM 57
Install the CA CEM Integration Pack for CA NSM ....................................................................................................... 57
Verify the Integration Installation ....................................................................................................................... 58
Install Custom Dashboards for Unicenter Management Command Center .............................................................. 59
Verify the Installation .......................................................................................................................................... 59
Set CA NSM Connection Information .................................................................................................................. 60
Chapter 7: Configuring the CA CEM and NSM Connections 61
Set CA CEM Connection Information ......................................................................................................................... 61
Configure Unicenter Management Portal with CA CEM ............................................................................................ 61
(Optional) Enable DEBUG logging in the CEM-NSM bridge ........................................................................................ 63

Contents 9

CA CEM-NSM Bridge Maintenance ............................................................................................................................ 63
CA CEM-NSM Bridge Start/Stop .......................................................................................................................... 63
Other Maintenance Information ......................................................................................................................... 63
Integrate with Unicenter Management Portal.................................................................................................... 64
Chapter 8: Using CA NSM with CA CEM 67
View CA CEM Objects in CA NSM ............................................................................................................................... 67
View CA CEM objects in Unicenter Explorer .............................................................................................................. 67
View CA CEM Objects in Management Command Center ......................................................................................... 69
View CA CEM Objects in Unicenter WorldView 2D Map ............................................................................................ 71
View CA CEM Objects in Unicenter Management Portal ........................................................................................... 71
View CA CEM Incidents in the CA NSM Event Console .............................................................................................. 73
Receive and Update CA CEM Objects in the CA NSM WorldView Repository ........................................................... 73
Synchronize CA CEM Data ................................................................................................................................... 74
Modify the Hierarchy of CA CEM Managed Objects ........................................................................................... 74
Receive and Update the Status of CA CEM Objects ................................................................................................... 75
Customize CA NSM Alarmset Severity Status Mappings ............................................................................................ 76
CA NSM Resources ..................................................................................................................................................... 77
CA NSM Documentation ..................................................................................................................................... 77
Appendix A: Troubleshooting 79
Verify CA NSM Integration with CA CEM.................................................................................................................... 79
Symptoms and Solutions-(NSM and CA CEM) ............................................................................................................ 80
Appendix B: CA CEM-NSM Bridge Properties 83
Edit the cemBridgeConnector.properties File ............................................................................................................ 83
WEBAPP_CONTAINER_HOST .............................................................................................................................. 84
WEBAPP_CONTAINER_PORT .............................................................................................................................. 84
CEM.1.HOST ........................................................................................................................................................ 84
CEM.1.PORT ........................................................................................................................................................ 85
CEM.1.USER......................................................................................................................................................... 85
CEM.1.PASSWORD .............................................................................................................................................. 86
CEM.1.TOPIC_BIZ_PROCESS_UPDATES_SUBSCRIBE ........................................................................................... 86
CEM.1.TOPIC_BIZ_TRANSACTION_UPDATES_SUBSCRIBE .................................................................................. 86
CEM.1.TOPIC_USER_GROUP_UPDATES_SUBSCRIBE .......................................................................................... 87
CEM.1.TOPIC_INCIDENT_UPDATES_SUBSCRIBE ................................................................................................. 87
CEM.1.TOPIC_BIZ_TRANS_SEVERITY_UPDATES_SUBSCRIBE .............................................................................. 88
CEM.1.TOPIC_USER_GROUP_SEVERITY_UPDATES_SUBSCRIBE ......................................................................... 88
CEM.1.CEM_CONNECTION_CHECK_SEC ............................................................................................................. 89
Filter User Groups, Business Services, and Business Transactions............................................................................. 89


CEM.1.USER_GROUP_FILTER_REGEX .................................................................................................................. 90
CEM.1.BIZ_PROCESS_FILTER_REGEX .................................................................................................................. 90
CEM.1.BIZ_TRANSACTION_FILTER_REGEX .......................................................................................................... 91
Edit the nsmBridgeConnector.properties File ............................................................................................................ 91
NSM_WV_HOST .................................................................................................................................................. 92
NSM_WV_USER .................................................................................................................................................. 92
NSM_WV_PASSWORD ........................................................................................................................................ 92
NSM_WV_DISABLE .............................................................................................................................................. 93
NSM_CONNECTION_CHECK_SEC ........................................................................................................................ 93
NSM_EM_HOST................................................................................................................................................... 94
NSM_EM_DISABLE .............................................................................................................................................. 94
Edit the cemNsmBridge.properties File ..................................................................................................................... 94
CEMNSM_CREATENODE_TESS ............................................................................................................................ 95
CEMNSM_CREATENODE_USERGROUPS ............................................................................................................. 95
CEMNSM_WTO_SOURCE .................................................................................................................................... 95
CEMNSM_WTO_TEXT ......................................................................................................................................... 96
Index 99


Chapter 1: Introduction

The CA Introscope Integration for CA Network and Systems Management (CA NSM)
enhances the CA Introscope platform with capabilities that allow you to create
monitoring solutions suitable to the requirements of the NSM managed environment.
The CA Introscope Integration for CA NSM provides out-of-the-box integration of
industry-leading business application performance management solution of CA with CA
NSM. This integrated solution can import CA Introscope performance agents, status,
alerts, and summary dashboards to CA NSM. The solution allows you to take advantage
of CA Introscope deep visibility into production web applications automatically,
without requiring J2EE or .NET expertise.
This section contains the following topics:
How Integration Works (see page 11)
Architecture Diagram (see page 12)
Benefits (see page 12)
How Integration Works
CA Introscope Integration for CA NSM integrates CA Introscope business application
performance agents into the CA Management Database (CA MDB). The integration
allows CA Introscope agents to be represented as managed objects within CA NSM.
These managed objects can also be utilized within CA NSM Business Process Views (BPV)
for defining custom management views incorporating business application and
infrastructure elements. Performance status and alerts from CA Introscope are
available within Unicenter Management Portal, 2D Map, Management Command
Center, Object Explorer, and the NSM Event Console. This solution enables proactive
incident management, simple correlation of business application, systems, network
availability, and performance. For an illustration of the integration pack architecture,
see Architecture diagram (see page 12).
Architecture Diagram


Architecture Diagram

Benefits
CA Introscope Integration for CA NSM:
Monitors mission critical web applications within the CA NSM consoles for more
effective and consolidated monitoring and triage across their entire infrastructure.
Allows IT organizations to collaborate more effectively by presenting CA
Introscope-collected business application performance alerts in a manner native
to their management tools.
Benefits


Simplifies monitoring processes by allowing business application performance alerts
from CA Introscope to participate in centralized correlation, notification, and
resolution processes.


Chapter 2: Installing CA Introscope
Integration for CA NSM

Remove CA Introscope to Unicenter NSM Integration Release 1.x (see page 15)
Remove the Integration Pack from the Enterprise Manager (see page 16)
Remove the Integration Pack from the NSM Bridge Proxy (see page 16)
Remove the Integration Pack from Unicenter WorldView (see page 16)
Remove the Integration Pack from Unicenter Management Portal (see page 17)
Remove Objects from the WorldView Repository (see page 17)
Remove the Introscope Web Services API/SDK 7.2 (see page 18)
Pre installation Requirements (see page 18)
Feature Prerequisites (see page 19)
Installation Archives (see page 20)
Installation Sets (see page 21)
Features of CA Introscope Integration for CA NSM (see page 21)
User Rights (see page 22)
Installation Scenarios (see page 22)
Installation Modes (see page 22)
Install using the GUI Installer (see page 23)
Install using Silent Mode (see page 25)
Install Using the Console Mode (see page 27)
Re-install CA Introscope Integration for CA NSM (see page 27)
Install on a Machine with an Existing Integration (see page 28)
Verify the Installation (see page 29)
Uninstall CA Introscope Integration for CA NSM (see page 29)
Remove CA Introscope to Unicenter NSM Integration Release
1.x
Previous versions of this integration pack, CA Introscope to Unicenter NSM Integration,
have to be first manually removed from your computer. Then, you can install CA
Introscope Integration for CA NSM successfully. If you install CA Introscope
Integration for CA NSM without removing the previous version of the integration, data is
duplicated in the CA NSM WorldView repository. If the same CA Introscope Enterprise
Manager alerts are configured, duplicate alert notifications are created in the Event
Console.
To delete the previous version, remove components from the following areas manually:
Introscope Enterprise Manager host Remove the integration pack from the
Enterprise Manager (see page 16).
Remove the Integration Pack from the Enterprise Manager


NSM Bridge Proxy host Remove the integration pack from the NSM Bridge Proxy
(see page 16).
Unicenter WorldView host Remove the integration pack from Unicenter
WorldView (see page 16).
Unicenter Management Portal host Remove the integration pack from Unicenter
Management Portal (see page 17).
WorldView Repository host Remove objects from the WorldView repository (see
page 17).
CA Introscope web services API/SDK 7.2 Remove the CA Introscope web
services API/SDK 7.2 (see page 18).
Remove the Integration Pack from the Enterprise Manager
To install CA Introscope Integration for CA NSM successfully, ensure all the previous
versions of this integration are removed from your computer.
Follow these steps:
1. Go to the <EM_Home> directory on the Enterprise Manager host.
2. Go to the <EM_Home>/ext directory and remove NsmBridge-EM.jar.
3. Go to the <EM_Home>/config directory and remove WilyNsmBridge.properties.
4. Go to the <EM_Home>/webapps directory and remove AgentDashboard.war and
castylesr2.war.
Remove the Integration Pack from the NSM Bridge Proxy
Follow these steps:
1. Uninstall the CA Introscope NSM Bridge Proxy service by running
UninstallApp-NT.bat from the introscope\nsmbridge\jsw\bin directory.
2. Go to the NSM Bridge Proxy host and remove the introscope\nsmbridge directory.
Remove the Integration Pack from Unicenter WorldView
To remove a previous integration pack from Unicenter WorldView, go to the Unicenter
WorldView host and remove IntroscopeAgentDashboard.rhp from the <NSM/CCS root
dir>/WVEM/BIN directory.
Remove the Integration Pack from Unicenter Management Portal


Remove the Integration Pack from Unicenter Management
Portal
Follow these steps:
1. Go to the Unicenter Management Portal host and select UMP, Manage
Components.
2. Click the Connection hyperlink for the Unicenter WorldView Management
component.
3. Click the Delete hyperlink and OK.
4. Click OK to confirm you want to delete the data source.
5. Click Back.
6. Click the Connection hyperlink for the Introscope Dashboard component.
7. Click the Delete hyperlink and OK.
8. Click OK to confirm you want to delete the data source.
9. Click Back.
10. Exit the Unicenter Management Portal.
Remove Objects from the WorldView Repository
Follow these steps:
1. Click the Start button on the Windows platform, point to Programs, and navigate to
Computer Associates, Unicenter, NSM WorldView, Object Browser,
ManagedObject, BusinessView.
2. From the right pane under WilyBV, right-click objects, select Delete Object, then
select the Delete child objects, and click OK.
3. Select Host, Windows_NetServer from the left pane.
4. Delete all instances of Wily and WilyAgent.
5. Delete Classes using Computer Associates, Unicenter, NSM, WorldView, Class
Wizard.
6. Select the Modify Existing Class check box.
Remove the Introscope Web Services API/SDK 7.2


7. Expand ManagedObject.
8. Expand BusinessView.
9. Click WilyBV.
10. Click Delete Class.
11. Click Yes to confirm the action.
12. From ManagedObject, expand Host and Windows_NetServer.
13. Click Wily.
16. Click WilyAgent.
19. Exit the system.
The web services API/SDK version 7.2 must be removed. The war and jar files must be
manually removed from your computer to install CA Introscope Integration for CA NSM
successfully.
Follow these steps:
1. Go to <Introscope_Home>\ext and remove IscopeAlertsExt-EM.jar.
2. Go to the <Introscope_Home>\webapps directory and remove
introscope-web-services.war and castylesr2.war.
Pre installation Requirements
Verify the following requirements before installing CA Introscope Integration for CA
NSM:
Verify that your system contains the components necessary for the features you
want to install Feature prerequisites (see page 19).
Download the installation files from the archive that best suits your
environmentInstallation archives (see page 20).
Familiarize yourself with the installation sets to help you determine which is the
best fit for your environmentInstallation sets (see page 21).
Feature Prerequisites


Familiarize yourself with the CA Introscope Integration for CA NSM features to
help you determine which is the best fit for your environmentCA Introscope
Integration for CA NSM features (see page 21).
Verify that the person performing the installation has the appropriate user rights
assignedUser rights (see page 22).
Determine what installation scenario and mode best suits your
environmentInstallation scenarios (see page 22) and Installation modes (see
page 22).
Feature Prerequisites
You must have at least one of the NSM components that are installed before proceeding
with installing the CA Introscope Integration for CA NSM.
Use this table to familiarize yourself with the prerequisites for this CA Introscope
Integration for CA NSM features:
Required Components
CA Introscope Integration for NSM
Windows Server 2003 operating system
Administrator rights
Event Management - Event Agent (included with 11.1 SP1 or higher)
WorldView - Administrative Client (included with 11.1 SP1 or higher)
Operating System Support
CA Introscope Integration for NSM Server
Management Command Center (included with 11.1 SP1 or higher)
Integration for Portal Server
Unicenter Management Portal (included with 11.1 SP1 or higher)
CA NSM Support
See the CA APM Compatibility Guide for the supported versions of CA
NSM.
Installation Archives


Required Memory
The minimum memory requirement for a computer hosting CA NSM
Integration product is 2 GB.
Virtual and Physical Environment Support
The integration must be on the same Virtual host as the NSM Server.
The integration is supported in physical and virtual environments; verify that
the sizing requirements of NSM are met with more capacity for the integration.
The integration pack works with any NSM version higher than 11.1 SP1, but it
has only been certified with NSM 11.2P version 1.
Installation Archives
Installation archives for Windows platforms and its contents vary depending on the
downloaded package.
Windows:
CA_APM_Introscope_NSM_Integration_<VersionNumber>Windows_Installer.zip

Archive contents:
Apache-tomcat-5.5.25.zip
These files are applicable only to the Windows platform. They are required to install
the CA Introscope Integration for NSM.
IntroscopeIntegrationNSM.zip
the Integration for NSM Server.
IntroscopeIntegrationPortal.zip
the Integration for Portal Server.
install.exe
The installer executable for the Windows Server platform.
silentInstallerSample.properties
The properties file necessary to install CA Introscope Integration for CA NSM using
silent mode.
More Information

Installation Sets


Installation Sets
Use installation sets to install the entire set of product features, or components
applicable only to your environment. The installer includes a drop-down list of preset
installation options that include:
CA Introscope NSM Integration Server
CA Introscope Integration for CA NSM.
CA NSM Server
Integration for NSM Server.
CA NSM Management Portal Server
Integration for Portal Server.
Custom
User can select features.
Features of CA Introscope Integration for CA NSM
The integration offers various features for various platforms. The following section helps
you determine which features best suit your environment.
CA Introscope Integration for CA NSM
Applicable only for the Windows Server platform where you want to install
Integration service.
Provides the connection between CA Introscope and CA NSM.
Integration for CA NSM Server
Applicable only for the Windows Server platform where you want to install files
specific to NSM Server to view dashboards.
Provides the Administration GUI.
Provides support for NSM Management Command Center and 2D Map.
Integration for Portal Server
Applicable only for the Windows Server platform where you want to install files
specific to Portal Server to launch dashboards from Portal Explorer.
Provides support for the Unicenter Management Portal.
User Rights


User Rights
You must have the proper user rights to install the CA Introscope Integration for CA
NSM.
Windowsthis platform requires you to have administrator rights.
Installation Scenarios
Determine which installation scenario best suits your environment:
Install using the GUI Installer (see page 23)Use if you are installing the integration
for the first time on your computer and you have no other integration packs on
your computer.
Re-install CA Introscope Integration for CA NSM (see page 27)Use if you have
installed CA Introscope Integration for CA NSM and you want to re-install or add a
feature of the same integration pack.
Install on a Computer with an Existing Integration (see page 28)Use if you have
other integrations on your computer.
Installation Modes
The following modes are available when installing the integration pack:
GUI Installera series of windows that guide you through the installation and
summarize the results when complete. The installer defaults to GUI mode on
Windows Server platforms.
Consolea series of text prompts that guide you through the installation and
summarize the results when complete. Use console mode to install on computers
without video cards, or Xservers.
Silentinvoked from the command line, the silent mode installer obtains input
from a specified response file. The silent mode installer eases the process of
performing multiple installations. The installer runs in the background and does not
provide outputyou check the install log to verify the installation results.
More information

Install using the GUI Installer


We recommend that you use the GUI installer if you are installing CA Introscope
Integration for CA NSM for the first time and the computer has no other integration
pack that is installed on it.
Use the GUI installer to install CA Introscope Integration for CA NSM on a Windows
platform.
Note: If the installation fails for any feature or combination of features, the log file,
CAWily_Introscope_NSM_IntegrationPack_InstallLog.log, is placed on the desktop for
Windows. The log file is located in the <USER_INSTALL_DIR>\<PRODUCT_DIR> directory.
Follow these steps:
1. Download the installation archive for your platform:
Windows:
CAWily_Introscope_NSM_IntegrationPack_<VersionNumber>Windows_Installe
r.zip
2. Extract the archive into a temporary folder.
The installation archive contents are extracted to the location.
3. Run the GUI:
Windows: Double-click install.exe.
The GUI launches.
4. Select the Install Set check box and any check boxes for more features you want to
install.
5. Depending on the features that are installed, some or all of these guidelines must
be followed when entering information.
The Installation Folder screen appears.
6. By default, the default Installation folder is C:\Program
Files\CAWily\IntegrationPack. If you specify a different location, verify that a valid
folder name is entered and do not leave the field empty and click Next.
The Administrators Credentials screen appears.
7. If the Integration Pack user check box is selected, the installer uses the
administrator user as an Integration Pack user. By default this check box is selected.
If you do not want to use the same credentials for the integration pack user, clear
the Use this user as the Integration Pack user check box. Enter a user ID and
password for the Integration Pack user and click Next.
If you are installing the CA Introscope Integration for NSM, the Tomcat Server
Ports screen appears.


8. If you are configuring Tomcat Server Ports, then enter the necessary values and
click Next.
Enter a valid value from 1024 through 65535 in the Connection Port field that is
not in use.
Enter a valid value from 1024 through 65535 in the Shutdown Port field that is
not in use.
9. If you are installing the CA Introscope Integration for NSM, the GUI installer screen
appears. Enter the necessary values and click Next.
The Installation Complete screen appears. Thereafter, depending on what you have
selected to install the GUI installer screens vary.
10. Select the Launch Configuration UI check box to launch the CA Introscope
Integration for CA NSM configuration UI.
The shortcut for the configuration UI is created in the
<USER_INSTALL_DIR>\<PRODUCT_DIR> and/or on the Windows desktop.
11. Click Done to complete the installation.
After Introscope Integration for CA NSM has been installed successfully, the
following directory structure is created:
<IntegrationPack_Home>\CAWily_Introscope_NSM_IntegrationPack
More information
Installation Archives (see page 20)
Installation Sets (see page 21)
Features of CA Introscope Integration for CA NSM (see page 21)
Using the CA NSM Configuration UI (see page 35)

Use the Integration Pack Configuration UI
If you use the Introscope Integration Pack GUI installer, the integration pack
configuration user interface opens when the installation is complete if the Launch
Configuration UI check box is selected in the last screen of the wizard. This is applicable
only for the Windows platform.
Use one of the following methods to launch UI:
Double-click the shortcut icon on the Windows desktop.
Assuming you selected defaults when installing the integration pack, you can also
use the following URL in a browser: http://<installation
host>:8082/CA-Wily-Introscope-NSM-IP/.
Install using Silent Mode


This section explains how to install the CA Introscope Integration for CA NSM using the
silent installation mode. When installing in silent mode, configuration values are read
from the properties file so no user interaction is required and installation proceeds
unattended.
User configuration values for the silent installer are stored as a set of variables in the
silentInstaller.properties file. You set these variables by editing the
silentInstallerSample.properties file that is provided and renaming it.
Include the full path when executing commands if this file is not located in the same
directory as install.exe. You can save the file with any name to any location.
Note: If the installation fails for any feature or combination of features, the log file, CA
APM_NSM_IntegrationPack_InstallLog.log, is placed on the desktop for Windows. The
log file can be found in the <USER_INSTALL_DIR>\<PRODUCT_DIR> directory.
Follow these steps:
1. Edit and save the silentInstallerSample.properties file provided in the installation
archive and rename it to silentInstaller.properties.
2. Use the following command to install in silent mode:
Windows:
install.exe i silent f <installer_properties_filename_with_full_path>
If the silent installation fails, a silent.install.failed.txt file is created. This file provides
more details and is located in the directory where you have launched the installation
from.
More information
Silent Installer Properties (see page 25)

Silent Installer Properties
This section explains the variables in the silentInstallerSample.properties file.
Important! If any variable value is not set correctly, installation can fail or provide
unintended results. Use caution when editing the installer file.
IA_CHOSEN_INSTALL_FEAT, URE_LIST=
Select the features that you want to install.


To install more than one feature, separate the features with a comma:
IntegrationPackrequired to install the CA Introscope Integration for NSM
feature.
IntegrationNSMrequired to install the Integration for NSM Server feature.
IntegrationPortalrequired to install the Integration for Portal Server feature.
Example:
IA_CHOSEN_INSTALL_FEATURE_LIST=IntegrationPack, Integration NSM
USER_INSTALL_DIR
Installation folder.
When setting paths on Windows systems, the backslash character must be escaped
(doubled). For example:
C:\\Program Files\\CAWily\\IntegrationPack
USER_TOMCAT_INPUT_USER
User name of a valid Tomcat administrator. This value must not be empty.
USER_TOMCAT_INPUT_PWD
Password of a valid Tomcat administrator. This value must not be empty.
USER_TOMCAT_INPUT_CONFIRM_PWD
Provide the same password as for USER_TOMCAT_INPUT_PWD.
USE_SAME_TOMCATUSER_FOR_IP
Set to 1 if you want to use the same Tomcat user credentials for the Integration
Pack user. If not, set to 0.
If set to 1, the following variables are ignored:
USER_IP_INPUT_USER
USER_IP_INPUT_PWD
USER_IP_INPUT_CONFIRM_PWD
USER_IP_INPUT_USER
Valid Integration Pack user name. This value must not be empty and it must not be
the same as the Tomcat user name.
USER_IP_INPUT_PWD
Valid Integration Pack user password. This value must not be empty.
USER_IP_INPUT_CONFIRM_PWD
Provide the same password as for USER_IP_INPUT_PWD.
Install Using the Console Mode


USER_TOMCAT_CONNECTION_PORT
Tomcat connection port. The default value is 8082.
Note: You can change the connector port number by editing the server.xml in the
WILYNSM_HOME\apache-tomcat-5.5.25\conf directory.
USER_TOMCAT_SHUTDOWN_PORT
Tomcat shutdown port. The default value is 8005.
IA_EM_HOME_DIR
Introscope installation folder.
When setting paths on Windows systems, the backslash character must be escaped
(doubled). For example:
On Windows, it would look like:
C:\\Introscope
USER_INPUT_LAUNCH_UI
Set to 0. This value is used to launch the configuration UI on Windows. However, it
does not launch the configuration UI in silent install mode.
Install Using the Console Mode
This section explains how to install the CA Introscope Integration for CA NSM from the
console.
If the installation fails for any feature or combination of features, the log file, CA
APM_NSM_IntegrationPack_InstallLog.log, is placed on the desktop for Windows. This
file can be found in the <USER_INSTALL_DIR>\<PRODUCT_DIR> directory.
To install from the console, type the following command:
Windows: install.exe i console
Re-install CA Introscope Integration for CA NSM
Re-installing CA Introscope Integration for CA NSM or any of its features requires a
slight variation in the installation process when you use the GUI Installer for these
features:
CA Introscope Integration for NSM:
You do not have to specify a path for the Installation folder.
Install on a Machine with an Existing Integration


You do not have to enter administrator credentials for the Tomcat server,
Tomcat ports, or the integration pack user credentials. The Installer obtains the
credentials for the existing integration pack.
The properties file, IscopensmProperties.xml, is preserved.
The Tomcat server requires a restart.
Introscope Integration for NSM Server:
Integration Pack for Portal Server:
When you install CA Introscope Integration for CA NSM on a computer with an existing
integration pack using the console and silent modes, the procedures do not vary.

More Information

Install on a Machine with an Existing Integration
Installing CA Introscope Integration for CA NSM or any of its features on a computer
with an existing integration pack requires a slight variation in the installation process
when you use the GUI Installer for these features:
CA Introscope Integration for NSM:
You do not have to enter administrator credentials for the Tomcat server or
Tomcat ports. The Installer obtains the credentials for the existing integration
pack.
If you select the Use Tomcat Administrator as the Integration Pack user check
box, then you do not have to enter user credentials for the integration pack.
The Installer obtains the user credentials for the existing integration pack. If
you do not select the check box, enter user credentials for the integration pack.
The Tomcat server requires a restart.
Introscope Integration for NSM Server
Verify the Installation


Integration Pack for Portal Server
When you install CA Introscope Integration for CA NSM on a computer with an existing
integration pack using the console and silent modes, the procedures do not vary.
More Information

You can verify that CA Introscope Integration for CA NSM was installed successfully, by
launching the configuration user interface. Using the CA NSM configuration UI (see
page 35).
Uninstall CA Introscope Integration for CA NSM
To remove the CA Introscope Integration for CA NSM, use the Uninstaller.
When you run the executable, all CA Introscope Integration for CA NSM features are
removed except for the Introscope objects. Introscope objects must be removed from
the WorldView repository manually using the Object Browser or Management
Command Center.
Follow these steps:
1. Go to
<product_home>\CAWily_Introscope_NSM_IntegrationPack\CAWily_Introscope_NS
M_IntegrationPack.
2. Double-click Uninstall CAWily_Introscope_NSM_IntegrationPack.exe.
The Uninstaller launches.
3. Click Uninstall to remove the CA Introscope Integration for CA NSM.
More information
Remove CA Introscope Objects (see page 30)



Remove CA Introscope Objects
If you uninstall the CA Introscope Integration for CA NSM, remove CA Introscope
objects from the WorldView repository manually. You can remove from the
Management Command Center or using the Object Browser. However, we recommend
that you use the Management Command Center because you can delete multiple
objects from a class in a single action.
To remove CA Introscope objects from the Management Command Center:
1. Open Management Command Center.
The Management Command Center console page appears.
2. From the drop-down list in the left pane, select Business Service Views.
3. Right-click Introscope Enterprise Manager and click Delete.
A message appears confirming the action.
4. Select the Delete child objects (irreversible) check box and click Yes.
All CA Introscope objects are deleted.
To delete CA Introscope objects from the Object Browser:
1. Open Object Browser.
2. From the tree view in the left pane select TNGRoot, ManagedObject,
IntroscopeEnterpriseManagers.
The following classes appear:
IntroscopeAgent
IntroscopeAlert
IntroscopeEM
IntroscopeHost
IntroscopeManagementModule
IntroscopeProcess
3. Select a class.
All objects belonging to that class appear in the right-hand pane.
4. Right-click an object from the right-hand pane and select Delete.
A message appears confirming the action.
5. Select the Delete child objects check box and click OK.
6. Repeat the steps necessary to delete an object until all of the objects belonging to a
particular class have been deleted.
After you have deleted all CA Introscope objects from all of the classes, delete the
classes.
7. Use Computer Associates, Unicenter, NSM, WorldView, and Class Wizard to delete
classes.


8. Select the Modify Existing Class check box.
9. Expand TNGRoot and ManagedObject.
10. Expand IntroscopeEnterpriseManagers.
11. Select a class.
12. Select Delete Class.
13. Click Yes.
14. Repeat the steps necessary to delete all IntroscopeEnterpriseManagers classes.
15. Exit the system.
After you have deleted all CA Introscope classes, CA Introscope Integration for CA
NSM is uninstalled successfully.


Chapter 3: Configuring and Managing
Whats Monitored

This chapter provides instructions for configuring the CA Introscope Integration for CA
NSM.
Overview (see page 33)
Configure the Alternate Bind Address (see page 34)
Configure the Unicenter Management Portal (see page 34)
Configure CA NSM (see page 39)
Overview
After you have installed CA Introscope Integration for CA NSM and its components,
configure its settings using the following web-based configuration GUIs:
CA Introscope Integration for CA NSM configuration UIConfigures the host of
Enterprise Manager, CA NSM WorldView repositories, CA NSM Event Manager,
alerts to monitor, map alert statuses, and format alert messages.
Configuration UI for Unicenter Management PortalConfigures the CA NSM Event
Manager host and CA NSM WorldView repositories for the Portal Manager.
More information
Configure the Unicenter Management Portal (see page 34)

Required Configurations
Before you can use CA Introscope Integration for CA NSM, configure the following
settings:
Configure Introscope Enterprise Manager Host (see page 36)
Configure Monitoring (see page 40)
Configure the Alternate Bind Address


Configure the Alternate Bind Address
If you deploy the integration pack on an NSM computer with two network cards, yet the
Enterprise Manager has access to only one due to your network configuration, edit the
IscopensmMisc.properties file to specify the alternate bind address of the NSM server to
which the Enterprise Manager has access. The Enterprise Manager is forced to make a
connection to the NSM server on this network card.
Follow these steps:
1. Go to
<Integration_Home>\apache-tomcat-5.5.25\webapps\CA-Wily-Introscope-NSM-IP\
WEB-INF\config and open IscopensmMisc.properties.
2. Edit this property value as follows:
ALTERNATE_BIND_ADDRESS=[the address/hostname to which the Introscope Enterprise
Manager has access].
3. Restart the Apache Tomcat for CA APM Integration Packs service.

Configure the Unicenter Management Portal
The Unicenter Management Portal displays CA NSM WorldView management data. The
web-based GUI lets you manage data by navigating WorldView objects, viewing alert
statuses, viewing CA Introscope Dashboards, and viewing Enterprise Manager console
messages. However, configure the Unicenter Management Portal.
Follow these steps:
1. Launch Internet Explorer.
2. Enter the Manage Portal URL and port in the address bar. For example:
http://myumpserver:8090.
3. Click Task 1. To configure portal to connect to your WV and Enterprise Manager.
The Manage Components page appears.
4. Click Set UKB to configure the Knowledge Base.
The Manage Configuration page appears.
5. Enter the host name in the Knowledge Base host name field and save the
information.
6. Select the Component check box next to Unicenter Event Management, and then
click the Connection hyperlink to configure the Enterprise Manager connection.
Using the CA NSM Configuration UI


The Manage Data Sources: Unicenter Event Management page appears.
7. Add the servers and select whether you want it to be the default and save your
settings.
8. Select the Component check box next to Unicenter WorldView Management, then
click the Connection hyperlink to configure the WorldView connection.
The Manage Data Sources: Unicenter WorldView Management page appears.
9. Add the servers and select whether you want it to be the default and save your
settings.
The connections are configured.
Configure the following settings with the CA Introscope Integration for CA NSM
configuration GUI:
Configure Introscope Enterprise Manager Host (see page 36).
Configure Monitoring (see page 40)
Configure Message Formatting (see page 41)
Configure Status Mapping (see page 41)
Access the CA Introscope Integration for CA NSM Configuration UI
Use the configuration UI to set CA NSM settings.
To access the configuration UI, go to http://localhost:8082/CA-Wily-Introscope-NSM-IP/
or http://<installation host>:8082/CA-Wily-Introscope-NSM-IP/ where <installation
host> is the host on which the administration GUI was installed.
More Information



Configure Introscope Enterprise Manager Host
In the CA NSM Configuration UI, select the Enterprise Managers for which you want to
generate objects or console messages in the WorldView repository.
The arrow icons can be clicked to sort data ascending/descending in its respective
column. The status icon expresses whether the server is connected or disconnected.
The Connection Status represents the Enterprise Manager status:
Unknownthe connection status was not validated when the information was
entered, and its status is unknown. If you click Refresh Status or select another tab
in the business application, the connection status updates to Connected or
Disconnected.
Connected the Enterprise Manager is up and the Integration Pack service is able
to connect to it.
Disconnectedthe Integration Pack service is unable to connect to the Enterprise
Manager. The Enterprise Manager is either down or wrongly defined, meaning the
credentials or Enterprise Manager host entered was not valid.

More Information
Add an Introscope Enterprise Manager Host (see page 36)
Delete an Introscope Enterprise Manager Host (see page 37)
Edit an Introscope Enterprise Manager Host (see page 38)

Add an Introscope Enterprise Manager Host
Add an Enterprise Manager host if you want to generate objects or messages for its
monitored alerts.
Follow these steps:
1. From the CA Introscope Integration for CA NSM configuration UI, select the
Introscope Enterprise Manager Hosts Configuration tab.
2. Click Add.
The Add Enterprise Manager Host page opens.
3. Enter the information for the required and optional settings:
Host (required)
The name of the computer hosting the Enterprise Manager host and with the
Web Services SDK installed.


Web Server Port (required)
The web server port as specified in the Enterprise Manager configuration file.
User (required)
The user name of the person assigned credentials to the Enterprise Manager.
This user also needs Web Services access.
Password
The password, if applicable, of the user who has been assigned a user name for
the Enterprise Manager.
Enable WorldView Updates
Enables the creation of CA NSM WorldView repository objects from monitored
alerts. To create the objects in CA NSM, the CA NSM WorldView Repository
credentials must be specified on the CA NSM Configuration tab. Configure CA
NSM.
Enable Console Message Updates
Enables console message updates and generates CA NSM Event Console
messages from monitored alerts. To receive alert notifications on the CA NSM
console, the CA NSM Enterprise Manager host must be specified on the CA
NSM Configuration tab. Configure CA NSM.
4. Click one of the available buttons on the right-hand pane:
Validate Connection to verify the credentials that are provided have Web
Service access.
The Validate Connection button only validates the connection. Click OK to add
the Enterprise Manager host.
OK to add the Enterprise Manager host information and return to the previous
page that lists all Enterprise Manager hosts.
An Enterprise Manager Host with an Unknown status is initially added. As you
begin to use the business application or if you click refresh, the credentials are
verified. The status now changes to Connected assuming the credentials are
valid.
Cancel to refrain from adding any Enterprise Manager host details and return
to the previous page.
Delete an Introscope Enterprise Manager Host
Delete an Enterprise Manager host if you no longer want to generate objects or
messages for its monitored alerts.
Follow these steps:


2. Use the check boxes to select the Enterprise Manager host you want to delete.
3. Click the Delete hyperlink in the table header.
A confirmation message appears to verify the action.
4. Click Yes.
Edit an Introscope Enterprise Manager Host
You can edit the Enterprise Manager Host details.
Follow these steps:
2. Click the host name hyperlink in the Host column of the Introscope Enterprise
Managers.
3. Edit any of the necessary details that are entered when the host was added. For
more information.
4. Click any of the following buttons in the right-hand pane to:
Validate Connection to verify the credentials that are provided have Web
Service access.
The Validate Connection button only validates the connection. Click OK to add
the Enterprise Manager host.
OK to add the Enterprise Manager host information and return to the previous
page that lists all Enterprise Manager hosts.
An Enterprise Manager hosts with an Unknown status is initially added. As you
begin to use the business application or if you click refresh, the credentials are
verified. The status is now changed to Connected assuming the credentials are
valid.
Cancel to refrain from adding any Enterprise Manager host details and return
to the previous page.
More information
Add an Introscope Enterprise Manager Host (see page 36)

Configure CA NSM


Configure CA NSM
In the CA Introscope Integration for CA NSM configuration UI, configure CA NSM. After
you configure this setting, the CA NSM WorldView repository creates a business service
view named Enterprise Managers.This view contains CA Introscope objects that are
generated from CA Introscope alerts you choose to monitor. If WorldView updates for
an Introscope Enterprise Manager host are enabled in the Introscope Enterprise
Manager Hosts Configuration tab, then the NSM connection information must be
provided.
More Information
Edit the NSM Enterprise Manager Host (see page 39)
Edit the NSM WorldView Repository (see page 39)

Edit the NSM WorldView Repository
In the CA Introscope Integration for CA NSM configuration UI, edit the connection
information for the NSM WorldView repository. A business service view named
Enterprise Managers contains CA Introscope objects that are generated from CA
Introscope alerts you choose to monitor in this repository.
Follow these steps:
1. From the CA Introscope Integration for CA NSM configuration UI, select the CA
NSM Configuration tab.
2. Click Edit.
3. Update the necessary fields.
4. Click OK to apply the settings or Cancel to return to the previous page.
Edit the NSM Enterprise Manager Host
In the CA Introscope Integration for CA NSM configuration UI, edit the NSM host
information. The NSM Enterprise Manager host contains Event Console messages
generated from CA Introscope alerts you choose to monitor.
Follow these steps:
1. From the CA Introscope Integration for CA NSM configuration UI, select the CA
NSM Configuration tab.
2. Click Edit.
3. Update the necessary fields.
Configure CA NSM


4. Click OK.
Configure Monitoring
In the CA Introscope Integration for CA NSM configuration UI, select which alerts to
monitor. The alert creates objects in the NSM WorldView repository and generate
messages in the NSM Enterprise Manager Console. The items that are displayed on this
page are only the management modules and alerts that are set to active in CA
Introscope.
Follow these steps:
1. Select the Monitoring Tab from the CA Introscope Integration for CA NSM
configuration UI.
2. Use the check boxes to select the alerts you want to monitor.
Note: CA NSM cannot import alerts that use Unicode characters. For these objects
to be viewed in CA NSM, their names must be changed to use only ascii characters.
For more information about this issue, see Knowledge Base Article TEC534282
https://support.ca.com/irj/portal/anonymous/redirArticles?reqPage=search&searc
hID=TEC534282.
3. Click one of the available buttons:
Saveto monitor Enterprise Managers, Management Modules, and Alerts,
which are saved in the configuration file and can be viewed in the Management
Command Center. The selected Enterprise Managers, Management Modules,
and Alerts can be viewed in NSM Management Command Center. If an
Enterprise Manager or Management Module is deselected, it appears as
unknown in NSM. Likewise, if a Management Module or alert was previously
selected and is deselected, it appears as unknown in NSM.
Note: You can view only simple alerts in the Monitor tab.
If you do not see the list of Management Modules under an Enterprise
Manager name, then set the
"introscope.alerts.extension.managementmodules.enable" property in the
IntroscopeEnterpriseManager.properties file. For more information, see the
"Configure the alerts extension" in the CA Application Performance
Management API Reference Guide.
Resetto reset the tree elements to their default values or a previous state.
Refreshto get the updated information about the Enterprise Manager,
Management Module, and alerts from the corresponding Enterprise Manager.
If new alerts or management modules are added to the Enterprise Manager
after starting the integration pack. Refresh the page to get the most recent
information.
Configure CA NSM


Configure Message Formatting
Message formatting lets you specify the format of the alert string and set the data
source value. Formatting replaces certain characters to ease the parsing of the alert in
the NSM Event Console.
Follow these steps:
Message Formatting tab.
2. Enter the data source value in the Console Message Source field.
Identifies the source of the message to the Event Console. The console message is
prefixed with a string that helps identify the source of the message on the NSM
Event Console. The default value is WilyAgent.
3. Enter the format using a mix of text and parameters in the Format field.
Click next to Console Message Parameter Help to expand help on the
parameters available for use in the Console Message Format. This format is used
when generating NSM Enterprise Manager console messages from monitored CA
Introscope alerts. The parameters are replaced with corresponding data from the
alert being used to generate the console message. If you manipulate message
parameters and there are spaces within the parameter tags ("%" and "%"), that
string is not considered when checking for valid parameters.
4. Enter strings to exclude in the Strings to Omit field.
These strings are omitted from the variable values that are substituted in the
message.
5. Click Generate Sample Message Output to verify that the message format appears
as you have specified.
If you decide not to apply the new message format, click Set to Default to reapply
the default format.
Configure Status Mapping
Use this page to map the CA Introscope alert status to the corresponding NSM status
and severity. The mappings apply to all alerts, rather than to a specific management
module or alert.
For example, if you apply the default settings, and the status of CA Introscope alerts
turned Critical, they appear as red objects in 2D Map of CA NSM and Management
Command Center, and are reported with an Error severity in Enterprise Manager
console message of CA NSM.
Configure CA NSM


The default settings are:
Introscope Alert
Status
NSM Managed
Object Status
NSM Event Console
Message Severity
NSM Event Console
Message Color
Normal Normal Success Green
Warning Warning Warning Yellow
Critical Critical Error Red
Unknown Unknown Informational Black
If you choose to change the default settings, the options are as follows:
Introscope Alert Status
Normal
Warning
Critical
Unknown
NSM Settings
NSM Managed Object Status
Normal
Warning
Critical
Unknown
Major
Minor
Down
NSM Event Console Message Severity
Success
Informational
Warning
Error
NSM Event Console Message Color
Black
Red
Orange
Yellow
Configure CA NSM


Green
Blue
Pink
Purple
Follow these steps:
1. From the CA Introscope Integration for CA NSM configuration UI, select the Status
Mapping tab.
2. Select the alert status and NSM object status, Event Console message severity, and
color of your choice.
3. Click Save to apply the settings.
4. Click one of the restore hyperlinks:
Restore Defaultsrestore the NSM status and severity to the default value for
the selected row.
Restore Default Statusrestore the NSM status to the default value for the
selected row.
Restore Default Severityrestore the NSM severity to the default value for the
selected row.
Restore Default Colorrestore the NSM event color to the default value for the
selected row.
5. Click Save to apply the settings.
(Optional) Enable DEBUG logging in the Introscope-NSM bridge
To obtain detailed logs for troubleshooting, you can enable DEBUG logging in the
Introscope-NSM bridge.
Follow these steps:
1. Open the logging file from
<Integration_Home>\apache-tomcat-5.5.25\webapps\CA-Wily-Introscope-NSM-IP\
WEB-INF\classes.
2. Uncomment all the lines that refer to the wily classes.
3. Save and close the file.
4. Restart the Introscope-NSM Bridge again.
Logging is enabled in the DEBUG mode.


Chapter 4: Using CA Introscope
Integration for CA NSM

View CA Introscope objects in Management Command Center (see page 45)
View CA Introscope Objects in the Unicenter Management Portal (see page 47)
View CA Introscope Objects in CA NSM WorldView 2D Map (see page 48)
View CA Introscope Alerts in the CA NSM Event Console (see page 49)
View CA Introscope objects in Management Command Center
The Management Command Center (available with CA NSM version 11.1 sp1 or higher)
provides a hierarchical tree structure for viewing CA Introscope objects. The objects
can be visualized in an infrastructure hierarchy or custom created business service views
hierarchy.
Each monitored object has a set of properties and an associated status. The child object
status propagates up the tree to their parent objects. The parent objects inherit the
worst status of the children objects.
The default class level hierarchy that is published from CA Introscope to CA NSM is as
follows:
ManagedObject
IntroscopeEnterpriseManagers
IntroscopeEM
IntroscopeManagementModule
IntroscopeHost
IntroscopeProcess
IntroscopeAgent
IntroscopeAlert
More information:
Configure Status Mapping (see page 41)
View Introscope Objects in the Management Command Center Tree Hierarchy (see page
46)
View Dashboards of CA Introscope Objects in the Management Command Center (see
page 46)
View CA Introscope Alerts in the Management Command Center Event Console (see
page 47)

View CA Introscope objects in Management Command Center


View Introscope Objects in the Management Command Center Tree Hierarchy
You can view CA Introscope objects in the Management Command Center Tree
Hierarchy. Use the following options to view objects in a tree hierarchy:
Objects appear in various states in the Management Command Center tree hierarchy
that is based on the following rules:
After you have installed and started the integration pack, objects for the
management modules you chose to monitor will appear with a Normal status under
their respective Enterprise Managers if the WorldView update is enabled.
If you monitor a new Management Module, it appears in the Management
Command Center and its status is Normal. The status remains Normal until an alert
is triggered for the management module.
If a Management Module is enabled for monitoring, it appears in the Management
Module with a Normal status. If the Management Module has alerts, it assumes the
status of the alert being monitored with the most critical status.
If you turn off Management Module monitoring, the Management Module objects
have an Unknown status in the Management Command Center.
If you turn on Management Module monitoring, the Management Module objects
have a Normal status in Management Command Center.
If the integration pack is disconnected, all Management Module objects have an
Unknown status.
Follow these steps:
1. Start NSM, MCC.
2. Select Business Service Views from the drop-down list in the left pane to see the
business service view nodes.
3. Right-click Introscope Enterprise Manager objects to see what menu items are
available.
4. Select different views from the right pane to explore CA Introscope objects in
different ways.
View Dashboards of CA Introscope Objects in the Management Command Center
You can view dashboards of CA Introscope objects in the Management Command
Center using the following options.
Follow these steps:
View CA Introscope Objects in the Unicenter Management Portal


1. Select Business Service Views from the drop-down list in the left pane.
2. Select the Introscope Enterprise Managers node, Introscope Management Module
node, Introscope Agent node, or Introscope Alert node.
3. Select the corresponding Introscope dashboard from the drop-down list in the right
pane:
Introscope Enterprise Management Node
Introscope Enterprise Manager Dashboard
Introscope Management Module Node
Introscope Management Module Dashboard
Introscope Agent Node
Introscope Agent Dashboard
Introscope Alert Node
Introscope Alert Dashboard
The dashboard for SiteMinder reporter appears.

View CA Introscope Alerts in the Management Command Center Event Console
Use this option to view CA Introscope Alerts in the Management Command Center
Event Console.
Follow these steps:
1. Start NSM, MCC.
2. Select Enterprise Management from the drop-down menu in the left pane.
3. Select Event Management, Console Logs.
4. Click the Launch Console Logs from the right pane.
View CA Introscope Objects in the Unicenter Management
Portal
The Unicenter Management Portal provides a role-based, personalized, and
consolidated view of Unicenter WorldView managed objects using a web portal
interface. Using Unicenter Management Portal, you can navigate to Introscope
WorldView objects, view object severities, Introscope Dashboards, and Event Console
messages.
View CA Introscope Objects in CA NSM WorldView 2D Map


Follow these steps:
1. Verify that you have installed the Integration Pack for Portal Server.
2. Open a web browser and enter the Unicenter Management Portal URL and port in
the address bar. For example:
http://myumpserver:8090
3. Select the Knowledge tab and then the Library tab.
4. Select Enterprise Management, Unicenter Event Management, Event Console from
the tree in the left pane.
View Event Console messages in the right pane.
From this view:
Click the Log Messages tab to view more details.
Select a message in the bottom pane and click Go to view more details.
Select Business Processes from the left pane and navigate through to see all
Business Service Views for a summary view of Introscope WorldView objects.
From the Unicenter Management Portal View:
Click the Portal Explorer button next to the Introscope Enterprise Managers
BPV in the right pane to open the Portal Explorer.
Navigate to the Introscope objects in the left pane to view more details.
Select an Introscope object from the left pane and click Go to see the available
dashboards:
Introscope Enterprise Manager Dashboard
Introscope Management Module Dashboard
Introscope Agent Dashboard
Introscope Alert Dashboard
View CA Introscope Objects in CA NSM WorldView 2D Map
CA NSM WorldView 2D Map provides a visual tool for exploring CA Introscope objects.
Follow these steps:
1. Start NSM, WorldView, 2D Map.
2. Double-click objects to see the next level of details.
The WorldView 2D Map window appears.
View CA Introscope Alerts in the CA NSM Event Console


From this view, you can right-click an CA Introscope object and can select the
Investigate options. The corresponding CA Introscope dashboard appears in a new
window.
View CA Introscope Alerts in the CA NSM Event Console
The CA NSM Event Console lets you monitor the status of events, respond to abnormal
events as they occur, and rectify critical situations immediately. The console organizes
the events in pages that you can navigate. The console has the returned view of events.
You can filter and search for specific events from this view.
Follow these steps:
1. Start NSM, Enterprise Management, Enterprise Manager Classic.
2. Double-click Windows, Event, Console Logs to view log messages.
The Enterprise Manager Console window appears.
Refresh to see the latest event messages or double-click a message to view the alert
message details.
Note: When you launch a CA Introscope dashboard, you are required to enter your
login credentials of Enterprise manager.


Chapter 5: Integrating CA NSM with CA CEM

CA Customer Experience Manager (CA CEM) collects important performance
information about business services and transactions. This information can be shared
with CA NSM, the management solution from CA. CA NSM helps improve infrastructure
performance by monitoring network and systems elements.
CA CEM Integration for Network and Systems Management integrates CA NSM with CA
CEM so you can monitor transactions in addition to monitoring overall network health.
Note: "Business process" in CA CEM is the same as "business service." The terms vary
depending on the CEM version you have installed. You can use the terms
interchangeably in this chapter.
About CA NSM with CA CEM (see page 52)
CA NSM Integration Overview (see page 53)
CA NSM to CA CEM Integration Terminology (see page 53)
About CA NSM with CA CEM


About CA NSM with CA CEM
You can use CA NSM to view and investigate CA CEM Incidents almost immediately,
which gives you added insight into the health of your network. Slow response times or
poor application performance affects users. CA NSM helps you see such users and help
you identify the root cause of problems. You can then take corrective action.
The CA CEM Integration for CA NSM consists of three components:
CEM-NSM Bridge
Custom Management Command Center dashboards
Unicenter Management Portal integration
The following diagram shows how the CA CEM Integration Pack for CA NSM works at a
high level.

The CEM-NSM Bridge dynamically creates NSM WorldView objects for each CA CEM
business service, business transaction, and user group, and updates them in the NSM
repository. The CEM-NSM Bridge also receives notifications for any changes in CA CEM
data, including incidents and severity changes, and updates the NSM repository with
these changes. CA CEM incidents are reported in the NSM Event Console.
CA NSM Integration Overview


CA NSM Integration Overview
The CA CEM Integration for CA NSM controls the CA CEM to CA NSM integration, which
allows information bridging between CA CEM and NSM. Once you install the Integration,
CA CEM objects and their status appear in CA NSM and CA CEM incidents appear in the
Unicenter Event Console. This integration calculates the severity of each CA CEM object
that is based on the impacting incident having the highest business impact. Any changes
in severity are reflected in NSM in real time (with an approximate 40-second delay).
Real-time updates are discussed in the following sections:
Receiving and updating CA CEM objects in the CA NSM WorldView repository
Receiving and updating the status of CA CEM objects

The CEM-NSM Bridge maintains CA CEM objects such as business services, business
transactions, user groups, and their status in NSM. The bridge also populates CA CEM
incidents to the NSM Event Console.
More information:
Using CA NSM with CA CEM (see page 67)

CA NSM to CA CEM Integration Terminology
An important aspect of product integration is terminology. Learn the language of the
products that are unfamiliar to you. Understand how terms and definitions in CA CEM
map to the terms in CA NSM.


CA NSM Terms
The following CA NSM terms are related to the product integration.
2D Map
A two-dimensional visual tool for viewing and managing WorldView objects.
Accessed within Management Command Center or the WorldView Classic GUI.
Business Service View (BSV)
A high-level WorldView object that is used to contain objects that are commonly
related to a business service. A logical group of managed objects that you create
based on any criteria, such as geographic location or business service. The BPV acts
as a filter that displays only relevant objects.
Dashboard
Displays real-time information that is related to objects in Unicenter NSM
WorldView. Accessible from the Unicenter Management Command Center or MP.
Event Manager
Monitors and consolidates message activity from event sources. You can identify
event messages that require special handling and can initiate a list of actions for
handling an event. Facilitates event correlation and root cause analysis.
Event
An event is a significant situation that indicates a change in your enterprise. When
an event occurs, a message is sent to the Event Console.
Event Console
Shows network activity in the form of event messages. All events are forwarded and
stored here.
Management Command Center
A visualization tool that displays a consolidated view across all managed
components, providing the primary interface for managing your enterprise.
Unicenter Management Portal
A role-based, dynamic, personalized, and consolidated view of Unicenter
WorldView managed objects using a web portal interface.
CA CEM Object
A business service, business transaction, or user group.
WorldView Repository
Where CA NSM WorldView objects and their class definitions are stored.


CA NSM to CA CEM Term Mapping
Products can have different evolution cycles and different core audiences. These
differences often mean that the product terms and definitions also differ.
Sometimes there is a one-to-one mapping (for example, an incident in one product can
be a ticket in another). And sometimes the same term can have a slightly different
meaning in a different product, which can be confusing.
See the CA APM Overview Guide for all glossary terms and definitions.
The following term mappings help you navigate the product integration.

CA CEM Term CA NSM Term Mapping
business service No exact equivalent in CA NSM, although there is a Business Service View (a
high-level object in WorldView). The Business Services nodes in the CA NSM
Management Command Center tree map to the CA CEM business service.
business transaction No equivalent in CA NSM. The Business Transactions nodes in the CA NSM
Management Command Center tree map to the CA CEM business service /
business transaction / transaction definitions.
defect No equivalent in CA NSM. A CA CEM defect is a single transaction opportunity that
failed.
impact level CA NSM WorldView status is similar to a CA CEM impact level.
incident A CA NSM event is similar to a CA CEM incident.
transaction No equivalent in CA NSM. A CA CEM transaction is a collection of business
transaction components that generally represents one request to the application
server.


Chapter 6: Installing CA CEM Integration
for CA NSM

The following section describes how to install the CA CEM-NSM Bridge client part of the
CA CEM-CA NSM integration.
Install the CA CEM Integration Pack for CA NSM (see page 57)
Install Custom Dashboards for Unicenter Management Command Center (see page 59)
Install the CA CEM Integration Pack for CA NSM
The CA CEM Integration for CA NSM can be installed on one of the following
components:
CA NSM WorldView Manager (version 3.1 or r11.1 SP1)
CA NSM Admin Client system
The NSM client must be version r3.1 for NSM 3.1 WorldView
The NSM client must be version r11.1 SP1 for NSM r11.1 SP1 WorldView
On a client, establish a connection to WorldView by defining a WorldView
Logical Repository
The minimum requirements for a CA NSM Admin Client are:
Database Client (SQL for NSM)
Note: The SQL version of the client must match the NSM server.
WorldView Administrative Client
NSM Event Management Agent
Follow these steps:
1. To download the cem-nsm-bridge.zip file, use the link in the email.
2. Install or use an existing Tomcat servlet engine.
Supported Tomcat versions:
5.5
6.0
The Tomcat servlet engine must be running on the specified JRE version. See the CA
APM Compatibility Guide for version number information.
Install the CA CEM Integration Pack for CA NSM


3. Stop the Tomcat instance on which the bridge is installed before installing the CA
CEM-CA NSM Integration.
Note: If an existing version of CEM-NSM bridge exists, then delete the folder
<TOMCAT_HOME>/webapps/cem-nsm-bridge.
4. Unzip the cem-nsm-bridge.zip file in the <TOMCAT_HOME> directory.
For example: C:\Program Files\Apache Software Foundation\Tomcat 5.5.23
5. If you are using Tomcat 6.0, update the following property in the
<TOMCAT_HOME>/conf/catalina.properties file:
Property Name: shared.loader
Property Value: ${catalina.home}/shared/classes,${catalina.home}/shared/lib/*.jar
For example:
shared.loader=${catalina.home}/lib,${catalina.home}/lib/*.jar,${catalina.home
}/shared/classes,${catalina.home}/shared/lib/*.jar
Verify the Integration Installation
Verify that the integration installation copies the following set of files under
TOMCAT_HOME:
<TOMCAT_HOME>/webapps
cem-nsm-integration.war
<TOMCAT_HOME>/cemNsmBridge
cemBridgeConnectorMetadata.properties
nsmBridgeConnectorMetadata.properties
SetCemBridgeConnector.bat
SetNsmBridgeConnector.bat
version.txt
<TOMCAT_HOME>/shared/classes
cemBridgeConnector.properties
nsmBridgeConnector.properties
cemNsmBridge.properties
<TOMCAT_HOME>/shared/lib/
commons-codec-1.3.jar
jline-0.9.9.jar
utilities.jar
Install Custom Dashboards for Unicenter Management Command Center


<TOMCAT_HOME>/bin/ext/tngjdklib
8 tngjdk*.dll files
Install Custom Dashboards for Unicenter Management
Command Center
The following section describes how to install the custom dashboards for Unicenter
Management Command Center.
Note: These custom dashboards are not supported in NSM 3.1 systems. Do not install
the following RHP files on NSM 3.1 systems.
Follow these steps:
1. Use the CA APM software download site link in the email to download the
NSMDashboards.zip file.
The zip file contains four rhp files.
Note: If you have both an NSM Admin Client and an NSM WorldView Manager,
install the rhp files on both systems.
2. Unzip the contents of NSMDashboards.zip, including the directory structure, to the
NSM or CCS WorldView bin directory <CCS_OR_NSM_WV_BIN_DIR>.
Possible values for <CCS_OR_NSM_WV_BIN_DIR> are:
C:\Program Files\CA\SC\CCS\WVEM\BIN
C:\NSM\bin
C:\TND\bin
Verify that the installation copies the following set of files under C:\Program
Files\CA\SC\CCS\WVEM\BIN:
CEMTessDashboard.rhp
CEMBPDashboard.rhp
CEMBTDashboard.rhp
CEMUGDashboard.rhp
Note: First install patch QO92983 for NSM r11.1 SP1 and then launch Management
Command Center dashboards.
Install Custom Dashboards for Unicenter Management Command Center


Set CA NSM Connection Information
The SetNsmBridgeConnector.bat file prompts you for the CA NSM WorldView Repository
host, username, password, and Enterprise Manager console host. This information is
needed before proceeding.
Follow these steps:
1. Launch a command window.
2. Change your directory to <TOMCAT_HOME>/cemNsmBridge.
3. Execute the SetNsmBridgeConnector.bat batch file.
4. Enter your connection information for the CA NSM host when prompted.
The settings are echoed and automatically set in the CA NSM connection properties
file, nsmBridgeConnector.properties (in <TOMCAT_HOME>/shared/classes).
Note: Password information is encrypted in the properties file.
Configuration information is contained in properties files, which include connection
settings and CA CEM subscribed topics, and other information. The properties files are
described in CA CEM-NSM Bridge properties (see page 83). The property file default
connection is for one CA CEM system but it can be modified to connect more CA CEM
hosts. For information about reducing the number of CA CEM managed objects in CA
NSM, Modify the hierarchy of CA CEM managed objects (see page 74).


Chapter 7: Configuring the CA CEM and
NSM Connections

The following sections explain how to set up the CA CEM and NSM connections.
Set CA CEM Connection Information (see page 61)
Configure Unicenter Management Portal with CA CEM (see page 61)
(Optional) Enable DEBUG logging in the CEM-NSM bridge (see page 63)
CA CEM-NSM Bridge Maintenance (see page 63)
Set CA CEM Connection Information
The SetCemBridgeConnector.bat file prompts you for the CA CEM host, port, username,
and password. This information is needed before proceeding.
Follow these steps:
1. Launch a command window.
2. Change your directory to <TOMCAT_HOME>/cemNsmBridge.
3. Execute the SetCemBridgeConnector.bat batch file.
4. Enter your connection information for the CA CEM host when prompted.
The settings are echoed and automatically set in the CA CEM connection properties
file, cemBridgeConnector.properties (in <TOMCAT_HOME>/shared/classes).
Note: Password information is encrypted in the properties file.
Configure Unicenter Management Portal with CA CEM
This section describes how to configure the Unicenter Management Portal to access CA
CEM objects. Using Unicenter Management Portal (MP), you can navigate to CA CEM
WorldView objects, view object severities, CA CEM Dashboards, and Event Console
messages.
Configure Unicenter Management Portal with CA CEM


Follow these steps:
1. Start Unicenter MP by launching a browser.
2. Type the Unicenter MP URL and port in the address bar.
For example:
3. Select UMP Administration from the drop-down list.
4. Click the Task 1. Manage Components link to configure Unicenter Management
Portal to connect to CA CEM objects.
The Manage Components screen appears.
5. Click Set UKB to configure the Knowledge Base.
The Manage Configuration screen appears.
6. Enter the host name for the Knowledge Base and click save (and Done).
The Knowledge Base server is where CA NSM WorldView Manager is installed.
You are returned to the Manage Components screen.
7. Find Unicenter Event Management in the list and click Connection to configure the
Enterprise Manager connection by specifying a data source.
8. Find Unicenter WorldView Management in the list and click Connection to
configure the WorldView connection by specifying a data source.
The configured connections appear in the Manage Components screen.
9. To view CA CEM objects in Unicenter MP, View CA CEM objects in Unicenter
(Optional) Enable DEBUG logging in the CEM-NSM bridge


(Optional) Enable DEBUG logging in the CEM-NSM bridge
To obtain detailed logs for troubleshooting, you can enable DEBUG logging in the
CEM-NSM bridge.
Follow these steps:
1. Open the logging file from
Apache_tomcat\webapps\cem-nsm-integration\WEB-INF\classes.
2. Remove the "#" from all the lines that refer to the wily classes:
log4j.logger.com.timestock.tess.webservices.api=debug
log4j.logger.com.timestock.tess.webservices.impl=debug
log4j.logger.com.timestock.tess.webservices.muse.extensions=debug
3. Save and close the file.
4. Restart the CEM-NSM bridge.
Logging is enabled in the DEBUG mode.

CA CEM-NSM Bridge Maintenance
The following sections describe how to maintain the CA CEM-NSM Bridge.
CA CEM-NSM Bridge Start/Stop
To start/stop the CA CEM-NSM Bridge, start/stop the Tomcat server engine once
the configuration steps are complete.
Other Maintenance Information
The log file by the bridge can be found under
<TOMCAT_HOME>/logs/cemNsmIntegration.log.
The logging can be configured using the log4j.properties file found under
<TOMCAT_HOME>/webapps/cem-nsm-integration/WEB-INF/classes using standard
log4j directives. (The log4j.properties file is created once the Tomcat server is
started.)
Refer to the CA CEM-NSM Bridge properties (see page 83) for details about
modifying these properties.
Restart the Tomcat server after modifying the properties files to see the changes
take effect.


Integrate with Unicenter Management Portal
The following section describes how to integrate the CA CEM Integration for CA NSM
with Unicenter Management Portal. You can install the Unicenter Management Portal
Integration from the Integration on a Unicenter Management Portal system.
Note: Integration is not supported with Unicenter Management Portal 3.1. Do not install
the following portal integration on Unicenter Management Portal 3.1 systems.
Follow these steps:
CEMPortalIntegration.zip file.
The file contains Unicenter Management Portal configuration files and an
installation script.
2. Unzip the contents of CEMPortalIntegration.zip, including the directory structure, to
the Unicenter Management Portal directory. For example:
C:\Program Files\CA\SharedComponents\Unicenter Management Portal
3. Launch a command Window and set your directory to the UMP webpages\cem
folder. For example:
C:\Program Files\CA\SharedComponents\Unicenter Management Portal\webpages\cem
4. Run the install.bat script in this directory.
Verify that the installation copies the following set of files under the Unicenter
Management Portal home directory:
<UMPFOLDER>\content\tndportal\menus\menuItemProfile\cem.xml
<UMPFOLDER>\content\tndportal\menus\menuProfile\cem.xml
<UMPFOLDER>\webpages\cem\cemDashboardLauncher.jsp
<UMPFOLDER>\webpages\cem\install.bat
<UMPFOLDER>\tndportal\lang\UMPMenu_cem.properties
The install batch script adds a few entries to the file:
<UMPFOLDER>\content\tndportal\menus\wvMap.properties
The following lines are added:
CEM_Tess=WV_CEMCEDashboard
CEM_Business_Service=WV_CEMBPDashboard
CEM_Business_Transaction=WV_CEMBTDashboard
CEM_User_Group=WV_CEMUGDashboard



More Information
Integrate with Unicenter Management Portal (see page 64)


Chapter 8: Using CA NSM with CA CEM

This chapter describes how CA CEM integrates with CA NSM.
View CA CEM Objects in CA NSM (see page 67)
View CA CEM objects in Unicenter Explorer (see page 67)
View CA CEM Objects in Management Command Center (see page 69)
View CA CEM Objects in Unicenter WorldView 2D Map (see page 71)
View CA CEM Objects in Unicenter Management Portal (see page 71)
View CA CEM Incidents in the CA NSM Event Console (see page 73)
Receive and Update CA CEM Objects in the CA NSM WorldView Repository (see page 73)
Receive and Update the Status of CA CEM Objects (see page 75)
Customize CA NSM Alarmset Severity Status Mappings (see page 76)
CA NSM Resources (see page 77)
View CA CEM Objects in CA NSM
The following CA NSM components provide ways to view and explore CA CEM objects
and incidents.
View CA CEM objects in Unicenter Explorer
Unicenter Explorer provides a hierarchical tree structure for viewing CA CEM objects
(business services, business transactions, and user groups). The objects can be visualized
in either an infrastructure hierarchy or custom created "Business Service Views"
hierarchy. Each monitored object has a set of properties and an associated status.
Business transactions and user groups have their own status, which propagates up the
tree to their parent objects. The parents (Business Services, Enterprise Manager, and
the Customer Experience BPV) inherit the worst status of their children.
The default instance hierarchy that is published from CA CEM to CA NSM is as follows:
Customer Experience
Wily CEM TESS(es)
Business Services
Wily CEM Business Services
Wily CEM Business Transactions
User Groups
Wily CEM User Group(s)

View CA CEM objects in Unicenter Explorer


Note: CA NSM cannot import CA CEM Business Services or Business Transactions that
use special Unicode characters. For these objects to be viewed in CA NSM, their names
must be changed to use only ascii characters. For more information about this issue, see
Knowledge Base Article TEC534282
https://support.ca.com/irj/portal/anonymous/redirArticles?reqPage=search&searchID=
TEC534282.
Follow these steps:
1. Start Unicenter TND > Unicenter Explorer.
The Unicenter Explorer console appears.
2. In the left pane, select Business Service Views from the drop-down list to see the
business service nodes and associated business transactions, and user group nodes.
3. Right-click CA CEM objects to see the available menu items.
4. Select different views from the right pane to explore CA CEM objects in different
ways.
You can investigate CA CEM objects in Unicenter Explorer.
Follow these steps:
1. Start Unicenter TND > Unicenter Explorer.
The Unicenter Explorer console appears.
2. In the left pane, select Business Service Views from the drop-down list.
3. Select any CA CEMTESS node, CA CEM business service, CA CEM business
transaction, or CA CEM user group.
4. Right-click CA CEM object and select the Investigate menu.
Note: Dashboards are not supported in NSM 3.1. Hence, the Investigate menu
option shows the same information as a dashboard but in a new browser.
The CA CEM Incident Management tab opens, showing incidents that are related to
the selected object. The Investigate menu option shows the same information as a
dashboard in a new browser and not within the Unicenter Management Command
Center window.
If you are prompted with a CA CEMlogin screen and you do not know your login
credentials, see your CA CEM system administrator. Depending on the type of
access you have, you can view incident details to analyze the incident. You can then
take appropriate action, such as closing the incident. For more information about
using CA CEM, see the CA APM Configuration and Administration Guide.
The default instance hierarchy of CA CEM managed objects is customizable. You can
also determine the status and severity levels of CA CEM objects.

View CA CEM Objects in Management Command Center


More information
Modify the Hierarchy of CA CEM Managed Objects (see page 74)

The Management Command Center provides a hierarchical tree structure for viewing CA
CEM objects (business services, business transactions, and user groups). The objects can
be visualized in either an infrastructure hierarchy or custom created "Business Service
Views" hierarchy. Each monitored object has a set of properties and an associated
status. Business transactions and user groups have their own status, which propagates
up the tree to their parent objects. The parents (Business Services, TESS, and the CA
CEM BPV) inherit the worst status of their children.
The default instance hierarchy that is published from CA CEM to CA NSM is as follows:
CEM
Wily CEM TESS(es)
Business Services
Wily CEM Business Services
Wily CEM Business Transactions
User Groups
Wily CEM User Group(s)

Follow these steps:
1. Start NSM, MCC.
2. In the left pane, select Business Service Views from the drop-down list to see the
business service nodes and associated business transactions, and user group nodes.
Right-click CA CEM objects to see the available menu items.
3. Select different views from the right pane to explore CA CEM objects in different
ways.
You can view dashboards of CA CEM objects in the Management Command Center.
Follow these steps:
1. In the left pane, select Business Service Views from the drop-down list.
2. Select any CA CEM TESS node, CA CEM business service, CA CEM business
transaction, or CA CEM user group.
3. In the right pane, select the corresponding CA CEM dashboard item from the
drop-down list.


The CA CEM Incident Management tab opens in the right pane, showing incidents
that are related to the selected object. You are prompted with a CA CEM login
screen. If you do not know your login credentials, contact your CA CEM system
administrator. Depending on the type of access you have, you can view incident
details or further analyze the incident and take action. For more information about
using CA CEM, see the CA APM Configuration and Administration Guide.
You can investigate CA CEM objects in Management Command Center.
Follow these steps:
1. Start NSM, MCC.
2. In the left pane, select Business Service Views.
3. In the left pane, right-click CA CEM object in the tree hierarchy.
Right-click CA CEM objects to see the available menu items.
4. Select Actions > Investigate.
The CA CEM Incident Management tab opens, showing incidents that are related to
the selected object. The Investigate menu option shows the same information as a
dashboard in a new browser window and not within the Management Command
Center window.
You are prompted with a CA CEM login screen. If you do not know your login
credentials, see your CA CEM system administrator. Depending on the type of
access you have, you can view incident details or further analyze the incident and
take action. For more information about using CA CEM, see the CA APM
Configuration and Administration Guide.
You can view CA CEM incidents in the Management Command Center Event
Console.
Follow these steps:
1. Start NSM, MCC.
2. In the left pane, select Enterprise Management from the drop-down list.
3. Drill down to Event Management, Console Logs.
4. In the right pane, click Launch Console Logs.
The default instance hierarchy of CA CEM managed objects is customizable. You can
also determine the status and severity levels of CA CEM objects.
More information
Modify the Hierarchy of CA CEM Managed Objects (see page 74)

View CA CEM Objects in Unicenter WorldView 2D Map


View CA CEM Objects in Unicenter WorldView 2D Map
Unicenter WorldView 2D Map provides a visual tool for exploring CA CEM objects.
Follow these steps:
1. Start NSM, WorldView, 2D Map.
2. Double-click objects to drill down to the next level.
The WorldView 2D Map windows reveal the CA CEM objects.

View CA CEM Objects in Unicenter Management Portal
Unicenter Management Portal provides a role-based, personalized, and consolidated
view of Unicenter WorldView managed objects using a web portal interface. Using
Unicenter Management Portal, you can navigate to CA CEM WorldView objects, view
object severities, CA CEM Dashboards, and Event Console messages.
Follow these steps:
1. Start Unicenter Management Portal by launching a browser.
Note: Install and configure Unicenter Management Portal. Integrate with Unicenter
2. Type the Unicenter Management Portal URL and port in the address bar. For
example:
3. Select the Knowledge Tab and then the Library Tab.
4. Drill down through the tree in the left pane to select Enterprise Management,
Unicenter Event Management, Event Console.
View Event Console messages in the right pane.
View CA CEM Objects in Unicenter Management Portal


5. To see details, click the Log Messages tab.
6. In the bottom pane, select a message and then click Go.
7. In the left pane, select Business Services and drill down to see all Business Process
Views (BPVs).
A summary view of CA CEM WorldView objects appears.
8. In the right pane, click the Portal Explorer button next to the Customer Experience
BPV.
The Portal Explorer opens.
9. Drill down to see CA CEM objects in the left pane.
Select an object in the left pane and click Go to see the dashboard.
10. The dashboard opens the Incident Management tab in CA CEM.
You can access the Customer Experience Dashboard, Business Service Dashboard,
Business Transaction Dashboard, and User Group Dashboard.The following section
describes how to integrate the CA CEM Integration for CA NSM with Unicenter
Management Portal. You can install the Unicenter Management Portal Integration from
the Integration on a Unicenter Management Portal system.
Note: Integration is not supported with Unicenter Management Portal 3.1. Do not install
the following portal integration on Unicenter Management Portal 3.1 systems.
Follow these steps:
CEMPortalIntegration.zip file.
The file contains Unicenter Management Portal configuration files and an
installation script.
2. Unzip the contents of CEMPortalIntegration.zip, including the directory structure, to
the Unicenter Management Portal directory. For example:
C:\Program Files\CA\SharedComponents\Unicenter Management Portal
3. Launch a command Window and set your directory to the UMP webpages\cem
folder. For example:
C:\Program Files\CA\SharedComponents\Unicenter Management Portal\webpages\cem
4. Run the install.bat script in this directory.

View CA CEM Incidents in the CA NSM Event Console


The CA NSM Event Console lets you monitor the status of events, respond to abnormal
events as they occur, and rectify critical situations immediately. The CA NSM Event
Console organizes the events in pages that you can navigate. Using the provided filtering
and searching functionality, you can narrow your search to view the events you want.
Follow these steps:
1. Start NSM, Enterprise Management, EM Classic.
2. Double-click Windows, Event, Console Logs to reveal log messages.
The Enterprise Manager Console window appears.
3. Refresh to see the latest event messages.
4. Double-click an event message to get details about it.
The event message details are displayed.
You can customize CA NSM Event Console messages by modifying the CA CEM-NSM
Bridge properties file.
Follow these steps:
1. Edit the cemNsmBridge.properties file located in TOMCAT_HOME/shared/classes to
change the format of Event Console messages.
2. The following properties can be modified:
The CEMNSM_WTO_SOURCE property can be altered to specify the source.
The CEMNSM_WTO_TEXT property can be altered to customize the Enterprise
Manager console message. The keywords encapsulated with <> are substituted
within the message.
Refer to the CA CEM-NSM Bridge properties (see page 83) for details about
modifying these properties. Restart the Tomcat server after modifying the
properties files to see the changes take effect.
3. Click a message in the Enterprise Manager Console Logs to see the details about it.
The message details are displayed.
Receive and Update CA CEM Objects in the CA NSM WorldView
Repository
The CA CEM-NSM Bridge subscribes with CA CEM to receive status updates and data
changes for user groups, business services, and enabled business transactions.
Receive and Update CA CEM Objects in the CA NSM WorldView Repository


CA CEM sends a change notification whenever the following occurs:
A user group, business service, or enabled business transaction is created.
A user group, business service, or enabled business transaction is deleted.
A user group, business service, or enabled business transaction is changed
(specifically a name change).
A business transaction is enabled or disabled.
The CA CEM-NSM Bridge processes all the notifications to reflect the change in CA CEM
data or status in the NSM repository.
Synchronize CA CEM Data
The CA CEM data inventory in the CA NSM WorldView repository is synchronized with
CA CEM upon the following events:

Event Description

CA CEM-NSM Bridge startup
CA CEM-NSM Bridge is started or restarted.

CA CEM restart
CA CEM is restarted or the connection is re-established.
CA NSM restart CA NSM is restarted or the connection is re-established
Although you can delete CA CEM objects from the repository, CA CEM data inventory
synchronization recreates these deleted objects if they are still present in CA CEM. The
following section describes changes that you can make to the properties file to reduce
the number of CA CEM objects. Restart the Tomcat server after modifying the
properties files.
Modify the Hierarchy of CA CEM Managed Objects
You can modify the properties files described in this section to reduce the CA CEM
managed objects that appear in the hierarchy. Properties files are located in
TOMCAT_HOME/shared/classes.
To reduce objects in the cemNsmBridge.properties file, you can specify:
Do not create the TESS server node in the hierarchy:
CEMNSM_CREATENODE_TESS=false
Do not create user groups in the hierarchy:
CEMNSM_CREATENODE_USERGROUPS=false
Receive and Update the Status of CA CEM Objects


To reduce objects in the cemBridgeConnector.properties file, you can specify:
Fetch and update business services that match a regular expression. For example:
CEM.<NODENO>.BIZ_PROCESS_FILTER_REGEX=.*.P.*|Plants|.*.p.*
Fetch and update enabled business transactions that match a regular expression.
For example:
CEM.<NODENO>.BIZ_TRANSACTION_FILTER_REGEX=.*.Login.*
Fetch and update user groups that match a regular expression. For example:
CEM.1.USER_GROUP_FILTER_REGEX=New.*|Boston|191.168.*.*
Note: A business transaction is created only when the following conditions are met:
Both business service and business transaction filters are enabled.
Business service name of the transaction matches the business service
filter.
Name of the transaction matches the business transaction filter.
Restart the Tomcat server after modifying the properties files to see the changes take
effect.
More Information
CA CEM-NSM Bridge Properties (see page 83)

The impact levels of CA CEM incidents determine the severity level status of CA CEM
objects. CA CEM has been extended to calculate the impact level of business
transactions and user groups.
The business transaction and user group instances do not have a status of their own;
they have a derived status from their associated incidents. The impact level of a
business transaction or user group is calculated as the impact level of the most critical
associated incidenta roll-up of the worst business impact of all associated open
incidents for that instance. For example, there are three open incidents affecting a
business transaction or user group. Each incident has a different impact levels Low,
Moderate, and Severe. The impact level of such a business transaction or user group is
Severe, as the impact level reflects the highest impact (in this case, Severe).
Incidents can be in an open, closed, or aged-out state. Only those incidents that are in
an open state are used to derive the status of CA CEM business transactions and user
group instances. Incidents can have a business impact too. The status of a CA CEM
business service in NSM is the worst business impact of all its associated business
transactions.
Customize CA NSM Alarmset Severity Status Mappings


The impact level of affected business transactions and user groups is calculated again on
the following events:
A new incident is created.
The impact level of an incident changes due to a change in the business impact.
An incident is closed.
Whenever there is a change in the impact level of a business transaction or user group,
CA CEM notifies CA NSM. CA NSM then processes the notification by updating the status
of the respective object in the CA NSM WorldView repository. Impact level changes are
for business transactions and user groups only.
The following table shows the mapping of CA CEM impact levels to CA NSM WorldView
status:

Highest CA CEM Impact Level NSM WorldView Status

No Incidents (Normal)
Normal (green)
Low Minor (yellow)
Moderate Warning (yellow)
Severe Major (orange)

Critical Critical (red)
Status is not available Unknown (gray)

Customize CA NSM Alarmset Severity Status Mappings
You can change the mappings by modifying the CA NSM Alarmset severity settings so
that the status number maps to a severity different from the default.
Follow these steps:
1. In Management Command Center, select the Topology view in the left pane and
Alarmset View in the right pane.
2. Right-click the object and select Add Viewer, Alarmset View.
The AlarmSet View appears.
3. Double-click the severity item in the severity column to change the status mapping.
Note: If you change, it is applied to all alarmsets of the same class. To change CA
CEM objects, the alarmset must have "Wily CEM" in the name. If the alarmset name
does not say "Wily CEM", the changes can affect other NSM WorldView objects.
4. Ensure to click Save in the top right side of the pane.
5. Restart the Tomcat server for the changes to take effect.
CA NSM Resources


For more information about alarmsets, see the CA NSM Administration Guide or CA
NSM Management Command Center online help.
CA NSM Resources
Each product comes with its own documentation and unique set of resources. This
section gives you an overview of other tools available to you.
CA NSM Documentation
The following documentation resources are available to you.
The CA NSM Administration Guide describes how to configure and administer CA
NSM components after installation and implementation. For more information,
including specific procedures, see the CA NSM Management Command Center
online help.
Note: This guide is available with NSM 3.1 or NSM r11.1 SP1.
The CA NSM Implementation Guide describes how to install and implement CA
NSM.
Note: This guide is available with NSM 3.1 or NSM r11.1 SP1.


Appendix A: Troubleshooting

This section provides high-level verification steps and a troubleshooting table to
troubleshoot the CA CEM integration with CA NSM.
Verify CA NSM Integration with CA CEM (see page 79)
Symptoms and Solutions-(NSM and CA CEM) (see page 80)
Verify CA NSM Integration with CA CEM
You can verify that the integration with CA NSM is functioning in several ways.
Follow these steps:
1. Verify that CA CEM is running.
2. Verify that CA NSM is running.
3. Verify that the CA CEM-NSM Bridge is running. Restart the Tomcat server if
necessary.
4. Check the log file (cemNsmIntegration.log located in TOMCAT_HOME/logs) to
diagnose connection configuration problems.
5. Create a business transaction in CA CEM and enable it. Verify that it appears in CA
NSM Management Command Center.(Wait 30 seconds before checking).
6. Close a CA CEM incident and verify that the change in status is reflected in CA NSM
Management Command Center.
7. Check the CA NSM Event Console logs to see that changes in status to CA CEM
incidents are reported.
8. Right-click CA CEM object in CA NSM Management Command Center and select
Actions > Investigate. See the CA CEM Incidents page.
Symptoms and Solutions-(NSM and CA CEM)


The following table provides some tips that help you troubleshoot the CA NSM
integration with CA CEM:

Symptom Possible Solution

CA CEM objects are unavailable (dimmed) in
CA NSM.
Disabled icons indicate "unknown" state and represent the last
known objects that were found. The CEM-NSM Bridge is down or
has lost connection with either CA NSM or CA CEM. Verify that the
Tomcat server is running. Restart if necessary. Check that CA CEM
is running and that all objects are enabled. If you have changed a
password, host, or username, you need to run the appropriate .bat
file again and restart the Tomcat server. Configuring the CA CEM
and NSM connections (see page 61).
Unable to see dashboards. Make sure that dashboards are installed, as well as patch QO92983
(see the Read Me). Install custom dashboards for Unicenter
Management Command Center (see page 59)
Dashboard displays Business Services
screen.
When logging in as CA CEM configadmin for the first time, the
dashboard launches the Business Services screen. This must not
occur with subsequent logins.
Unable to see the Unicenter Management
Portal.
Make sure you have installed the Unicenter Management Portal
Integration from the Integration Pack on a Unicenter Management
Portal system. Integrate with Unicenter Management Portal (see
page 64)
Too many CA CEM objects appear in CA
NSM.
Use Java regular expressions to specify the business services,
business transactions, and user groups you want in the
cemBridgeConnector.properties file. You can also unsubscribe to
topics by marking them false. CA CEM-NSM Bridge properties (see
page 83) for details about modifying these properties. Restart the
Tomcat server after making changes to properties files to see the
changes take effect.
CA CEM objects dont appear in CA NSM. Check that configuration and credentials to log in to the NSM WV
System are correct. Also check the cemBridgeConnector.properties
file to ensure that the CA CEM objects have not been filtered out.


Symptom Possible Solution
Deleted CA CEM objects reappear in CA
NSM.
Deleted objects are only suppressed from view and must not be
recreated during runtime. However, a restart of the Tomcat server,
NSM, or the CA CEM instance recreates the object. To exclude
excess objects, try filtering them out using Java regular expressions
in the cemBridgeConnector.properties file. You can also
unsubscribe to topics by marking them false. See CA CEM-NSM
bridge properties for details about modifying these properties.
Restart the Tomcat server after making changes to properties files
to see the changes take effect.

Management Command Center displays
"PM Item not found".
If the user has a Management Command Center window open
when a CA CEM object is being deleted on CA CEM, an error
message may appear in the Management Command Center
window due to the underlying CA CEM object being deleted in
NSM by the CA CEM-NSM bridge.
cemNsmIntegration.log displays the
following error:
[NSM Connection Checker] ERROR
NSMSpringBeans Connecting to WV
repository failed (will retry) host:nsmhost
TNGWV_Exception: Could not connect to
repository rc: 28
Run the application modp from a command line:
modp -R nsmbox -u nsmadmin -n password
This creates registry keys that allow a NSM WorldView connection
by using the username and password tngsa/tngadmin. Services
typically use the username and password tngsa/tngadmin to
connect to NSM WorldView, no matter what NSM WorldView box
they are connecting to.


Appendix B: CA CEM-NSM Bridge Properties

This appendix documents the CA CEM-NSM Bridge properties files. The properties files
that can be edited are found in <TOMCAT_HOME>/shared/classes.
All the CA CEM-NSM Bridge properties are preconfigured to the required options for the
CA CEM to CA NSM integration to work. In some circumstances, you can modify default
values. Restart the Tomcat server after modifying the properties files to see the changes
take effect.
Note: "Business process" in CA CEM is the same as "business service." The term varies
based on the CA CEM version you have installed. You can use the terms interchangeably
in this chapter.
Edit the cemBridgeConnector.properties File (see page 83)
Filter User Groups, Business Services, and Business Transactions (see page 89)
Edit the nsmBridgeConnector.properties File (see page 91)
Edit the cemNsmBridge.properties File (see page 94)
Edit the cemBridgeConnector.properties File
Edit the TOMCAT_HOME/shared/classes/cemBridgeConnector.properties file to set the
correct CA CEM connection properties. The following section explains the currently
supported properties.
WEBAPP_CONTAINER_HOST (see page 84)
WEBAPP_CONTAINER_PORT (see page 84)
CEM.1.HOST (see page 84)
CEM.1.PORT (see page 85)
CEM.1.USER (see page 85)
CEM.1.PASSWORD (see page 86)
CEM.1.TOPIC_BIZ_PROCESS_UPDATES_SUBSCRIBE (see page 86)
CEM.1.TOPIC_BIZ_TRANSACTION_UPDATES_SUBSCRIBE (see page 86)
CEM.1.TOPIC_USER_GROUP_UPDATES_SUBSCRIBE (see page 87)
CEM.1.TOPIC_INCIDENT_UPDATES_SUBSCRIBE (see page 87)
CEM.1.TOPIC_BIZ_TRANS_SEVERITY_UPDATES_SUBSCRIBE (see page 88)
CEM.1.TOPIC_USER_GROUP_SEVERITY_UPDATES_SUBSCRIBE (see page 88)
CEM.1.CEM_CONNECTION_CHECK_SEC (see page 89)


WEBAPP_CONTAINER_HOST
Identifies the Tomcat host where the CA CEM Bridge web archive gets deployed.
Settings
The host name or IP address of the system running the servlet engine. Possible values:
localhost or 127.0.0.1
specific IP address
Default
localhost
Example
WEBAPP_CONTAINER_HOST=localhost
Note: The system checks to see if the provided IP maps to the local host. If not, an error
is logged to the cemNsmIntegration.log from <TOMCAT_HOME>/logs and the rest of the
bridge does not start up.
WEBAPP_CONTAINER_PORT
Identifies the Tomcat port where the CA CEM Bridge web archive gets deployed.
Settings
Any valid Tomcat port number
Default
8080
Example
WEBAPP_CONTAINER_PORT=8080
CEM.1.HOST
Identifies the CA CEM host.
Settings
The host name or IP address of the CA CEM system
Default
cem_host


Example
CEM.1.HOST=123wilycem
Note: The default value must be set to a correct CA CEM host using the
SetCemBridgeConnector.bat file located in <TOMCAT_HOME>/cemNsmBridge.
CEM.1.PORT
Identifies the CA CEM port.
Settings
Any valid port number
Default
CEM.1.PORT=80
Example
CEM.1.PORT=80
Note: The default value must be set to a correct CA CEM port using the
CEM.1.USER
Identifies the user that has privileges to access CA CEM.
Settings
N/A
Default
cemadmin
Example
CEM.1.USER=cemadmin
Note: Only the cemadmin can set the connection.


CEM.1.PASSWORD
Identifies the password for the CA CEM user.
Settings
N/A
Default
cem_password
Example
CEM.1.PASSWORD=<ENCRYPTED_PASSWORD>
Note: The password for the CA CEM user must be set using the
CEM.1.TOPIC_BIZ_PROCESS_UPDATES_SUBSCRIBE
Specifies whether to subscribe to notifications on business service updates.
Settings
True or False
Default
True
Example
CEM.1.TOPIC_BIZ_PROCESS_UPDATES_SUBSCRIBE=true
Note: This property can be used to turn on/off receiving of business service update
messages. The creation, updates, or deletions of business services in CA CEM must not
be sent to the bridge if this property is set to false.
CEM.1.TOPIC_BIZ_TRANSACTION_UPDATES_SUBSCRIBE
Specifies whether to subscribe to notifications on business transaction updates.
Settings
True or False


Default
True
Example
CEM.1.TOPIC_BIZ_TRANSACTION_UPDATES_SUBSCRIBE=true
Note: This property can be used to turn on/off receiving of business transaction update
messages. The creation, updates, or deletions of business transactions in CA CEM must
not be sent to the bridge if this property is set to false.
CEM.1.TOPIC_USER_GROUP_UPDATES_SUBSCRIBE
Specifies whether to subscribe to notifications on user group updates.
Settings
True or False
Default
True
Example
CEM.1.TOPIC_USER_GROUP_UPDATES_SUBSCRIBE=true
Note: This property can be used to turn on/off receiving of user group update messages.
The creation, updates, or deletions of user groups in CA CEM must not be sent to the
bridge if this property is set to false.
CEM.1.TOPIC_INCIDENT_UPDATES_SUBSCRIBE
Specifies whether to subscribe to notifications on incident updates.
Settings
True or False
Default
True
Example
CEM.1.TOPIC_INCIDENT_UPDATES_SUBSCRIBE=true


Note: Incidents that are created or updated on CA CEM are sent as events in the
Unicenter admin console. This property must be set to false if you are not interested in
receiving incidents as events in the admin console.
CEM.1.TOPIC_BIZ_TRANS_SEVERITY_UPDATES_SUBSCRIBE
Specifies whether to subscribe to notifications on business transaction severity updates.
Settings
True or False
Default
True
Example
CEM.1.TOPIC_BIZ_TRANS_SEVERITY_UPDATES_SUBSCRIBE=true
Note: Business transaction severity updates are notifications that are sent whenever the
severity of a business transaction changes due to business impact change in impacting
incidents. This property must be set to false if you are not interested in receiving
business transaction severity change notifications.
CEM.1.TOPIC_USER_GROUP_SEVERITY_UPDATES_SUBSCRIBE
Specifies whether to subscribe to notifications on user group severity updates.
Settings
True or False
Default
True
Example
CEM.1.TOPIC_USER_GROUP_SEVERITY_UPDATES_SUBSCRIBE=true
Note: User group severity updates are notifications that are sent whenever the severity
of a user group changes due to business impact change in impacting incidents. This
property must be set to false if you are not interested in receiving user group severity
change notifications.
Filter User Groups, Business Services, and Business Transactions


CEM.1.CEM_CONNECTION_CHECK_SEC
Specifies the time interval (in seconds) at which the bridge checks whether the CA CEM
connection is available.
Settings
N/A
Default
30
Example
CEM.1.CEM_CONNECTION_CHECK_SEC=30
Filter User Groups, Business Services, and Business
Transactions
The user groups, business services, and business transactions that are created in the
NSM repository can be controlled using Java regular expressions. The following example
specifies the creation of user groups, business services, and business transactions that
start with "New," "East," or the letter "A":
CEM.1.USER_GROUP_FILTER_REGEX=New.*|East.*|A.*
CEM.1.BIZ_PROCESS_FILTER_REGEX=New.*|East.*|A.*
CEM.1.BIZ_TRANSACTION_FILTER_REGEX=New.*|East.*|A.*
The following table shows more examples of regular expressions:

Property value Meaning

Boston
Name "Boston".
191.168.*.* Name matching the 191.168 subnet. Meaning 191.168.1.1, 191.168.1.2, etc., gets
created.
New.* Names starting with "New". Sample user group names that match and be created:
"New Users", "New Orleans", "New York", etc.

.*.A.*
Any name with the letter "A" in it.
.*.login.* Any name with the word "login" in it.
Filter User Groups, Business Services, and Business Transactions


Note: The | symbol can be used to separate multiple values.
When Filtering is enabled the bridge fetches only the user groups, business services, and
business transactions that match the respective regular expressions. A business
transaction is fetched only if the business transaction name and the business service
name of the business service to which it belongs match the respective regular
expressions.
Severity updates that are sent from CA CEM are also filtered. Only severity changes of
the business transactions and user groups that match the respective regular expressions
are sent.
CEM.1.USER_GROUP_FILTER_REGEX (see page 90)
CEM.1.BIZ_PROCESS_FILTER_REGEX (see page 90)
CEM.1.BIZ_TRANSACTION_FILTER_REGEX (see page 91)
CEM.1.USER_GROUP_FILTER_REGEX
Uses an expression to filter user groups.
Settings
Uses Java Regular expressions
Default
The filter is commented out and not applied by default.
Example
CEM.1.USER_GROUP_FILTER_REGEX=New.*|Boston|191.168.*.*
Note: For creating all user groups and to disable filtering, comment out the property by
prepending a # symbol before the property name as follows:
#CEM.1.USER_GROUP_FILTER_REGEX. Remove the # symbol before the property name
to enable filtering.
CEM.1.BIZ_PROCESS_FILTER_REGEX
Uses an expression to filter business services.
Settings
Uses Java Regular expressions
Edit the nsmBridgeConnector.properties File


Default
Example
CEM.1.BIZ_PROCESS_FILTER_REGEX=.*.P.*|Plants|.*.p.*
Note: For creating all business services and to disable filtering, comment out the
property by prepending a # symbol before the property name as follows:
#CEM.1.BIZ_PROCESS_FILTER_REGEX. Remove the # symbol before the property name
to enable filtering.
CEM.1.BIZ_TRANSACTION_FILTER_REGEX
Uses an expression to filter business transactions.
Settings
Uses Java Regular expressions.
Default
Example
CEM.1.BIZ_TRANSACTION_FILTER_REGEX=.*.Login.*|.*.Shopping.*|.*.login.*
Note: For creating all business transactions and to disable filtering, comment out the
property by prepending a # symbol before the property name as follows:
#CEM.1.BIZ_TRANSACTION_FILTER_REGEX.
Edit the TOMCAT_HOME/shared/classes/nsmBridgeConnector.properties file to set the
correct NSM connection properties. The following section explains the currently
supported properties.
NSM_WV_HOST (see page 92)
NSM_WV_USER (see page 92)
NSM_WV_PASSWORD (see page 92)
NSM_WV_DISABLE (see page 93)
NSM_CONNECTION_CHECK_SEC (see page 93)
NSM_EM_HOST (see page 94)
NSM_EM_DISABLE (see page 94)


NSM_WV_HOST
Identifies the host name of the system hosting the NSM WorldView Manager.
Settings
N/A
Default
wv_host
Example
NSM_WV_HOST=wv_host
Note: The default value must be set to a correct NSM WV host using the
SetNsmBridgeConnector.bat.
NSM_WV_USER
Identifies the user name to connect to the NSM WV Manager.
Settings
N/A
Default
nsmadmin/tngsa
Example
NSM_WV_USER=nsmadmin
NSM_WV_PASSWORD
Identifies the password to connect to the NSM WV Manager.
Settings
N/A
Default
wv_password


Example
NSM_WV_PASSWORD=<ENCRYPTED_PASSWORD>
Note: The password for the NSM WV user must be set using
SetNsmBridgeConnector.bat.
NSM_WV_DISABLE
Disables the NSM WV connection.
Settings
True or False
Default
False
Example
NSM_WV_DISABLE=false
NSM_CONNECTION_CHECK_SEC
Specifies the time interval (in seconds) at which the bridge checks whether the NSM
connection is available.
Settings
N/A
Default
180
Example
NSM_CONNECTION_CHECK_SEC=180
Note: The time interval cannot be shorter than 3 minutes (180 seconds).
Edit the cemNsmBridge.properties File


NSM_EM_HOST
Identifies the NSM Enterprise Manager Host.
Settings
N/A
Default
em_host
Example
NSM_EM_HOST=em_host
Note: You can specify a local or remote NSM Enterprise Manager Host.
NSM_EM_DISABLE
Disables the NSM Enterprise Manager console connection.
Settings
True or False
Default
False
Example
NSM_EM_DISABLE=false
Edit the TOMCAT_HOME/shared/classes/cemNsmBridge.properties file to configure the
properties for the Bridge. The following section explains the currently supported
properties.
CEMNSM_CREATENODE_TESS (see page 95)
CEMNSM_CREATENODE_USERGROUPS (see page 95)
CEMNSM_WTO_SOURCE (see page 95)
CEMNSM_WTO_TEXT (see page 96)


CEMNSM_CREATENODE_TESS
Specifies whether to create the Enterprise Manager (TESS) server node under the
Customer Experience BPV or not. If set to false, objects from different Enterprise
Manager (TESS) servers appear under the common root node, Customer Experience.
Settings
True or False
Default
True
Example
CEMNSM_CREATENODE_TESS=true
CEMNSM_CREATENODE_USERGROUPS
Specifies whether to create the user groups or not.
Settings
True or False
Default
True
Example
CEMNSM_CREATENODE_USERGROUPS=true
Note: Recommended to be set to false if the CA CEM discovers there are a large number
(in thousands) of user groups.
CEMNSM_WTO_SOURCE
Specifies the source for Enterprise Manager Console messages to indicate when an
event message came from the bridge.
Settings
N/A


Default
Customer Experience
Example
CEMNSM_WTO_SOURCE=Customer Experience
CEMNSM_WTO_TEXT
Defines the format of Enterprise Manager Console text messages for incidents. The text
message is customizable. The fields within <...> are substituted at run time.
Settings
<host> the Enterprise Manager (TESS) server where the incident resides
<source> the source (defines the CEMNSM_WTO_SOURCE in this file)
<prevseverity> previous incident severity (such as NORMAL, SEVERE, or n/a if there
is no prior severity)
<severity> incident severity (such as NORMAL or SEVERE)
<status> incident status (such as Opened, Closed, Changed, or Aged-out)
<bp> the affected business service
<bt> the affected business transaction
<url> a URL to detailed incident information
<defect> defect name (such as High Throughput or Slow Time)
<id> incident ID (such as 600000000000000141)
Default
CEMNSM_WTO_TEXT=<source>, Incident for <host>, <bp>, <bt>, ID <id>, <defect>,
<status> to <severity>, from <prevseverity>. <url>
Results in the message:
Customer Experience, Incident for wilycem, Plants1, SelectBonsaiTree /
SelectBonsaiTree, ID 600000000000000123, High Throughput, Changed, to Critical, from
Low,
http://wilycem:8081/wily/cem/tess/app/biz/bizEventDetail.html?pId=600000000000000
123


Example
CEMNSM_WTO_TEXT=<source> incident for <host>, <bp>/ <bt>, ID <id>: <defect> <status>
to <severity> from <prevseverity>. See details: <url>
Results in the message:
Customer Experience incident for wilycem, Plants1, SelectBonsaiTree /
SelectBonsaiTree, ID 600000000000000123: High Throughput Changed to Critical from
Low. See
details:http://wilycem:8081/wily/cem/tess/app/biz/bizEventDetail.html?pId=6000000
00000000123

Index 99

Index

(
(Optional) Enable DEBUG logging in the CEM-NSM
bridge 63
(Optional) Enable DEBUG logging in the
Introscope-NSM bridge 43
A
About CA NSM with CA CEM 52
Access the CA Introscope Integration for CA NSM
Configuration UI 35
Add an Introscope Enterprise Manager Host 36
Architecture Diagram 12
B
Benefits 12
C
CA CEM-NSM Bridge Maintenance 63
CA CEM-NSM Bridge Properties 83
CA CEM-NSM Bridge Start/Stop 63
CA NSM Documentation 77
CA NSM Integration Overview 53
CA NSM Resources 77
CA NSM Terms 54
CA NSM to CA CEM Integration Terminology 53
CA NSM to CA CEM Term Mapping 55
CA Technologies Product References 3
CEM.1.BIZ_PROCESS_FILTER_REGEX 90
CEM.1.BIZ_TRANSACTION_FILTER_REGEX 91
CEM.1.CEM_CONNECTION_CHECK_SEC 89
CEM.1.HOST 84
CEM.1.PASSWORD 86
CEM.1.PORT 85
CEM.1.TOPIC_BIZ_PROCESS_UPDATES_SUBSCRIBE
86
CEM.1.TOPIC_BIZ_TRANS_SEVERITY_UPDATES_SUBS
CRIBE 88
CEM.1.TOPIC_BIZ_TRANSACTION_UPDATES_SUBSCR
IBE 86
CEM.1.TOPIC_INCIDENT_UPDATES_SUBSCRIBE 87
CEM.1.TOPIC_USER_GROUP_SEVERITY_UPDATES_S
UBSCRIBE 88
CEM.1.TOPIC_USER_GROUP_UPDATES_SUBSCRIBE
87
CEM.1.USER 85
CEM.1.USER_GROUP_FILTER_REGEX 90
CEMNSM_CREATENODE_TESS 95
CEMNSM_CREATENODE_USERGROUPS 95
CEMNSM_WTO_SOURCE 95
CEMNSM_WTO_TEXT 96
Configure CA NSM 39
Configure Introscope Enterprise Manager Host 36
Configure Message Formatting 41
Configure Monitoring 40
Configure Status Mapping 41
Configure the Alternate Bind Address 34
Configure the Unicenter Management Portal 34
Configure Unicenter Management Portal with CA
CEM 61
Configuring and Managing Whats Monitored 33
Configuring the CA CEM and NSM Connections 61
Contact CA Technologies 5
Customize CA NSM Alarmset Severity Status
Mappings 76
D
Delete an Introscope Enterprise Manager Host 37
E
Edit an Introscope Enterprise Manager Host 38
Edit the cemBridgeConnector.properties File 83
Edit the cemNsmBridge.properties File 94
Edit the NSM Enterprise Manager Host 39
Edit the NSM WorldView Repository 39
Edit the nsmBridgeConnector.properties File 91
F
Feature Prerequisites 19
Features of CA Introscope Integration for CA NSM
21
Filter User Groups, Business Services, and Business
Transactions 89
H
How Integration Works 11


I
Install Custom Dashboards for Unicenter
Management Command Center 59
Install on a Machine with an Existing Integration 28
Install the CA CEM Integration Pack for CA NSM 57
Install using Silent Mode 25
Install Using the Console Mode 27
Install using the GUI Installer 23
Installation Archives 20
Installation Modes 22
Installation Scenarios 22
Installation Sets 21
Installing CA CEM Integration for CA NSM 57
Installing CA Introscope Integration for CA NSM
15
Integrate with Unicenter Management Portal 64
Integrating CA NSM with CA CEM 51
Introduction 11
M
Modify the Hierarchy of CA CEM Managed Objects
74
N
NSM_CONNECTION_CHECK_SEC 93
NSM_EM_DISABLE 94
NSM_EM_HOST 94
NSM_WV_DISABLE 93
NSM_WV_HOST 92
NSM_WV_PASSWORD 92
NSM_WV_USER 92
O
Other Maintenance Information 63
Overview 33
P
Pre installation Requirements 18
R
Receive and Update CA CEM Objects in the CA NSM
WorldView Repository 73
75
Re-install CA Introscope Integration for CA NSM
27
Remove CA Introscope Objects 30
Remove CA Introscope to Unicenter NSM
Integration Release 1.x 15
Remove Objects from the WorldView Repository
17
Remove the Integration Pack from the Enterprise
Manager 16
Remove the Integration Pack from the NSM Bridge
Proxy 16
Remove the Integration Pack from Unicenter
Management Portal 17
Remove the Integration Pack from Unicenter
WorldView 16
18
Required Configurations 33
S
Set CA CEM Connection Information 61
Set CA NSM Connection Information 60
Silent Installer Properties 25
Symptoms and Solutions-(NSM and CA CEM) 80
Synchronize CA CEM Data 74
T
Troubleshooting 79
U
29
Use the Integration Pack Configuration UI 24
User Rights 22
Using CA Introscope Integration for CA NSM 45
Using CA NSM with CA CEM 67
Using the CA NSM Configuration UI 35
V
Verify CA NSM Integration with CA CEM 79
Verify the Installation 29, 59, 64
Verify the Integration Installation 58
73
View CA CEM Objects in CA NSM 67
View CA CEM Objects in Management Command
Center 69
View CA CEM objects in Unicenter Explorer 67
View CA CEM Objects in Unicenter Management
Portal 71

Index 101

View CA CEM Objects in Unicenter WorldView 2D
Map 71
View CA Introscope Alerts in the CA NSM Event
Console 49
View CA Introscope Alerts in the Management
Command Center Event Console 47
View CA Introscope Objects in CA NSM WorldView
2D Map 48
View CA Introscope objects in Management
Command Center 45
View CA Introscope Objects in the Unicenter
Management Portal 47
View Dashboards of CA Introscope Objects in the
Management Command Center 46
View Introscope Objects in the Management
Command Center Tree Hierarchy 46
W
WEBAPP_CONTAINER_HOST 84
WEBAPP_CONTAINER_PORT 84

APM - 9.5 NSM Integration Guide

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

APM - 9.5 NSM Integration Guide

Enviado por

Direitos autorais:

Formatos disponíveis

Integration for CA NSM Guide

Você também pode gostar