Loading RA Solutions into Automic SaaS

Products

• Automic SaaS

Issue/Introduction

An RA Solution like Oracle EBS needs to be loaded into an Automic SaaS system.  How can this be accomplished?

Environment

Automic SaaS

Resolution

Loading the solution is something that should be done from your end with a curl command which will use the system's REST endpoint.  Here are the steps to do so:

Download the RA solution from downloads.automic.com
Unzip the zip file and move the [agent_type]Agent_solution.jar file to a server that has a white-listed IP and can reach the REST API endpoint (this was sent in the initial email and should have a URL like https://rest-[tenant_id].example.com)
From the server where the *_solution.jar file now resides, run a curl command like:

For Windows:

curl --request POST --data-binary "@[agent_type]Agent_solution.jar" -u "0/{Client 0 username}/{Client 0 user department}" --header "Content-Type:application/octet-stream" --cacert "C:\{path to JCP cert}" https://{REST API URL}/ae/api/v1/0/system/ra-solutions/upload

For Linux:

curl --request POST --data-binary '@[agent_type]Agent_solution.jar' -u '0/{Client 0 username}/{Client 0 user department}' --header 'Content-Type:application/octet-stream' --cacert '/{path to JCP cert}' https://{REST API URL}/ae/api/v1/0/system/ra-solutions/upload

Please note that you will need to replace:

• {Client 0 username}/{Client 0 user department} with the username and department used to log in to client 0 like: USERNAME/SAAS
• {path to JCP cert} with the path to the certificate to connect to the REST JCP
• {REST API URL} with the URL from the initial email

This should load the solution into client 0 and allow for that type of agent to be created.

Additional Information

IMPORTANT: Make sure to use https and the --cacert option to connect to the REST endpoint! Note that if you don't use TLS your user/password is only base64 encoded, which is readable by any attacker.