2.4.8 Export of a service template
Function
Exports the specified service template.
Execution permissions
Admin role, Develop role
API version
v1
Request format
POST http://host:port/Automation/version/objects/ServiceTemplates/id/actions/export/invoke
Status code
The following table describes the various status codes that can be returned as the response to a request.
Status code |
Message |
Description |
|---|---|---|
200 |
OK |
Processing has been successfully completed. |
401 |
Unauthorized |
The user does not have login permission. |
404 |
Not found |
The permission is invalid, or the resource does not exist. |
406 |
Not acceptable |
The specified Accept header is invalid. |
412 |
Precondition failed |
The server is not available. |
500 |
Server-side error |
A server processing error occurred. |
Usage example
In the following example, the API function exports the service template whose instanceID is 1116.
Request header: POST /Automation/v1/objects/ServiceTemplates/1116/actions/export/invoke HTTP/1.1 Authorization: Basic c3lzdGVtOm1hbmFnZXI= User-Agent: curl/7.36.0 Host: 10.196.184.182:22015 Accept: application/octet-stream Content-Type: application/json Accept-Language: ja Response header: HTTP/1.1 200 OK Date: Thu, 30 Jul 2015 01:58:34 GMT Server: Cosminexus HTTP Server Access-Control-Expose-Headers: WWW-Authenticate WWW-Authenticate: HSSO 866ad68aa7c23e457456b5b08479fb62250fdf_Vlo8Y30JdDBUB3ljJSVPaRtjBSA=_V0810 Access-Control-Allow-Origin: * Content-disposition: attachment; filename="com.hitachi.software.dna.cts_SP_GenericApplication_01.20.00.st" Access-Control-Allow-Methods: GET, POST, DELETE, PUT, HEAD, OPTIONS Access-Control-Allow-Credentials: true Cache-Control: no-cache Transfer-Encoding: chunked Content-Type: application/octet-stream Response body: Binary formatted "com.hitachi.software.dna.cts_SP_GenericApplication_01.20.00.st"