SOA Policy Gateway Pattern V2.5 enables businesses to:
- Save money by controlling precisely which clients can access which services and help prevent service overload and unexpected outages.
- Be much more reactive by providing a single point to dynamically make policy changes.
SOA Policy Gateway Pattern for AIX and SOA Policy Gateway Pattern for Red Hat Enterprise Linux can enable rapid deployment of all the components required to register, control, and monitor services. These components are automatically preintegrated to get your business up and running faster than ever before. Use of the pattern reduces the time taken for getting a system installed and set up from weeks to hours. With SOA Policy Gateway Pattern, a new environment for testing, staging, or production can be set up in a few clicks and with the bare minimum of supplied information.
An SOA policy provides a dynamic interaction point to rapidly handle web service or Representational State Transfer (REST) requests as they flow through the business. You can run this pattern on a PureApplication System (W1500 or W1700). You can also connect to a DataPower appliance to provide policy enforcement for REST and Web Service (Simple Object Access Protocol (SOAP)).
To enable policy enforcement, IBM SOA Policy Gateway for Red Hat Enterprise Linux includes WebSphere DataPower virtual editions as part of the pattern.
These patterns enable:
- Definition of different endpoints for different classes of service. For example, a policy could be set to route service requests to a different endpoint for premium users, to provide a high quality of service with fastest response times.
- Implementation of traffic scheduling, by routing requests to different endpoints at different times of day. For example, route requests to a service can be hosted in an overseas data center overnight, while regular backup takes place in the local center.
- Annotation of the policies with service metadata and documents to describe their usage in your enterprise. You can use access control and establish a lifecycle with approval steps to control who is authorized to approve policy changes.
- Establishment and automatic enforcement of contracts between consumers and providers using Service Level Agreements (SLAs). SLAs defined in the policy can determine how the service should behave and who should have access.
- Prevention of system outages and protection of your services, which can potentially save you money. For example, to protect a back end service, a threshold limit can be set for the number of requests that the service handles before a notification is sent. A warning can be sent to system administrators that the request load is increasing so appropriate actions can be taken.
Policy administration is provided using the Business Space user interface provided by WebSphere Service Registry and Repository. Monitoring is provided by IBM Tivoli Composite Application Manager For Applications.
SOA Policy Gateway Pattern for AIX and SOA Policy Gateway Pattern for Red Hat Enterprise Linux utilize IBM governance to register and manage services. These patterns deliver WebSphere Service Registry and Repository to provide policy authoring, catalog services, discover existing services, record consumer and provider contracts, author SLAs, and provide lifecycle management and visualization reports.
Find out more here.
LATEST COMMENTS
MC Press Online