Longview Enterprise Deployment

Hardware and software requirements

Before you begin, review the Hardware and Software Requirements .

This contains information on these main topics:

• Supported client platforms
• Supported languages

For more information, refer to Supported client platforms and Supported languages

Note: Third party components and versions, such as operating systems, browsers etc., no longer in mainstream support by the third-party provider are not supported by Longview as well.

Before you begin

Obtaining the Install files

The following file is required from Longview to install the Longview Components to the client machines:

• Longview Deployment-25.3.zip

The Longview Deployment-25.3.zip contains 2 .msi files:

• Longview Components-25.3.msi
• Longview Add-in for Office-25.3.msi

The Longview Components-25.3.msi is used to install the following:

• Longview Client
• Longview Smart Client
• Longview Report Viewer
• Longview Launcher (Longview Analysis and Reporting, Longview Journal Entries, Longview Workflow, Longview Application Administrator, Longview Server Manager)

The Longview Add-In for Office-25.3.msi is used to install the following:

• Longview Add-In for Office

Set USE_WEB_DEPLOYMENT to FALSE

To use Enterprise Deployment, the USE_WEB_DEPLOYMENT must be set to FALSE.

You can set this parameter to FALSE using either the Server Manager or modifying directly in the lvsrvr.cfg file on the Longview Data Server.

Using Server Manager

1. Launch Longview Server Manger.
2. Right click on your server in the server explorer window.
3. Select Server Configuration.
4. Select Application under Server Configuration.
5. Deselect the Use Web Deployment checkbox.
6. Click OK to save changes.
7. Click OK to the Information dialog "You must restart the server for the changes to take effect."
8. Stop and Start the Data Servers.

Modifying in the lvsrvr.cfg file

1. Stop the Longview Data Servers
2. Open the lvsrvr.cfg file found in the config folder in the Files Custom Root Path directory.
3. Set the USE_WEB_DEPLOYMENT parameter to FALSE.
4. Save the file.
5. Start the Longview Data Servers

Installing Longview using the .msi

For more information on how to use the .msiexec, refer to Microsoft Support.

Single instance setup

If your company does not have multiple instances of Longview or the user is only required to connect to one instance of Longview then the single instance deployment can be used.

If it is required for the user to connect to multiple Longview instances, see the Multiple instance setup section.

Note: The msi install requires Administrator privileges.

1. Extract the Longview Deployment-25.3.zip
2. Open a command line with administrator privileges and navigate to either the Longview Components or Longview Add-In for Office subfolder from the extracted package.
3. Run one of the following commands:
   1. For Longview Components:

   msiexec -lv <logfile> -i "Longview Components-25.3.msi" LVID=<lvid> [TARGETDIR=<installdir>]

   2. For Longview Add-In for Office:

   msiexec -lv <logfile> -i "Longview Add-In forOffice-25.3.msi" LVID=<lvid> [TARGETDIR=<installdir>]

   where:

   logfile is the name of the installation log file.

   lvid is the Longview identifier.

   installdir is optional and is the path where the files will be installed. If this parameter is not set the default location will be C:\Longview.

   Caution: The installdir cannot be set to a system folder, such as C:\Program Files. Doing so may cause our software to not work once installed.

4. The software is installed in a subfolder called <lvid> in the installation directory.
5. If you have installed the Longview Components, you must continue to Installing the Java JDK
6. If you have installed the Longview Add-In for Office, you must launch the first time through the Longview Dashboard or by clicking on the executable located in "<installdir>/Longview Add-In for Office\LongviewAddIn.Office.exe". Once this is completed you only need to launch Excel to see the Longview Add-In for Office.

Multiple instance setup

Since an MSI can only be installed once on a machine, you will need to run a Longview utility to generate a new MSI specific to the Longview Identifier the components will connect to.

1. Extract the Longview Deployment-25.3.zip
2. Open a command line with administrator privileges and navigate to either the Longview Components or Longview Add-In for Office subfolder from the extracted package.
3. Create the instance specific file using the following command:

   LVMSIGenerator.exe <lvid>

   where:

   lvid is the Longview identifier.

4. Install the MSI with the newly generated .msi file using one of the following commands:
   1. For Longview Components:

   msiexec -lv <logfile> -i "Longview Components_<lvid>-25.3.msi" [TARGETDIR=<installdir>]

   2. For Longview Add-In for Office:

   msiexec -lv <logfile> -i "Longview Add-In for Office_<lvid>-25.3.msi" [TARGETDIR=<installdir>]

   where:

   logfile is the name of the installation log file.

   lvid is the Longview identifier.

   installdir is optional and is the path where the files will be installed. If this parameter is not set the default location will be C:\Longview.

   Caution: The installdir cannot be set to a system folder, such as C:\Program Files. Doing so may cause our software to not work once installed.

5. The software is installed in a subfolder called <lvid> in the installation directory.
6. If you have installed the Longview Components, you must continue to Installing the Java JDK
7. If you have installed the Longview Add-In for Office, you must launch the Longview Add-In for the first time either by the Longview Dashboard or by clicking on the Longview Add-In application located in "<installdir>/Longview Add-In for Office\LongviewAddIn.Office.exe". Once this is completed you only need to launch Excel to see the Longview Add-In for office.

Installing the Java JDK

The Longview Components deployment also requires the Java JDK. The Java JDK must be configured before any of these components may be used. You must obtain a supported version of the Java JDK and install using one of the following 2 methods:

Configuring the Java JDK using JDK zip

If the user does not have the JDK installed on their machine the following steps can be used to deploy the required JDK for the Longview Components:

1. Obtain a supported version of the Java JDK in .zip file format.

   Extract the Java JDK to <InstallDir>/<LVID>/Longview Launcher/Software

   where:

   InstallDir is the directory where the Longview Components were installed. If the TargetDir option was not used, then the install directory will be C:/Longview.

   LID is the Longview identifier that was specified when using the .msi isntall.

