SOA Governance and API Management : Getting Started with CentraSite : Implementation Concepts : Defining Design/Change-Time Policies
Defining Design/Change-Time Policies
 
What is a Design/Change-Time Policy?
System-Wide vs. Organization-Specific Policies
Policy Priority
Pre-Operation and Post-Operation Event Types
What Happens When a Design/Change-Time Policy Executes?
OnTrigger Policies
Typical Uses for Design/Change-Time Policies
Issues to Consider When Developing Design/Change-Time Policies
Managing Design/Change-Time Policies
Design/change-time polices provide governance controls that you can use to effectively administer and manage Web services and other assets within your SOA environment. Design-time policies enable you to control the acceptance of assets into the registry and manage their eventual deployment into the runtime environment. You can use design/change-time policies to ensure that assets entering the SOA environment conform to organizational standards and conventions, meet the architectural requirements of your enterprise and adhere to industry best practices. You can also use policies to execute standard procedures, such as initiating review processes, issuing notifications and granting instance-level permissions at key junctures in an asset's lifecycle.
The following sections generally describe design/change-time policies and explain how you might apply them at your site. For additional information about design/change-time policies, including specific steps for the procedures described in these sections, see the CentraSite User’s Guide.
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback