update SAP integration docs

docs/components/early-access/alpha/sap/btp-integration.md → docs/components/early-access/alpha/sap/btp-plugin.md

@@ -1,15 +1,15 @@
 ---
-id: btp-integration
-title: SAP BTP integration
-description: "Learn about the Camunda SAP Business Technology Platform (BTP) integration, an artifact run on BTP."
+id: btp-plugin
+title: SAP BTP plugin
+description: "Learn about the Camunda SAP Business Technology Platform (BTP) plugin, an artifact run on BTP."
 ---
 
-The Camunda SAP Business Technology Platform (BTP) integration is an artifact run on BTP. This connects to Camunda 8 SaaS to provide:
+The Camunda SAP Business Technology Platform (BTP) plugin is an artifact run on BTP. This connects to Camunda 8 SaaS to provide:
 
 - A generic Fiori app for starting BPMN processes and displaying [Camunda Forms](/components/modeler/forms/camunda-forms-reference.md) in the Fiori design language.
 - The select exposure of SAP BTP services to [BPMN tasks](/components/modeler/bpmn/bpmn.md) and vice versa.
 - A generic endpoint to start BPMN processes with.
 
 :::note Important!
-The SAP BTP integration is an alpha feature available upon request. Visit [our contact page](/reference/contact.md) to contact us.
+The SAP BTP plugin is an alpha feature available upon request. Visit [our contact page](/reference/contact.md) to contact us.
 :::

docs/components/early-access/alpha/sap/camunda-sap-integration.md

@@ -1,14 +1,14 @@
 ---
 id: sap-integration
 title: SAP integration
-description: "Camunda's SAP integration consists of several features that can be used independently of one another: SAP OData, RFC, and BTP."
+description: "Camunda's SAP integration consists of several modules that can be used independently of one another: SAP OData, RFC, and BTP."
 ---
 
-Camunda's SAP integration consists of several features that can be used independently of one another: SAP OData, RFC, and BTP.
+Camunda's SAP integration consists of several modules that can be used independently of one another: SAP OData, RFC, and BTP.
 
-- [SAP OData Connector](./odata-connector.md): Interact with a S/4HANA or ECC System via OData v2 + v4 APIs, directly from your BPMN model.
+- [SAP OData outbound Connector](./odata-connector.md): Interact with a S/4HANA or ECC System via OData v2 + v4 APIs, directly from your BPMN model.
 - [SAP RFC outbound Connector](./rfc-connector.md): Query BAPIs and remote-enabled function modules on SAP ECC systems.
