Versions Compared

Key

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

...

  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 in to 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/Solaris/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".

Running 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:

...

The URL for the ES Management Console should be in the following format: 
https://<Server Host>:9443/carbon carbon 
http://<Server Host>:9763/carbon carbon 

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 Management Console URL by modifying the value of the <MgtHostName> property in the <ES_HOME>/repository/conf/carbon.xml file. 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:

...

You can restrict access to the Management Console of your product by binding the Management Console with selected IP addresses. You can either restrict access to the Management Console only, or you can restrict access to all Web applications in your server as explained below. 

  • To control access only to the Management Console, add the IP addresses to the <ES_HOME>/repository/conf/tomcat/carbon/META-INF/context.xml file as follows:

    Code Block
    <Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="<IP-address-01>|<IP-address-02>|<IP-address-03>"/>

    The RemoteAddrValve Tomcat valve defined in this file only applies to the Management Console, and thereby all outside requests to the Management Console are blocked. 

  • To control access to all Web applications deployed in your server, add the IP addresses to the <ES_HOME>/repository/conf/context.xml file as follows.

    Code Block
    <Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="<IP-address-01>|<IP-address-02>|<IP-address-03>"/>

    The RemoteAddrValve Tomcat valve defined in this file applies to each Web application hosted on the WSO2 product server. Therefore, all outside requests to any Web application are blocked.

  • You can also restrict access to particular servlets in a Web application by adding a Remote Address Filter to the <ES_HOME>/repository/conf/tomcat/web.xml file and by mapping that filter to the servlet URL. In the Remote Address Filter that you add, you can specify the IP addresses that should be allowed to access the servlet. The following example from a web.xml file illustrates how access to the Management Console page (/carbon/admin/login.jsp) is granted only to one IP address.

    Code Block
    <filter>
        <filter-name>Remote Address Filter</filter-name>
        <filter-class>org.apache.catalina.filters.RemoteAddrFilter</filter-class>
            <init-param>
                <param-name>allow</param-name>
                <param-value>127.0.01</param-value>
            </init-param>
    </filter>
    
    <filter-mapping>
        <filter-name>Remote Address Filter</filter-name>
        <url-pattern>/carbon/admin/login.jsp</url-pattern>
    </filter-mapping>

...