ITCM ConnectorGuide ENU

CA Catalyst
CA IT Client Manager Connector Guide

Version 1
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 2010 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
CA Technologies Product References

This documentation set references the following CA products: CA IT Client Manager (CA ITCM) CA IT Client Manager Web Services (CA ITCM Web Services) CA Message Queuing (CAM) CA Catalyst CA Spectrum Service Assurance (CA Spectrum SA) CA IT Process Automation Manager (CA IT PAM) CA Network and Systems Management (CA NSM)
Contact CA Technologies
Contact CA Support For your convenience, CA Technologies provides one site where you can access the information you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following: 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
Provide Feedback If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. If you would like 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
Chapter 1: Overview 7
About This Guide .............................................................................. 7 Terminology ................................................................................... 7 CA ITCM Connector ............................................................................ 9 Integration Scenarios ......................................................................... 10 Connector Integration ..................................................................... 11 Business Service Management (BSM) Use Case ............................................. 12 Insight Use Case .......................................................................... 12
Chapter 2: Installation
15
Operating Environment Support ............................................................... 15 Installation Considerations .................................................................... 16 Installation Scenarios ......................................................................... 16 Install the CA ITCM Connector ................................................................. 17
Chapter 3: Configuration
21
Post-installation Tasks ........................................................................ 21 Enabling Full Alert Functionality ............................................................ 21 Enabling the Asset Collector for Inbound Functionality ....................................... 22 Configure the CA ITCM Connector ............................................................. 22 Configure Multiple Connector Instances on One Server .......................................... 24 Scoping the Data Published to CA Catalyst ..................................................... 25 Reconciled Services ........................................................................... 26 Using Multi-Tenant Support for Inbound Operations ............................................. 27
Chapter 4: Connector and Domain Manager Interaction
29
Outbound from Connector Operations .......................................................... 29 Inbound to Connector Operations .............................................................. 31 USM Data Mapping ........................................................................... 31 Type Mapping ............................................................................ 31 Relationship Mapping ..................................................................... 32 Severity Mapping ......................................................................... 32 Custom Mappings ......................................................................... 33
Contents 5
Chapter 5: Troubleshooting
35
Behavioral Limits of the CA ITCM Connector .................................................... 35 Known Issues ................................................................................ 36 Delay in Updating Relationships in CA Spectrum SA When Deleting a Computer System ....... 36 Deleting the catalystScope Group Is Not Supported ......................................... 36 CA ITCM Connector Is Offline .............................................................. 36 Unable to Link Additional Connector Instance to Another CA Spectrum SA Manager ........... 37 Installation of Connector from Remote Shared Folder Fails to Install Integration Services ...... 37
Chapter 6: High Availability Considerations
39
Installing the CA ITCM Connector on a Failover Cluster .......................................... 39 The CA ITCM Connector on a High Availability Cluster ........................................... 40
Chapter 7: Uninstallation
41
Uninstall and Reinstall the DSM Scalability Server ............................................... 41 Uninstall the CA ITCM Connector .............................................................. 42
Appendix A: CA ITCM/USM Attribute Mappings
43
Computer/ComputerSystem Outbound Attribute Mapping ....................................... 43 ComputerStatus/ComplianceStatus Outbound Attribute Mapping ................................. 45 ComputerGroupMember/IsComposedOf Outbound Attribute Mapping for Computers .............. 46 ComputerGroupMember/IsComposedOf Outbound Attribute Mapping for Groups .................. 47 ComputerStatusRelationship/HasDetail Outbound Attribute Mapping ............................. 48 ComputerGroup/Service Outbound Attribute Mapping ........................................... 49 AssetQueryPolicyViolation/Alert Outbound Attribute Mapping .................................... 49 SoftwarePolicyViolation/Alert Outbound Attribute Mapping ....................................... 50 ComputerSystem/Computer Inbound Attribute Mapping ......................................... 51
Appendix B: Sample Asset Collector Input File Appendix C: Third-Party Acknowledgements
55 59
Apache License Version 2.0 ................................................................... 59 Apache Log4j 1.2.15 .......................................................................... 63
Index
69
6 CA IT Client Manager Connector Guide
Chapter 1: Overview
This section contains the following topics: About This Guide (see page 7) Terminology (see page 7) CA ITCM Connector (see page 9) Integration Scenarios (see page 10)
About This Guide

This guide describes how to install and configure the CA Catalyst connector for CA IT Client Manager Release 12.5.00 (CA ITCM connector). CA Catalyst connectors expose product data to consuming products such as CA Spectrum Service Assurance (CA Spectrum SA) and CA IT Process Automation Manager (CA IT PAM) for visualization, analysis, and management in a unique, heterogeneous context. This guide contains information specific to the CA Catalyst connector for CA ITCM. For more general information about CA Catalyst connectors and the CA Catalyst infrastructure, information that applies to all connectors, and information about custom connector integrations, see the Connector Guide distributed with CA Spectrum SA. For known issues related to this specific connector, see the "Troubleshooting" chapter in this guide.
Terminology
The following list contains concepts and terms that may be useful to know if you are integrating a CA Catalyst connector with CA Spectrum SA or other consuming products for the first time: Connectors Connectors are the links from products that consume connector data to external products, referred to in this document as domain managers. Each connector retrieves information from its domain manager and transmits the information through the connector framework to the consuming product for visualization and analysis. Connectors can also enact inbound operations on data in the source domain manager, such as object creation. CA Catalyst connectors use a unified connector framework to enable integration with multiple consuming products.
Terminology
USM The Unified Service Model (USM) is a schema of common object types and properties to which data from all connectors is converted. The USM schema enables analysis of data from all domain managers in a common interface with identical formatting. Configuration Items (CIs) Configuration items (CIs) represent IT elements managed by a domain manager. Each CI belongs to a type (defined in the USM schema), such as ComputerSystem, Database, Process, Relationship, and so on. Services contain CIs, and you define relationships between CIs in services. Connectors transform managed objects from domain managers to adhere to the USM schema and import the objects to the consuming products as CIs. Services Services represent discrete business functions that can contain configuration items managed by multiple domain managers. For example, a payroll service may contain an Active Directory database managed by Microsoft SCOM, a user store managed by a security product, batch jobs managed by a mainframe product, a router managed by a network product, applications managed by an application management product, and so on. You can do the following in consuming products such as CA Spectrum SA: Detect the root cause of service degradation quickly and navigate to the appropriate product to resolve problems Model services based on imported CIs or import existing service models from integrated products to construct a comprehensive, service-centric model of your enterprise
Alerts Alerts are the CA Spectrum SA mechanism for reporting fault conditions and service degradation. Infrastructure alerts are fault conditions originally reported by one of the domain managers (such as a CA NSM event or CA Spectrum alarm). An alert is associated with a corresponding CI, and associated alert severities determine CI condition and, ultimately, service impact. Service alerts are conditions generated by CA Spectrum SA based on analysis of a modeled service. Service alerts result when the condition of one or more CIs combines to impact the overall quality or risk level associated with the service. Outbound from connector operations Outbound from connector operations are operations that a connector invokes to import data from domain managers into consuming products such as CA Catalyst and CA Spectrum SA. All connectors support outbound from connector operations.
CA ITCM Connector
Inbound to connector operations Inbound to connector operations invoke changes in the domain manager data store as a result of changes to the imported data in the consuming product. For example, CI reconciliation in CA Catalyst can change the values of CI properties. Connectors that support inbound operations can then enact that change in the source domain manager so that its data matches the reconciled data. Or if a CI is deleted in a domain manager that CA Catalyst defines as a source of truth, connectors that support inbound operations can delete the CI in other domain managers with a record of that CI. Note: For more CA Spectrum SA concepts, see the CA Spectrum SA Administration Guide.
CA ITCM Connector
CA ITCM provides management features in three major areas: asset management, remote control, and software delivery. At a high level, asset management provides comprehensive collection of software and hardware inventory, remote control provides managed remote desktop capabilities, and software delivery manages the deployment of operating systems, applications, and patches. These feature areas all share a common infrastructure that includes installation services, database services (through MDB), user interfaces, reporting capabilities, communication protocols, configuration services, logging services, and so on. The architecture provides two management tiers, the enterprise manager and the domain manager, and the scalability server and agent tiers. Each manager uses one instance of a Management Database (MDB), and select management data is replicated between the two management tiers. Agents connect to scalability servers for most management operations.
Integration Scenarios
The following graphic illustrates CA IT Client Manager tier structure:
Note: For more information about CA ITCM architecture and implementation, see the CA ITCM Release 12.5 Implementation Guide.
The CA ITCM connector interfaces with the DSM domain manager/scalability server to expose CA ITCM data for use by products that leverage the CA Catalyst infrastructure. Integrating CA ITCM data with consuming products, such as CA Spectrum SA, enables reconciliation and correlation of entity properties with existing CIs. Integration also lets you evaluate the data in a different, broader business service context.
Connector Integration
With CA Catalyst connector integration, there is one CA ITCM connector per domain. The CA ITCM connector interfaces with the domain manager using the following CA ITCM components or functionality: CA ITCM Web Services CA ITCM Web Services is used to retrieve information about the CIs to be published to CA Catalyst. CA ITCM Event Notification Subsystem Events about updates to published CIs are received through the CA ITCM event notification subsystem. This mechanism also avoids polling. Asset Collector The Asset Collector component is used during CA Spectrum SA subscribe operations for Computer CI data. The Asset Collector files help to move the inbound create and update data from the connector to the CA ITCM MDB. The following graphic summarizes CA ITCM - CA Catalyst connector integration:
Business Service Management (BSM) Use Case

