Start of change

Refresh a software services template

You can use this operation to refresh the files that are associated with a software services template.

HTTP method and URI path

POST /zosmf/provisioning/rest/<version>/scc/<object-id>/actions/refresh
In this request:
<version>
Is the URI path variable that identifies the version of the z/OSMF software services template service. The following value is valid: 1.0.
<object-id>
Identifies the software services template that the approval is associated with.
<approval-object-id>
Identifies the approval object to delete.

Query parameters

None.

Description

This operation obtains the latest contents of the files that are associated with a software services template: the workflow definition XML file, the actions XML file, and the workflow variable input file if one is specified, and any documentation files that are provided. The information in the software services template is updated to reflect the latest contents, including timestamps, of those files. The files are located by the original source paths.

Refresh causes all approvals to be reset.

On successful completion, HTTP status code 204 (Successful) is returned.

The software services template must be in one of the draft states.

Request content

None.

Authorization requirements

The user's z/OS user ID must be defined as a landlord and a domain administrator.

The user’s z/OS user ID must have READ access to the following resource profile in the ZMFAPLA class: <SAF-prefix>.ZOSMF.PROVISIONING.SOFTWARE_SERVICES.

For more information, see Authorization requirements.

HTTP status codes

On successful completion, HTTP status code 204 (Successful) is returned.

Example HTTP interaction

In Figure 1, a request is submitted to refresh a software services template.
Figure 1. Sample request to refresh a software services template
POST https://localhost:4444/zosmf/provisioning/rest/1.0/scc/d0166782-4e18-4b07-a075-c8946c88e068/actions/refresh

End of change