Checking the Web-based User Interface of the BRIDGE

Open a Web browser and enter the URL of the BRIDGE in the address bar. If you use a proxy, make sure that the proxy is bypassed for localhost, or alternatively for the external name or IP address of the node instance, where the BRIDGE has been installed.
If the BRIDGE runs on your local system, you can enter the URL for a local connection (https://localhost:8080). Note that the port 8080 was suggested as default value during the BRIDGE installation. If you changed that value, you have to enter the new port number in the URL.

The URL is case sensitive.

During the installation, a self-signed certificate was created and will be used to encrypt the communication between members of a BRIDGE domain and when deploying xUML services from MagicDraw (Scheer PAS BUILDER).
When entering the URL of the BRIDGE, the Web browser will display a security alert, as the BRIDGE runs with this self-signed security certificate, whose name may not match to the name of the site, or the certifying authority is not known by the browser. As this is a default certificate, always accept this certificate to run the BRIDGE.

If you have any problems accessing the page, try the following:

  • Make sure that you bypass the proxy server for localhost with your browser.
  • Disable all caches, proxies, etc. (e.g. by selecting direct connection to the internet in the browser settings).
  • Instead of localhost, use the external name or IP address of the server (e.g. https://bridge.scheer-acme.com:8080).
  • Port 8080 is the default port. If you changed it during the installation, make sure to use the correct port number in the URL.
  • Check if the Windows service/Unix daemon of the BRIDGE is running.

After accepting the self-signed certificate provided by Scheer E2E, …

…the login page is displayed.

Login with user admin and enter the password you have chosen during the installation.

Some Additional Checks for Linux Installations

Getting a List of all BRIDGE Installations

/etc/init.d/e2e_console list

The response contains the hostname and the location of all BRIDGE installations on this system.

Checking the Status of the BRIDGE

To check the background daemon you can use the following commands as root:

Checking the status for all BRIDGE installations on this system:
/etc/init.d/e2e_console status
Checking the status for a specific BRIDGE installation:
/etc/init.d/e2e_console status <DNS name> 

he following responses are possible:

  • Status of E2E Console <DNS name>: running

  • Status of E2E Console <DNS name>: not running

Stopping or Starting the BRIDGE

To start or stop the background daemon you can use the following commands as root:

Starting all installations on this system:

/etc/init.d/e2e_console start

Starting a specific installation:

/etc/init.d/e2e_console start <DNS name>

Stopping all installations on this system:

/etc/init.d/e2e_console stop

Stopping a specific installation:

/etc/init.d/e2e_console stop <DNS name>

The following responses are possible:

  • Starting E2E Console <DNS name>: ok

  • Starting E2E Console <DNS name>: error, already running

  • Stopping E2E Console <DNS name>: ...ok

  • Stopping E2E Console <DNS name>: not running

  • No labels