All docs This doc

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: ✉️: [APM] Duplicate content in the docs APM 2.5.0

...

Info

The Management Console uses the default HTTP-NIO transport, which is configured in the <PRODUCT_HOME>/repository/conf/tomcat/catalina-server.xml file. (<PRODUCT_HOME> is the directory where you installed the WSO2 product you want to run.) You must properly In order to access the Management Console, you must configure the HTTP-NIO transport properly in this file to access the Management Console. For more information on the HTTP-NIO transport, see the related topics section at the bottom of this page.

...

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

On Windows/Linux/Mac OS

To start the server, you run <PRODUCT_HOME>\bin\wso2server.bat (on Windows) or <PRODUCT_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/Mac OS: Establish an SSH connection to the server, log on to the text Linux console, or open a terminal window.
  2. Navigate to the <PRODUCT_HOME>/bin/ directory using the Command Promptthe command prompt.
  3. Execute one of the following commands:
    • To start the server in a typical environment:
      • On Windows:  wso2server.bat --run
      • On Linux/Mac OS:  sh wso2server.sh

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

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

      • On Windows: wso2server.bat --run -DworkerNode
      • On Linux/Mac OS: sh wso2server.sh -DworkerNode
    • To check for additional options you can use with the startup commands, type -help after the command, such as: 
      sh wso2server.sh -help (see the related topics section at the end of this page).
  4. The operation log appears in the command window. When the product server has started successfully started, the log displays the message "WSO2 Carbon started in 'n' seconds".

On Solaris

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

Note

Following instructions are tested on an Oracle Solaris 10 8/11 x86 environment.

  1. Anchor
    instructions
    instructions
    Click Launch - > Run Applications, type dtterm at the Promptprompt, and then press Enter, to  to open a Command Promptcommand prompt.
  2. Navigate to the <PRODUCT_HOME>/bin/ directory using the Command Promptthe command prompt.
  3. Execute the following command: bash wso2server.sh
  4. The operation log appears in the command window. When the product server has started successfully started, the log displays the message "WSO2 Carbon started in 'n' seconds".

...

Once the server has started, you can run the Management Console by typing its URL in a Web web browser. The following sections provide more information about running the Management Console:

Table of Content Zone
maxLevel5
minLevel5
locationtop
Working with the URL

The URL appears next to “Mgt Mgt Console URL” URL in the start script log that is displayed in the command window. For example:

The URL should be in the following format: https://<Server Host>:9443/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

Note

You can change the Management Console URL by modifying the value of the <MgtHostName> property in the <PRODUCT_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:

Code Block
In /etc/hosts:
127.0.0.1       localhost

In carbon.xml:
<MgtHostName>localhost</MgtHostName>
Signing in

At the sign-in screen, you can sign in to the Management Console using admin as both the username and password.

Info

When the Management Console sign-in page appears, the Web web browser typically displays an "insecure connection" message, which requires your confirmation before you can continue.

The Management Console is based on the HTTPS protocol, which is a combination of HTTP and SSL protocols. This protocol is generally used to encrypt the traffic from the client to server for security reasons. The certificate it works with is used for encryption only, and does not prove the server identity. Therefore, when you try to access the Management Console, a warning of untrusted connection is usually displayed. To continue working with this certificate, some steps should be taken to "accept" the certificate before access to the site is permitted. If you are using the Mozilla Firefox browser, this usually occurs only on the first access to the server, after which the certificate is stored in the browser database and marked as trusted. With other browsers, the insecure connection warning might be displayed every time you access the server.

This scenario is suitable for testing purposes, or for running the program on the company's internal networks. If you want to make the Management Console available to external users, your organization should obtain a certificate signed by a well-known certificate authority, which verifies that the server actually has the name it is accessed by and that this server actually belongs to the given organization.

Getting help

The tabs and menu items in the navigation pane on the left may vary depending on the features you have installed. To view information about a particular page, click the Help link at the top right corner of that page, or click the Docs link to open the documentation for full information on managing the product.

Configuring the session time-out

If you leave the Management Console unattended for a defined time, its login session will time out. The default timeout value is 15 minutes, but you can change this in the <PRODUCT_HOME>/repository/conf/tomcat/carbon/WEB-INF/web.xml file as follows.

Code Block
languagehtml/xml
<session-config>
   <session-timeout>15</session-timeout>
</session-config>
Tip

In products like WSO2 API Manager where web applications such as API Publisher/API Store exist, you can configure a session time out timeout for those web apps by changing the repository/conf/tomcat/web.xml file as follows:

Code Block
    <session-config>
        <session-timeout>15</session-timeout>
    </session-config>
