Versions Compared

Old Version 3

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.

...

Info

The Management Console uses the default HTTP-NIO transport, which is configured in the catalina-server.xml file in the <PRODUCT<GREG_HOME>/repository/conf/tomcat directory. This transport must be properly configured in this file for the Management Console to be accessible.

...

To start the server, you run the script wso2server.bat (on Windows) or wso2server.sh (on Linux/Solaris) from the bin folder. Alternatively, you can install and run the server server as a Windows service.

Info

We do not recommend starting WSO2 products as a daemon, because there is a known issue that causes automatic restarts in the wrapper mode. Instead, you can configure the heap memory allocations in the wso2server.sh script and run it using the nohup command. For example:

nohup ./wso2server.sh &To start and stop the server in the background mode of Linux, run wso2server.sh start and wso2server.sh stop commands.

  1. 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 in to the text Linux console.
  2. Execute one of the following commands, where <PRODUCT<GREG_HOME> is the directory where you installed the product distribution:
    • On Windows: <PRODUCT<GREG_HOME>/bin/wso2server.bat --run

    • On Linux/Solaris: sh <GREG_HOME>/bin/wso2server.sh

      Info

      If you want to provide access to the production environment without allowing any user group (including admin) to log into the management console, execute one of the following commands.

      • On Windows: <PRODUCT_HOME>\bin\wso2server.bat --run -DworkerNode
      • On Linux/Solaris: sh <PRODUCT_HOME>/bin/wso2server.sh -DworkerNode

      For additional options you can use with these startup commands, type -help after the command, such as: sh <PRODUCT_HOME>/bin/wso2server.sh -help

       

The operation log appears. When the product server is running, the log displays the message "WSO2 Carbon started in 'n' seconds."

When a WSO2 product server starts, it starts all features and related artifacts bundled in the product. If you want to start only a subset of features (e.g., only the backend features), see Running the product on a Preferred Profile.

...

Running the management console
Anchor
run
run

Once the server has started, you can 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. For example:

...

At the sign-in screen, sign in to the Management Console using admin as both the username and password. You can then use the Management Console to manage the product. 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 the Help link in the top right corner of that page page , or click the Docs link to open this documentation for full information on managing the product.

Info

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

The Management Console is based on 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, so 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 belongs to the given organization.

If you leave the Management Console unattended, the session will time out. The default timeout value is 15 minutes, but you can change this in the <PRODUCT<GREG_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>
 
Stopping the server
 Anchor
stop
stop
...