--- title: Use the SAP Solution Manager Pull connector description: 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. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/event-management/sap-pull-connector.html release: australia product: Event Management classification: event-management topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Enable SAP connector configurations, Configure SAP Solution Manager connector, Configure a pull connector, Configure Event Management connectors, Event Management Integrations, Configure, Event Management, ITOM AIOps, IT Operations Management] --- # Use the SAP Solution Manager Pull connector 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 **All** > **Event Management** > **Event 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.| 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**. \[Omitted image "sap-solman-pull-example.png"\] Alt text: Event generated by the example instance source PSM\_001 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. The following table lists the actions you can perform in Event Management, and the resulting updates occurring in SAP Solution Manager. |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.| 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. **Parent Topic:**[SAP configurations for the SAP Solution Manager connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/sap-manager-connector.md)