2. Rename the extracted folder JDK-<Version> found in the <InstallDir>/<LVID>/Longview Launcher/Software to be Java. For example: C:/Longview/LVClose/Longview Launcher/Software/Java

   Caution: Longview requires the JDK files to be in the folder Java without the JDK-<version> subfolder. If you do not rename the version folder to be Java, the Longview Components will not work

Configuring UJavaHome Attribute to find the Java JDK

If the user already has the Java JDK installed on their machine, the following steps can be used to configure Java to work with the Longview Components:

1. Set the Longview User Attribute UJavaHome to the path the JDK was extracted to.

   Note: If the JDK is in the same location for all users then you can set the Longview User Attribute UJavaHome default value to this location.

Upgrading Longview using the .msi

When a new version of Longview software is available, you will need to get the new version of the MSI and perform an upgrade.

Upgrade when single instance setup was used

If the previous installed MSI is a Single instance setup, follow the following steps to upgrade:

1. Extract the Longview Deployment-.zip
2. Open a command line with administrator privileges and navigate to either the Longview Components or Longview Add-In for Office subfolder from the extracted package.
3. Run the MSI for the new .msi file using one of the following commands to upgrade:
   1. For Longview Components

   msiexec -lv <logfile> -i "Longview Components-25.3.msi" LVID=<lvid> [TARGETDIR=<installdir>]

   2. For Longview Add-In for Office:

   msiexec -lv <logfile> -i "Longview Add-In for Office-25.3.msi" LVID=<lvid> [TARGETDIR=<installdir>]

   where:

   logfile is the name of the installation log file.

   lvid is the Longview identifier.

   InstallDir is the directory where the Longview Components were installed. If the TargetDir option was not used, then the install directory will be C:/Longview.

Upgrade when multiple instance setup was used

If the previous installed MSI is a Multiple instance setup, follow the following steps to upgrade:

1. Extract the Longview Deployment-.zip
2. Open a command line with administrator privileges and navigate to either the Longview Components or Longview Add-In for Office subfolder from the extracted package.
3. Create the instance specific file using the following command:

LVMSIGenerator.exe <lvid>

where:

lvid is the Longview identifier.

4. Run the MSI for the newly generated .msi file using one of the following commands to upgrade:
   1. For Longview Components
      

      msiexec -lv <logfile> -i "Longview Components_<lvid>-25.3.msi" [TARGETDIR=<installdir>]

   2. For Longview Add-In for Office:

      msiexec -lv <logfile> -i "Longview Add-In for Office_<lvid>-25.3.msi" [TARGETDIR=<installdir>]

      where:

      logfile is the name of the installation log file.

      lvid is the Longview identifier.

      InstallDir is the directory where the Longview Components were installed. If the TargetDir option was not used, then the install directory will be C:/Longview.

Custom Links

If you want to use custom cards that have custom links to Longview software on the dashboard the following is the syntax to use when using Enterprise Deployment.

Note: Depending on your system configuration, you may need to use https instead of http

Longview Client

Longview Launcher

Longview Launch custom link is used to launch the Longview Application Administrator, Longview Analysis and Reporting, Longview Journal Entries, Longview Server Manager or Longview Workflow Designer.

In the sample link, replace the <LongviewComponentName> with the component you want to launch. The following are valid options:

• AnalysisReporting
• ApplicationAdministrator
• JournalEntries
• ServerManager
• Workflow

Longview Report Viewer

Longview Smart Client

Longview Add-In for Office

Troubleshooting

There are some limitations of the Enterprise Deployment and limited error handling. Below are listed limitations you may run into, to help you troubleshoot.

Multiple instance setup

• To provide the ability to install Longview for multiple Longview instances, we needed to provide a utility to create and generate a unique .msi installer for each LVID (i.e., one per Longview instance; LongviewDev, Longview, LongviewProd, etc..) you need to install for. The .msi that is generated by the utility is not signed, since it is a generated msi from the original signed one. Therefore, when running a generated .msi, the UAC prompt (with unknown publisher) is displayed when it is not Run as Administrator.

  All the files deployed by the installer are signed.

• The install process must be Run as Administrator when running msi in quiet mode (/quiet) on cmd window. When not run as an Administrator, as the UAC prompt cannot be presented, the install will fail due to the lack of Administrator permissions.

Limited error handling in first release

• No error handling for an invalid LVID (Longview Identifier).
• No error handling on TARGETDIR for deployment if it is set to an existing installation.
• If a user tries to launch a component from the Longview Dashboard without the Longview software for the matching LVID (Longview Identifier) being installed to their machine they will get either a blank tab page, or the following popup that will close the tab when they click Open:

  

• If you only install the Longview Add-In for Office and not the Longview Components, nothing will happen if you try to launch the Locks or the Submission tools from Longview Add-In for Office.

Installs, uninstalls and upgrades

• The <installdir> cannot be set to system folders such as C:\Program Files etc. This will result in Longview not working.
• The <installdir> cannot be a mapped drive or a UNC Path.
• When installing using quiet mode (/quiet), if the LVID (Longview Identifier) is not specified, the installation will fail without a proper error message in the Install.log.
• Uninstall currently does not remove all files. Temporary files created by our software (cache, copies of .dlls, etc..) will remain.
• The install process must be Run as Administrator when running msi in quiet mode (/quiet) on cmd window. When not run as an Administrator, as the UAC prompt cannot be presented, the install will fail due to the lack of Administrator permissions.
• The uninstall for the Longview Add-In for Office only removes the "stub" that was installed to handle the launching of the Addin (this was previously the ClickOnce stub)