Services A business service like an e-mail service is formed by a collaboration of groups of CIs, such as Active Directory servers, exchange servers, database servers, and so on. CA ITCM provides configuration management capabilities for these CIs. The CI groups can be created either statically or dynamically using query functionality in CA ITCM. CA ITCM can publish these CI groups, also referred to as "computer groups" in client manager terminology, into CA Catalyst as Services. This integration allows a business service to be holistically modeled by including all the constituent CIs in CA Catalyst. Alerts CA ITCM provides two alert types associated with the CIs published in CA Catalyst. The inventory alerts monitor the inventory attributes of the CI, and the software alert analyses the software policy violations. When an attribute associated with either the inventory or software policy of the CI changes, for example, when free disk space becomes lower than the set threshold, an alert is published in CA Catalyst. These alerts influence the broader service alert generated by CA Spectrum SA.
Insight Use Case

Publish/Outbound Allow CA ITCM to share data about managed computers with CA Catalyst and add value to the overall consolidation and reconciliation processes. Note: The operations supported for publishing data from CA ITCM to CA Catalyst are sometimes referred to as "outbound." The terms "publish" and "outbound" are used interchangeably. Subscribe/Inbound Allow CA ITCM to consume data about systems discovered by other CA Catalyst providers to enable the management of those systems with an option to provision the systems with the CA ITCM agent to enable complete management capabilities. Once the system is managed by CA ITCM, other consumers can benefit from the data collected by CA ITCM. Note: The operations supported for the subscription of data from CA Catalyst to CA ITCM are sometimes referred to as "inbound." The terms "subscribe" and "inbound" are used interchangeably.
Both goals are reflected in the following flowchart:
More information: Scoping the Data Published to CA Catalyst (see page 25)
Chapter 2: Installation
This section contains the following topics: Operating Environment Support (see page 15) Installation Considerations (see page 16) Installation Scenarios (see page 16) Install the CA ITCM Connector (see page 17)
Operating Environment Support

The CA ITCM connector supports the following versions of CA Spectrum SA and CA Catalyst: CA Spectrum SA r2.5 CA Catalyst r2.5
The CA ITCM connector supports the following versions of CA ITCM: CA ITCM Release 12.5 - Full functionality. CA ITCM r12 SP1 - Alert functionality is not supported.
The CA ITCM connector can be installed with an existing domain manager or scalability server only on Windows operating systems. Both the CA ITCM connector and CA Spectrum SA support the following Windows operating environments: Windows Server 2008 R2 (Enterprise Edition, Standard Edition, Web Edition, Datacenter Edition) 64-bit Windows Server 2008 SP2 (Enterprise Edition, Standard Edition, Datacenter Edition) 32- and 64-bit Windows Server 2003 R2 SP2 (Enterprise, Standard) 32- and 64-bit Windows Server 2003 SP2 (Enterprise, Standard, Web) 32- and 64-bit
Chapter 2: Installation 15
Installation Considerations
Installation Considerations
You must consider the following prerequisites before you install the CA ITCM connector: Domain Manager or Scalability Server Prior to installing the CA ITCM connector, a DSM domain manager or scalability server must be installed on the dedicated computer that is intended for the CA ITCM connector. Two patches, RO20969 and RO21981, must be downloaded from Technical Support and applied to the DSM domain manager. The patches are applicable to CA ITCM Release 12.5 only. The DSM domain manager requires CA ITCM Web Services (enabled). The DSM domain manager or scalability server requires the Asset Collector component (enabled and configured). Note: The Asset Collector is only needed for incoming write CRUD operations. Ports and Protocols Only the following ports and protocols may be used for communication between CA Catalyst, the CA ITCM connector, and the MDR: CA ITCM Web Services 80 CAM CAM 4104 4728 HTTP UDP TCP
Installation Scenarios
The connector must be co-installed with a DSM scalability server to get access to the interfaces used for connector-management data repository (MDR) communication. The scalability server is always installed together with the domain manager so the connector can be installed on the domain manager machine. The connector can also be installed on any machine where a standalone scalability server registered with the domain manager has been installed. However, only one connector per CA ITCM domain is supported, so if you already have a connector installed on either the domain manager or a scalability server registered with that domain manager, you cannot install a second connector for that domain.
Install the CA ITCM Connector
The following graphic shows two typical installation scenarios: A connector, scalability server, and domain manager installed together on a domain manager machine (Computer A) Another connector installed on a standalone scalability server (Computer C) that is registered with another domain manager (Computer B)

You can install the CA ITCM connector on a Windows-only DSM domain manager or scalability server that meets the restrictions described previously in the Operating Environment Support section. During installation, you configure the CA ITCM connector to integrate with the remote CA ITCM instance and the CA Spectrum SA manager components. To install the remote CA ITCM connector 1. Double-click the Connector_CA ITCM.exe file from the CA ITCM connector package to start the connector installation. The installer Introduction page opens if all prerequisites are met. 2. Click Next. The License Agreement page appears.
3. Scroll to the bottom of the agreement, select "I accept the terms of the License Agreement" and click Next. The Choose Install Folder page appears. Note: This page does not open if CA Spectrum SA components already reside on the system. 4. Do one of the following to specify the installation folder and click Next: Accept the default. Enter the name of a new installation folder. Click Choose and select an installation folder.
Note: The maximum installation path length is 150 characters. The installer blocks paths with more than 150 characters. One of the following occurs: The CA ITCM Connector Configuration page opens if another connector or the SA Manager resides on the same system. The Integration Services Configuration page opens if you are installing the connector on a system with no other CA Spectrum SA components (that is, a "clean" installation).
5. (Clean installation only) Specify the following information to connect to the appropriate SA Manager and configure connector preferences: Manager Host Defines the name of the SA Manager server, which is the CA Spectrum SA manager component. ActiveMQ Port Defines the specified port number for the ActiveMQ server, which is installed with the SA Manager. Retain the default of 61616 unless you changed this port number when installing CA Spectrum SA. Default: 61616 SA Admin Defines the name of the CA Spectrum SA administrator user. You define this user during CA Spectrum SA installation, and the default name is samuser. Default: samuser Password Defines the password for the CA Spectrum SA administrator user.
UCF Broker Port Defines a valid port for the UCF Broker to interface with connectors and perform create, update, and delete operations on domain managers. Default: 8020 Verify Connection Defines whether to verify the SA Manager connection information when you click Next on the Integration Services Configuration page. Use DNS for name resolution Specifies whether to use DNS to normalize CI server names. If a reliable DNS mechanism is not in place (for example, no DNS server on the network, or CIs not defined to the DNS), disable DNS lookups to prevent import delays. If you disable DNS, all name resolution must be handled without DNS, which may require creation of a hosts file. Connector Name Defines the connector name. Change this name only if you are installing multiple instances of the connector to operate in a high availability cluster environment. In this case, define this property as the virtual host name associated with the cluster. Connectors must reference the same virtual host name to perform appropriately in a failover scenario. The CA ITCM Connector Configuration page opens. 6. Complete the following fields: DSM Manager Hostname (Domain\Username) Specifies the host name of the DSM domain manager. This field should include the domain name and the user name following the "DomainName\Username" convention. For example, if the Active Directory domain name is "Imp-User" and the user name is "Administrator," then the value to enter is "Imp-User\Administrator". DSM Manager User Name Specifies the user name for connecting to the domain manager, for example, Administrator. DSM Manager Password Specifies the password associated with the specified user name. Connector Instance Name Defines a unique name to identify the name of the connector instance (not related to CA ITCM or CA Spectrum SA database instance). For example, this name could be the connector host name or domain manager host name. 7. Click Next. The Service Startup page opens.
8. Specify whether to start the services automatically after installation, and click Next. The Pre-Installation Summary page opens. 9. Review your selections, and click Install. The connector installs on the system and integrates with the appropriate CA ITCM and CA Spectrum SA instances. The Install Complete page opens when the installation finishes. When you exit the installer, a Spectrum_Connector_InstallLog.log file is created at the root of the installation directory. Use this file to troubleshoot installation errors.
Chapter 3: Configuration
This chapter describes how to configure the CA ITCM connector after installation. This section contains the following topics: Post-installation Tasks (see page 21) Configure the CA ITCM Connector (see page 22) Configure Multiple Connector Instances on One Server (see page 24) Scoping the Data Published to CA Catalyst (see page 25) Reconciled Services (see page 26) Using Multi-Tenant Support for Inbound Operations (see page 27)
Post-installation Tasks
This section describes the post-installation tasks that are required for the CA ITCM connector.
Enabling Full Alert Functionality

