Installing DiveLine

DiveLine is the Diver server component that authenticates users and provides centralized access to cBase and model data. DiveLine shares processing with various DI clients, such as Workbench, DivePort, ProDiver, NetDiver, and DiveTab. DiveLine accepts connections from clients and communicates with them by means of a proprietary protocol. DiveLine runs in the background as a service and requires a Windows user account that you or the installation wizard creates.

Note that with Diver Server 7.2, DI is building 64-bit encrypted DiveLines only.

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

To install DiveLine, complete the following steps:

  1. Navigate to the DI\Solution\downloads directory.
  2. Double-click the DiveLine-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 ClosedDiveLine 7.2 Setup Wizard dialog box opens.

  4. Review the setup instructions, and click Next.

    CAUTION: If NET 4.7.2 is not installed, the Verify Microsoft .NET 4.7.2 Install page displays.

    1. Click the Install .NET 4.7.2 button.

      The Microsoft .NET Framework window opens.

    2. Select the check box to accept the licensing terms.
    3. Click Install.

      When the installation completes, the Installation is Complete page opens.

    4. Click Finish.

    5. Click Restart Now, to restart your machine.

      IMPORTANT: Choosing to restart later may cause applications depending on .NET to stop working.

    After restarting your machine, return to Step 1 to start the DiveLine installation process again.

    The ClosedInstalled DiveLines page displays.

  5. Select the Install New option. This page lists any existing DiveLine installations, which you can choose to Upgrade, Modify, or Uninstall.
  6. Click Next.

    If Microsoft Edge WebView2 Runtime is not installed, the Verify Microsoft Edge WebView Install page displays.

    1. Click the ClosedInstall Microsoft Edge WebView2 Runtime button to start the installation process.

    2. Click Next when the installation process finishes.

    The ClosedDiveLine Paths page displays.

  7. Accept the default values or select new ones for the following options:

    • DI directory—The default path is C:\DI.
    • DI Solution directory —The default path is C:\DI\Solution.
    • Port number—The default port number is 2130, but it must match the port number used in the license request. Assign unique port numbers for different environments. For example, 2131 for a Test environment.
    • Dataroot directory—The default directory is dl-dataroot. If you previously installed DiveLine or have another instance, you can choose that Dataroot directory. However, sharing dataroots between environments such as test and production is not recommended.
    • DI Projects directory—The default directory is C:\DI\Projects.
  8. Click Next.

    The ClosedDiveLine Service Settings page displays.

  9. The DiveLine Service Settings dialog box is populated with default values (which you can change).

    • Service Name—The default is DI-DiveLine. If you specify a port number other than the default, 2130, the port number is appended to the end of the name. For example, DI-DiveLine-2131.
    • Install directory—The default is diveline. You can change this to give it a meaningful label. For example, specifying a particular DiveLine if more than one is in use.
    • Service Display Name—The default is DI-DiveLine. If you specify a port number other than the default, 2130, the port number is appended to the end of the name. For example, DI-DiveLine-2131.
    • Service Description—Add a service description; recommended when more than one diveline resides on a machine. The description should indicate the purpose of the DiveLine. For example, Test DiveLine.
    • DiveLine Service User—Specifies which user on the machine owns the DiveLine service. Clear the Create a new Windows user check box if you have already identified a Windows user for the DiveLine service. The Windows user must have administrator rights.

      NOTE: A non-blank password for the Windows user is required.

    • User name—The default is divelineuser. If you are not creating a new Windows user, enter the existing user name and password. If you are creating a new user, choose a user name and enter and retype a password for the account.

      This is the user that runs the service in the background. You can either create a new Windows user, divelineuser, on your machine to act as the DiveLine Service user, or use an existing user by clearing the Create a new Windows user check box and entering an existing Windows user name and password.

      NOTE: As of 7.1(9), you can run the DiveLine service as special users LocalService or NetworkService (or the equivalent NTAuthority\LocalService or NTAuthority\NetworkService). No password is required for these users.

      CAUTION: When installing DiveLine as the Local Service user, be aware that changes to the Windows share permissions property can remove Local Service user access to files and folders, resulting in "permission denied" errors in Workbench and ProDiver.

  10. Click Next.

    The ClosedDiveLine Users page displays. You must specify an Administrative user name and password and, optionally, create a test user. Be sure to re-type the password. The administrative user is needed in order to access and make configuration changes to the DiveLine server. A test account is useful for verifying access by a non-administrative user.

    NOTE: If you used a preexisting Dataroot directory (see Step 7), this DiveLine Users dialog box is skipped.

    Creating an administrative user enables you to log in to DiveLine. No specified user results in an inaccessible DiveLine.

    A test user gives you a non-administrative user to test with. To create a test user, select the Create a test user check box, and enter a Test user name, a Test user password, and re-type the password.

  11. Click Next.

    The ClosedDiveLine Certificate page displays.

  12. Do one of the following:

    • If you do not want to create or use an encryption certificate, select Skip this step. This is not recommended.

      NOTE: If you select this option, users see a message similar to This site is insecure when using DiveLine to access data. If you have existing DiveLine certificates, click the ellipsis buttons to locate and select their private key files and certificate key files.

    • If you do not already have an encryption certificate, fill in the following fields to create one:

      • Country code—Enter your two character country code. Click List of Country Codes to display a complete list of country codes.
      • State—Enter your state abbreviation.
      • Location—Enter a city name or other identifier.
      • Organization—Enter the name of your company or organizational name.
      • Server Name—Enter the name of the server (the machine name).
      • Email—Enter an email address.
    • If you already have an encryption certificate (for example, from a previous installation), select your private key and certificate files. These files are located in the DI\Solution\<DiveLine directory>\install-files directory, and are the privatekey.txt and certificate.pem files.
  13. Click Next.

    The ClosedDiveLine License page displays. Browse for and open the license file.

  14. Click Add License.

    The ClosedResult of adding license window opens.

  15. Click OK.

    The window closes.

  16. Click Next.

    The ClosedRequired Software page displays for installing Java 17 or later (if not already installed). This is required to run DIAL (Dimensional Insight Access Language) and DivePort.

    NOTE: If Java already exists on your machine, it appears in the Existing Java Installation box with the Install Java check box cleared. Click Next, and proceed to Step 21.

  17. Click Next.

    The ClosedInstall Java page displays.

  18. Do the following:

    • Accept or change the Java installation directory.
    • Click License Agreement to open the terms of the license.
    • Select the license agreement check box to accept the license terms.
    • Click Install Java, and click OK in the pop-up window to confirm the installation. This might take several minutes.
  19. After you see the Successfully installed Java message in the Installation Result text box, click Next.
  20. When the ClosedReady to Install dialog box opens giving a summary of the pending DiveLine installation, click Install.

  21. When you see the ClosedInstallation Complete confirmation message, click Finish.

  22. Restart your machine.

