Unknown macro: {next_previous_links}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

  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, where <PRODUCT_HOME> is the directory where you installed the product distribution. For more information on the preferred profile, see Running the Product in a Specific Profile.

    OSCommand
    On Windows
    <CARBON_HOME>\bin\wso2server.bat -Dprofile=<preferred-profile> --run
    On Linux/Solaris

    sh <CARBON_HOME>/bin/wso2server.sh -Dprofile=<profile>

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

    sh <CARBON_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

Corresponding profile names

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

Service/ApplicationProfile Name
web applicationwebapp
Axis2 serviceaxis2service
Data servicedataservice
Jaggeryjaggery
Mashup Servicemashup

How does multi-profiling work?

When starting a product with a given profile, it starts the product with a subset of the features available 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 <PRODUCT_HOME>/repository/components/default/configuration/org.eclipse.equinox.simpleconfigurator/ directory, which includes references to all the 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_HOME>/repository/components/<profile-name>/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info

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

<PRODUCT_HOME>/repository/components/webapp/configuration/org.eclipse.equinox.simpleconfigurator/

 

  • No labels