To enable full Alert functionality on CA ITCM Release 12.5, you must set several configuration parameters on the domain manager after you install the CA ITCM connector. To set configuration parameters on the DSM domain manager for Alert functionality, run the following ccnfcmda commands on the domain manager:
ccnfcmda -cmd SetParameterValue -ps itrm/manager/am -pn PolicyNotification -v 2 ccnfcmda -cmd SetParameterValue -ps itrm/manager/am -pn MaxPolicyNotification -v 1000 ccnfcmda -cmd SetParameterValue -ps itrm/usd/manager -pn disablefoldernotifications -v 0
Note: These configuration parameters have no effect on earlier versions of CA ITCM.
Chapter 3: Configuration 21
Configure the CA ITCM Connector
After applying the configuration changes to the domain manager, a restart of the CAF service is needed, that is, close any DSM Explorers and DSM Reporters and run the following two commands (let the first one finish before issuing the second):
caf stop caf start
Enabling the Asset Collector for Inbound Functionality

To support inbound (subscribe) functionality for the CA ITCM connector, you must enable the Asset Collector on the DSM scalability server after you install the CA ITCM connector. To enable the Asset Collector on the DSM scalability server, run the following commands in the given order:
caf enable assetcollector caf start assetcollector

After installation, you can change the connector properties you defined during installation and edit other properties to refine connector behavior or adjust to changes in the integrated product. To configure the CA ITCM connector 1. Open the CA Spectrum SA Administration user interface and click the Administration tab. Note: For more information about accessing the CA Spectrum SA interfaces, see the CA Spectrum SA Administration Guide. The Administration page opens. 2. Expand Connector Configuration and the connector server name, and click the entry for the CA ITCM connector. A page opens for editing the CA ITCM connector. 3. (Optional) Change any properties in the Connector Controls table, and click Save. The control changes are saved. Note: Connector controls are common properties that control how the connector operates. For more information about the function of each connector control, see the CA Spectrum SA Connector Guide or click the Help button to access the Online Help.
4. Change any of the following properties in the Connection Details table and click Save: itcmManager Specifies the host name of the DSM domain manager. ssaRoot Specifies the CA Spectrum SA installation root path. username Specifies the user name associated with the DSM domain manager. password Specifies the encrypted password of the specified user name. Note: This field is populated by the installer and must not be changed manually. webServiceUrl Specifies the URL of CA ITCM Web Services. catalystScope Specifies the scope group. The default setting is Catalyst. Note: We recommend that this property not be changed. See the Scoping the Data Published to CA Catalyst section for detailed information. itcmAssetCollectorPath Specifies the path to the Asset Collector input directory on the DSM domain manager or scalability server where the CA ITCM connector is running. During installation, the connector installer automatically fetches the CA ITCM installed path from the environment to set the default path here. You can edit this value for the required path. Note: If the Asset Collector input path configured by the connector installer is changed to a new value, then the CA ITCM administrator must update the configuration policy to include the newly configured Asset Collector input path in CA ITCM. For detailed information about adding Asset Collector input directories to the DSM domain manager, see the CA IT Client Manager Implementation Guide. itcmCatalystSBTenantSupportEnabled Specifies whether multi-tenancy for inbound data operations is enabled or not. By default, this value is set to False. You can change the value to True to enable multi-tenancy for inbound operations.
Configure Multiple Connector Instances on One Server
reconciliationScheduleTime Specifies the daily reconciliation schedule based on the HH:MM time format. For example, if you specify 22:30, the connector initiates reconciliation for all the CIs between CA ITCM and CA Spectrum SA each day at 22:30 (10:30 PM). The property changes are saved. Important! Do not change any other properties in the Connection Details table. 5. (Optional) Change the host, port, or both values in the Launch in Context Details tables only if you changed either of these values in the Connection Details table. Note: Do not change any other values in the Launch in Context Details tables. The property changes are saved. 6. Click Stop, and wait until the connector status changes to Offline. 7. Click Start, and wait until the connector status changes to Online. The connector restarts. Depending on the type of connector, there can be a delay while the connector Status displays Online. Important! Do not perform rapid start and stop operations on the connector. Each stop and start sends the corresponding command to the connector. Rapid start and stop operations from the interface can cause these commands to queue on the connector and cause the connector to start and stop repeatedly until all commands in the queue are processed. More information: Using Multi-Tenant Support for Inbound Operations (see page 27)
Configure Multiple Connector Instances on One Server

CA ITCM connector does not support multiple connector instances on the same server.
Scoping the Data Published to CA Catalyst
Scoping the Data Published to CA Catalyst

The CA ITCM connector by default only publishes CIs that are part of the CA ITCM root computer group, Catalyst. This restriction means that when the connector is started and this group either does not exist or is empty nothing is published. To start publishing information to CA Catalyst, the Catalyst computer group must be created in the root of the Computer and Users group. Then, the Catalyst group must be populated with CIs. This step can be done in either of the following ways: By directly linking the computers you want to publish to the Catalyst group. By linking computer groups to the Catalyst group that contains the computers you want to publish.
Any computer groups linked to the Catalyst group are published as services and are available for import in CA Spectrum SA. Note: Be careful when publishing because the import can take a long time if too many computers are published. We recommend that you perform some tests before publishing larger numbers of CIs to determine the overall performance and avoid lengthy import operations. When a CI is moved out of scope (that is, unlinked from the scope group directly or indirectly), it is deleted from CA Catalyst even though it was not actually deleted from CA ITCM. Obviously, if a CI is deleted from CA ITCM, it is also deleted from CA Catalyst, regardless of scoping. The scoping mechanism can be disabled by editing the CA ITCM connector configuration file. To do so, open <SSA installation dir>\resources\Configurations\ itcm_<given name of connector>.xml and remove the catalystScope attribute from the ConnectionInfo tag. You can also rename the scoping group used by changing the value of the attribute to some other group name. After such a change the connector must be restarted.
Reconciled Services
Note: If the CA ITCM connector has already published data, you should not attempt to rename or delete the catalystScope group in CA ITCM or change the catalystScope group property to a name other than Catalyst in the CA ITCM connector configuration. If it is absolutely necessary to delete or rename the catalystScope group property to other than Catalyst, and delete or rename the group Catalyst in CA ITCM, follow this process: 1. Stop the connector. 2. Remove the connector from CA Spectrum SA using the SSA Admin Console. 3. Delete the connector cache by deleting the <SSA installation dir>\resources\ITCM\data\cache folder. 4. Update, add, or remove the catalystScope attribute. Note: Updating, adding, or removing the catalystScope attribute can result in the disconnection of the communication between CA ITCM and CA Spectrum SA, which stops all data flow in both directions through the CA ITCM connector. 5. Delete or rename the group Catalyst in CA ITCM. 6. Restart the connector.
Reconciled Services
When services (CA ITCM computer groups) with the same name are published by multiple CA ITCM connectors to a single CA Spectrum SA manager, the services sharing names get reconciled into single service instances. Consequently, any members of those services, regardless of origin, are linked to the reconciled service instance rather than to connector-specific ones. This action can appear as if the CA ITCM connectors have published more records than available in their domains, when in fact the service shows the records from all CA ITCM connectors. This behavior is expected. If this behavior is not desirable, either verify that the published CA ITCM computer groups are uniquely named across DSM domain managers or adjust the CA ITCM connector policy file located at SA_HOME\resources\Core\Catalogpolicy for each CA ITCM connector to prefix the published service name, making it unique across DSM domain managers.
Using Multi-Tenant Support for Inbound Operations
Using Multi-Tenant Support for Inbound Operations

