You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,12 +63,12 @@ cds:
63
63
### Setting Up the Broker
64
64
65
65
The broker itself must be created manually in SAP Integration Suite, advanced event mesh and trust must be established to the respective application in [SAP Cloud Identity Services](https://help.sap.com/docs/cloud-identity-services/cloud-identity-services), both for the Solace broker and the [SEMP API](https://docs.solace.com/Admin/SEMP/Using-SEMP.htm).
66
-
For details, please consult SAP Integration Suite, advanced event mesh's documentation at [help.pubsub.em.services.cloud.sap](https://help.pubsub.em.services.cloud.sap/Get-Started/get-started-lp.htm).
66
+
For details, please consult SAP Integration Suite, advanced event mesh's documentation at [help.pubsub.em.services.cloud.sap](https://help.pubsub.em.services.cloud.sap/Get-Started/get-started-lp.htm) and [help.sap.com](https://help.sap.com/docs/sap-integration-suite/advanced-event-mesh).
67
67
68
-
// TODO: where to put?
69
-
You need to manually configure SAP Integration Suite, advanced event mesh to allow your application to connect to the broker by following the [steps in the documentation](https://help.sap.com/docs/sap-integration-suite/advanced-event-mesh/cap-plugin-for-sap-integration-suite-advanced-event-mesh).
68
+
Specifically, you need to configure SAP Integration Suite, advanced event mesh to allow your CAP application to connect to the broker.
69
+
For this, follow guide [CAP Plugin for SAP Integration Suite, Advanced Event Mesh](https://help.sap.com/docs/sap-integration-suite/advanced-event-mesh/cap-plugin-for-sap-integration-suite-advanced-event-mesh).
70
70
71
-
The broker's credentials must be provided via a [user-provided service instance](https://docs.cloudfoundry.org/devguide/services/user-provided.html) with the name `advanced-event-mesh` and credentials in the following format:
71
+
Finally, the broker's credentials must be provided via a [user-provided service instance](https://docs.cloudfoundry.org/devguide/services/user-provided.html) with the name `advanced-event-mesh` and credentials in the following format:
72
72
73
73
```jsonc
74
74
{
@@ -80,13 +80,14 @@ The broker's credentials must be provided via a [user-provided service instance]
80
80
"endpoints": {
81
81
"advanced-event-mesh": {
82
82
"uri": "https://<broker host>:<port>",
83
-
"smf_uri": "wss://<broker host>:<port>"
83
+
"amqp_uri": "amqps://<broker host>:<port>"
84
84
}
85
85
},
86
86
"vpn": "<vpn>"
87
87
}
88
88
```
89
89
90
+
// TODO: adjust for CAP Java
90
91
To troubleshoot connection issues, set log level for component `messaging` to `DEBUG`.
91
92
Check [`cds.log()`](https://cap.cloud.sap/docs/node.js/cds-log) for how to maintain log levels.
0 commit comments