Oracle® Enterprise Manager

Installation and Configuration Guide for HP Service Manager Version 9 Connector

Release 12.1.0.1.0

E38607-03

December 2013

Oracle Enterprise Manager Installation and Configuration Guide for HP Service Manager Version 9 Connector, Release 12.1.0.1.0

E38607-03

Copyright © 2013, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Michael Zampiceni

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction to the Connector

- 1.1 Auto Ticketing

- 1.2 Manual Ticketing

- 1.3 Ticket Templates

- 1.4 Grace Period

- 1.5 Retry

- 1.6 Versions Supported

- 1.7 Prerequisites

2 Installing and Uninstalling the Connector

- 2.1 Installing the Connector

- 2.1.1 Installing the Connector if Enterprise Manager is in "Offline" Mode

- 2.2 Uninstalling the Connector

3 Configuring the Connector

- 3.1 Creating a Connector Instance

- 3.2 Configuring the Connector

- 3.3 Enabling or Disabling the Connector

- 3.4 Providing General Settings

- 3.4.1 Connection Settings

- 3.4.2 Web Console Settings

- 3.4.3 Grace Period

- 3.4.4 Retry

- 3.5 Working with Ticket Templates

- 3.5.1 Adding Ticket Templates

- 3.5.2 Viewing Template Code

- 3.5.3 Removing a Template

- 3.5.4 Editing Templates

- 3.5.5 Restoring Templates

- 3.6 Configuring the HP Service Manager Web Console

- 3.7 Navigating Between Enterprise Manager and HP Service Manager

- 3.7.1 Navigating from Enterprise Manager to HP Service Manager

- 3.7.2 Navigating from HP Service Manager to Enterprise Manager

4 Creating Service Manager Tickets

- 4.1 Automatically Creating a Ticket

- 4.2 Manually Creating a Ticket

- 4.3 Post-creation Advisory Information

5 Using Out-of-Box Templates

- 5.1 Out-of-Box HP Service Manager Templates

- 5.2 Reading and Mapping Ticket Templates

- 5.2.1 Service_Manager_9_Default_Incident.xsl - Create

- 5.2.2 Service_Manager_9_Default_Incident.xsl - Update

- 5.2.3 Service_Manager_9_Default_Incident_AutoClose.xsl - Create

- 5.2.4 Service Manager_9_Default_Incident_AutoClose.xsl - Update

- 5.2.5 Formatted Enterprise Manager Incident Contents

- 5.2.6 Severity Mapping

- 5.3 Customizing Ticket Templates

- 5.4 Exporting the Ticketing Template Files

- 5.5 Modifying Ticket Templates

- 5.6 Custom Template Examples

- 5.6.1 Example 1

- 5.6.2 Example 2

6 Customizing Support Ticketing Inbound Operations

- 6.1 Adding a Custom Field to HP Service Manager

- 6.2 Setting Up EM CLI

- 6.3 Exporting the Notification Script Files

- 6.4 Setting Up the Notification Script

- 6.5 Uninstall Customization to HP Service Manager for Support Ticket Inbound Operations

- 6.5.1 Remove Calls to the Notification Script

- 6.5.2 Remove Custom Field Added for Script Operation

- 6.6 Uninstalling EM CLI

A Enabling SSL for HTTPS

- A.1 Generating and Importing a Certificate Request

- A.2 Installing and Configuring SSL

- A.3 Importing the Adapter Certificate into Enterprise Manager

B Preventing HP Service Manager Update Issues

C Enterprise Manager Incident Format

D HP Service Manager WSDL Format

E Enterprise Manager Incident Examples

- E.1 Create Example

- E.2 Update Example

- E.3 Clear Example

- E.4 Reopen Example

Index

Preface

This Connector Configuration guide provides the information that you require to configure Management Connectors that integrate Enterprise Manager with other management tools and help desk systems.

Audience

This guide is written for Oracle Database system administrators who want to configure Management Connectors to enable integration between Enterprise Manager and other systems.

You should already be familiar with Oracle Enterprise Manager.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following books in the Oracle Enterprise Manager documentation set:

- Oracle Enterprise Manager Cloud Control Basic Installation Guide

- Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide

- Oracle Enterprise Manager Cloud Control Administrator's Guide

- Oracle Enterprise Manager Cloud Control Upgrade Guide

- Oracle Enterprise Manager Framework, Host, and Services Metric Reference Manual

- Oracle Enterprise Manager Command Line Interface

- Oracle Enterprise Manager Cloud Control Extensibility Programmer's Guide

- Oracle Database 2 Day DBA

The latest versions of this and other Oracle Enterprise Manager documentation can be found at:

http://www.oracle.com/technology/documentation/oem.html

Oracle Enterprise Manager also provides extensive online help. Click Help on any Oracle Enterprise Manager page to display the online Help system.

Printed documentation is available for sale in the Oracle Store at

http://oraclestore.oracle.com/

To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at

http://otn.oracle.com/membership/

If you already have a user name and password for OTN, then you can go directly to the documentation section of the OTN Web site at

http://otn.oracle.com/documentation/

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction to the Connector

The HP Service Manager 9 Connector 12.1.0.1.0 integrates HP Service Manager Version 9 (HPSM) incident management with Enterprise Manager. Using this connector, you can create, update, reopen, and close an HP Service Manager Incident (ticket) based on incidents in Enterprise Manager. The HP Service Manager Connector integrates Enterprise Manager with HP Service Manager through either an HTTP or HTTPS connection. Note that the term ticket refers to an HP Service Manager incident, and is used throughout this document.

The ticket generated by the connector contains the relevant information about the Enterprise Manager incident, including a link to the Enterprise Manager console to enable helpdesk analysts leverage Enterprise Manager's diagnostic and resolution features to resolve the incident. In Enterprise Manger, the ticket ID, ticket status, and link to the HP Service Manager console is the shown in the context of the incident. This provides Enterprise Manager administrators with ticket status information and an easy way to quickly access the ticket.

The following sections explain various HP Service Manager Connector concepts and requirements that you should understand before you start using the HP Service Manager Connector:

- Auto Ticketing

- Manual Ticketing

- Ticket Templates

- Grace Period

- Retry

- Versions Supported

- Prerequisites

1.1 Auto Ticketing

Auto ticketing refers to creating or updating tickets automatically for any matching rule(s) in Enterprise Manager. You can define a set of event or incident rules for which tickets must be opened/updated for changes in underlying event or incident attributes. For example, changing event severity from Warning to Critical can update the associated ticket.

See Also:
"Incident Management Chapter" in the Oracle Enterprise Manager Administrator's Guide.

After the ticket is opened, any subsequent update of the incident attributes or underlying event attributes, such as a change in underlying events severity, updates the ticket. After the incident is cleared in Enterprise Manager, the ticket is updated and you can optionally go to HP Service Manager to close the ticket.

See Also:
Section 4.1, "Automatically Creating a Ticket".

1.2 Manual Ticketing

From the Enterprise Manager console, you can manually open an HP Service Manager ticket based on an open incident in Enterprise Manager. The HP Service Manager Connector populates the ticket with details based on the incident and the ticket template selected.

1.3 Ticket Templates

Ticket templates are XML transformation style sheets that transform Enterprise Manager incidents to a ticket format before the requests are sent to HP Service Manager. A ticket template specifies how an Enterprise Manager incident and its associated event attributes can be mapped to the ticket attributes of HP Service Manager.

These templates specify how Enterprise Manager incident attributes can populate the fields of a Service Manager ticket. A ticket template helps in the mapping of Enterprise Manager incident fields into Service Manager incident fields.

In Auto Ticketing, while setting up a rule, you select a configured connector and select the ticket template from the template list. The selected ticket template is used when a ticketing request is sent to HP Service Manager. For manual ticketing, you have to select a connector instance and ticket template before submitting a request for ticket creation.

1.4 Grace Period

The grace period enables you to prevent creating a large number of tickets for frequently created incidents due to reoccurrence of the same event.

For recurring incidents, the grace period is a time period during which reoccurrences of the same incident update (or reopen) an existing ticket for the incident instead of opening a new ticket.

For example, an incident triggers and a ticket is opened for it. If the grace period is one hour and the incident is cleared at 10:00 a.m., and if the same incident retriggers before 11:00 a.m. (one-hour grace period), the ticket that had been originally created for the incident is updated/reopened rather than creating a new ticket.

1.5 Retry

The “Retry” section, available on the connector configuration page, enables you to specify whether a failed ticketing request needs to be retried within a configurable expiration time.

Enabling the Retry option gives you the option of specifying whether you want to resend a ticketing request if the request fails the first time, and specifying the time period after which you want to abandon the retry. Enterprise Manager retries every 5 minutes until the request is successful or the retry interval expires.

1.6 Versions Supported

This connector supports the following versions of Oracle Enterprise Manager and HP Service Manager:

- Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.2.0 and higher versions

- HP Service Manager 9.x

1.7 Prerequisites

Before using the HP Service Manager Connector, ensure that you meet the following prerequisites:

- Service Manager 9 service tier is installed and configured.

- Service Manager 9 consoles are installed and configured. If the URL connector framework option is selected, the Service Manager Web console must be installed and configured. To install the middle tier, see the HP Service Manager 9 Web Tier Installation Guide. To configure the Web console, see Section 3.6, "Configuring the HP Service Manager Web Console" for instructions.

2 Installing and Uninstalling the Connector

The HP Service Manager Connector is not installed as part of the Enterprise Manager base installation, so you need to manually install it as described in this chapter. The following topics are discussed:

- Installing the Connector

- Installing the Connector if Enterprise Manager is in "Offline" Mode

- Uninstalling the Connector

2.1 Installing the Connector

The HP Service Manager connector is not included out-of-the-box, so you must download it from the Oracle Enterprise Manager store. All connectors in the Enterprise Manager store are available on the Self Update page for downloading.

To download and install the connector:

1. From the Setup menu of the Enterprise Manager console, select Extensibility, then Self Update.

See Also:
"Refer to the "Setting up Self Update" section of the "Updating Cloud Control" chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide for more details:

http://docs.oracle.com/cd/E24628_01/doc.121/e24473/self_update.htm#BEJJEHDJ

2. Click on the Management Connector link in the Type column.
The HP Service Manager connectors appear in the list with a status of Available.

3. Click on the appropriate HP Service Manager connector to select it, and then click Download.
The Schedule Download window appears, where you can determine when the download should be performed.

4. Click Select to download immediately.
If you want to schedule the download for a later time, specify the date and time when the download should occur, and click Select. You will need to return and finish the remainder of this procedure after the scheduled download date and time.

5. If necessary, refresh the screen until the status of the connector changes to Downloaded.

6. Click on the HP Service Manager connector to select it, then click Apply.
After you respond to the prompt to confirm the operation, a page appears that indicates the request has been submitted.

7. Refresh the screen until the status of the connector changes from Apply Scheduled to Applied.

2.1.1 Installing the Connector if Enterprise Manager is in "Offline" Mode

Under certain circumstances, such as in high security environments, an active Internet connection between Enterprise Manager and the Enterprise Manager Update Store may not be available. In such situations, Enterprise Manager can be set to install the connector in an "offline" mode.

The installation process still requires that a computer exist at your site that has Internet access, as a connection to the Enterprise Manager Update Store is still required to obtain the necessary files. The files that you download to this computer can then be transferred to a computer behind your firewall.

To install the connector if Enterprise Manager is in "offline" mode:

1. From the system that you will ultimately deploy the connector, set Enterprise Manager Cloud Control to Offline Mode:

1. From the Setup menu, select Provisioning and Patching, then select Offline Patching.

2. In the Online and Offline Settings page, select Offline.

2. From the Setup menu, select Extensibility, then select Self Update.

3. On the Self Update page, click Check Updates. A message appears with the following URL to an Oracle site from where the updates catalog file can be downloaded:

https://updates.oracle.com/Orion/Download/download_patch/p9348486_112000_Generic.zip

4. From an Internet-enabled computer, download the catalog file using the aforementioned URL.

5. Copy the downloaded catalog file to the OMS host or the Management Agent host where you plan to import the connector.

6. Import the catalog file to Enterprise Manager:

- If the catalog file is on the OMS host:

emcli import_update_catalog -file="file" -omslocal

Where:

- -file: is the direct path to the connector archive (*.zip).

- -omslocal: indicates that the path mentioned in the -file option is directly accessible to the Enterprise Manager server

- If the catalog file is on a different host:

emcli import_update_catalog -file="file" -host="hostname" [-credential_set_name="setname"] | -credential_name="name" -credential_owner="owner"

Example 2-1 shows a sample for importing the catalog archive.

7. On the Self Update page, in the table, click Management Connectors.

8. On the Connector Updates page, select the imported update that is available for download. Click Download.
A message appears with a URL to an Oracle site from where the update can be downloaded.

9. From a computer that is connected to the internet, download the update using the aforementioned URL.

10. Copy the downloaded file to the OMS host or the Management Agent host where you plan to deploy the connector.

11. To import the downloaded connector archive into Enterprise Manager, run the following command:

emcli import_update -file=”<path to *.zip file>” -omslocal

Where:

- -file: is the direct path to the connector archive (*.zip).

- -omslocal: indicates that the path mentioned in the -file option is directly accessible to the Enterprise Manager server

Example 2-1 Sample for Importing Catalog Archive

emcli import_update_catalog -file="/u01/common/p9348486_112000_Generic.zip"  -omslocal

Imports the master catalog file p9348486_112000_Generic.zip. The file must exist
on the OMS host. In a multiple OMS setup, the request can be processed by any
OMS, so the file should be accessible from the OMS processing the request. This
means that the file must be kept on a shared location that is accessible from all
the OMS instances.

emcli import_update_catalog -file="/u01/common/p9348486_112000_Generic.zip" -host="host1.example.com" -credential_set_name="HostCredsNormal"

Imports the master catalog file p9348486_112000_Generic.zip that is present on
the host host1.example.com. The host must be a managed host target in Enterprise
Manager, and the Management Agent on this host must be up and running. The
preferred unprivileged credentials for host host1.example.com are used to retrieve
the remote file.

2.2 Uninstalling the Connector

To uninstall the connector, you must first delete all defined instances of the connector, then you must delete the connector from the Self Update page.

To uninstall the connector:

1. From the Setup menu, select Extensibility, then Management Connectors.

2. Select an instance of the connector you want to delete, then click Delete.

3. On the Confirmation page, click Yes.

4. Repeat steps 2 and 3 until all instances of the connector have been deleted.

5. From the Setup menu, select Extensibility, then Self Update.

6. Click on the Management Connector link in the Type column.
A list of updates appears for Management Connectors.

7. Click on the connector you want to delete, select Actions, then select Delete.
The Delete Update window appears.

8. Click Delete to delete the connector.
A pop-up confirmation window appears.

9. Click OK to confirm and delete the connector.

3 Configuring the Connector

This chapter explains how to perform tasks directly or indirectly related to configuring the connector, and also discusses the post-configuration task of navigating between the Enterprise Manager and HP Service Manager consoles. The following topics are discussed:

- Creating a Connector Instance

- Configuring the Connector

- Enabling or Disabling the Connector

- Providing General Settings

- Working with Ticket Templates

- Configuring the HP Service Manager Web Console

- Navigating Between Enterprise Manager and HP Service Manager

3.1 Creating a Connector Instance

To create a connector instance:

1. From the Setup menu of the Enterprise Manager console, select Extensibility, then Management Connectors.

2. Select a connector type of HP Service Manager 9 Connector from the Create Connector drop-down list, then click Go.

3. Enter the connector name and description on the next page, then click OK.

The connector instance appears as unconfigured in the Management Connectors page, as shown in Figure 3-1.

Figure 3-1 Unconfigured HPSM 9 Connector

3.2 Configuring the Connector

To configure the connector:

1. Click on the name of the HP Service Manager Connector.
The General tab of the Configure Management Connector page appears, as shown in Figure 3-2.

Figure 3-2 Configure Management Connector Page

2. Provide the required settings. See Section 3.4, "Providing General Settings" for details.

3. Click OK.
The Management Connectors page reappears. The row for the HP Service Manager Connector should have a check mark in the Configured column.

4. Optionally, you can click the configure icon again to check for the available ticket templates.

5. Click the Ticket Templates tab.
All out-of-box ticket templates should appear in the table.

If you choose HTTPS as the protocol to establish a connection between HP Service Manager and Enterprise Manager, see "Importing the Adapter Certificate into Enterprise Manager" in Appendix A.

3.3 Enabling or Disabling the Connector

You can enable or disable a connector from the Management Connectors page by selecting the connector and clicking either Enable or Disable. After a connector is disabled, a red cross icon appears under the status column. By default, the connector instance is enabled as soon as it is configured.

Note:
Only enabled connectors are available for ticketing operations.

3.4 Providing General Settings

The following sections explain how to provide various configuration details.

3.4.1 Connection Settings

The HP Service Manager Connector communicates with the Service Manager server through a web service provided through the Service Manager web tier. All fields are mandatory.