If the CA ITCM connector is configured for multi-tenant support for inbound data operations, then the connector does the following upon finding a tenant ID field in the Computer CI received from CA Spectrum SA: 1. Extracts the tenant name from the catalyst Computer record. 2. Looks for the directory with this tenant name in the Asset Collector input path. 3. If there is an existing directory, copies the Asset Collector file to this path. 4. If a directory is not found, creates that directory and then copies the Asset Collector file to this path. The Asset Collector files remain in the tenant directories until the CA ITCM administrator updates the configuration policy to include the tenant directories created by the CA ITCM connector and to associate them with a CA ITCM tenant. For detailed information about adding Asset Collector input directories to the DSM domain manager, see the CA IT Client Manager Implementation Guide. If the CA ITCM connector finds an empty tenant ID field in the Computer CI received from CA Spectrum SA, it copies the Asset Collector file to itcmAssetCollectorPath as configured by the connector.
Chapter 4: Connector and Domain Manager Interaction

This chapter describes how the CA ITCM connector interacts with CA IT Client Manager and how CA ITCM objects are mapped to the USM schema in CA Spectrum SA. This section contains the following topics: Outbound from Connector Operations (see page 29) Inbound to Connector Operations (see page 31) USM Data Mapping (see page 31)
Outbound from Connector Operations

The CA ITCM connector can invoke outbound from connector operations to import the following CA ITCM data into consuming products such as CA Spectrum SA. The CA ITCM connector uses the following CA ITCM interfaces: Connection to Domain Manager Uses CA ITCM Web Services and CA ITCM event notifications to get data from the DSM domain manager. CI and relationship updates Uses the CA ITCM event notification subsystem to monitor addition, modification, and deletion of CA ITCM managed objects. Alerts Uses the CA ITCM event notification subsystem to monitor additions and modifications to CA ITCM alerts. Asset Collector When the CA ITCM connector has subscribed ComputerSystem CI data from CA Spectrum SA, the connector maps the inbound data to CA ITCM Computer object attributes and uses the CA ITCM Asset Collector to move this create/update data over to the CA ITCM MDB. Note: For more information, see Computer/ComputerSystem Inbound Attribute Mapping (see page 51) in the "CA ITCM/USM Attribute Mappings" appendix. Also, see the "Sample Asset Collector Input File (see page 55)" appendix.
Chapter 4: Connector and Domain Manager Interaction 29
Outbound from Connector Operations
The CA ITCM connector imports the following CA ITCM object types as the indicated USM classes as part of the outbound from connector operations: Computers as ComputerSystem All target Computers defined to and managed by the domain manager are imported as ComputerSystem CIs. Computer Groups as Service Computer groups are the collections of target computers and subgroups available on the enterprise and domain managers. A global group is created at the enterprise manager level and can be replicated to a domain manager. A local group is created at the domain manager level. All computer groups are imported as Service CIs that are part of the root group, Catalyst, created in the domain manager. Group Membership as BinaryRelationship Group Membership defines the relationship between computers and computer groups. A computer or a computer group can be a member of many groups. A computer group can have many computers and computer groups as members. All memberships defined to computers and computer groups are imported as BinaryRelationship CIs. Automatic ComputerSystem, Service, and BinaryRelationship Synchronization The CA ITCM connector continually synchronizes updates to ComputerSystem CIs, Services CIs, and BinaryRelationships CIs in CA ITCM with CA Spectrum SA. The CA ITCM connector can invoke the following operations in CA ITCM for outbound data operations: Alert Types All Alerts published by CA ITCM are of the compliance type. Inventory Compliance and Software Compliance Alerts are currently supported. Inventory Compliance Query policy violations are published as Alerts, and a violation is reflected as the inventory compliance status for computers. All query policy violations are imported as Inventory ComplianceStatus CIs. Software Compliance Software policy violations are published as Alerts, and a violation is reflected as the software compliance status for computers. All software policy violations are imported as Software ComplianceStatus CIs. Note: For more information about CA ITCM class objects, policies, and other concepts, see the CA IT Client Manager documentation.
Inbound to Connector Operations
Inbound to Connector Operations

The CA ITCM connector supports the following inbound to connector operations to modify the data in CA ITCM: CI updates ComputerSystem CI creation ComputerSystem CI deletes N/A Alert updates N/A Custom operations N/A
USM Data Mapping

When connectors import services and CIs from domain managers, they normalize the classes, properties, relationships, and severities in the domain manager to adhere to the USM schema. This section lists the CA ITCM classes, relationships, and severities and their USM mapping after the import. Note: For more information about CI property mapping, see the CA ITCM connector policy file located at SA_HOME\resources\Core\Catalogpolicy, where SA_HOME denotes the CA Spectrum SA installation directory. For more information about how connector policy maps product data to adhere to the USM schema, see the CA Spectrum SA Connector Guide.
Type Mapping
The following CA ITCM classes and constructed entities are mapped to the following USM types.
CA ITCM Class Computer ComputerStatus (Constructed)
USM Type ComputerSystem ComplianceStatus
USM Data Mapping
Note: For detailed information about attribute mapping for each type, relationship, or severity, see the "CA ITCM/USM Attribute Mappings" appendix.
Relationship Mapping
Relationships in the USM schema model either operational relationships, such as network connectivity, or services. The following CA ITCM classes and constructed entities are mapped to the following USM types.
CA ITCM Class ComputerGroupMember (Computer) ComputerGroupMember (Group) ComputerStatusRelationship ComputerGroup
USM Type IsComposedOf IsComposedOf HasDetail Service
Note: For detailed information about attribute mapping for each type, relationship, or severity, see the "CA ITCM/USM Attribute Mappings" appendix.
Severity Mapping
Policy-driven management is an important part of CA ITCM. Computers that violate a policy are in a noncompliant state. When computers violate a policy, an alert is published to CA Catalyst. When the computer no longer violates the policy, the alert is cleared.
CA ITCM Severity AssetQueryPolicyViolation SoftwarePolicyViolation
USM Severity Alert Alert
The severity mapping is determined as follows:
AssetQueryPolicyViolation.severity (CA ITCM)
SeverityEnum (USM)
Alert Warning
Critical Minor
USM Data Mapping
Info
Indeterminate
SoftwarePolicyViolation.prio (CA ITCM)
SeverityEnum (USM)
105 43 21
Minor Major Critical Note: For detailed information about attribute mapping for each type, relationship, or severity, see the "CA ITCM/USM Attribute Mappings" appendix.
Custom Mappings
Connectors use connector policy to map product data to adhere to the USM schema. Each connector includes default policy in an XML file in the following directory, where SA_HOME denotes the CA Spectrum SA installation directory:
SA_HOME\resources\Core\Catalogpolicy
The default policy establishes all mappings included in this section. You can customize CA ITCM connector policy to add mappings based on product changes or customizations, or to support entities not supported by the default policy. For example, if you have updated enumerations in the product that the default policy does not support, you can edit the connector policy to map these to USM enumerations. For more information about writing and customizing connector policy, see the CA Spectrum SA Connector Guide.
Chapter 5: Troubleshooting
This chapter includes troubleshooting information specific to CA ITCM. This section contains the following topics: Behavioral Limits of the CA ITCM Connector (see page 35) Known Issues (see page 36)
Behavioral Limits of the CA ITCM Connector

The CA ITCM connector currently has the following behavioral limitations: Inventory policy alerts existing in CA ITCM before the CA ITCM connector is installed are not published. Instead, inventory policy alerts are published for inventory policies that are evaluated after the CA ITCM connector is installed for the first time. When a group is deleted from CA ITCM, the respective service is not deleted from CA Spectrum SA; however, the service is not shown as managed by the specific connector instance. When a group, for example, childGroup, which is a child of another group, for example, parentGroup, is unlinked from the parentGroup, this group (childGroup) becomes a root service in the CA Spectrum SA console. Here parentGroup was an imported service. When an asset policy is modified, that is, the policy Severity is changed in CA ITCM, the CA ITCM connector does not update the alerts associated with this policy at that time. The alerts will be updated accordingly only when the policy is evaluated again and there is an change in the list of violators of the policy. In Manual Import Mode, if a service, for example, S2, is added to an existing imported service, for example, S1, CA Spectrum SA will add S2 as child of S1 but will not show the full service graph of service S2 in the console until service S2 or service S1 is imported again.
Chapter 5: Troubleshooting 35
Known Issues
Known Issues
Delay in Updating Relationships in CA Spectrum SA When Deleting a Computer System
When a computer system that is part of a service (group) is deleted in CA ITCM, the relationship between the service and the computer system is not updated in CA Spectrum SA until other changes to the service are done, triggering a refresh of relationships of that service in CA Spectrum SA. To avoid this scenario for CA ITCM Release 12.5, download two patches, RO20969 and RO21981, from Technical Support and apply them to the CA ITCM manager installation.
Deleting the catalystScope Group Is Not Supported

