Docs / Connectors / Solace Platform

Solace Platform Connector

The ASAPIO Integration Add-on connects SAP S/4HANA and SAP ECC directly to Solace PubSub+ using both REST and AMQP protocols. Events are published in real time without middleware — supporting dynamic topic routing, high-availability configurations, and inbound message consumption.

Protocol Support

Protocol	Cloud Adapter	Use Case
REST	`/ASADEV/CL_ACI_SOLACE_HANDLER`	Standard HTTP-based publishing to Solace REST messaging endpoints. Supports OAuth 2.0 authentication and high-availability secondary failover.
AMQP	`/ASADEV/CL_S4_SOLACE_HANDLER`	AMQP 1.0 protocol for guaranteed message delivery with acknowledgement. Requires AMQP-enabled Solace message VPN.

Create an outbound interface (Event Studio)

Event Studio is the recommended configuration path. It uses the Data Catalog to discover available SAP business objects and guides you through connector setup without direct SPRO navigation.

Open Event Studio from the ASAPIO Launchpad.
In the Data Catalog, locate the business object to stream.
Click Create Event and select Solace PubSub+ as the target connector.
Select the protocol: REST or AMQP.
Select or create a Connection Instance pointing to the Solace message VPN endpoint.
Configure the Header Attributes (see below) — these apply to both Event Studio and SAP GUI paths.
Set the Outbound Method: Simple Notify, Message Builder, or Packed Load.
Activate the event and verify delivery from the Event Studio monitor.

After creating the interface in Event Studio, see Header Attributes for message configuration and Dynamic Topics for advanced routing.

Header Attributes

Header attributes control topic routing and message behaviour. They are identical whether the event is configured via Event Studio or via SAP GUI transaction.

Attribute	Description
`SOLACE_TOPIC`	Target topic path on the Solace message VPN (e.g., `sap/s4/purchaseorder/created`)
`SOLACE_VPN`	Name of the Solace message VPN
`SOLACE_CONTENT_TYPE`	MIME content type of the message (default: `application/json`)
`SOLACE_DELIVERY_MODE`	Delivery mode: `DIRECT` or `PERSISTENT`
`SOLACE_CORRELATION_ID`	Optional correlation identifier mapped from an SAP document field

SAP Connection Setup (in SAP Gui) — REST Protocol

Step 1 — Create RFC Destinations (SM59)

Create two HTTP RFC destinations of type G:

One for the Solace REST messaging endpoint
One for the OAuth 2.0 token endpoint

SM59 RFC destination for Solace REST endpoint

SM59 RFC destination for Solace OAuth endpoint

Step 2 — Import SSL Certificate (STRUST)

Import the Solace endpoint SSL certificate into the SAP SSL client identity in transaction STRUST:

Step 3 — Import BC-Set (SCPR20)

Import the ASAPIO Solace framework BC-Set:

BC-Set: /ASADEV/ACI_BCSET_FRAMEWORK_SOLC

SCPR20 BC-Set import for Solace connector

Step 4 — Configure Cloud Adapter

Navigate to SPRO → ASAPIO Integration → Connector Configuration and set:

Cloud Adapter: /ASADEV/CL_ACI_SOLACE_HANDLER

Step 5 — Create Connection Instance

Create a connection instance using transaction /ASADEV/ACI, pointing to the Solace REST RFC destination.

For high-availability deployments, configure the secondary (HA) RFC destination in the same instance:

Step 6 — Configure Default Values

Set the OAuth token endpoint RFC, client ID, and message VPN as default values on the connection instance:

Store the OAuth client secret in the SAP Secure Store:

Solace OAuth client secret in Secure Store

Create an outbound interface (SAP Gui)

All three outbound methods are available for the Solace REST connector:

Method	Function Module	Description
Simple Notify	`/ASADEV/ACI_GEN_NOTIFY_SOLACE`	Lightweight notification with SAP document key fields only
Message Builder	`/ASADEV/ACI_GEN_VIEWEXT_SOLACE` + `/ASADEV/ACI_GEN_VIEWFRM_SOLACE`	Full CDS-based payload extraction configured via the Payload Designer
Packed Load	Batch delivery	Accumulates multiple events into a single packed message before publishing

Message Type Configuration

Event Linkage (SWE2)

Packed Load Header Attributes

When using Packed Load, configure the additional delivery attributes:

Attribute	Description
`SOLACE_TOPIC`	Target topic for the packed batch
`SOLACE_BATCH_SIZE`	Number of records per delivery batch
`SOLACE_FILE_FORMAT`	Format of the packed message: `JSON` or `CSV`
`SOLACE_DELIVERY_MODE`	Delivery mode for the packed batch

Dynamic Topics

The Solace connector supports dynamic topic construction, allowing the topic path to include values from the SAP business document (e.g., company code, document type, or plant).

Field Mapping

Conversion Methods

Monitor Display

Dynamically resolved topics are visible in the ASAPIO message monitor for tracing and troubleshooting:

SAP Connection Setup (in SAP Gui) — AMQP Protocol

The AMQP connector uses a separate cloud adapter and a dedicated RFC destination configured for TCP (not HTTP). AMQP delivers guaranteed messaging with end-to-end acknowledgement.

Step 1 — Create AMQP RFC Destination (SM59)

Create a TCP/IP RFC destination pointing to the Solace AMQP port (typically 5671 for TLS):

Step 2 — Configure Cloud Adapter

Cloud Adapter: /ASADEV/CL_S4_SOLACE_HANDLER
Cloud Type: SOLACEAMQP

Step 3 — Create AMQP Connection Instance

Step 4 — Configure Default Values

Set the AMQP username as a default value on the connection instance:

AMQP instance default values with username

Store the AMQP password in the SAP Secure Store:

AMQP Inbound Object

Configure the inbound object to receive messages from Solace over AMQP. Set the source address attribute AMQP_SOURCE to the Solace queue name to consume from:

AMQP Inbound Header Attributes

Demo & Resources