Once you have installed WSO2 Governance Registry (See Installing Governance Registry on Windows from Binary Distribution, Installing Governance Registry on Windows from Source Distribution), follow the below instructions to access the Governance Registry Management Console on Windows.
...
| Table of Contents | ||||
|---|---|---|---|---|
|
...
|
...
Step 1. Execute Governance Registry Start Script
...
2. Execute the following command, replacing "<GREG_HOME>" with the path of the Governance Registry installation folder (e.g., c:\greg\wso2greg-4.15.10\bin):
| Code Block |
|---|
cd <GREG_HOME>\bin |
3. Execute the following command:
| Code Block |
|---|
wso2server.bat --run |
...
| Info | ||
|---|---|---|
| ||
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.
...
Step 2. Access Governance Registry Management Console (Web Interface)
...
1. You can connect to the Governance Registry Web Interface from the computer on which it is installed. Open a web browser and enter the following URL:
| Code Block |
|---|
https://localhost:9443/carbon
|
...
1. Open a web browser and enter the actual IP address of the server for WSO2 Governance Registry. Typically, it is the same as the IP address of the computer. Example:
| Code Block |
|---|
https://192.168.56.32:9443/carbon
|
...
| Note | ||
|---|---|---|
| ||
A situation may occur in which your Internet browser displays an insecure connection message, requiring the user's confirmation to proceed.
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.
excerpt
| Info |
|---|
...
|
...
| |||||
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:
|