- Web Service End Points - URL of the web service end-point to call for the createTicket, updateTicket, and getTicket operations.The Service Manager web service URL is formatted as shown below:

http://[Hostname]:13080/sc62server/ws

In most cases, you will just need to replace [Hostname] with the host name or IP address of the server where the web tier is located. The port number defaults to 13080, so you only need to change the port number if you have changed the port used by the web tier. The only other change you might make is the protocol. If you want to use SSL, you need to change the protocol from http to https.

Note:
If you want to use SSL to encrypt communications between Enterprise Manager and Service Manager, see "Importing the Adapter Certificate into Enterprise Manager" in Appendix A.

- Service Manager Username - Specify the user name for HTTP basic authentication supported by the HP Service Manager web services. This user name must have the appropriate privileges/roles in HP Service Manager to create, update, and query tickets in the HP Service Manager. All tickets created through the connector are generated with this user account.

- Service Manager Password - Specify the password associated with the user specified in the Service Manager Username field.

- Ticket Number - Enter a valid ticket number to test the connection when you save the configuration.

- If you specify the correct Web service end-points and enter a valid ticket number, the following message appears on the Management Connectors page after you click OK:
Connection test succeeded. The configuration was saved.

- If you have not previously saved the connector configuration and enter incorrect Web service endpoints or an invalid ticket number, the following message appears on the Management Connectors page after you click OK:
Connection test failed. The configuration was saved.

- If you have previously saved the connector configuration and enter incorrect Web service endpoints or an invalid ticket number, the following message appears on the Management Connectors page after you click OK:
Connection test failed. The configuration was not saved.

3.4.2 Web Console Settings

Web Console settings are required if you want the Connector to provide links to HP Service Manager tickets created by Enterprise Manager in the context of an incident. This feature requires configuration changes in HP Service Manager. See Section 3.6, "Configuring the HP Service Manager Web Console" for details.

To enable this functionality, provide the following Web console settings:

- Enable web console - Check this box to enable launching of the HP Service Manager ticket page within context from Enterprise Manager.

- Web Server - Specifies Web server information the connector uses to connect to the web tier when accessing incidents in HP Service Manager. Set the value using the following format:

<hostname>:<port>/<tier>

Where <hostname> is the hostname or IP address of the web tier server machine, <port> is the port that the web tier is configured to support, and <tier> is the name of the web services tier. The default value for the port is 8080, and the default name of the web tier is sm7.

A sample value for the field is as follows:

10.2.1.110:8080/sm7

3.4.3 Grace Period

You can enable and disable the grace period and configure its value. By default, the grace period is disabled. See Section 1.4, "Grace Period" for details. This setting applies to all incidents the HP Service Manager Connector processes.

3.4.4 Retry

You can enable and disable the Retry option and configure its interval value. By default, the Retry is disabled. See Section 1.5, "Retry" for details. This setting applies to all incidents the HP Service Manager Connector processes.

3.5 Working with Ticket Templates

When a connector instance is created in Enterprise Manager, all associated templates are available for ticket create/update operations. For Auto Ticketing, a notification method is created based on the ticket template selected while creating an incident rule. For manual ticketing, you select a ticket template while creating a ticket from the Enterprise Manager console, as shown in Figure 3-3.

Figure 3-3 Adding Conditional Actions

There are two default templates for each of the HP Service Manager Connectors. The default templates for the HP Service Manager 9 connector are:

- ServiceManager_9_Default_Incident_AutoClose.xsl

- ServiceManager_9_Default_Incident.xsl

Tip:
See Section 5.1, "Out-of-Box HP Service Manager Templates" for detailed information about these templates.

3.5.1 Adding Ticket Templates

If you want to create a custom template, you need to add ticket templates before they are recognized in Enterprise Manager. For each new custom template, run the following emctl register_template connector command as a user with execute privilege on emctl and the ability to read the ticket template:

$ORACLE_HOME/bin/emctl register_template connector
-t <template.xsl> -repos_pwd <reposPassword>
-cname <connectorName> -iname <internalName>
-tname <templateName> -ttype 2 [-d <description>]

Where —

<template.xsl> is the full path name of the template file.

<reposPassword> is the Enterprise Manager root (SYSMAN) password.

<connectorName> is the name of the connector instance installed in step 3 of Section 3.1, "Creating a Connector Instance".

<internalName> is the internal name to use for the template.

<templateName> is the name to display for the template.

<description> is the description of the template.

For example, the following command adds a new outbound template (newTemplate.xsl) for the connector instance with the HP Service Manager 9 Connector Instance:

emctl register_template connector
-t /home/oracle/custom_templates/template.xml
-repos_pwd sysmanpass
-cname "HPSM 9"
-iname "newTemplate"
-tname "New Template"
-ttype 2
-d "Demo template"

3.5.2 Viewing Template Code

To view template code, do the following:

1. Select the connector instance and go to the Configure Management Connector page.

2. Select the Template tab.

3. Click a template name or click View to view the XSLT code for the template.

The ticket templates are in XSLT format. A basic knowledge of XSLT is required to understand the code.

3.5.3 Removing a Template

To remove a template, do the following:

1. Select the connector instance and go to the Configure Management Connector page.

2. Select the Template tab.

3. Select the template and click Delete.

4. Click Yes to confirm the delete operation.

Important:
If the template you delete has an incident rule associated with it, ticketing will not function for this particular incident rule after the deletion.

3.5.4 Editing Templates

Note:
The Edit Template feature is available in Oracle Enterprise Manager Release 12.1.0.2 and later.

To edit an existing ticket template for Release 12.1.0.2 and later, do the following:

1. Select the connector instance and go to the Configure Management Connector page.

2. Select the Template tab.

3. Select the template and click Edit.

4. Edit the Description and Template Contents fields as needed, then click Save.

The ticket template is automatically registered. Saving the registered template updates it in the repository.

3.5.5 Restoring Templates

After you edit or customize a template, you can restore it to its previous default contents if needed by performing the following steps.

Note:
The Restore feature is available in Oracle Enterprise Manager Release 12.1.0.2 and later.
You can restore out-of-box templates that you have may edited or customized to their default values. You cannot restore new templates that you have created (using the emctl register_template command).

1. Select the connector instance and go to the Configure Management Connector page.

2. Select the Template tab.

3. Select the template and click Restore.

4. Click Yes in the confirmation page that appears in order to restore.

3.6 Configuring the HP Service Manager Web Console

The web console provides an alternative view for HP Service Manager. You can either use the HP Service Manager Client (which is a standalone application) or use the web application to manage incidents. Connector integration is possible for both of these methodologies.

If you want to have links to HP Service Manager tickets within Enterprise Manager, configuration changes are required in HP Service Manager.

To configure the HP Service Manager web console:

1. Locate the web.xml file under the following path and verify its configuration:

webtier-9.20\WEB-INF\web.xml

2. Make sure the serverHost parameter value is changed from local host to the fully-qualified name of the web tier server.

3. Make sure the querySecurity parameter is set to false as follows:

<init-param>
<param-name>querySecurity</param-name>
<param-value>false</param-value>

4. If any changes were made to the configuration file, you must restart the web application server for the changes to take effect.

Tip:
See the "Generating Web Tier URL Queries" section in the Service Manager client help contents for additional information.

Note:
The ticket URL generated requires parameters, such as the ticket ID, that need to be part of the URL string. This requires that the URL security be turned off. Your security team may need to evaluate if the risks outweigh the need to access the HP Service Manager ticket directly from Enterprise Manager using the ticket URL. HP Service Manager still requires user authentication when accessing the ticket through the URL.

3.7 Navigating Between Enterprise Manager and HP Service Manager

After you have configured the connector, you will want to access incidents from the Enterprise Manager and HP Service Manager consoles. The following sections explain how to switch from one console to the other.

3.7.1 Navigating from Enterprise Manager to HP Service Manager

To navigate from Enterprise Manager to HP Service Manager:

1. From the Enterprise Manager console Enterprise menu, select Monitoring, then Incident Manager.
The open incidents appear.

2. Click on the desired incident to display information for the incident.

3. Click on the ticket identifier listed to the right of the Ticket ID label in the Tracking section as shown in Figure 3-4.
You will be forwarded to the HP Service Manager Web console login page.

Figure 3-4 Incident Details in Enterprise Manager Console

4. Provide valid HP Service Manager account details.
The HP Service Manager incident details associated with this incident are displayed through the HP Service Manager web console as shown in Figure 3-5.

Note:
If you do not use the HP Service Manager Web console, uncheck the "Enable web console features" option discussed in Section 3.4.2, "Web Console Settings" so that the ticket ID is shown in plain text. Otherwise, it is displayed as a link that does not function.

Figure 3-5 Incident Details

3.7.2 Navigating from HP Service Manager to Enterprise Manager

To navigate from HP Service Manager to Enterprise Manager:

1. At the HP Service Manager client, open an incident from Enterprise Manager as shown in Figure 3-6.

2. Scroll down in the Description field to the URL: field and click on the URL listed.
This forwards you to the Enterprise Manager console login page. After you provide the Enterprise Manager user name and password, you are forwarded to the incident related to this ticket.

Note:

- The Enterprise Manager user whose name you specify should at least have View privileges on the target on which the alert was raised.

- On the HP Service Manager console, if the URL appears as text, you need to cut and paste the URL into the browser.

Figure 3-6 Alert Details in HP Service Manager Console

4 Creating Service Manager Tickets

You can create tickets automatically or manually. The following sections explain how to create both types:

- Automatically Creating a Ticket

- Manually Creating a Ticket

4.1 Automatically Creating a Ticket

To automatically create a ticket in HP Service Manager, you need to create an incident rule that references a template from the HP Service Manager connector.

To create an incident rule to automatically create a ticket in HP Service Manager:

1. From the Enterprise Manager console Setup menu, select Incidents, then Incident Rules.

2. Click Create Rule Set.
The Create Rule Set page appears.

3. Provide a Name and Description.

4. In the Targets tab, specify the targets for which you want tickets to be generated for events/incidents that Enterprise Manager detects.

5. Click the Rules tab.

- For events —
Click Create and select Incoming events or updates to events as a type of rule to create from the pop-up window, then click Continue.

The Create New Rule wizard appears. Follow the steps to create a rule. (Refer to the "Rules" section of the Using Incident Management chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide 12c .)

- For incidents —
Click Create and select Newly created incidents or updates to incidents as a type of rule to create from the pop-up window, then click Continue.

