Page Comparison

...

...

...

...

...

...

...

...

...

...

...

...

1. Download the product distribution.
   For more information, see Downloading the Product.
2. Open a command prompt:
• On Windows, choose Start > Run, type cmd at the prompt, and press Enter.
• On Linux/Solaris, establish a SSH connection to the server or log into the Linux console.

3. Execute one of the following commands to start a product on a preferred profile, where <PRODUCT_HOME> is the directory where you installed the product distribution and . For more information on the preferred profile, see Running the Product in a Specific ProfileAS profiles.

   OS	Command
   On Windows	<PRODUCT_HOME>\bin\wso2server.bat -Dprofile=<preferred-profile> --run
   On Linux/Solaris	sh <PRODUCT _HOME>/bin/wso2server.sh -Dprofile=<profile><preferred-profile>

   For example, in Linux/Solaris to start the Application Server with the support for Axis2 services only, type the following command:

   sh <PRODUCT_HOME>/bin/wso2server.sh -Dprofile=axis2service

4. Once the server has started, run the Management Console by opening a Web browser and typing in the management console's URL.
   The URL is displayed as the last line in the start script's console and log. The URL should be in the following format: https://<Server Host>:9443/carbon

...

AS profiles

The following are the list of profiles that corresponds to the respective services/applications:

How

...

multi-profiling

...

works

When starting Starting a product with on a given preferred profile , it starts the product with only a subset of the features available bundled in AS. We maintain a file named bundles.info that includes the references to the components/bundles inside the <PRODUCT_HOME>/repository/components/plugins/ directory. By default, we reference the bundles.info file under the the product. In order to identify what feature bundles apply to which profile, each product maintains a set of  bundles.info files in the <PRODUCT_HOME>/repository/components/default<profile-name>/configuration/org.eclipse.equinox.simpleconfigurator/ directory, which includes directories. The bundles.info files contain references to all the actual bundles in the <PRODUCT_HOME>/repository/components/plugins/ directory. Therefore, when you start the product, you get all the features available. However, the user can modify the bundles.info file to load only a set of features that he/she needs. Therefore, we have created several bundles.info files, each containing a given subset of features. In the case of the webapp profile, we only included the features required for the function of the web applications. While, the default bundles.info is located inside the above said location, the bundles.info for other profiles are located inside the following directory:<PRODUCT. Note that <profile-name> in the directory path refers to the name of the profile. For example, when there is a product profile named webapp, references to all the feature bundles required for the webapp profile to function are in a bundles.info file saved in <PRODUCT_HOME>/repository/components/<profile-name>webapp/configuration/org.eclipse.equinox.simpleconfigurator/bundles directory.info

For example, for the webapp profile, the bundles.info is located in the following directory:

Note that when you start the server without using a preferred profile, the server refers to the <PRODUCT_HOME>/repository/components/

...

default/configuration/org.eclipse.equinox.simpleconfigurator/

...

bundles.info file by default. This file contains references to all bundles in the <PRODUCT_HOME>/repository/components/plugins directory, which is where all the components/bundles of a product are saved.