Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

These settings require administrative access to the Solace PubSub+ Mesh instance

Configuring connections from Int4 Suite to Solace PubSub+

1. Configuring API (Management) Connectivity

Finding endpoint and credentials

In Solace PubSub+ portal, find endpoint and credentials for SEMP API. It is located in Cluster manager, Manage tab, Other Management Tools and SEMP - REST API section.

image-20241017-163052.png

Create RFC destination for API (Management) Endpoint:

Connection Type: G

Target host: copy host from Public Internet field (without http:// prefix)

Path Prefix: copy path from Public Internet field

Service no. (port): as in Public Internet field

Basic authentication:

User: user id from SEMP Credentials section

Password: user password from SEMP Credentials section

SSL: Active

Maintain environment parameters for created destination in table /INT4/IFTT_PARAM

image-20241017-164124.png

2. Configuring API (Messaging) Connectivity

Finding endpoint and credentials

In Solace PubSub+ portal, find endpoint and credentials for REST Messaging API. It is located in Cluster manager / Connect tab. Select view by Protocol and Connection details will be visible under Rest section.

image-20241017-164357.png

Create RFC destination for API (Messaging) Endpoint:

Connection Type: G

Target host: copy host from Secured REST URI (without https:// prefix)

Path Prefix: empty

Service no. (port): as in Secured REST URI

Basic authentication:

User: user id from Connection Details

Password: user password from Connection Details

SSL: Active

There might be a different user created for messaging API. It can be found in Message VPN in Access Control tab

image-20241017-165105.png

image-20241017-165131.png

Maintain environment parameters for created destination in table /INT4/IFTT_PARAM

image-20241017-164124.png

3. Activate SICF service /sap/bc/int4/iftt/aem

4. Expose service /sap/bc/int4/iftt/aem in Integration Suite

image-20241017-165657.png

5. Create Rest Delivery Point

In Message VPN, Create a new REST Delivery Point. It can be found in Clients tab.

image-20241017-165753.png

6. Create REST consumer

For Created REST Delivery Point create REST consumer. Use Host, Port and credentials as defined in Integration Suite for service /sap/bc/int4/iftt/aem.

HTTP method: POST

image-20241017-170111.png

7. Create Technical Queue

Create Technical Queue INT4SuiteTech that will be used by Int4 Suite.

As a owner of the queue set #rdp/<rdp_name>. Use REST Delivery Point created in previous steps.

8. Create Queue Binding

Go back to created RDP (Clients->REST->created RDP) and create Queue Binding using name of technical queue created in previous step.

image-20241017-170839.png

As a Post Request Target put API Base Path from Integration Suite:

image-20241017-171215.png

Add Environment parameter SAP Adv. Event Mesh Post Request Target (AEM_PRT) in table /INT4/IFTT_PARAM.

Parameter value should be equal to API Base Path for service exposed in Integration Suite. By default, this parameter is created with value /int4/iftt/aem.

9. Create Request Header

For created Queue Binding create Request Header
Header name: aem-topic
Header value: ${topic()}

image-20241017-171444.png

  • No labels