Deleting the catalystScope group, which by default is the root group Catalyst, is not supported in this release. Deleting this group can result in the incomplete deletion of all the data that has already been published.
CA ITCM Connector Is Offline

Symptom: CA ITCM connector appears to be offline. Solution: If the CA ITCM connector is offline, do the following: 1. Verify that the DSM domain manager is up and running. 2. Verify that the host name of the DSM domain manager in the Connection Details table is valid. 3. Verify the user and password details in the Connection Details table. 4. Restart the CA ITCM connector. More information: Configure the CA ITCM Connector (see page 22)
Known Issues
Unable to Link Additional Connector Instance to Another CA Spectrum SA Manager

Symptom: During the CA ITCM connector installation process, I wanted to create another connector instance. When I selected the "Additional instance" option, I was prompted for the CA ITCM domain manager name, user name, and password. There was no option, however, to link to another CA Spectrum SA manager. Solution: Any additional connector instances that are configured on the server must point to the same CA Spectrum SA manager installed on the machine. By design, it is not possible to configure additional connectors to point to another CA Spectrum SA manager. Therefore, there is no workaround.
Installation of Connector from Remote Shared Folder Fails to Install Integration Services
Symptom: I installed the CA ITCM connector from a remote shared folder, but the integration services and "jsw" module were not created in the installation directory as expected. So the connector did not get integrated with the CA Spectrum SA manager. Solution: To work around this installation merge module limitation, we recommend that you copy the installer locally and then copy the CA ITCM connector build onto the local machine to perform the installation. The CA Spectrum SA services are created as expected during the installation process.
Chapter 5: Troubleshooting 37
Chapter 6: High Availability Considerations

This section contains the following topics: Installing the CA ITCM Connector on a Failover Cluster (see page 39) The CA ITCM Connector on a High Availability Cluster (see page 40)
Installing the CA ITCM Connector on a Failover Cluster

CA ITCM supports failover in a Windows clustered environment. Before installing the CA ITCM connector on a failover cluster, you must first verify that the DSM domain manager is installed on that failover cluster. For detailed information about installing the DSM domain manager on a failover cluster, see the CA IT Client Manager Implementation Guide. To install the CA ITCM connector on a failover cluster 1. After installing the DSM domain manager, verify that the domain manager is up and running on the failover cluster. 2. Install the CA ITCM connector on the Active Node in the shared disk with cluster details (for Release 12.5 use the SQL Server name). Note: For detailed information, see the Failover Support and Hardware Replacement section in the CA IT Client Manager Implementation Guide. 3. Copy the HA toolkit folder with all its files (Disk1\SSAHA) of the CA Spectrum SA build image to the shared disk on Active Node. 4. Run the HA Resource Kit utility by opening the SSAHA folder on the shared drive and running setupMscs.hta. Note: For detailed information, see the Run the High Availability Resource Kit section in the CA Spectrum Service Assurance Implementation Guide. 5. Stop Active Node and start Passive Node so that the switchover can take place. 6. Once the switchover is complete, run the DSM domain manager script from Program Files\CA\DSM\bin\ActivateManagerNode.bat to activate the domain manager services on the Passive Node. 7. Install the ITCM connector on the Passive Node with the same instance name and location (shared disk) as that of the Active Node.
Chapter 6: High Availability Considerations 39
The CA ITCM Connector on a High Availability Cluster
8. Execute the High Availability Resource Kit utility on the Passive Node by running setupMscs.hta from the shared disk location. 9. Verify the status of the CA ITCM connector in the CA Spectrum SA manager admin UI. The status must be Online. 10. Stop Passive Node and start Active node so that switchover takes place. 11. Bring up all the DM services by running the script file, ActivateManagerNode.bat. 12. Restart the connector service in the active node.
The CA ITCM Connector on a High Availability Cluster

The CA ITCM connector can be installed in a high availability (HA) cluster environment but does not support automatic switchover. The connector has to be manually restarted after the domain manager (DM) services are up and running after the switchover. The following scenario is supported: DSM domain manager and the CA ITCM connector on the same cluster system with a CA Spectrum SA manager on a different server. Note: The DSM domain manager and the CA ITCM connector must be configured to use a disk shared between the cluster nodes. See the Failover Support and Hardware Replacement section in the CA IT Client Manager Implementation Guide for details on how to set up the domain manager in a cluster environment. The following scenario is not supported: DSM scalability server and the CA ITCM connector on the same cluster system.
Chapter 7: Uninstallation
This section contains the following topics: Uninstall and Reinstall the DSM Scalability Server (see page 41) Uninstall the CA ITCM Connector (see page 42)
Uninstall and Reinstall the DSM Scalability Server

The DSM scalability server on which the CA ITCM connector is installed can be uninstalled and reinstalled when necessary. To uninstall and reinstall the DSM scalability server 1. Stop the CA ITCM connector on the DSM scalability server. 2. Uninstall the scalability server. 3. Reboot the system. 4. Install the scalability server. Note: Verify first that the connector is not running at the time of installation. 5. After successful reinstallation of the scalability server, copy the NCWrapper.dll file to the folder C:\Program Files\CA\DSM\bin or Agent Technology\bin. NCWrapper.dll is available at C:\Program Files\CA\SSA\resources\ITCM\Utils or <SSA>\resources\ITCM\Utils, which is a backup file. 6. Start the CA ITCM connector.
Chapter 7: Uninstallation 41
Uninstall the CA ITCM Connector
Uninstall the CA ITCM Connector

You can uninstall the CA ITCM connector when it is no longer required. Note: The uninstallation of the connector is separate from the base uninstallation of any consuming product. To uninstall the CA ITCM connector 1. Select Start, Programs, CA, Service Assurance Manager, Uninstall CA ITCM on the computer where the connector is installed. The Uninstall CA Spectrum Service Assurance dialog opens. 2. Click Uninstall. The connector uninstalls and the Uninstall Complete page lists the result of the uninstallation, including any errors that occurred. 3. Open the CA Spectrum SA Administration user interface and click the Administration tab. The Administration page opens. 4. Expand Connector Configuration and the connector server name, and click the entry for the CA ITCM connector. A page opens for the CA ITCM connector. Verify that the connector status is Offline. 5. Click Remove Connector. A message prompts you to confirm that you want to delete the connector database entry. 6. Click OK. The CA ITCM connector registration is removed from the CA Spectrum SA database, and the connector name is removed from the tree on the Administration tab and all other interfaces.
Appendix A: CA ITCM/USM Attribute Mappings

This appendix provides detailed attribute mapping information for types, relationships, and severities. Note: The term "outbound" refers to the publication of data from CA ITCM to CA Catalyst and "inbound" refers to the subscription of data from CA Catalyst to CA ITCM. This section contains the following topics: Computer/ComputerSystem Outbound Attribute Mapping (see page 43) ComputerStatus/ComplianceStatus Outbound Attribute Mapping (see page 45) ComputerGroupMember/IsComposedOf Outbound Attribute Mapping for Computers (see page 46) ComputerGroupMember/IsComposedOf Outbound Attribute Mapping for Groups (see page 47) ComputerStatusRelationship/HasDetail Outbound Attribute Mapping (see page 48) ComputerGroup/Service Outbound Attribute Mapping (see page 49) AssetQueryPolicyViolation/Alert Outbound Attribute Mapping (see page 49) SoftwarePolicyViolation/Alert Outbound Attribute Mapping (see page 50) ComputerSystem/Computer Inbound Attribute Mapping (see page 51)
Computer/ComputerSystem Outbound Attribute Mapping

