Installing a DivePort Instance for DiveTab

Before you set up a DiveTab, you must set up a DivePort instance because a DivePort URL is required to configure the DiveTab in Workbench. The first instance of a DivePort on a server installs Java plus Apache Tomcat to act as the web application server. You can have other DivePorts installed on your server—a new instance can be installed for DiveTab at any time.

NOTE: DI recommends that DiveTab have its own DivePort instance—do not share a single DivePort instance for portal use and for DiveTab use.

To install a new DivePort instance on a Linux server for your DiveTab, refer to the installation guides, found at Windows 7.0 Installation and Operation Guides or Linux 7.0 Installation and Operation Guides.

To install a new DivePort instance on a Windows server for your DiveTab:

  1. Navigate to the DI\Solution\downloads directory, or where the DivePort-Setup.exe file is located.

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

    The Open File – Security Warning Closeddialog box opens.

    The Open File dialog box.

  3. Click Run.

    The DivePort <version number> Setup Wizard Closeddialog box opens.

    The DivePort Setup Wizard window.

  4. Click Next.

    The Choose an Action Closeddialog box opens.

    The Choose an Action dialog box for installing DivePort.

    NOTE: This dialog box does not appear if you have no existing DivePort installed. Instead, the Required Software dialog box (Step 6) opens.

  5. Select Install a new portal.

  6. Click Next.

    The Required Software Closeddialog box opens.

    The Required Software window.

  7. If the Existing Java Installation and Existing Tomcat Installation boxes show that the software is already installed, verify the installation locations and proceed to Step 8.

    If the Existing Java Installation, Existing Tomcat Installation, or both boxes are empty, select Install Java or Install Apache Tomcat or both, click Next, and follow the instructions to install these required components until a successful installation message displays.

  8. Click Next.

    The Create Certificate for HTTPS Closeddialog box opens.

    The Create Certificate for HTTPS dialog box.

  9. Do one of the following:

    • Fill out the details for the self-signed HTTPS certificate, and click Create Certificate to generate a self-signed certificate.
    • Select Skip this step.

    NOTE: A self-signed certificate generates browser warnings requiring you to verify the authenticity of the certificate.

  10. Click Next.

    The Certificate Signing Request for HTTPS Closeddialog box opens.

    The Certificate Signing Request for HTTPS dialog box.

  11. Do one of the following:

    • Fill out the details for the Certificate Signing Request (csr), and click Create Request.

      An official Certificate Signing Request generates.

      NOTE: The csr file must be forwarded to your certificate vendor of choice.

    • Select Skip this step.

      NOTE: If you generated a self-signed certificate in the previous step, you can select Skip this step to continue with the installation of the self-signed certificate.

  12. Click Next.

    The Install Certificate for HTTPS Closeddialog box opens.

    The dialog for installing the certificate with example information.

    NOTE: This dialog box does not appear if you decided to skip Step 9, Step 11, or both.

  13. Do one of the following:

    • Fill out the details for the Site Certificate HTTPS, and click Install Certificate.

      A message about successful installation appears.

    • Select Skip this step.

  14. Click Next.

    The Installing a New Portal Closeddialog box opens.

    The Installing a New Portal dialog box.

  15. Fill in the following information, and verify the values:

    • Portal name—The default name is diveport. 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:\Program Files\Java\jre1.8.0_121.
    • Path to Apache Tomcat Server—The default path is C:\Program Files\Apache Software Foundation\Tomcat 7.0.

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

  16. Click Next.

    A second Installing a New Portal Closeddialog box opens.

    The dialog box for DiveLine server and port number information.

    NOTE: The server name must be a fully qualified domain name. For example, docs.dimins.com.

  17. Enter the DiveLine server and port (<machine_name>:<port_number>) and the administrator logon information, and click Next.

    The Ready to Install Closeddialog box opens.

    The Ready to Install dialog box.

    NOTE: Take note of the Portal URL. This URL is used to access DiveTab.

  18. Review the information, and click Install.

  19. When the Completing the DivePort <version number> Setup Wizard dialog box opens, click Finish.

    The new DivePort instance is installed.

After you install a DivePort, you can proceed to define the DiveTab connection in Workbench. See Defining a DiveTab Connection and Project.