API Guide

OME

Table 5. Roles and associated privileges for OME

Privilege Roles

ADMINISTRATOR DEVICE_MANAGER VIEWER

APPLIANCE_SETUP Y N N

BASELINE_MANAGEMENT Y N N

DEVICE_CONFIGURATION Y Y N

DEVICE_UPDATE Y Y N

DISCOVERY_MANAGEMENT Y N N

INVENTORY_MANAGEMENT Y N N

JOB_MANAGEMENT Y Y N

MONITORING_SETUP Y Y N

OPERATING_SYSTEM_DEPLO

YMENT

Y Y N

POWER_CONTROL Y Y N

POWER_MANAGEMENT Y Y N

REPORT_MANAGEMENT Y Y N

REPORT_RUN Y Y Y

SECURITY_SETUP Y N N

TEMPLATE_MANAGEMENT Y Y N

TRAP_MANAGEMENT Y N N

VIEW Y Y Y

ALERT_MANAGEMENT Y N N

AUTO_DEPLOY_MANAGEMEN

Y N N

FABRIC_MANAGEMENT Y N N

NETWORK_MANAGEMENT Y N N

Resource addressing

Each managed resource must be uniquely addressable using a distinct URI. The URI syntax must be intuitive and should indicate the

relationships with a parent resource.

There are several ways to address specific resources either as instances of specific resource classes or within an associated parent

context.

Following is the format of a resource URI:

<BASE_URI>/<resource class identifier>/<resource instance identifier>

Following is an example of a resource URI, where 1234 is the unique identifier for the device:

<BASE_URI>/DeviceService/Devices(1234)

Key integration concepts