|Table of Contents|
Before you begin
Before you start the server, note the following:
config-validation.xmlfile in the
<PRODUCT_HOME>/repository/conf/etcdirectory contains a list of recommended system parameters, which are validated against your system when the server starts. See Configuring config-validation.xml for details on modifying these parameters before starting the server.
- The Management Console uses the
- default HTTP-NIO transport, which is configured in
- file in
- directory. This transport must be properly configured in this file for the Management Console to be accessible.
Changing the default configurations
After you download the product is downloaded, you must change the default configurations in the product installation (as per have to be changed according to your requirement), before starting you start the server. See See the following topics for details:
- Open a command prompt:
- On Windows, choose Start -> Run, type
cmdat the prompt, and press Enter.
- On Linux/Solaris, establish a SSH connection to the server or log in to the text Linux console.
Execute one of the following commands, where
<SS_HOME> is the directory where you installed the product distribution:
- On Windows:
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.
If you want to check any additional options available to be used with the startup commands, type
The operation log appears. When the product server is running, the log displays the message "WSO2 Carbon started in 'n' seconds".
Running the management console
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 Help link in the top right corner of that page , or click the Docs link to open this documentation for full information on managing the product.
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
<SS_HOME>/repository/conf/tomcat/carbon/WEB-INF/web.xml file as follows:
<session-config> <session-timeout>15</session-timeout> </session-config>
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.
Note: Any configurations (including valves) defined in the
Stopping the server