Overview
Dell EMC is not one product. It is the storage portfolio Dell assembled from its own lines and the EMC acquisition, and it covers block arrays such as PowerStore, PowerMax and Unity, scale-out NAS in PowerScale (formerly Isilon), object storage in ECS, and purpose-built backup appliances in PowerProtect and Data Domain. Each of those platforms runs its own management software and publishes its own REST API on its own management address, with its own resource names and its own idea of what an object, a volume and a node are.
The ReadyWorks connector is a single authenticated REST client that you point at whichever of those management endpoints you are collecting from. It uses the json_rest_api.php driver, takes an API domain, a username and password and a server-side working path, and authenticates with an HTTP Basic header built from the credentials and Base64-encoded. Because the portfolio has no common API, the connector ships no platform-specific jobs; you define the endpoint, the return data node and the destination table per array family.
Dell hardware is typically the largest single refresh population in an enterprise estate, and storage arrays are the part of it that inventory tools see least well. Pulling array, node, pool and capacity records into ReadyWorks lets you line up serial numbers and models against support contracts and end-of-life dates, tie stored capacity back to the applications and business units that depend on it, and sequence array refreshes against the migration waves that will move data off them.
The connector is registered as bidirectional. Inbound jobs pull into staging tables. The outbound side posts a record from ReadyWorks to an endpoint you nominate and captures status, message and record key from the reply. Both sides ship as empty skeletons.
NOTE: One connection addresses one management endpoint. An estate running PowerStore, PowerScale and Data Domain needs a separate ReadyWorks connection for each, since the credentials, base URL and resource paths all differ.
Connector Properties
Authentication Methods
Dell EMC offers a single authentication method, cloned from the generic REST username and password pattern.
Method 1: Basic Authorization: Username / Password (DELL EMC_f63e7a705a)
Connect to a GET method API with a username / password
Sends the connection’s username and password as a Base64-encoded HTTP Basic credential. Most Dell management APIs accept Basic auth for a local or directory-backed administrative account; check which role your target platform requires, because a read-only monitoring role is usually enough and avoids giving ReadyWorks an account that can change array configuration.
Connection Configuration Fields (6)
Authentication Configuration
Headers sent on the authentication call:
cURL options:
Inbound Job Fields Enabled (44)
Inbound jobs expose the full REST field set, including three levels of enumeration and all five pagination modes.
NOTE: Several labels and tooltips in this form carry defects inherited from the shared ETL5 field templates: the Enumeration 1 Node label reads “Enumaration”, the Append New Data label reads “Exisiting”, and the help text on Enumeration 1 Keys End Point and Enumeration 3 Fields both refer to enumeration 2. The underlying fields behave as their labels say.
Outbound Job Fields Enabled (13)
Outbound jobs expose the REST posting field set, including the outbound field list, the return data mapping and an optional raw JSON body template.
Inbound Job Templates (1)
Dell EMC ships one inbound template, and it is the generic REST skeleton rather than a pull against any particular Dell platform.
Job Template Configuration
Settings
Outbound Job Templates (1)
One outbound template ships, and it is the matching generic REST skeleton.
Job Template Configuration
Settings
Job Parameters and Enumeration
Rest POST API
Outbound fields list:
Return data fields: