Start SOA governance with WSO2 governance Registry

WSO2 has recently announced their new release of WSO2 Governance Registry which is based on WSO2 Carbon framework 3.0.0.

It was packed with some exciting and very useful new features. The product can be used not only to govern you SOA metadata, but also as a registry-repository for your organization. Most interestingly the product is open source and available freely under Apache license. First version (0.1) of the product was released in December, 2007. Thus, the product has been matured over two years and good enough to cater your SOA governance requirement easily.

List of new features of the release as follows.

New Features
============================

* Gadgets for impact analysis on services and registry resources
* WSDL custom view
* Dynamic Handler configuration
* Handler simulator
* Tree-based Resource view
* API to govern SOA artifacts
* Complete Web Services API for Registry
* Improved options for Service discovery
* WS-Discovery support
* Scripting support for lifecycle management
* Improved P2 based provisioning and feature management support
* Support for adding remote mounts
* Platform, and Group/Cluster based deployment model
* Support for multiple server instances
* E-mail verification for subscriptions
* Support for deleting tags and comments
* Support for PostgreSQL DBMS
* Paged activity and resource search
* Hierarchical permission model with granular and extensible permissions
* Ability to upload metadata (in addition to importing)
* Governance Archive for uploading WSDLs and Schemas with imports
* Ability to update resource content by uploading
* Rich text editor for editing text resources
* XML editor for editing handler, lifecycle and service UI configurations

WSO2 Governance Registry 3.0.0 installation on Jboss 5.0 with Oracle 10g

WSO2 G-Reg, one of the leading open source SOA governance solution available. The latest release of the WSO2 G-Reg support multiple application servers along with most common production databases.This post list down the steps to deploy G-Reg 3.0.0 on Jboss 5.0 GA using oracle 10g.

Step 1
Download WSO2 G-Reg-3.0.0 from here. Extract the downloaded zip into a directory. Copy conf, database, repository and resources directories in to a new folder. Here after, we will refer it is greg-repo (i.e:- /home/krishatha/greg-repo)

Step 2
Lets refer to your jboss installation directory, JBOSS_HOME. Go to JBOSS_HOME/server/default/deploy directory and create a new folder, wso2greg.war.Now, copy wso2greg-3.0.0/webapps/ROOT/WEB-INF to JBOSS_HOME/server/default/deploy/wso2greg.war

Step3
Now configuring jboss ssl connector as given below.

a. First up, you should probably shut down the JBoss server as you do this step.
In the JBoss directory, there should be a file called server.xml:

JBOSS_HOME/server/default/deploy/jbossweb.sar/server.xml

This file includes information about what web features to turn on when the server starts up.Inside this file, there should be a part that looks like this

<!--<Connector protocol="HTTP/1.1" SSLEnabled="true"
port="8443" address="${jboss.bind.address}"
scheme="https" secure="true" clientAuth="false"
keystoreFile="${jboss.server.home.dir}/conf/chap8.keystore"
keystorePass="rmi+ssl" sslProtocol = "TLS" />-->

b. Make the following changes:

i. Uncomment the block
ii. Change the port to 8443
iii. Change the keystore password to the password used.

The end result should look something like this:

<!-- SSL/TLS Connector configuration using the admin devl guide keystore-->
<Connector protocol="HTTP/1.1" SSLEnabled="true"
port="8443" address="${jboss.bind.address}"
scheme="https" secure="true" clientAuth="false"
keystoreFile="/home/krishatha/greg-repo/resources/security /wso2carbon.jks"
keystorePass="wso2carbon" sslProtocol = "TLS" />

Make sure to give the exact location of wso2carbon.jks as highlighted above.
Note: you can use your own keystore file if required.

Step 4
Now we must do the necessary configurations in a set of config files shipped with WSO2 G-Reg. We will update carbon.xml, axis2.xml, registry.xml, transports.xml and user-mgt.xml which can be found at greg-repo\conf directory.

a. Edit the carbon.xml in greg-repo/conf and set backend sever URL as below.

<ServerURL>https://IP:8443/wso2greg/services/</ServerURL>

it is recommended to use your IP rather than using localhost or hostname.
Note that we have configured JBoss to run on 8443 port.

