Action Handlers are integration components of the HIRO™ system. They are used to\ninvoke actions on target systems. This document walks you through the configuration procedure of the HIRO™ SAP™ Action Handler.
\nFrom a technical perspective, the SAP™ Action Handler is an additional capability using the HIRO™ HTTP Action Handler, which is included in the Standard Docker image for Action Handlers.
\nBefore you can configure the SAP Action Handler, make sure the following prerequisites are fulfilled:
\nYou have configured your SAP according to the HIRO™ for SAP Operations - Implementation Guide. This document will be provided to you by us in the implementation phase of your project.
\nYou have followed the instructions in Standard Docker image for Action Handlers to setup the Action Handler Docker container. Please ensure that you are able to process HTTP requests from HIRO.
\nArago has a SAP demo instance, which customers may use on request for testing purposes. We can provide you with the IP and credentials for this demo instance.
\nIn order to make use of the SAP™ Action Handler capability, you need to add the following handler definition to your docker composition file:
\nenvironment:\n AH_CONFIG: >\n {\n \"handlers\": [\n {\n \"name\": \"SAPHandler\",\n \"capability\": \"SAPRequest\",\n \"implementation\": \"HTTP\",\n \"url\": \"https://<IP of your SAP System>:<Port>/jsonbc/$${function}\",\n \"params\": \"$${destination}\",\n \"body\": \"$${parameters}\",\n \"insecure\": \"false\",\n \"method\": \"post\",\n }\n ]\n }Please refer to How to configure capabilities in the standard Action Handler (Docker image) for details on the configuration map.
\nIn case your SAP System requires a secure connection using certificates, you need to include these in your handler configuration as well:
\nenvironment:\n AH_CONFIG: >\n {\n \"handlers\": [\n {\n \"name\": \"SAPHandler\",\n \"capability\": \"SAPRequest\",\n [...]\n \"client_certificate\": \"/<virtual path to certificate>/cert.crt\",\n \"client_key\": \"/<virtual path to certificate>/cert.key\"\n }\n ]\n }Also, please ensure the certificates are either included in your docker image, or accessible as volumes or alike.\nHere is an example using volumes in docker-compose.yml:
environment:\n AH_CONFIG: >\n {...}\nvolumes:\n - type: bind\n source: /<actual path to certificate>/cert.crt\n target: /<virtual path to certificate>/cert.crt\n - type: bind\n source: /<actual path to certificate>/cert.key\n target: /<virtual path to certificate>/cert.keyOnce you have successfully configured and started the Action Handler, you can test it by triggering the follow KI from HIRO™:
\non\n ogit/_id\nwhen\n ProcessIssue == \"TestSAPRequest\"\ndo\n stdout: LOCAL::OUTPUT,\n stderr: LOCAL::ERROR,\n rc: LOCAL::SYSTEMRC = action(\"SAPRequest\",\n function :\"RFC_GET_SYSTEM_INFO\"\n )\n if LOCAL::SYSTEMRC == 0 then\n log(\"SUCCESS: ${LOCAL::OUTPUT}\")\n else\n log(\"ERROR ${LOCAL::ERROR}\")\n end\n\n stdout: LOCAL::OUTPUT,\n stderr: LOCAL::ERROR,\n rc: LOCAL::SYSTEMRC = action(\"SAPRequest\",\n function :\"RFC_READ_TABLE\",\n parameters: '{\n \"QUERY_TABLE\": \"T000\"\n }'\n )\n if LOCAL::SYSTEMRC == 0 then\n log(\"SUCCESS: ${LOCAL::OUTPUT}\")\n else\n log(\"ERROR ${LOCAL::ERROR}\")\n end\n\n delete(ProcessIssue)