Add Service Manager as a supplier

To enable Service Portal to connect to Service Manager, you must add Service Manager as a supplier.

Important Service Portal supports only the SM backend system type and only one supplier of this type.

Suppliers are associated with organizations, and the Organization Administrator manages the supplier systems for his organization.

Note If HTTPS is used for communication between Service Portal and Service Manager, HTTPS must be configured. See (Optional) Configure two-way SSL between Service Portal and Service Manager for instructions.

The Organization Administrator can create new suppliers in Service Portal. To add Service Manager as a new supplier, follow these steps:

  1. Log in to Service Portal as the orgadmin user by opening a browser and specifying the following URL:

    https://<ServicePortal_HOSTNAME>:9000/org/CONSUMER

    Replace ServicePortal_HOSTNAME with the fully qualified domain name of Service Portal.

  2. From the Launchpad in Service Portal, click the Suppliers application.
  3. In the Suppliers view, click Add Supplier.
  4. In the Add Supplier dialog, do the following:
    1. In the Display Name field, enter a display name for the new supplier. For example, enter SM9.52.
    2. Select SM as the Backend System Type, and then select Use As Default Support System.

    3. Select None in the Pricing Service field.
  5. After the Backend System Type is selected, additional General fields are displayed, such as integration account credentials and end-point URLs. Fill in and select the required General fields as described in the following table.

    Field(s) Description
    Endpoint

    Base url for SM web services in the form http://<host>:<port>/SM

    For example:

    http://mysmhost.mycompany.net:13082/SM

    With Process Designer Select this option.
    SM Version

    This is the SM version number.

    Select 9.52.

    Locale

    Expected in the language tag format like pt or pt-BR. Used for SM catalog locale and for locale of case exchange-related messages in SM.

    If left blank, English is used.

    URL escaping charset

    If the supplier needs REST URL encoded by a charset different from the default value of UTF-8, enter the charset code here (for example "windows-1252").

    For a Service Manager supplier, leave this field blank.

    Login name

    Password

    Enter the login name and password of the Service Manager user account to be used for Service Portal to access Service Manager through web services calls.

    Note This user account must have system administration privileges in Service Manager, and the password cannot be blank. As best practice, create a dedicated user account for this purpose.

    LWSSO domain Enter the domain of the Service Manager Server host.
    LWSSO init string

    This must be a value that matches the initString value in the lwssofmconfig.xml file located in the Service Manager Server's RUN directory. Additionally, this value must contain both numbers and letters and must be 32 characters in length.

    Protocol

    Host name

    Port

    These are the protocol (http or https), host name, and port of your proxy server, respectively.

    If you are not using a proxy server, leave these fields blank.

  6. Click Create in the Add Supplier dialog to finish and save your changes. The new supplier and its properties are displayed.
  7. Configure LW-SSO in the Service Manager Server and Service Portal.

  8. Run the Service Portal Diagnostics application to validate connectivity between Service Portal and Service Manager. To do this, follow these steps:

    1. Log in to Service Portal as the admin user (https://<Service Portal host name>:9000/org/Provider).
    2. Click the Diagnostics application, and them click Configuration Check in the Supplier Detail view for an HPE Service Manager instance.

Tip Next, If you want to enable two-way SSL between Service Manager and Service Portal, go to (Optional) Configure two-way SSL between Service Portal and Service Manager; otherwise you should directly go to Configure shopping, ticketing, Knowledge Management, hot news, Change approval, and search.