Software AG’s Centrasite registry / repository is a popular product for handling design-time service and policy lifecycle challenges. While many products have the ability to integrate with Centrasite at a service level (both consume and publish service artifacts to Centrasite) only the Layer 7 SOA Gateway has the ability to also integrate a policy level.
From Layer 7’s Policy Manager, you create a policy template to import as a Centrasite Asset.
This policy template can contain variables that are controlled by Centrasite. For example, look at this Quota assertion.
This is adjusted at design time within Centrasite as a property of the service itself. Again within Centrasite, you define all dependencies of the service including the policy template, the PEP host name.
Once these dependencies are modeled, the action of changing the service lifecycle within Centrasite, triggers a call to the Layer 7 SOA Gateway management service, authenticated using the same administrator account associated with the Centrasite session. Back on the Layer 7 SOA Gateway, the management service validates the authorization of the administrative roles granted by the user, and audit these actions. Security between Centrasite and the Layer 7 SOA Gateway can be adjusted to accommodate any security requirements, using any identity provider.
Metrics on the service consumption can be sent back to CentraSite by the Layer 7 SOA Gateway Policy Enforcement Point.
Global policies can also be declared at that level which are automatically inherited by any policies that are submitted via CentraSite.
The integration between the two solutions can also be driven from Layer 7 Gateway side. The Layer 7 Policy Editor lets its administrator search services in Centrasite, publish them on the Layer 7 Gateway, attach UDDI based WS-Policy tModels and more. This current integration is extensible and supported through Software AG.