on 02-09-2022 5:19 AM
Hello Experts,
we are creating subscription for Event Mesh in SAP BTP cockpit, we need to upload JSON file which contains the following data.
What should I fill in "emname" & "namespace"?
We are replicating Quotes from SAP CPQ to SAP CPI, where we are using event mesh.
{
"emname": "<message-client-name>", // fill in your message client name
"namespace": "<your-namespace>", // fill in your namespace
"version": "1.1.0",
"options": {
"management": true,
"messagingrest": true,
"messaging": true
},
"rules": {
"queueRules": {
"publishFilter": [
"${namespace}/*"
],
"subscribeFilter": [
"${namespace}/*"
]
},
"topicRules": {
"publishFilter": [
"${namespace}/*"
],
"subscribeFilter": [
"${namespace}/*"
]
}
}
}
Hi,
the detailed description of all the fields in the service descriptor can be found in the documentation.
In short:
emname: It specifies the name of the message client. emname is the name displayed in the Event Mesh admin UI to identify messaging clients. We recommend that you use the same value for service instance name and emname (as mentioned here).
namespace: It ensures that every message client within a subaccount is unique. The queues managed by the message client and topics used to publish by the message client have the namespace as prefix. Use semantically relevant namespaces when defining your service descriptor.
As a general description, each Event Mesh service instance that you create inside a CF subaccount equals to one messaging client that has access the the event broker available on CF subaccount level. For this messaging client your a defining a name, a namespace (all topics and queues will start with this namespace) and a set of rules what this client is allowed to access inside the event broker.
For your scenario you would create two Event Mesh instances. One for the CPQ system (as event provider) and another one for CPI (as the event consumer).
Best regards,
Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.