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.

After you save and publish a process, you can also publish the process to API Center. You can then create an API that the consumers can use to access enterprise services. You can also apply policies, manage, and monitor the API in API Center.

1On 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.

Note: 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.

2Optionally, click the Publish to API Center button to publish the process to API Center. The button appears only when you open a process in the modern view. For information about the rules and guidelines that you must follow to publish a process to API Center, see Rules and guidelines for publishing processes to API Center.

3On 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.

Note: 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.

Note: If you switch from a parent organization to a sub-organization, you can't save and publish a process that was created in the sub-organization.

Rules and guidelines for publishing processes to API Center

After you save and publish a process in Application Integration, you can use the Publish to API Center button to publish the process to API Center.

The Publish to API Center button is available only if the following conditions are met:

1You have the license to access API Center.

2You are assigned an Admin or Deployer role in addition to persona-based roles.

3The process is open in the modern view and runs on the Cloud Server.

4You have configured the allowed groups or allowed users, or configured anonymous access for the process.