Camunda is a workflow and decision automation platform. It's similar to Openedge BPM.
Current Camunda Akioma Environment is: https://camunda.akiomacloud.de/
The installation was done as docker image on our docker server. Current user: "demo" password is our common password.
For the Camunda integrationwe used their REST API, which allows end users to quickly create/delete/fetch tasks/processes etc.
For more info regarding the Camunda API see: https://docs.camunda.org/manual/7.3/api-references/rest/
Current Akioma Kinvey console URL: https://kvy-eu3-console.kinvey.com/
From here, you can view/edit applications, services, custom endpoints/functions and test kinvey collections.
First, make sure kinvey cli is installed on your machine. If not, you can use the following command: npm install kinvey-cli
When deploying the Kinvey service locally, you need to have a config file in the current folder from which you are deploying the service. The file name will be '.kinevy'. This will be configured using the kinvey init command.
Once you run this command, you will need to supply your kinvey console credentials and the Kinvey instance ID (optional - in our case this is kvy-eu3).
Alternatively, if you already have a profile configure, you can use it with the command kinvey profile use.
In order to connect the application to to Kinvey, we need to set 3 session properties in the pasoe-config.xml file from the ofr-config project: kinveyAppSecret, kinveyInstanceId, kinveyAppKey.
The above 3 properties can be found by selecting an environment within a Kinvey App and clicking on the 3 dots:
After you set the properties in the file, restart the PASOE.
After we set the Kinvey parameters in the pasoe-config.xml file, for the dataSource we can use the SimpleSwatBusinessEntity.
Here, we would need to set 2 attributes:
Custom endpoints are defined on the Application Environment settings. They can be called from the frontend using akioma.InvokeServerTask. A custom endpoint is linked to a service flex function. Essentially, when a custom endpoint is called, we are calling the the flex function defined in the service.
Custom endpoints can be defined on the application environment from the Business Logic → Custom Endpoints:
Click on the add new Endpoint button, give the new endpoint a name and select the Business Logic Type. In our case, that is Microservice (Execute a handler function running inside a Flex Services Runtime service). Once the endpoint is created, select the service, then environment and finally the handler function:
Calling a Kinvey custom endpoint is done using akioma.InvokeServerTask.
The only thing we need to specify is the methodType: "kinvey" in the request.
akioma.invokeServerTask({
name: "completeTask",
methodType: "kinvey",
paramObj: {
id: "id-of-task"
}
}).then(resp => { //process response// } );