Creating a REST service

To create the REST service:

1. Open the designer.
2. In the library, select Exposed Automation Services > + > REST service.
3. Name the REST service.
   The REST service editor opens.
4. Add an operation for each business function that you want to expose. To add an operation, click Add.
   In the operation details, name the operation and specify the service flow that provides the implementation for the operation. For the implementation, you can:

   • Create a new service flow by clicking New.
   • Select an existing service flow by clicking Select.

   For more information about service flows and how to create them, see Creating a service flow.
   
   
   Inputs and outputs can use the simple types that are included with the product, such as String, Integer, Boolean, Decimal, Date, or Time, from the System Data toolkit or custom business objects. Types from other system toolkits are not supported.
   Tip: Make sure that there aren't multiple business objects with the same name in the dependency chain of your exposed REST automation service and its interface.
   Note: Only ASCII characters are allowed in the following:

   • The name of an operation
   • The names of the business objects that are referenced by the inputs or outputs of the automation service implementation (for example, service flow)

   Rationale: From the exposed REST automation service definition, a valid OpenAPI definition is generated that adheres to the respective specifications.
   After you edit the REST service, click Save or Finish Editing.
5. Optional: For consumers other than automation service consumers:

   To develop an external client, see the OpenAPI definition for the REST service as it exists and is available in the development environment, by clicking the OpenAPI definition URL in the Behavior section of the REST service editor.

Results

To invoke a REST service, the appropriate snapshot must be activated.

In the development environment, the REST service on the tip or the default track can be invoked directly. Make sure to make the track the default to open the OpenAPI definition URL in REST service directly.

In a test, staging, or production runtime environment, the consumer can either invoke the REST automation service from the default snapshot or consume the REST automation service from a dedicated snapshot.

You can get the OpenAPI definition for your REST service in a runtime environment from the following URL:

http://host_name[:port]/[custom_prefix/]automationservices/rest/process_app_acronym/[snapshot_acronym/]rest_service_name/docs

where:

• host_name is the host name.
• port is the optional port number.
• custom_prefix is an optional custom prefix
• process_app_acronym is the acronym of the process app
• snapshot_acronym is the optional snapshot acronym that, if not specified, resolves to either the tip of the default branch in the development environment, or to the default snapshot in a runtime environment.
• rest_service_name is the name of the REST service.

Basic authentication works for service accounts and LDAP users managed by IBM Cloud Pak® for Business Automation or Identity Manager/Zen; it does not work for users managed by Okta. Zen API key authentication works for all user types. See Authorizing HTTP requests by using the Zen API key for more information.

Note: If you use IBM Cloud Pak for Business Automation , what you exposed here as a REST automation service can be published, and then consumed by applications and automations in Business Automation Studio.

Note: Advanced Properties and Advanced Parameter Properties defined for Business Objects used in REST Services are neither included in the OpenAPI specification nor validated at runtime.