b. Edit the same carbon.xml and put /wso2greg as the WebContextRoot

<WebContextRoot>/wso2greg</WebContextRoot>

the webcontextroot will be the name you used to create war distribution in JBOSS_HOME/server /default/deploy/wso2greg.war/

c. Then open axis2.xml, We must change the http and https ports in In Transports section of axis2.xml as follows.

<transportReceiver name="http"
class="org.wso2.carbon.core.transports.http.HttpTransportListener">
<parameter name="port">8080</parameter>


</transportReceiver>
<transportReceiver name="https"
class="org.wso2.carbon.core.transports.http.HttpsTransportListener">
<parameter name="port">8443</parameter>
</transportReceiver>

d. Edit the transports.xml as follows. https and http ports of the transport section can be changed as follows.

<transport name="http" class="org.wso2.carbon.server.transports.http.HttpTransport">
<parameter name="port">8080</parameter>


<transport name="https" class="org.wso2.carbon.server.transports.http.HttpsTransport">
<parameter name="port">8443</parameter>

e. Open registry.xml and update DB configurations as follows.

<dbconfig name="wso2registry">
<url>jdbc:oracle:thin:@hostname:1521:SID</url>
<userName>wso2</userName>
<password>wso2</password>
<driverName>oracle.jdbc.driver.OracleDriver</driverName>
<maxActive>80</maxActive>
<maxWait>60000</maxWait>
<minIdle>5</minIdle>
</dbconfig>

Note that the DB configuration used here is for oracle and you can set the DB configuration to any other supported DB accordingly.

f. Open user-mgt.xml and update DB configurations as follows.

<Database>
<URL>jdbc:oracle:thin:@hostname:1521:SID</URL>
<UserName>wso2</UserName>
<Password>wso2</Password>
<Dialect>oracle</Dialect>
<Driver>oracle.jdbc.driver.OracleDriver</Driver>
<maxActive>30</maxActive>
<maxWait>60000</maxWait>
<minIdle>5</minIdle>
</Database>
Note that the DB configuration used here is for oracle and you can set the DB configuration to any other supported DB accordingly.now you have done with configuration changes.

More details on setting up G-Reg with oracle can be found from here.

Step 5
Now you need to copy oracle driver class to the correct location. In my case I have used ojdbc14.jar.


copy ojdbc14.jar into greg-repo/repository/components/extensions


step 6
You also need to copy the wso2greg-3.0.0/lib/log4j.properties file into JBOSS_HOME/server/default/deploy/wso2greg.war/WEB-INF/classes, and JBOSS_HOME/common/lib/log4j.jar to JBOSS_HOME/server/default/deploy/wso2greg.war/WEB-INF/lib

step7
We have completed the required configurations. Now, open a new command window and change the directory to JBOSS_HOME/bin.Define an environment variable called CARBON_HOME and set the path to your greg-repo directory.


In windows; set CARBON_HOME=C:\greg\greg-repo
In linux; export CARBON_HOME=\home\user\greg\greg-repo


Start JBoss from the same command window/shell. To start JBoss with the "-b [IP]" option use the following commands.

ex:- run.bat -b 12.34.56.78 OR
./run.sh -b 12.34.56.78

WSO2 G-Reg will be started successfully. You can access the management console using https:\\IP:8443\wso2greg\carbon

Related posts: How to deploy WSO2 WSAS-3.* on JBoss

Open Source registry for SOA governance.

WSO2 has announced their latest release of WSO2 Registry 1.1. Comparing to registry 1.0 release, the new release has lots of new features and performance improvements. So it has more enhanced support for SOA governance.

New features:

• Performance improvements
• Change from auto-versioning collections to explicit checkpointing
• Lifecycle/Aspect support
• Much improved WSDL handling, validation, and WS-I validation
• Support for transaction handling
• Generic typed associations
• API improvements, including streamlined Filter/Handler plugins
  

WSO2 registry comes with a web based user interface, which is really user friendly and easy to use by technical or non technical people. The UI is based on web 2.0 look and feel. Newly implemented pagination support is cool feature which serve the users more faster. WSO2 ESB and WSO2 Mashup Server have embedded WSO2 Registry, so the registry is already used in production environments.