How to Deploy WSO2 Registry on JBoss using oracle

The step by step guide is available at here

Deploying WSO2 Registry on tomcat

WSO2 registry is one of the leading open source registry-repository available today. It allows users to store and manage SOA metadata in a more convenient and manageable manner. WSO2 Registry can be used as a standalone distribution as well as it can be deployed on most of the servlet containers . Following step by step guide will show you how to deploy wso2registry on tomcat.

This guide applies to WSO2 registry 2.0.1 and tomcat-6.0.14

Step 1 – Enable SSL connector in tomcat.

Lets refer to your tomcat installation directory, CATALINA_HOME.

E.g.: -
CATALINA_HOME=C:\apache-tomcat-6.0.14

Now you will need to enable HTTPS on Apache Tomcat since WSO2 REGISTRY runs over HTTPS. To do this, access the server.xml file located at %CATALINA_HOME%/conf and uncomment the following.

Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS"

Then you will need to provide the keystore file location along with it's password as below.

Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS"
keystoreFile = "C:\Carbon\ESB\tomcat\WSO2-registry-2.0.1\resources\security\wso2carbon.jks"
keystorePass="wso2carbon"

One could find the wso2carbon.jks file inside the /resources/security/ directory in wso2 registry installation home.

Step 2 - Downloading and installing WSO2 Registry

Download the latest WSO2 Registry distribution from here and extract to a specific location. (E.g.:- C:\Carbon\Registry\tomcat\WSO2 registry 2.0.1). From this folder copy the folders,

- conf
- database
- resources
- repository

to a separate folder. (E.g.:- C:\Carbon\REGISTRY\tomcat\registry_home)

Step 3 - Setting environmental variables

You will have to set an environment variable with the name CARBON_HOME pointing it to the directory which you copied the above files to.

E.g.:-
CARBON_HOME=C:\Carbon\REGISTRY\tomcat\registry_home


Step 4 - Copying required files to Apache Tomcat

Now create a folder inside the webapps folder of Tomcat.

E.g.:-
C:\apache-tomcat-5.5.20\webapps\wso2registry

Next, you need to copy the WEB-INF folder, which is in the folder which you extracted the downloaded Registry distribution. Then copy it into the registry folder which you created above.

E.g.:-
Copy
C:\Carbon\REGISTRY\tomcat\WSO2-registry-2.0.1\webapps\ROOT\WEB-INF
to
C:\WSO2\Installations\apache-tomcat-6.0.14\webapps\wso2registry

Step 5 - Changing necessary files of the WSO2 Registry distribution

a) Open the carbon.xml file which is in the CARBON_HOME\conf folder and specify the following URL as the backend ServerURL

E.g.:-
https://localhost:8443/wso2registry/services/

b) Next open the axis2.xml which is located inside the CARBON_HOME\conf and change the http port from 9763 to 8080 (the default http port of Tomcat) and the https port from 9443 to 8443.

c) In addition to the above, you need to specify the correct paths for the two .jks files wso2carbon.jks and client-truststore.jks specified in the axis2.xml and also the wso2carbon.jks file specified in the carbon.xml file.

d) Then you need to specify the absolute paths of the WSO2CARBON_DB of the two files registry.xml and user-mgt.xml

E.g.:- Change
jdbc:derby:database/WSO2CARBON_DB;create=true
to
jdbc:derby:C:\Carbon\REGISTRY\tomcat\registry_home\WSO2CARBON_DB;create=true

Step 6 - Starting the Apache Tomcat Server

Now you can start the Apache Tomcat server by giving the following command.
catalina.bat run

Step 7 - Login to the WSO2 Registry Administration Console

Now you should be able to login to the WSO2 Registry Administration Console as, https://localhost:8443/wso2registry/carbon

Guide to deploy other wso2 product on tomcat server is available also.

1. WSO2 Web Services Application Server (WSAS)
2. WSO2 Enterprise Service Bus (WSO2 ESB)
3. WSO2 Business Process Server (WSO2 BPS)

Using WSO2 Registry as URL-based repository for WSO2 Web Services Application Server (WSAS)

Here I discusses how to configure WSAS to use WSO2 registry as URL repository. Versions above WSAS 2.0 support URL-based repositories. It is simple to configure WSAS to use WSO2 Registry as repository. Let's follow step by step guide given below to do the configuration.

Step 1: Deploy WSAS binary distribution. See WSO2 WSAS Installation Guide for details.

Step 2: Deploy wso2registry.war file in a preferred servelet container it is matter of copying wso2registry.war file into your servelet container. See WSO2 Registry user guide for details. WSO2 Registry 1.1 can be downloaded from here.

Step 3: Go to http://localhost:8080/wso2registry. Note that port should be changed according to yours.

Step 4: Login to the system using user name “admin” and password “admin.

Step 5: Then go to add collection and create a collection with the name “wsas-repo” , and select Media Type as “application/vnd.wso2.wsas”. you will notice it creates a collection name "wsas-repo",there will be three sub collection called “services” , “modules” and “conf” inside the wsas-repo.

At the moment please ignore the “conf” directory.

Step 6: Next you need to upload WSAS administration modules into “wsas-repo”. To do that go to modules collection and upload following modules and module.list file by using “Add resource” option. These modules are shipped with WSAS binary distribution and can be found under the $WSO2WSAS_HOME/repository/module
(in my case /home/krishantha/wsas/wso2wsas-2.2.1/repository/modules on Linux).

Step 7: Same as the above step, now you need to upload WSAS default services in to “services” collections. To do that, go to “service” collection and upload following service files. These services are shipped with WSAS and can be found under the $WSO2WSAS_HOME/repository/services.

Step 8: Now you need to configure the registry URL repository in WSAS. Locate the server.xml file under the $WSO2WSAS_HOME/conf directory, and locate the following entry in the file.

<RepositoryLocation>${wso2wsas.home}/repository/<RepositoryLocation>

Change the "RepositoryLocation" entry to "http://localhost:8080/wso2registry/resources/wsas-repo".

Step 9: Restart WSAS server pointing to repository so all the available services under “services” collection will be deployed.

step 10: Check your WSO2 WSAS instance using the URL https://localhost:9443. Login as administrator with user name “admin” and password “admin”

Step 11: Now navigate though services link in WSAS admin console (Services > echo > Try Web Service) . And try out the echo sample.

FinallyIf you have done the above steps correctly then you will be able to invoke all the WSO2 WSAS default services without any problem.You can find nice tutorial explaining WSAS URL-based repositories from here.

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.