You are on page 1of 13

ESB – Governance

WSO2 service
registry
Revision History

Version Date Revision Description Revised By

0.1 21-Apr-2016 Initial Draft Chaitali Patil

0.2

Approval List

Version Date Name Role Department Date

Acronyms

Acronym Explanation
G-Reg Governance registry

SOA Service Oriented architecture


Table of Contents

1 Introduction .............................................................................................................................. 4
1.1 Overview ............................................................................................................................. 4
1.2 Components ........................................................................................................................ 4
2 Using publisher for configuration ........................................................................................... 6
2.1 Uploading application WSDLs provided by target systems like CRM,CBS,MDM etc. ... 6
2.2 Configuring SOAP over JMS (Target) service ................................................................... 7
2.3 Configuring SOAP over HTTP (Source) service ............................................................... 8
2.4 Adding Associations ......................................................................................................... 10
1 Introduction
1.1 Overview

WSO2 Governance Registry is an enterprise-ready open source product for storing, cataloguing, indexing,
managing and governing your enterprise metadata related to any kind of asset. It provides the right level
of structure straight out of the box to govern any enterprise assets, including services, APIs and projects,
and federate the artifacts across distributed systems. It supports SOA governance, configuration
governance, development process governance, design and runtime governance, lifecycle management,
and team collaboration.

1.2 Components
WSO2 Governance Registry provides three main Web based user interfaces to facilitate the features and
functionality as follows.

G-Reg Publisher
The G-Reg Publisher provides an end-user, collaborative Web interface as shown below, for governance
artifacts providers to publish artifacts, manage them, show their dependencies, and gather feedback on
quality and usage of them.
G-Reg Store
The G-Reg Store provides an end-user, collaborative Web interface as shown below, for consumers to self-
register, discover governance artifact functionality, subscribe to artifacts, evaluate them and interact with
artifact publishers.

Management Console

The Management console is a Web-based user interface powered by JSP and AJAX as shown below.
2 Using publisher for configuration
1) Go on link and enter username password
https://172.19.36.68:9443/publisher

2) Identify your source, target and orchestrator applications and keep the list and wsdls ready with
you to be uploaded in WSO2 service registry.
Update attached excel file with data for configuration.

WSO2 data.xlsx

3) After login, the below screen will be displayed.

2.1 Uploading application WSDLs provided by target systems like


CRM,CBS,MDM etc.

Example – Uploading CRMNext API WSDL

a) Select WSDL menu and click on add WSDL button.


b) Select Upload WSDL from a file dropdown in WSDL URL and enter version as 1.0.0 and click
on Create button.
c) You can see uploaded WSDL in WSDL list.
d) Select Soap Service menu and search for service name you created and edit details like
description, contact details, document links etc.

2.2 Configuring SOAP over JMS (Target) service

Example – Configuring CreateCRMAccount_01 service

a) Select SoapService menu and click on “ADD SOAPSERVICE” button.


b) Enter details and click on Create.
c) You can see your asset in list.

2.3 Configuring SOAP over HTTP (Source) service

Example – Configuring CreateMicroATMAccountInCRM_01 service

For adding Soap over HTTP service, follow below steps.


a) Click on “Add WSDL” by selecting WSDL menu.
b) Once it is added, you can see the resource in WSDL list and SoapService list.

c) Open the SoapService resource and click on Edit to update details and enter below details and
click on “Update”
1) Scope
2) CatalogID
3) Contact
4) Interface – transport protocol and message format, message exchange pattern
5) Doc Links for mapping sheet, sample request ,
6) Tags – source ,target or orchestrator , <<scope>>
2.4 Adding Associations

Associations are used to configure relationships between different artifacts to help g-reg user to identify
an artifact is related to which all other artifacts.

1. Provider XSD need added as Schema


2. Provider WSDL has added as WSDLs ( Soap over HTTP)
3. Orchestrator and Target adapter as SOAP SERVICE (JMS)
4. SourceAdapter has added as WSDL ( Soap over HTTP)
Click on Association tab to add association.
1) Select target provider soap Service and click on Association tab to add “UsedBy” relation.

2) Click on target and select “Dependencies” association type in association tab to have relation
between target application WSDL and target service.

3) Select “IsProviderFor” association type and map source applications for which asset is provider
for.
4) Click on each source application to associate related target services and select “Dependencies”
association type.

For Rest services also, we need to follow same approach of configurations.

Report Generation:
Report Class: org.wso2.carbon.registry.samples.reporting.ServiceReportGenerator
/_system/governance/repository/components/org.wso2.carbon.governance/templates/ser
vice_template.jrxml