DiveLine Files

The DiveLine installation wizard adds the following files to the C:\DI\Solution\executables directory:

  • dial.jar—The Dimensional Insight Access Language component that enables you to remotely analyze and report the content of models and cBases.
  • di-broadcast.exe—The DiveLine client that provides scheduled or event-driven delivery of Diver markers using email.
  • dicfg.exe—The DiveLine subcomponent that allows an administrator to configure DiveLine options using a command line tool.
  • di-config.exe—The DiveLine client that allows an administrator to configure DiveLine options using a Windows user interface. It is included to ease the transition from 6.x.
  • dictl.exe—The command line tool for DI-Controller; used to disconnect users accessing a particular model or cBase. It is included to ease the transition from 6.x.
  • disch.exe—The command line tool for DI-Scheduler. It is included to ease the transition from 6.x.
  • di-scheduler.exe—The DiveLine subcomponent that allows an administrator to create, automate, and monitor events related to DI products using a Windows user interface. It is included to ease the transition from 6.x.
  • di-updater.exe—The subcomponent that creates a package for managing downloads to DiveLine.
  • diver.exe—The desktop version of the Diver application. It does not work with cBases.
  • exportinfo.exe—The subcomponent that provides machine identification information for licensing a machine that is not connected to the Internet.
  • prodiver.exe—The desktop analytics client of the Diver Platform.
  • register.exe—The command line tool for license maintenance.

In addition to the above listed executables, the DiveLine installer adds the following Diver 7.2 executables to the C:\DI\Solution\<DiveLine directory>\bin directory:

  • builder.exe—The Diver component that transforms data by summarizing and preprocessing it in order to create classic models.
  • dial.jar—The Dimensional Insight Access Language component that enables you to remotely analyze and report the content of models and cBases.
  • di-diveline.exe—The main component of the DiveLine application server software that servers data to client applications.
  • di-listener.exe—The component of the application server that manages incoming client connections.
  • di-logger.exe—The component of the application server that collects a list of activities performed by the server.
  • di-scheduler-engine.exe—The component of the application server that handles the scheduling of jobs.
  • di-service.exe—The component of the application server that manages services.
  • integ.exe—The Diver Solution extract, transform, and load scripting tool.
  • spectre.exe—The data analysis software that is used to build and query cBases. It powers the DiveLine server software for efficient queries from DI clients against those cBases.