The following table shows how CA ITCM Computer class attributes are transformed into USM attributes for outbound data operations.
Computer (CA ITCM) "CA:00022 MdrProdInstance as in Connector Configuration cmp:<ComputerProperties.computerUUID> http://<ws_hostname>/wac/jsp/wac.jsp? context_launch_class= DSMComputerAsset&context_launch_id=<computerUUID> Generated by CA Spectrum SA ComputerProperties.computerCreationDate ComputerProperties.computerLastUpdatedDate
ComputerSystem (USM) MdrProduct MdrProdInstance MdrElementID UrlParams Label CreationTimestamp LastModTimestamp
Appendix A: CA ITCM/USM Attribute Mappings 43
Computer/ComputerSystem Outbound Attribute Mapping
Computer (CA ITCM) <extract the value from notification and use here> <extract the value from notification and use here> ComputerProperties.computerVendorName ComputerInventory.System.Model ComputerProperties.computerAssetTag ComputerProperties.computerPrimaryNetworkAddress ComputerProperties.computerPrimaryMACAddress ComputerInventory.Network.TCP/IP.IPAddress ComputerInventory.Network.TCP/IPv6.IPv6Address ComputerProperties.computerHostName ComputerProperties.computerSystemID Must be derived from the fields ComputerInventory.System.Type AND ComputerInventory.System.OperatingSystem.VirtualMachine as per logic used by other modules in CA ITCM ComputerInventory.System.TotalMemory ComputerInventory.Storage.TotalDiskSpace ComputerInventory.System.Processor[0].Model ComputerInventory.System.Processor[0].CoreCount AND ComputerInventory.System.NoOfProcessors Note: Calculate NoOfProcessors * CoreCount (physical cores, ignore HT). ComputerInventory.System.Processor[0].MaxSpeed ComputerInventory.System.OperatingSystem.OperatingSystem ComputerInventory.System.OperatingSystem.Version
ComputerSystem (USM) LastModActivity DeletionTimestamp Vendor Model AssetNumber PrimaryDnsName PrimaryMacAddress PrimaryIPV4Address PrimaryIPV6Address ComputerName BiosSystemID SystemType
MemoryInGB StorageInGB ProcessorType NumberOfCores
ProcessorSpeedInGHz PrimaryOSType PrimaryOSVersion
ComputerStatus/ComplianceStatus Outbound Attribute Mapping
ComputerStatus/ComplianceStatus Outbound Attribute Mapping

ComplianceStatus is a constructed entity in that is used to reflect the status of a particular aspect of management. In the case of CA ITCM, there are two aspects published, one for overall software policy (Software) compliance and one for overall asset query policy (Inventory) compliance. Each published computer will have one of each. The ComputerStatus attributes are transformed into USM attributes as shown in the following table.
ComputerStatus (CA ITCM) CA:00022 MdrProdInstance as in Connector Configuration csi:<ComputerProperties.computerUUID> OR css:<ComputerProperties.computerUUID> http://<ws_hostname>/wac/jsp/wac.jsp? context_launch_class= DSMComputerAsset&context_launch_id=<computerUUID> Generated by CA Spectrum SA ComputerProperties.computerCreationDate <extract the value from policy notification and use here> <extract the value from policy notification and use here> <extract the value from policy notification and use here> ComputerProperties.computerLabel + ("Software" or "Inventory") Software or Inventory from ComplianceContextEnum Compliant or NotCompliant from ComplianceStatusEnum <same as LastModTimestamp>
ComplianceStatus (USM) MdrProduct MdrProdInstance MdrElementID
UrlParams Label CreationTimestamp LastModTimestamp LastModActivity DeletionTimestamp ComplianceID ComplianceContext ComplianceStatus LastVerifiedTimestamp
ComputerGroupMember/IsComposedOf Outbound Attribute Mapping for Computers
ComputerGroupMember/IsComposedOf Outbound Attribute Mapping for Computers

CA ITCM group membership for computers is transformed into USM relationships as shown in the following table.
ComputerGroupMember (Computer) (CA ITCM) CA:00022 MdrProdInstance as in Connector Configuration brsvccmp:<ComputerGroupProperties.groupUUID>: <ComputerProperties.computerUUID> <extract the value from notification and use here> <extract the value from notification and use here> <extract the value from notification and use here> <extract the value from notification and use here> <MdrProduct of parent Service> <MdrProdInstance of parent Service> <MdrElementID of parent Service> <MdrProduct of child ComputerSystem> <MdrProdInstance of child ComputerSystem> <MdrElementID of child ComputerSystem> N/A or <MdrProduct of Imported Service> N/A or <MdrProdInstance of Imported Service> N/A or <MdrElementID of Imported Service> IsComposedOf from RelationshipSemanticEnum
IsComposedOf (USM) MdrProduct MdrProdInstance MdrElementID CreationTimestamp LastModTimestamp LastModActivity DeletionTimestamp SourceMdrProduct SourceMdrProdInstance SourceMdrElementID TargetMdrProduct TargetMdrProdInstance TargetMdrElementID ScopeMdrProduct ScopeMdrProdInstance ScopeMdrElementID Semantic
ComputerGroupMember/IsComposedOf Outbound Attribute Mapping for Groups
ComputerGroupMember/IsComposedOf Outbound Attribute Mapping for Groups

CA ITCM group membership for groups is transformed into USM relationships as shown in the following table.
ComputerGroupMember (Group) (CA ITCM) CA:00022 MdrProdInstance as in Connector Configuration brsvcsvc:<ParentComputerGroupProperties.groupUUID>: <ChildComputerGroupProperties.groupUUID> <extract the value from notification and use here> <extract the value from notification and use here> <extract the value from notification and use here> <extract the value from notification and use here> <MdrProduct of parent Service> <MdrProdInstance of parent Service> <MdrElementID of parent Service> <MdrProduct of child Service > <MdrProdInstance of child Service > <MdrElementID of child Service > N/A or <MdrProduct of Imported Service> N/A or <MdrProdInstance of Imported Service> N/A or <MdrElementID of Imported Service> IsComposedOf from RelationshipSemanticEnum
IsComposedOf (USM) MdrProduct MdrProdInstance MdrElementID CreationTimestamp LastModTimestamp LastModActivity DeletionTimestamp SourceMdrProduct SourceMdrProdInstance SourceMdrElementID TargetMdrProduct TargetMdrProdInstance TargetMdrElementID ScopeMdrProduct ScopeMdrProdInstance ScopeMdrElementID Semantic
ComputerStatusRelationship/HasDetail Outbound Attribute Mapping
ComputerStatusRelationship/HasDetail Outbound Attribute Mapping

ComputerStatusRelationship is a constructed relationship entity in CA ITCM. The ComputerStatusRelationship attributes are transformed into USM attributes as shown in the following table.
ComputerStatusRelationship (CA ITCM) CA:00022 MdrProdInstance as in Connector Configuration brcmpcsi:<ComputerProperties.computerUUID>: <ComputerProperties.computerUUID> OR brcmpcss:<ComputerProperties.computerUUID>: <ComputerProperties.computerUUID> ComputerProperties.computerCreationDate ComputerProperties.computerCreationDate Created for its active life time then Deleted <extract the value from computer delete notification and use here> <MdrProduct of ComputerSystem> <MdrProdInstance of ComputerSystem> <MdrElementID of ComputerSystem> <MdrProduct of associated ComplianceStatus> <MdrProdInstance of associated ComplianceStatus> <MdrElementID of associated ComplianceStatus> N/A or <MdrProduct of Imported Service> N/A or <MdrProdInstance of Imported Service> N/A or <MdrElementID of Imported Service> HasDetail from RelationshipSemanticEnum
HasDetail (USM) MdrProduct MdrProdInstance MdrElementID
CreationTimestamp LastModTimestamp LastModActivity DeletionTimestamp SourceMdrProduct SourceMdrProdInstance SourceMdrElementID TargetMdrProduct TargetMdrProdInstance TargetMdrElementID ScopeMdrProduct ScopeMdrProdInstance ScopeMdrElementID Semantic
ComputerGroup/Service Outbound Attribute Mapping
ComputerGroup/Service Outbound Attribute Mapping

The CA ITCM concept of computer groups is used for USM services. You may group computers together and give the group a name, for example, Server Hall A. The service is affected by its computers. The services are published as a flat list. Nested groups are considered. Note: Only customer-created groups are published as services. The CA ITCM computer groups are transformed into USM services as shown in the following table.
ComputerGroup (CA ITCM) CA:00022 MdrProdInstance as in Connector Configuration svc:<ComputerGroupProperties.groupUUID> http://<ws_hostname>/wac/jsp/wac.jsp? context_launch_class= DSMCustomGroup&context_launch_id=<groupUUID> Generated by CA Spectrum SA ComputerGroupProperties.groupDescription ComputerGroupProperties.groupCreationDate ComputerGroupProperties.groupLastUpdatedDate <extract the value from notification and use here> <extract the value from notification and use here> ComputerGroupProperties.groupLabel "0"
Service (USM) MdrProduct MdrProdInstance MdrElementID UrlParams Label Description CreationTimestamp LastModTimestamp LastModActivity DeletionTimestamp ServiceName ServiceVersion
AssetQueryPolicyViolation/Alert Outbound Attribute Mapping

