The Consumer Environment Service is the gateway to all other services. It scopes the Consumer's possible interactions with the infrastructure and any Provider Services accessible from it. The Environment Service provides the set of (possibly customized) information the Application needs to interoperate successfully.

Unique environment identifier that can be safely shared with others. In order to not compromise security it MUST NOT match the environment's refId, sessionToken, userToken, or applicationKey.

The solution the Application would like to participate in. This is optional only, is advisory, and may be ignored by the Administrator. If processed it may be reflected in the URLs of the infrastructure services which are provided in the consumerEnvironment.

Defines the way in which the applicationKey can be used to enforce security.

A descriptive name for the application that will be readily identifiable to Zone Administrators if it becomes a Registered Consumer

All functional services must use this object design to track state. While Events may be published back to the objects creator, they must not be published to the Consumer when the event was generated based on its request (since results were included in the response). Each functional service should define the expectations of how management of the job is managed for both the Consumer and Provider. For instance, certain optional fields may need to be included in-order-to successfully cause a job to be created.

The name of the job, e.g. "grading" or "sre".

A description of the job, e.g. "Bowers Elementary School Final Marks"

The current enumerable state of the job.

A descriptive message elaborating on the current state, e.g. if the current state is "FAILED" the stateDescription may be "Timeout occured".

The datetime this job was created.

The datetime this job was last modified.

The ammount of time after creation before this job is automatically deleted.

The phases that make up this job.

If an Environment supports self-provisioning Consumers than either this section must initially contain all the rights the Consumer has to all Services in all Zones, or the provisionRequests Infrastructure Service must be present in the Consumer's Environment to allow additional rights to be obtained.

A specific Zone defined for this environment.

The Queues Service supports creation, deletion and querying of Queue (Instance) / Queue Messages Service pairs.

Determines, when no messages are queued, whether the Consumer will have to periodically reissue Polling Requests at timed intervals or can reissue a Polling Request immediately.

The Environment ID of the owning Consumer for which this Queue is buffering messages. It is not specified at Queue create time, but is returned as part of the response to a query operation, and serves to allow an administrative application to identify which application the Queue instance is assigned to.

A name which the Consumer assigns to the Queue. It is useful for reporting purposes, but is not guaranteed to be unique.

The URI of the Messages Service associated with the Queue instance. This is the endpoint where the 'get next message' requests are issued.

When present, this contains the URL which the Queue instance will use when it determines the owner needs to be asynchronously alerted that a new message has arrived in the Queue.

Is the maximum time in seconds the Messages Service will wait for a message to arrive, before returning an HTTPS Response of 'no message seen' to the Consumer.

indicates the minimum time in seconds that the Consumer should wait after receiving a 'no message seen' response to a previous query, before posting another.

Number of (properly identified) concurrent connections supported by (the consumer, if suggested, and) the queue.

Time that Queue Instance was Created

Time that Queue Instance was last Accessed and a message was dequeued.

Time that Queue Instance was last Modified by receiving a new incoming message.

The number of messages currently residing in the Queue.

For states updatable by the Consumer, it creates a new state much like it would a single object. The actual result (state or error) is included in the response. Each functional service should define the expectations for which Adaptor is responsible for updating the phase status. NOTE: The "states" collection represented here is reserved for future capabilities.

The type of this State object.

The datetime this job was created.

The datetime this job was last modified.

A descriptive message ellaborating the condition of this state, e.g. if the state is "FAILED" the stateDescription may be "Timeout occured".

A Consumer uses the Subscriptions Infrastructure Service to subscribe to Events published by one or more Service Providers.

The unique identity of a context element, which is associated with a Provider of this name and type operating in a Zone with this ID.

The type of the service

The subtype of the Service

The type of the message

The name of the Service. For utilities, this is fixed to one of the defined set of Utility Service Names. For objects and functions, it is defined by the Data Model.

Specifies which queues you want data associated with this subscription published to.