You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stratos.apache.org by la...@apache.org on 2013/07/22 17:00:13 UTC
[18/19] applied 0001-Removed-stratos2-folder-from-products.patch
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/docs/xdoc/admin_guide.xml
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/admin_guide.xml b/products/stratos2/cloud_controller/1.0.0/docs/xdoc/admin_guide.xml
deleted file mode 100644
index 3461c36..0000000
--- a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/admin_guide.xml
+++ /dev/null
@@ -1,484 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
- ~ Copyright (c) 2005-2010, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
- ~
- ~ WSO2 Inc. licenses this file to you under the Apache License,
- ~ Version 2.0 (the "License"); you may not use this file except
- ~ in compliance with the License.
- ~ You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- ~ KIND, either express or implied. See the License for the
- ~ specific language governing permissions and limitations
- ~ under the License.
- -->
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
- <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
- <title>WSO2 MB - System Administration Guide</title>
- <link href="css/mb-docs.css" rel="stylesheet" />
- <link href="styles/dist-docs.css" rel="stylesheet" type="text/css"
- media="all" />
-</head>
-
-<body>
-<h2>WSO2 MB - System Administration Guide </h2>
-
-<h4>Contents </h4>
-
-<p>1.0 Introduction<br />
-2.0 Document Conventions<br />
-3.0 Getting WSO2 MB<br />
-4.0 Installing and Running WSO2 MB<br />
-4.1 Running the MB in Standalone Mode<br />
-4.2 Running MB Samples<br />
-6.0 Using the WSO2 MB Management Console<br />
-7.0 User Management<br />
-8.0 Setting Up Logging<br />
-9.0 Configuring the Underlying Axis2 Engine<br />
-10.0 Adding External Dependencies to the System<br />
-11.0 Registry Integration<br />
-11.1 Using the Embedded Registry<br />
-11.2 Using a Remote Registry<br />
-12.0 Setting Up Key Stores<br />
-13.0 Setting Up Host Names and Ports<br />
-</p>
-
-<h4>1.0 Introduction </h4>
-
-<p>WSO2 MB is an open source Message Broker solution.It is to be your Message
-Broker System. Our ultimate goal is to provide you a reliable Message
-Brokering System</p>
-
-
-<p>WSO2 MB is based on the revolutionary WSO2
-Carbon framework. WSO2 Carbon is an OSGi based middleware framework for SOA.
-Currently all WSO2 Java products are based on WSO2 Carbon including WSO2
-Governance Registry and WSO2 WSAS. Since MB is OSGi based some knowledge in
-OSGi would be helpful in administrating the WSO2 MB. </p>
-
-<p>This document explains how to get WSO2 MB and install it on a server. The
-latter sections of the document illustrates how to setup and configure various
-features of the WSO2 MB. </p>
-
-<h4>2.0 Document Conventions </h4>
-<ul>
- <li>The phrase 'MB_HOME' refers to the directory in the file system where
- WSO2 MB is installed</li>
- <li>The phrase 'MB_SRC_HOME' refers to the directory in the file system
- where WSO2 MB source distribution is installed</li>
- <li>All file paths follow Unix/Linux conventions but they resemble Windows
- file paths as well</li>
-</ul>
-
-<h4>3.0 Getting WSO2 MB </h4>
-
-<p>Binary distributions and source distributions of WSO2 MB can be downloaded
-free from the <a href="http://wso2.com/products/message-broker/">WSO2 MB project</a> home
-page in the <a href="http://wso2.org">WSO2 Oxygen Tank</a>. Before proceeding
-to the downloads page you will be asked to register on the WSO2 Oxygen Tank.
-Registration is free and optional however it is recommended that you sign up
-for an account right away since registered Oxygen Tank users get exclusive
-access to our support forums and tons of valuable content related to SOA and
-Web Services. </p>
-
-<p>Once you are on the downloads page click on the relevant links to download a
-binary distribution or a source distribution of the alpha release of
-the WSO2 MB.</p>
-
-<p>If you downloaded a source distribution of the MB you need to build the
-source to get the executable binary. WSO2 MB uses an <a
-href="http://maven.apache.org">Apache Maven2</a> based build system and
-therefore you need to first download and install Apache Maven2. Please refer
-Maven2 documentation on installing and configuring Apache Maven2. Also note
-that Apache Maven2 requires Java to run. Once Maven2 is properly configured
-extract the downloaded source distribution and change your working directory to
-the directory that is created. Then execute the command mvn clean install to
-run the builder. Once the build process is complete you can find the binary
-distribution archive in MB_SRC_HOME/modules/distribution/target directory. </p>
-
-<h4>4.0 Installing and Running WSO2 MB </h4>
-
-<p>To install the WSO2 MB simply extract the downloaded binary distribution
-archive. If you built WSO2 MB from source extract the archive created by the
-builder. We recommend installing WSO2 MB on a Unix/Linux system since that
-will enable you to get the maximum out of the MB. In order to be able to start
-WSO2 MB you first need Java 6 or higher. Having installed Java on your system
-please set the JAVA_HOME environment variable to point to the directory in
-which Java is installed. </p>
-
-<h5>4.1 Running WSO2 MB in Standalone Mode </h5>
-
-<p>Now you are all set to start WSO2 MB in the standalone mode. Go to
-MB_HOME/bin directory and if you are on Unix/Linux execute the wso2server.sh
-shell script or if you are on Windows execute the wso2server.bat batch file.
-This will start the MB and you can see the progress of the startup procedure
-on the console. Please note that server startup may take some time depending on
-the hardware configuration of your system. The first time startup can take up
-few additional seconds since some first time configuration logic is run by the
-MB. If the server started up cleanly you should get an output similar to the
-following on the console. </p>
-<pre>[2011-02-07 16:18:14,748] INFO {org.wso2.carbon.server.Main} - Initializing system...
-[2011-02-07 16:18:15,121] INFO {org.wso2.carbon.server.TomcatCarbonWebappDeployer} - Deployed Carbon webapp: StandardEngine[carbonEngine].StandardHost[defaulthost].StandardContext[/]
-[2011-02-07 16:18:20,721] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Starting WSO2 Carbon...
-[2011-02-07 16:18:20,744] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Operating System : Linux 2.6.32-27-generic, i386
-[2011-02-07 16:18:20,744] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Java Home : /opt/softwares/jdk1.6.0_17/jre
-[2011-02-07 16:18:20,744] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Java Version : 1.6.0_17
-[2011-02-07 16:18:20,744] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Java VM : Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc.
-[2011-02-07 16:18:20,744] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Carbon Home : /home/shammi/wso2/checkouts/carbon-trunk/carbon/products/mb/modules/distribution/target/wso2mb-1.0.0
-[2011-02-07 16:18:20,744] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Java Temp Dir : /home/shammi/wso2/checkouts/carbon-trunk/carbon/products/mb/modules/distribution/target/wso2mb-1.0.0/tmp
-[2011-02-07 16:18:20,744] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - User : shammi, en-US, Asia/Colombo
-[2011-02-07 16:18:25,531] INFO {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} - Registry Mode : READ-WRITE
-[2011-02-07 16:18:26,833] INFO {org.apache.qpid.wso2.internal.QpidBundleActivator} - Setting BundleContext in PluginManager
-[Broker] BRK-1006 : Using configuration : /home/shammi/wso2/checkouts/carbon-trunk/carbon/products/mb/modules/distribution/target/wso2mb-1.0.0/repository/conf/qpid/etc/config.xml
-Logging configuration error: unable to read file /home/shammi/wso2/checkouts/carbon-trunk/carbon/products/mb/modules/distribution/target/wso2mb-1.0.0/repository/conf/qpid/etc/log4j.xml
-Using the fallback internal log4j.properties configuration
-[2011-02-07 16:18:26,976] INFO {org.apache.qpid.server.registry.ApplicationRegistry} - Initialising Application Registry(org.apache.qpid.server.registry.ConfigurationFileApplicationRegistry@1adff28):1
-[2011-02-07 16:18:27,008] INFO {org.apache.qpid.server.plugins.PluginManager} - Opened service trackers
-[2011-02-07 16:18:27,022] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Elements to lookup:
-[2011-02-07 16:18:27,022] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'queue'
-[2011-02-07 16:18:27,022] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'virtualhosts'
-[2011-02-07 16:18:27,027] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'com'
-[2011-02-07 16:18:27,027] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'common'
-[2011-02-07 16:18:27,027] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'catalina'
-[2011-02-07 16:18:27,027] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'package'
-[2011-02-07 16:18:27,027] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'QPID_HOME'
-[2011-02-07 16:18:27,027] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'line'
-[2011-02-07 16:18:27,027] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'cache-directory'
-[2011-02-07 16:18:27,027] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'security'
-[2011-02-07 16:18:27,027] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'conf'
-[2011-02-07 16:18:27,028] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'osgi'
-[2011-02-07 16:18:27,028] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'wso2'
-[2011-02-07 16:18:27,028] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'sun'
-[2011-02-07 16:18:27,028] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'tomcat'
-[2011-02-07 16:18:27,028] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'javax'
-[2011-02-07 16:18:27,028] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'carbon'
-[2011-02-07 16:18:27,028] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'file'
-[2011-02-07 16:18:27,028] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'advanced'
-[2011-02-07 16:18:27,028] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'path'
-[2011-02-07 16:18:27,029] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'plugin-directory'
-[2011-02-07 16:18:27,029] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'work'
-[2011-02-07 16:18:27,029] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'shared'
-[2011-02-07 16:18:27,029] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'os'
-[2011-02-07 16:18:27,029] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'impl'
-[2011-02-07 16:18:27,029] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'status-updates'
-[2011-02-07 16:18:27,029] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'axis2'
-[2011-02-07 16:18:27,029] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'heartbeat'
-[2011-02-07 16:18:27,030] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'prefix'
-[2011-02-07 16:18:27,030] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'wso2carbon'
-[2011-02-07 16:18:27,030] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'connector'
-[2011-02-07 16:18:27,030] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'java'
-[2011-02-07 16:18:27,030] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'server'
-[2011-02-07 16:18:27,030] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'components'
-[2011-02-07 16:18:27,030] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'management'
-[2011-02-07 16:18:27,030] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'user'
-[2011-02-07 16:18:27,038] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'amqj'
-[2011-02-07 16:18:27,038] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'log4j'
-[2011-02-07 16:18:27,042] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Elements to lookup:security
-[2011-02-07 16:18:27,042] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'msg-auth'
-[2011-02-07 16:18:27,042] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'principal-databases'
-[2011-02-07 16:18:27,042] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'jmx'
-[2011-02-07 16:18:27,047] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Elements to lookup:security.principal-databases
-[2011-02-07 16:18:27,047] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'principal-database'
-[2011-02-07 16:18:27,047] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Elements to lookup:security.jmx
-[2011-02-07 16:18:27,047] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'principal-database'
-[2011-02-07 16:18:27,047] INFO {org.apache.qpid.server.configuration.plugins.ConfigurationPlugin} - Tag:'access'
-[Broker] BRK-1001 : Startup : Version: 0.9 Build: 1041962M
-[2011-02-07 16:18:27,163] INFO {qpid.message.broker.startup} - [Broker] BRK-1001 : Startup : Version: 0.9 Build: 1041962M
-[2011-02-07 16:18:27,166] INFO {org.apache.qpid.server.management.JMXManagedObjectRegistry} - Initialising managed object registry using platform MBean server
-[2011-02-07 16:18:27,173] INFO {org.apache.qpid.server.security.auth.database.ConfigurationFilePrincipalDatabaseManager} - Initialising PrincipalDatabase authentication manager
-[2011-02-07 16:18:27,177] INFO {org.apache.qpid.server.security.auth.database.ConfigurationFilePrincipalDatabaseManager} - Initialised principal database 'carbon-user-store' successfully
-[2011-02-07 16:18:27,178] INFO {org.apache.qpid.server.security.auth.manager.PrincipalDatabaseAuthenticationManager} - Initialising Default PrincipalDatabase authentication manager.
-[2011-02-07 16:18:27,179] INFO {org.apache.qpid.server.security.auth.manager.PrincipalDatabaseAuthenticationManager} - Initialised PLAIN SASL provider successfully
-[2011-02-07 16:18:27,211] INFO {org.apache.qpid.server.security.auth.manager.PrincipalDatabaseAuthenticationManager} - Additional SASL providers successfully registered.
-[Broker] MNG-1001 : Startup
-[2011-02-07 16:18:27,243] INFO {qpid.message.managementconsole.startup} - [Broker] MNG-1001 : Startup
-[Broker] MNG-1004 : Ready : Using the platform JMX Agent
-[2011-02-07 16:18:27,244] INFO {qpid.message.managementconsole.ready} - [Broker] MNG-1004 : Ready : Using the platform JMX Agent
-[2011-02-07 16:18:27,249] INFO {qpid.message.virtualhost.created} - [Broker] VHT-1001 : Created : carbon
-[2011-02-07 16:18:27,290] INFO {qpid.message.exchange.created} - [Broker] EXH-1001 : Create : Durable Type: headers Name: amq.match
-[2011-02-07 16:18:27,295] INFO {qpid.message.exchange.created} - [Broker] EXH-1001 : Create : Durable Type: topic Name: amq.topic
-[2011-02-07 16:18:27,297] INFO {qpid.message.exchange.created} - [Broker] EXH-1001 : Create : Durable Type: direct Name: amq.direct
-[2011-02-07 16:18:27,299] INFO {qpid.message.exchange.created} - [Broker] EXH-1001 : Create : Durable Type: fanout Name: amq.fanout
-[2011-02-07 16:18:27,302] INFO {qpid.message.exchange.created} - [Broker] EXH-1001 : Create : Durable Type: direct Name: default
-[2011-02-07 16:18:27,309] INFO {qpid.message.exchange.created} - [Broker] EXH-1001 : Create : Durable Type: direct Name: carbon.direct
-[2011-02-07 16:18:27,310] INFO {qpid.message.exchange.created} - [Broker] EXH-1001 : Create : Type: topic Name: carbon.topic
-[2011-02-07 16:18:27,322] INFO {qpid.message.configstore.created} - [Broker] [vh(/carbon)/ms(DerbyMessageStore)] CFG-1001 : Created : org.apache.qpid.server.store.DerbyMessageStore
-[2011-02-07 16:18:27,510] INFO {qpid.message.messagestore.store_location} - [Broker] [vh(/carbon)/ms(DerbyMessageStore)] MST-1002 : Store location : /home/shammi/wso2/checkouts/carbon-trunk/carbon/products/mb/modules/distribution/target/wso2mb-1.0.0/repository/database/qpid/derbystore
-[2011-02-07 16:18:29,360] INFO {qpid.message.messagestore.recovery_start} - [Broker] [vh(/carbon)/ms(DerbyMessageStore)] MST-1004 : Recovery Start
-[2011-02-07 16:18:29,362] INFO {qpid.message.transactionlog.recovery_start} - [Broker] [vh(/carbon)/ms(DerbyMessageStore)] TXN-1004 : Recovery Start
-[2011-02-07 16:18:29,381] INFO {org.apache.qpid.server.store.DerbyMessageStore} - Recovering bindings...
-[2011-02-07 16:18:29,399] INFO {qpid.message.messagestore.created} - [Broker] [vh(/carbon)/ms(DerbyMessageStore)] MST-1001 : Created : org.apache.qpid.server.store.DerbyMessageStore
-[2011-02-07 16:18:29,406] INFO {qpid.message.transactionlog.created} - [Broker] [vh(/carbon)/ms(DerbyMessageStore)] TXN-1001 : Created : org.apache.qpid.server.store.DerbyMessageStore
-[2011-02-07 16:18:29,415] INFO {qpid.message.transactionlog.recovery_complete} - [Broker] [vh(/carbon)/ms(DerbyMessageStore)] TXN-1006 : Recovery Complete
-[2011-02-07 16:18:29,416] INFO {org.apache.qpid.server.security.auth.manager.PrincipalDatabaseAuthenticationManager} - Initialising 'carbon' PrincipalDatabase authentication manager.
-[Broker] BRK-1002 : Starting : Listening on TCP port 5672
-[2011-02-07 16:18:29,484] INFO {qpid.message.broker.listening} - [Broker] BRK-1002 : Starting : Listening on TCP port 5672
-[Broker] BRK-1004 : Qpid Broker Ready
-[2011-02-07 16:18:29,485] INFO {qpid.message.broker.ready} - [Broker] BRK-1004 : Qpid Broker Ready
-[2011-02-07 16:18:29,685] INFO {org.wso2.carbon.messagebox.internal.ds.MessageBoxServiceComponent} - MessageBoxService bundle is activated successfully
-[2011-02-07 16:18:29,686] INFO {org.wso2.carbon.event.core.internal.builder.EventBrokerBuilderDS} - Successfully registered the event broker
-[2011-02-07 16:18:29,746] INFO {org.wso2.carbon.core.init.CarbonServerManager} - Starting Carbon initialization...
-[2011-02-07 16:18:29,997] INFO {org.wso2.carbon.core.init.CarbonServerManager} - Creating super-tenant Axis2 ConfigurationContext
-[2011-02-07 16:18:30,444] INFO {org.apache.axis2.deployment.ClusterBuilder} - Clustering has been disabled
-[2011-02-07 16:18:30,780] INFO {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2 module: rahas-1.60-wso2v1 {super-tenant}
-[2011-02-07 16:18:30,950] INFO {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2 module: wso2xfer-3.20-SNAPSHOT {super-tenant}
-[2011-02-07 16:18:31,121] INFO {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2 module: rampart-1.60-wso2v1 {super-tenant}
-[2011-02-07 16:18:31,388] INFO {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2 module: addressing-3.20-SNAPSHOT {super-tenant}
-[2011-02-07 16:18:31,421] INFO {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2 module: wso2mex-3.20-SNAPSHOT {super-tenant}
-[2011-02-07 16:18:31,534] INFO {org.apache.axis2.transport.tcp.TCPTransportSender} - TCP Sender started
-[2011-02-07 16:18:31,974] INFO {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2 service: version {super-tenant}
-[2011-02-07 16:18:32,280] INFO {org.apache.axis2.deployment.DeploymentEngine} - Deploying Web service: Version.aar - file:/home/shammi/wso2/checkouts/carbon-trunk/carbon/products/mb/modules/distribution/target/wso2mb-1.0.0/repository/deployment/server/axis2services/Version.aar
-[2011-02-07 16:18:32,364] INFO {org.wso2.carbon.core.init.CarbonServerManager} - Completed super-tenant Axis2 ConfigurationContext creation in 2.367 sec
-[2011-02-07 16:18:32,460] INFO {org.apache.axis2.deployment.ModuleDeployer} - Deploying module: addressing-SNAPSHOT - file:/home/shammi/wso2/checkouts/carbon-trunk/carbon/products/mb/modules/distribution/target/wso2mb-1.0.0/repository/deployment/client/modules/addressing-SNAPSHOT.mar
-[2011-02-07 16:18:32,464] INFO {org.apache.axis2.transport.tcp.TCPTransportSender} - TCP Sender started
-[2011-02-07 16:18:33,070] INFO {org.wso2.carbon.core.deployment.DeploymentInterceptor} - Deploying Axis2 service: TopicManagerAdminService {super-tenant}
-[2011-02-07 16:18:33,550] INFO {org.apache.axis2.deployment.DeploymentEngine} - Deploying Web service: org.wso2.carbon.event.admin -
-[2011-02-07 16:18:34,926] INFO {org.apache.axis2.deployment.DeploymentEngine} - Deploying Web service: org.wso2.carbon.tryit -
-[2011-02-07 16:18:35,724] INFO {org.wso2.carbon.core.init.CarbonServerManager} - Repository : /home/shammi/wso2/checkouts/carbon-trunk/carbon/products/mb/modules/distribution/target/wso2mb-1.0.0/repository/deployment/server/
-[2011-02-07 16:18:35,884] INFO {org.wso2.carbon.core.internal.permission.update.PermissionUpdater} - Permission cache updated for tenant 0
-[2011-02-07 16:18:35,884] INFO {org.wso2.carbon.core.init.CarbonServerManager} - ConfigurationContextService registered in 160ms
-[2011-02-07 16:18:35,902] WARN {org.apache.axis2.engine.ListenerManager} - ConfigurationContext provided for the ListenerManager initialization is null. ListenerManager will not be initialized
-[2011-02-07 16:18:35,902] INFO {org.wso2.carbon.core.transports.http.HttpsTransportListener} - HTTPS port : 9443
-[2011-02-07 16:18:35,902] INFO {org.wso2.carbon.core.transports.http.HttpTransportListener} - HTTP port : 9763
-[2011-02-07 16:18:37,207] INFO {org.wso2.carbon.ui.internal.CarbonUIServiceComponent} - Mgt Console URL : https://10.100.0.164:9443/carbon/
-[2011-02-07 16:18:37,242] INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Started Transport Listener Manager
-[2011-02-07 16:18:37,242] INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - Server : WSO2 MB -1.0.0
-[2011-02-07 16:18:37,242] INFO {org.wso2.carbon.core.internal.StartupFinalizerServiceComponent} - WSO2 Carbon started in 21 sec
-
-
-
-</pre>
-
-<p>To verify that the MB is up and running fire off your Web browser and go to
-https://localhost:9443/carbon. This will take you to the WSO2 MB on-line
-management console. </p>
-<img src="images/Login.png" alt="Log-in" />
-
-<p>You can login to the console using the default user credentials given below.
-</p>
-<ul>
- <li>Username: admin</li>
- <li>Password: admin</li>
-</ul>
-
-<p>If you can get that far then the MB is properly installed and running. </p>
-
-<p>WSO2 MB startup scripts stated above accept a few useful arguments. </p>
-
-<p>--cleanRegistry<br />
- This argument forces the embedded Registry instance to be cleaned before
-starting the MB. Note that this will clean the internal database therefore any
-configurations you saved previously will be permanently lost. </p>
-
-<p>--restart<br />
- Restart the Carbon Unix daemon.</p>
-
-<p>-debug <port><br />
- Enables remote debugging on the MB through the specified port. </p>
-
-<p>-dump<br />
- Print a thread dump of the Carbon Unix daemon.</p>
-
-
-<p>In addition to the above mentioned arguments the MB startup scripts accept
-the following VM arguments. </p>
-
-<p>-DosgiConsole<br />
- Starts the OSGi console from which you can directly interact with the
-underlying OSGi runtime. </p>
-
-
-<h4>4.0 WSO2 MB Directory Hierarchy </h4>
-
-<p>When you extract a WSO2 MB binary distribution archive you will find the
-following directories in the top level that is created. </p>
-
-<p>bin -<br />
-Contains all the necessary scripts to interact with the WSO2 MB instance.
-There are shell scripts (with .sh extension) for Unix/Linux users and batch
-files (with .bat extension) for Windows users. In general you will find the
-following scripts in this directory.<br />
-<br />
-<ul>
- <li>wso2server.sh/wso2server.bat - Launches WSO2 MB </li>
- <li>wsdl2java.sh/wsdl2java.bat - Launches the Java stub generation tool for
- Web Services </li>
- <li>java2wsdl.sh/java2wsdl.bat - Launches the WSDL generation tool for Java
- Web Services </li>
- <li>tcpmon.sh/tcpmon.bat - Launches TCPMon, the TCP connection monitor </li>
- <li>chpasswd.sh/chpasswd.bat -Use this script to change the administrator
- password without signing in to the server<br />
- </li>
- <li>daemon.sh -Start WSO2 MB as a daemon on Unix/Linux systems<br />
- </li>
- <li>install.bat - Install WSO2 MB as a background service on Windows<br />
- </li>
- <li>repowriter.sh/repowriter.bat </li>
-</ul>
-<br />
-In addition to the above mentioned scripts you will find a sub-directory named
-'native' in the bin directory.<br />
-</p>
-
-<p>repository/deployment -<br />
-This directory houses all the OSGi bundles, service artifacts, modules and
-related resources used by the WSO2 MB instance. The repository/components/plugins
-directory will contain all the necessary OSGi bundles at server runtime.</p>
-
-<p>repository/conf -<br />
-All the global configuration files (eg: axis2.xml, transports-mgt.xml,
-carbon.xml ) used by the MB are stored in this directory.
-</p>
-
-<p>lib -<br />
-The lib directory houses all the jar files and OSGi bundles required by the
-embedded Tomcat instance. Starting from Carbon 2.0 the log4j.properties file
-used by the MB is also stored here. </p>
-
-<p>resources -<br />
-Contains additional resources required by WSO2 MB. This includes security
-related resources such as keystores. </p>
-
-<p>repository/logs -<br />
-All the server logs created during server runtime will be stored here. </p>
-
-<p>dbscripts -<br />
-Contains a collection of database scripts required to create the Carbon
-database on a variety of database management systems.<br />
-</p>
-
-<h4>5.0 Using the WSO2 MB Management Console </h4>
-
-<p>WSO2 MB management console is a Web based control panel powered by JSP and
-AJAX which enables system administrators to interact with a running MB
-instance, without having to touch any underlying configuration files. The
-management console allows the users to command and control proxy services,
-sequences, transports, local entries, registry, modules, endpoints and much
-more. MB management console is a great way to try things out without having to
-edit the actual configuration files or without having to restart the MB for
-changes to take effect. </p>
-
-<p>We recommend using Mozilla Firefox 3 or Internet Explorer 7 to access the
-WSO2 MB management console. Please note that your browser must be JavaScript
-enabled to take the full advantage of the management console. To access the MB
-management console fire off you Web browser and navigate to https://<Server
-Host>:<Server Port>/<Context>. If you are running the Web
-browser on the same machine as the MB you may use 'localhost' as the server
-host. The default port and the context for the MB management console are
-'9443' and 'carbon' respectively. If you entered the URL correctly you will be
-taken to the management console's login page. </p>
-
-<p>On the login page enter 'admin' as the username and the password to login to
-the system. You can change user credentials and even add new users once you
-login. Controls and wizards in the MB management console are pretty much self
-explanatory. However if you are having trouble finishing your way in the
-management console, click on the 'Help' link at the top right corner of any
-page to access context sensitive help. </p>
-
-<p>Please note that the MB management console makes use of the default HTTPS
-servlet transport which is configured in the MB_HOME/conf/transports.xml file.
-It is important that this transport is always properly configured in the
-mentioned file. Otherwise the management console might be inaccessible to the
-users. </p>
-
-<h4>6.0 User Management </h4>
-
-<p>To access the WSO2 MB user management features, first sign in to the MB
-management console and click on 'User Management' under the 'Configure' menu in
-the left navigation bar. This will take you to the User Management home page
-which contains the controls illustrated below. </p>
-<img src="images/user-mgt.PNG" alt="User Mgt" />
-
-<p>From here you can manage users and roles. A user is associated with zero or
-more roles (generally specified at user creation time) and each role is
-associated with zero or more permissions (generally specified at role creation
-time). Therefore the set of permissions owned by a user is determined by the
-roles assigned to that user. A user owns the union of all the permissions
-associated with the roles assigned to that user. By default MB comes with only
-one role, the 'admin' role. This role is associated with the following set of
-permissions.</p>
-
-<p>By default the admin user is associated with the admin role and hence the
-admin user is entitled to all the permissions. </p>
-
-<p>To add a new role to the system click on 'Roles' in the User Management home
-page and on the page that appears click the 'Add New Role' link. This will
-start the 'Add Role' wizard. The wizard will guide you though the process of
-creating a role by specifying a unique name for the role and adding the
-relevant permissions to the new role. Similarly to create a new user, click on
-'Users' in the User Management home page. Then from the next page that appears
-select 'Create New User' link. This will launch the 'Add User' wizard which
-will enable you to create a new user account with login credentials and
-associate the account with one or more existing roles. The MB management
-console also enables you to search for and modify existing users and roles. </p>
-
-<p>WSO2 MB can be easily configured to use an external user store in addition
-to the built-in system user store. An external user store is an external
-database which stores user data. It could be as simple as a relational database
-or as sophisticated as an LDAP instance. Most organizations maintain such
-centralized databases and it would be productive from the organization's point
-of view to have the MB pick up user data from the existing centralized user
-database. To connect the MB to an external user store simply click on the 'Add
-External User Store' link on the User Management home page. Then on the page
-that appears select the type of user store that will be plugged into the MB.
-Currently the following types of user stores are supported. </p>
-<ul>
- <li>JDBC </li>
- <li>LDAP </li>
- <li>Active Directory </li>
-</ul>
-
-<p>Having selected the type of the user store you need to provide additional
-information required by the MB to connect to and retrieve user data from the
-external user store. If all the required parameters were specified accurately
-the MB will pick up user data from the external user store and users
-registered on the external store will be able to access the MB as if their
-accounts were created in the built-in system user store. </p>
-
-<h4>7.0 Setting Up Logging </h4>
-
-<p>Logging is one of the most important aspects of a production grade server. A
-properly configured logging system is vital in identifying errors, security
-threats and usage patterns. WSO2 MB uses a log4j based logging mechanism
-through Apache Commons Logging facade library. The log4j.properties file which
-governs how logging is performed by the server can be found in MB_HOME/lib
-directory. However it is recommended not to make any alterations to the default
-log4j.properties file. The recommended way of setting up logging is by using
-the MB management console. Simply login to the management console and click on
-'Logging' under the 'Configure' menu in the left navigation bar. From here you
-can setup various appenders and configure log levels for various loggers. Any
-changes to the logging configuration you make from the management console will
-get priority over what is defined in the actual log4j.properties file. </p>
-
-<p>By default WSO2 MB comes with the following log appenders configured. </p>
-<ul>
- <li>CARBON_CONSOLE (Logs to the console when the server is running) </li>
- <li>CARBON_LOGFILE (Writes the logs to MB_HOME/logs/wso2-MB.log) </li>
- <li>CARBON_MEMORY </li>
- <li>CARBON_SYS_LOG </li>
- <li>SERVICE_APPENDER (Writes mediation time audit messages to
- MB_HOME/logs/wso2-MB-service.log) </li>
- <li>TRACE_APPENDER (Writes mediation time tracing/debug messages to the
- MB_HOME/logs/wso2-MB-trace.log for tracing enabled services) </li>
- <li>TRACE_MEMORYAPPENDER </li>
-</ul>
-
-<p>Tracing can be enabled for individual mediation sequences and proxy services
-from the 'Mediation Sequences' home page and the 'Service Dashboard' page
-respectively. Click on the 'Sequences' link under 'Mediation' in the 'Manage'
-menu of the left navigation bar to access the 'Mediation Sequences' page. This
-page lists all the deployed sequences. Each sequence gives you the options to
-enable/disable tracing. To access the service dashboard for a proxy service go
-to the Services List page and click on the proxy service that you are
-interested in. Once a sequence or a proxy service is tracing enabled you can
-view the generated log messages by visiting the 'Mediation Tracer' page under
-the 'Monitor' menu. The 'Monitor' menu also gives you access to the system logs
-and the SOAP tracer logs all through the Web interface itself. </p>
-<img src="images/logs.PNG" alt="Logs" />
- </body>
-</html>
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/docs/xdoc/cluster_scenario_03.xml
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/cluster_scenario_03.xml b/products/stratos2/cloud_controller/1.0.0/docs/xdoc/cluster_scenario_03.xml
deleted file mode 100644
index 2a8c48c..0000000
--- a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/cluster_scenario_03.xml
+++ /dev/null
@@ -1,199 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- ~ Copyright (c) 2009, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
- ~
- ~ WSO2 Inc. licenses this file to you under the Apache License,
- ~ Version 2.0 (the "License"); you may not use this file except
- ~ in compliance with the License.
- ~ You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- ~ KIND, either express or implied. See the License for the
- ~ specific language governing permissions and limitations
- ~ under the License.
- -->
-
-<!DOCTYPE html
- 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>
- WSO2 MB Clustered Deployment - Scenario 03
- </title>
- <link href="css/mb-docs.css" rel="stylesheet"/>
- <link href="styles/dist-docs.css" rel="stylesheet" type="text/css" media="all"/>
- </head>
- <body xml:lang="en">
- [ <a href="docs_index.html"> Documentation Index </a> ]
-
- <h2>Starting external cassandra server and use inbuilt zoo keeper server in ring model with broker nodes</h2>
- <p>
- In this model you need to get downloaded following apache products
- </p>
-
- <ul>
- <li><a href="http://cassandra.apache.org/download/">Apache Cassandra</a><p> Version 1.0.*</p></li>
- </ul>
- <p> Deployment model will be like bellow </p>
- <p>
- <img src="images/cluster_scenario_03.png" alt="Cluster Setup Scenario 03" height="600" width ="950"/>
- </p>
- <p> In this model we have a common cassandra server. Since we are shipping a zoo keeper server with Message broker product we can
- use that and create a zoo keeper ring in the cluster.</p>
- <ul>
- <li>Cassandra Server - 192.168.0.100</li>
- </ul>
- <p> We have three Message Broker servers in three different hosts as</p>
- <ul>
- <li>MB Server 01 - 192.168.0.101</li>
- <li>MB Server 02 - 192.168.0.102</li>
- <li>MB Server 03 - 192.168.0.103</li>
- </ul>
-
- <p>First we need to configure the HostName in carbon.xml file which is located in "wso2mb-2.0.1/repository/conf/" directory.
- Specify the ip of the host as follows. <font color="red">You need to configure this for all the three servers.</font></p>
- <pre>
- <!--
- Host name or IP address of the machine hosting this server
- e.g. www.wso2.org, 192.168.1.10
- This is will become part of the End Point Reference of the
- services deployed on this server instance.
- -->
- <HostName>192.168.0.101</HostName>
-
- </pre>
-
-
- <p> Then we need to configure cassandra server to listen to all the broker nodes.For that we need to change the following entries
- in the "Cassandra.yaml" file which is located in the "apache-cassandra-1.0.1/conf/" directory.</p>
-
- <ul>
- <li>Change the data storage directories of cassandra. Here by default it will point to the location "/var/lib/". But
- it will be better, if you can keep the data locally inside the folder where you have the server setup. So change it to "./repository/database" off
- all three entries as</li>
- <pre>
- # directories where Cassandra should store data on disk.
- data_file_directories:
- - ./repository/database/cassandra/data
-
- # commit log
- commitlog_directory: ./repository/database/cassandra/commitlog
-
- # saved caches
- saved_caches_directory: ./repository/database/cassandra/saved_caches
-
- </pre>
-
- <li>Change listen address of the server. By default it is "localhost", change it to the ip address of the host where you
- have the cassandra server.
- </li>
- <pre>
- listen_address: 192.168.0.100
- </pre>
-
- <li>Change RPC address of the server.By default it is "localhost", change it to the ip address of the host where you
- have the cassandra server. </li>
- <pre>
- rpc_address: 192.168.0.100
- </pre>
- </ul>
- <p> Now save the cassandra.yaml file and you can start the cassandra server by executing the script "cassandra" with the
- option -f. Eg: "./cassandra -f"
- </p>
-
- <p>
- <b>Configuring Zookeeper Cluster</b>
- </p>
- <p> Then we need to configure the Zoo Keeper Servers to create a ring within among all broker nodes. We can do it by
- adding client port address to the "zoo.cfg" which is located at "wso2mb-2.0.1/repository/conf/etc " . </p>
-
- <p>After modifying the file , it will look like bellow. </p>
- <pre>
- tickTime=2000
- dataDir=repository/data/zookeeper
- clientPort=2181
- <b>start_zk_server=true</b>
- <b>clientPortAddress=192.168.0.101</b>
- <b>server.1=192.168.0.100:2888:3888</b>
- <b>server.2=192.168.0.101:2888:3888</b>
- <b>server.3=192.168.0.102:2888:3888</b>
- </pre>
-
- <p> Above zoo.cfg file is for the server 192.168.0.101. You can copy the same zoo.cfg file to other two servers
- and change the entry "clientPortAddress" to the ip of that particular server.</p>
-
- <p> Then you need to create file "myid" in the data directory (repository/data/zookeeper) of each server. In that file
- you need to specify the id of the server.</p>
-
- <p>
- eg: Id of the the server 192.168.0.100 will be "1". You need only to have the number 1 in that myid file.
- </p>
-
- <p>You can find more information on this in <a href="http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html#sc_zkMulitServerSetup">zookeeper clustering setup guide</a></p>
-
- <p>
- <b>You need to do above configuration in each of the message broker servers appropriately.</b>
- </p>
-
- <p>
- Then you need to do the following configuration changes in each Message broker nodes
- </p>
- <p>
- Modify qpid-config.xml file which is located at : /repository/conf/advanced directory as bellow
- </p>
- <ul>
-
- <li>Enable clustering</li>
- <li>Change the server ip of the Zookeeper by adding all zoo keeper server details</li>
- </ul>
- <pre>
- <clustering>
-
- <enabled><b>true</b></enabled>
- <OnceInOrderSupportEnabled>false</OnceInOrderSupportEnabled>
- <externalCassandraServerRequired>true</externalCassandraServerRequired>
-
- <coordination>
- <!-- Apache Zookeeper Address -->
- <ZooKeeperConnection><b>192.168.0.101:2181,192.168.0.102:2181,192.168.0.103:2181</b></ZooKeeperConnection>
- <!-- Format yyyy-MM-dd HH:mm:ss -->
- <ReferenceTime>2012-02-29 08:08:08</ReferenceTime>
- </coordination>
- </pre>
-
- <p>Modify qpid-virtualhosts.xml file which is located at :/repository/conf/advanced directory as bellow</p>
- <ul>
- <li>Change the connection string by pointing to the cassandra server</li>
- </ul>
- <pre>
- <store>
- <class>org.wso2.andes.server.store.CassandraMessageStore</class>
- <username>admin</username>
- <password>admin</password>
- <cluster>ClusterOne</cluster>
- <idGenerator>org.wso2.andes.server.cluster.coordination.TimeStampBasedMessageIdGenerator</idGenerator>
- <connectionString><b>192.168.0.100</b>:9160</connectionString>
- </store>
- </pre>
-
- <p>Now you can start all three Message Broker nodes.</p>
-
- <h2>
-
- Other Resources
- </h2>
- <p/>
- <p>
- <a href="http://wso2.org/library/mb">The WSO2 Oxygen Tank
- Library</a> : The Library contains articles, tutorials,
- presentations, and other knowledge base items published on The Oxygen
- Tank on different styles of deployments.
- </p>
- </body>
-</html>
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/docs/xdoc/cluster_scenario_04.xml
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/cluster_scenario_04.xml b/products/stratos2/cloud_controller/1.0.0/docs/xdoc/cluster_scenario_04.xml
deleted file mode 100644
index 36b2595..0000000
--- a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/cluster_scenario_04.xml
+++ /dev/null
@@ -1,168 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- ~ Copyright (c) 2009, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
- ~
- ~ WSO2 Inc. licenses this file to you under the Apache License,
- ~ Version 2.0 (the "License"); you may not use this file except
- ~ in compliance with the License.
- ~ You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- ~ KIND, either express or implied. See the License for the
- ~ specific language governing permissions and limitations
- ~ under the License.
- -->
-
-<!DOCTYPE html
- 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>
- WSO2 MB Clustered Deployment - Scenario 04
- </title>
- <link href="css/mb-docs.css" rel="stylesheet"/>
- <link href="styles/dist-docs.css" rel="stylesheet" type="text/css" media="all"/>
- </head>
- <body xml:lang="en">
- [ <a href="docs_index.html"> Documentation Index </a> ]
-
- <h2>Use inbuilt cassandra server and zoo keeper server for all the broker nodes</h2>
-
- <p> The deployment model of this scenario will be like bellow </p>
- <p>
- <img src="images/cluster_scenario_04.png" alt="Cluster Setup Scenario 04" height="600" width ="950"/>
- </p>
- <p> In this model we have two rings, Cassandra ring and ZooKeeper ring. Since we are shipping a cassandra server and zoo keeper server
- with Message broker product we can use them and create a cassandra ring and a zoo keeper ring in the cluster.</p>
-
- <p> We have three Message Broker servers in three different hosts as and all of them are having a cassandra server in it</p>
- <ul>
- <li>MB Server 01 - 192.168.0.100</li>
- <li>MB Server 02 - 192.168.0.101</li>
- <li>MB Server 03 - 192.168.0.102</li>
- </ul>
-
- <p>First we need to configure the HostName in carbon.xml file which is located in "wso2mb-2.0.1/repository/conf/" directory.
- Specify the ip of the host as follows. <font color="red">You need to configure this for all the three servers.</font></p>
- <pre>
- <!--
- Host name or IP address of the machine hosting this server
- e.g. www.wso2.org, 192.168.1.10
- This is will become part of the End Point Reference of the
- services deployed on this server instance.
- -->
- <HostName>192.168.0.100</HostName>
-
- </pre>
-
- <p> Then We need to configure cassandra servers in these MB servers to form a cassandra ring. For that we need to change the following
- entries in the "Cassandra.yaml" file which is located in the "wso2mb-2.0.1/repository/conf/etc" directory.</p>
-
- <ul>
- <li>Change the seeds in the ring. You can get a better idea on setting a cassandra from following <a href="http://www.datastax.com/docs/1.0/install/cluster_init">web page.</a>
- Here we are configuring two seed nodes. (MB Server 01 and 02)</li>
-
- <pre>
- # seeds is actually a comma-delimited list of addresses.
- # Ex: "<ip1>,<ip2>,<ip3>"
- - seeds: "192.168.0.101,192.168.0.102"
-
- </pre>
-
- <li>Change listen address of the server. By default it is "localhost", change it to the ip address of the host where you
- have the cassandra server. <b>You need to change the listen address of the each server to it's ip address. Here
- for the server 192.168.0.102, it will like bellow. </b>
- </li>
- <pre>
- listen_address: 192.168.0.102
- </pre>
-
- <li>Change RPC address of the server.By default it is "localhost", change it to the ip address of the host where you
- have the cassandra server. <b>You need to change the RPC address of the each server to it's ip address. Here
- for the server 192.168.0.103, it will like bellow. </b></li>
- <pre>
- rpc_address: 192.168.0.103
- </pre>
- </ul>
-
- <p>
- <b>Configuring Zookeeper Cluster</b>
- </p>
- <p> Then we need to configure the Zoo Keeper Servers to create a ring within among all broker nodes. We can do it by
- adding client port address to the "zoo.cfg" which is located at "wso2mb-2.0.1/repository/conf/etc " . </p>
-
- <p>After modifying the file , it will look like bellow. </p>
- <pre>
- tickTime=2000
- dataDir=repository/data/zookeeper
- clientPort=2181
- <b>start_zk_server=true</b>
- <b>clientPortAddress=192.168.0.101</b>
- <b>server.1=192.168.0.100:2888:3888</b>
- <b>server.2=192.168.0.101:2888:3888</b>
- <b>server.3=192.168.0.102:2888:3888</b>
- </pre>
-
- <p> Above zoo.cfg file is for the server 192.168.0.101. You can copy the same zoo.cfg file to other two servers
- and change the entry "clientPortAddress" to the ip of that particular server.</p>
-
- <p> Then you need to create file "myid" in the data directory (repository/data/zookeeper) of each server. In that file
- you need to specify the id of the server.</p>
-
- <p>
- eg: Id of the the server 192.168.0.100 will be "1". You need only to have the number 1 in that myid file.
- </p>
-
- <p>You can find more information on this in <a href="http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html#sc_zkMulitServerSetup">zookeeper clustering setup guide</a></p>
-
- <p>
- <b>You need to do above configuration in each of the message broker servers appropriately.</b>
- </p>
-
- <p>
- Then you need to do the following configuration changes in each Message broker nodes
- </p>
- <p>
- Modify qpid-config.xml file which is located at : /repository/conf/advanced directory as bellow
- </p>
- <ul>
-
- <li>Enable clustering</li>
- <li>Change the server of the Zookeeper</li>
- </ul>
- <pre>
- <clustering>
-
- <enabled><b>true</b></enabled>
- <OnceInOrderSupportEnabled>false</OnceInOrderSupportEnabled>
- <externalCassandraServerRequired>false</externalCassandraServerRequired>
-
- <coordination>
- <!-- Apache Zookeeper Address -->
- <ZooKeeperConnection><b>192.168.0.100:2181,192.168.0.101:2181,192.168.0.102:2181</b></ZooKeeperConnection>
- <!-- Format yyyy-MM-dd HH:mm:ss -->
- <ReferenceTime>2012-02-29 08:08:08</ReferenceTime>
- </coordination>
- </pre>
-
- <p>Now you can start all three Message Broker nodes.</p>
-
- <h2>
-
- Other Resources
- </h2>
- <p/>
- <p>
- <a href="http://wso2.org/library/mb">The WSO2 Oxygen Tank
- Library</a> : The Library contains articles, tutorials,
- presentations, and other knowledge base items published on The Oxygen
- Tank on different styles of deployments.
- </p>
- </body>
-</html>
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/docs/xdoc/deployment_guide.xml
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/deployment_guide.xml b/products/stratos2/cloud_controller/1.0.0/docs/xdoc/deployment_guide.xml
deleted file mode 100644
index f9cf0e5..0000000
--- a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/deployment_guide.xml
+++ /dev/null
@@ -1,90 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- ~ Copyright (c) 2009, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
- ~
- ~ WSO2 Inc. licenses this file to you under the Apache License,
- ~ Version 2.0 (the "License"); you may not use this file except
- ~ in compliance with the License.
- ~ You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- ~ KIND, either express or implied. See the License for the
- ~ specific language governing permissions and limitations
- ~ under the License.
- -->
-
-<!DOCTYPE html
- 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>
- WSO2 MB - Deployment Guide
- </title>
- <link href="css/mb-docs.css" rel="stylesheet"/>
- <link href="styles/dist-docs.css" rel="stylesheet" type="text/css" media="all"/>
- </head>
- <body xml:lang="en">
- [ <a href="docs_index.html"> Documentation Index </a> ]
- <h1>
- WSO2 Message Broker Server (MB) Deployment Guide
- </h1>
- <p>Deploying the WSO2 MB correctly on your infrastructure is a vital task for the success
- of the usage of the MB. You should first analyze the requirement and then select the
- best matching deployment mode. There are different set of possible deployment modes with
- different configurations.
- </p>
- <h2>
- Available Deployment options
- </h2>
- <p>
- <a href="installation_guide.html">Standalone Deployment Guide</a> :
- Describes the default standalone installation and deployment of the MB
- </p>
- <p>
- <a>Clustered Deployment Guide</a> :
- Contains the information on deploying the Message Broker in a clustered environment, this particular guide
- explains the available options on a clustered deployment.
- </p>
- <h2>Clustered Deployment Guide </h2>
- <p> In clustered deployment of WSO2 message broker, there are several scenarios which can be implemented. Basically
- in WSO2 message broker, there are three components.
- </p>
- <ul>
- <li>Broker</li>
- <li>Cassandra Server</li>
- <li>Zoo Keeper Server</li>
- </ul>
- <p>By default, WSO2 mb is packed with all these three component. In a clustered setup, it is possible to have these
- three components separately and shared with each other.
- </p>
- <p>Here we are describing some of the possible deployment scenarios and it can be customized according to your
- requirement.</p>
-
- <h3> Deployment models</h3>
- <ul>
- <li><a href="cluster_scenario_01.html">Starting external cassandra server and zoo keeper server and point all broker nodes to them</a> </li>
- <li><a href="cluster_scenario_02.html">Starting external zoo keeper server and use the inbuilt cassandra server in ring model with broker nodes</a></li>
- <li><a href="cluster_scenario_03.html">Starting external cassandra server and use inbuilt zoo keeper server in ring model with broker nodes</a></li>
- <li><a href="cluster_scenario_04.html">Use inbuilt cassandra server and zoo keeper server for all the broker nodes</a></li>
- <li><a href="cluster_scenario_05.html">Use inbuilt cassandra server and zoo keeper server in a customized manner</a></li>
- </ul>
-
- <h2>
-
- Other Resources
- </h2>
- <p/>
- <p>
- <a href="http://wso2.org/library/mb">The WSO2 Oxygen Tank
- Library</a> : The Library contains articles, tutorials,
- presentations, and other knowledge base items published on The Oxygen
- Tank on different styles of deployments.
- </p>
- </body>
-</html>
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/docs/xdoc/docs_index.xml
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/docs_index.xml b/products/stratos2/cloud_controller/1.0.0/docs/xdoc/docs_index.xml
deleted file mode 100644
index 7b72a82..0000000
--- a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/docs_index.xml
+++ /dev/null
@@ -1,76 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- ~ Copyright (c) 2009, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
- ~
- ~ WSO2 Inc. licenses this file to you under the Apache License,
- ~ Version 2.0 (the "License"); you may not use this file except
- ~ in compliance with the License.
- ~ You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- ~ KIND, either express or implied. See the License for the
- ~ specific language governing permissions and limitations
- ~ under the License.
- -->
-
-<!DOCTYPE html
- 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>
- WSO2 MB - Documentation Index
- </title>
- <link href="css/mb-docs.css" rel="stylesheet"/>
- <link href="styles/dist-docs.css" rel="stylesheet" type="text/css" media="all"/>
- </head>
- <body xml:lang="en">
- <h1>
- WSO2 Message Broker Server (MB) Documentation Index
- </h1>
- <h2>
- Getting Started
- </h2>
- <p>
- <a href="installation_guide.html">Installation Guide</a>
- : Gives
- basic steps on how to download, install, and run WSO2 MB using the binary
- distribution, and how to build WSO2 MB using the source distribution.
- </p>
- <p>
- <a href="user_guide.html">User Guide</a>
- : A
- manual on how to run and configure the WSO2 MB through the management
- console. The user guide is centered on describing key features such as pub/sub of WSO2
- MB product.
- </p>
-
- <h2>
- Samples
- </h2>
- <p>
- <a href="samples_index.html">How to Run the WSO2 MB Samples</a>
- :
- This document provides you with a set of MB samples demonstrating various capabilities
- of the MB.
- </p>
- <p>
- <a href="http://wso2.org/library/mb">The WSO2 Oxygen Tank
- Library
- </a>
- : The Library contains articles, tutorials,
- presentations, and other knowledge base items published on The Oxygen
- Tank.
- </p>
- <p>
- <a href="http://wso2.org/wiki/display/mb">Wiki Space</a>
- :
- This is the working Wiki for WSO2 MB.
- </p>
- </body>
-</html>
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/docs/xdoc/faq.xml
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/faq.xml b/products/stratos2/cloud_controller/1.0.0/docs/xdoc/faq.xml
deleted file mode 100644
index 0a2325b..0000000
--- a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/faq.xml
+++ /dev/null
@@ -1,79 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- ~ Copyright (c) 2009, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
- ~
- ~ WSO2 Inc. licenses this file to you under the Apache License,
- ~ Version 2.0 (the "License"); you may not use this file except
- ~ in compliance with the License.
- ~ You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- ~ KIND, either express or implied. See the License for the
- ~ specific language governing permissions and limitations
- ~ under the License.
- -->
-
-<!DOCTYPE html
- 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>
- WSO2 MB - Frequently Asked Questions
- </title>
- <link href="css/mb-docs.css" rel="stylesheet"/>
- <link href="styles/dist-docs.css" rel="stylesheet" type="text/css" media="all"/>
- </head>
- <body xml:lang="en">
- [
- <a href="docs_index.html">Documentation Index</a>
- ]
- <h1>WSO2 Business Server (MB) Frequently Asked Questions</h1>
- <h2>Contents</h2>
- <div class="toc">
- <ol>
- <li>
- <a href="#what-features">What are main features of WSO2 MB</a>
- </li>
- <li>
- <a href="#how-to-monitor">How to monitor queues and topics using MB?</a>
- </li>
- <li>
- <a href="#what-sqs">What is MessageBox(SQS)?
- </a>
- </li>
- </ol>
-
- <h3 id="what-features">
- 1. What are main features of WSO2 MB?
- </h3>
- <p>The Message Broker is compliant with the latest WS-Eventing specification. It's
- easy-to-use
- Amazon SQS API provides a standard interface for your message queuing requirements.
- </p>
- <p>The underlying JMS engine handles WS-Eventing/JMS synchronisation that enables
- exposing and
- consuming your events using two different standard API's.
- </p>
- <h3 id="how-to-monitor">
- 2. How to monitor queues and topics using MB?
- </h3>
- <p>All the topics, subscriptions and queue details can be monitored using MB Management
- Console
- </p>
- <h3 id="what-sqs">
- 3. What is MessageBox(SQS)?
- </h3>
- <p>Simple Queue Service(SQS) is a web service interface to do queue related operations.
- Message box provides this service. Please find more details on how to use SQS in
- <a href="samples_index.html">WSO2 MB Samples</a>.
- </p>
-
- </div>
- </body>
-</html>
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/docs/xdoc/samples/jms_topic_sample.xml
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/samples/jms_topic_sample.xml b/products/stratos2/cloud_controller/1.0.0/docs/xdoc/samples/jms_topic_sample.xml
deleted file mode 100644
index d58dba4..0000000
--- a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/samples/jms_topic_sample.xml
+++ /dev/null
@@ -1,252 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!--
-~ Copyright (c) 2009, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
-~
-~ WSO2 Inc. licenses this file to you under the Apache License,
-~ Version 2.0 (the "License"); you may not use this file except
-~ in compliance with the License.
-~ You may obtain a copy of the License at
-~
-~ http://www.apache.org/licenses/LICENSE-2.0
-~
-~ Unless required by applicable law or agreed to in writing,
-~ software distributed under the License is distributed on an
-~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-~ KIND, either express or implied. See the License for the
-~ specific language governing permissions and limitations
-~ under the License.
--->
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//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>WSO2 MB Samples - JMS Topic Sample</title>
- <link href="../css/mb-docs.css" rel="stylesheet"/>
- <link href="../styles/dist-docs.css" rel="stylesheet" type="text/css"
- media="all"/>
- </head>
-
- <body>
- <p>[<a href="../docs_index.html">Documentation Index</a>] </p>
- <h1>WSO2 MB - Samples :JMS Topic Sample</h1>
-
- <p>This guide demonstrates how topics can be created and used in Message
- Broker using JMS API.
- </p>
-
- <h2>Contents</h2>
-
- <div class="toc">
- <ul>
- <li>
- <a href="#jms_queue_sample">JMS Topic Sample</a>
- </li>
- </ul>
- </div>
-
- <h2 id="jms_queue_sample">JMS Topic Sample</h2>
-
- <p>Following code is used to create a topic, subscribe to it and publish messages. To
- run this code sample, you need to have dependencies located at
- $CARBON_HOME/client-lib in class path.
- To try out following code fragment, Run the Topic Subscriber first and then run
- Topic Publisher code. You should see, published message in Topic subscriber console.
-
- You can see created topics in management console as well.
- </p>
-
- <p>Topic Publisher: This code is used to publish messages to a given topic.</p>
-
- <pre xml:space="preserve">
- package com.org.wso2.mb.jms.sample;
- /**
- * Copyright (c) 2009, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
- import javax.jms.JMSException;
- import javax.jms.QueueSession;
- import javax.jms.TextMessage;
- import javax.jms.Topic;
- import javax.jms.TopicConnection;
- import javax.jms.TopicConnectionFactory;
- import javax.jms.TopicSession;
- import javax.naming.Context;
- import javax.naming.InitialContext;
- import javax.naming.NamingException;
- import java.util.Properties;
-
-
- public class TopicPublisher {
- public static final String QPID_ICF = "org.wso2.andes.jndi.PropertiesFileInitialContextFactory";
- private static final String CF_NAME_PREFIX = "connectionfactory.";
- private static final String CF_NAME = "qpidConnectionfactory";
- String userName = "admin";
- String password = "admin";
-
- private static String CARBON_CLIENT_ID = "carbon";
- private static String CARBON_VIRTUAL_HOST_NAME = "carbon";
- private static String CARBON_DEFAULT_HOSTNAME = "localhost";
- private static String CARBON_DEFAULT_PORT = "5672";
- String topicName = "MYTopic";
-
-
- public static void main(String[] args) throws NamingException, JMSException {
- TopicPublisher topicPublisher = new TopicPublisher();
- topicPublisher.publishMessage();
- }
-
- public void publishMessage() throws NamingException, JMSException {
- Properties properties = new Properties();
- properties.put(Context.INITIAL_CONTEXT_FACTORY, QPID_ICF);
- properties.put(CF_NAME_PREFIX + CF_NAME, getTCPConnectionURL(userName, password));
-
- System.out.println("getTCPConnectionURL(userName,password) = " + getTCPConnectionURL(userName, password));
-
- InitialContext ctx = new InitialContext(properties);
- // Lookup connection factory
- TopicConnectionFactory connFactory = (TopicConnectionFactory) ctx.lookup(CF_NAME);
- TopicConnection topicConnection = connFactory.createTopicConnection();
- topicConnection.start();
- TopicSession topicSession =
- topicConnection.createTopicSession(false, QueueSession.AUTO_ACKNOWLEDGE);
-
- // Send message
- Topic topic = topicSession.createTopic(topicName);
-
- // create the message to send
- TextMessage textMessage = topicSession.createTextMessage("Test Message");
-
- javax.jms.TopicPublisher topicPublisher = topicSession.createPublisher(topic);
- topicPublisher.publish(textMessage);
-
- topicSession.close();
- topicConnection.close();
- }
-
- public String getTCPConnectionURL(String username, String password) {
- // amqp://{username}:{password}@carbon/carbon?brokerlist='tcp://{hostname}:{port}'
- return new StringBuffer()
- .append("amqp://").append(username).append(":").append(password)
- .append("@").append(CARBON_CLIENT_ID)
- .append("/").append(CARBON_VIRTUAL_HOST_NAME)
- .append("?brokerlist='tcp://").append(CARBON_DEFAULT_HOSTNAME).append(":").append(CARBON_DEFAULT_PORT).append("'")
- .toString();
- }
-
- }
-
-
- </pre>
-
- <p>Topic Subscriber: This code is used to Subscribe for topics.
- topicSubscriber.receive() will wait till a message is received and exit the main
- thread.
- </p>
- <pre xml:space="preserve">
- package com.org.wso2.mb.jms.sample;
- /**
- * Copyright (c) 2009, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-
- import javax.jms.JMSException;
- import javax.jms.Message;
- import javax.jms.QueueSession;
- import javax.jms.TextMessage;
- import javax.jms.Topic;
- import javax.jms.TopicConnection;
- import javax.jms.TopicConnectionFactory;
- import javax.jms.TopicSession;
- import javax.naming.Context;
- import javax.naming.InitialContext;
- import javax.naming.NamingException;
- import java.util.Properties;
-
-
- public class TopicSubscriber {
- public static final String QPID_ICF = "org.wso2.andes.jndi.PropertiesFileInitialContextFactory";
- private static final String CF_NAME_PREFIX = "connectionfactory.";
- private static final String CF_NAME = "qpidConnectionfactory";
- String userName = "admin";
- String password = "admin";
-
- private static String CARBON_CLIENT_ID = "carbon";
- private static String CARBON_VIRTUAL_HOST_NAME = "carbon";
- private static String CARBON_DEFAULT_HOSTNAME = "localhost";
- private static String CARBON_DEFAULT_PORT = "5672";
- String topicName = "MYTopic";
-
-
- public static void main(String[] args) throws NamingException, JMSException {
- TopicSubscriber topicSubscriber = new TopicSubscriber();
- topicSubscriber.subscribe();
- }
-
- public void subscribe() throws NamingException, JMSException {
- Properties properties = new Properties();
- properties.put(Context.INITIAL_CONTEXT_FACTORY, QPID_ICF);
- properties.put(CF_NAME_PREFIX + CF_NAME, getTCPConnectionURL(userName, password));
-
- System.out.println("getTCPConnectionURL(userName,password) = " + getTCPConnectionURL(userName, password));
-
- InitialContext ctx = new InitialContext(properties);
- // Lookup connection factory
- TopicConnectionFactory connFactory = (TopicConnectionFactory) ctx.lookup(CF_NAME);
- TopicConnection topicConnection = connFactory.createTopicConnection();
- topicConnection.start();
- TopicSession topicSession =
- topicConnection.createTopicSession(false, QueueSession.AUTO_ACKNOWLEDGE);
-
- // Send message
- Topic topic = topicSession.createTopic(topicName);
- javax.jms.TopicSubscriber topicSubscriber = topicSession.createSubscriber(topic);
- Message message = topicSubscriber.receive();
- if (message instanceof TextMessage) {
- TextMessage textMessage = (TextMessage) message;
- System.out.println("textMessage.getText() = " + textMessage.getText());
- }
- topicSession.close();
- topicConnection.close();
- }
-
- public String getTCPConnectionURL(String username, String password) {
- // amqp://{username}:{password}@carbon/carbon?brokerlist='tcp://{hostname}:{port}'
- return new StringBuffer()
- .append("amqp://").append(username).append(":").append(password)
- .append("@").append(CARBON_CLIENT_ID)
- .append("/").append(CARBON_VIRTUAL_HOST_NAME)
- .append("?brokerlist='tcp://").append(CARBON_DEFAULT_HOSTNAME).append(":").append(CARBON_DEFAULT_PORT).append("'")
- .toString();
- }
-
- }
-
-
- </pre>
- <p>Also note that a MessageListener can be set to topicSubscriber to receive messages asynchronously.</p>
- </body>
-</html>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/docs/xdoc/samples_index.xml
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/samples_index.xml b/products/stratos2/cloud_controller/1.0.0/docs/xdoc/samples_index.xml
deleted file mode 100644
index 4a40608..0000000
--- a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/samples_index.xml
+++ /dev/null
@@ -1,79 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- ~ Copyright (c) 2009, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
- ~
- ~ WSO2 Inc. licenses this file to you under the Apache License,
- ~ Version 2.0 (the "License"); you may not use this file except
- ~ in compliance with the License.
- ~ You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- ~ KIND, either express or implied. See the License for the
- ~ specific language governing permissions and limitations
- ~ under the License.
- -->
-
-<!DOCTYPE html
- 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">
- <head>
- <meta http-equiv="content-type" content="text/html; charset=iso-8859-1"/>
- <title>
- WSO2 MB - Samples Guide Index
- </title>
- <link href="css/mb-docs.css" rel="stylesheet"/>
- <link href="styles/dist-docs.css" rel="stylesheet" type="text/css"
- media="all"/>
- </head>
-
- <body>
- [
- <a href="docs_index.html">Documentation Index</a>
- ]
- <h1>Running the WSO2 Message Broker Server (MB) Samples</h1>
-
- <h2>
- <a name="TOC">Table of Contents</a>
- </h2>
-
- <div class="section-content">
- <ul>
- <li>
- <a href="samples_index.html#Overview">Overview</a>
- </li>
- <li>
- <a href="samples/jms_queue_sample.html">JMS Queue Sample</a>
- </li>
- <li>
- <a href="samples/jms_topic_sample.html">JMS Topic Sample</a>
- </li>
- <li>
- <a href="samples/jms_transport_sample.html">JMS Transport Sample</a>
- </li>
- <li>
- <a href="samples/web_service_client_sample.html">Web Service Eventing Sample</a>
- </li>
- </ul>
- </div>
- <h2 id="Overview">Overview</h2>
- <p>
- This set of samples demonstrates the features in Message Broker product to use in
- various situations. We will use JMS APIs with Message Broker to
- publish,subscribe messages.
- </p>
- <p>
- The source code used in the samples can be found in $CARBON_HOME/samples.
- </p>
-
- <p>
- Please refers the
- <a href="user_guide.html">User Guide</a>
- to get familiar with Message Broker product.
- </p>
- </body>
-</html>
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/docs/xdoc/setting_java_home.xml
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/setting_java_home.xml b/products/stratos2/cloud_controller/1.0.0/docs/xdoc/setting_java_home.xml
deleted file mode 100644
index e3c073a..0000000
--- a/products/stratos2/cloud_controller/1.0.0/docs/xdoc/setting_java_home.xml
+++ /dev/null
@@ -1,53 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!--
- ~ Copyright (c) 2009, WSO2 Inc. (http://www.wso2.org) All Rights Reserved.
- ~
- ~ WSO2 Inc. licenses this file to you under the Apache License,
- ~ Version 2.0 (the "License"); you may not use this file except
- ~ in compliance with the License.
- ~ You may obtain a copy of the License at
- ~
- ~ http://www.apache.org/licenses/LICENSE-2.0
- ~
- ~ Unless required by applicable law or agreed to in writing,
- ~ software distributed under the License is distributed on an
- ~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- ~ KIND, either express or implied. See the License for the
- ~ specific language governing permissions and limitations
- ~ under the License.
- -->
-
-<!DOCTYPE html
- 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>How to setup JAVA_HOME environment variable in Windows</title>
- <link href="css/mb-docs.css" rel="stylesheet"/>
- <link href="styles/dist-docs.css" rel="stylesheet" type="text/css" media="all"/>
- </head>
- <body>
- <h2>How to setup JAVA_HOME environment variable in Windows</h2>
-
- <p>Please follow the instructions to set up JAVA_HOME environment variable in your computer.
- First find out the installation folder of Java development kit (JDK) in your machine.
- Let's
- assume it is installed in the folder "C:/j2sdk1.4.2"
- </p>
-
- <ol>
- <li>Right click on the My Computer icon on your desktop and select properties</li>
- <li>Click the Advanced Tab</li>
- <li>Click the Environment Variables button</li>
- <li>Under System Variable, click New</li>
- <li>Enter the variable name as JAVA_HOME</li>
- <li>Enter the variable value as the install path for the Development Kit</li>
- <li>Click OK</li>
- <li>Click Apply Changes</li>
-
- </ol>
-
- <img src="images/set-java-home.jpg" width="802" height="590" alt=""/>
- </body>
-</html>
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/bottom.gif
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/bottom.gif b/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/bottom.gif
deleted file mode 100644
index 5679266..0000000
Binary files a/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/bottom.gif and /dev/null differ
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/feature-01-icon.gif
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/feature-01-icon.gif b/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/feature-01-icon.gif
deleted file mode 100644
index b4ea8cd..0000000
Binary files a/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/feature-01-icon.gif and /dev/null differ
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/powered-logo.gif
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/powered-logo.gif b/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/powered-logo.gif
deleted file mode 100644
index fb478bf..0000000
Binary files a/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/powered-logo.gif and /dev/null differ
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/register.gif
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/register.gif b/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/register.gif
deleted file mode 100644
index 98c5362..0000000
Binary files a/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/register.gif and /dev/null differ
http://git-wip-us.apache.org/repos/asf/incubator-stratos/blob/a6d73412/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/title-bg.gif
----------------------------------------------------------------------
diff --git a/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/title-bg.gif b/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/title-bg.gif
deleted file mode 100644
index 2d539a7..0000000
Binary files a/products/stratos2/cloud_controller/1.0.0/modules/distribution/lib/home/images/title-bg.gif and /dev/null differ