How to run multiple WSO2 WSAS instances in a single host

Charitha Kankanamge - WSO2 Technical lead/Manager for Quality Assurance in just 3 quick steps describes how to run multiple WSO2 WSAS instances in a single host.

Date: Tue, 29th Sep, 2009
Level: Introductory
Reads: 2434 Comments: 3 | Login or register to post comments
Charitha Kankanamge
Manager QA
WSO2 Inc.
charithak's picture

In this 3 step short tutorial, Charitha describes how you can configure your WSO2 WSAS instances to facilitate more than one instance within a single host.

Step 1

Download the latest version of WSO2 WSAS from here

Extract the downloaded zip in to a directory in your file system. We can name this location as CARBON_HOME

Step 2

Go to CARBON_HOME/conf directory and the open transports.xml file. Update the http and https ports as follows:

<transport name="http" class="org.wso2.carbon.server.transports.http.HttpTransport">

<parameter name="port">9764</parameter>

 

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

<parameter name="port">9444</parameter>

Save and close the file.

Step 3

Similarly, change the ports of the other WSO2 WSAS instances. You can follow the same steps to change the default ports in WSO2 Governance Registry, WSO2 Identity Server and WSO2 Mashup Server products.

Step 4

In the case of the WSO2 ESB, in addition to the above change, you should change the non-blocking HttpCore + NIO transports in CARBON_HOME/conf/axis2.xml

 <transportReceiver name="http" class="org.apache.synapse.transport.nhttp.HttpCoreNIOListener">
 <parameter name="port" locked="false">8281</parameter>

  <transportReceiver name="https" class="org.apache.synapse.transport.nhttp.HttpCoreNIOSSLListener">
  <parameter name="port" locked="false">8244</parameter>

 

Applies To:- WSO2 WSAS-3.0 or later, WSO2 ESB-2.0 or later, WSO2 Governance Registry-2.0 or later, WSO2-IS-1.5 or later

 

jim.telford@infousa.com's picture

Tried this get login issues

I tried the steps above, but when I do this I get login issues. It appears as though when I log into one (server1), and then login to another (server2) the second login force a logout on the first server (server1).

It would seem the only thing that they are sharing is the Keystore values: CN=wso2carbon, OU=None, L=Seattle, ST=Washington, O=WSO2, C=LK for instance. Is this causing my problem?

Thanks for any light you can shed on the issue.

Cheers!

samindaw's picture

I think the reason for this

I think the reason for this is that you may be using the same browser instance. For example if you are using IE to access one server, try using firefox or anyother browser to access the other browser. See it is works. You can also use different firefox profiles also.

Saminda

jim.telford@infousa.com's picture

That was it!

Thanks Samindaw!

I didn't even think about the client side....

Thanks Again!

Hot Topic
Hot
Topic

Google Gadgets are a nice way to develop user interfaces for distributed services. The fact that they can be hosted anywhere over a network, not necessarily in the very portal server they eventually run in makes them re-usable and allows users to quickly...

Mini Banners
WSO2Con 2010
Latest Webinar
In this webinar we'll share the range of concerns we've heard from the industry, and survey some of the new and sometimes subtle types of lock-in associated with cloud technologies.
Wednesday, 8 September, 10.00 AM (PDT)