The CA ITCM asset policy violation attributes are transformed into USM severity attributes as shown in the following table.
AssetQueryPolicyViolation (CA ITCM) CA:00022 MdrProdInstance as in Connector Configuration
Alert (USM) MdrProduct MdrProdInstance
SoftwarePolicyViolation/Alert Outbound Attribute Mapping
AssetQueryPolicyViolation (CA ITCM) alrt:<AssetQueryPolicyViolation.policyUUID>: <ComputerProperties.computerUUID> http://<ws_hostname>/wac/jsp/wac.jsp? context_launch_class= DSMQryPolicy&context_launch_id=< policyUUID > <extract the value from notification and use here> Use Compliance from AlertTypeEnum Map AssetQueryPolicyViolation.severity Alert,Warning, Info to Critical,Minor, Indeterminate from SeverityEnum. Note: Clear the alert by sending Normal. <MdrProduct of associated Inventory ComplianceStatus of affected ComputerSystem> <MdrProdInstance of associated Inventory ComplianceStatus of affected ComputerSystem> <MdrElementID of associated Inventory ComplianceStatus of affected ComputerSystem> AssetQueryPolicyViolation.name True
Alert (USM) MdrElementID UrlParams ReportTimestamp AlertType Severity
AlertedMdrProduct AlertedMdrProdInstance AlertedMdrElementID Summary IsClearable
SoftwarePolicyViolation/Alert Outbound Attribute Mapping

The CA ITCM software policy violation attributes are transformed into USM severity attributes as shown in the following table.
SoftwarePolicyViolation (CA ITCM) CA:00022 MdrProdInstance as in Connector Configuration alrt:<SoftwarePolicyViolation.policyUUID>: <ComputerProperties.computerUUID> http://<ws_hostname>/wac/jsp/wac.jsp? context_launch_class= DSMSftPolicy&context_launch_id=<policyUUID> <extract the value from notification and use here> Use Compliance from AlertTypeEnum Map SoftwarePolicyViolation.prio 105 to Minor, 43 to Major, and 21 to Critical from SeverityEnum. Note: Clear the alert by sending Normal.
Alert (USM) MdrProduct MdrProdInstance MdrElementID UrlParams ReportTimestamp AlertType Severity
ComputerSystem/Computer Inbound Attribute Mapping
SoftwarePolicyViolation (CA ITCM) <MdrProduct of associated Software ComplianceStatus of affected ComputerSystem> <MdrProdInstance of associated Software ComplianceStatus of affected ComputerSystem> <MdrElementID of associated Software ComplianceStatus of affected ComputerSystem> SoftwarePolicy.name True
Alert (USM) AlertedMdrProduct AlertedMdrProdInstance AlertedMdrElementID Summary IsClearable

The USM ComputerSystem attributes are transformed into CA ITCM Computer class attributes as shown in the following table.
ComputerSystem (USM) MdrProdInstance MdrElementID Description TenantID Vendor
Computer (CA ITCM) ComputerInventory.Hardware.UserDefinedInventory. Catalyst.Catalyst Instance <Derive only ComputerProperties.computerHostKey> ComputerInventory.Hardware.UserDefinedInventory. Catalyst.Description ComputerInventory.Hardware.UserDefinedInventory. Catalyst.TenantID ComputerProperties.computerVendorName AND ComputerInventory.Hardware.System.Vendor ComputerInvetory.Hardware.System.Model ComputerProperties.computerSerialNumber AND ComputerInventory.Hardware.System.SerialNumber ComputerProperties.computerAssetTag AND ComputerInventory.Hardware.System.AssetTag ComputerProperties.computerPrimaryNetworkAddress AND ComputerInventory.Hardware.Network.HostName AND ComputerInventory.Hardware.Network.TCP/IP[0].HostName
Model PhysSerialNumber
AssetNumber
PrimaryDnsName
ComputerSystem (USM) OtherDnsNames SysName PrimaryMacAddress
Computer (CA ITCM) ComputerInventory.Hardware.Network.TCP/IP[1].HostName ComputerInventory.Hardware.System.SystemName ComputerProperties.computerPrimaryMACAddress AND ComputerInventory.Hardware.Network.TCP/IP[0]. MacAddress AND ComputerInventory.Hardware.Network.TCP/IPv6. IPv6Addresses.MacAddress ComputerInventory.Hardware.Network.TCP/IP[1]. MacAddress ComputerProperties.computerPrimaryIPAddress AND ComputerInventory.Hardware.Network.IPAddress AND ComputerInventory.Hardware.Network.TCP/IP[0].IPAddress ComputerInventory.Hardware.Network.TCP/IP[0].Domain ComputerInventory.Hardware.Network.TCP/IPv6. IPv6Addresses.IPv6Address ComputerInventory Hardware.Network.TCP/IPv6. IPv6Addresses.Domain ComputerInventory.Hardware.Network.TCP/IP[1].IPAddress ComputerInventory.Hardware.Network.TCP/IP[1].Domain ComputerProperties.computerHostName AND ComputerInventory.Hardware.Network.ComputerName ComputerProperties.computerSystemID ComputerInventory.Hardware.System.Type ComputerInventory.Hardware.System.TotalMemory ComputerInventory.Hardware.Storage.TotalDiskSpace ComputerInventory.Hardware.System.Processor[0].Model ComputerInventory.Hardware.system. TotalProcessorCoreCount ComputerInventory.Hardware.System.Processor[0]. MaxSpeed
OtherMacAddresses PrimaryIPV4Address
PrimaryIPV4AddressWithDomain PrimaryIPV6Address PrimaryIPV6AddressWithDomain OtherIPAddresses OtherIPAddressesWithDomain ComputerName
BiosSystemID SystemType MemoryInGB StorageInGB ProcessorType NumberOfCores ProcessorSpeedInGHz
ComputerSystem (USM) PrimaryOSType
Computer (CA ITCM) ComputerInventory.Hardware.OperatingSystem. OperatingSystem AND ComputerProperties.computerClassID (after transformation per logic given in itcm_policySB.xml) ComputerInventory.Hardware.OperatingSystem.Version ComputerInventory.Hardware.OperatingSystem.ServicePack
PrimaryOSVersion OtherOSDetails
Appendix B: Sample Asset Collector Input File

