Operational Policies

Policy Name Description
API Consumer Application Security Policy

Used to identify (authenticate) the application that is attempting to consume an API to determine if it is authorized or not. This policy type supports multiple mechanisms for the App to present its identity, including plain text App Id, signed header with x.509 or a shared secret, or OAuth (1.0 or 2.0).

Category: Security

API User Security Policy

Is the default security policy for Atmosphere services and controls who can perform administrative actions on the Atmosphere portal.

Category: Security

BasicAuditing

Provides basic auditing of messages. Message metrics will be recorded in the Policy Manager Usage Logs Monitoring tab. The messages themselves will not be audited. That can be achieved using the DetailedAuditing policy.

Category: Auditing

DetailedAuditing

Provides detailed auditing of messages. Message metrics will be recorded in the Policy Manager Usage Logs Monitoring tab as well as the entire messages of each exchange.

Category: Auditing

WS-Auditing Message Policy

Used to audit to service operations and binding operations.


WS-Auditing SOAP Message Policy Used to audit service operations and binding operations.

Category: Auditing
WS-Auditing SOAP Service Policy

Used to audit SOAP binding operations.

Category: Auditing

WS-Auditing Service Policy Used to audit Services, Bindings, Operations, and Access Points.

Category: Auditing
WS-Auditing Transaction Tracking Policy

Supports Transaction Tracking functionality that correlates related web service events within a single activity or transaction. For example, if a service in a Container uses the SOA Software Delegate to call another service in a different container that is managed by the SOA Software Agent, it will automatically insert correlation information into the message that is collected and used by Policy Manager to collect tracking and log information.

Category: Auditing



Service Level Policies

Policy Name Description
Service Level Policy

Defines conditions for measuring and reporting performance of a specific Contract. Each policy is composed of a "Rule" and "Access Interval." Rules represent the conditions you define to measure and report performance of a service contract. When a defined system condition matches a defined rule, an alert is raised.

Category:
QoS (Quality of Service Policy)

Bandwidth Quota Policy

Allows you to configure the bandwidth cap (i.e, quota) that a consumer can upload or download at any given time. The bandwidth cap can be specified as kilobytes or megabytes per second. If the quota is exceeded, the runtime will throttle the traffic to conform to the quota policy. The quota is also assigned to either the request (upload) or response (download). No alerts are generated for this policy since the bandwidth consumed is a function of the network speed and capabilities of the service provider, not the consumer.

Category:
QoS (Quality of Service Policy)

Script Policy

Allows you to update a policy defined using BeanShell or Jython script languages. A series of predefined functions and variables are provided that allow you to build a custom policy expression that is evaluated at runtime. Several sample scripts are also provided that illustrate common quota management activities.

Category:
QoS (Quality of Service Policy)

Service Level Enforcement

The Service Level Enforcement Policy is a Quality of Service (QoS) policy that allows you to enable and configure the error message returned to the consumer when their SLA is violated.

This policy works in conjunction with a Service Level Policy and only applies to the following Service Level rules: "Usage Count," "Total Request Message Size," and "Total Response Message Size."

You define a Service Level Policy and specify each service level condition and alert code, then you define a Service Level Enforcement Policy and specify the error message you would like displayed when a specified service level condition is violated.

Category:
QoS (Quality of Service Policy)

Throughput Quota Policy

Allows you to monitor web service throughput performance by specifying a throughput limit (i.e., quota), queue size, and configuring fault and alert notifications.

If the quota is exceeded, a consumer fault message will be returned to the service consumer and an alert will be logged.

Category:
QoS (Quality of Service Policy)

Timeout Policy

Allows you allows you to configure the timeout for each request and specify a custom fault error message that is returned to the client.

Category:
QoS (Quality of Service Policy)

Concurrency Quota Policy

Allows you to monitor the web service concurrency performance by specifying a concurrency limit (i.e., quota) that represents the maximum number of concurrency connections, and configuring fault and alert notifications.

If the specified concurrency limit is exceeded, Policy Manager will return a fault and send an alert.

Category:
QoS (Quality of Service Policy)