HP Service Manager Configuration guide for integration with Precision Bridge

Please Note: Precision Bridge currently supports HP Service Manager REST API v9 only.

Pre-configuration steps

1. Install Precision Bridge client version 5.4 or later.
2. Make sure access to HPSM with System Administrator privileges is available to complete the below steps, either via the web client or the Windows client.

Before using Precision Bridge client, the below configuration steps need to be completed on your HP Service Manager instance:

1. Precision Bridge client will need an integration user to connect to HP Service Manager using REST web services. This user can be a user with ‘System Administrator’ privileges, or a non-admin user assigned with a new role ‘pbridge’. Please proceed to step 4, if this integration user already has System Administrator privileges.
2. Create a new role 'pbridge' by importing the ‘pbridge-sec.unl’ file from the Precision Bridge installation directory (C:\Program Files\Service Management Integrations\Precision Bridge <version>\resources\hpsm\load_files). This role has view-only rights to all the included areas. In case attachments need to need to be migrated, the corresponding areas such as Incident, Problem, and Change need to be updated to Update 'Always' from Update 'Never' in the role, although these areas are never updated.
3. Please follow the below steps to load the file into the server using the web client. Alternatively, similar steps can be used using the windows client.
   • Log in to HP Service Manager web client using a user with System Administration privileges. The default web client URL is of the format:

                        http://myserver.mydomain.com:myport/SM/index.do 

                           

• • • • Go to Tailoring->Database Manager and select ‘Import/Load’ from the dropdown as shown   below:

                           

                         

• • Choose the ‘pbridge-sec.unl’ file from Precision Bridge installation directory (C:\Program Files\Service Management Integrations\Precision Bridge <version>\resources\hpsm\load_files). and click on List Contents (to verify) and then Load FG to load and import the file record.

                       

3. Create a new operator record or use an existing operator and assign the above role to it. Please note that a contact record has to be created before an operator record can be created for it. Please see below the sample operator record with ‘pbridge’ role:

         

4. The number of user sessions( Max Logins or Unlimited Sessions) has to be set in the operator record, especially if the user is being shared for other operations:

         

5. Create 2 new ‘External Access Definition’ records that will be used by Precision Bridge REST integration. Load the records from the ‘pbridge-extaccess.unl’ file provided in the Precision Bridge installation directory (C:\Program Files\Service Management Integrations\Precision Bridge <version>\resources\hpsm\load_files). using the same procedure as above.
6. Please verify if the External Access Definition records have been created successfully on the server. Go to Tailoring Tools-> Web Services-> Web Service Configuration and search for Service Name=’Precision Bridge Integration’. There should be 2 records on the server:

       

       

7. Please verify if ‘RESTful Enabled’ and ‘Attachments’ have been enabled on your server in the ‘External Access Definition’ form, for the records and related attachments that you wish to migrate:

Note: Precision Bridge will only retrieve those 'External Definition Access' fields that are configured to be retrieved by the REST API in the definition record. In order to see more fields in the client for a specific table, the External Access Definition will have to be changed as below:

• • Select a field from the field list to include in the 'Field' section. Add a label for it in the 'Caption' and a 'Type' that is most suited for this field or it can be left blank if this information is not available. Below is an example from the External Access Definition record for table: 'cm3r'.