---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Use the SAP Solution Manager Pull connector

# Use the SAP Solution Manager Pull connector {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

The SAP Solution Manager Pull connector sends information from Event Management to the SAP Solution Manager. The Pull connector sends responses
received from a Push connector in a bi-directional environment.

## Before you begin

Role required: evt_mgmt_admin

## Procedure

1. Navigate to AllEvent ManagementEvent Connectors (Pull)Connector Instances.
2. Click New.  
   The Connector Instance New Record page appears.
3. Enter values in the required fields, which are indicated by a red asterisk.

   | Field | Description |
   | Name | Descriptive name for the connector. |
   | Connector definition | Search for and select SAP Solution Manager. |
   | Credential | Select Basic auth for basic authentication. |
   | Host IP | The SAP Solution Manager IP address. |
   |-|-|

   {#sap-pull-connector__choicetable_rhk_dv4_23b}  
   The Connector Update Queues table \[em_connector_update_queue\] lists manual updates of alerts and sends an event to the SAP Solution Manager, using the Pull interface.  
   Note:  
   When adding bi-directional functionality for a Push connector, the Connector Instance name must match the Source Instance field of the event generated by that source. The Connector Instance field value is a combination of `SID + _ + Mandant`.

   For
   example, the following image displays an event generated by the instance
   source PSM_001. To enable sending information
   back, you would have to name your connector instance
   PSM_001.

   <br />

4. Set the following values for the connector instance:  
   * Client: Represents the client value in SAP, usually 001.
   * Port: The SAP Solution Manager WebService port. Default value = 8000.

   {#sap-pull-connector__ul_arw_3j1_xhb}

   The following table lists the actions you can perform in Event Management, and the resulting updates occurring in SAP
   Solution Manager.
   {#sap-pull-connector__table_kld_3gd_rhb__entry__2}

   | Action in Event Management | Result in SAP Solman |
   |-|-|
   | Close an alert. | Confirms an alert in the alert inbox. The alert is removed. |
   | Select the Maintenance setting in an alert. | Adds a comment indicating that the alert is in Maintenance mode. |
   | Clear the Maintenance setting in an alert. | Removes the Maintenance mode comment. |
   | Select the Acknowledged setting in an alert. | Adds a comment indicating that the alert is in the Acknowledged mode. |
   | Clear the Acknowledged setting in an alert. | Removes Acknowledged mode comment. |
   [Table 1. Event Management actions and SAP Solution Manager updates]

   {#sap-pull-connector__table_kld_3gd_rhb}

   Note the following behaviors:
   * The Update queue business rule in the Alert table identifies each manual update of the alert and updates the connector queue accordingly. By default, changes to all alert fields are tracked.
   * The Event Management --- Queue Connector Processor job removes alert changes from the queue and sends them to the MID Server. By default, Event Management performs this dequeue process in batches of 1,000 alerts. You can configure the batch size by setting the `evt_mgmt.max_update_source_records` property.
   {#sap-pull-connector__ul_rjt_dx4_23b}

*[\>]: and then