Starting ESB Management Console on Linux and Solaris
- Former user (Deleted)
Once you have installed WSO2 ESB v.4.0.3 (See Installing ESB on Linux and Solaris from Binary Distribution, Installing ESB on Linux and Solaris from Source Distribution), follow the instructions below to access ESB Management Console on Linux or Solaris from the command prompt.
Establish a SSH connection to the Linux/Solaris machine or log in on the text Linux console.Â
Step 1. Execute the WSO2 ESB Start Script
Follow the instructions below to execute the WSO2 ESB start script from the bin folder.
1. Establish a SSH connection to the Linux server or log in on the text Linux console.
2. Go to <ESB_HOME>/bin, where "<ESB_HOME>" is actual folder where WSO2 ESB files are stored.
3. Execute the following command to start ESB:
sh ./wso2server.sh
4. Operation log is displayed. ESB is running. The last line in the following example indicates the ESB has been started successfully.
Step 2. Access ESB Management Console (Web Interface)
With WSO2 ESB properly installed, you can access its Management Console (web interface) by opening a Web browser and typing in the Host Name or IP address of the ESB.
Accessing ESB from Local Machine
1. You can connect to the ESB Web Interface from the computer where it is installed. Open a Web browser and access the following URL:
https://localhost:9443/esb
2. WSO2 ESB homepage opens.
Accessing ESB from Internet/LAN
To connect to the ESB Web Interface from any computer connected to Internet/LAN, follow the instructions below.
1. Open a Web browser and access the real IP of the WSO2 ESB server. Typically, it is same as the IP address of the computer. Example:
https://192.168.56.32:9443/esb
2. WSO2 ESB homepage opens.
Notice
A situation can occur, in which Internet browser will display an insecure connection message, requiring the user's confirmation of being aware of the risks.
The WSO2 ESB 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 doesn't prove the server identity. So, when the users try to access the WSO2 ESB 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.
Step 3. Login to ESB Management Console (Web Interface)
Once you have established a connection to the WSO2 ESB, you will be prompted for a "Username" and "Password." Type in default "admin" as the "Username" and "admin" as the "Password." Click on "Sign-in."
Now you are logged into the WSO2 ESB Management Console.
