Invoke

Back Next

Publishing a process

You must publish a process to invoke or run the process.

You can also publish multiple processes in bulk. For more information, see Publishing Application Integration assets in bulk.

When you publish a process, Application Integration activates the API. It generates service URLs, a Swagger file, an OpenAPI 3.0 file, and a WSDL file for the process. You can use the service endpoint URLs to invoke the process. You can use the Swagger, OpenAPI 3.0, and WSDL files to view the API definitions of the process.

If you edit a published process, you must publish the process again for the changes to get reflected. Otherwise, the process status changes to

Outdated

in the

Property Details

dialog box and on the

Explore

page. The

Outdated

status indicates that the process contains unpublished changes.

On the

Explore

page, navigate to the process that you want to publish and click

Publish

Application Integration publishes the process and activates the API. It generates the service URLs, a Swagger file, an OpenAPI 3.0 file, and a WSDL file.

If you do not specify the allowed groups or allowed users, or allow anonymous access for the process, Application Integration does not generate the service URLs, Swagger file, OpenAPI 3.0 file, and WSDL file.

On the

Actions

menu, click

Properties Detail

to view the API status, generated service URLs, Swagger file, OpenAPI 3.0 file, and WSDL file.

The

Properties Detail

dialog box appears.

The following image shows the

Properties Detail

dialog box:

The image shows the generated service URLs, Swagger file, OpenAPI 3.0 file, and WSDL file.

The status indicates that the API is active.

When you publish a process from

Application Integration

for the first time, the API is activated and displayed on the

APIs

page in

Application Integration Console

. Later, when you activate or deactivate the API from the

APIs

page,

Application Integration

also updates the API status in the

Properties Detail

dialog box. Republishing a process with an inactive API status does not activate the API. You must activate the API from the

APIs

page to make the API available for the user. For more information about activating and deactivating the API, see

APIs

in the Monitor help.

You can also view the service URL and SOAP service URL, and use them to invoke the process. The

Endpoints

section indicates if the process is configured to only accept HTTP authorization requests from the API Gateway.

You can click the

View Swagger File

View OpenAPI 3.0 File

, and

View WSDL File

links to view the associated Swagger file, OpenAPI 3.0 file, and WSDL file.

Runtime tasks for processes

Download Guide

Watch

Comments

Cloud Application Integration Homepage

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Invoke

Invoke

Publishing a process

Publishing a process