 |
| |
Centrasite SOA |
|
|
| |
Attune Infocom offers best of the industry solution with CentraSite SOA and BPM product stakes to Build the right services on the right way. It gives developers and business analysts one place to store, find and re-use all your organization service and process assets. Attune Infocom guide your development of new business processes and services faster while improving collaboration between business and IT. CentraSite is the Business Service Repository for SOA and BPM that eliminates re-work, assures consistent quality and keeps your services aligned with business needs. |
|
| |
|
|
| |
Imagine being able to build repeatable solutions faster and at less cost. You can do that with CentraSite. You can catalog dozens or even thousands of processes and services in one place so developers and business analysts will know what assets they can re-use. Plus, you’ll have the assurance that services perform to the high standards you’ve enforced with CentraSite. |
|
| |
|
|
| |
CentraSite features |
|
| |
Metadata Registry & Repository |
|
| |
Active Lifecycles |
|
| |
Active Policies |
|
| |
Search & Notification |
|
| |
Relationship Tracking |
|
| |
Federation Engine |
|
| |
Standards Support |
|
| |
|
|
| |
Metadata Registry & Repository |
|
| |
|
|
| |
Get asset information in an instant |
|
| |
CentraSite gives you a unified registry and repository—a central, platform-independent store for defining and describing assets. You can easily catalog all services, processes and related assets, such as XML schemas and business rules. This means information for faster decision-making and collaboration among SOA and BPM teams is just a click away. |
|
| |
|
|
| |
Rich and expandable descriptions |
|
| |
CentraSite's flexible metadata store captures information like asset capabilities, owner, location, version, classifications and configuration. You also can store associated artifacts, such as requirements documents and usage guidelines, as part of the asset description. You can customize all aspects of the store to suit your unique needs—for example, by defining custom asset types and adding custom attributes, attachments and classifications. |
|
| |
|
|
| |
Publishing assets to CentraSite |
|
| |
You can publish asset definition and descriptions to CentraSite using a wide range of options. For example, you can:Adding assets using CentraSite’s Web-based interface |
|
| |
|
|
| |
Add assets using CentraSite's Web-based interface |
|
| |
Publish assets from Eclipse-based IDEs and UDDI-compliant IDEs |
|
| |
Bulk-load hundreds of assets using command line utilities and APIs |
|
| |
|
|
| |
More than 25 ready-to-use asset types |
|
| |
CentraSite provides more than 25 ready-to-use asset types definitions, including service, XML schema and BPEL process. Use them as-is to get started quickly. Or, use them as inspiration for defining your own asset types. |
|
| |
|
|
| |
Active Lifecycles |
|
| |
Build the right services the right way |
|
| |
CentraSite's Active Lifecycle technology tracks and guides the evolution of every service and process asset, from conception through retirement. Active Lifecycles ensure your SOA and BPM teams build the right services and processes—and build them the right way. |
|
| |
|
|
| |
Lifecycle models |
|
| |
You can assign every asset type in CentraSite's store a unique lifecycle that models its real-world status, such as proposed, built, productive or retired.Users can easily change lifecycle states for any asset |
|
| |
|
|
| |
Ensure standards and practices are followed as every asset moves through its lifecycle. You can do this by defining permissible transitions between states. |
|
| |
|
|
| |
Versioning |
|
| |
In the distributed and always-on world of SOA and BPM, managing changes to services and processes can be a challenge. That’s why CentraSite has built-in versioning capabilities so you can define and track asset versions. Multiple versions can exist side-by-side, and older versions can be retired over time. |
|
| |
|
|
| |
Active Policies |
|
| |
Increase consistency and control |
|
| |
CentraSite’s Active Policy technology automates lifecycle processes. An Active Policy defines a series of actions that you associate with an event, such as the addition, modification or lifecycle status change of an asset. When the event occurs, CentraSite executes the actions prescribed in the policy. For example, when a service is added to CentraSite, a policy can trigger a series of automated steps, such as validating metadata and provisioning appropriate permissions. |
|
| |
|
|
| |
Development-time policies |
|
| |
CentraSite enforces policies along an asset’s lifecycle at major governance checkpoints, such as funding approval, architecture and design reviews and operational readiness reviews. Automated enforcement provides timely and consistent guidance to interdependent but autonomous SOA and BPM teams. To save time, you can use pre-loaded development-time policies, including metadata validation, WS-I compliance, approval workflow, permission provisioning, notifications and much more. |
|
| |
|
|
| |
Run-time policies |
|
| |
CentraSite also provides a powerful roster of policies that can be enforced when services are invoked at run-time to ensure correct and authorized use of services. Run-time policies include consumer authorization, message-level encryption and signatures and schema validation. Run-time policies are managed in CentraSite and enforced using webMethods Mediator. |
|
| |
|
|
| |
Custom policies |
|
| |
In addition to using CentraSite’s pre-built policy templates, you can write custom policies in Java or Groovy scripting language. Your custom policies will have full access to all metadata available in CentraSite. |
|
| |
|
|
| |
Smart policy provisioning |
|
| |
Manually associating the right policies with right assets can be tedious and result in errors. CentraSite’s smart policy provisioning takes away that guesswork. Once a policy is defined and approved, CentraSite automatically applies it to all assets that meet a specific criteria you define. You can change the policy’s scope simply by changing this criteria. |
|
| |
|
|
| |
Search & Notification |
|
| |
Find and re-use assets - easily |
|
| |
Finding and re-using service and process assets is easy with CentraSite’s Web-based interface. Built-in workflow capabilities quickly on-board consumers and track consumption of assets. |
|
| |
|
|
| |
Browse and search |
|
| |
You can find service and process assets by browsing using built-in or custom taxonomies. You can also use CentraSite’s powerful keyword search or its advanced search capabilities for defining complex criteria. For XML-savvy users, CentraSite also supports searching using the XQuery language. |
|
| |
|
|
| |
Anonymous access |
|
| |
CentraSite can be set up for anonymous access so project teams can see assets available for re-use. Viewing is quick and easy—no credentials are required! You can even brand the Web-based interface as your own and let customers and partners use it for self-service viewing of available assets. |
|
| |
|
|
| |
Consumer registration |
|
| |
Once project teams find services and process assets they’d like to use, they can request access to them. Requesting teams need to specify the users and applications that will consume the assets. Administrators can set up and enforce policies before approval to use the assets is granted. |
|
| |
|
|
| |
Change notifications |
|
| |
You can create a list of favorite assets to track and receive notifications on any event that impacts them. |
|
| |
|
|
| |
Relationship Tracking |
|
| |
Keep track of interdependencies |
|
| |
Make sense of the complex interdependencies among services, processes and IT applications using CentraSite's relationship tracking capabilities. Importantly, CentraSite also captures the relationships of services and processes with the people and organizations that built, operate and maintain them |
|
| |
|
|
| |
CentraSite identifies and tracks many relationships automatically as services and processes are created, deployed and used. As needed, project teams can easily add new relationship definitions. |
|
| |
|
|
| |
Power analysis |
|
| |
See a graphical and interactive view of assets and their relationships. You use power analysis to interactively explore your entire asset landscape. A real-time graphical map shows the “downstream” impact of any proposed change or disruption. You can customize the view to restrict the set of assets and associations shown to zero-in on the details that interest you the most. |
|
| |
|
|
| |
Federation Engine |
|
| |
Sync up your metadata |
|
| |
Is some of the information you want to see in CentraSite already available in another repository? Do you need to exchange service and process information within multiple independent SOA domains? CentraSite's industry-leading federation engine is the most efficient solution for synchronizing metadata across multiple repositories. |
|
| |
|
|
| |
CentraSite’s federation engine can synchronize metadata between CentraSite and another repository, such as Configuration Management Databases (CMDBs) or a source-code control system. You can specify what metadata is exchanged and how often.CentraSite can synchronize with other repositories |
|
| |
|
|
| |
"Pluggable" federation |
|
| |
CentraSite provides built-in support for metadata federation among multiple instances of CentraSite. Federation with other repositories is "pluggable" so that any arbitrary source of metadata can be connected with CentraSite. A federation adapter for UDDI-compliant repositories comes with CentraSite. Custom adapters can be built for other repositories. |
|
| |
|
|
| |
Standards Support |
|
| |
Bring your platforms together |
|
| |
CentraSite is a standards-based solution designed to support a variety of SOA and BPM platforms. CentraSite’s support for open standards also allows it to work directly with third-party solutions for SOA testing, management and security. |
|
| |
|
|
| |
CentraSite adheres to these key standards: |
|
| |
| |
Policy management |
|
|
WS-I Basic Profile 1.1 |
|
|
WS-SecurityPolicy |
|
|
WS-Policy 1.5 |
|
|
WS-PolicyAttachment 1.2 |
|
|
WS-PolicyAttachment 1.5 |
|
|
JSR-223 Scripting(Groovy) |
|
| |
XML Standards |
|
|
XML Schema 1.0, 1.1 |
|
|
XML Query |
|
|
XSLT 1.0 |
|
|
XML 1.0 |
|
|
XMI |
|
|
XQJ (JSR 225) |
|
|
|
| |
|
|
| |
| |
Enterprise infrastructure |
|
|
LDAP |
|
|
POP3/IMAP & SMTP |
|
|
JAAS |
|
|
SNMPv3,supported |
|
|
JMX 1.2 |
|
|
|
|
| |
Registry/repository |
|
|
JAXR, level 1 |
|
|
UDDI V2, UDDI V3 |
|
|
WebDAV |
|
|
WSDL 1.1 |
|
|
BPEL 1.1 |
|
|
BPEL4WS |
|
|
XPDL 1.0 |
|
|
SCA |
|
|
|
 |