The following is a sample .xiu file generated by the CA ITCM connector during inbound create/update data operations. In this sample, <Origin> is always set to "Catalyst" and <trustlevel> is always set to 4. Other values are extracted from CA Spectrum SA Computer records.
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <asset translator="ACBsFmt" version="1_0"> <general> <host_name>sample02-xp</host_name> <host_key>E8F80F8C-77C2-48EF-8A23-8E0A6141EE59</host_key> <vendor>Dell Inc.</vendor> <class_id>24</class_id> <system_id>44454C4C-3700-1032-8038-C8C04F324253</system_id> <asset_tag>N/A</asset_tag> <serial_number>H7282BS</serial_number> <default_address>172.24.123.456</default_address> <default_hostname>sample02-xp.example.com</default_hostname> <default_mac>01:23:45:67:89:AB</default_mac> <collect_time>1283563312</collect_time> <origin>Catalyst</origin> <trustlevel>4</trustlevel> </general> <hardware> <group name="GeneralInventory"> <group name="System"> <attribute name="System Name" type="string">sample02-sys-xp</attribute> <attribute name="Model" type="string">OptiPlex 755</attribute> <attribute name="Type" type="string">Mini Tower</attribute> <attribute name="Total Memory" subtype="byte" type="int64">1073741824</attribute> <attribute name="Total Processor Core Count" type="int32">10</attribute> <attribute name="Vendor" type="string">Dell Inc.</attribute> <attribute name="Serial Number" type="string">H7282BS</attribute> <attribute name="Asset Tag" type="string">N/A</attribute> <attribute name="System ID" type="string">44454C4C-3700-1032-8038-C8C04F324253</attribute> <group name="Processors"> <attribute name="Model" type="string">Intel Core2 Duo E7200</attribute> <attribute name="Max Speed" subtype="normal" type="int64">5200.0</attribute> </group>
Appendix B: Sample Asset Collector Input File 55
</group> <group name="Network"> <attribute name="Computer Name" type="string">sample02-xp</attribute> <attribute name="IP Address" type="string">172.24.123.456</attribute> <attribute name="Host Name" type="string">sample02-xp.example.com</attribute> <attribute name="IPv4 Enabled" type="string">Enabled</attribute> <attribute name="IPv6 Enabled" type="string">Enabled</attribute> <group name="TCPIP" tableid="0001"> <attribute name="IP Address" type="string">172.24.123.456</attribute> <attribute name="MAC Address" type="string">01:23:45:67:89:AB</attribute> <attribute name="Host Name" type="string">sample02-xp. example.com</attribute> <attribute name="Domain" type="string">internal.example.com</attribute> </group> <group name="TCPIP" tableid="0002"> <attribute name="IP Address" type="string">172.24.7.89</attribute> <attribute name="MAC Address" type= "string">01:23:45:67:89:CD</attribute> <attribute name="Host Name" type= "string">sample02-other.example.com</attribute> <attribute name="Domain" type="string">other.example.com</attribute> </group> <group name="$TCP/IPV6$"> <group name="$IPv6 Addresses$"> <attribute name="IPv6 Address" type= "string">0123:1234:ABCD:1111:0000:0000:0000:0000</attribute> <attribute name="MAC Address" type= "string">01:23:45:67:89:AB</attribute> <attribute name="Domain" type="string">ipv6.example.com</attribute> </group> </group> </group> <group name="OperatingSystem"> <attribute name="Version" type="string">5.1</attribute> <attribute name="Operating System" type= "string">windows xp professional</attribute> <attribute name="Service Pack" type="string">Windows SP1</attribute> </group> <group name="Storage"> <attribute name="Total Disk Space" subtype="byte" type= "int64">115964116992</attribute> </group> </group>
<group name="AdditionalInventory"/> <group name="UserDefinedInventory"> <group name="Catalyst"> <attribute name="Catalyst Instance" type= "string">ssaqa25demo2.example.com</attribute> <attribute name="Description" type= "string">Sample CI created for testing</attribute> <attribute name="TenantID" type= "string">ITCMSBTenantSupport</attribute> </group> </group> </hardware> </asset>
Appendix B: Sample Asset Collector Input File 57
Appendix C: Third-Party Acknowledgements

This section contains the following topics: Apache License Version 2.0 (see page 59) Apache Log4j 1.2.15 (see page 63)
Apache License Version 2.0

This product includes Apache Axis 1.4 which is distributed in accordance with the following license agreement: Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
Appendix C: Third-Party Acknowledgements 59
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: a. b. c. You must give any other recipients of the Work or Derivative Works a copy of this License; and You must cause any modified files to carry prominent notices stating that You changed the files; and You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
d.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Apache Log4j 1.2.15
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
============================================== ======================= NOTICE file corresponding to section 4(d) of the Apache License, Version 2.0, in this case for the Apache Axis distribution. ============================================== =======================
This product includes software developed by The Apache Software Foundation (http://www.apache.org/).
Apache Log4j 1.2.15

This product includes Log4j 1.2.15 which was developed by the Apache Software Foundation. This Apache software is distributed in accordance with the following license agreement: Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
Apache Log4j 1.2.15
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
Apache Log4j 1.2.15
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: a. b. c. You must give any other recipients of the Work or Derivative Works a copy of this License; and You must cause any modified files to carry prominent notices stating that You changed the files; and You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
d.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
Apache Log4j 1.2.15
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS
Apache Log4j 1.2.15
APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Index
A
Alerts 7, 29, 31, 32 Asset Collector component 11, 16, 21, 29, 55 attribute mappings 43, 45, 46, 47, 48, 49, 50, 51
I
imported information 29, 31 inbound to connector operations 27, 31 input files, Asset Collector 11, 16, 21, 55 Insight use case 12 installation installing CA ITCM Connector 17 operating environments, supported 15 post-installation tasks 21 prerequisites 16 scenarios 16 integration inbound to connector operations 27, 31 limitations 35 outbound from connector operations 29 scenarios 10 use cases 12
B
BSM use case 12
C
CA Catalyst connectors overview 7 terminology 7 CA ITCM architecture 9 CA ITCM event notification subsystem 11, 29 CA ITCM Web Services 11, 16 Catalyst root computer group 25, 29 configuration connector 22, 24, 25 domain manager 21 Configuration Items (CIs) 7, 29, 31 connector import connector integration 11 inbound to connector operations 27, 31 limitations 35 USM data mapping 31, 32, 33 connector integration 11 custom mappings 33
M
multi-tenant support 27
O
operating environments, supported 15 outbound from connector operations 29 overview 7
P
ports and protocols 16 post-installation tasks 21
D
data mapping custom mappings 33 relationship mapping 32, 46, 47, 48, 49 scoping data 25 severity mapping 32, 49, 50 type mapping 31, 43, 45
R
reconciled services 26 reinstalling the scalability server 41 relationship mapping 32, 46, 47, 48, 49
S
scoping data 25 Services 7, 26 severity mapping 32, 49, 50
F
failover cluster environment 39
H
high availability (HA) cluster environment 40
T
terminology 7 troubleshooting 35, 36, 37
Index 69
type mapping 31, 43, 45
U
Unified Service Model (USM) 7, 31 uninstalling the CA ITCM connector 42 uninstalling the scalability server 41 use cases 12 USM data mapping 31, 32, 33

ITCM ConnectorGuide ENU

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ITCM ConnectorGuide ENU

Uploaded by

Copyright:

Available Formats

CA Catalyst

CA IT Client Manager Connector Guide

CA Technologies Product References

Chapter 4: Connector and Domain Manager Interaction

Chapter 6: High Availability Considerations

Appendix A: CA ITCM/USM Attribute Mappings

Appendix B: Sample Asset Collector Input File Appendix C: Third-Party Acknowledgements

Apache License Version 2.0 ................................................................... 59 Apache Log4j 1.2.15 .......................................................................... 63

6 CA IT Client Manager Connector Guide

About This Guide

8 CA IT Client Manager Connector Guide

The following graphic illustrates CA IT Client Manager tier structure:

10 CA IT Client Manager Connector Guide

Business Service Management (BSM) Use Case

Insight Use Case

12 CA IT Client Manager Connector Guide

Both goals are reflected in the following flowchart:

Operating Environment Support

16 CA IT Client Manager Connector Guide

Install the CA ITCM Connector

Install the CA ITCM Connector

Install the CA ITCM Connector

18 CA IT Client Manager Connector Guide

Install the CA ITCM Connector

Install the CA ITCM Connector

20 CA IT Client Manager Connector Guide

Enabling Full Alert Functionality

Note: These configuration parameters have no effect on earlier versions of CA ITCM.

Configure the CA ITCM Connector

Enabling the Asset Collector for Inbound Functionality

Configure the CA ITCM Connector

22 CA IT Client Manager Connector Guide

Configure the CA ITCM Connector

Configure Multiple Connector Instances on One Server

Configure Multiple Connector Instances on One Server

24 CA IT Client Manager Connector Guide

Scoping the Data Published to CA Catalyst

Scoping the Data Published to CA Catalyst

26 CA IT Client Manager Connector Guide

Using Multi-Tenant Support for Inbound Operations

Using Multi-Tenant Support for Inbound Operations

Chapter 4: Connector and Domain Manager Interaction

Outbound from Connector Operations

Chapter 4: Connector and Domain Manager Interaction 29

Outbound from Connector Operations

30 CA IT Client Manager Connector Guide

Inbound to Connector Operations

Inbound to Connector Operations

USM Data Mapping

CA ITCM Class Computer ComputerStatus (Constructed)

USM Type ComputerSystem ComplianceStatus

Chapter 4: Connector and Domain Manager Interaction 31

USM Data Mapping

CA ITCM Class ComputerGroupMember (Computer) ComputerGroupMember (Group) ComputerStatusRelationship ComputerGroup

USM Type IsComposedOf IsComposedOf HasDetail Service

CA ITCM Severity AssetQueryPolicyViolation SoftwarePolicyViolation

USM Severity Alert Alert

The severity mapping is determined as follows:

AssetQueryPolicyViolation.severity (CA ITCM)

32 CA IT Client Manager Connector Guide

USM Data Mapping

SoftwarePolicyViolation.prio (CA ITCM)