The Create New Rule wizard appears. Follow the steps to create a rule. (Refer to the "Rules" section of the Using Incident Management chapter in the Oracle Enterprise Manager Cloud Control Administrator's Guide 12c .)

6. While configuring the above rule in the Add Actions page:

- For events —
Enable the Create Incident check box. This makes the Create Ticket option visible. Now enable the Create Ticket check box, which displays lists to select the Connector Type, Connector Name, and Template Name as shown in Figure 4-1.

Figure 4-1 Event Add Actions

- For incidents —
Enable the Create Ticket check box, which displays lists to select the Connector Type, Connector Name, and Template Name as shown in Figure 4-2.

Figure 4-2 Incident Add Actions

7. After completing all of the wizard steps, click Save.

The following process occurs after you create the incident rule for your incidents:

- A request is sent to the HP Service Manager Connector when an incident is created due to an event that matches your rule.

- The ticket is created or updated in the HP Service Manager system.

- In Enterprise Manager, the incident annotation is updated. A comment is added to the event Detail page of the incident to indicate that a ticket was created or updated, along with the ticket ID, status, and ticket URL.

A ticket is updated if there is an existing active ticket for an incident. Figure 4-3 shows the ticket in the HP Service Manager console.

Figure 4-3 HP Service Manager Console Incident

4.2 Manually Creating a Ticket

To manually create a ticket:

1. After an incident occurs, go to its incident details page by clicking on the incident message in the Incident Manager console in Enterprise Manager. The incident details page for the incident should appear, as shown in Figure 4-4.

Figure 4-4 Incident Details Page

2. In the Tracking section, select More, then Create Ticket.
The Create Ticket pop-up appears, as shown in Figure 4-5. The Create Ticket option is only available if there is at least one ticketing connector configured, and no prior ticket exists for the same incident.

3. In the Create Ticket pop-up window, select a ticket template from the Template Name list, then click OK.

Figure 4-5 Create Ticket Pop-up Window

4.3 Post-creation Advisory Information

- If you have successfully created the ticket, the ticket ID appears in the Last Comment column in the Event Details for the incident. If the Web console settings are configured and enabled, the ticket ID appears as a link to the ticket page in Service Manager.

- If the default templates do not provide the desired mappings, you can create custom templates to map data as desired. See Section 5.3, "Customizing Ticket Templates" for additional information.

5 Using Out-of-Box Templates

This chapter provides details on the out-of-box ticket templates shipped with the HP Service Manager Connector based on the out-of-box Service Manager IncidentManagement WSDL. The ticket templates specify the mappings between Enterprise Manager incident attributes and HP Service Manager ticket attributes.

This chapter covers the following topics:

- Out-of-Box HP Service Manager Templates

- Reading and Mapping Ticket Templates

- Customizing Ticket Templates

- Exporting the Ticketing Template Files

- Modifying Ticket Templates

- Custom Template Examples

5.1 Out-of-Box HP Service Manager Templates

All out-of-box templates cause the following actions to occur when you create or update a ticket for an incident:

- Write Enterprise Manager incident information to the ticket description.

- Set the ticket summary based on the incident message.

- Add an entry to the Journal Update that shows the incident details. This provides a trail of the changes that have occurred to the incident.

- Sets the ticket severity based on the severity of the incident in Enterprise Manager.

The out-of-box templates are:

- Service_Manager_9_Default_Incident.xsl
This templates creates, updates, or reopens a Service Manager ticket using the default field mapping. This template does not close the ticket when the event severity value becomes Clear.

- Service_Manager_9_Default_Incident_AutoClose.xsl
This template creates, updates, or reopens a Service Manager ticket using the default field mapping. This template sets the ticket status to Closed when the incident severity value becomes Clear.

5.2 Reading and Mapping Ticket Templates

This section provides detailed mapping information for the default ticket templates described above. The mappings are based on the out-of-box IncidentManagement WSDL for the HP Service Manager Web Service.

Each template is capable of handling create and update requests. The incident TicketID field determines how it is mapped. If the TicketID is empty, it is mapped to the Service Manager create request format. Otherwise, it is mapped to an update request format. The following sub-sections identify the create and update mappings for each template.

5.2.1 Service_Manager_9_Default_Incident.xsl - Create

Table 5–1 lists the fields and values that this template maps for a create operation. All references to the incident refer to the Enterprise Manager incident.

Table 5-1 HP Service Manager 9 Default Incident Create Field Names and Values

Service Manager Field Name

Value

Urgency

Set the severity based on the incident severity. See Section 5.2.6, "Severity Mapping" for details.

Area

Hard-coded to "failure".

Subarea

Hard-coded to "error message".

Product Type

Hard-coded to "applications".

Problem Type

Hard-coded to "incident".

Assignment Group

Hard-coded to "Service Desk".

Impact

Hard-coded to "1".

Description

Set to the formatted contents of the incident as specified in Section 5.2.5, "Formatted Enterprise Manager Incident Contents".

Title

Set to the incident Summary.

Journal Updates

Set to the formatted contents of the incident as specified in Section 5.2.5, "Formatted Enterprise Manager Incident Contents".

Oracle Connector ID

Set to the incident ConnectorGUID.

5.2.2 Service_Manager_9_Default_Incident.xsl - Update

Table 5–2 lists the fields and values that this template maps for an update operation. All references to the incident refer to the Enterprise Manager incident.

Table 5-2 HP Service Manager 9 Default Incident Update Field Names and Values

Service Manager Field Name

Value

Incident ID

Set to the incident TicketID.

Description

Set to the formatted contents of the incident as specified in Section 5.2.5, "Formatted Enterprise Manager Incident Contents".

Title

Set to the incident Summary.

Status

Set to "Open" if the incident ReopenTicket field is set to "Yes."

Alert Status

Set to "reopen" if the incident ReopenTicket field is set to "Yes."

Journal Updates

Set to the formatted contents of the incident as specified in Section 5.2.5, "Formatted Enterprise Manager Incident Contents".

5.2.3 Service_Manager_9_Default_Incident_AutoClose.xsl - Create

The field mappings for this template are identical to the mappings specified in Section 5.2.1, "Service_Manager_9_Default_Incident.xsl - Create".

5.2.4 Service Manager_9_Default_Incident_AutoClose.xsl - Update

Table 5–3 lists the fields and values that this template maps for an update operation. All references to the incident refer to the Enterprise Manager incident.

Table 5-3 HP Service Manager 9 Default Incident AutoClose Update Field Names and Values

Service Manager Field Name

Value

Incident ID

Set to the incident TicketID.

Description

Set to the formatted contents of the incident as specified in Section 5.2.5, "Formatted Enterprise Manager Incident Contents".

Title

Set to the incident Summary.

Status

Set to "Open" if the incident ReopenTicket field is set to "Yes."

Set to "Closed" if the incident severity is "Clear."

Alert Status

Set to "reopen" if the incident ReopenTicket field is set to "Yes."

Set to "closed" if the incident severity is "Clear."

Resolution Fix Type

Set to "permanent" if the incident severity is "Clear."

Closure Code

Set to "User Closure" if the incident severity is "Clear."

Solution

Set to "The alert was resolved in Oracle Enterprise Manager" if the incident severity is "Clear."

Journal Updates

Set to the formatted contents of the incident as specified in Section 5.2.5, "Formatted Enterprise Manager Incident Contents".

5.2.5 Formatted Enterprise Manager Incident Contents

shows the format used by the templates for the Description and JournalUpdates fields.

- Text delimited by angle brackets (< and >) designates an Enterprise Manager Incident field name that will be replaced by the actual field contents.

- Lines marked with double asterisks indicate they will only be present if the designated incident field contains data.

- The Notes section after the format contains information about some of the fields.

Example 5-1 Formatted Incident Contents

EM User: <NotificationRuleOwner>
.
Incident Information:
.
Source Name: <SourceObjInfo/ObjName>
Source Owner: <SourceObjInfo/ObjOwner>**
Source Type: <SourceObjInfo/SourceObjType>
Source SubType: <SourceObjInfo/SourceObjSubType>
Target Name: <TargetInfo/TargetName>
Target Type: <TargetInfo/TargetType>
Target Type Label: <TargetInfo/TargetTypeLabel>
Target URL: <TargetInfo/TargetURL>
.
Target Properties:**
<TargetProperty/Name>: <TargetProperty/Value>**
.
Severity: <Severity>
Priority: <Priority>
CreationDate: <CreationDate>
LastUpdatedDate: <LastUpdatedDate>
Owner: <Owner>
Notification Rule: <NotificationRuleName>**
URL: <IncidentURL>
.
EM Incident Status: <ResolutionState>
EM Acknowledge: <Acknowledge>
EM Auto Close: <AutoClose>
EM Escalation Level: <EscalationLevel>
<AdditionalDetails/Name>: <AdditionalDetails/Value>**

Example 5-1 Notes

- EM User is set to the incident rule set owner when the ticket is created through auto-ticketing, and is the Enterprise Manager log-in user when the ticket is created through manual-ticketing.

- The Target Properties section is only present if the incident contains target property values. Listed below are a couple of sample target property name/value pairs:
Line of business: Finance

Owner: Finance-DB Team

- CreationDate is set to the date the incident was created in Enterprise Manager.

- Owner is set to the incident owner in Enterprise Manager.

- URL is set to the URL of the incident details page in Enterprise Manager. The URL is set up as a link that can be clicked on to view the incident in Enterprise Manager.

5.2.6 Severity Mapping

The Service Manager ticket severity is set based on the Enterprise Manager incident severity value. Table 5–4 shows the values used when creating the ticket in Service Manager.

Table 5-4 Ticket Severity Mappings

When the incident severity is …

Set the ticket severity to …

Fatal

1 (Critical)

Critical

1 (Critical)

Warning

3 (Average)

Minor Warning/Advisory

4 (Low)

Informational

4 (Low)

5.3 Customizing Ticket Templates

If the out-of-box ticket templates do not satisfy your requirements, you can create custom templates tailored to your environment. Templates are XSLT files, so you must have a good understanding of XSLT transformations to create custom templates. To do this, Oracle recommends that you use one of the existing templates as the base template.

To create a custom template:

1. Export the default template XSLT files from Enterprise Manager to use as a baseline. Follow the instructions in Section 5.4, "Exporting the Ticketing Template Files" to obtain copies of the default template files.

2. Review Section 5.1 and Section 5.2 to understand the default mappings. Determine which file you want to use as a baseline and what mapping changes you want to make. Copy the baseline file to a new file with a different name.

3. Make the desired mapping changes to the new template file. See Section 5.5, "Modifying Ticket Templates"for guidance on mapping changes.

4. Register the new template with Enterprise Manager as specified in Section 3.5.1, "Adding Ticket Templates" .

See Section 5.6, "Custom Template Examples" for examples of how to create a custom template.

5.4 Exporting the Ticketing Template Files

The connector installation .jar file is included in the Self Update archive that was installed in Section 2.1, "Installing the Connector".

To extract the installation file:

1. Determine the command required to export the adapter installation file. To do this, perform the following steps:

1. From the Setup menu in the Enterprise Manager console, select Extensibility, then Self Update.

2. Click on the Management Connector link.

3. Click on the HP Service Manager 9 connector and then select Export from the Actions list.
A pop-up window appears with the command required to export the file. Figure 5-1 shows an example of the window.

Figure 5-1 Export Command Example

2. Open a command window on the Management Server host system and navigate to a temporary directory where you can copy the file.

3. Log into EM CLI using the following command. You will be asked to provide the password information for the sysman account.

emcli login -username=sysman

4. Run the EM CLI export_update command from your system, changing <dirname> to the full path of the temporary directory.
This creates a .zip file. The file name is comprised of the id value specified in the export_update command with a .zip extension. In the example command in Figure 5-1, the .zip file name would be:

E9F684312AE7A18E98340715D079E58D.zip

5. Extract the adapter installation .jar file from the .zip file using the following command:

unzip *.zip archives/*connector.jar

6. Extract the templates from the connector .jar file using the following command:

$JAVA_HOME/bin/jar xf archives/*.jar templates

Note:
If the system where the connector file is located does not have the JDK installed, you cannot extract the .jar file contents. You must copy the .jar file to a system that has the JDK installed and transfer the template files after they have been extracted.

5.5 Modifying Ticket Templates

A template is an XSLT file that transforms an input XML format to an output XML format. To make the mapping changes, you need to understand the input XML format being transformed, and the output XML the template generates. The input document is the XML document that contains the Enterprise Manager incident information. The output document is the request being sent to the HP Service Manager web service. The output XML document must conform to the data format specified in the Service Manager IncidentManagement WSDL.

Appendix C contains details on the format of the incident data Enterprise Manager generates. Appendix D contains details on the XML format required by the out-of-box IncidentManagement Service Manager web service. Service Manager web services may be customized, so the format used in your environment could be significantly different.

To modify the custom template file:

1. Review Appendix D to identify the names of the fields in Service Manager that you are planning to modify. The order of the fields is important, so if you need to add new fields, make sure to note where the field goes.

2. If you are planning on using data from the incident, review Appendix C to identify the field(s) you want to use in the mapping. Appendix E contains sample transactions that could be very helpful in identifying what data is present in the XML document from Enterprise Manager.

3. Open the custom template file in a text editor or a utility that you can use to build XSLT files.

4. Make the necessary changes to the custom template file and save it.

5. Unless the change is very simple, you should test the changes that you have made using the sample data from Appendix E. This requires a utility that performs XSLT translations.

5.6 Custom Template Examples

This section provides walk-through examples of what is required to create custom templates. The first example is a simple case of changing values for fields that are already specified in the default templates. The second example is more involved, and includes populating fields that are not already in the default templates.

5.6.1 Example 1

In this example, the customer has determined that the default mappings do not function for their environment. They have created a new assignment group named "Tier 1 Support" that should handle all incidents that Enterprise Manager reports. They are running version 9 in their environment and would like to close the incidents in Service Manager after the incidents have cleared in Enterprise Manager. They have also created a temporary directory on the OMS server system at /home/oracle/custom_templates to hold the templates.

To create a custom template that handles the customer's requirements:

1. Navigate to the Management Connector Updates page and export the HPSM 9 Connector.

2. Copy the first EM CLI command listed in the Export Steps window for later use:

emcli export_update -id=DD4E9161C5E7129F9641447FB4F0497B -omslocal -dir=<dirname>

3. Open a command window on the OMS server system and change the working directory to the temporary directory:

cd /home/oracle/custom_templates

4. Log into EM CLI:

emcli login -username=sysman

5. Run the EM CLI command from step 1 to export the .zip file to the temporary directory.

emcli export_update -id=DD4E9161C5E7129F9641447FB4F0497B -omslocal -dir=/home/oracle/connector_templates

6. Extract the connector .jar file from the .zip file:

unzip *.zip archives/*connector.jar

7. Extract the template files from the .jar file:

$JAVA_HOME/bin/jar xf archives/*.jar templates

8. Copy the default template to a custom template file for modification:

cd templates

cp ServiceManager_9_Default_Incident_AutoClose.xsl Tier1_Support_AutoClose.xsl

9. Open the custom template file with a text editor and make the modifications shown below to the AssignmentGroup node.
Before changes —

<m:AssignmentGroup>Service Desk</m:AssignmentGroup>

After changes —

<m:AssignmentGroup>Tier1 Support</m:AssignmentGroup>

Since this is a trivial change, you can skip testing.

10. At the OMS server system, run the following command to register your new custom template:

emctl register_template connector
-t /home/oracle/custom_templates/templates/Tier1_Support_AutoClose.xsl
-repos_pwd sysmanpass
-cname "HPSM 9"
-iname "Tier1SupportAutoClose"
-tname "Tier1 Support AutoClose"
-ttype 2
-d "Template to set assignment group to Tier1 Support"

5.6.2 Example 2

In this example, the customer would like to populate the following additional fields:

- Affected Item — This field will be populated by the Target Host information from the Target Properties.

- Location — This field will be populated by the Location information from the Target Properties.

- Target URL — This a new custom field that was added to their web service to hold the Target URL from the Enterprise Manager incident.

They are running version 9 in their environment, and would like to close the incidents in Service Manager after the incidents have cleared in Enterprise Manager. They have also created a temporary directory on the OMS server system at /home/oracle/custom_templates to hold the templates.

To create a custom template that handles their requirements:

1. Navigate to the Management Connector Updates page and export the HPSM 9 Connector.

2. Copy the first EM CLI command listed in the Export Steps window for later use:

emcli export_update -id=C5289206C5A5A84AF82C49821C8F2931 -omslocal -dir=<dirname>

3. Open a command window on the OMS server system and change the working directory to the temporary directory:

cd /home/oracle/custom_templates

4. Log into EM CLI:

emcli login -username=sysman

5. Run the EM CLI command from step 1 to export the .zip file to the temporary directory.

emcli export_update -id=C5289206C5A5A84AF82C49821C8F2931 -omslocal -dir=/home/oracle/connector_templates

6. Extract the connector .jar file from the .zip file:

unzip *.zip archives/*connector.jar

7. Extract the template files from the .jar file:

$JAVA_HOME/bin/jar xf archives/*.jar templates

8. Copy the default template to a custom template file for modification:

cd templates

cp ServiceManager_9_Default_Incident_AutoClose.xsl Target_Info_AutoClose.xsl

9. Open the custom template file with a text editor and make the modifications shown below. The changes are shown in bold. Note that the new fields were added in the correct sequence as defined in the WSDL.
Before changes —

<m:AssignmentGroup>Service Desk</m:AssignmentGroup>

. . .

<m:Impact>1</m:Impact>

. . .

<m:OracleConnectorId><xsl:value-of select="ns0:ConnectorGUID"/></m:OracleConnectorId>

After changes —

<m:AssignmentGroup>Service Desk</m:PrimaryAssignmentGroup>
<xsl:for-each select="ns0:SystemAttributes/ns0:SourceInfo/ns0:TargetInfo/ns0:TargetProperty">
<xsl:if test="./ns0:Name = 'Target_Host'">
<m:AffectedItem><xsl:value-of select="./ns0:Value"/></m:AffectedItem>
</xsl:if>
</xsl:for-each>

. . .

<m:Impact>1</m:Impact>
<xsl:for-each select="ns0:SystemAttributes/ns0:SourceInfo/ns0:TargetInfo/ns0:TargetProperty">
<xsl:if test="./ns0:Name = 'Location'">
<m:Location><xsl:value-of select="./ns0:Value"/></m:Location>
</xsl:if>
</xsl:for-each>

. . .

<m:OracleConnectorId><xsl:value-of select="ns0:ConnectorGUID"/></m:OracleConnectorId>
<m:TargetURL><xsl:value-of
select="ns0:SystemAttributes/ns0:SourceInfo/ns0:TargetInfo/ns0:TargetURL"/></m:TargetURL>

10. To set up for testing, create the create.xml file and open the file in a text editor.

11. Copy the contents of the XML document in the "Create Example" section of Appendix E into the create.xml file and save it.

12. Test the new template using a utility that performs XSLT translations using the create.xml file as the input XML document.

13. Examine the output XML document and verify that the results are correct.

Note:
You can also use an XML client to send the XML output document to the Management Server web service to verify that it is a format accepted by Service Manager.

14. If you encounter problems with the XML document, make any necessary corrections and repeat steps 12 and 13.

15. At the OMS server system, run the following command to register your new custom template:

emctl register_template connector
-t /home/oracle/custom_templates/templates/Target_Info_AutoClose.xsl
-repos_pwd sysmanpass
-cname "HPSM 9"
-iname "TargetInfoAutoClose"
-tname "Target Info AutoClose"
-ttype 2
-d "Template to set target fields"

6 Customizing Support Ticketing Inbound Operations

Ticketing Inbound is a new optional feature added in Enterprise Manager 12c. This feature synchronizes the ticket status between Service Manager and Enterprise Manager. This feature requires the addition of a new field to the HP Service Manager incident database to contain the Enterprise Manager connector identifier. It also requires the setup of a Java script in HP Service Manager that is called to send the status information to Enterprise Manager whenever a status change occurs. You can skip this chapter if you choose not to implement this feature.

When a ticket or incident Enterprise Manager creates is updated manually at the Service Manager console, the new ticket status is updated in Enterprise Manager. The update at the Service Manager console triggers a Java script that calls the EM CLI utility to send the new status to Enterprise Manager.

This chapter provides the following procedures to set up the ticketing inbound feature:

- Adding a Custom Field to HP Service Manager

- Setting Up EM CLI

- Exporting the Notification Script Files

- Setting Up the Notification Script

- Uninstall Customization to HP Service Manager for Support Ticket Inbound Operations

- Uninstalling EM CLI

6.1 Adding a Custom Field to HP Service Manager

This section provides instructions to add a custom field to the HP Service Manager incident database to contain the Enterprise Manager connector identifier. The identifier must be stored with the incident, because it is a required value that must be supplied when status updates are sent to Enterprise Manager.

To add the custom field:

1. Log in to the HP Service Manager client using an account that has Administrative permissions.

2. Add the new custom field to the HP Service Manager database to contain the Enterprise Manager connector ID as follows:

1. Expand Menu Navigation, then Tailoring in the System Navigator pane.

2. Double-click on Database Dictionary.
The Database Dictionary panel appears.

3. Enter a File Name of probsummary and click Search.
A form with the probsummary table information appears, as shown in Figure 6-1.

Figure 6-1 probsummary Information

4. Click on the line with a Name of descriptor and a Type of structure.

5. Click on New Field/Key.
The Add Field window appears.

6. Enter a Name of oracle.connector.id and a type of character, then click Add.

7. Scroll down to the bottom of the list of fields and click on the row with the name of oracle.connector.id.

8. Click on Edit Field/Key. The field edit window appears, as shown in Figure 6-2.

Figure 6-2 Update Field Window

9. Enter ORACLE_CONN_ID in the SQL Name field, VARCHAR(32) in the SQL Type field, and m2 in the SQL Table field, then click OK.

10. Click OK on the main panel.
The ALTER TABLE database SQL statement appears, and you are asked whether Service Manager should automatically apply the change, or whether you want to apply it manually.

11. Click SM Alters.
After a period of time, a message states that the record has been updated in the dbdict file.

3. Modify the web service to include the new database field as follows:

1. Expand Menu Navigation, then Tailoring, then Web Services in the System Navigator pane.

2. Double-click on WSDL Configuration.
The External Access Definition panel appears.

3. Enter probsummary in the Name field and click Search.
The record for probsummary will be loaded as shown in Figure 6-3.

Figure 6-3 External Access Definition Panel

4. Click on the Fields tab and scroll to the bottom of the list of fields.

5. Click on the Field column of the first empty row and select oracle.connector.id from the list.

6. Click on the Caption column on the same row and enter OracleConnectorId, as shown in Figure 6-4, then click OK.

Figure 6-4 Oracle Connector ID

6.2 Setting Up EM CLI

Install the Enterprise Manager EM CLI Client on the Service Manager server system. The EM CLI Client needs to be able to communicate with your OMS.

To install the Enterprise Manager EM CLI Client:

1. Log into the Enterprise Manager console.

2. From the Setup menu, select Command Line Interface.

3. Click the Download the EM CLI kit to your workstation link, and download the emclikit.jar file to the local system.

4. Transfer the jar file to the Service Manager server system.

5. At the HP Service Manager server, set your JAVA_HOME environment variable and ensure that it is part of your PATH. You must be running Java 1.6.0_25 or greater. For example:

setenv JAVA_HOME /usr/local/packages/j2sdk1.6.0_2
setenv PATH $JAVA_HOME/bin:$PATH

6. Install the EM CLI Client on the Service Manager server. You can install the client portion of EM CLI in any directory using the following command, where <emcli_dir> is the installation directory:

java -jar emclikit.jar client -install_dir=<emcli_dir>

7. Open a window using the account that runs the Service Manager Server. On a Windows system, this should be the System account.
To open a window running the System account, run the following command with <time> being 1 minute in the future. At the time specified, a window opens at the system console running under the context of the System account.

at <time> /interactive cmd.exe

8. Run the following command to configure the EM CLI Client to connect to OMS, where <hostname> is the host name or IP address where the OMS server is located, and <sysman_pwd> is the password for the sysman account in OMS:

<emcli_dir>\emcli setup -url=https://<hostname>:7801/em -username=<em_super_user> -password=<sysman_pwd>

9. Run the following command to synchronize the EM CLI Client with OMS:

<emcli_dir>\emcli sync

Note:
EMCLI must be installed on the Service Manager server in order to communicate with your OMS.

6.3 Exporting the Notification Script Files

The notification script files are included in the Self Update archive that was installed in Section 2.1, "Installing the Connector".

To extract the script files:

1. Determine the command required to export the archive files. To do this, perform the following steps:

1. From the Setup menu of the Enterprise manager console, select Extensibility, then Self Update.

2. Click on the Management Connector link in the Type column.
The HP Service Manager connectors appear in the list with a status of Applied.

3. Click on the HP Service Manager connector, then select Export from the Actions list.
A pop-up window, like the example shown in Figure 6-5, appears with the command required to export the file.

Figure 6-5 Export Command Example

2. Open a command window on the Management Server host system and navigate to a temporary directory where you can copy and unzip the file.

3. Log into EM CLI using the following command. You will be asked to provide the password information for the sysman account.

emcli login -username=sysman

4. Run the EM CLI export_update command from your system, changing <dirname> to the full path of the temporary directory.
This action creates a zip file. The file name is comprised of the id value you specify in the export_update command with a .zip extension. In the example command in Figure 6-5, the zip file name would be:

E9F684312AE7A18E98340715D079E58D.zip

5. Extract the adapter installation jar file from the zip file using the following command:

unzip *.zip archives/OracleOMSPost.js

6.4 Setting Up the Notification Script

This section provides the steps required to configure HP Service Manager to call the notification script.

To configure HP Service Manager to call the notification script:

1. Log into the HP Service Manager client with an account that has Administrative permissions.

2. Create a Script Library that generates the parameters for the EM CLI call by performing the following sub-steps:

1. Expand Menu Navigation, then Tailoring in the System Navigator pane.

2. Double-click on Script Library.
The Script Library panel appears.

3. Enter a Name of OracleServices and a Package of OracleScripts.

4. Copy the contents of the OracleOMSPost.js file from Section 6.3 into the script panel. Figure 6-6 shows the Script Library panel after the fields have been specified.

5. Change the value of the username on line 6 from oms_user to the username that Enterprise Manager will use to access the Service Manager web service. See Service Manager Username in Section 3.4.1, "Connection Settings" for more information.

6. Click Add.

Figure 6-6 Script Library Panel

3. Create a Script Panel that calls the Script Library by performing the following sub-steps:

1. Double-click on Scripts in the System Navigator panel.
The Script Panel Definition panel appears.

2. Enter a script name of OracleScript.

3. Click on the Pre RAD Statements tab.

4. Click on the first line and enter the following text, where <emcli_dir> is the path where the EM CLI tool was installed:

$L.command="<emcli_dir>\\emcli.bat;"+jscall("OracleServices.OracleOMSPost", $script)

Note:
Backslashes in the path must be entered as double backslashes. For example, C:\tools\em\emcli.bat would be entered as C:\\tools\\em\\emcli.bat.

Figure 6-7 shows the Script Library panel after the fields have been specified.

5. Click on the RAD tab and set Application to us.launch.external.

6. Click on the first line in the Names column and enter name.

7. Click on the first line in the Values column and enter $L.command.

8. Click Add to create the Script Panel.

Figure 6-7 Script Panel Definition

4. Perform the following sub-steps to update the Format Control to invoke the script upon creating or updating a ticket:

1. Double-click on Format Control in the System Navigator panel.
The Search Format Control Records panel appears.

2. Enter probsummary in the Name field and click Search.
The Format Control: probsummary panel appears.

3. Click on the line where the Name is probsummary.

4. Click Subroutines to open the Subroutines tab.
One or more subroutines may already be defined.

5. Scroll down the screen to the last empty entry and enter the following data:

- Set Add to true.

- Set Upd to true.

- Set Names to file on line 1, and name on line 2.

- Set Values to $file on line 1, and OracleScript on line 2.

Figure 6-8 shows the Format Control panel after you have specified the fields.

6. Click Save.

Figure 6-8 Format Control Panel

6.5 Uninstall Customization to HP Service Manager for Support Ticket Inbound Operations

This section provides the steps required to remove the changes made to HP Service Manager to allow for ticket inbound operations.

6.5.1 Remove Calls to the Notification Script

Follow the steps below to remove calls to the notification script:

1. Log in to the HP Service Manager client with an account that has Administrative permissions.

2. Expand Menu Navigation, then Tailoring in the System Navigator pane.

3. Double-click on Script Library.

4. Click Search to view all Scripts in the Script Library.

5. Find and select OracleServices, then click Delete, and Yes to confirm.

6. Double-click on Scripts in the System Navigator panel.

7. Click Search to view all Scripts available.

8. Find and select OracleScript, click Delete, then Yes to confirm.

9. Double-click on Format Control in the System Navigator panel.

10. Enter probsummary in the Name field and click Search.

11. Click on the line where the Name is probsummary.

12. Click Subroutines to open the Subroutines tab.

13. Click Delete, then Yes to confirm.

6.5.2 Remove Custom Field Added for Script Operation

Follow the steps below to remove custom field added for script operation:

1. Log in to the HP Service Manager client using an account that has Administrative permissions.

2. Expand Menu Navigation, then Tailoring in the System Navigator pane.

3. Double-click on Database Dictionary.
The Database Dictionary panel appears.

4. Enter a File Name of probsummary and click Search.

5. Scroll down to the bottom of the list of fields and click on the row with the name of oracle.connector.id.

6. Click Delete Dbdict Record, and select Yes to confirm.

7. Expand Menu Navigation, then Tailoring, then Web Services in the System Navigator pane.

8. Double-click WSDL Configuration.

9. Enter probsummary in the Name field and click Search.

10. Click the Fields tab and scroll to the bottom of the list of fields.

11. Click the Field column of the first empty row and remove oracle.connector.id.

12. Click the Caption column on the same row and remove OracleConnectorId, then click OK.

6.6 Uninstalling EM CLI

To uninstall the Enterprise Manager command line interface (emcli), perform the following steps:

1. Navigate to the emcli installation directory.

2. Delete the emcli directory and all sub-directories from the system.

A Enabling SSL for HTTPS

This appendix provides the needed instructions if you choose HTTPS as the protocol to establish a connection between HP Service Manager and Enterprise Manager.

A.1 Generating and Importing a Certificate Request

Do the following to generate and then import the certificate:

1. Generate a certificate request file for HP Service Manager and send it to the Certificate authority, such as VeriSign.
The host name or IP address specified in the request must exactly match the host name or IP address that the connector will use.

Note:
The certificate request file is dependent on the Web server that HP Service Manager uses.

2. After you get the certificate, import it to the Web server that HP Service Manager uses. The import mechanism varies depending on the Web server that the HP Service Manager Help Desk uses.

A.2 Installing and Configuring SSL

For information about installing and configuring SSL, see the Service Manager 9 Installation Guide.

A.3 Importing the Adapter Certificate into Enterprise Manager

To import the adapter SSL certificate into the Enterprise Manager keystore:

1. At the Service Manager web server system, extract the SSL certificate from the keystore into a certificate file using the RFC 1421 format.
If you use the Java keytool -export_cert command to extract the certificate, the -rfc option stores the certificate in the correct format.

2. Transfer the certificate file to the system where Enterprise Manager is installed.

3. Append the contents of the certificate file to:

$INSTANCE_HOME/sysman/config/b64LocalCertificate.txt

- Only append the following lines to the b64LocalCertificate.txt file (that is, do not include blank lines or comments or any other special characters):

-----BEGIN CERTIFICATE-----
<<<Certificate in Base64 format>>>
-----END CERTIFICATE-----

4. Restart the OMS by entering the following commands:

emctl stop oms
emctl start oms

Note:
Do not run the emctl secure oms/agent command after adding the external certificate to the b64LocalCertificate.txt file. If you run the emctl secure command later, repeat steps 3 and 4 to make sure the external certificate exists in the b64certificate.txt file.

B Preventing HP Service Manager Update Issues

HP Service Manager 9 can cause update issues due to the method of locking for incidents. When either the Service Manager Thick or Web Client opens an incident in Service Manager for editing, a lock is placed on the incident that prohibits any updates to the incident record until it is released.

It is best practice for Help Desk administrators not to open the incident in edit mode to view the incident. If they need to edit the incident, they should minimize the time the incident is in edit mode, so if any updates are processed by the Enterprise Manager Connector Framework, the updates will be successful.

C Enterprise Manager Incident Format

Templates translate the XML format of Enterprise Manager incidents to the XML format required for the end-point application's web service. To create custom templates, you need to understand the format of both sides so that you know how to map the data. This appendix provides detailed information on the format of the XML document that contains incident information from Enterprise Manager.

A schema file defines the structure of an XML document. The EMIncident.xsd schema file defines the main structure of the incident data. This file also imports structure information from other schema files. The following examples provide information from the schema files that define the EMIncident XML format.

Examples in this appendix are as follows:

- EMIncident.xsd File

- connectorCommon.xsd File

- EMEvent.xsd File

- externalEvent.xsd File

Example C-1 EMIncident.xsd File

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://xmlns.oracle.com/sysman/connector"
targetNamespace="http://xmlns.oracle.com/sysman/connector"
elementFormDefault="qualified">
<xsd:include schemaLocation="connectorCommon.xsd"/>
<xsd:include schemaLocation="EMEvent.xsd"/>
<xsd:element name="EMIncident">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ConnectorGUID" type="xsd:string"/>
<xsd:element name="TicketID" type="xsd:string" minOccurs="0"/>
<xsd:element name="HDUser" type="xsd:string" minOccurs="0"/>
<xsd:element name="NotificationRuleOwner" type="xsd:string"/>
<xsd:element name="NotificationRuleName" type="xsd:string"/>
<xsd:element name="ReopenTicket" type="xsd:string" minOccurs="0"/>
<xsd:element name="ConnectorVariable" type="VariableType"
minOccurs="0" maxOccurs="50"/>
<xsd:element name="Property" type="PropertyType" minOccurs="0"
maxOccurs="50"/>
<xsd:element name="SystemAttributes"
type="IncidentSystemAttributesType"/>
<xsd:element name="HasEMEvent" type="xsd:boolean" minOccurs="1"               maxOccurs="1"/>
<xsd:element name="EMEvent" type="EMEventType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="IncidentSystemAttributesType">
<xsd:sequence>
<xsd:element name="IncidentID" type="xsd:string"/>
<xsd:element name="SourceInfo" type="SourceInfoType"
maxOccurs="unbounded"/>
<xsd:element name="IncidentURL" type="xsd:string"/>
<xsd:element name="AutoClose" type="xsd:boolean"/>
<xsd:element name="TicketStatus" type="xsd:string" minOccurs="0"/>
<xsd:element name="Owner" type="xsd:string"/>
<xsd:element name="ResolutionState" type="xsd:string"/>
<xsd:element name="Acknowledge" type="xsd:boolean"/>
<xsd:element name="Escalated" type="xsd:boolean"/>
<xsd:element name="EscalationLevel" type="xsd:string"/>
<xsd:element name="Priority" type="xsd:string"/>
<xsd:element name="Summary" type="xsd:string"/>
<xsd:element name="CreationDate" type="xsd:dateTime"/>
<xsd:element name="LastUpdatedDate" type="xsd:dateTime"/>
<xsd:element name="Category" type="xsd:string" minOccurs="0"
maxOccurs="50"/>
<xsd:element name="LastModifiedBy" type="xsd:string"/>
<xsd:element name="Severity" type="xsd:string"/>
<xsd:element name="SeverityCode" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Example C-2 connectorCommon.xsd File

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://xmlns.oracle.com/sysman/connector"
targetNamespace="http://xmlns.oracle.com/sysman/connector"
elementFormDefault="qualified">
<xsd:include schemaLocation="externalEvent.xsd"/>
<xsd:complexType name="SourceInfoType">
<xsd:annotation>
<xsd:documentation>
This section defines a complext type for Source Information.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="SourceObjInfo" type="SourceObjInfoType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
This element defines the data structure for the source object, the                EM subsystem or component, that raises an EM event or an incident.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TargetInfo" type="TargetInfoType" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
The element defines the data structure for an EM target as related
to the connector framework.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="SourceObjInfoType">
<xsd:annotation>
<xsd:documentation>
This section defines a complex type for Source Object Information.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="ObjID" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The unique ID to identify the source object.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ObjName" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The name of the source object.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="ObjOwner" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
The owner of the source object.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SourceObjType" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The type of the source object.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="SourceObjSubType" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
The subtype of the source object.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="TargetInfoType">
<xsd:annotation>
<xsd:documentation>
This section defines a complex type for target information.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="TargetGUID" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A unique GUID for the target.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TargetName" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Name of the target.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TargetType" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Type of the target.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TargetTypeLabel" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The display label of the target type.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TargetURL" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The URL of the target.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="TargetProperty" type="PropertyType" minOccurs="0"
maxOccurs="50">
<xsd:annotation>
<xsd:documentation>
An optional list of properties for the target.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="PropertyType">
<xsd:annotation>
<xsd:documentation>
This section defines a complex type for a property attribute.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Name" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A string name defining a property attribute.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Value" type="xsd:string" nillable="true">
<xsd:annotation>
<xsd:documentation>
A non-null string value.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="VariableType">
<xsd:annotation>
<xsd:documentation>
This section defines a complex type for a general variable.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="VariableName" type="StringStrictT32">
<xsd:annotation>
<xsd:documentation>
Name of the variable. It has to be a string containing 1 or upto
32 upper case or lower case letters or numbers.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="VariableValue" type="StringT2048">
<xsd:annotation>
<xsd:documentation>
Value of the variable. It has to be a string containing 1 or up to
2048 characters.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="GetAlertsResponse">
<xsd:annotation>
<xsd:documentation>
This section defines a complex type for responses to a getAlerts            request.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Alert" minOccurs="0" maxOccurs="200">
<xsd:annotation>
<xsd:documentation>
The individual alerts contained in the response. A response may                  have up to 200 alerts.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="ExternalEvent">
<xsd:annotation>
<xsd:documentation>
Details of the external event in the alert, as defined in
ExternalEvent.xsd.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="InstanceVariable" type="VariableType"
minOccurs="0" maxOccurs="50">
<xsd:annotation>
<xsd:documentation>
A list of instance variables for the alert.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ConnectorVariablesType">
<xsd:annotation>
<xsd:documentation>
This section defines a complex type for connector variables. An element
of type ConnectorVariablesType may have up to 50 connector variables, as
defined next.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="ConnectorVariable" type="VariableType" minOccurs="0"
maxOccurs="50">
<xsd:annotation>
<xsd:documentation>
A connector varialbe as a name/value pair.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="StringT64">
<xsd:annotation>
<xsd:documentation>
This section defines a simple type for a String with maximum length of
64 bytes.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="64"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="StringT128">
<xsd:annotation>
<xsd:documentation>
This section defines a simple type for a String with maximum length of
128 bytes.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="128"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="StringT256">
<xsd:annotation>
<xsd:documentation>
This section defines a simple type for a String with maximum length of
256 bytes.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="256"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="StringT512">
<xsd:annotation>
<xsd:documentation>
This section defines a simple type for a String with maximum length of
512 bytes.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="512"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="StringT2048">
<xsd:annotation>
<xsd:documentation>
This section defines a simple type for a String with maximum length of
2048 bytes.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="2048"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="StringStrictT16">
<xsd:annotation>
<xsd:documentation>
This section defines a simple type for a String with maximum length of
16 bytes. The String can only contain lower or upper case letters, numbers,
and the underscore characters.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="16"/>
<xsd:pattern value="([a-zA-Z0-9_])*"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="StringStrictT32">
<xsd:annotation>
<xsd:documentation>
This section defines a simple type for a String with maximum length of
32 bytes. The String can only contain lower or upper case letters, numbers,
and the underscore characters.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="32"/>
<xsd:pattern value="([a-zA-Z0-9_])*"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="StringStrictT64">
<xsd:annotation>
<xsd:documentation>
This section defines a simple type for a String with maximum length of
64 bytes. The String can only contain lower or upper case letters, numbers,
and the underscore characters.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="64"/>
<xsd:pattern value="([a-zA-Z0-9_])*"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="StringStrictT128">
<xsd:annotation>
<xsd:documentation>
This section defines a simple type for a String with maximum length of
128 bytes. The String can only contain lower or upper case letters, numbers,
and the underscore characters.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="128"/>
<xsd:pattern value="([a-zA-Z0-9_])*"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="StringStrictT256">
<xsd:annotation>
<xsd:documentation>
This section defines a simple type for a String with maximum length of
256 bytes. The String can only contain lower or upper case letters, numbers,
and the underscore characters.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="256"/>
<xsd:pattern value="([a-zA-Z0-9_])*"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="VersionT">
<xsd:annotation>
<xsd:documentation>
This section defines a simple type for a String with maximum length of
20 bytes. The String can only contain numbers and the period characters.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="20"/>
<xsd:pattern value="([0-9.])*"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>

Example C-3 EMEvent.xsd File

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://xmlns.oracle.com/sysman/connector"
targetNamespace="http://xmlns.oracle.com/sysman/connector"
elementFormDefault="qualified"
xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
jaxb:version="2.0"
xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc"
jaxb:extensionBindingPrefixes="xjc">

<xsd:annotation>
<xsd:appinfo>
<jaxb:globalBindings>
<xjc:simple />
</jaxb:globalBindings>
</xsd:appinfo>
</xsd:annotation>
<xsd:include schemaLocation="connectorCommon.xsd"/>
<xsd:element name="EMEvent" type="EMEventType" />
<xsd:complexType name="EMEventType">
<xsd:sequence>
<xsd:element name="ConnectorGUID" type="xsd:string"/>
<xsd:element name="ExternalEventID" type="xsd:string"
minOccurs="0"/>
<xsd:element name="NotificationRuleOwner" type="xsd:string"/>
<xsd:element name="NotificationRuleName" type="xsd:string"/>
<xsd:element name="ConnectorVariable" type="VariableType"
minOccurs="0" maxOccurs="50"/>
<xsd:element name="Property" type="PropertyType" minOccurs="0"
maxOccurs="50"/>
<xsd:element name="SystemAttributes"
type="EventSystemAttributesType"/>
<xsd:element name="EventClassSpecificAttributes">
<xsd:complexType>
<xsd:sequence>
<xsd:choice minOccurs="0" maxOccurs="200">
<xsd:element name="StringAttribute" type="StringValueType"/>
<xsd:element name="NumberAttribute" type="StringValueType"/>
<xsd:element name="RawAttribute" type="StringValueType"/>
<xsd:element name="DateAttribute" type="DateValueType"/>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EventContextAttributes">
<xsd:complexType>
<xsd:sequence>
<xsd:choice minOccurs="0" maxOccurs="200">
<xsd:element name="StringAttribute" type="StringValueType"/>
<xsd:element name="NumberAttribute" type="StringValueType"/>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="EventSystemAttributesType">
<xsd:sequence>
<xsd:element name="EventClass" type="xsd:string"/>
<xsd:element name="EventID" type="xsd:string"/>
<xsd:element name="SequenceID" type="xsd:string"/>
<xsd:element name="OccurredDate" type="xsd:dateTime" minOccurs="0"/>
<xsd:element name="ReportedDate" type="xsd:dateTime"/>
<xsd:element name="DisplayTZ" type="xsd:string"/>
<xsd:element name="EventName" type="xsd:string"/>
<xsd:element name="Severity" type="xsd:string"/>
<xsd:element name="SeverityCode" type="xsd:string"/>
<xsd:element name="SourceInfo" type="SourceInfoType"/>
<xsd:element name="Message" type="xsd:string" minOccurs="0"/>
<xsd:element name="ActionMessage" type="xsd:string" minOccurs="0"/>
<xsd:element name="EventURL" type="xsd:string"/>
<xsd:element name="AutoClose" type="xsd:boolean"/>
<xsd:element name="EventCategory" type="xsd:string" minOccurs="0"
maxOccurs="50"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="StringValueType">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="Value" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="DateValueType">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="Value" type="xsd:dateTime"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Example C-4 externalEvent.xsd File

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://xmlns.oracle.com/sysman/connector"
targetNamespace="http://xmlns.oracle.com/sysman/connector"
elementFormDefault="qualified">
<xsd:element name="ExternalEvent">
<xsd:annotation>
<xsd:documentation>
This section defines the attribute requirement of an extenral event
for the connector framework to process it.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="SystemAttributes" type="ExternalEventSystemAttributesType">
<xsd:annotation>
<xsd:documentation>
Attributes to capture general information about the external event
system. These attributes are system-specific, with all events from
the same external system sharing the same system attributes.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="EventClassAttributes"
type="ExternalEventClassAttributesType">
<xsd:annotation>
<xsd:documentation>
Attributes to capture specific information required for the event
as defined in the event class.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="ExternalEventSystemAttributesType">
<xsd:annotation>
<xsd:documentation>
This section defines a complext type for system attributes required for
all external events.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="eventName" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Name of the event.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="category" type="xsd:string" minOccurs="0" maxOccurs="50">
<xsd:annotation>
<xsd:documentation>
The event category to which the event belongs.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="targetName" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Name of the target on which event was generated. It refers
to an entity in external systems simillar to an EM target.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="targetType" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The type of the target. Target types defined for event connectors
are used. See connectorDeploy.xsd.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="occurrenceDate" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Date when the event occured.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="detectedDate" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Date when the event was last detected.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="autoClose" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
A flag indicating if an event is auto closed by the system, or it
has to be manually closed by users.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="message" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A description of the event.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="severity" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Severity level of the event.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ExternalEventClassAttributesType">
<xsd:annotation>
<xsd:documentation>
This section defines a complext type for class specific attributes            required
for all external events in the class.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="external_event_id" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
ID used in external system to identify the event.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="external_rule_id" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Optional rule ID that delivered the event in the external system.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="external_host" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Optional host information from extrernal system where event was                generated.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="external_source" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Optional source information from the external system.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="external_severity" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Severity level of the event on external system.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="external_status" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
Status of the event on extenral system.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="custom_field1" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
An optional field.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="custom_field2" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
An optional field.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="custom_field3" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
An optional field.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="custom_field4" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
An optional field.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="custom_field5" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>
An optional field.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

D HP Service Manager WSDL Format

Templates translate the XML format of Enterprise Manager incidents to the XML format required for the end-point application's web service. To create custom templates, you need to understand the format of both sides so that you know how to map the data. This appendix provides detailed information on the format of the XML document that the Service Manager Web service requires.

A WSDL file defines the interface that must be used to call a Web service. The WSDL defines the structure of the XML document that it accepts and how the Web service is to be called. The contents of the WSDL file are listed in Example D-1. All unused operations and messages have been removed to reduce the amount of information. This is the out-of-box WSDL that Service Manager provides. Your WSDL may be significantly different, because the Service Manager web services can be highly customized.

Examples provided in this appendix are as follows:

- IncidentManagement WSDL File

- Common.xsd File

Example D-1 IncidentManagement WSDL File

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<definitions targetNamespace="http://servicecenter.peregrine.com/PWS"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:cmn="http://servicecenter.peregrine.com/PWS/Common"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:ns="http://servicecenter.peregrine.com/PWS"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.xmlsoap.org/wsdl/  http://schemas.xmlsoap.org/wsdl/">
<types>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified"
elementFormDefault="qualified" targetNamespace="http://servicecenter.peregrine.com/PWS"
version="2012-10-25 Rev 0" xmlns="http://servicecenter.peregrine.com/PWS"
xmlns:cmn="http://servicecenter.peregrine.com/PWS/Common">
<xs:import namespace="http://servicecenter.peregrine.com/PWS/Common"
schemaLocation="http://iwave-hpsm.iwave.local:13080/sc62server/PWS/Common.xsd"/>
<xs:complexType name="IncidentKeysType">
<xs:sequence>
<xs:element minOccurs="0" name="IncidentID" nillable="true"
type="cmn:StringType"/>
</xs:sequence>
<xs:attribute name="query" type="xs:string" use="optional"/>
</xs:complexType>
<xs:complexType name="IncidentInstanceType">
<xs:sequence>
<xs:element minOccurs="0" name="IncidentID" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="Category" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="OpenTime" nillable="true"
type="cmn:DateTimeType"/>
<xs:element minOccurs="0" name="OpenedBy" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="Urgency" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="UpdatedTime" nillable="true"
type="cmn:DateTimeType"/>
<xs:element minOccurs="0" name="AssignmentGroup" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="ClosedTime" nillable="true"
type="cmn:DateTimeType"/>
<xs:element minOccurs="0" name="ClosedBy" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="ClosureCode" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="AffectedCI" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="Description">
<xs:complexType>
<xs:complexContent>
<xs:extension base="cmn:ArrayType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0"
name="Description" type="cmn:StringType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="Solution">
<xs:complexType>
<xs:complexContent>
<xs:extension base="cmn:ArrayType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0"
name="Solution" type="cmn:StringType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="Assignee" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="Contact" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="JournalUpdates">
<xs:complexType>
<xs:complexContent>
<xs:extension base="cmn:ArrayType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0"
name="JournalUpdates" type="cmn:StringType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="AlertStatus" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="ContactLastName" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="ContactFirstName" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="Company" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="Title" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="TicketOwner" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="UpdatedBy" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="Status" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="Area" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="SLAAgreementID" nillable="true"
type="cmn:DecimalType"/>
<xs:element minOccurs="0" name="SiteCategory" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="Subarea" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="ProblemType" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="ResolutionFixType" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="UserPriority" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="Location" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="explanation">
<xs:complexType>
<xs:complexContent>
<xs:extension base="cmn:ArrayType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0"
name="explanation" type="cmn:StringType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element minOccurs="0" name="Impact" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="folder" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="Service" nillable="true" type="cmn:StringType"/>
<xs:element minOccurs="0" name="OracleConnectorId" nillable="true"
type="cmn:StringType"/>
<xs:element minOccurs="0" name="attachments" nillable="true"
type="cmn:AttachmentsType"/>
</xs:sequence>
<xs:attribute name="query" type="xs:string" use="optional"/>
<xs:attribute name="uniquequery" type="xs:string" use="optional"/>
<xs:attribute name="recordid" type="xs:string" use="optional"/>
</xs:complexType>
<xs:complexType name="IncidentModelType">
<xs:sequence>
<xs:element name="keys" type="IncidentKeysType"/>
<xs:element name="instance" type="IncidentInstanceType"/>
<xs:element minOccurs="0" name="messages" type="cmn:MessagesType"/>
</xs:sequence>
<xs:attribute name="query" type="xs:string" use="optional"/>
</xs:complexType>
<xs:element name="RetrieveIncidentRequest">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
</xs:sequence>
<xs:attribute name="attachmentInfo" type="xs:boolean" use="optional"/>
<xs:attribute name="attachmentData" type="xs:boolean" use="optional"/>
<xs:attribute default="true" name="ignoreEmptyElements" type="xs:boolean"
use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="RetrieveIncidentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
<xs:element minOccurs="0" name="messages" type="cmn:MessagesType"/>
</xs:sequence>
<xs:attribute name="status" type="cmn:StatusType" use="required"/>
<xs:attribute name="message" type="xs:string" use="required"/>
<xs:attribute name="schemaRevisionDate" type="xs:date" use="required"/>
<xs:attribute name="schemaRevisionLevel" type="xs:int" use="required"/>
<xs:attribute name="returnCode" type="xs:decimal" use="optional"/>
<xs:attribute name="query" type="xs:string" use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="RetrieveIncidentKeysListRequest">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
</xs:sequence>
<xs:attribute name="attachmentInfo" type="xs:boolean" use="optional"/>
<xs:attribute name="attachmentData" type="xs:boolean" use="optional"/>
<xs:attribute default="true" name="ignoreEmptyElements" type="xs:boolean"
use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="RetrieveIncidentKeysListResponse">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="keys" type="IncidentKeysType"/>
<xs:element minOccurs="0" name="messages" type="cmn:MessagesType"/>
</xs:sequence>
<xs:attribute name="status" type="cmn:StatusType" use="required"/>
<xs:attribute name="message" type="xs:string" use="required"/>
<xs:attribute name="schemaRevisionDate" type="xs:date" use="required"/>
<xs:attribute name="schemaRevisionLevel" type="xs:int" use="required"/>
<xs:attribute name="returnCode" type="xs:decimal" use="optional"/>
<xs:attribute name="query" type="xs:string" use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="RetrieveIncidentListRequest">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="keys" type="IncidentKeysType"/>
</xs:sequence>
<xs:attribute name="attachmentInfo" type="xs:boolean" use="optional"/>
<xs:attribute name="attachmentData" type="xs:boolean" use="optional"/>
<xs:attribute default="true" name="ignoreEmptyElements" type="xs:boolean"
use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="RetrieveIncidentListResponse">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="instance"
type="IncidentInstanceType"/>
<xs:element minOccurs="0" name="messages" type="cmn:MessagesType"/>
</xs:sequence>
<xs:attribute name="status" type="cmn:StatusType" use="required"/>
<xs:attribute name="message" type="xs:string" use="required"/>
<xs:attribute name="schemaRevisionDate" type="xs:date" use="required"/>
<xs:attribute name="schemaRevisionLevel" type="xs:int" use="required"/>
<xs:attribute name="returnCode" type="xs:decimal" use="optional"/>
<xs:attribute name="query" type="xs:string" use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="CreateIncidentRequest">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
</xs:sequence>
<xs:attribute name="attachmentInfo" type="xs:boolean" use="optional"/>
<xs:attribute name="attachmentData" type="xs:boolean" use="optional"/>
<xs:attribute default="true" name="ignoreEmptyElements" type="xs:boolean"
use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="CreateIncidentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
<xs:element minOccurs="0" name="messages" type="cmn:MessagesType"/>
</xs:sequence>
<xs:attribute name="status" type="cmn:StatusType" use="required"/>
<xs:attribute name="message" type="xs:string" use="required"/>
<xs:attribute name="schemaRevisionDate" type="xs:date" use="required"/>
<xs:attribute name="schemaRevisionLevel" type="xs:int" use="required"/>
<xs:attribute name="returnCode" type="xs:decimal" use="optional"/>
<xs:attribute name="query" type="xs:string" use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="CloseIncidentRequest">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
</xs:sequence>
<xs:attribute name="attachmentInfo" type="xs:boolean" use="optional"/>
<xs:attribute name="attachmentData" type="xs:boolean" use="optional"/>
<xs:attribute default="true" name="ignoreEmptyElements" type="xs:boolean"
use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="CloseIncidentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
<xs:element minOccurs="0" name="messages" type="cmn:MessagesType"/>
</xs:sequence>
<xs:attribute name="status" type="cmn:StatusType" use="required"/>
<xs:attribute name="message" type="xs:string" use="required"/>
<xs:attribute name="schemaRevisionDate" type="xs:date" use="required"/>
<xs:attribute name="schemaRevisionLevel" type="xs:int" use="required"/>
<xs:attribute name="returnCode" type="xs:decimal" use="optional"/>
<xs:attribute name="query" type="xs:string" use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="ReopenIncidentRequest">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
</xs:sequence>
<xs:attribute name="attachmentInfo" type="xs:boolean" use="optional"/>
<xs:attribute name="attachmentData" type="xs:boolean" use="optional"/>
<xs:attribute default="true" name="ignoreEmptyElements" type="xs:boolean"
use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="ReopenIncidentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
<xs:element minOccurs="0" name="messages" type="cmn:MessagesType"/>
</xs:sequence>
<xs:attribute name="status" type="cmn:StatusType" use="required"/>
<xs:attribute name="message" type="xs:string" use="required"/>
<xs:attribute name="schemaRevisionDate" type="xs:date" use="required"/>
<xs:attribute name="schemaRevisionLevel" type="xs:int" use="required"/>
<xs:attribute name="returnCode" type="xs:decimal" use="optional"/>
<xs:attribute name="query" type="xs:string" use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="ResolveIncidentRequest">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
</xs:sequence>
<xs:attribute name="attachmentInfo" type="xs:boolean" use="optional"/>
<xs:attribute name="attachmentData" type="xs:boolean" use="optional"/>
<xs:attribute default="true" name="ignoreEmptyElements" type="xs:boolean"
use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="ResolveIncidentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
<xs:element minOccurs="0" name="messages" type="cmn:MessagesType"/>
</xs:sequence>
<xs:attribute name="status" type="cmn:StatusType" use="required"/>
<xs:attribute name="message" type="xs:string" use="required"/>
<xs:attribute name="schemaRevisionDate" type="xs:date" use="required"/>
<xs:attribute name="schemaRevisionLevel" type="xs:int" use="required"/>
<xs:attribute name="returnCode" type="xs:decimal" use="optional"/>
<xs:attribute name="query" type="xs:string" use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="UpdateIncidentRequest">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
</xs:sequence>
<xs:attribute name="attachmentInfo" type="xs:boolean" use="optional"/>
<xs:attribute name="attachmentData" type="xs:boolean" use="optional"/>
<xs:attribute default="true" name="ignoreEmptyElements" type="xs:boolean"
use="optional"/>
</xs:complexType>
</xs:element>
<xs:element name="UpdateIncidentResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="model" type="IncidentModelType"/>
<xs:element minOccurs="0" name="messages" type="cmn:MessagesType"/>
</xs:sequence>
<xs:attribute name="status" type="cmn:StatusType" use="required"/>
<xs:attribute name="message" type="xs:string" use="required"/>
<xs:attribute name="schemaRevisionDate" type="xs:date" use="required"/>
<xs:attribute name="schemaRevisionLevel" type="xs:int" use="required"/>
<xs:attribute name="returnCode" type="xs:decimal" use="optional"/>
<xs:attribute name="query" type="xs:string" use="optional"/>
</xs:complexType>
</xs:element>
</xs:schema>
</types>
<message name="RetrieveIncidentRequest">
<part element="ns:RetrieveIncidentRequest" name="RetrieveIncidentRequest"/>
</message>
<message name="RetrieveIncidentResponse">
<part element="ns:RetrieveIncidentResponse" name="RetrieveIncidentResponse"/>
</message>
<message name="RetrieveIncidentKeysListRequest">
<part element="ns:RetrieveIncidentKeysListRequest" name="RetrieveIncidentKeysListRequest"/>
</message>
<message name="RetrieveIncidentKeysListResponse">
<part element="ns:RetrieveIncidentKeysListResponse" name="RetrieveIncidentKeysListResponse"
/>
</message>
<message name="RetrieveIncidentListRequest">
<part element="ns:RetrieveIncidentListRequest" name="RetrieveIncidentListRequest"/>
</message>
<message name="RetrieveIncidentListResponse">
<part element="ns:RetrieveIncidentListResponse" name="RetrieveIncidentListResponse"/>
</message>
<message name="CreateIncidentRequest">
<part element="ns:CreateIncidentRequest" name="CreateIncidentRequest"/>
</message>
<message name="CreateIncidentResponse">
<part element="ns:CreateIncidentResponse" name="CreateIncidentResponse"/>
</message>
<message name="CloseIncidentRequest">
<part element="ns:CloseIncidentRequest" name="CloseIncidentRequest"/>
</message>
<message name="CloseIncidentResponse">
<part element="ns:CloseIncidentResponse" name="CloseIncidentResponse"/>
</message>
<message name="ReopenIncidentRequest">
<part element="ns:ReopenIncidentRequest" name="ReopenIncidentRequest"/>
</message>
<message name="ReopenIncidentResponse">
<part element="ns:ReopenIncidentResponse" name="ReopenIncidentResponse"/>
</message>
<message name="ResolveIncidentRequest">
<part element="ns:ResolveIncidentRequest" name="ResolveIncidentRequest"/>
</message>
<message name="ResolveIncidentResponse">
<part element="ns:ResolveIncidentResponse" name="ResolveIncidentResponse"/>
</message>
<message name="UpdateIncidentRequest">
<part element="ns:UpdateIncidentRequest" name="UpdateIncidentRequest"/>
</message>
<message name="UpdateIncidentResponse">
<part element="ns:UpdateIncidentResponse" name="UpdateIncidentResponse"/>
</message>
<portType name="IncidentManagement">
<operation name="RetrieveIncident">
<documentation/>
<input message="ns:RetrieveIncidentRequest"/>
<output message="ns:RetrieveIncidentResponse"/>
</operation>
<operation name="RetrieveIncidentKeysList">
<documentation/>
<input message="ns:RetrieveIncidentKeysListRequest"/>
<output message="ns:RetrieveIncidentKeysListResponse"/>
</operation>
<operation name="RetrieveIncidentList">
<documentation/>
<input message="ns:RetrieveIncidentListRequest"/>
<output message="ns:RetrieveIncidentListResponse"/>
</operation>
<operation name="CreateIncident">
<documentation/>
<input message="ns:CreateIncidentRequest"/>
<output message="ns:CreateIncidentResponse"/>
</operation>
<operation name="CloseIncident">
<documentation/>
<input message="ns:CloseIncidentRequest"/>
<output message="ns:CloseIncidentResponse"/>
</operation>
<operation name="ReopenIncident">
<documentation/>
<input message="ns:ReopenIncidentRequest"/>
<output message="ns:ReopenIncidentResponse"/>
</operation>
<operation name="ResolveIncident">
<documentation/>
<input message="ns:ResolveIncidentRequest"/>
<output message="ns:ResolveIncidentResponse"/>
</operation>
<operation name="UpdateIncident">
<documentation/>
<input message="ns:UpdateIncidentRequest"/>
<output message="ns:UpdateIncidentResponse"/>
</operation>
</portType>
<binding name="IncidentManagement" type="ns:IncidentManagement">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="RetrieveIncident">
<soap:operation soapAction="Retrieve" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="RetrieveIncidentKeysList">
<soap:operation soapAction="RetrieveKeysList" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="RetrieveIncidentList">
<soap:operation soapAction="RetrieveList" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="CreateIncident">
<soap:operation soapAction="Create" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="CloseIncident">
<soap:operation soapAction="Close" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="ReopenIncident">
<soap:operation soapAction="Reopen" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="ResolveIncident">
<soap:operation soapAction="Resolve" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
<operation name="UpdateIncident">
<soap:operation soapAction="Update" style="document"/>
<input>
<soap:body use="literal"/>
</input>
<output>
<soap:body use="literal"/>
</output>
</operation>
</binding>
<service name="IncidentManagement">
<port binding="ns:IncidentManagement" name="IncidentManagement">
<soap:address location="http://iwave-hpsm.iwave.local:13080/sc62server/ws"/>
</port>
</service>
</definitions>

Example D-2 Common.xsd File

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified"
elementFormDefault="qualified" targetNamespace="http://servicecenter.peregrine.com/PWS/Common"
version="2012-10-25 Rev 0" xmlns="http://servicecenter.peregrine.com/PWS/Common"
xmlns:cmn="http://servicecenter.peregrine.com/PWS/Common">
<xs:complexType name="StringType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute fixed="String" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="DecimalType">
<xs:simpleContent>
<xs:extension base="xs:decimal">
<xs:attribute fixed="Decimal" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="BooleanType">
<xs:simpleContent>
<xs:extension base="xs:boolean">
<xs:attribute fixed="Boolean" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="DateTimeType">
<xs:simpleContent>
<xs:extension base="xs:dateTime">
<xs:attribute fixed="DateTime" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="DateType">
<xs:simpleContent>
<xs:extension base="xs:date">
<xs:attribute fixed="Date" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="TimeType">
<xs:simpleContent>
<xs:extension base="xs:time">
<xs:attribute fixed="Time" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="DurationType">
<xs:simpleContent>
<xs:extension base="xs:duration">
<xs:attribute fixed="Duration" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="IntType">
<xs:simpleContent>
<xs:extension base="xs:int">
<xs:attribute fixed="Int" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="ShortType">
<xs:simpleContent>
<xs:extension base="xs:short">
<xs:attribute fixed="Short" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="LongType">
<xs:simpleContent>
<xs:extension base="xs:long">
<xs:attribute fixed="Long" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="ByteType">
<xs:simpleContent>
<xs:extension base="xs:byte">
<xs:attribute fixed="Byte" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="FloatType">
<xs:simpleContent>
<xs:extension base="xs:float">
<xs:attribute fixed="Float" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="DoubleType">
<xs:simpleContent>
<xs:extension base="xs:double">
<xs:attribute fixed="Double" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="Base64Type">
<xs:simpleContent>
<xs:extension base="xs:base64Binary">
<xs:attribute fixed="Base64" name="type" type="xs:string" use="required"/>
<xs:attribute name="mandatory" type="xs:boolean" use="optional"/>
<xs:attribute name="readonly" type="xs:boolean" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="ArrayType">
<xs:attribute fixed="Array" name="type" type="xs:string" use="required"/>
</xs:complexType>
<xs:complexType name="StructureType">
<xs:attribute fixed="Structure" name="type" type="xs:string" use="required"/>
</xs:complexType>
<xs:complexType name="AttachmentType">
<xs:attribute name="href" type="xs:string" use="optional"/>
<xs:attribute name="contentId" type="xs:string" use="optional"/>
<xs:attribute name="action" type="xs:string" use="optional"/>
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="type" type="xs:string" use="required"/>
<xs:attribute name="len" type="xs:int" use="optional"/>
<xs:attribute name="charset" type="xs:string" use="optional"/>
<xs:attribute name="attachmentType" type="xs:string" use="optional"/>
</xs:complexType>
<xs:complexType name="AttachmentsType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="attachment" type="AttachmentType"
/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="MessageType">
<xs:simpleContent>
<xs:extension base="StringType">
<xs:attribute name="severity" type="xs:int" use="optional"/>
<xs:attribute name="module" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="MessagesType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="message" type="MessageType"/>
</xs:sequence>
</xs:complexType>
<xs:simpleType name="StatusType">
<xs:restriction base="xs:string">
<xs:enumeration value="SUCCESS"/>
<xs:enumeration value="FAILURE"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>

E Enterprise Manager Incident Examples

This appendix contains examples that show the XML format of incidents from Enterprise Manager that conform to the schemas defined in Appendix C. You can use these examples to help identify the fields to map when generating custom templates. You can also use them to test your custom templates after they have been built.

Examples provided in this appendix are as follows:

- Create Example

- Update Example

- Clear Example

- Reopen Example

E.1 Create Example

The following example shows the XML format Enterprise Manager generates for HP Service Manager create operations.

<?xml version="1.0" encoding="UTF-8"?>
<EMIncident xmlns="http://xmlns.oracle.com/sysman/connector">
<ConnectorGUID>5F8B3F54D2164AA8B4D3701656FF2524</ConnectorGUID>
<TicketID/>
<HDUser>iwave</HDUser>
<NotificationRuleOwner>SYSMAN</NotificationRuleOwner>
<NotificationRuleName>HPSM 9 Autoclose Rule</NotificationRuleName>
<ReopenTicket>No</ReopenTicket>
<ConnectorVariable>
<VariableName>TICKET_ID</VariableName>
<VariableValue>IM10237</VariableValue>
</ConnectorVariable>
<Property>
<Name>AuthenticationType</Name>
<Value>HTTPBasicAuthentication</Value>
</Property>
<Property>
<Name>IsNewTargetType</Name>
<Value>no</Value>
</Property>
<SystemAttributes>
<IncidentID>B6096FBDB6FEC905E040020A780122F7</IncidentID>
<SourceInfo>
<SourceObjInfo>
<ObjID>D93A2E4E1622013D74D9534ECB090944</ObjID>
<ObjName>orcsvr1.iwavesoftware.com</ObjName>
<ObjOwner>SYSMAN</ObjOwner>
<SourceObjType>Targets</SourceObjType>
<SourceObjSubType>host</SourceObjSubType>
</SourceObjInfo>
<TargetInfo>
<TargetGUID>D93A2E4E1622013D74D9534ECB090944</TargetGUID>
<TargetName>orcsvr1.iwavesoftware.com</TargetName>
<TargetType>host</TargetType>
<TargetTypeLabel>Host</TargetTypeLabel>
<TargetURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=TARGET_HOMEPAGE&amp;targetName=orcsvr1.iwavesoftware.com&amp;targetType=host</TargetURL>
<TargetProperty>
<Name>Target_Host</Name>
<Value>orcsvr1.iwavesoftware.com</Value>
</TargetProperty>
<TargetProperty>
<Name>Target Version</Name>
<Value>5.5.0.0.0</Value>
</TargetProperty>
<TargetProperty>
<Name>Line of Business</Name>
<Value>Software</Value>
</TargetProperty>
<TargetProperty>
<Name>Location</Name>
<Value>Frisco, TX</Value>
</TargetProperty>
<TargetProperty>
<Name>Comment</Name>
<Value>Testing target properties</Value>
</TargetProperty>
</TargetInfo>
</SourceInfo>
<IncidentURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=sdk-core-event-console-detailIncident&amp;issueID=B6096FBDB6FEC905E040020A780122F7 </IncidentURL>
<AutoClose>true</AutoClose>
<Owner/>
<ResolutionState>new</ResolutionState>
<Acknowledge>false</Acknowledge>
<Escalated>false</Escalated>
<EscalationLevel>0</EscalationLevel>
<Priority>None</Priority>
<Summary>Memory Utilization is 81.988%, crossed warning (40) or critical          (60) threshold.</Summary>
<CreationDate>2012-01-10T16:07:54.000-06:00</CreationDate>
<LastUpdatedDate>2012-01-10T16:07:54.000-06:00</LastUpdatedDate>
<Category>Capacity</Category>
<Severity>Critical</Severity>
<SeverityCode>CRITICAL</SeverityCode>
</SystemAttributes>
<HasEMEvent>true</HasEMEvent>
<EMEvent>
<ConnectorGUID>5F8B3F54D2164AA8B4D3701656FF2524</ConnectorGUID>
<NotificationRuleOwner>SYSMAN</NotificationRuleOwner>
<NotificationRuleName>HPSM 9 Autoclose Rule</NotificationRuleName>
<ConnectorVariable>
<VariableName>TICKET_ID</VariableName>
<VariableValue>IM10237</VariableValue>
</ConnectorVariable>
<Property>
<Name>AuthenticationType</Name>
<Value>HTTPBasicAuthentication</Value>
</Property>
<Property>
<Name>IsNewTargetType</Name>
<Value>no</Value>
</Property>
<SystemAttributes>
<EventClass>metric_alert</EventClass>
<EventID>B609743F7D2DA971E040020A78012529</EventID>
<SequenceID>B609743F7D2EA971E040020A78012529</SequenceID>
<ReportedDate>2012-01-10T16:07:53.000-06:00</ReportedDate>
<DisplayTZ>America/Chicago</DisplayTZ>
<EventName>Load:memUsedPct</EventName>
<Severity>Critical</Severity>
<SeverityCode>CRITICAL</SeverityCode>
<SourceInfo>
<SourceObjInfo>
<ObjID>D93A2E4E1622013D74D9534ECB090944</ObjID>
<ObjName>orcsvr1.iwavesoftware.com</ObjName>
<ObjOwner>SYSMAN</ObjOwner>
<SourceObjType>TARGET</SourceObjType>
<SourceObjSubType>host</SourceObjSubType>
</SourceObjInfo>
<TargetInfo>
<TargetGUID>D93A2E4E1622013D74D9534ECB090944</TargetGUID>
<TargetName>orcsvr1.iwavesoftware.com</TargetName>
<TargetType>host</TargetType>
<TargetTypeLabel>Host</TargetTypeLabel>
<TargetURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=TARGET_HOMEPAGE&amp;targetName=orcsvr1.iwavesoftware.com&amp;targetType=host</TargetURL>
<TargetProperty>
<Name>Target_Host</Name>
<Value>orcsvr1.iwavesoftware.com</Value>
</TargetProperty>
<TargetProperty>
<Name>Target Version</Name>
<Value>5.5.0.0.0</Value>
</TargetProperty>
<TargetProperty>
<Name>Line of Business</Name>
<Value>Software</Value>
</TargetProperty>
<TargetProperty>
<Name>Location</Name>
<Value>Frisco, TX</Value>
</TargetProperty>
<TargetProperty>
<Name>Comment</Name>
<Value>Testing target properties</Value>
</TargetProperty>
</TargetInfo>
</SourceInfo>
<Message>Memory Utilization is 81.988%, crossed warning (40) or               critical (60) threshold.</Message>
<EventURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=sdk-core-event-console-detailEvent&amp;issueID=B609743F7D2EA971E040020A78012529</EventURL>
<AutoClose>true</AutoClose>
<EventCategory>Capacity</EventCategory>
</SystemAttributes>
<EventClassSpecificAttributes>
<StringAttribute>
<Name>is_thresholdable</Name>
<Value>1</Value>
</StringAttribute>
<StringAttribute>
<Name>coll_name</Name>
<Value>LoadLinux</Value>
</StringAttribute>
<StringAttribute>
<Name>is_metric_extension</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_column_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>unit_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>cycle_guid</Name>
<Value>B609743F7D2AA971E040020A78012529</Value>
</StringAttribute>
<StringAttribute>
<Name>is_remote</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_type</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_guid</Name>
<Value>86821B5F0CE858D6E4A7F7390E88B73C</Value>
</StringAttribute>
<StringAttribute>
<Name>num_keys</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>key_value</Name>
<Value> </Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description_nlsid</Name>
</StringAttribute>
<StringAttribute>
<Name>value</Name>
<Value>81.988</Value>
</StringAttribute>
<StringAttribute>
<Name>is_long_running</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group</Name>
<Value>Load</Value>
</StringAttribute>
<StringAttribute>
<Name>is_udm</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description</Name>
</StringAttribute>
<StringAttribute>
<Name>metric_column_nlsid</Name>
<Value>host_load_memUsedPct</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_column</Name>
<Value>memUsedPct</Value>
</StringAttribute>
<StringAttribute>
<Name>unit_nlsid</Name>
<Value>em__sys__standard_percent</Value>
</StringAttribute>
<StringAttribute>
<Name>unit</Name>
<Value>%</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group_nlsid</Name>
<Value>host_load</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>severity_guid</Name>
<Value>B609743F7D2AA971E040020A78012529</Value>
</StringAttribute>
</EventClassSpecificAttributes>
</EMEvent>
</EMIncident>

E.2 Update Example

The following example shows the XML format Enterprise Manager generates for HP Service Manager update operations.

<?xml version="1.0" encoding="UTF-8"?>
<EMIncident xmlns="http://xmlns.oracle.com/sysman/connector">
<ConnectorGUID>5F8B3F54D2164AA8B4D3701656FF2524</ConnectorGUID>
<TicketID>IM10258</TicketID>
<HDUser>iwave</HDUser>
<NotificationRuleOwner>SYSMAN</NotificationRuleOwner>
<NotificationRuleName>HPSM 9 Autoclose Rule</NotificationRuleName>
<ReopenTicket>No</ReopenTicket>
<ConnectorVariable>
<VariableName>TICKET_ID</VariableName>
<VariableValue>IM10237</VariableValue>
</ConnectorVariable>
<Property>
<Name>AuthenticationType</Name>
<Value>HTTPBasicAuthentication</Value>
</Property>
<Property>
<Name>IsNewTargetType</Name>
<Value>no</Value>
</Property>
<SystemAttributes>
<IncidentID>B6096FBDB6FEC905E040020A780122F7</IncidentID>
<SourceInfo>
<SourceObjInfo>
<ObjID>D93A2E4E1622013D74D9534ECB090944</ObjID>
<ObjName>orcsvr1.iwavesoftware.com</ObjName>
<ObjOwner>SYSMAN</ObjOwner>
<SourceObjType>Targets</SourceObjType>
<SourceObjSubType>host</SourceObjSubType>
</SourceObjInfo>
<TargetInfo>
<TargetGUID>D93A2E4E1622013D74D9534ECB090944</TargetGUID>
<TargetName>orcsvr1.iwavesoftware.com</TargetName>
<TargetType>host</TargetType>
<TargetTypeLabel>Host</TargetTypeLabel>
<TargetURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=TARGET_HOMEPAGE&amp;targetName=orcsvr1.iwavesoftware.com&amp;targetType=host</TargetURL>
<TargetProperty>
<Name>Target_Host</Name>
<Value>orcsvr1.iwavesoftware.com</Value>
</TargetProperty>
<TargetProperty>
<Name>Target Version</Name>
<Value>5.5.0.0.0</Value>
</TargetProperty>
<TargetProperty>
<Name>Line of Business</Name>
<Value>Software</Value>
</TargetProperty>
<TargetProperty>
<Name>Location</Name>
<Value>Frisco, TX</Value>
</TargetProperty>
<TargetProperty>
<Name>Comment</Name>
<Value>Testing target properties</Value>
</TargetProperty>
</TargetInfo>
</SourceInfo>
<IncidentURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=sdk-core-event-console-detailIncident&amp;issueID=B6096FBDB6FEC905E040020A780122F7 </IncidentURL>
<AutoClose>true</AutoClose>
<Owner/>
<ResolutionState>new</ResolutionState>
<Acknowledge>false</Acknowledge>
<Escalated>false</Escalated>
<EscalationLevel>0</EscalationLevel>
<Priority>None</Priority>
<Summary>Memory Utilization is 81.988%, crossed warning (40) or critical          (99) threshold.</Summary>
<CreationDate>2012-01-10T16:07:54.000-06:00</CreationDate>
<LastUpdatedDate>2012-01-10T16:09:31.000-06:00</LastUpdatedDate>
<Category>Capacity</Category>
<Severity>Warning</Severity>
<SeverityCode>WARNING</SeverityCode>
</SystemAttributes>
<HasEMEvent>true</HasEMEvent>
<EMEvent>
<ConnectorGUID>5F8B3F54D2164AA8B4D3701656FF2524</ConnectorGUID>
<NotificationRuleOwner>SYSMAN</NotificationRuleOwner>
<NotificationRuleName>HPSM 9 Autoclose Rule</NotificationRuleName>
<ConnectorVariable>
<VariableName>TICKET_ID</VariableName>
<VariableValue>IM10237</VariableValue>
</ConnectorVariable>
<Property>
<Name>AuthenticationType</Name>
<Value>HTTPBasicAuthentication</Value>
</Property>
<Property>
<Name>IsNewTargetType</Name>
<Value>no</Value>
</Property>
<SystemAttributes>
<EventClass>metric_alert</EventClass>
<EventID>B60974257B042B09E040020A7801251A</EventID>
<SequenceID>B609743F7D2EA971E040020A78012529</SequenceID>
<ReportedDate>2012-01-10T16:09:30.000-06:00</ReportedDate>
<DisplayTZ>America/Chicago</DisplayTZ>
<EventName>Load:memUsedPct</EventName>
<Severity>Warning</Severity>
<SeverityCode>WARNING</SeverityCode>
<SourceInfo>
<SourceObjInfo>
<ObjID>D93A2E4E1622013D74D9534ECB090944</ObjID>
<ObjName>orcsvr1.iwavesoftware.com</ObjName>
<ObjOwner>SYSMAN</ObjOwner>
<SourceObjType>TARGET</SourceObjType>
<SourceObjSubType>host</SourceObjSubType>
</SourceObjInfo>
<TargetInfo>
<TargetGUID>D93A2E4E1622013D74D9534ECB090944</TargetGUID>
<TargetName>orcsvr1.iwavesoftware.com</TargetName>
<TargetType>host</TargetType>
<TargetTypeLabel>Host</TargetTypeLabel>
<TargetURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=TARGET_HOMEPAGE&amp;targetName=orcsvr1.iwavesoftware.com&amp;targetType=host</TargetURL>
<TargetProperty>
<Name>Target_Host</Name>
<Value>orcsvr1.iwavesoftware.com</Value>
</TargetProperty>
<TargetProperty>
<Name>Target Version</Name>
<Value>5.5.0.0.0</Value>
</TargetProperty>
<TargetProperty>
<Name>Line of Business</Name>
<Value>Software</Value>
</TargetProperty>
<TargetProperty>
<Name>Location</Name>
<Value>Frisco, TX</Value>
</TargetProperty>
<TargetProperty>
<Name>Comment</Name>
<Value>Testing target properties</Value>
</TargetProperty>
</TargetInfo>
</SourceInfo>
<Message>Memory Utilization is 81.988%, crossed warning (40) or                critical (99) threshold.</Message>
<EventURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=sdk-core-event-console-detailEvent&amp;issueID=B609743F7D2EA971E040020A78012529</EventURL>
<AutoClose>true</AutoClose>
<EventCategory>Capacity</EventCategory>
</SystemAttributes>
<EventClassSpecificAttributes>
<StringAttribute>
<Name>is_thresholdable</Name>
<Value>1</Value>
</StringAttribute>
<StringAttribute>
<Name>coll_name</Name>
<Value>LoadLinux</Value>
</StringAttribute>
<StringAttribute>
<Name>is_metric_extension</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_column_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>unit_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>cycle_guid</Name>
<Value>B609743F7D2AA971E040020A78012529</Value>
</StringAttribute>
<StringAttribute>
<Name>is_remote</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_type</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_guid</Name>
<Value>86821B5F0CE858D6E4A7F7390E88B73C</Value>
</StringAttribute>
<StringAttribute>
<Name>num_keys</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>key_value</Name>
<Value> </Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description_nlsid</Name>
</StringAttribute>
<StringAttribute>
<Name>value</Name>
<Value>81.988</Value>
</StringAttribute>
<StringAttribute>
<Name>is_long_running</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group</Name>
<Value>Load</Value>
</StringAttribute>
<StringAttribute>
<Name>is_udm</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description</Name>
</StringAttribute>
<StringAttribute>
<Name>metric_column_nlsid</Name>
<Value>host_load_memUsedPct</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_column</Name>
<Value>memUsedPct</Value>
</StringAttribute>
<StringAttribute>
<Name>unit_nlsid</Name>
<Value>em__sys__standard_percent</Value>
</StringAttribute>
<StringAttribute>
<Name>unit</Name>
<Value>%</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group_nlsid</Name>
<Value>host_load</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>severity_guid</Name>
<Value>B60974257B012B09E040020A7801251A</Value>
</StringAttribute>
</EventClassSpecificAttributes>
</EMEvent>
</EMIncident>

Clear Sample
Listed below is a sample of the XML format generated by Enterprise Manager for HPSM clear operations.
<?xml version="1.0" encoding="UTF-8"?>
<EMIncident xmlns="http://xmlns.oracle.com/sysman/connector">
<ConnectorGUID>5F8B3F54D2164AA8B4D3701656FF2524</ConnectorGUID>
<TicketID>IM10258</TicketID>
<HDUser>iwave</HDUser>
<NotificationRuleOwner>SYSMAN</NotificationRuleOwner>
<NotificationRuleName>HPSM 9 Autoclose Rule</NotificationRuleName>
<ReopenTicket>No</ReopenTicket>
<ConnectorVariable>
<VariableName>TICKET_ID</VariableName>
<VariableValue>IM10237</VariableValue>
</ConnectorVariable>
<Property>
<Name>AuthenticationType</Name>
<Value>HTTPBasicAuthentication</Value>
</Property>
<Property>
<Name>IsNewTargetType</Name>
<Value>no</Value>
</Property>
<SystemAttributes>
<IncidentID>B6096FBDB6FEC905E040020A780122F7</IncidentID>
<SourceInfo>
<SourceObjInfo>
<ObjID>D93A2E4E1622013D74D9534ECB090944</ObjID>
<ObjName>orcsvr1.iwavesoftware.com</ObjName>
<ObjOwner>SYSMAN</ObjOwner>
<SourceObjType>Targets</SourceObjType>
<SourceObjSubType>host</SourceObjSubType>
</SourceObjInfo>
<TargetInfo>
<TargetGUID>D93A2E4E1622013D74D9534ECB090944</TargetGUID>
<TargetName>orcsvr1.iwavesoftware.com</TargetName>
<TargetType>host</TargetType>
<TargetTypeLabel>Host</TargetTypeLabel>
<TargetURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=TARGET_HOMEPAGE&amp;targetName=orcsvr1.iwavesoftware.com&amp;targetType=host</TargetURL>
<TargetProperty>
<Name>Target_Host</Name>
<Value>orcsvr1.iwavesoftware.com</Value>
</TargetProperty>
<TargetProperty>
<Name>Target Version</Name>
<Value>5.5.0.0.0</Value>
</TargetProperty>
<TargetProperty>
<Name>Line of Business</Name>
<Value>Software</Value>
</TargetProperty>
<TargetProperty>
<Name>Location</Name>
<Value>Frisco, TX</Value>
</TargetProperty>
<TargetProperty>
<Name>Comment</Name>
<Value>Testing target properties</Value>
</TargetProperty>
</TargetInfo>
</SourceInfo>
<IncidentURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=sdk-core-event-console-detailIncident&amp;issueID=B6096FBDB6FEC905E040020A780122F7 </IncidentURL>
<AutoClose>true</AutoClose>
<Owner/>
<ResolutionState>closed</ResolutionState>
<Acknowledge>false</Acknowledge>
<Escalated>false</Escalated>
<EscalationLevel>0</EscalationLevel>
<Priority>None</Priority>
<Summary>Memory Utilization is 81.791%, fallen below warning (98) and           critical (99) thresholds.</Summary>
<CreationDate>2012-01-10T16:07:54.000-06:00</CreationDate>
<LastUpdatedDate>2012-01-10T16:11:01.000-06:00</LastUpdatedDate>
<Category>Capacity</Category>
<Severity>Clear</Severity>
<SeverityCode>CLEAR</SeverityCode>
</SystemAttributes>
<HasEMEvent>true</HasEMEvent>
<EMEvent>
<ConnectorGUID>5F8B3F54D2164AA8B4D3701656FF2524</ConnectorGUID>
<NotificationRuleOwner>SYSMAN</NotificationRuleOwner>
<NotificationRuleName>HPSM 9 Autoclose Rule</NotificationRuleName>
<ConnectorVariable>
<VariableName>TICKET_ID</VariableName>
<VariableValue>IM10237</VariableValue>
</ConnectorVariable>
<Property>
<Name>AuthenticationType</Name>
<Value>HTTPBasicAuthentication</Value>
</Property>
<Property>
<Name>IsNewTargetType</Name>
<Value>no</Value>
</Property>
<SystemAttributes>
<EventClass>metric_alert</EventClass>
<EventID>B609743F7D32A971E040020A78012529</EventID>
<SequenceID>B609743F7D2EA971E040020A78012529</SequenceID>
<ReportedDate>2012-01-10T16:11:00.000-06:00</ReportedDate>
<DisplayTZ>America/Chicago</DisplayTZ>
<EventName>Load:memUsedPct</EventName>
<Severity>Clear</Severity>
<SeverityCode>CLEAR</SeverityCode>
<SourceInfo>
<SourceObjInfo>
<ObjID>D93A2E4E1622013D74D9534ECB090944</ObjID>
<ObjName>orcsvr1.iwavesoftware.com</ObjName>
<ObjOwner>SYSMAN</ObjOwner>
<SourceObjType>TARGET</SourceObjType>
<SourceObjSubType>host</SourceObjSubType>
</SourceObjInfo>
<TargetInfo>
<TargetGUID>D93A2E4E1622013D74D9534ECB090944</TargetGUID>
<TargetName>orcsvr1.iwavesoftware.com</TargetName>
<TargetType>host</TargetType>
<TargetTypeLabel>Host</TargetTypeLabel>
<TargetURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=TARGET_HOMEPAGE&amp;targetName=orcsvr1.iwavesoftware.com&amp;targetType=host</TargetURL>
<TargetProperty>
<Name>Target_Host</Name>
<Value>orcsvr1.iwavesoftware.com</Value>
</TargetProperty>
<TargetProperty>
<Name>Target Version</Name>
<Value>5.5.0.0.0</Value>
</TargetProperty>
<TargetProperty>
<Name>Line of Business</Name>
<Value>Software</Value>
</TargetProperty>
<TargetProperty>
<Name>Location</Name>
<Value>Frisco, TX</Value>
</TargetProperty>
<TargetProperty>
<Name>Comment</Name>
<Value>Testing target properties</Value>
</TargetProperty>
</TargetInfo>
</SourceInfo>
<Message>Memory Utilization is 81.791%, fallen below warning (98) and critical (99) thresholds.</Message>
<EventURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=sdk-core-event-console-detailEvent&amp;issueID=B609743F7D2EA971E040020A78012529</EventURL>
<AutoClose>true</AutoClose>
<EventCategory>Capacity</EventCategory>
</SystemAttributes>
<EventClassSpecificAttributes>
<StringAttribute>
<Name>is_thresholdable</Name>
<Value>1</Value>
</StringAttribute>
<StringAttribute>
<Name>coll_name</Name>
<Value>LoadLinux</Value>
</StringAttribute>
<StringAttribute>
<Name>is_metric_extension</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_column_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>unit_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>cycle_guid</Name>
<Value>B609743F7D2AA971E040020A78012529</Value>
</StringAttribute>
<StringAttribute>
<Name>is_remote</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_type</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_guid</Name>
<Value>86821B5F0CE858D6E4A7F7390E88B73C</Value>
</StringAttribute>
<StringAttribute>
<Name>num_keys</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>key_value</Name>
<Value> </Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description_nlsid</Name>
</StringAttribute>
<StringAttribute>
<Name>value</Name>
<Value>81.791</Value>
</StringAttribute>
<StringAttribute>
<Name>is_long_running</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group</Name>
<Value>Load</Value>
</StringAttribute>
<StringAttribute>
<Name>is_udm</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description</Name>
</StringAttribute>
<StringAttribute>
<Name>metric_column_nlsid</Name>
<Value>host_load_memUsedPct</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_column</Name>
<Value>memUsedPct</Value>
</StringAttribute>
<StringAttribute>
<Name>unit_nlsid</Name>
<Value>em__sys__standard_percent</Value>
</StringAttribute>
<StringAttribute>
<Name>unit</Name>
<Value>%</Value>
</StringAttribute>             <StringAttribute>
<Name>metric_group_nlsid</Name>
<Value>host_load</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>severity_guid</Name>
<Value>B60974257B012B09E040020A7801251A</Value>
</StringAttribute>
</EventClassSpecificAttributes>
</EMEvent>
</EMIncident>

E.3 Clear Example

The following example shows the XML format Enterprise Manager generates for HP Service Manager clear operations.

<?xml version="1.0" encoding="UTF-8"?>
<EMIncident xmlns="http://xmlns.oracle.com/sysman/connector">
<ConnectorGUID>5F8B3F54D2164AA8B4D3701656FF2524</ConnectorGUID>
<TicketID>IM10258</TicketID>
<HDUser>iwave</HDUser>
<NotificationRuleOwner>SYSMAN</NotificationRuleOwner>
<NotificationRuleName>HPSM 9 Autoclose Rule</NotificationRuleName>
<ReopenTicket>No</ReopenTicket>
<ConnectorVariable>
<VariableName>TICKET_ID</VariableName>
<VariableValue>IM10237</VariableValue>
</ConnectorVariable>
<Property>
<Name>AuthenticationType</Name>
<Value>HTTPBasicAuthentication</Value>
</Property>
<Property>
<Name>IsNewTargetType</Name>
<Value>no</Value>
</Property>
<SystemAttributes>
<IncidentID>B6096FBDB6FEC905E040020A780122F7</IncidentID>
<SourceInfo>
<SourceObjInfo>
<ObjID>D93A2E4E1622013D74D9534ECB090944</ObjID>
<ObjName>orcsvr1.iwavesoftware.com</ObjName>
<ObjOwner>SYSMAN</ObjOwner>
<SourceObjType>Targets</SourceObjType>
<SourceObjSubType>host</SourceObjSubType>
</SourceObjInfo>
<TargetInfo>
<TargetGUID>D93A2E4E1622013D74D9534ECB090944</TargetGUID>
<TargetName>orcsvr1.iwavesoftware.com</TargetName>
<TargetType>host</TargetType>
<TargetTypeLabel>Host</TargetTypeLabel>
<TargetURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=TARGET_HOMEPAGE&amp;targetName=orcsvr1.iwavesoftware.com&amp;targetType=host</TargetURL>
<TargetProperty>
<Name>Target_Host</Name>
<Value>orcsvr1.iwavesoftware.com</Value>
</TargetProperty>
<TargetProperty>
<Name>Target Version</Name>
<Value>5.5.0.0.0</Value>
</TargetProperty>
<TargetProperty>
<Name>Line of Business</Name>
<Value>Software</Value>
</TargetProperty>
<TargetProperty>
<Name>Location</Name>
<Value>Frisco, TX</Value>
</TargetProperty>
<TargetProperty>
<Name>Comment</Name>
<Value>Testing target properties</Value>
</TargetProperty>
</TargetInfo>
</SourceInfo>
<IncidentURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=sdk-core-event-console-detailIncident&amp;issueID=B6096FBDB6FEC905E040020A780122F7< /IncidentURL>
<AutoClose>true</AutoClose>
<Owner/>
<ResolutionState>closed</ResolutionState>
<Acknowledge>false</Acknowledge>
<Escalated>false</Escalated>
<EscalationLevel>0</EscalationLevel>
<Priority>None</Priority>
<Summary>Memory Utilization is 81.791%, fallen below warning (98) and           critical (99) thresholds.</Summary>
<CreationDate>2012-01-10T16:07:54.000-06:00</CreationDate>
<LastUpdatedDate>2012-01-10T16:11:01.000-06:00</LastUpdatedDate>
<Category>Capacity</Category>
<Severity>Clear</Severity>
<SeverityCode>CLEAR</SeverityCode>
</SystemAttributes>
<HasEMEvent>true</HasEMEvent>
<EMEvent>
<ConnectorGUID>5F8B3F54D2164AA8B4D3701656FF2524</ConnectorGUID>
<NotificationRuleOwner>SYSMAN</NotificationRuleOwner>
<NotificationRuleName>HPSM 9 Autoclose Rule</NotificationRuleName>
<ConnectorVariable>
<VariableName>TICKET_ID</VariableName>
<VariableValue>IM10237</VariableValue>
</ConnectorVariable>
<Property>
<Name>AuthenticationType</Name>
<Value>HTTPBasicAuthentication</Value>
</Property>
<Property>
<Name>IsNewTargetType</Name>
<Value>no</Value>
</Property>
<SystemAttributes>
<EventClass>metric_alert</EventClass>
<EventID>B609743F7D32A971E040020A78012529</EventID>
<SequenceID>B609743F7D2EA971E040020A78012529</SequenceID>
<ReportedDate>2012-01-10T16:11:00.000-06:00</ReportedDate>
<DisplayTZ>America/Chicago</DisplayTZ>
<EventName>Load:memUsedPct</EventName>
<Severity>Clear</Severity>
<SeverityCode>CLEAR</SeverityCode>
<SourceInfo>
<SourceObjInfo>
<ObjID>D93A2E4E1622013D74D9534ECB090944</ObjID>
<ObjName>orcsvr1.iwavesoftware.com</ObjName>
<ObjOwner>SYSMAN</ObjOwner>
<SourceObjType>TARGET</SourceObjType>
<SourceObjSubType>host</SourceObjSubType>
</SourceObjInfo>
<TargetInfo>
<TargetGUID>D93A2E4E1622013D74D9534ECB090944</TargetGUID>
<TargetName>orcsvr1.iwavesoftware.com</TargetName>
<TargetType>host</TargetType>
<TargetTypeLabel>Host</TargetTypeLabel>
<TargetURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=TARGET_HOMEPAGE&amp;targetName=orcsvr1.iwavesoftware.com&amp;targetType=host</TargetURL>
<TargetProperty>
<Name>Target_Host</Name>
<Value>orcsvr1.iwavesoftware.com</Value>
</TargetProperty>
<TargetProperty>
<Name>Target Version</Name>
<Value>5.5.0.0.0</Value>
</TargetProperty>
<TargetProperty>
<Name>Line of Business</Name>
<Value>Software</Value>
</TargetProperty>
<TargetProperty>
<Name>Location</Name>
<Value>Frisco, TX</Value>
</TargetProperty>
<TargetProperty>
<Name>Comment</Name>
<Value>Testing target properties</Value>
</TargetProperty>
</TargetInfo>
</SourceInfo>
<Message>Memory Utilization is 81.791%, fallen below warning (98) and                critical (99) thresholds.</Message>
<EventURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=sdk-core-event-console-detailEvent&amp;issueID=B609743F7D2EA971E040020A78012529</EventURL>
<AutoClose>true</AutoClose>
<EventCategory>Capacity</EventCategory>
</SystemAttributes>
<EventClassSpecificAttributes>
<StringAttribute>
<Name>is_thresholdable</Name>
<Value>1</Value>
</StringAttribute>
<StringAttribute>
<Name>coll_name</Name>
<Value>LoadLinux</Value>
</StringAttribute>
<StringAttribute>
<Name>is_metric_extension</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_column_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>unit_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>cycle_guid</Name>
<Value>B609743F7D2AA971E040020A78012529</Value>
</StringAttribute>
<StringAttribute>
<Name>is_remote</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_type</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_guid</Name>
<Value>86821B5F0CE858D6E4A7F7390E88B73C</Value>
</StringAttribute>
<StringAttribute>
<Name>num_keys</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>key_value</Name>
<Value> </Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description_nlsid</Name>
</StringAttribute>
<StringAttribute>
<Name>value</Name>
<Value>81.791</Value>
</StringAttribute>
<StringAttribute>
<Name>is_long_running</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group</Name>
<Value>Load</Value>
</StringAttribute>
<StringAttribute>
<Name>is_udm</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description</Name>
</StringAttribute>
<StringAttribute>
<Name>metric_column_nlsid</Name>
<Value>host_load_memUsedPct</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_column</Name>
<Value>memUsedPct</Value>
</StringAttribute>
<StringAttribute>
<Name>unit_nlsid</Name>
<Value>em__sys__standard_percent</Value>
</StringAttribute>
<StringAttribute>
<Name>unit</Name>
<Value>%</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group_nlsid</Name>
<Value>host_load</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>severity_guid</Name>
<Value>B609743F7D30A971E040020A78012529</Value>
</StringAttribute>
</EventClassSpecificAttributes>
</EMEvent>
</EMIncident>

E.4 Reopen Example

The following example shows the XML format Enterprise Manager generates for HP Service Manager reopen operations.

<?xml version="1.0" encoding="UTF-8"?>
<EMIncident xmlns="http://xmlns.oracle.com/sysman/connector">
<ConnectorGUID>5F8B3F54D2164AA8B4D3701656FF2524</ConnectorGUID>
<TicketID>IM10257</TicketID>
<HDUser>iwave</HDUser>
<NotificationRuleOwner>SYSMAN</NotificationRuleOwner>
<NotificationRuleName>HPSM 9 Autoclose Rule</NotificationRuleName>
<ReopenTicket>Yes</ReopenTicket>
<ConnectorVariable>
<VariableName>TICKET_ID</VariableName>
<VariableValue>IM10237</VariableValue>
</ConnectorVariable>
<Property>
<Name>AuthenticationType</Name>
<Value>HTTPBasicAuthentication</Value>
</Property>
<Property>
<Name>IsNewTargetType</Name>
<Value>no</Value>
</Property>
<SystemAttributes>
<IncidentID>B6096FBDB700C905E040020A780122F7</IncidentID>
<SourceInfo>
<SourceObjInfo>
<ObjID>D93A2E4E1622013D74D9534ECB090944</ObjID>
<ObjName>orcsvr1.iwavesoftware.com</ObjName>
<ObjOwner>SYSMAN</ObjOwner>
<SourceObjType>Targets</SourceObjType>
<SourceObjSubType>host</SourceObjSubType>
</SourceObjInfo>
<TargetInfo>
<TargetGUID>D93A2E4E1622013D74D9534ECB090944</TargetGUID>
<TargetName>orcsvr1.iwavesoftware.com</TargetName>
<TargetType>host</TargetType>
<TargetTypeLabel>Host</TargetTypeLabel>
<TargetURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=TARGET_HOMEPAGE&amp;targetName=orcsvr1.iwavesoftware.com&amp;targetType=host</TargetURL>
<TargetProperty>
<Name>Target_Host</Name>
<Value>orcsvr1.iwavesoftware.com</Value>
</TargetProperty>
<TargetProperty>
<Name>Target Version</Name>
<Value>5.5.0.0.0</Value>
</TargetProperty>
<TargetProperty>
<Name>Line of Business</Name>
<Value>Software</Value>
</TargetProperty>
<TargetProperty>
<Name>Location</Name>
<Value>Frisco, TX</Value>
</TargetProperty>
<TargetProperty>
<Name>Comment</Name>
<Value>Testing target properties</Value>
</TargetProperty>
</TargetInfo>
</SourceInfo>
<IncidentURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=sdk-core-event-console-detailIncident&amp;issueID=B6096FBDB700C905E040020A780122F7 </IncidentURL>
<AutoClose>true</AutoClose>
<Owner/>
<ResolutionState>new</ResolutionState>
<Acknowledge>false</Acknowledge>
<Escalated>false</Escalated>
<EscalationLevel>0</EscalationLevel>
<Priority>None</Priority>
<Summary>Memory Utilization is 81.65%, crossed warning (44) or critical          (66) threshold.</Summary>
<CreationDate>2012-01-10T16:13:04.000-06:00</CreationDate>
<LastUpdatedDate>2012-01-10T16:13:04.000-06:00</LastUpdatedDate>
<Category>Capacity</Category>
<Severity>Critical</Severity>
<SeverityCode>CRITICAL</SeverityCode>
</SystemAttributes>
<HasEMEvent>true</HasEMEvent>
<EMEvent>
<ConnectorGUID>5F8B3F54D2164AA8B4D3701656FF2524</ConnectorGUID>
<NotificationRuleOwner>SYSMAN</NotificationRuleOwner>
<NotificationRuleName>HPSM 9 Autoclose Rule</NotificationRuleName>
<ConnectorVariable>
<VariableName>TICKET_ID</VariableName>
<VariableValue>IM10237</VariableValue>
</ConnectorVariable>
<Property>
<Name>AuthenticationType</Name>
<Value>HTTPBasicAuthentication</Value>
</Property>
<Property>
<Name>IsNewTargetType</Name>
<Value>no</Value>
</Property>
<SystemAttributes>
<EventClass>metric_alert</EventClass>
<EventID>B609743F16C20220E040020A78012524</EventID>
<SequenceID>B609743F16C30220E040020A78012524</SequenceID>
<ReportedDate>2012-01-10T16:13:04.000-06:00</ReportedDate>
<DisplayTZ>America/Chicago</DisplayTZ>
<EventName>Load:memUsedPct</EventName>
<Severity>Critical</Severity>
<SeverityCode>CRITICAL</SeverityCode>
<SourceInfo>
<SourceObjInfo>
<ObjID>D93A2E4E1622013D74D9534ECB090944</ObjID>
<ObjName>orcsvr1.iwavesoftware.com</ObjName>
<ObjOwner>SYSMAN</ObjOwner>
<SourceObjType>TARGET</SourceObjType>
<SourceObjSubType>host</SourceObjSubType>
</SourceObjInfo>
<TargetInfo>
<TargetGUID>D93A2E4E1622013D74D9534ECB090944</TargetGUID>
<TargetName>orcsvr1.iwavesoftware.com</TargetName>
<TargetType>host</TargetType>
<TargetTypeLabel>Host</TargetTypeLabel>
<TargetURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=TARGET_HOMEPAGE&amp;targetName=orcsvr1.iwavesoftware.com&amp;targetType=host</TargetURL>
<TargetProperty>
<Name>Target_Host</Name>
<Value>orcsvr1.iwavesoftware.com</Value>
</TargetProperty>
<TargetProperty>
<Name>Target Version</Name>
<Value>5.5.0.0.0</Value>
</TargetProperty>
<TargetProperty>
<Name>Line of Business</Name>
<Value>Software</Value>
</TargetProperty>
<TargetProperty>
<Name>Location</Name>
<Value>Frisco, TX</Value>
</TargetProperty>
<TargetProperty>
<Name>Comment</Name>
<Value>Testing target properties</Value>
</TargetProperty>
</TargetInfo>
</SourceInfo>
<Message>Memory Utilization is 81.65%, crossed warning (44) or               critical (66) threshold.</Message>
<EventURL>https://orcsvr1.iwavesoftware.com:7801/em/redirect?pageType=sdk-core-event-console-detailEvent&amp;issueID=B609743F16C30220E040020A78012524</EventURL>
<AutoClose>true</AutoClose>
<EventCategory>Capacity</EventCategory>
</SystemAttributes>
<EventClassSpecificAttributes>
<StringAttribute>
<Name>is_thresholdable</Name>
<Value>1</Value>
</StringAttribute>
<StringAttribute>
<Name>coll_name</Name>
<Value>LoadLinux</Value>
</StringAttribute>
<StringAttribute>
<Name>is_metric_extension</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_column_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>unit_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>cycle_guid</Name>
<Value>B609743F16BF0220E040020A78012524</Value>
</StringAttribute>
<StringAttribute>
<Name>is_remote</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_type</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_guid</Name>
<Value>86821B5F0CE858D6E4A7F7390E88B73C</Value>
</StringAttribute>
<StringAttribute>
<Name>num_keys</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>key_value</Name>
<Value> </Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description_nlsid</Name>
</StringAttribute>
<StringAttribute>
<Name>value</Name>
<Value>81.65</Value>
</StringAttribute>
<StringAttribute>
<Name>is_long_running</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group</Name>
<Value>Load</Value>
</StringAttribute>
<StringAttribute>
<Name>is_udm</Name>
<Value>0</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_description</Name>
</StringAttribute>
<StringAttribute>
<Name>metric_column_nlsid</Name>
<Value>host_load_memUsedPct</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_column</Name>
<Value>memUsedPct</Value>
</StringAttribute>
<StringAttribute>
<Name>unit_nlsid</Name>
<Value>em__sys__standard_percent</Value>
</StringAttribute>
<StringAttribute>
<Name>unit</Name>
<Value>%</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group_nlsid</Name>
<Value>host_load</Value>
</StringAttribute>
<StringAttribute>
<Name>metric_group_resbundle</Name>
<Value>oracle.sysman.eml.rsc.gen.hostMsg</Value>
</StringAttribute>
<StringAttribute>
<Name>severity_guid</Name>
<Value>B609743F16BF0220E040020A78012524</Value>
</StringAttribute>
</EventClassSpecificAttributes>
</EMEvent>
</EMIncident>

Index
A  G  H  I  M  O  P  R  T  U

A

Auto Ticketing

HP ServiceCenter Connector, 1.1

G

grace period

HP ServiceCenter Connector, 1.4

H

HP ServiceCenter

Auto Ticketing, 1.1

out-of-box templates, 5.1

HP ServiceCenter Connector

grace period, 1.4

installing, 2.1

manual ticketing, 1.2

out-of-box templates, 5.1

overview, 1

prerequisites, 1.7

ticket templates, 1.3

uninstalling, 2.2

HP ServiceCenter HelpDesk

6.1, 1.7

Web services, 1.7

I

install

offline mode, 2.1.1

installing

HP ServiceCenter Connector, 2.1

M

manual ticketing

HP ServiceCenter Connector, 1.2

O

offline mode, 2.1.1

out-of-box templates, HP ServiceCenter Connector and, 5.1

P

prerequisites

HP ServiceCenter Connector, 1.7

R

Remedy 7 Connector

replacing a template, 3.5.4

replacing a template

Remedy 7 Connector, 3.5.4

T

templates

out-of-box for HP ServiceCenter, 5.1

replacing, 3.5.4

ticket templates

HP ServiceCenter Connector, 1.3

transformation style sheets

HP ServiceCenter Connector, 1.3

U

uninstalling the HP ServiceCenter Connector, 2.2

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2015, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.