Restricting access to the Management Console and Web applications

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 <PRODUCT_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 <PRODUCT_HOME>/repository/conf/tomcat/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 <PRODUCT_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>
Info
Any configurations (including valves defined in the <PRODUCT_HOME>/repository/conf/tomcat/catalina-server.xml file) apply to all Web applications and are globally available across the server, regardless of the host or cluster. For more information about using remote host filters, see the Apache Tomcat documentation.
timeout>
    </session-config>

Accessing the API Publisher

Once the server has started, you can run the API Publisher by typing its URL in a Web web browser. The following sections provide more information about running the API Publisher:

Table of Content Zone
maxLevel5
minLevel5
locationtop
Working with the URL

The URL appears next to “API API Publisher Default Context” Context in the start script log that is displayed in the command window. For example:

The URL should be in the following format: https://<Server Host>:9443/publisher

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

Signing in

At the sign-in screen, you can sign in to the API Publisher using admin as both the username and password.

Info

When the API Publisher sign-in page appears, the Web web browser typically displays an "insecure connection" message, which requires your confirmation before you can continue.

The API Publisher is based on the HTTPS protocol, which is a combination of HTTP and SSL protocols. This protocol is generally used to encrypt the traffic from the client to server for security reasons. The certificate it works with is used for encryption only, and does not prove the server identity. Therefore, when you try to access the API Publisher, a warning of untrusted connection is usually displayed. To continue working with this certificate, some steps should be taken to "accept" the certificate before access to the site is permitted. If you are using the Mozilla Firefox browser, this usually occurs only on the first access to the server, after which the certificate is stored in the browser database and marked as trusted. With other browsers, the insecure connection warning might be displayed every time you access the server.

This scenario is suitable for testing purposes, or for running the program on the company's internal networks. If you want to make the API Publisher available to external users, your organization should obtain a certificate signed by a well-known certificate authority, which verifies that the server actually has the name it is accessed by and that this server actually belongs to the given organization

...

Once the server has started, you can run the API Store by typing its URL in a Web web browser. The following sections provide more information about running the API Store:

Table of Content Zone
maxLevel5
minLevel5
locationtop
Working with the URL

The URL appears next to “API API Store Default Context” Context in the start script log that is displayed in the command window. For example:

The URL should be in the following format: https://<Server Host>:9443/store

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

Signing in

At the API Store home page, you can click sign in link at top right corner to sign-in to the API Publisher using admin as both the username and password.

Info

When the API Store home page appears, the Web browser typically displays an "insecure connection" message, which requires your confirmation before you can continue.

The API Store is based on the HTTPS protocol, which is a combination of HTTP and SSL protocols. This protocol is generally used to encrypt the traffic from the client to server for security reasons. The certificate it works with is used for encryption only, and does not prove the server identity. Therefore, when you try to access the API Store, a warning of untrusted connection is usually displayed. To continue working with this certificate, some steps should be taken to "accept" the certificate before access to the site is permitted. If you are using the Mozilla Firefox browser, this usually occurs only on the first access to the server, after which the certificate is stored in the browser database and marked as trusted. With other browsers, the insecure connection warning might be displayed every time you access the server.

This scenario is suitable for testing purposes, or for running the program on the company's internal networks. If you want to make the API Store available to external users, your organization should obtain a certificate signed by a well-known certificate authority, which verifies that the server actually has the name it is accessed by and that this server actually belongs to the given organization

...

sh <PRODUCT_HOME>/bin/wso2server.sh stop

...

Restricting

...

access to the Management Console and

...

web applications

You can restrict access to the management console of your product by binding the management console with selected IP addresses. Note that 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 <PRODUCT_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 will only apply to the Carbon management console, and thereby all outside requests to the management console will be blocked. 

  • To control access to all web applications deployed in your server, add the IP addresses to

...

  • the <PRODUCT_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 will apply to each web application hosted on the Carbon server. Therefore, all outside requests to any web application will be blocked.

  • You can also restrict access to particular servlets in a web application by adding a Remote Address Filter to

...

  • the web.xml

...

  •  file (stored in

...

  • the <PRODUCT_HOME>/repository/conf/tomcat/

...

  •  directory), 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

...

  • web.xml

...

  •  file illustrates how access to the management 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>


Info

...

Any configurations (including valves

...

defined in the <PRODUCT_HOME>/repository/conf/tomcat/catalina-server.xml file

...

) apply to all web applications and

...

are available globally

...

across the server, regardless of the host or cluster.

...

For more information

...

on using remote host filters, see the Apache Tomcat documentation.
Panel
titleRelated

...