Free Essay

Hp Discovery Content Guide

In:

Submitted By kareemhamed
Words 15907
Pages 64
HP Universal CMDB
Software Version: UCMDB 10.10, CP 13.00

Universal Discovery Content Guide - HP Integrations

Document Release Date: November 2013 Software Release Date: November 2013

Legal Notices
Warranty
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.

Restricted Rights Legend
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notice
© Copyright 1996 - 2013 Hewlett-Packard Development Company, L.P.

Trademark Notices
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated. AMD and the AMD Arrow symbol are trademarks of Advanced Micro Devices, Inc. Google™ and Google Maps™ are trademarks of Google Inc. Intel®, Itanium®, Pentium®, and Intel® Xeon® are trademarks of Intel Corporation in the U.S. and other countries. Java and Oracle are registered trademarks of Oracle Corporation and/or its affiliates. Microsoft®, Windows®, Windows NT®, Windows® XP, and Windows Vista® are U.S. registered trademarks of Microsoft Corporation. UNIX® is a registered trademark of The Open Group. l l l l l l This product includes software developed by the Apache Software Foundation (http://www.apache.org/). This product includes OpenLDAP code from OpenLDAP Foundation (http://www.openldap.org/foundation/). This product includes GNU code from Free Software Foundation, Inc. (http://www.fsf.org/).This product includes JiBX code from Dennis M. Sosnoski. This product includes the XPP3 XMLPull parser included in the distribution and used throughout JiBX, from Extreme! Lab, Indiana University. This product includes the Office Look and Feels License from Robert Futrell (http://sourceforge.net/projects/officelnfs). This product includes JEP - Java Expression Parser code from Netaphor Software, Inc. (http://www.netaphor.com/home.asp).

Documentation Updates
The title page of this document contains the following identifying information: l l l Software Version number, which indicates the software version. Document Release Date, which changes each time the document is updated. Software Release Date, which indicates the release date of this version of the software.

To check for recent updates or to verify that you are using the most recent edition of a document, go to: http://h20230.www2.hp.com/selfsolve/manuals This site requires that you register for an HP Passport and sign in. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html Or click the New users - please register link on the HP Passport login page. You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.

Support
Visit the HP Software Support Online web site at: http://www.hp.com/go/hpsoftwaresupport This web site provides contact information and details about the products, services, and support that HP Software offers. HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to: l l l l l l Search for knowledge documents of interest Submit and track support cases and enhancement requests Download software patches Manage support contracts Look up HP support contacts Review information about available services

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 2 of 191

Universal Discovery Content Guide - HP Integrations

l l

Enter into discussions with other software customers Research and register for software training

Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html To find more information about access levels, go to: http://h20230.www2.hp.com/new_access_levels.jsp HP Software Solutions Now accesses the HPSW Solution and Integration Portal Web site. This site enables you to explore HP Product Solutions to meet your business needs, includes a full list of Integrations between HP Products, as well as a listing of ITIL Processes. The URL for this Web site is http://h20230.www2.hp.com/sc/solutions/index.jsp

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 3 of 191

Universal Discovery Content Guide - HP Integrations Contents

Contents
Chapter 1: HP APM Push Integration
Overview How Data is Synchronized Between HP APM and UCMDB Supported Versions How to Integrate UCMDB and HP APM Create an Integration Point between HP APM and UCMDB Adapter Push CI Data from UCMDB to HP APM Schedule Data Push Jobs View UCMDB Data in HP APM Default Entity and Field Mappings between HP APM and UCMDB Default Field Mappings between HP APM Application and UCMDB BusinessApplication Default Field Mappings between HP APM Process and UCMDB BusinessProcess Default Field Mappings between HP APM Location and UCMDB Location Default Field Mappings between HP APM Server and UCMDB Node REST APIs Called in the Integration Delete a Request Customize the Integration Overview Data Flow Architecture Integration TQL Queries Customize an Existing Mapping Add a New Mapping to the Integration Troubleshooting and Limitations Limitations Troubleshooting Problems Logs

9
9 9 11 11 12 16 16 20 21 22 22 24 25 26 27 27 28 29 29 29 29 30 33 33 34 35

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 4 of 191

Universal Discovery Content Guide - HP Integrations Contents

Chapter 2: HP Asset Manager Integration
Overview Supported Versions How to Integrate Asset Manager with UCMDB Adapter Troubleshooting and Limitations

36
37 37 37 40 40

Chapter 3: HP Asset Manager Push Integration
Quick Start Overview Supported Versions How to Integrate UCMDB and Asset Manager Validate Pre-Loaded Data in Asset Manager Set Up Asset Manager Set Up UCMDB Push CI Data from UCMDB to Asset Manager How to View UCMDB Data in Asset Manager Nodes Business Elements How to Schedule Data Push Jobs Installed Software How to Tailor the Integration Integration Architecture Data Flow Architecture Integration TQL Queries Reconciliation Proposals Asset Manager Rules and Flows Data Mapping Push Mapping Basic Information Reconciliation Target CI Validation

41
42 42 43 44 44 44 48 52 56 57 57 57 59 61 62 62 63 63 64 64 65 65 66 67

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 5 of 191

Universal Discovery Content Guide - HP Integrations Contents

Reference Attribute Attribute Reconciliation Action on Delete Enum Attribute Ignored Attributes How to Change Adapter Settings How to Customize an Existing Mapping How to Add a New Mapping to the Integration Frequently Asked Questions Troubleshooting and Limitations Logs

68 69 69 70 70 71 72 73 77 79 84

Chapter 4: HP Configuration Manager - Federating KPI Data
Overview How to Consume Federated KPI Data from Configuration Manager Troubleshooting and Limitations

85
86 87 89

Chapter 5: HP Configuration Manager - Federating Policy Data
Overview How to Consume Federated Policy Data from Configuration Manager Troubleshooting and Limitations

90
91 92 96

Chapter 6: HP Discovery and Dependency Mapping Inventory Integration 97
Overview Supported Versions DDMI Adapter How to Populate the CMDB with Data from DDMI How to Federate Data with DDMI How to Customize the Integration Data Model in UCMDB Predefined Queries for Population Jobs DDMI Adapter Configuration Files Troubleshooting and Limitations 98 98 98 100 101 102 103 103 104

Chapter 7: HP Network Automation (NA) Integration
Overview

105
106

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 6 of 191

Universal Discovery Content Guide - HP Integrations Contents

Supported Versions Topology How to Pull Data Topology from an HP NA Server using a Java Client Pull Topology from HP NA Adapter Limitations

106 106 107 109 110

Chapter 8: HP Network Node Manager (NNMi) Integration
Overview Use Cases Supported Versions NNMi - UCMDB Integration Architecture Topology How to Run NNMi–UCMDB Integration How to Manually Add the IpAddress CI of the NNMi Server How to Set Up HP NNMi–HP UCMDB Integration NNMi Integration Job How to Customize Integration Troubleshooting and Limitations

111
112 112 112 113 113 114 116 117 118 121 124

Chapter 9: HP Service Anywhere Push Integration
Overview How Data is Synchronized Between UCMDB and Service Anywhere Supported Versions How to Integrate UCMDB and Service Anywhere Setup the UCMDB Push CI Data from the UCMDB to Service Anywhere Schedule Data Push Jobs Tailor the Integration Integration Architecture Data Flow Architecture Integration TQL Queries Service Anywhere Rules and Flows Data Mapping

126
127 127 128 128 128 131 134 135 135 135 136 136 136

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 7 of 191

Universal Discovery Content Guide - HP Integrations Contents

Push Mapping Change Adapter Settings Customize an Existing Mapping Add a New Mapping to the Integration Troubleshooting and Limitations

136 138 139 140 143

Chapter 10: HP ServiceCenter/Service Manager Integration
Overview Supported Versions Data Push Flow Federation Use Cases Viewing the Actual State The serviceDeskConfiguration.xml File How to Deploy the Adapter – Typical Deployment How to Deploy the ServiceDesk Adapter How to Add an Attribute to the ServiceCenter/Service Manager CIT How to Communicate with Service Manager over SSL How to Add a New Attribute to an Existing CI Type How to Add a New CI Type Predefined Queries for Data Push Jobs Flow and Configuration Troubleshooting and Limitations

144
145 145 146 147 148 150 156 156 161 167 168 169 170 171 177

Chapter 11: HP Systems Insight Manager (HP SIM) Integration
Overview Supported Versions HP SIM Integration Mechanism How to Discover HP SIM Data Center Infrastructure SIM WebService Ports Job SIM Integration by WebServices Job Instance Views Troubleshooting and Limitations

180
181 181 181 183 186 187 189 191

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 8 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

Chapter 1: HP APM Push Integration
This section includes the following: l "Overview" below "How to Integrate UCMDB and HP APM" on page 11 "View UCMDB Data in HP APM" on page 21 "Default Entity and Field Mappings between HP APM and UCMDB" on page 22 "REST APIs Called in the Integration" on page 27 "Customize the Integration" on page 28 "Troubleshooting and Limitations" on page 33

l

l

l

l

l

l

Overview
The integration between HP APM and HP Universal CMDB (UCMDB) enables you to share information from UCDMB with HP APM. You can use the integration to automate the creation and update of applications in HP APM, freeing you from repetitive and manual input of information in HP APM. This also ensures that HP APM is kept up to date with real, accurate, discovered data in your environment. The following table provides an overview of the HP APM integration with UCMDB: Integration direction Integration technology Pushed data From UCMDB to HP APM HP Universal CMDB generic database adapter CIs created in UCMDB are pushed to HP APM to create requests in HP APM HP APM Push Adapter (APMPushAdapter)

HP Universal CMDB adapter

How Data is Synchronized Between HP APM and UCMDB
When referring to the concept of data information, it is important to distinguish between a UCMDB CI (Configuration Item) and an HP APM Application. Both are defined in a different Data Model, and there must be a conversion before transferring CIs in UCMDB to Applications in HP APM. The following graphic shows the high-level components of the integration:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 9 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

Note: The Push Adapter is executed in the Data Flow Probe/Integration Service process. UCMDB stores its information using CIs. The integration chooses which data to pull from UCMDB by defining integration TQL queries. Each TQL query defines a superset of data relevant for the integration. The UCMDB Push Engine: l Retrieves the required data from the UCMDB, using the given TQL query. Filters the data to include only the data that has changed since the last execution of this synchronization. Splits the data into multiple chunks without breaking consistency. Sends the information to the Probe/Adapter.

l

l

l

The Push Adapter is a generic framework for easily configuring push adapters, using only XML and Groovy. It allows easy mapping of the data from the UCMDB data model into the HP APM data model, and the transfer of this converted data into the HP APM database through REST APIs called from HP APM. For more information about push adapter, see Developing Push Adapters in the HP Universal CMDB Developer Reference Guide. For details about REST APIs that this integration call from HP APM, see "REST APIs Called in the Integration" on page 27. For entity mappings and field mappings between HP APM and UCMDB, see "Default Entity and Field Mappings between HP APM and UCMDB" on page 22.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 10 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

Supported Versions
The HP APM adapter supports the following: l Universal CMDB version 10.00 and later HP Project and Portfolio Management Center (PPM Center) version 9.22 (and later) where HP APM for PPM 9.20 is installed

l

How to Integrate UCMDB and HP APM
To set up integration between UCMDB and HP APM, you must complete the following steps: l "Deploy the APM Push Adapter" below "Create an Integration Point between HP APM and UCMDB" on the next page "Adapter" on page 16 "Push CI Data from UCMDB to HP APM" on page 16 "Schedule Data Push Jobs" on page 20

l

l

l

l

Deploy the APM Push Adapter
To integrate HP APM with UCMDB, administrators must deploy the APM Push Adapter. To do so, 1. Start the UCMDB server. 2. Open a browser and log on to UCMDB as an administrator. 3. From the left navigation bar, click the Administration tab. 4. Click Package Manager. 5. Click Deploy packages to server (from local disk) The Deploy Packages to Server dialog opens. 6. Click Add . .

7. Browse to the folder where APMPushAdapter.zip is located. Select the zip file, and click Open. 8. Click Deploy.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 11 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

9. Click OK when the following confirmation message displays: Resources were deployed successfully. 10. Verify that the package has been deployed successfully. a. From the list of deployed packages, right click APMPushAdapter. b. Select View package resources. c. Check that the resources as shown in the screenshot below display.

Create an Integration Point between HP APM and UCMDB
1. Log in to UCMDB as an administrator. 2. Navigate to Data Flow Management > Integration Studio. UCMDB displays a list of existing integration points. 3. Click the

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 12 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

button. The New Integration Point dialog box is displayed. 4. Complete the Integration Properties and Adapter Properties fields as shown in the following table: Field (*Required)

Description

Integration Properties section *Integration Name Integration Description *Adapter Type the name (unique key) of the integration point.

Type a description of the current integration point.

HP Software Products > APM > APM Push Adapter from the Select Adapter dialog Select this option to indicate the integration point is active.

Click the

button and select

*Is Integration Activated?

Adapter Properties section *Protocol Type Select http or https from the drop-down list

*Hostname/IP Type the hostname or IP Address of the PPM Server. For example, 16.166.16.16 or hostname. *Port Type the communication port of the PPM Server. The default value is 80. Example: 30000 Type the path of the PPM Server. The default value is itg.

*Path

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 13 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

Field (*Required) *Credentials ID

Description button, and from the Credentials list, select a credential or Click the create a new credential that is to be used by UCMDB to access HP APM. To create a credential for this integration point, a. Click the b. Click the button. The Choose Credentials dialog opens. button. The Generic Protocol Parameters dialog opens.

c. Provide values for the following fields and click OK: o o o

Network Scope: Use the default value ALL. User Label: Type a label for the credential. User Name: Provide the user name for the HP APM account that is to be used by UCMDB to access HP APM. Password: Click and provide the password for the HP APM account that is to be used by UCMDB to access HP APM.

o

d. Click OK twice. *Data Flow Probe The name of the Data Flow Probe/Integration service used to execute the synchronization from. Select IntegrationService for this integration. Additional Probes Not required for this integration point.

Below is an example of the completed dialog:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 14 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

5. Click Test Connection to make sure there is a valid connection. 6. Click OK. The integration point is created and its detailed are displayed (It’s not saved to the server until you click on the Save button).

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 15 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

UCMDB creates a default data push job when creating the integration point. If needed you may create or edit the existing job. For more information, see Work with Data Push Jobs in the HP Universal CMDB Data Flow Management Guide. 7. Save the integration point.

Adapter
This integration job uses the adapter called APMAdapter.

Input CI Type destination_config Triggered CI Data
Name adapterId attributeValues credentialsId destinationId Value ${ADAPTER.adapter_id} ${SOURCE.attribute_values} ${SOURCE.credentials_id} ${SOURCE.destination_id}

Adapter Parameters
Name credentialsId domain host port probeName protocalType http 80 itg Value

Push CI Data from UCMDB to HP APM
Data push jobs copy or update CI or CI relationship records from the local UCMDB system to your HP APM system. To run a data push job, complete the following steps:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 16 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

1. Log in to UCMDB as an administrator. 2. Navigate to Data Flow Management > Integration Studio. UCMDB displays a list of existing integration points. 3. Select the integration point you created for HP APM. 4. Select the default data push job APM Push. Or, if the default data push job does not satisfy your needs, you may add a new data push job as follows: a. Click the button on the right panel.

b. In the Name field, type a unique name for the job. c. Click the button to add existing TQL queries to the job.

UCMDB creates a default data push job when creating the integration point for HP APM. The following table lists the Topology Query Language (TQL) queries in the default data push job. If required, you may create, update, or remove TQL queries for the push job. You may also need to update the mapping. See . Note: To access these OOTB TQL queries for push, navigate to Modelling > Modeling Studio > Resources, select Queries from the drop-down list for the Resource Type field and then navigate to Root > Integration > APM Push. TQL Query APM Location Push Description Pushes Location CIs. Mapping XML: pushMappingAPMLocation.xml APM Process Push Pushes BusinessProcess CIs. Mapping XML: pushMappingAPMProcess.xml APM Process Relation Clear Push Clears old relations between processes in HP APM. This TQL query synchronization must have been run BEFORE the 'APM Process Relation Push' TQL query synchronization. Mapping XML: pushMappingAPMProcessRClear.xml

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 17 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

TQL Query APM Process Relation Push

Description Pushes relations between Processes (pushed by APM Process Push) to other business elements or to processes. BusinessProcess CIs must have been pushed before this TQL query synchronization in the ‘APM Process Push’ TQL query synchronization. Mapping XML: pushMappingAPMProcessR.xml

APM Server Push

Pushes Node CIs (Computers, Network Devices, etc.). Mapping XML: pushMappingAPMServer.xml

APM Server Relation Clear Push

Clears old relations between Servers in HP APM. This TQL query synchronization must have been run BEFORE the 'APM Server Relation Push' TQL query synchronization. Mapping XML: pushMappingAPMServerRClear.xml

APM Server Relation Push

Pushes relations between Servers (pushed by APM Server Push) to other servers. Node CIs must have been pushed before this TQL query synchronization in the ‘APM Server Push’ TQL query synchronization. Mapping XML: pushMappingAPMServerR.xml

APM Application Push

Pushes BusinessApplication CIs. Location, BusinessProcess, and/or Node CIs must have been pushed before this TQL query synchronization. Mapping XML: pushMappingAPMApplication.xml

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 18 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

TQL Query APM Application Relation Clear Push

Description Clears old relations (except for the downstream relations) between Applications in HP APM. This TQL query synchronization must have been run BEFORE the 'APM Application Relation Push' TQL query synchronization. Mapping XML: pushMappingAPMApplicationRClear.xml

APM Application Relation Push

Pushes relations (except for the downstream relations) between Applications (pushed by APM Application Push) to other business elements or to nodes. BusinessApplication CIs must have been pushed before this TQL query synchronization in the ‘APM Application Push’ TQL query synchronization. Mapping XML: pushMappingAPMApplicationR.xml

APM Application Relation Clear Down Push

Clears old downstream relations between Applications in HP APM. This TQL query synchronization must have been run BEFORE the 'APM Application Relation Down Push' TQL query synchronization. Mapping XML: pushMappingAPMApplicationDownRClear.xml

APM Application Relation Down Push

Pushes downstream relations between Applications (pushed by APM Application Push) to other business elements or to nodes. BusinessApplication CIs must have been pushed before this TQL query synchronization in the ‘APM Application Push’ TQL query synchronization. Mapping XML: pushMappingAPMApplicationDownR.xml

d. Select the Allow Deletion option for each query. This allows deletion of synchronized data in HP APM when data in UCMDB are deleted. Otherwise requests created in HP APM as a result of synchronization remain even when their original data in UCMDB are deleted.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 19 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

Note: For scheduling configuration, see "Schedule Data Push Jobs" below. e. Click OK. f. Save the integration point. 5. Run the job manually to see if the integration job works properly: a. To push all the relevant data for the job, click the button. button.

b. To push only the changes in the data since the job last executed, click the 6. Wait for the job to complete; click the completed.

button multiple times as needed until the job is

7. When the job is completed, the job status becomes one of the following depending on the results: n Succeeded Passed with failures Failed

n

n

8. Click the Statistics tab to view the results; if any errors occur, click the Query Status tab and Job Errors tab for more information. For more information about errors, see "Troubleshooting and Limitations" on page 33.

Schedule Data Push Jobs
UCMDB allows you to schedule job executions directly from a data push job. 1. Log in to UCMDB as an administrator. 2. Navigate to Data Flow Management > Integration Studio. UCMDB displays a list of existing integration points. 3. Select the integration point you created for the APM - UCMDB integration. 4. Select the APM Push job. 5. Click the button.

The Edit Integration Job dialog opens.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 20 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

Note: UCMDB allows you to define two different schedules for two types of data push: Changes Synchronization and All Data Synchronization. It is recommended to use the Changes Sync schedule to only synchronize changes and avoid synchronizing the entire set of data each time. 6. Define a schedule for Changes Synchronization. a. Click on the Changes Synchronization tab. b. Select the Scheduler enabled option. c. Select the scheduling options you want to use. 7. Click the All Data Synchronization tab and select the scheduling options you want to use. 8. Click OK. 9. Save the integration point.

View UCMDB Data in HP APM
After a push job is successfully completed, you can search for and verify that the pushed CI/relationship data is in HP APM. To view UCMDB data in HP APM, 1. Log on to PPM Center. 2. On the Open menu, click Application Portfolio > Search Entities. The Search Entities page opens. 3. In the Entities section, click one of the following entities: n Application Location Process Server

n

n

n

The Search: APM - page opens. In this example, click Application and the Search: APM - Application page opens. 4. Click Search.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 21 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

The Search Results page displays request search results. 5. Click any Application No to view an APM - request.

Default Entity and Field Mappings between HP APM and UCMDB
The following sections describe out of the box mappings that are available with the APM Push Adapter for integration with HP APM and UCMDB. The following table provides an overview of type mappings between HP APM entities and UCMDB CI Types: HP APM Entity Application PPM Center Request Type APM Application

UCMDB CI Type BusinessApplication

Remarks For detailed mappings, see "Default Field Mappings between HP APM Application and UCMDB BusinessApplication" below. For detailed mappings, see "Default Field Mappings between HP APM Process and UCMDB BusinessProcess" on page 24. For detailed field mappings, see "Default Field Mappings between HP APM Location and UCMDB Location" on page 25. For detailed field mappings, see "Default Field Mappings between HP APM Server and UCMDB Node" on page 26.

Process

APM - Process

BusinessProcess

Location

APM - Location

Location

Server

APM - Server

Node

Default Field Mappings between HP APM Application and UCMDB BusinessApplication
The following table describes the default field mappings that can be modified for the integration between the HP APM entity of Application and the UCMDB CI Type of BusinessApplication.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 22 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

HP APM Field Name and Field Type Name KNTA_PROJECT_NAME Text Field - 300 Updated By a Create On b CREATION_DATE Date Purpose APM_APP_PURPOSE Text Field - 4000 Business Criticality c APM_RATING_BUSINESS_CRIT Drop Down List Created Bya CREATED_BY Auto Complete List Supported Processes APM_SUPPORTED_PROCESSES Auto Complete List Downstream Applications APM_DOWNSTREAM_APPS Auto Complete List

UCMDB CI Attribute and Field Type Name name string (N/A) (N/A)

Description description string BusinessCriticality business_criticality integer (N/A)

Name (of CI Type BusinessProcess) name (of CI Type BusinessProcess) string Name (of downstream CI Type BusinessApplication) name (of downstream CI Type BusinessApplication) string Name (of upstream CI Type BusinessApplication) name (of upstream CI Type BusinessApplication) string Name (of CI Type ServiceLevelAgreement) name (of CI Type ServiceLevelAgreement) string Name (of CI Type Node) name (of CI Type Node) string Name (of CI Type Database) name (of CI Type Database) string

Upstream Applications APM_UPSTREAM_APPS Auto Complete List

Service Level Agreement APM_APP_SLA Text Field - 200 Servers APM_SERVER_LIST Auto Complete List Database APM_DATABASE_LIST Text Field - 200

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 23 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

HP APM Field Name and Field Type

UCMDB CI Attribute and Field Type

a. The HP APM account you provided when creating the integration point (see "Create an Integration Point between HP APM and UCMDB" on page 12). b. Time when the request is created for the first time in HP APM. c. The following mapping rule is used for this mapping: where the definition of ‘bc’ token is defined as follows in the server.properties field: bc.0=0 bc.1=1 bc.2=2 bc.3=3 bc.4=4 bc.5=5 Least critical Slightly critical Less than average More than average Critical Highly critical

When synchronizing the Business Criticality field from UCMDB to HP APM, if the value is ‘1’ in UCMDB, then the field value will be set to ‘1 - Slightly critical’ in APM.

Default Field Mappings between HP APM Process and UCMDB BusinessProcess
The following table describes the default field mappings that can be modified for the integration between the HP APM entity of Process and the UCMDB CI Type of BusinessProcess. [[[Undefined variable PPM.yUCMDBs]]] CI Attribute, Database ID, and Field Type Name name string Name of parent BusinessProcess name of parent BusinessProcess string Description description string (N/A)

HP APM Field Name, Database ID, and Field Type Process Name DESCRIPTION Text Field - 200 Parent Process APM_PARENT Auto Complete List Description APM_DESCRIPTION Text Area - 4000 Created By a CREATED_BY Auto Complete List

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 24 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

HP APM Field Name, Database ID, and Field Type Created On b CREATION_DATE Date

[[[Undefined variable PPM.yUCMDBs]]] CI Attribute, Database ID, and Field Type (N/A)

a. The HP APM account you provided when creating the integration point (see "Create an Integration Point between HP APM and UCMDB" on page 12) b. Time when the request is created for the first time in HP APM.

Default Field Mappings between HP APM Location and UCMDB Location
The following table describes the default field mappings that can be modified for the integration between the HP APM entity of Location and the UCMDB CI Type of Location. [[[Undefined variable PPM.yUCMDBs]]] CI Attribute, Database ID, and Field Type Name name string Description description string StreetAddress+ExtendedStreetAddress street_address+extended_street_address string+string PostalCode postal_code string CountryOrArea country_or_area string Region region string

HP APM Field Name, Database ID, and Field Type Location Name DESCRIPTION Text Field - 200 Description APM_DESCRIPTION Text Field - 4000 Address APM_LOC_ADDRESS Text Field - 200 Postal Code APM_LOC_ZIPCODE Text Field - 20 Country APM_LOC_COUNTRY Text Field - 200 Region APM_LOC_REGION DDL

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 25 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

HP APM Field Name, Database ID, and Field Type Longitude APM_LONGITUDE Text Field - 40 Latitude APM_LATITUDE Text Field - 40 City APM_LATITUDE Text Field - 200 State/Province APM_STATE Text Field - 200

[[[Undefined variable PPM.yUCMDBs]]] CI Attribute, Database ID, and Field Type Longitude longitude string Latitude latitude string Citya city string Statea state string

a. The CI attribute is removed from UCMDB version 10.x, but exists in earlier versions of UCMDB. For UCMDB instances that upgraded from an earlier version to 10.x, this CI attribute exists but is readonly. If the CI attribute has a value, the value can be synchronized to HP APM, otherwise the HP APM field remains empty after you run the synchronization push job in UCMDB.

Default Field Mappings between HP APM Server and UCMDB Node
The following table describes the default field mappings that can be modified for the integration between the HP APM entity of Server and the UCMDB CI Type of Node. [[[Undefined variable PPM.yUCMDBs]]] CI Attribute Display Name, Name, and Type Name name string Description description string (value size: 1000) IP Address (of IpAddress) ip_address (of IpAddress) string

HP APM Field Name, Token, and Component Type Server Name DESCRIPTION Text Field - 200 Description APM_DESCRIPTION Text Area - 4000 IP Address APM_IP_ADDRESS Text Field, Max Length: 15

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 26 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

HP APM Field Name, Token, and Component Type OS APM_OS Drop-down List Running Software APM_RUNNING_SOFTWARE Text Area - 4000 Location APM_LOCATION Auto Complete List

[[[Undefined variable PPM.yUCMDBs]]] CI Attribute Display Name, Name, and Type OsDescription os_description string ProductName:Name (of RunningSoftware) product_name:name (of RunningSoftware) product_name_enum:string Name (of Location) name (of Location) string

REST APIs Called in the Integration
The following HP Demand Management REST APIs are called in this integration to convert data from UCMDB into HP APM compatible data: l Get a request For more information, see Get Details of a Request section of the RESTful Web Services Guide for 9.20.

l

Create a request For more information, see Create/Update a Request section of the RESTful Web Services Guide for 9.20.

l

Update a request For more information, see Create/Update a Request section of the RESTful Web Services Guide for 9.20.

l

Delete a request Added in version 9.22. For more information, see "Delete a Request" below

Delete a Request
Request: http://:/itg/rest/dm/requests/{reqId} HTTP Method: DELETE Description: Delete a request with a specific ID. To perform this operation, you must be in one or more of the authorized security groups for the create/update action. Request path variables:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 27 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

Attribute reqId

Description Request ID. Indicates which request will be deleted.

Required? Yes

Response entity body: l on success: When the operation is successfully executed, no message is returned. However, the REST API automatically calls the GET operation and returns the following message in Response Header (with empty message body):
Status Code: 204 No Content Cache-Control: no-cache Date: Mon, 26 Aug 2013 09:20:29 GMT Expires: -1 Pragma: no-cache

l

on failure: The following message codes are returned if the operation fails: Message Code PPMC_ WSE108

Message Not Found

Cause The quest is not found.

Possible Corrective Action The request ID is not passed or the request of this ID doesn’t exist. N/A

PPMC_ WSE001

Internal Server Error

There was an error when you tried to delete a request. There was an error when you tried to delete a request.

PPMC_ WSE116

Internal Server Error

N/A

Limitation: This operation supports field security check, but it ignores user interface (UI) rules or status dependency. Such constraints have to be validated and enforced on the client side before this operation is invoked.

Customize the Integration
This section includes: l "Overview" on the next page "Customize an Existing Mapping" on the next page "Add a New Mapping to the Integration" on page 30

l

l

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 28 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

Overview
This section contains details about the architecture of the integration.

Data Flow Architecture
1. The Push Engine executes the TQL query. 2. For a differential flow, the data is compared to the last synchronized data, and only the changes are forwarded. 3. Data is converted into Composite CIs (instances of data according to the TQL Root elements). 4. Data is then pushed to the Push Adapter. 5. The Push Adapter loads the correct mapping for the specific TQL query. 6. All dynamic_mappings are executed and saved to maps, to allow usage in the next mapping stage. For more information, see Developing Push Adapters in the HP Universal CMDB Developer Reference Guide. 7. Data is sent to HP APM database via REST APIs from HP APM, where REST APIs converts data to HP APM compatible data.

Integration TQL Queries
A TQL query used for the integration must contain a root query node. Any attribute using in the mapping flow of the Push Adapter must be marked in the selected layout of the query node. Each TQL query may only have one mapping. For more information, see Data Flow Management > Integration > Integration Studio > Integration Studio User Interface > Integration Jobs Pane.

Customize an Existing Mapping
This example shows you how to add the NAME attribute to the integration including the TQL query and Push Adapter Mapping. It allows the integration to both push the NAME attribute to Location in HP APM. After completing the following steps, you may run the job with the customized mapping:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 29 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

1. Add the NAME attribute to the APM Location Push TQL query layout. In this step we add the NAME attribute of the Location to the integration TQL query so that we can use the attribute and value in the mapping. a. Navigate to Modeling > Modeling Studio > Resources and select the Queries Resource Type. b. Navigate to Query: Root > Integration > APM Push > APM Location Push. c. Select Root, right-click and select Query Node Properties. d. Go to the Element Layout tab. e. Move the Name to the Specific Attributes box. f. Click OK. g. Save the Query. 2. Add the NAME Mapping to the pushMappingAPMLocation.xml push adapter mapping. In this step we take the value from the TQL result and remodel it to the HP APM Data Model. a. Navigate to Data Flow Management > Adapter Management > Packages > APMPushAdapter > Configuration Files > pushMapingAPMLocation.xml. b. Navigate to the XML tag. c. Below the tag, add the following XML tag to hold the value of the Description:

where, "REQ.DESCRIPTION" is the request Name field token of Location. d. Click OK.

Add a New Mapping to the Integration
This example shows how to add a new TQL query and push-mapping to the integration. It also shows how to push Locations from UCMDB to HP APM. It consists of the following steps:

Step 1: Create a TQL Query
1. Navigate to Modeling > Modeling Studio > New > Query. 2. From the CI Types tab, add a Location to the query. 3. Right-click the Location Query Node and select Query Node Properties.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 30 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

4. Rename the Element Name to Root. 5. Navigate to the Element Layout tab. 6. Select Select attributes for layout. 7. In the Attributes condition drop down, select Specific Attributes, and add the Name attribute 8. Click OK. 9. Save the query to Root > Integration > APM Push > APM Location Push.

Step 2: Create a Push-Mapping
1. Navigate to Data Flow Management > Adapter Management > APMPushAdapter. 2. Click the button and select New Configuration File.

3. Type the following Name: APMPushAdapter/mappings/pushMappingAPMLocation.xml. 4. Select the APMPushAdapter package. 5. Click OK. 6. Copy the following into the newly created XML file:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 31 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

Integration Studio. 2. Create an Integration Point with HP APM. 3. In the Integration Jobs tab, click the 4. Insert a job name in the Name field. 5. Click the 6. Click OK. button, and choose the APM Location Push query. button .

Step 4: Run the Job
1. Click on the job created in "Step 3: Create a Job with the New TQL Query" above. 2. Click the button. button to see progress.

3. Wait for the job to finish. You should click the 4. Make sure that the status is Succeeded.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 32 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

Step 6: View the Results
1. Log on to . 2. On the Open menu, n Click Application Portfolio > Search Entities, then in the Entities section, click Location. Or, Click Search > Requests, then from the Request Type drop-down list, select APM Location.

n

3. Click Search. The Search Results page displays request search results.

Troubleshooting and Limitations
This section includes the following: l "Limitations" below "Troubleshooting Problems" on the next page "Logs" on page 35

l

l

Limitations l The Data Flow Probe or Integration Service must be installed on a Windows OS. For requests created in HP APM from CIs pushed from UCMDB, any changes made in HP APM are overwritten when you run the data push job in UCMDB. The APM Application request form holds a single value for Location, therefore it is designed to push only one value for Location of Application from the UCMDB BusinessApplication. In the definition of Location to Application (see the pushMappingAPMApplicationR.xml file), the Location to Server of Application is used. For an Application that contains multiple servers, select one of the servers and then you can get its Location.

l

l

l

For value mappings between UCMDB and HP APM, certain mapping rules are followed. For example, when synchronizing the Business Criticality field of Application, the following mapping rule is used for the mapping:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 33 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

where the definition of ‘bc’ token is defined as follows in the /mappings/scripts/server.properties file: bc.0=0 bc.1=1 bc.2=2 bc.3=3 bc.4=4 bc.5=5 Least critical Slightly critical Less than average More than average Critical Highly critical

When synchronizing the Business Criticality field from UCMDB to HP APM, if the value is ‘1’ in UCMDB, then the field value will be set to ‘1 - Slightly critical’ in APM. If you need to use this value mapping for other fields from UCMDB to APM, make sure you customize the mapping by following the example above. l This integration does not support synchronizing values in languages that are not supported by UCMDB. For example, Simplified Chinese.

Troubleshooting Problems l Problem: Some UCMDB CIs include characters that are not supported in APM Entities. Solution: The suggested solution is to modify the content synchronized from UCMDB to APM. You can use the Replace function to replace the unsupported characters for this field mapping in the XML mapping file. However, note that this may cause inconsistent content between UCMDB and APM. An example, in the pushMappingAPMApplication.xml file,

l

Problem: For some fields, the field value lengths between HP APM and UCMDB are different, therefore you may need to customize the field mapping. You can follow the example below: Example Use a substring as illustrated below to limit the field length to 200 characters:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 34 of 191

Universal Discovery Content Guide - HP Integrations Chapter 1: HP APM Push Integration

Logs
The push adapter framework uses a different logs then the normal fcmdb.adapters.*.log files. To change the level of the log files to debug, edit the following file: l On the Data Flow Probe machine:
..\DataFlowProbe\conf\log\fcmdb.push.properties

l

If using the integration service, on the UCMDB server:
..\UCMDB Server\Integrations\conf\log\fcmdb.push.properties

Change the log level to DEBUG: loglevel=DEBUG The integration generates fcmdb.push.* logs in the following folder: l On the Data Flow Probe machine:
..\DataFlowProbe\runtime\log\

l

If using the integration service, on the UCMDB server:
..\UCMDB Server\Integrations\runtime\log\

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 35 of 191

Chapter 2: HP Asset Manager Integration
This chapter includes: Overview Supported Versions How to Integrate Asset Manager with UCMDB Adapter Troubleshooting and Limitations 37 37 37 40 40

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 36 of 191

Universal Discovery Content Guide - HP Integrations Chapter 2: HP Asset Manager Integration

Overview
HP Asset Manager is an asset lifecycle management solution with modular components allowing an IT organization to measure and communicate the value it provides to the business it supports. UCMDB-Asset Manager integration is implemented by the Asset Manager adapter (AMAdapter) pulling CIs and relationships from Asset Manager to UCMDB. This chapter covers the use of the Asset Manager 9.02 adapter and the Asset Manager 9.02 Update 1 adapter. For information about the Asset Manager Population and Federation adapter 9.30, see "Populating HP Universal CMDB from HP Asset Manager" in the HP Service Asset and Configuration Management (SACM ) Solution Configuration Guide Version 9.30 . If you have an HP Passport, you can access this document from the HP Software Product Manuals web site (http://support.openview.hp.com/selfsolve/manuals), selecting your product - Universal CMDB (Application Mapping) - version number, and operating system, and searching. To register for an HP passport, go to http://h20229.www2.hp.com/passport-registration.html, or click the New users - please register link on the HP Passport login page.

Supported Versions
The Asset Manager adapter supports Asset Manager Versions 5.22 and later.

How to Integrate Asset Manager with UCMDB
This documentation covers the use of the Asset Manager 9.02 adapter, and the Asset Manager 9.02 Update 1 adapter. There is an HP SACM Solution Configuration Guide available for each. You can access this document from HP Live Network (https://hpln.hp.com/) by searching for "HP Solution Content for Asset Manager". This task consists of the following steps: 1. Prerequisites - Deploying the Asset Manager package Ensure the following steps are completed as detailed in "Integrating Asset Manager with HP Universal CMDB" in the HP SACM Solution Configuration Guide. a. Create the Asset Manager SQL views b. Deploying the Asset Manager integration package to HP Universal CMDB c. Making some CI attributes visible

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 37 of 191

Universal Discovery Content Guide - HP Integrations Chapter 2: HP Asset Manager Integration

d. Mapping the location types in Asset Manager and HP Universal CMDB e. Only relevant for the Asset Manager 9.02 adapter: Adding the asset_tag attribute 2. Create the integration point In DFM, in the Integration Studio, create a new integration point. a. Provide a name and description for the integration point. b. Ensure the Is Integration Activated option is enabled. c. Under Integration Properties > Adapter, select HP Software Products > Asset Manager >: Asset Manager Adapter 9.02 Update 1 for SACM 9.02 Update 1 Asset Manager Adapter for SACM 9.02 or earlier d. Under Adapter Properties: Field Hostname\IP Value \ Type the port to access the Asset Manager database. See Create credentials, below. Type the database identifier used by Asset Manager. Select the database type. For example: SQL Server. Select an appropriate probe. Leave empty.

Port Credentials ID DB Name/SID DB Type Data Flow Probe Additional Probes e. Create credentials

i. Click the ellipsis to the right of the Credentials ID property. ii. Select the Generic DB Protocol (SQL) protocol in the left pane. iii. Click the Create new connection details for selected protocol type button.

iv. Populate the fields on the SQL Protocol Parameters page, General section, as follows:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 38 of 191

Universal Discovery Content Guide - HP Integrations Chapter 2: HP Asset Manager Integration

Field Network Scope User Label

Value Use the default value. Type a label for the credential.

v. Populate the fields on the SQL Protocol Parameters page, SQL section, as follows: Field Database Type Port Number Connection Timeout User Name Password Instance Name Encryption Method Trust Store File Path Value Select the DBMS type. The port to access the database. The time in milliseconds after which the probe stops trying to connect to the database. The name of the user used to connect to the database. The password of the user needed to connect to the database. For Oracle, enter the name of the instance. Choose None or SSL. For Oracle, choose None. Enter the full path to the SSL trust store file. Note: only available if you have chosen an encryption method. Trust Store Password The SSL trust store password. Note: only available if you have chosen an encryption method.

Note: For details about integration points and credentials, see the HP Universal CMDB Data Flow Management Guide. f. Click Test Connection to verify the connection is successfully established. g. Click OK. h. Save the integration point. 3. Run the appropriate integration data flow: n Population

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 39 of 191

Universal Discovery Content Guide - HP Integrations Chapter 2: HP Asset Manager Integration

n

Federation Note: For details on running these, see "Integrating Asset Manager with HP Universal CMDB" in the HP SACM Solution Configuration Guide.

Adapter
This section contains details about the adapter called AMAdapter which the job uses.

Input CIT destination_config Triggered CI Data
Name adapterId attributeValues credentialsId destinationId Value ${ADAPTER.adapter_id} ${SOURCE.attribute_values} ${SOURCE.credentials_id} ${SOURCE.destination_id}

Parameters
Name dbname dbtype port Value AssetManager SQLServer 1433

Troubleshooting and Limitations
When running a diff population job, ensure amComputer.dtLastModif for related CIs is updated. For more information, see the HP SACM Solution Configuration Guide.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 40 of 191

Chapter 3: HP Asset Manager Push Integration
This chapter includes: Quick Start Overview Supported Versions How to Integrate UCMDB and Asset Manager Validate Pre-Loaded Data in Asset Manager Set Up Asset Manager Set Up UCMDB Push CI Data from UCMDB to Asset Manager How to View UCMDB Data in Asset Manager Nodes Business Elements How to Schedule Data Push Jobs Installed Software How to Tailor the Integration Integration Architecture How to Change Adapter Settings How to Customize an Existing Mapping How to Add a New Mapping to the Integration Frequently Asked Questions Troubleshooting and Limitations Logs 42 42 43 44 44 44 48 52 56 57 57 57 59 61 62 71 72 73 77 79 84

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 41 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Quick Start
Note: This section is only for advanced users who want to start using Asset Manager Push Integration quickly, without reading the full documentation. It therefore provides the minimum information required before you run your first integration. Before starting the integration for the first time, you must complete the following: l "Validate Pre-Loaded Data in Asset Manager" on page 44 "Update Asset Manager Schema" on page 46 "Create AMPushAdapterAPI Package with Required AM API Files" on page 48 "Install a Database Client" on page 49

l

l

l

Overview
Integration between HP Universal CMDB (UCMDB) and HP Asset Manager enables you to share information from UCMDB with Asset Manager. Common use cases include Hardware, Installed Software and Business Services. You can use the integration to automate the creation and update of Asset and Portfolio information in Asset Manager. This ensures Asset Manager is kept up to date with real, accurate, discovered data in your environment. Note: This Integration replaces the Connect-It Scenarios used for syncing Hardware and Software information from DDMI 9.3x and below to Asset Manager. Also, this integration replaces the Connect-It Scenarios used to sync Business Services and Business Applications from UCMDB to Asset Manager.

How Data is Synchronized Between UCMDB and Asset Manager
When referring to the concept of data information, it is important to distinguish between a UCMDB CI (Configuration Item) and an Asset Manager Asset. Both are defined in a different Data Model, and there must be a conversion before transferring CIs in UCMDB to Assets in Asset Manager. The following graphic shows the high-level components of the integration:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 42 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Note: The Push Adapter and AM Connector are executed in the Data Flow Probe/Integration Service process. UCMDB stores its information using CIs. The integration chooses which data to pull from UCMDB by defining integration TQL queries. Each TQL query defines a superset of data relevant for the integration. The UCMDB Push Engine: l Retrieves the required data from the UCMDB, using the given TQL query. Filters the data to include only the data that has changed since the last execution of this synchronization. Splits the data into multiple chunks without breaking consistency. Sends the information to the Probe/Adapter

l

l

l

The Push Adapter is a generic framework for easily configuring push adapters, using only XML and Groovy1. It allows easy mapping of the data from the UCMDB data model into the Asset Manager Data model, and the transfer of this converted data into the AM Connector. For more information, see Developing Push Adapters in the HP Universal CMDB Developer Reference Guide. The AM Connector is a component that connects to the Push Adapter, built specifically to reconcile, push, and handle the complex logic needed to synchronize data into Asset Manager.

Supported Versions
This integration supports HP Asset Manager versions 5.20, 5.21, 5.22, 9.30, 9.31 and later.

1Groovy is an agile and dynamic language, natively supported by the Java Virtual Machine. It

allows simple scripting capabilities, while maintaining all the strengths and capabilities of Java. It can execute simple String manipulation, and use 3rd party libraries. For more information, see http://groovy.codehaus.org/

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 43 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

How to Integrate UCMDB and Asset Manager
To set up integration between UCMDB and Asset Manager, you must complete the following steps: l "Validate Pre-Loaded Data in Asset Manager" below "Set Up Asset Manager" below "Set Up UCMDB" on page 48 "Push CI Data from UCMDB to Asset Manager" on page 52

l

l

l

Validate Pre-Loaded Data in Asset Manager
For the integration to succeed, it requires there to be some basic data already in the Asset Manager database. This data may either be imported during the database creation (using the Asset Manager Application Designer), or may be added later. For more information, see the Asset Manager Documentation – Administration. For hardware synchronization the required data is: l Shared Data UNSPSC Product Classification Portfolio – Line-of-business data Virtualization – Line-of-business data Business services management – Line-of-business data

l

l

l

l

For software synchronization the required data is: l Software Asset Management – Line-of-business data

Set Up Asset Manager
To set up Asset Manager you must complete the following steps:

Create an Account with Administrative Rights
For the integration, any user with administrative rights will suffice. Asset Manager OOTB installations include an administrator account. The details of the default Administrator user are:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 44 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

l

User: Admin Password:

l

The following example shows how to create a new user (named Integration-Admin) with administration rights, specifically for the integration. 1. Log in to Asset Manager as Administrator 2. Go to Organization Management > User actions > Add a user. a. In ID #, type: Integration-Admin. b. In Name, type: Integration-Admin. c. In First, type: Integration-Admin. d. Click Next. e. Click Next. f. Click Finish. 3. Go to Organization Management > Organization > Employees. 4. Select the newly created User and go to the Profile tab. 5. In User name, type: Integration-Admin. 6. In Password, type: . 7. In the Password Administration pane, ensure Never Expires is selected. 8. In the Profile pane, ensure Administration rights is selected. 9. Click Modify.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 45 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Update Asset Manager Schema
The default Asset Manager database schema includes column lengths that may be significantly shorter than their counterparts in the UCMDB database schema. For attributes used for reconciliation, this may be critical and may cause creation of multiple records. To fix this issue, you are recommended to change the Asset Manager Column Sizes to the values shown in the following table of Asset Manager Attributes. Default Max Length 40 40 128 36 80 30 128 26 128 64 100 100 New Value 255 250 250 250 250 100 255 255 255 250 200 200 New Value as of AM 9.31[*] 255 250 250 250 250 100 255 255 255 250 200 200 500 500 500

Table amComputer amComputer amPortfolio amAsset amModel amCompany amSoftInstall amSoftInstall amSoftInstall amBrand amEmplDept amEmplDept amBrand amComputer amModel

Name TcpIpHostName WorkGroup Folder SerialNo Name Name Folder Field1 TechnicalInfo Name UserName UserDomain FullName FullName FullName

[*] Also available in Asset Manager versions 5.22 and 9.3 with an appropriate hotfix for column length limit. Note: l The new values in the table are only a suggestion, and you may need to change them according to actual data per customer use case. DB2 default table space page size of 4K may be too small in some cases; using 8K or higher is recommended.

l

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 46 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Prepare Asset Manager for Parallel Push
Enabling Parallel Push significantly increases the performance of the push. However, some advance preparation is necessary. Different actions are needed for different database types, as shown in the following table: Database Action DB2 Mandatory: follow Eliminating locks and deadlocks in the Asset Manager Tuning Guide. Limitation: DB2 parallel push is not supported in UCMDB 10.01. Oracle Optional: follow Eliminating locks and deadlocks in the Asset Manager Tuning Guide. The following are all mandatory steps: 1. Alter the SQLServer Schema isolation level: Execute the following command on the database, replacing with the real schema name:
ALTER DATABASE SET READ_COMMITTED_SNAPSHOT ON ALTER DATABASE SET ALLOW_SNAPSHOT_ISOLATION ON GO

SQL Server

Note: If the execution takes too long, you may need to disconnect all connections to the database. One possible way is to restart the database service, then execute the command. If you restart the SQL Server, and an Integration Point has already been created in the UCMDB, you should restart the UCMDB Probe as well to avoid the issue of dead connections. 2. Alter Asset Manager database options: a. Open the Asset Manager Client and connect to the appropriate database schema b. Navigate on the top menus to Administration > Database options c. For option ‘Sql Server specifics’|‘Isolation command before starting a write transaction’change the current value to set transaction isolation level snapshot 3. Follow Eliminating locks and deadlocks in the Asset Manager Tuning Guide.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 47 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Set Up UCMDB
To set up UCMDB you must complete the following steps:

Create AMPushAdapterAPI Package with Required AM API Files
Note: If you want to create several integrations to different versions of Asset Manager, follow this procedure for each version of Asset Manager you want to integrate to. Otherwise, see "Integrating to a Single Version of Asset Manager" below. In order for the adapter to connect to the appropriate Asset Manager version, you must supply the Data Flow Probe/Integration Service with the appropriate Asset Manager API DLLs and Jars, as follows: 1. Copy the files below: n \x64\*.dll \websvc\lib\*.jar

n

2. Create a package called AMPushAdapterAPI_.zip. For example, for version 9.3 the package is AMPushAdapterAPI_9.3.zip. 3. Paste the copied files to: \discoveryResources\AMPushAdapter\amVersion\ For example, for version 9.3 the path is: AMPushAdapterAPI_9.3.zip\discoveryResources\AMPushAdapter\amVersion\9.3 4. Add the subfolder AMPushAdapter/amVersion//*.* to the additionalClasspath property in the globalSettings.xml file. 5. Deploy the AMPushAdapterAPI_.zip package.

Integrating to a Single Version of Asset Manager
If you want to create an integration to only a single version of Asset Manager, take the following steps instead: 1. Copy these files \x64\*.dll \websvc\lib\*.jar

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 48 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

2. Paste the copied files to the Data Flow Probe\Integration service\lib directory. 3. Restart the probe.

Install a Database Client
You must install database client software according to the type of database the Asset Manager schema is installed on, as detailed in the following table: Database Client Software DB2 1. Download and Install “IBM Data Server Client” 64 bit for windows on your Data Flow Probe/Integration Service computer. This may be downloaded from: http://www-01.ibm.com/support/docview.wss?rs=4020&uid=swg21385217 2. Create a connection to the DB2 database of Asset Manager. You may create this using the DB2 Control Center. Note: Remember the Database Alias you define in the connection, because you need it when creating the integration point. 3. Copy the db2cli64.dll file from the DB2 client bin directory (By default: C:\Program Files\IBM\SQLLIB\BIN) to the \lib folder. 4. Restart the Data Flow Probe/Integration Service.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 49 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Database Client Software Oracle There are two installation options: 1. Oracle client windows 64 bit For example: Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft Windows (x64). a. Download the client installation from: http://www.oracle.com/technetwork/database/enterpriseedition/downloads/index.html b. Install the client, in Administrator mode, on the Data Flow Probe/Integration Service computer. c. Copy oci.dll from the into: \lib. d. Restart the Data Flow Probe/Integration Service. 2. Basic Instant Client for Microsoft Windows (x64) a. Download the instant client zip file from: http://www.oracle.com/technetwork/database/features/instantclient/index.html b. Unzip the packages on the Data Flow Probe/Integration Service computer, into a single directory; for example: instantclient. c. Open \bin\WrapperGateway and add to the wrapper.java.library.path section an additional line (with unused index) which adds the directory that contains the client oci.dll. For example: wrapper.java.library.path.5=C:\instantclient d. Restart the Data Flow Probe/Integration Service. SQL Server None required.

Create an Integration Point in UCMDB
1. Log in to UCMDB as an administrator. 2. Go to Data Flow Management > Integration Studio. UCMDB displays a list of existing

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 50 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

integration points. 3. Click the button. The New Integration Point dialog box is displayed.

4. Complete the Integration and Adapter Properties fields as shown in the following table: Field Integration Name Integration Description Adapter Required Description Yes Type the name (unique key) of the integration point.

No

Type a description of the current integration point.

Yes

Select HP Software Products > Asset Manager > Asset Manager Push Adapter Select this option to indicate the integration point is active.

Is Integration Activated? Hostname/IP

Yes

Yes

Type the hostname or IP Address of the Asset Manager database. Select the database type your Asset Manager schema is located on. Type the communication port of the Asset Manager Data Base. n DB Type

Yes

DB Port

Yes

DB Name/SID

Yes

DB2: type in the name of the Database Alias you defined in the database connection. Oracle: type the name of the SID. SQL Server: type the name of the schema.

n

n

Credentials ID

Yes

Select Asset Manager Protocol. To create a new protocol, button. Under Asset Manager Protocol click the complete: n Asset Manager User Name: An AM administrator's user name. Asset Manager Password: An AM administrator's password. DB User Name: The AM database user's name. DB Password: The AM database user's password.

n

n

n

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 51 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Field AM Version

Required Description Yes Select the version of Asset Manager this integration point is to connect to. Select to allow parallel (multi-threaded) data push to Asset Manager. This improves performance. Note that you must configure SQL Server & DB2 to support parallel push. See "Prepare Asset Manager for Parallel Push". Select the name of the Data Flow Probe/Integration service used to execute the synchronization from. Select additional probes to use when pushing to AM in order to increase redundancy. Not required for this integration point. Note: This field only appears in a Multi-Tenant Enabled UCMDB.

Enable Parallel Push

Yes

Data Flow Probe Additional Probes Default owner name

Yes

No

No

5. Click Test Connection to make sure there is a valid connection. 6. Click OK. The integration point is created and its detailed are displayed. UCMDB creates a default data push job when creating the integration point. If needed you may create or edit the existing job. For more information, see "Work with Data Push Jobs" in the HP Universal CMDB Data Flow Management Guide.

Push CI Data from UCMDB to Asset Manager
Data push jobs copy CI or CI relationship records from your UCMDB system to your Asset Manager System. To run a data push job, complete the following steps: 1. Log in to UCMDB as an administrator. 2. Go to Data Flow Management > Integration Studio. UCMDB displays a list of existing integration points. 3. Select the integration point you created for Asset Manager. 4. Add a new data push job as follows: a. Click the button on the right panel.

b. In the Name field, type a unique name for the job.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 52 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

c. Click the

button to add existing TQL queries to the job.

UCMDB Creates a default data push job when creating an integration point.The following table lists the Topology Query Language (TQL) queries in the default data push job. If required, you may create, update, or remove TQL queries for the push job. You may also need to update the mapping. See "How to Customize an Existing Mapping" on page 72. To access these OOTB TQL queries for push, go to Modeling > Modeling Studio > Resources, select Queries for Resource Type and then go to Root > Integration > AM Push. TQL Query AM Business Element Push Description Pushes Business Applications, Business Services and Business Infrastructure CIs. Mapping XML: pushMappingAMBusinessElement.xml AM Business Element Relations Push Pushes relationships between Business Elements (pushed by AM Business Element Push Query) to other business elements or to nodes. Business Elements must have been pushed before this TQL query synchronization in the ‘AM Business Element Push’ TQL query synchronization. Nodes must have been pushed before this TQL query synchronization in the ‘AM Computer Push’ TQL query synchronization. Mapping XML: pushMappingBeRelations.xml

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 53 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

TQL Query AM Computer Push

Description Pushes nodes (Computers, Network Devices, etc.). Also pushes IPs, Interfaces, Disk Devices, Physical Ports, Hardware Boards, Display Monitors, CPUs, Printers, Inventory Scanners, File Systems, and Assets. Minimal attributes for pushing a Node: o o o o

Serial Number Vendor or Discovered Vendor Model or Discovered Model Node Role Note: These are required values, and depend on the capability of the data source to report them.

Mapping XML: pushMappingAMCoumputer.xml AM Computer Relations Push Pushes relationships between Computers to any node (Computers, Network Devices, etc.). Nodes must have been pushed before this TQL query synchronization in the ‘AM Computer Push’ TQL query synchronization. Mapping XML: pushMappingAMComputerRelations.xml AM Host Server And Running LPAR VM Relations Push AM Host Server And Running Solaris VM Relations Push Pushes relationships between Host and Guest (virtualized) systems of LPAR type. Nodes must have been pushed before this TQL query synchronization in the 'AM Computer Push' TQL query synchronization. Mapping XML: pushMappingHostToVMLpar.xml Pushes relationships between Solaris Host and Guest (Virtualized) operating systems. Nodes must have been pushed before this TQL query synchronization in the ‘AM Computer Push’ TQL query synchronization. Mapping XML: pushMappingHostToVMSolaris.xml

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 54 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

TQL Query AM Host Server And Running VM Relations Push

Description Pushes relationships between Host and Guest (Virtualized) operating systems. Nodes must have been pushed before this TQL query synchronization in the ‘AM Computer Push’ TQL query synchronization. Mapping XML: pushMappingHostToVM.xml

AM Installed Software Sync

Pushes Installed Software and User_Software_Utilization CIs. Nodes must have been pushed before this TQL query synchronization in the ‘AM Computer Push’ TQL query synchronization. Mapping XML: pushMappingNormalizedSW.xml (Possible alternate mapping: pushMappingSWNonNorm.xml See "Installed Software" on page 59.)

AM Net Device Relations Push

Pushes relationships between Network Devices to Network Devices. Nodes must have been pushed before this TQL query synchronization in the ‘AM Computer Push’ TQL query synchronization. Mapping XML: pushMappingAMNetDeviceConnections.xml

AM Oracle LMS Push

Pushes the Oracle Running Software and its Oracle LMS data. Nodes must have been pushed before this TQL query synchronization in the ‘AM Computer Push’ TQL query synchronization. Mapping XML: pushMappingOracleLMS.xml

AM Software Sync Hypervisor

Pushed Hypervisor Installed Software. Nodes must have been pushed before this TQL query synchronization in the ‘AM Computer Push’ TQL query synchronization. Mapping XML: pushMappingHypervisor.xml

d. Select or unselect the Allow Deletion option for each query. (The setting determines if this

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 55 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

TQL query is allowed to delete data from Asset Manager, though the actual action on delete is defined by CI type in the mapping xml.) Note: For scheduling configuration, see "How to Schedule Data Push Jobs" on the next page. e. Click OK. f. Save the integration point. 5. Run the job manually to see if the integration job works properly: a. To push all the relevant data for the job, click the button. button.

b. To push only the changes in the data since the job last executed, click the 6. Wait for the job to complete; click the completed.

button multiple times as needed until the job is

7. When the job is completed, the job status becomes one of the following depending on the results: n Succeeded Completed Failed

n

n

8. Click the Statistics tab to view the results; if any errors occur, click the Query Status tab and Job Errors tab for more information. For more information about errors, see "Troubleshooting and Limitations". Note: For details about these tabs and managing the integration, see Integration Jobs Pane in the HP Universal CMDB Data Flow Management Guide. If the job completes successfully, you can view the UCMDB CI data in Asset Manager.

How to View UCMDB Data in Asset Manager
After a push job is successfully completed, you can search for and verify that the pushed CI/relationship data is in Asset Manager.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 56 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Nodes
This includes computers, network devices, etc. To view: 1. Log in to Asset Manager as a system administrator. 2. Go to Portfolio Management > Asset Configurations > IT equipment > Computers and virtual machines. 3. In the opened dialog box, for IP name, type the name of the computer you are searching for. 4. You may use ‘%’ for easier searching. For example, searching IP name for mycomp% returns computer mycomp1, mycomp2, etc. 5. Browse the computer for the different data.

Business Elements
This includes Business Applications, Business Services and Business Infrastructures. 1. Log in to Asset Manager as a system administrator. 2. Go to Asset Lifecycle > IT Services and virtualization > Business services > Business services. 3. Browse the different Services. For more information about viewing data in Asset Manager, see the Asset Manager Documentation.

How to Schedule Data Push Jobs
UCMDB allows you to schedule job executions directly from a data push job. 1. Log in to UCMDB as an administrator 2. Go to Data Flow Management > Integration Studio. UCMDB displays a list of existing integration points. 3. Select the integration point you created for the UCMDB - AM integration. 4. Select the push job. 5. Click the button.

Note: UCMDB allows you to define two different schedules for two types of data push:

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 57 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Changes Synchronization and All Data Synchronization. It is recommended to use the Changes Sync schedule to only synchronize changes and avoid synchronizing the entire set of data each time. 6. Define a schedule for Changes Sync. a. Click on the Changes Synchronization tab. b. Select the Scheduler enabled option. c. Select the scheduling options you want to use. 7. Click the All Data Synchronization tab and select the scheduling options you want to use. 8. Click OK. 9. Save the integration point.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 58 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Installed Software
The Integration supports the following different flows for pushing Installed Software to Asset Manager. You may switch between these flows. Note: The flows below show a simplified high-level flow of the different Installed Software synchronization behavior. The actual behavior may be more complex in some cases, mainly for performance improvement. See also "Switching between Installed Software Flows" on the next page.

Normalized Installed Software
This flow uses an InventoryModel to catalog each exact Software Version. Therefore, if the AM Operator decides to map a certain Software version to a different model, he only has to do it once to the Inventory Model, and does not have to process all the Installed Software in AM. This flow allows using either the SAI Version ID, or the attributes name, version, and vendor, to correctly reconcile the Installed Software, and uses the information to automatically create Models according to major versions as needed.

1. Each Installed Software is first mapped to an Inventory Model. If one does not exist, it creates one. The mapping is done according to the SAI Version ID which is an inventory ID from the Universal Discovery Scanner, or by using the Installed Software's name, version, and vendor. 2. It then sees if the InventoryModel has a final mapping to a Model. If it is a new InventoryModel, or the InventoryModel has no final mapping to a Model, it attempts to search for one with the same name and version. If one is found, it connects the InventoryModel to it; otherwise it creates a new Model. 3. It then connects the Installed Software to the Model as well. Note: Normalized Installed Software is the default flow.

Normalized Installed Software – No Model Creation
This flow uses an InventoryModel to catalog each exact Software Version. Therefore, if the AM Operator decides to map certain Software version to a different model, he only has to do it once to the InventoryModel, and does not have to process all the Installed Software in AM. This flow does not automatically create a Model. Instead, the Model must be connected to the InventoryModel by a different flow, or manually by an Asset Manager Operator.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 59 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

1. Each Installed Software is first mapped to an Inventory Model. If one does not exist, it creates one. The mapping is done according to the SAI Version ID, which is an inventory ID from the Universal Discovery Scanner, or by using the Installed Software attributes: name, version, and vendor. 2. It then sees if the InventoryModel has a final mapping to a Model. If not, it chooses the temporary model (an Unknown Software Model). 3. It then connects the Installed Software to the Model found in the step 2. 4. Later, an Asset Manager Operator manually connects each Inventory Model to a final Model, as he wishes.

Non-Normalized Installed Software
This flow pushes Installed Software and Models only. (It does not map or use the Inventory Models in any way).

Each Installed Software is mapped to a matching Model which is created if not found.

Switching between Installed Software Flows
Switching to Normalized Installed Software Flow This is the default flow, enabled OOTB for this integration. If the flow was changed and you would like to return to this flow: l Change the Installed Software push TQL query name (original name: AM Software Push) to AM Installed Software Push.

Switching to Normalized Installed Software – No Model Creation In Adapter Management, edit am-push-mapping.xml: 1. Go to ci-type="Complete_amModel" 2. Change operation-type to optional_reference

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 60 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Switching to Non-Normalized Installed Software Change the Installed Software push TQL query name (original name: AM Installed Software Push) name to: AM Software Non Norm.

How to Tailor the Integration
This section includes: l "Integration Architecture" on the next page "How to Change Adapter Settings" on page 71 "How to Customize an Existing Mapping" on page 72 "How to Add a New Mapping to the Integration" on page 73 Note: For more detailed information about customizing the mapping, see "Developing Enhanced Generic Push Adapters" in the HP Universal CMDB Developer Reference Guide.

l

l

l

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 61 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Integration Architecture
This section contains details about the architecture of the integration. l "Data Flow Architecture" below "Integration TQL Queries" on the next page "Reconciliation Proposals" on the next page "Asset Manager Rules and Flows" on page 64 "Data Mapping" on page 64 "Push Mapping" on page 65

l

l

l

l

l

Data Flow Architecture
1. The Push Engine executes the TQL query. 2. For a differential flow, the data is compared to the last synchronized data, and only the changes are forwarded. 3. Data is converted into Composite CIs (instances of data according to the TQL Root elements). 4. Data is then pushed to the Push Adapter. 5. The Push Adapter loads the correct mapping for the specific TQL query. 6. All dynamic_mappings are executed and saved to maps, to allow usage in the next mapping stage. For more information, see "Developing Enhanced Generic Push Adapters" in the HP Universal CMDB Developer Reference Guide. 7. Data is mapped from the UCMDB data Model into the AM Data model according to the mapping XML. 8. Data is sent to the AM Connector. 9. AM Connector orders all the data in a set of dependency trees, starting with the records that do not depend on any other record. 10. AM Connector attempts to merge any duplicate records 11. AM Connector starts reconciling and pushing any record without any dependencies, or a record whose dependencies have already been reconciled/pushed to Asset Manager.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 62 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

a. AM Connector first tries to reconcile with existing records b. If it finds a match, it attempts to update that record, c. If it does not find a match, it attempts to create a new record. 12. AM Connector deletes any records it is required to delete in AM, as permitted by action-ondelete.

Integration TQL Queries
A TQL query used for the integration must contain a root query node. Any attribute using in the mapping flow of the Push Adapter must be marked in the selected layout of the query node. Each TQL query may only have one mapping. For more information, see Data Flow Management > Integration > Integration Studio > Integration Studio User Interface > Integration Jobs Pane.

Reconciliation Proposals
When pushing data to Asset Manager, there is an option to create a reconciliation proposal (RP). A reconciliation proposal should be created if there is a change in a specific attribute that may need AM Operator validation or action to support AM business processes. The OOTB configuration creates a reconciliation proposal record when the memory size of the pushed computer has decreased compared to the AM computer. How to use Reconciliation Proposals In the OOTB configuration lMemorySizeMb is marked for attribute-reconciliation. The update script calls the updateMemorySize function. This function verifies if the memory size of the computer was decreased. It initializes all the parameters that are passed to the function validateReconcUpdateAdvance. Calls validateReconcUpdateAdvance and return its returned value. validateReconcUpdateAdvance is a function that returns the value that should be set to the attribute according to the Reconciliation Proposal status.The following table describes its parameters: Parameter AMApiWrapper newVal oldVal Description The wrapper that is used to communicate with the AM. The value of the attribute in the pushed data. The value of the attribute that is retrieved from AM.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 63 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Parameter recordId strCode strName path recordTable

Description The primary key of the table that the attribute belongs to. The prefix of the code field in the reconciliation proposal. The name of the reconciliation proposal. The name of the attribute. The table that the attribute belongs to.

validateReconcUpdateAdvancereturns the value that should be set for the attribute, according to the Reconciliation Proposal status. In order to create a reconciliation proposal flow on a different attribute, the following steps must be completed: 1. Add the tag for this attribute. 2. The update-script should call a new function that initializes the parameters passed to validateReconcUpdateAdvance, and returns the value returned from validateReconcUpdateAdvance. Note: It is suggested to use the updateMemorySize function as a reference.

Asset Manager Rules and Flows
Asset Manager has its own set of rules and flows that are enforced by the Asset Manager API. Some customizations may need to later these rules and flows as well. For more information, see the Asset Manager documentation.

Data Mapping
For details, see Developing Push Adapters in the HP Universal CMDB Developer Reference Guide.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 64 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Push Mapping
This section includes tables explaining each XML tag and the attributes available for configuration. l "Basic Information" below "Reconciliation" on the next page "Target CI Validation" on page 67 "Reference Attribute" on page 68 "Attribute Reconciliation" on page 69 "Action on Delete" on page 69 "Ignored Attributes" on page 70

l

l

l

l

l

l

Basic Information
Attributes in the tag. Attribute ci-type primarykey operationtype Description Name used in push adapter mapping to recognize this record type. The primary key column in AM database schema.

Defines what operations may be done with the record: l insert Only allows creation of new records; if it already exists, an exception is thrown. update - Only allows updates of an existing record; if it does not exist, an exception is thrown. update_else_insert - If the record exists it is updated, otherwise the record is created. reference-only - The record is only used for referencing by other record (and is not updated). An exception is thrown if the record does not exist. ignore - The record is unaffected by operations. insert_else_reference - If the record does not exist, it is created. Otherwise it is only used as a reference and is not be updated; see reference-only.

l

l

l

l

l

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 65 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Attribute parallelpushallowed mergeallowed

Description If enabled with the enabled-parallel-push configuration of the integration point, will attempt to push to the entity with multiple threads in order to increase performance.

If enabled and this entity is an exact duplicate of another entity in the chunk, it merges both entities into one and fixes any relevant references.

errorcode- If used together with the adapter specific errors, allows the printing of a customized override error message to the UI if the push or reconciliation of this entity fails. target-citype fromversion to-version Real name of the AM database table to push this record to. If missing , it uses citype instead. Use this mapping only from (and including) this version. The version is taken from the integration point configuration. Use this mapping only up to (and including) this version. The version is taken from the integration point configuration.

Reconciliation
Reconciliation defined for each mapping may include more than one set of reconciliation rules. When attempting to reconcile the record with existing ones in the AM database, the AM Connector tries each of the reconciliation sets until it finds a matching record. Priority is defined by order of reconciliation rules. If no record in the AM database matches this record, an insert operation occurs if the operation type permits it. Name reconciliation Type Tag Description Parent XML tag for all reconciliation configuration. Represents a single reconciliation rule that may be made of one or more attributes. All attributes inside the rule must match in order for the reconciliation of this rule to be successful. Represents a single attribute used for reconciliation as part of the reconciliation-keys rule.

reconciliation- Tag keys

reconciliation- Tag key Ignore-case

Attribute Part of the reconciliation-key tag. Specifies that this attribute comparison ignores case.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 66 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Name

Type

Description Allows definition of the reconciliation rule by manually defining the WHERE clause of the AQL (Asset Query Language). Uses GString (Groovy String) to generate the replacement String. Any variable or property defined in this record or its parent during the mapping stage (in the Push Adapter) may be used as a variable in the GString. (See http://groovy.codehaus.org/Strings+and+GString for more information). Note: AMPushAdvancesReconciliationException may be thrown inside this tag to skip to the next rule. Used for defining overflow tables. See the AM documentation for more information on overflow tables. When using follow-parent, no other reconciliation may be used as this target CI has a 1:1 connection with its parent, and it uses the parent reconciliation to push data to AM.

reconciliation- Tag advanced

follow-parent

Tag

am-prefix

Attribute Part of the follow-parent tag. Defines the name that the parent target CI uses to reference to this table. (To find out the correct value, navigate to AM Application Designer > Edit Links.)

Example: Portfolio.CMDBId = '${if(globalId==null) { throw new com.hp.ucmdb.adapters.ampush.exception. AMPushAdvancesReconciliationException ('Not enough reconciliation data') }else{ return globalId}}' AssetTag TcpIpHostName Workgroup

Target CI Validation
This tag allows the definition of a validation rule that is executed on specific attribute values: the new one held in memory, and the old one stored in the AM database. The following table shows the attributes of the tag: Name attributename Description The attribute that you want to use for validation.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 67 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Name validationscript

Description A Groovy based script that returns true if this record is to be pushed, and false if it is not to be pushed. The script may access any external Groovy code in the path in order to run the evaluation. l vNewVal - Attribute value of the record in memory. vOldVal - Attribute value of the record in the AM database.

l

failedvalidationerror-code

This optional attribute holds the error code that appears if there is a validation failure. The arguments that can be referenced in the error message are: l {0} - The validated attribute name. {1} - The property value in UCMDB. {2} - The property value in Asset |Manager. {3} - The validation script. {4} - The additional message from the additional-failure-message attribute, or 'null' if there is no additional message.

l

l

l

l

additional- This optional attribute holds an additional error message that can be referenced by failurethe error message in the properties.error file. See failed-validation-error-code, message above. Example:

Reference Attribute
A reference attribute defines a column that references another record from a different or same table. This record is not pushed, or reconciled against existing AM database records, until this reference is resolved. Resolved references are replaced by a reference ID that represents the primary ID of the referenced record. The following table shows the attributes of the tag: Name ci-name datatype Description The CI-type of the referenced record. The value type of the record.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 68 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

Name name referencedirection Example:

Description The column in the current record that is to be populated by the reference ID. According to the tree created by the Push Adapter, the value specifies if the referenced record is a parent or child of the current record.

Attribute Reconciliation
This tag allows the AM connector to decide what to do with an attribute value according to the existing value in the AM database. The following table shows the attributes of the tag: Name Description

attribute- The attribute to be reconciled. name updatescript The script to execute in case of an update operation on the record. The returned value by the groovy script will be push to AM as the value of this attribute. l vNewVal - Attribute value of the record in memory. vOldVal - Attribute value of the record in the AM database.

l

Insertscript

The script to execute in case of an insert operation on the record. The value returned by the Groovy script is pushed to AM as the value of this attribute. vNewVal - Attribute value of the record in memory.

Example:

Action on Delete
This tag allows customization of the behavior on receipt of a delete notification for a record. Note: No deletion occurs if the Allow Delete option in the job definition is disabled. The following actions are possible

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 69 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

l

- Do nothing. - Delete this record from the AM database. - Change the value of one or more attributes in the AM database.

l

l

Example:

Enum Attribute
This tag allows a specific enum attribute to be pushed in a serial mode, when the adapter is configured to push data in parallel mode. Note: This option exists to prevent duplicate key exceptions occurring when several threads push the same enum value. The following table shows the attributes of the tag: Name attribute-name itemized-name Description The enum attribute name. The itemized list format (amOS) of the enum.

Ignored Attributes
This tag allows specific attributes to be ignored and not pushed to the AM database. This capability is commonly used with the from-version and to-version attributes or tags, to ignore certain attributes for specific versions of Asset Manager. The following table shows the attributes of the tag: Name fromversion toversion Example: Description Ignore this attribute only from (and including) this version. The version is taken from the integration point configuration. Ignore this attribute only up to (and including) this version. The version is taken from the integration point configuration.

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 70 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

lSeq

How to Change Adapter Settings
1. Go to Data Flow Management > Adapter Management > AMPushAdapter > Adapters. 2. Right-click AMPushAdapter and click Edit Adapter Source. 3. Scroll down to the tag. 4. Edit the settings as required and click the Save button. The following table shows the Settings relevant to the AM Push Adapter: Setting replication.chunk.size Default 4,000 Description Defines the requested number of CIs and Relationships sent in each chunk. It is possible to adjust this setting to try and improve performance of the server and the Probe. Defines the maximum requested number of Roots sent in each chunk. This works with replication.chunk.size as a limiter on the amount of data sent in each chunk. The name of the Java class used to load the AM Connector. 8 The amount of threads used in Parallel Push Mode. The more threads, the more CPU used. Increasing the pool size may lower performance.

replication.chunk.root.limit

850

PushConnector.class.name

parallel.thread.pool.size

mapping.size.fuse

100,000 The maximum number of records the AM Connector may to retrieve in . The maximum number of retries the AM Connector attempts to push a deadlocked database transaction.

transaction.deadlock.max.retry.count 3

HP Universal CMDB (UCMDB 10.10, CP 13.00)

Page 71 of 191

Universal Discovery Content Guide - HP Integrations Chapter 3: HP Asset Manager Push Integration

How to Customize an Existing Mapping
This example shows you how to add the BarCode/RFID attribute to the integration, including the TQL query, Push Adapter Mapping and AM Mapping configuration. It allows the integration to both push the BarCode/RFID attribute to Asset Manager, as well as use it for reconciliation of a Hardware Asset. After completing the following steps, you may run the job with the customized mapping: 1.

Add the BarcodeOrRfidTag attribute to the AM Computer Push TQL query layout.
In this step we add the attribute of the Asset CI to the integration TQL query so that we can use the attribute and value in the mapping. a. Go to Modeling > Modeling Studio > Resources and select the Queries Resource Type. b. Go to Queries: Root > Integration > AM Push > AM Computer Push. c. Select Asset, right-click and select Query Node Properties. d. Go to the Element Layout tab. e. Move the BarcodeOrRfidTag to the Specific Attributes box. f. Click OK. g. Save the Query.

2.

Add the BarCode Mapping to the pushMappingAMComputer.xml push adapter mapping.
In this step we take the value from the TQL result and remodel it to the Asset Manager Data Model. a. Go to Data Flow Management > Adapter Management > Packages > AMPushAdapter > Configuration Files > pushMapingAMComputer.xml. b. Go to the XML tag. c. Add the variable to hold the value of the barcode:

Similar Documents

Free Essay

Cisco

...FROM THE SOLUTIONS CENTER Solution Guide: Migrating from Brocade Enterprise Fabric Connectivity Manager to Brocade Data Center Fabric Manager Brocade DCFM simplifies infrastructure management with the performance and scalability required in the Brocade data center fabric, which connects applications to infrastructure in the majority of the world’s data centers. FROM THE SOLUTIONS CENTER SOLUTION GUIDE CONTENTS Introduction........................................................................................................................................................................................................................................ 3 Supported Firmware ...................................................................................................................................................... 3 Upgrade Paths ............................................................................................................................................................... 4 Migration Facts .............................................................................................................................................................. 4 Migration Overview ......................................................................................................................................................................................................................... 4 Planning.......................................................

Words: 6893 - Pages: 28

Premium Essay

Management Information Systems

...Table of Contents 1.0 What is Knowledge Management 3 1.1 The Influence of Technology- Applications in the Workplace 3 1.2 Business-Information Technology (IT)Alignment 3 1.3 Aspects of Knowledge Management 4 1.4 Knowledge Strategy – IT Alignment is achieved through the completion of four main steps: 5 1.5 HP’s Knowledge Management Programme 5 1.6 KM Approaches: 6 1.7 Aligning Existing Information Systems with Corporate Goals: 7 2.0 Knowledge Management Integrating Information 8 2.1 Knowledge Management Systems at HP 8 2.2 Implications and Applications 9 2.3 Infrastructure and Collaborative Technology 9 2.4 Building a Knowledge Management Rationale 9 2.5 Knowledge Resources 10 3.0 Challenges faced by HP 11 3.1 Obstacles to KM Implementation 12 3.2 Importance of Organizational Knowledge 12 3.3 Knowledge Management Models 13 4.0 Advantages of adopting new technologies: 15 4.1 Brand identity and Brand loyalty: 15 4.2 Role of Information Systems in establishing Brand Identity & Brand Loyalty: 15 4.3 Social Media and its benefits to organizations: 17 4.4 Threats on over reliance of Information Systems: 18 Wrapping Up 19 5.0 Bibliography 20 1.0 What is Knowledge Management Knowledge Management is a project or framework intended to generate, capture, allocate and control knowledge towards the accomplishment of the organization. This is easily said than done. Organizing a Knowledge Management project obliges plentiful changes and...

Words: 5424 - Pages: 22

Free Essay

Test

...HP 3PAR StoreServ Storage Concepts Guide HP 3PAR OS 3.1.2 MU2 Abstract This guide is for all levels of system and storage administrators who plan storage policies, configure storage resources, or monitor the storage usage of HP 3PAR storage systems. HP Part Number: QR482-96384 Published: June 2013 © Copyright 2007, 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 and 12.212, Commercial 1 Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgements Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation. Oracle is a registered trademarks of Oracle and/or its affiliates. UNIX® is a registered trademark of The Open Group. Warranty To obtain a copy of the warranty for this product, see the warranty information website: http://www.hp.com/go/storagewarranty Contents 1 Overview..............................................................

Words: 36581 - Pages: 147

Premium Essay

Increase Productivity of Print Management System

...| Stevenson UniversityGraduate SchoolBTM606 Creativity in Information SystemsIncreasing Productivity of the Print Management System | | Contents Table of Figures 2 Background Information 3 Problem Statement 4 Three Basic Principles Behind All Creative Thinking 4 Preparation Phase 6 Imagination Phase 8 Development Phase 9 Troubleshooting with Technology App on Tablet 10 Scenarios 10 Action Phase 12 Conclusion 13 Glossary of Terms and Abbreviations 15 Bibliography 16 Table of Figures Figure 1 – HP All-In-One Printer 3 Figure 2 – Plesk’s Model of Directed Creativity 5 Figure 3 – Flowchart for Current Print Management System 7 Figure 4 – Six Thinking Hats 8 Figure 5 – New Print Management System Flowchart 13 Figure 1 – HP All-In-One Printer Background Information As part of the Digital Learning Initiative, Baltimore County Public Schools (BCPS) contracted Hewlett-Packard (HP) for hybrid devices and all-in-one printers. HP was contracted to deliver, service, and maintain the HP revolve devices and the all-in-one networked printers to all central offices and school locations for BCPS. HP technicians removed all previously owned BCPS printer equipment and replaced them with HP networked all-in-one printers to be more cost effective and efficient. This new process was designed to fulfill Dr. Dance's vision to create budget savings that will allow BCPS to reallocate funding resources for the purchase of tablets/laptops for every teacher and...

Words: 2710 - Pages: 11

Premium Essay

Pros And Disadvantages Of The UK Housing Market

...living index amounting to 133.68. (Jones C. 2017). Will the government intervene once again and restore parity to cost of common residences? I will be viewing the UK housing market system and provide a thorough evaluation as to whether government intervention is mandatory in the aspect of housing market. Free market is a market determined by the consumers and producers. Resources in this type of market are only allocated to those who can afford it, which deduces that there is constant inequality of income amongst individuals, for example, Hong Kong. They’re known to possess the lowest income tax, statistics justifying their tax “starting at 2% and ending at 17%.’’(https://www.guidemehongkong.com/business-guides/staffing-your-business/hong-kong-salaries-tax-guide)...

Words: 1476 - Pages: 6

Premium Essay

Cloud Computing

...Security Alliance “Top Threats to Cloud Computing” at http://www.cloudsecurityalliance.org/topthreats/csathreats.v1.0.pdf subject to the following: (a) the Guidance may be used solely for your personal, informational, non-commercial use; (b) the Guidance may not be modified or altered in any way; (c) the Guidance may not be redistributed; and (d) the trademark, copyright or other notices may not be removed. You may quote portions of the Guidance as permitted by the Fair Use provisions of the United States Copyright Act, provided that you attribute the portions to the Cloud Security Alliance “Top Threats to Cloud Computing” Version 1.0 (2010). Copyright © 2010 Cloud Security Alliance 2 Top Threats to Cloud Computing V1.0 Table of Contents Introduction................................................................................................................................... 2 Foreword........................................................................................................................................ 4 Executive Summary ...................................................................................................................... 6 Threat #1: Abuse and Nefarious Use of Cloud Computing .......................................................... 8 Threat #2: Insecure Interfaces and APIs ....................................................................................... 9 Threat #3: Malicious...

Words: 3759 - Pages: 16

Free Essay

Nintendo

...game company, becoming what is arguably the most influential in the industry, and Japan's third most valuable listed company, with a market value of over US$85 billion.[8] Also, Nintendo of America is the majority owner of the Seattle Mariners Major League Baseball team.[9] The name Nintendo can be roughly translated from Japanese to English as "leave luck to heaven".[10] As of October 18, 2010, Nintendo has sold over 565 million hardware units and 3.4 billion software units.[11] Contents * 1 History o 1.1 As a card company (1889–1956) o 1.2 New ventures (1956–1974) o 1.3 Electronic era (since 1974) + 1.3.1 Handheld console history * 2 Infrastructure o 2.1 Key Executives o 2.2 Offices and locations * 3 Software development studios o 3.1 First-party studios o 3.2 Second-party studios o 3.3 Former affiliates * 4 Policy o 4.1 Emulation o 4.2 Content guidelines o 4.3 License guidelines o 4.4 Seal of Quality + 4.4.1 NTSC regions + 4.4.2 PAL regions o 4.5 Environmental record * 5 See also * 6 Notes * 7 References * 8 Further reading * 9 External links [edit] History Main article: History of Nintendo Former headquarters plate, from when Nintendo was solely a playing card company [edit] As a card company (1889–1956) Nintendo was founded...

Words: 7314 - Pages: 30

Premium Essay

Manaement

...distinctive habits of companies of enduring greatness. In the words of the authors, “Visionary companies are premier institutions – the crown jewels – in their industries, widely admired by their peers, and having a long track record of making a significant impact on the world around them.” Visionary leaders and breakthrough ideas come and go, but visionary companies survive the transitions. The “successful habits” of the visionary companies were observed in comparison to “silver medalist” companies in the same industry. Both the visionary and comparison companies outperformed the market, but the visionary companies demonstrated extraordinary long-term results. The tandems most frequently referenced in the book are GE/Westinghouse, HP/Texas Instruments, Motorola/Zenith, P&G/Colgate, Merck/Pfizer, and Wal-Mart/Ames. These comparisons dispelled commonly held myths regarding the nature of exceptional companies. Myth Reality 1 It takes a great idea to start a great company Visionary companies did not demonstrate early success 2 Visionary companies require great and charismatic visionary leaders Leaders of visionary companies were focused on building great institutions as opposed to building their individual reputations 3 The most successful companies exist first and foremost to maximize profits Visionary companies are characterized by the pursuit of multiple priorities only one of which is making money. 4 Visionary companies share a common subset...

Words: 6143 - Pages: 25

Premium Essay

Productivity Handbook by Hubspot

...Welcome to the productivity handbook My use of desktop and search-engine technology is slowly being replaced by the use of apps that provide me with information, storage, and answers relevant to my personal needs. My guess is that while you may not have taken note, you’re using more apps to do more online and increase your productivity. Apps inside social networks provide answers. Apps inside socialbookmark sites serve up interesting reading. Apps in content-curation tools like Storify provide relevant context for content. Apps on mobile devices, such as Yelp’s, help you find bars and restaurants. Apps using QR readers give you deeper information on companies and products. Apps are delivering sports scores, movie times, videos and images. In this guide I'll give you the why and how on a handful of apps that I use every single day to increase my personal productivity and run my business. Sincerely, John Jantsch, founder of Duct Tape Marketing table of contents dropbox // page 6 evernote // page 8 gmail // page 10 stumbleupon // page 12 instagram // page 14 pinterest // page 16 delicious // page 18 about the author // page 20 Dropbox isn’t the new kid on the block and lots of folks speak lovingly about this online file storage service. There’s a free version that may be robust and large enough for most, but I’ve chosen the full meal deal because I use Dropbox so completely. There are other tools that can do all of what I’m going to describe...

Words: 4699 - Pages: 19

Premium Essay

Mbo at Hewlett Packard

...NUMBER: EC-16 MAY 2000 HP E-SERVICES.SOLUTIONS The concept behind e-services is there’s a particular task, asset, or capability that you want to gain access to, that now can be made available to you over the Net, because it’s now being created as an Internet service. ––Linda Lazor, Director of Operations, ESS, Hewlett-Packard How does any large company reinvent itself? Can a company with a past have a future? I mean that’s basically the question that we’re posing because a lot of people claim that anyone who has a past does not have a future in this world. ––Nick Earle, President, ESS, Hewlett-Packard In early April 2000, Nick Earle sat in his cube on the upper level of Building 44 of the HewlettPackard (HP) campus in Cupertino, California. He wore a wireless telephone headset, which allowed him the freedom to jump up and wander about his team’s open cubes as he fielded calls from potential business partners. Earle, age 42, was President and Chief Evangelist of the 90person E-Services.Solutions (ESS) group. The group had grown out of a task force he had put together more than a year earlier. Asked to create an Internet marketing strategy, he and several other “frustrated radicals” created a plan which ultimately led to the formation of the ESS group. ESS now held the mandate to develop an Internet strategy and framework for all of HP. Earle and his team faced tough challenges. They had pulled together some great technologies and products within HP and secured partnerships...

Words: 10981 - Pages: 44

Premium Essay

Gsl Mc

...Knowledge Checks: Multiple Choice and Extended Response Questions and Solutions GLOBAL STRATEGY AND LEADERSHIP Version 16a © Copyright CPA Australia unless otherwise indicated. Multiple Choice Questions and Solutions KNOWLEDGE CHECKS: MULTIPLE CHOICE AND EXTENDED RESPONSE QUESTIONS AND SOLUTIONS | i Contents Questions 1 Module 1 Question 1.1 Question 1.2 Question 1.3 Question 1.4 Question 1.5 Question 1.6 Question 1.7 Question 1.8 Question 1.9 Question 1.10 Module 2 Question 2.1 Question 2.2 Question 2.3 Question 2.4 Question 2.5 Question 2.6 Question 2.7 Question 2.8 Question 2.9 Question 2.10 Module 3 Question 3.1 Question 3.2 Question 3.3 Question 3.4 Question 3.5 Question 3.6 Question 3.7 Question 3.8 Question 3.9 Question 3.10 Module 4 Question 4.1 Question 4.2 Question 4.3 Question 4.4 Question 4.5 Question 4.6 Question 4.7 Question 4.8 Question 4.9 Question 4.10 R:\Workgroups\CPA-Production\CPA MCQs and ERs\1st Semester 2016\GSL\GSL-Knowledge-check-MCQ_16a.docx 1 1 1 1 2 2 2 2 2 3 3 3 3 3 4 4 4 4 5 5 5 6 6 6 6 6 7 7 7 7 8 8 8 8 8 9 9 9 10 10 10 10 11 11 DTP: Mira 1st set 15b 05-02-16 ii | GLOBAL STRATEGY AND LEADERSHIP Module 5 Question 5.1 Question 5.2 Question 5.3 Question 5.4 Question 5.5 Question 5.6 Question 5.7 Question 5.8 Question 5.9 Question 5.10 Module 6 Question 6.1 Question 6.2 Question 6.3 Question...

Words: 25487 - Pages: 102

Premium Essay

Bloomberg Get Start

...FOR EDUCaTION a bloomberg Professional Service Offering GETTING STaRTED GUIDE FOR STUDENTS // FEbRUaRy 2012 CONTENTS>>>>>>>>>> 02 bLOOMbERG TERMINaL® 02 The bloomberg Keyboard 03 accessing the application 04 Logging In 05 bloomberg Panels 06 FUNCTIONS & SECURITIES 06 Running Functions 07 Working with Securities 09 basic Search (autocomplete) 10 Full Search 11 browsing Menus 09 NavIGaTION 12 PERFORMING aNaLySIS 12 Navigating Functions 13 Stock/Company Screening 14 analyzing a Company 15 analyzing an Index, bond or Currency 16 ExPORTING DaTa 16 The bloomberg Excel add-In 19 Drag & Drop 19 Printing and Other Export Options 20 GETTING HELP aND LEaRNING MORE CONTENTS>>>>>>>>>> 21 aPPENDIx 21 Equity 21 Fundamental analysis 22 analytics 23 M&a analysis 23 Fixed Income 25 Swaps 26 Money Markets 27 Structured Finance analytics 28 Price Discovery 29 analytics 29 Descriptive 29 Relative value 29 Ticketing 29 Hedging 30 additional FI Functions 31 FI Futures and Options 32 Repo analysis Data 32 Calculators 33 High yield/Syndicated Loans/Distressed Research 34 Municipal bonds INTRODUCTION For more than 20 years, bloomberg has been committed to helping universities and colleges incorporate the bLOOMbERG PROFESSIONaL® service into their academic programs to better prepare students for the global job market. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Universities and colleges around the globe use Bloomberg to bring the real world of finance into...

Words: 13258 - Pages: 54

Premium Essay

Establishing Security Risks and Countermeasures for Large Scale Businesses

...Establishing Security Risks and Countermeasures for Large Scale Businesses Stephen Yopp 23 May 2014 ISSC-361 American Military University Establishing risks and countermeasures can be a complex procedure, even more so when protecting hundreds of systems from internal and external threats. Many tools exist to assist in implementing and scaling security operations. There are many assets that represent risks to businesses ranging from information systems to the data which is stored on them and therefore almost as many existing threats (Smith, 2013). The National Institute of Standards and Technology (NIST) describes 11 types of assets; people, organizations, systems, software, databases, networks, services, data, computing devices, circuits, and websites (Halberdier, Waltermire, and Wunder, 2011). This list is more extensive than the categories discussed, for the sake of brevity, but it might be helpful to enterprise employees seeking to identify different assets. Hardware represents a large investment for businesses. Servers, network devices, cables, workstations, and mobile devices can cost enterprise businesses millions of dollars up front. Because information systems are such an integral part of modern business, companies cannot afford to be without access to file and print servers or internet access. This means that the loss of hardware would represent setbacks in productivity, potential negative impacts to the organization’s reputation, and necessary additional...

Words: 3285 - Pages: 14

Premium Essay

Tools for Business

...Mid Sweden University The Department of Information Technology and Media (ITM) Author: Katarina Lundqvist, kalu9700@student.miun.se Study program: Master of Science in Engineering – Computer Engineering, 270 higher education credits Examiner: Tingting Zhang, tingting.zhang@miun.se Tutor: Aron Larsson, aron.larsson@miun.se Tutor: Mats Olsson, mats.olsson@sogeti.se Scope: 20102 words inclusive of appendices Date: 2010-03-17 M.Sc. Thesis in Computer Engineering AV, 30 higher education credits Tools for Business Intelligence A comparison between Cognos 8 BI, Microsoft BI and SAP BW/NetWeaver Katarina Lundqvist Abstract 2010-03-17 Tools for Business Intelligence A comparison between Cognos 8 BI, Microsoft BI and SAP BW/NetWeaver Katarina Lundqvist Abstract The aim of the thesis was to conduct a general study of Business Intelligence and BI systems followed by a comparison of Cognos 8 BI, Microsoft BI and SAP BW/NetWeaver. The goal was to distinguish similarities and differences between the tools regarding technique, cost, usability and educational need and to provide a mapping for different customer situations. The method consisted of a theoretical study followed by a practical part including development, testing and interviews. The comparison showed that SAP and Microsoft both use the client/server model while Cognos is an integrated web-based system built on SOA. SQL Server can only be installed on Windows while BW and Cognos also support...

Words: 25350 - Pages: 102

Free Essay

Exal

...Chinese | 華碩電腦股份有限公司 | Literal meaning | ASUSTeK Computer Inc. (Great Splendid Computer Corporation) | [show]Transcriptions | | ASUSTeK Computer Inc., trading as Asus (/ˈeɪsuːs/[2]), is a Taiwanese multinational computer hardware and electronics company headquartered in Taipei, Taiwan. Its products include desktops, laptops, mobile phones, monitors, motherboards, servers, tablet PCs and video cards. The company's slogan is: "Inspiring Innovation. Persistent Perfection."[3] Asus is the world's fifth-largest PC vendor by 2012 unit sales (after HP, Lenovo, Dell and Acer).[4] Asus appears in BusinessWeek’s "InfoTech 100" and "Asia’s Top 10 IT Companies" rankings, and it ranked first in the IT Hardware category of the 2008 Taiwan Top 10 Global Brands survey with a total brand value of US$1.3 billion.[5] Asus has a primary listing on the Taiwan Stock Exchange and a secondary listing on the London Stock Exchange. Contents * 1 Name * 2 History * 3 Operations * 4 Products * 4.1...

Words: 6997 - Pages: 28