To run WSO2 products, you start the product server at the command line. You can then run the Management Console to configure and manage the product.
...
Once the server has started, you can access the Management Console by typing its URL in a Web browser. The following sections provide more information about running the Management Console:Table of Contents
- Working with the URL
- Signing in
- Getting help
- Configuring the session time-out
- Restricting access to the Management Console and Web applications
Working with the URL
| Anchor | ||||
|---|---|---|---|---|
|
The URL appears next to “Mgt Console URL” in the start script log that is displayed in the command window. For example:
...
| Code Block |
|---|
In /etc/hosts: 127.0.0.1 localhost In carbon.xml: <MgtHostName>localhost</MgtHostName> |
Signing in
| Anchor | ||||
|---|---|---|---|---|
|
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 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
| Anchor | ||||
|---|---|---|---|---|
|
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
| Anchor | ||||
|---|---|---|---|---|
|
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 | ||
|---|---|---|
| ||
<session-config> <session-timeout>15</session-timeout> </session-config> |
Restricting access to the Management Console and Web applications
| Anchor | ||||
|---|---|---|---|---|
|
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.
...
sh <PRODUCT_HOME>/bin/wso2server.sh stop
| Excerpt | ||
|---|---|---|
| ||
Related topicsNOTE TO WRITERS: copy this content manually to your change and add relative links to the appropriate pages within your document. If you do not have an HTTP-NIO Transport page in your doc, point to the page in the relevant version of the Carbon docs.
|