Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

To run WSO2 Enterprise Store (ES), you start the product server at the command line. You can then run the ES Publisher (Back Office), to configure and manage the store assets; while you can use the Store as an asset catalog. You can then run the ES Management Console to configure and manage the product. 

...

Starting the server

Tip

If you want your dynamic changes on asset type RXTs to take place as a hot deployment in ES, then first enable asset hot deployment before starting the server. For more information, see Asset Type Hot Deployment.

Follow the instructions below to start your WSO2 product ES based on the Operating System that you use.

On Windows/Linux/Mac OS

To start the server, you run <ES_HOME>/bin/wso2server.bat (on Windows) or <ES_HOME>/bin/wso2server.sh (on Linux/Mac OS) from the command prompt as described below. Alternatively, you can install and run the server as a Windows or Linux service (see the related topics section at the end of this page).

  1. Open a command prompt by following the instructions below.
    • On Windows: Click Start -> Run, type cmd at the prompt, and then press Enter.
    • On Linux/Solaris/Mac OS: Establish an SSH connection to the server, log into the text Linux console, or open a terminal window.
  2. Execute one of the following commands:
    • To start the server in a typical environment:
      • On Windows:  <ES_HOME>\bin\wso2server.bat --run

      • On Linux/Solaris/Mac OS:  sh <ES_HOME>/bin/wso2server.sh

    • To start the server in the background mode of Linux: sh <ES_HOME>/bin/wso2server.sh start
      To stop the server running in this mode, you will enter: sh <ES_HOME>/bin/wso2server.sh stop

      Excerpt
      hiddentrue

      • To provide access to the production environment without allowing any user group (including admin) to log into the Management Console:

        • On Windows: <ES_HOME>\bin\wso2server.bat --run -DworkerNode
        • On Linux/Mac OS: sh <ES_HOME>/bin/wso2server.sh -DworkerNode

      The above is not available in ES.

    • To check for additional options you can use with the startup commands, type -help after the command, such as:
      sh <ES_HOME>/bin/wso2server.sh -help (see the related topics section at the end of this page).

  3. The operation log appears in the command window. When the product server has successfully started, the log displays the message "WSO2 Carbon started in 'n' seconds".

...

To start the server, you run <PRODUCT<ES_HOME>/bin/wso2server.sh  from the Command Prompt as described below. 

...

  1. Anchor
    instructions
    instructions
    Click Launch -> Run Applications, type dtterm at the Prompt, and then press Enter, to open a Command Prompt.
  2. Navigate to the <PRODUCT<ES_HOME>/bin directory using the Command Prompt.

  3. Execute the following command:

    Code Block
    bash wso2server.sh

  4. The operation log appears in the command window. When the product server has successfully started, the log displays the message "WSO2 Carbon started in 'n' seconds".

    1. nohup

    1. sh

    1. "$CARBON_HOME"/bin/wso2server.sh

    1. $args

    1. >

    1. /dev/null

    1. 2>&1

    1. &

    2. Replace

the latter mentioned

    1. those occurrences with the following

.nohup bash

    1. :  nohup bash "$CARBON_HOME"/bin/wso2server.sh

    1. $args

    1. >

    1. /dev/null

    1. 2>&1

    1. &

Info
You need to do the following modification to the <PRODUCT_HOME>/bin/wso2server.sh file, to start the product as a service/in nohup mode on Solaris.
Open the <PRODUCT

If you are starting the product in service/nohup mode in Solaris, do the following:

  1. Update the <ES_HOME>/bin/wso2server.sh file
in a text editor.
  1. as follows:

    1. Search for the following occurrences: 

Code Block
Code Block
Tip

The only change is replacing sh with bash. This is required only for Solaris.

  • Update your PATH variable to have /usr/xpg4/bin/sh as the first element. This is because /usr/xpg4/bin/sh contains an sh shell that is newer than the default sh shell. You can set this variable as a system property in the wso2server.sh script or you can run the following command on a terminal:

    Code Block
    export PATH=/usr/xpg4/bin/sh:$PATH
  • Start the product by following the above instructions.

    • Accessing the ES Consoles

    Once the server has started, you can run the ES Management Console, Publisher (Back-Office) Console or Store Console by typing its URL in a Web browser. For more information, see Accessing ES Consoles. 

    ...

    You can use this URL to access the Management Console on this computer from any other computer connected to the Internet or LAN. When accessing the Management Console from the same server where it is installed, you can type localhost instead of the IP address as follows: https://localhost:9443/carbon You can change the

    Tip

    The Management Console URL can be changed by modifying the value of

    ...

    the MgtHostName in the <ES_HOME>/repository/conf/carbon.xmlfile.

    Code Block
    <MgtHostName>localhost</MgtHostName>

    When the host is internal or not resolved by a DNS, map the hostname alias to its IP address in the /etc/hosts file of your system, and then enter that alias as the value of the <MgtHostName> property in carbon.xml. For example:

    ...