Versions Compared

Key

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

...

Make sure you have run the product by executing the shell script (for Linux/Solaris) or the batch file (for Windows) as explained in the previous section. With any WSO2 product properly installed, you can access its Management Console (Web interface) by opening a Web browser and typing in the management console's URL as it appears in the start script's log. For example,

WSO2 Carbon startImage Removedproduct management console URLImage Added

Accessing from Internet/LAN

...

1. You can also connect to the product's Web Interface from the computer where it is installed by typing "localhost"instead of the IP.

...

https://localhost:<Server

...

Port>/carbon

Tip

The Management Console URL can be changed by modifying the value of the MgtHostName in the <PRODUCT_HOME>/repository/conf/carbon.xmlfile.

Code Block
languagexml
<MgtHostName>localhost</MgtHostName>

2. Once you have established a connection, the Management Console opens in the anonymous mode.

Info
iconfalse

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 <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>
 
Info
titleNotice

When the product's homepage opens, it is possible that the Internet browser will display an "insecure connection" message, requiring your confirmation of being aware of the risks.

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 the users try to access the Management Console, a warning of untrusted connection is usually displayed. In order to continue working with this certificate, some steps should be taken to "accept" the certificate before access to the site is permitted. In case Mozilla Firefox browser is used, this usually occurs only on the first access to the server. Then the certificate is stored in the browser database marked as trusted. In case of some other browsers are used, insecure connection warning may be displayed every time server is accessed.

This scenario is suitable for testing purposes, or for running the program on the company's internal networks. But in case there is a need to provide an interface to the outside world, a company should obtain a certificate signed by a well-known CA. The role of a CA is to verify that the server accessed actually has the name it is accessed by, and that this server actually belongs to the given organization.

The homepage of the Management Console typically has the following sections:

...