[Carbon-dev] svn commit r30560 - branches/carbon/1.5/trunk/esb/java/docs/xdoc
ruwan at wso2.com
ruwan at wso2.com
Thu Feb 5 23:33:57 PST 2009
Author: ruwan
Date: Thu Feb 5 23:33:57 2009
New Revision: 30560
URL: http://wso2.org/svn/browse/wso2?view=rev&revision=30560
Log:
Fixing the quickstart guide
Modified:
branches/carbon/1.5/trunk/esb/java/docs/xdoc/quickstart_guide.xml
Modified: branches/carbon/1.5/trunk/esb/java/docs/xdoc/quickstart_guide.xml
URL: http://wso2.org/svn/browse/wso2/branches/carbon/1.5/trunk/esb/java/docs/xdoc/quickstart_guide.xml?rev=30560&r1=30559&r2=30560&view=diff
==============================================================================
--- branches/carbon/1.5/trunk/esb/java/docs/xdoc/quickstart_guide.xml (original)
+++ branches/carbon/1.5/trunk/esb/java/docs/xdoc/quickstart_guide.xml Thu Feb 5 23:33:57 2009
@@ -20,10 +20,9 @@
-->
<!DOCTYPE html
- PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" >
-
-<html xmlns="http://www.w3.org/1999/xhtml">
+ PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"/>
<title>
@@ -50,15 +49,15 @@
<li>
<a href="#Pre-requis">Prerequisites</a>
</li>
- <li>
- <a href="#Message">Message Mediation</a>
- <ul>
- <li>
+ <li>
<a href="#Download">Download</a>
- </li>
- <li>
+ </li>
+ <li>
<a href="#Installati">Installation</a>
- </li>
+ </li>
+ <li>
+ <a href="#Message">Message Mediation</a>
+ <ul>
<li>
<a href="#Running">Running the Sample Scenario</a>
<ul>
@@ -144,7 +143,7 @@
</h3>
<p>
Our first task is to download the WSO2 ESB. Open a Web browser and access
- the following URL: http://dist.wso2.org/products/esb/java/. You will then
+ the following URL: <a href="http://wso2.org/downloads/esb/">http://wso2.org/downloads/esb/</a>. You will then
see the list of available releases. Click on the latest release version,
and you will be directed to the WSO2 ESB latestrelease download page. Now
download the binary distribution ZIP or tar.gz archive compatible with
@@ -190,55 +189,54 @@
You will see the following messages on the console to indicate that the
ESB started successfully.
</p>
-<pre xml:space="preserve"> Feb 5, 2009 1:27:02 PM org.wso2.carbon.server.Main main
-INFO: Starting WSO2 Carbon...
-Feb 5, 2009 1:27:02 PM org.wso2.carbon.server.Main main
-INFO: Using Java Home : C:\Program Files\Java\jdk1.5.0\jre
-Feb 5, 2009 1:27:02 PM org.wso2.carbon.server.Main main
-INFO: Using Java Version : 1.5.0_15
-Feb 5, 2009 1:27:02 PM org.wso2.carbon.server.Main main
-INFO: Using Carbon Home : F:\wso2esb-2.0\bin\..
-Feb 5, 2009 1:27:03 PM org.apache.catalina.startup.Embedded start
-INFO: Starting tomcat server
-Feb 5, 2009 1:27:03 PM org.apache.catalina.core.StandardEngine start
-INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
-Feb 5, 2009 1:27:03 PM org.apache.catalina.core.StandardHost start
-INFO: XML validation disabled
-Feb 5, 2009 1:27:03 PM org.apache.coyote.http11.Http11BaseProtocol init
-INFO: Initializing Coyote HTTP/1.1 on http-9763
+<pre xml:space="preserve"> Feb 5, 2009 1:27:02 PM org.wso2.carbon.server.Main main
+INFO: Starting WSO2 Carbon...
+Feb 5, 2009 1:27:02 PM org.wso2.carbon.server.Main main
+INFO: Using Java Home : C:\Program Files\Java\jdk1.5.0\jre
+Feb 5, 2009 1:27:02 PM org.wso2.carbon.server.Main main
+INFO: Using Java Version : 1.5.0_15
+Feb 5, 2009 1:27:02 PM org.wso2.carbon.server.Main main
+INFO: Using Carbon Home : F:\wso2esb-2.0\bin\..
+Feb 5, 2009 1:27:03 PM org.apache.catalina.startup.Embedded start
+INFO: Starting tomcat server
+Feb 5, 2009 1:27:03 PM org.apache.catalina.core.StandardEngine start
+INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
+Feb 5, 2009 1:27:03 PM org.apache.catalina.core.StandardHost start
+INFO: XML validation disabled
+Feb 5, 2009 1:27:03 PM org.apache.coyote.http11.Http11BaseProtocol init
+INFO: Initializing Coyote HTTP/1.1 on http-9763
Feb 5, 2009 1:27:04 P
-2009-02-05 13:21:17,328 [-] [Start Level Event Dispatcher] INFO Activator Using embedded Registry
-2009-02-05 13:21:17,328 [-] [Start Level Event Dispatcher] INFO Activator Registry is used in READ-WRITE mode
-2009-02-05 13:21:19,937 [-] [Start Level Event Dispatcher] INFO SynapseInitializationModule Initializing Synapse at : Thu Feb 05 13:21:19 PKT 2009
-2009-02-05 13:21:19,937 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Loading mediator extensions...
-2009-02-05 13:21:20,296 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Initializing the Synapse configuration ...
-2009-02-05 13:21:20,312 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO XMLConfigurationBuilder Generating the Synapse configuration model by parsing the XML configuration
-2009-02-05 13:21:20,406 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseConfigurationBuilder Loaded Synapse configuration from : conf/synapse.xml
-2009-02-05 13:21:20,406 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Deploying the Synapse service..
-2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Synapse server name : localhost
-2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Deploying Proxy services...
-2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Synapse initialized successfully...!
-2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSSLSender Loading Identity Keystore from : resources/security/wso2carbon.jks
-2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSSLSender Loading Trust Keystore from : resources/security/client-truststore.jks
-2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSender HTTPS Sender starting
-2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSender HTTP Sender starting
-2009-02-05 13:21:20,625 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO VFSTransportSender VFS Sender started
-2009-02-05 13:21:20,828 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO JMSSender JMS Sender started
-
-2009-02-05 13:21:23,390 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO DefaultServerInitializer Repository : F:\WSO2ES~1.0\bin\../repository/
-2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSSLListener Loading Identity Keystore from : resources/security/wso2carbon.jks
-2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSSLListener Loading Trust Keystore from : resources/security/client-truststore.jks
-2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOListener HTTPS Listener starting on port : 8243
-2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOListener HTTP Listener starting on port : 8280
-
-2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO StartupServlet HTTPS port : 9443
-2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO StartupServlet HTTP port : 9763
-
+2009-02-05 13:21:17,328 [-] [Start Level Event Dispatcher] INFO Activator Using embedded Registry
+2009-02-05 13:21:17,328 [-] [Start Level Event Dispatcher] INFO Activator Registry is used in READ-WRITE mode
+2009-02-05 13:21:19,937 [-] [Start Level Event Dispatcher] INFO SynapseInitializationModule Initializing Synapse at : Thu Feb 05 13:21:19 PKT 2009
+2009-02-05 13:21:19,937 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Loading mediator extensions...
+2009-02-05 13:21:20,296 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Initializing the Synapse configuration ...
+2009-02-05 13:21:20,312 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO XMLConfigurationBuilder Generating the Synapse configuration model by parsing the XML configuration
+2009-02-05 13:21:20,406 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseConfigurationBuilder Loaded Synapse configuration from : conf/synapse.xml
+2009-02-05 13:21:20,406 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Deploying the Synapse service..
+2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Synapse server name : localhost
+2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Deploying Proxy services...
+2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO SynapseInitializationModule Synapse initialized successfully...!
+2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSSLSender Loading Identity Keystore from : resources/security/wso2carbon.jks
+2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSSLSender Loading Trust Keystore from : resources/security/client-truststore.jks
+2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSender HTTPS Sender starting
+2009-02-05 13:21:20,609 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSender HTTP Sender starting
+2009-02-05 13:21:20,625 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO VFSTransportSender VFS Sender started
+2009-02-05 13:21:20,828 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO JMSSender JMS Sender started
+
+2009-02-05 13:21:23,390 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO DefaultServerInitializer Repository : F:\WSO2ES~1.0\bin\../repository/
+2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSSLListener Loading Identity Keystore from : resources/security/wso2carbon.jks
+2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOSSLListener Loading Trust Keystore from : resources/security/client-truststore.jks
+2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOListener HTTPS Listener starting on port : 8243
+2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO HttpCoreNIOListener HTTP Listener starting on port : 8280
+
+2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO StartupServlet HTTPS port : 9443
+2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO StartupServlet HTTP port : 9763
+
2009-02-05 13:21:23,546 [10.100.1.90-wso2-3d9598d678] [Start Level Event Dispatcher] INFO StartupServlet WSO2 Carbon started in 16 sec</pre>
<p/>
- <p>Above start-up was captured without changing the log level to DEBUG</p>
- <p></p>
+ <p><strong>Note:</strong> Above start-up was captured without changing the log level to DEBUG</p>
<h4 id="Configurin">
Configuring the ESB to Perform Message Mediation
</h4>
@@ -249,17 +247,17 @@
sufficient for our first scenario. Later on, we will change this
configuration using the management console to build different mediations.
Now examine the default configuration using the ESB console. Open a Web
- browser and point it to the URL https://localhost:9443/carbon. You will be
+ browser and point it to the URL <a href="https://localhost:9443/carbon">https://localhost:9443/carbon</a>. You will be
directed to the log-in screen of the management console shown below.
</p>
<p/>
<p>
<img alt="Login screen" src="images/login.png"/>
+ <br/>
</p>
- <p/>
<p>
The management console ships with a default username and password called
- "admin". Type "admin" in both the username and password fields and click
+ "admin". Type "admin" (without quotes) in both the username and password fields and click
Sign In. You will be directed to the home page of the ESB management
console, which displays information about the system on which you are running the ESB.
In the left side of the management console you can see a set of menu items.
@@ -271,18 +269,18 @@
</p>
<p/>
<p>
- Now it is time to examine the mediation configuration visually. Click on
- the "Sequences" link under "Manage->Mediation". You will see that two sequences
- named "fault" and "main" are currently available. These two sequences are
- generated automatically by the ESB at start up. We can add any number of
- sequences using this page to suit our mediation requirement. However these
- pre-defined sequences are sufficient for this sample application.
- </p>
- <p>
- <img alt="Sequences" src="images/sequences.png"/>
- </p>
- <p>Let's analyze what happens to the messages, inside the main sequence by clicking
- on the "Edit" link in front of the sequence name "main". You will see a
+ Now it is time to examine the mediation configuration visually. Click on
+ the "Sequences" link under "Manage->Mediation". You will see that two sequences
+ named "fault" and "main" are currently available. These two sequences are
+ generated automatically by the ESB at start up. We can add any number of
+ sequences using this page to suit our mediation requirement. However these
+ pre-defined sequences are sufficient for this sample application.
+ </p>
+ <p>
+ <img alt="Sequences" src="images/sequences.png"/>
+ </p>
+ <p>Let's analyze what happens to the messages, inside the main sequence by clicking
+ on the "Edit" link in front of the sequence name "main". You will see a
Tree of mediators listed for the main sequence as shown below.
</p>
<p/>
@@ -292,23 +290,19 @@
<p/>
<p/>
<p>
- The mediation sequence (visually represented as a Tree) starts with a Root.
- You will see there are two nodes named "In" and "Out" as siblings of the Root.
- Every node in this tree is a mediator. So In and Out nodes represent the
- "In Mediator" and "Out Mediator". These two mediators handle request messages
- and response messages respectively. Inside the In Mediator, two mediators
- named Log Mediator and Filter Mediator are listed as children. Therefore,
- incoming messages will flow through these two mediators. To see the configuration
- for a specific mediator click on its corresponding node in the sequence tree.
- You will see the configuration for a mediator in the bottom of the page as shown below.
- Configuration for the log mediator is shown in the image below. If you
- want to change this configuration for a mediator, first you need to click
- on the mediator node in the tree. Then mediator specific configuration will appear
- on the bottom of the page. Now you can edit the configuration for the mediator and click
+ The mediation sequence (visually represented as a Tree) starts with a Root.
+ You will see there are two nodes named "In" and "Out" as siblings of the Root.
+ Every node in this tree is a mediator. So In and Out nodes represent the
+ "In Mediator" and "Out Mediator". These two mediators handle request messages
+ and response messages respectively. Inside the In Mediator, two mediators
+ named Log Mediator and Filter Mediator are listed as children. Therefore,
+ incoming messages will flow through these two mediators. To see the configuration
+ for a specific mediator click on its corresponding node in the sequence tree.
+ You will see the configuration for a mediator in the bottom of the page as shown below.
+ Configuration for the log mediator is shown in the image below. Now you can edit the configuration for the mediator and click
on the "Update" button. After you have done the changes to the mediators, you need to
save the sequence by clicking on the "Save" button on the bottom of the page.
</p>
- <p></p>
<p><img alt="Log Mediator Configuration" src="images/log_mediator_conf.png"/></p>
<p>
You will notice that Log Mediator is configured to log all the details of
@@ -351,27 +345,27 @@
server.
</p>
<pre xml:space="preserve">F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService>ant
-Buildfile: build.xml
-
-clean:
- [delete] Deleting directory F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp
-
-init:
- [mkdir] Created dir: F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp
- [mkdir] Created dir: F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\classes
-
-compile-all:
- [javac] Compiling 9 source files to F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\classes
-
-build-service:
- [mkdir] Created dir: F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\SimpleStockQuote
- [mkdir] Created dir: F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\SimpleStockQuote\META-INF
- [copy] Copying 1 file to F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\SimpleStockQuote\META-INF
- [copy] Copying 1 file to F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\SimpleStockQuote\META-INF
- [copy] Copying 9 files to F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\SimpleStockQuote
- [jar] Building jar: F:\wso2esb-2.0\samples\axis2Server\repository\services\SimpleStockQuoteService.aar
-
-BUILD SUCCESSFUL
+Buildfile: build.xml
+
+clean:
+ [delete] Deleting directory F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp
+
+init:
+ [mkdir] Created dir: F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp
+ [mkdir] Created dir: F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\classes
+
+compile-all:
+ [javac] Compiling 9 source files to F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\classes
+
+build-service:
+ [mkdir] Created dir: F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\SimpleStockQuote
+ [mkdir] Created dir: F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\SimpleStockQuote\META-INF
+ [copy] Copying 1 file to F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\SimpleStockQuote\META-INF
+ [copy] Copying 1 file to F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\SimpleStockQuote\META-INF
+ [copy] Copying 9 files to F:\wso2esb-2.0\samples\axis2Server\src\SimpleStockQuoteService\temp\SimpleStockQuote
+ [jar] Building jar: F:\wso2esb-2.0\samples\axis2Server\repository\services\SimpleStockQuoteService.aar
+
+BUILD SUCCESSFUL
Total time: 2 seconds</pre>
<p>
Now go to <esb-home>/samples/axis2Server directory and start the
@@ -384,37 +378,37 @@
<p>
You will see the following messages on the console.
</p>
-<pre xml:space="preserve">"Starting Sample Axis2 Server ..."
-Using AXIS2_HOME: F:\WSO2ES~1.0\samples\AXIS2S~1\
-Using JAVA_HOME: C:\Program Files\Java\jdk1.5.0
---> Wrapper Started as Console
-Launching a JVM...
-Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
- Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
-
-[SimpleAxisServer] Using the Axis2 Repository : F:\WSO2ES~1.0\samples\AXIS2S~1\repository
-[SimpleAxisServer] Using the Axis2 Configuration File : F:\WSO2ES~1.0\samples\AXIS2S~1\repository\conf\axis2.xml
-2009-02-05 14:04:53,062 [-] [WrapperSimpleAppMain] ERROR SandeshaModule Could not load module policies. Using default values.
-2009-02-05 14:04:53,093 [-] [WrapperSimpleAppMain] ERROR SandeshaModule Could not load module policies. Using default values.
-2009-02-05 14:04:53,093 [-] [WrapperSimpleAppMain] INFO SynapseInitializationModule Initializing Synapse at : Thu Feb 05 14:04:53 PKT 2009
-2009-02-05 14:04:53,093 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Loading mediator extensions...
-2009-02-05 14:04:53,625 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Initializing the Synapse configuration ...
-2009-02-05 14:04:53,656 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] WARN SynapseInitializationModule System property or init-parameter 'synapse.xml' is not specified. Using default configuration..
-2009-02-05 14:04:53,687 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Deploying the Synapse service..
-2009-02-05 14:04:53,687 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Synapse server name : localhost
-2009-02-05 14:04:53,687 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Deploying Proxy services...
-2009-02-05 14:04:53,687 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Synapse initialized successfully...!
-2009-02-05 14:04:53,734 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSSLSender Loading Identity Keystore from : ../../resources/security/wso2carbon.jks
-2009-02-05 14:04:53,750 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSSLSender Loading Trust Keystore from : ../../resources/security/client-truststore.jks
-2009-02-05 14:04:53,765 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSender HTTPS Sender starting
-2009-02-05 14:04:53,796 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSender HTTP Sender starting
-2009-02-05 14:04:53,796 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO JMSSender JMS Sender started
-2009-02-05 14:04:53,828 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSSLListener Loading Identity Keystore from : ../../resources/security/wso2carbon.jks
-2009-02-05 14:04:53,828 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSSLListener Loading Trust Keystore from : ../../resources/security/client-truststore.jks
-2009-02-05 14:04:53,843 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOListener HTTPS Listener starting on port : 9002
-2009-02-05 14:04:53,843 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOListener HTTP Listener starting on port : 9000
-2009-02-05 14:04:53,843 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO MailTransportListener MAILTO Listener started
-2009-02-05 14:04:53,859 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] WARN MailTransportListener Error configuring the Mail transport for Service : SimpleStockQuoteService :: Cannot find parameter : transport.mail.Address for service : SimpleStockQuoteService
+<pre xml:space="preserve">"Starting Sample Axis2 Server ..."
+Using AXIS2_HOME: F:\WSO2ES~1.0\samples\AXIS2S~1\
+Using JAVA_HOME: C:\Program Files\Java\jdk1.5.0
+--> Wrapper Started as Console
+Launching a JVM...
+Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
+ Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved.
+
+[SimpleAxisServer] Using the Axis2 Repository : F:\WSO2ES~1.0\samples\AXIS2S~1\repository
+[SimpleAxisServer] Using the Axis2 Configuration File : F:\WSO2ES~1.0\samples\AXIS2S~1\repository\conf\axis2.xml
+2009-02-05 14:04:53,062 [-] [WrapperSimpleAppMain] ERROR SandeshaModule Could not load module policies. Using default values.
+2009-02-05 14:04:53,093 [-] [WrapperSimpleAppMain] ERROR SandeshaModule Could not load module policies. Using default values.
+2009-02-05 14:04:53,093 [-] [WrapperSimpleAppMain] INFO SynapseInitializationModule Initializing Synapse at : Thu Feb 05 14:04:53 PKT 2009
+2009-02-05 14:04:53,093 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Loading mediator extensions...
+2009-02-05 14:04:53,625 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Initializing the Synapse configuration ...
+2009-02-05 14:04:53,656 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] WARN SynapseInitializationModule System property or init-parameter 'synapse.xml' is not specified. Using default configuration..
+2009-02-05 14:04:53,687 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Deploying the Synapse service..
+2009-02-05 14:04:53,687 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Synapse server name : localhost
+2009-02-05 14:04:53,687 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Deploying Proxy services...
+2009-02-05 14:04:53,687 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO SynapseInitializationModule Synapse initialized successfully...!
+2009-02-05 14:04:53,734 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSSLSender Loading Identity Keystore from : ../../resources/security/wso2carbon.jks
+2009-02-05 14:04:53,750 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSSLSender Loading Trust Keystore from : ../../resources/security/client-truststore.jks
+2009-02-05 14:04:53,765 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSender HTTPS Sender starting
+2009-02-05 14:04:53,796 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSender HTTP Sender starting
+2009-02-05 14:04:53,796 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO JMSSender JMS Sender started
+2009-02-05 14:04:53,828 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSSLListener Loading Identity Keystore from : ../../resources/security/wso2carbon.jks
+2009-02-05 14:04:53,828 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOSSLListener Loading Trust Keystore from : ../../resources/security/client-truststore.jks
+2009-02-05 14:04:53,843 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOListener HTTPS Listener starting on port : 9002
+2009-02-05 14:04:53,843 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO HttpCoreNIOListener HTTP Listener starting on port : 9000
+2009-02-05 14:04:53,843 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] INFO MailTransportListener MAILTO Listener started
+2009-02-05 14:04:53,859 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] WARN MailTransportListener Error configuring the Mail transport for Service : SimpleStockQuoteService :: Cannot find parameter : transport.mail.Address for service : SimpleStockQuoteService
2009-02-05 14:04:53,859 [10.100.1.90-wso2-3d9598d678] [WrapperSimpleAppMain] WARN MailTransportListener Disabling the mailto transport for the service SimpleStockQuoteService, because it is not configured properly for the service</pre>
<p/>
<h4 id="Running1">
@@ -429,20 +423,20 @@
You can see the following output with the quote price sent by the server.
</p>
<pre xml:space="preserve">F:\wso2esb-2.0\samples\axis2Client$ ant stockquote -Daddurl=http://localhost:9000/soap/SimpleStockQuoteService -Dtrpurl=http://localhost:8280 -Dsymbol=IBM -Dmode=quote
-Buildfile: build.xml
-
-init:
-
-compile:
-
-stockquote:
- [java] 2009-02-05 14:17:04,281 [-] [main] ERROR SandeshaModule Could not load module policies. Using default values.
- [java] 2009-02-05 14:17:04,312 [-] [main] ERROR SandeshaModule Could not load module policies. Using default values.
- [java] 2009-02-05 14:17:04,406 [-] [main] INFO MailTransportSender MAILTO Sender started
- [java] 2009-02-05 14:17:04,468 [-] [main] INFO JMSSender JMS Sender started
- [java] Standard :: Stock price = $149.52982574060746
-
-BUILD SUCCESSFUL
+Buildfile: build.xml
+
+init:
+
+compile:
+
+stockquote:
+ [java] 2009-02-05 14:17:04,281 [-] [main] ERROR SandeshaModule Could not load module policies. Using default values.
+ [java] 2009-02-05 14:17:04,312 [-] [main] ERROR SandeshaModule Could not load module policies. Using default values.
+ [java] 2009-02-05 14:17:04,406 [-] [main] INFO MailTransportSender MAILTO Sender started
+ [java] 2009-02-05 14:17:04,468 [-] [main] INFO JMSSender JMS Sender started
+ [java] Standard :: Stock price = $149.52982574060746
+
+BUILD SUCCESSFUL
Total time: 2 seconds</pre>
<p>
This sends a request for a stock quote for the symbol IBM, sets the
@@ -610,8 +604,8 @@
Now click on "Address Endpoint". You'll get a form with various options
for defining an Address endpoint.
</p>
- <img alt="Address Endpoint"
- src="images/qs_address.png"/>
+ <p><img alt="Address Endpoint"
+ src="images/qs_address.png"/></p>
<p>
Here just type "http://localhost:9000/services/SimpleStockQuoteService"
for the Address field. Keep other fields unchanged and click "Save" to
@@ -637,8 +631,7 @@
<img alt="Out Sequence"
src="images/qs_out_sequence.png"/>
</p>
- <p></p>
- <p>
+ <p>
Click "Save" to save the out sequence configuration. Then click "Finish" to end
proxy wizard creation. When you click "Finish" you will be directed
to the Service management page.
@@ -654,7 +647,6 @@
<p>
<img alt="Service Dashboard (StockQuoteProxy)" src="images/qs_proxy_dashbord_in.png"/>
</p>
- <p></p>
<p>
On the "Service Dashboard (StockQuoteProxy)" page you will see various
details of the proxy service. Click on "Enable Statistics" and
@@ -721,7 +713,6 @@
<p>
<img alt="Overall statistics" src="images/qs_ps_overall_stats.png"/>
</p>
- <p></p>
<p>
To get more information about proxy service statistics click on the
"Proxy Service Statistics" link in the top right box. You will see
@@ -735,7 +726,7 @@
<p/>
<p>
This quick guide illustrates the visual construction of a proxy service
- and a simple use case. Please refer to samples #150 and above in the
+ and a simple use case. Please refer to <a href="samples/proxy_samples.html#Sample150">samples #150</a> and above in the
Samples guide, for in-depth coverage of more advanced use cases. You don't
have to worry about the configuration language too much when reading the
samples. You can build all those samples visually using the ESB management
More information about the Carbon-dev
mailing list