Installing Bridge

Wherever you install Bridge, the hosting DiveLine serves as the basis for its user list. Once you have determined which DiveLine to use for Bridge, launch the installer downloaded from DI-Download. This section guides you through the installation process of Bridge for Windows.

NOTE: You need to be an administrative user to install the software.

To install Bridge:

  1. Navigate to the DI\Solution\downloads directory.

  2. Double-click the Bridge-Setup.exe file.

    The User Account Control dialog box opens, asking you to confirm making changes to your device.

    NOTE: Depending on your Windows version and user account settings, you might see the Open File - Security Warning dialog box instead. Confirm that you want to open and run the executable.

  3. Click Yes.

    The Bridge <version number> Setup Wizard dialog box opens.

    The Bridge Setup Wizard.

  4. Click Next.

    The Installing a New Portal page opens.

    Enter the location of the DI Solution directory.

  5. Verify the default locations for the DI and DI Solution directories.

  6. Click Next.

    The Required Software page opens.

    The required software page.

  7. Do one of the following:

    • If already installed, verify the existing installation paths and change if necessary.

      NOTE: If Tomcat already has HTTPS installed, skip to Step 12.

    • If not installed, select the Install Java or Install Apache Tomcat or both check boxes and follow the instructions. If following the installation guide, Java is installed in Installing DiveLine, and Tomcat in Installing DivePort.

  8. Click Next.

    The Create Certificate for HTTPS page opens.

    Creating a Certificate for HTTPS.

  9. Do one of the following:

    • Fill in the information as appropriate and click Create Certificate.
    • Select Skip this Step.

    NOTE: If you installed DiveLine, there is already a certificate available. Select Skip this Step.

  10. Click Next.

    The Certificate Signing Request for HTTPS page opens.

    Certificate Signing Request for HTTPS.

  11. Do one of the following:

    • Verify the information and click Create Request.
    • Select the Skip this step check box.

    NOTE: If you installed DiveLine, there is already a certificate available. Select Skip this Step.

  12. Click Next.

    The Installing a New Portal page opens with the following defaults:

    • Portal name—The default name is bridge. You can change it to suit your needs.
    • Path to DI Solution folder—The default folder is C:\DI\Solution.
    • Path to Java Runtime Environment—The default path is C:\DI\Java\jdk-11.0.1.
    • Path to Apache Tomcat Server—The default path is C:\DI\Tomcat\Tomcat 9.0.

    A best practice is to change the default Portal name to something other than bridge (for example, bridge-test) to keep the software distinct from another implementation. One installation of the software can support multiple instances or portals. Verify the other default fields.

    Installing a New Portal.

  13. Click Next.

    The second Installing a New Portal page opens, with the default name of the DiveLine service and port number (for example, jsmith-001:3330). Verify that the port number matches the DiveLine service. This page also prompts you to enter the administrator Username and Password previously defined for the DiveLine administrator.

    DiveLine server and port number.

  14. Click Next.

    The Ready to Install page opens, with a summary of the Bridge installation information. Verify the information. Use the Back button if needed.

    Ready to Install.

    NOTE: Take note of the Portal URL. This is used to access Bridge from a web browser.

  15. Click Install.

  16. Click Finish to close the installation wizard.

    The Completing page.

NOTES:

  • The default web application name is bridge. This is easily changed when installing.
  • The Bridge application has its own section in the Windows Registry.
  • The Bridge software has its own section in the Windows Start menu. From the Start menu, enter “bridge” to see a link for the <bridge> Logon Page. Click to open in your default browser.
  • When multiple instances of Bridge are installed on the same Windows machine, you might want to edit Properties to display different Program labels from the Start menu.
  • Multiple Bridges can be installed on a single server, or multiple servers, and can communicate each other. When nesting Bridges, avoid creating circular loops. That is, if Bridge A points to Bridge B, Bridge B should not point back to Bridge A.