Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Code Block
wso2server.bat --run
Info
titleNote

Note that you can pass some system properties when starting the server.

4. The operation log is displayed, showing that the Governance Registry start script is running.

...

Note
titleNotice

A situation may occur in which your Internet browser displays an insecure connection message, requiring the user's confirmation to proceed.Image Removed

The WSO2 Governance Registry 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 with which it works is used for encryption purposes only and does not verify the server's identity. So, when users try to access the WSO2 Governance Registry Management Console, they may receive a warning that they are trying to connect to an untrusted connection. In order to continue working with this certificate, you must "accept" the certificate before access to the site is permitted. If the Mozilla Firefox browser is used, this warning message only occurs the first time that the server is accessed. The certificate is then stored in the browser's database, marked as "trusted." When other browsers are used, an insecure connection warning may be displayed every time the server is accessed.

This scenario is suitable for testing purposes or for running the program on a company's internal networks. But in cases where 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 by which it is accessed and that this server actually belongs to the given organization.

...

5. Now you are logged in to the WSO2 Governance Registry Management Console.

Instructions on how to start and access the Governance Registry Management Console (web interface) on Windows.
Excerptinfo
hiddenicontrue
false

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>