Version 9.6

Implementation Concepts

This document describes concepts and considerations associated with implementing CentraSite for different use-case goals. This guide is intended for the individuals who are involved with the deployment and implementation of CentraSite, including the Enterprise Architects and Implementation Leaders who are responsible for planning and managing the implementation of CentraSite at their site.

Important:
This guide provides suggested approaches and practices for implementing CentraSite. However, you should always test that a particular approach or recommendation to ensure that it satisfies the needs of your organization.

The content is organized under the following sections:

green ball Overview of CentraSite Provides a high-level overview of the major components in a CentraSite environment.
green ball Implementation Decisions and Configuration Tasks Identifies the high-level decisions that you need to make and tasks you need to complete when implementing CentraSite.
green ball Obtaining and Installing the Starter Kit Describes how to obtain and install a set of examples that you can reference while preparing for your implementation.
green ball Choosing a Deployment Strategy Describes the approaches you can use to implement CentraSite in terms of single- or multi-stage deployments.
green ball Defining Your Organizational Structure Describes the role of Organizations in a CentraSite registry and identifies issues you should consider when defining organizations for a CentraSite implementation.
green ball Setting Up Users and Groups Describes the role of Users and Groups in a CentraSite registry and identifies issues you should consider when defining organizations for a CentraSite implementation.
green ball Using Permissions and Roles to Manage Access to the Registry Describes how CentraSite uses permissions and roles to control access to registry objects and operations and identifies issues you should consider when assigning roles and permissions to CentraSite users.
green ball Customizing Your Asset Catalog Describes ways in which you can customize the registry to support the types of assets that make up your SOA environment and identifies issues you should consider when making these customizations.
green ball Working with Versions and Revisions Describes the versioning and revisioning capabilities in CentraSite and discusses when to generate new versions of existing assets.
green ball Defining Lifecycle Models Describes how CentraSite uses lifecycle models to enable governance of assets in the registry and identifies issues you should consider when applying lifecycle models to the assets in your SOA environment.
green ball Defining Design/Change-Time Policies Describes how you can use design/change-time policies to control the creation, modification and deletion of registry objects and identifies issues you should consider when applying design/change-time policies to your registry.
green ball Planning Your Run-Time Environment Provides an overview of the components that make up the run-time environment and describes how the components interoperate when CentraSite is implemented across two stages.
green ball Implementing the Mediation Environment Describes issues to consider when configuring webMethods Mediator for collecting performance metrics and logging. Also provides information about using CentraSite with Insight.
green ball Managing Run-Time Policies Describes how to use run-time policies to enforce security policies, perform logging tasks and monitor performance metrics for virtual services.
green ball Managing Virtualized Services Describes how to create virtual services, who should create virtual services and when to create virtual services. Also discusses which services you should consider virtualizing.
green ball Identifying the Consumers of Virtual Services Describes how consumer applications are identified at run time and are specified at design time.
green ball Managing Endpoints Describes how CentraSite represents the endpoints for services and how to keep endpoint information up-to-date as a service moves through its development lifecycle.

Top of page