-- [SAP BTP integration](./btp-integration.md)
+- [SAP BTP plugin](./btp-plugin.md)
   - Use [Tasklist's](/components/tasklist/introduction-to-tasklist.md) forms in the Fiori UI
   - Operate SAP BTP services from [BPMN tasks](/components/modeler/bpmn/bpmn.md)
   - Inbound proxy endpoint to start process instances of BPMN models, including custom variables
@@ -21,6 +21,7 @@ These features run in the customer's [SAP BTP instance](https://www.sap.com/prod
 
 All SAP integration artifacts have the following technical requirements:
 
+- Camunda version 8.5+
 - They run on SAP BTP, Cloud Foundry environment, and thus [need the respective service](https://discovery-center.cloud.sap/serviceCatalog/cloud-foundry-runtime?region=all).
 - [(free) Destination Service](https://discovery-center.cloud.sap/serviceCatalog/destination?region=all&service_plan=lite&commercialModel=btpea) for system and service connectivity.
 - If the S/4 or ECC system is located on-premises:
@@ -41,6 +42,6 @@ No additional requirements.
 - [(free) SAP Authorization and Trust Management Service](https://discovery-center.cloud.sap/serviceCatalog/authorization-and-trust-management-service?region=all)
 - [PostgreSQL on SAP BTP, hyperscaler option](https://discovery-center.cloud.sap/serviceCatalog/postgresql-hyperscaler-option?region=all)
 
-For scaling out and up, either add multiple instances of an integration module (for example, the SAP OData Connector) or equip an integration module with more runtime memory (for example, the SAP BTP integration).
+For scaling out and up, either add multiple instances of an integration module (for example, the SAP OData Connector) or equip an integration module with more runtime memory (for example, the SAP BTP plugin).
 
 For more sophisticated tuning, all mechanisms of BTP can be applied (such as the [(free) Application Autoscaler](https://discovery-center.cloud.sap/serviceCatalog/application-autoscaler?service_plan=standard&region=all&commercialModel=btpea)), as all SAP integration artifacts fully adhere to the BTP cloud-based development standards and can be fully configured just as any custom developed apps on BTP.

docs/components/early-access/alpha/sap/odata-connector.md

@@ -50,21 +50,28 @@ Currently, only `BasicAuthentication` is supported on the Destination by the SAP
 
 A descriptor file is required to deploy the SAP OData Connector to a space in a SAP BTP subaccount. An exemplary deployment descriptor `mtad.yaml.example` is provided by Camunda. This is a standard format in SAP BTP's Cloud Foundry environment to describe the application that needs deployment. Take the following steps:
 
-1. Adjust the values to match those of the targeted Camunda 8 SaaS environment and rename it to `mtad.yaml`.
-2. Adjust the names of the SAP BTP Destination and Connectivity instances to your liking - both will be created automatically for you upon deployment. If instances in your subaccount of any of the two services exist, they will be reused.
-3. After creating the `mtad.yaml` file, log into the desired SAP BTP subaccount via the [Cloud Foundry `cli`](https://github.com/cloudfoundry/cli) (cf-cli):
+1. Find the matching [Docker image](https://hub.docker.com/r/camunda/sap-odata-connector/tags) for the targeted Camunda 8 SaaS version.  
+    The version follows the format `<C8 version major>.<C8 version minor>.<OData connector version>`.  
+   Examples:
+
+   - `8.6.0` is the OData Connector in version `0` for C8 SaaS version `8.6`
+   - `8.5.1` is the OData Connector in version `1` for C8 SaaS version `8.5`
+
+2. Adjust the values for the credentials (client ID, client secret, etc.) to match those of the API client of the targeted Camunda 8 SaaS environment and rename it to `mtad.yaml`.
+3. Adjust the names of the SAP BTP Destination and Connectivity instances to your liking - both will be created automatically for you upon deployment. If instances of the same name in your subaccount of any of the two services exist, they will be reused.
+4. After creating the `mtad.yaml` file, log into the desired SAP BTP subaccount via the [Cloud Foundry `cli`](https://github.com/cloudfoundry/cli) (cf-cli):
 
 ```shell
 $> cf login
 API endpoint: https://api.cf. ...
 ...
 ```
 
-4. Deploy the SAP OData Connector via the `cf-cli`. Note that this requires [the "multiapps" plugin of Cloud Foundry](https://github.com/cloudfoundry/multiapps-cli-plugin) to be installed on the machine the deployment runs on:
+5. Deploy the SAP OData Connector via the `cf-cli`. Note that this requires [the "multiapps" plugin of Cloud Foundry](https://github.com/cloudfoundry/multiapps-cli-plugin) to be installed on the machine the deployment runs on:
 
 ```shell
 $> cf deploy ./ # append the -f flag to shortcircuit ongoing deployments
-Deploying multi-target app archive /Some/path/sap-odata-connector.mtar in org <your-org> / space <your-space> as you@example.org ..
+Deploying multi-target app archive /some/path/sap-odata-connector in org <your-org> / space <your-space> as you@example.org ..
 ...
 Application "sap-odata-connector" started and available at "some.url.hana.ondemand.com"
 ```

docs/components/early-access/alpha/sap/rfc-connector.md

@@ -4,7 +4,7 @@ title: SAP RFC Connector
 description: "The SAP RFC Connector is a Java Spring Boot application that runs on SAP BTP."
 ---
 
-The SAP RFC [Connector](/components/connectors/introduction.md) is a [protocol and outbound Connector](/components/connectors/connector-types.md). This Connector is a Java Spring Boot application that runs on SAP Business Technology Platform (BTP).
+The SAP RFC [Connector](/components/connectors/introduction.md) is a [protocol and outbound Connector](/components/connectors/connector-types.md). This Connector is a Java Spring Boot application that runs as a `.war` on SAP Business Technology Platform (BTP).
 
 It connects to Camunda 8 SaaS, and utilizes SAP BTP's [Destination](https://learning.sap.com/learning-journeys/administrating-sap-business-technology-platform/using-destinations) and [Connectivity](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/what-is-sap-btp-connectivity) concepts to query a SAP system via the RFC protocol to interact with remote-enabled Function Modules and BAPIs.
 
@@ -20,7 +20,7 @@ For a standard overview of the steps involved in the SAP RFC Connector, see the
 
 ## Prerequisites
 
-To run the SAP RFC Connector Docker image, the following SAP infrastructure setup is required:
+To run the SAP RFC Connector, the following SAP infrastructure setup is required:
 
 - [Cloud Foundry CLI](https://github.com/cloudfoundry/cli) with the [multiapps plugin](https://github.com/cloudfoundry/multiapps-cli-plugin) installed on the machine executing the deployment.
 - SAP BTP subaccount with a [Cloud Foundry environment](https://discovery-center.cloud.sap/serviceCatalog/cloud-foundry-runtime?region=all) enabled and a [created space](https://help.sap.com/docs/btp/sap-business-technology-platform/create-spaces).
@@ -35,54 +35,33 @@ To run the SAP RFC Connector Docker image, the following SAP infrastructure setu
 
 ## Deployment to BTP
 
-Unlike other Camunda Connectors, the SAP RFC Connector must be deployed as a Java application. This is because it uses SAP's [JCo Java library](https://support.sap.com/en/product/connectors/jco.html) to connect via RFC to the configured SAP system. You must build the application yourself as the JCo library's license prohibits redistribution, so Camunda cannot pre-build it for you.
+Unlike other Camunda Connectors, the SAP RFC Connector must be deployed as a Java `.war` archive. This is because it uses SAP's [JCo Java library](https://support.sap.com/en/product/connectors/jco.html) to connect via RFC to the configured SAP system. the JCo library's license prohibits redistribution, but it is available at runtime on BTP and auto-discovered by Camunda's RFC Connector.
 
-### Building the Java application
+A descriptor file is required to deploy the SAP RFC Connector to a space in a SAP BTP subaccount. An exemplary deployment descriptor `mtad.yaml.example` is provided by Camunda. This is a standard format in SAP BTP's Cloud Foundry environment to describe the application that needs deployment.
 
-1. In the application folder, navigate to `src/main/resources/application.properties` and insert the credentials for the cluster the SAP RFC Connector should connect to:
+### Deploying to BTP
 
-```properties
-zeebe.client.cloud.region=xxx
-zeebe.client.cloud.clusterId=guid
-zeebe.client.cloud.clientId=yyy
-zeebe.client.cloud.clientSecret=zzz
-camunda.connector.polling.enabled=false
-```
-
-2. Copy the deployment descriptor `mta.yaml.example` to `mta.yaml` and enter the same credentials in the `modules.properties` scope:
-
-```yaml
-_schema-version: 3.3.0
-ID: sap-rfc-connector
-# ...
-modules:
-  - name: sap-rfc-connector
-  # ...
-  	properties:
-			ZEEBE_CLIENT_CLOUD_CLUSTERID: 'guid'
-      ZEEBE_CLIENT_CLOUD_CLIENTID: 'xxx'
-      ZEEBE_CLIENT_CLOUD_CLIENT_SECRET: 'yyy'
-      ZEEBE_CLIENT_CLOUD_REGION: 'zzz'
-```
-
-3. Adjust any property describing an infrastructure setting to your requirements. For example, if a pre-existing destination instance is to be used, adjust the respective resource name. Otherwise, the deployment will create any of the services listed in `resources` for you.
-4. Build the deployable archive via `$> mbt build`.
+1. Find the matching `.war` archive for the targeted Camunda 8 SaaS version.  
+    The version follows the format `<C8 version major>.<C8 version minor>.<OData connector version>`.  
+   Examples:
 
-### Deploying the Java application
+   - `rfc-8.6.0.war` is the RFC Connector in version `0` for C8 SaaS version `8.6`
+   - `rfc-8.5.1.war` is the RFC Connector in version `1` for C8 SaaS version `8.5`
 
-1. Log in to the desired SAP BTP subaccount via the [Cloud Foundry `cli`](https://github.com/cloudfoundry/cli) (cf-cli):
+2. Adjust the values for the credentials (client ID, client secret, etc.) to match those of the API client of the targeted Camunda 8 SaaS environment and rename it to `mtad.yaml`.
+3. Log into the desired SAP BTP subaccount via the [Cloud Foundry `cli`](https://github.com/cloudfoundry/cli) (cf-cli):
 
 ```shell
 $> cf login
 API endpoint: https://api.cf. ...
 ...
 ```
 
-2. Deploy the SAP RFC Connector via the `cf-cli`. Note that this requires [the "multiapps" plugin of Cloud Foundry](https://github.com/cloudfoundry/multiapps-cli-plugin) to be installed on the machine the deployment runs on.
+4. Deploy the SAP RFC Connector via the `cf-cli`. Note that this requires [the "multiapps" plugin of Cloud Foundry](https://github.com/cloudfoundry/multiapps-cli-plugin) to be installed on the machine the deployment runs on.
 
 ```shell
-$> cf deploy mta_archives/*.mtar # append the -f flag to shortcircuit ongoing deployments
-Deploying multi-target app archive <path/to/>.mtar in org <your-org> / space <your-space> as you@example.org ..
+$> cf deploy ./ # append the -f flag to shortcircuit ongoing deployments
+Deploying multi-target app archive /some/path/sap-rfc-connector in org <your-org> / space <your-space> as you@example.org ..
 ...
 Application "sap-rfc-connector" started and available at "some.url.hana.ondemand.com"
 ```