Skip to content

Commit b24ccfc

Browse files
committed
streamline with @cap-js/advanced-event-mesh
1 parent bbbf675 commit b24ccfc

File tree

1 file changed

+65
-11
lines changed

1 file changed

+65
-11
lines changed

README.md

Lines changed: 65 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -12,35 +12,89 @@ CDS plugin providing integration with SAP Integration Suite, advanced event mesh
1212

1313

1414

15-
## Requirements and Setup
15+
## Table of Contents
1616

17-
See [Getting Started](https://cap.cloud.sap/docs/get-started/in-a-nutshell?impl-variant=java) on how to jumpstart your development and grow as you go with SAP Cloud Application Programming Model.
17+
- [About this project](#about-this-project)
18+
- [Requirements](#requirements)
19+
- [Setup](#setup)
20+
- [Setting Up the Broker](#setting-up-the-broker)
21+
- [Broker Validation](#broker-validation)
22+
- [Support, Feedback, Contributing](#support-feedback-contributing)
23+
- [Security / Disclosure](#security--disclosure)
24+
- [Code of Conduct](#code-of-conduct)
25+
- [Licensing](#licensing)
1826

1927

20-
### CDS Plugin
2128

22-
The usage of CAP Java plugins is described in the [CAP Java Documentation](https://cap.cloud.sap/docs/java/building-plugins#reference-the-new-cds-model-in-an-existing-cap-java-project). Following this documentation this plugin needs to be referenced in the `srv/pom.xml` of a CAP Java project:
29+
## Requirements
30+
31+
See [Getting Started](https://cap.cloud.sap/docs/get-started/in-a-nutshell?impl-variant=java) on how to jumpstart your development and grow as you go with SAP Cloud Application Programming Model (CAP).
32+
To learn about messaging in CAP, please consult the guide on [Events & Messaging](https://cap.cloud.sap/docs/guides/messaging/).
33+
34+
35+
36+
## Setup
37+
38+
Install the plugin by adding it to the dependencies of your CAP Java project:
2339

2440
```xml
41+
<!-- srv/pom.xml -->
2542
<dependency>
26-
<groupId>com.sap.cds</groupId>
27-
<artifactId>cds-feature-advanced-event-mesh</artifactId>
28-
<version>${latest-version}</version>
43+
<groupId>com.sap.cds</groupId>
44+
<artifactId>cds-feature-advanced-event-mesh</artifactId>
45+
<version>${latest-version}</version>
2946
</dependency>
3047
```
3148

3249
The latest version can be found in the [changelog](./CHANGELOG.md) or in the [Maven Central Repository](https://central.sonatype.com/artifact/com.sap.cds/cds-feature-advanced-event-mesh/versions).
50+
The usage of CAP Java plugins is described in the [CAP Java Documentation](https://cap.cloud.sap/docs/java/building-plugins#reference-the-new-cds-model-in-an-existing-cap-java-project).
51+
52+
Then, set the `kind` of your messaging service to `aem`:
3353

54+
```yaml
55+
# srv/src/main/resources/application.yaml
56+
cds:
57+
messaging.services:
58+
- name: "messaging-name"
59+
kind: "aem"
60+
```
61+
62+
63+
### Setting Up the Broker
3464
35-
### WHAT ABOUT THE MESSAGING KIND?
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).
3667
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).
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:
72+
73+
```jsonc
74+
{
75+
"authentication-service": {
76+
"tokenendpoint": "https://<ias host>/oauth2/token",
77+
"clientid": "<client id>",
78+
"clientsecret": "<client secret>"
79+
},
80+
"endpoints": {
81+
"advanced-event-mesh": {
82+
"uri": "https://<broker host>:<port>",
83+
"smf_uri": "wss://<broker host>:<port>"
84+
}
85+
},
86+
"vpn": "<vpn>"
87+
}
88+
```
3789

38-
### COPY OUTCOME OF https://github.com/cap-js/advanced-event-mesh/pull/32
90+
To troubleshoot connection issues, set log level for component `messaging` to `DEBUG`.
91+
Check [`cds.log()`](https://cap.cloud.sap/docs/node.js/cds-log) for how to maintain log levels.
3992

4093

41-
### SAP Integration Suite, Advanced Event Mesh
94+
### Broker Validation
4295

43-
For details on how to use SAP Integration Suite, advanced event mesh, please see the [SAP Integration Suite, advanced event mesh documentation](https://help.sap.com/docs/sap-integration-suite/advanced-event-mesh/cap-plugin-for-sap-integration-suite-advanced-event-mesh).
96+
Your app must be bound to an instance of service `SAP Integration Suite, advanced event mesh` with plan `aem-validation-service`.
97+
Please see [Validation of VMR Provisioning](https://help.sap.com/docs/sap-integration-suite/advanced-event-mesh/validation-of-vmr-provisioning) for more information.
4498

4599

46100

0 commit comments

Comments
 (0)