Operating and Managing Hitachi Content Platform v8.2: Management API
Operating and Managing Hitachi Content Platform v8.2: Management API
Hitachi Content
Platform v8.2
Management API
Tenants
• Retrieve information about a single tenant
• Set default properties for namespaces created for an HCP tenant
• Retrieve statistics about the content of the namespaces owned by a tenant
• Generate a chargeback report for an HCP tenant
Namespaces
• Create, modify, and delete HCP namespaces
• Retrieve information about a single namespace
• Retrieve a list of all the namespaces owned by a tenant
• Retrieve statistics about the content of a namespace
• Generate a chargeback report for an HCP namespace
• Reset the indexing checkpoint for a namespace
Retention classes
• Create, modify, and delete retention classes for a namespace
• Retrieve information about a single retention class
• Retrieve a list of all the retention classes defined for a namespace
Content classes
• Create, modify, and delete content classes for a tenant
• Retrieve information about a single content class
• Retrieve a list of all the content classes defined for a tenant
HEAD Performs a GET but does not return the response body
When you request information about resources, you can ask for the
response to be returned in XML format or in JSON format
• For one resource, chargebackReport, you can also ask for the response to
be returned in CSV format
The value of this header is the version number of the currently installed
HCP software; for example:
• X-HCP-SoftwareVersion: 8.3.0.2
1. Log into the Tenant Management Console using a user account with
the security role.
Many of the data types that describe HCP management API resources
and properties are named, unordered sets of properties
When you create a resource, some properties for the applicable data
type are required and some are optional
When you modify a resource, all properties for the applicable data type
are optional
You can access the HCP system through the management API by
specifying either a hostname or an IP address in the resource URL
• If the system uses DNS and you specify a hostname, HCP selects the IP
address for you from the currently available nodes
• HCP uses a round-robin method to ensure that it doesn’t always select the
same address
When you use the HCP management API to create a resource, the best
way to ensure that the request body includes the applicable properties
is to use a template
• You can generate your own template by submitting a GET request for an
existing resource of the same type
• In the request, include the verbose=false query parameter on the resource
URL (or omit the verbose parameter to accept the default of false)
The best way to modify a resource through the HCP management API
is to:
• Submit a GET request for the resource you want to modify.
In the request, include the verbose=false query parameter on the resource URL (or
omit the verbose parameter to accept the default of false)
This ensures that the response body includes only the properties whose values you
can set
• In the response body from the GET request, change property values as
needed
• Submit the POST request for the resource, using the entire modified
response body as the request body
Response headers
• HTTP/1.1 200 OK
• X-HCP-SoftwareVersion: 8.2.0.2
• Content-Length: 0
2. With MAPI you can manage Tenant-level users and groups. (True or
False)
REST MAPI
Follow us on
Validate yourknowledge
Validate your knowledgeandand skills
skills withwith certification
certification. social media:
Get practical advice and insight with Hitachi Vantara white papers.
Join the conversation with your peers in the Hitachi Vantara Community.