Prerequisites For Installing Longview
Required installation files
The following files need to be downloaded from Longview Support prior to installing the Longview application.
The following tables include the installation files required:
Core Components
This table includes all required files for installing only core components. If installing Longview Close and Plan or Longview Tax, skip this section.
| Component | Files |
|---|---|
Longview Servers |
Longview Installer-24.4.exe |
Longview Close and Plan
This table includes all required files for installing Longview Close and Plan. If installing Longview Tax skip this section.
| Component | Files |
|---|---|
Longview Servers |
Longview Installer 24.4.exe |
Longview Close and Plan |
Longview Close and Plan-24.4.zip |
Additionally, if you purchased Longview Analytics additional files are required:
| Component | Files |
|---|---|
Longview Close Analytics |
Longview Close Analytics-24.4.zip |
Longview Tax
This table includes all required files for installing Longview Tax.
| Component | Files |
|---|---|
Longview Servers |
Longview Installer-24.4.exe |
Additional files are required depending on which tax components you purchased:
- Longview Tax Analytics files
- Longview Tax Provision files
- Longview Tax Multi-Regional Provision files
- Longview Tax Task Management only files
- Longview Transfer Pricing only files
- Longview Pillar Two only files
Longview Tax Analytics Files
| Component | Files |
|---|---|
Longview Tax Analytics |
Longview Tax Analytics-24.4.zip |
Longview Tax Provision Files
| Component | Files |
|---|---|
Longview Tax Provision |
Longview Tax Provision-24.4.zip |
If you also purchased Longview Tax Global Transparency |
Longview Tax Global Transparency-24.4.zip |
If you also purchased Longview Tax Task Management |
Longview Tax Task Management-24.4.zip |
If you also purchased Longview Tax Planning |
Longview Tax Planning-24.4.zip |
If you also purchased Longview Transfer Pricing |
Longview Transfer Pricing-24.4.zip |
If you also purchased Longview Pillar Two |
Longview Pillar Two-24.4.zip |
Longview Tax Multi-Regional Provision Files
| Component | Files |
|---|---|
Longview Tax Multi-Regional Provision |
Longview Tax Multi-Regional Provision-24.4.zip |
If you also purchased Longview Tax Global Transparency |
Longview Tax Global Transparency-24.4.zip |
If you also purchased Longview Tax Task Management |
Longview Tax Task Management-24.4.zip |
If you also purchased Longview Tax Planning |
Longview Tax Planning-24.4.zip |
If you also purchased Longview Transfer Pricing |
Longview Transfer Pricing-24.4.zip |
If you also purchased Longview Pillar Two |
Longview Pillar Two-24.4.zip |
Longview Tax Task Management Only Files
| Component | Files |
|---|---|
Longview Tax Task Management |
Longview Tax Task Management-24.4.zip |
Longview Transfer Pricing Only Files
| Component | Files |
|---|---|
Longview Transfer Pricing |
Longview Transfer Pricing-24.4.zip |
Longview Pillar Two Only Files
| Component | Files |
|---|---|
Longview Pillar Two |
Longview Pillar Two-24.4.zip |
Optional Components
This table includes all optional files that can be used with any installation.
| Component | Files |
|---|---|
Longview Application Framework (local install) |
Application Framework(x64)-24.4.zip Or Application Framework-24.4.zip |
Longview Data Server Web Service |
Longview Data Server Web Service Setup-24.4.exe |
Longview Grid (SQL Server) |
Grid_Nodes-win(x64)-24.4.zip |
Preparing for a tiered system
If you plan to use a tiered system (your Data Server and database will be on separate host machines), you must perform some additional setup steps on your Data Server to accommodate the connection between the Data Server and the database.
For more information, see:
- Preparing for a tiered system with SQL Server
- Preparing for a tiered system with Oracle
- Preparing for a tiered system with OS authentication
Preparing for a tiered system with SQL Server
On the application server, you must install the SQL Management Studio that matches the version of the DBMS that it will connect to. If you choose not to install the full package, you must download the following required components from the Microsoft website:
- The ODBC Driver 18 for SQL Server
- The SQLCMD.exe - 64-bit executable
Note: You may also be required to add the binary path for this executable to the PATH variable on the application server.
After you install SQL Management Studio or download the required components, you must complete the following steps to enable the BULKINSERT function that the application performs:
- Locate the SQL Server (MSSQLSERVER) service on the database server.
- Set the owner of the service to a domain account.
- Give the owner of the service read/write privileges to the network share on the application server. This network share is created as part of the settings for the RECALC_FILES parameter. For more information, see the RECALC_FILES section in Settings for all systems.
Preparing for a tiered system with Oracle
On the application server, you must install the full Oracle Client - 64-bit installation package for Oracle version 19.3. Ensure you have configured your TNSNAMES.ORA file to point to the Oracle instance you will connect to.
Preparing for a tiered system with OS authentication
If you plan to use OS authentication with a tiered system, extra steps are required in the Active Directory. Make sure the following apply:
- The Longview database owner account can be delegated (this must be the account that owns the Longview Administrative Service on the Application Server)
- The SQL Service Owner is trusted for delegation to any service
- The SQL host computer is also trusted for delegation to any service
- Each instance of SQL Server must be owned by a unique service account
Note: For more information on using a tiered system with OS authentication, contact Longview Support Services.
Preparing for Longview Dashboard
If you are using the Longview Dashboard, the following steps are required:
Note: Potentially weak protocols and cipher suites should be disabled according to your InfoSec policy.
Installing .NET Framework
As a prerequisite for Longview HTTP Proxy, the following .NET Framework must be installed.
| Server | .NET Version |
|---|---|
Server 2016/2019 |
4.8 |
Installing the Web Server (IIS)
As a prerequisite for Longview Dashboard, the Web Server (IIS) must be installed with the following roles services.
| Category | Role |
|---|---|
Common HTTP Features |
Static Content |
Default Document | |
Directory Browsing | |
HTTP Errors | |
HTTP Redirection | |
Application Development |
ASP.NET |
CGI | |
ISAPI Extensions | |
ISAPI Filters | |
Server Side Includes | |
Health and Diagnostics |
HTTP Logging |
Request Monitor | |
Security (Installed) |
Basic Authentication |
Windows Authentication | |
Digest Authentication | |
Request Filtering | |
Performance |
Static Content Compression |
Management Tools |
IIS Management Console |
IIS Management Scripts and Tools |
If you are using REST APIs or the HTML5 Dashboard the following features must not be installed as they interfere with DELETE and PUT requests.
| Category | Role |
|---|---|
Common HTTP Features |
WebDAV Publishing |
Configuring program components on IIS
As a prerequisite for Longview Dashboard, the following program components on IIS must be configured:
- Configuring authorizations
- Configuring handler mappings
- Configuring component restrictions
- Adding a handler mapping (IPC only)
- Configuring a redirection for the Longview sign-on URL
- Determining the URL for HTTP Proxy Server (if using HTTP Proxy Server)
- Configuring application request routing extension (if using HTTP Proxy Server)
- Configuring URL rewrite (if using HTTP Proxy Server)
Configuring authorizations
- In IIS, select your server in the Connections pane.
- Double-click Authentication.
- Select Anonymous Authentication in the list and click Disable in the Actions pane.
- Select Windows Authentication in the list and click Enable in the Actions pane.
Configuring handler mappings
- In IIS, select your server in the Connections pane.
- Double-click Handler Mappings.
- Do one of the following:
- If you are using IPC/CGI, right-click CGI-exe and select Edit Feature Permissions.
- If you are using TCP/ISAPI, right-click ISAPI-dll and select Edit Feature Permissions.
- Select Execute to enable CGI-exe or ISAPI-dll and click OK.
Configuring component restrictions
- In IIS, select your server in the Connections pane.
- Double-click ISAPI and CGI Restrictions.
- Select Edit Feature Settings in the Actions pane
- Do one of the following:
- For IPC, select Allow unspecified CGI modules and click OK.
- For TCP, select Allow unspecified ISAPI modules and click OK.
Adding a handler mapping (IPC Only)
Note: This section applies to IPC Only
- In IIS, select your server in the Connections pane.
- Double-click Handler Mappings.
- Click Add Module Mapping in the Actions pane.
- Complete the following fields:
- Request path: Enter “*.cgi”.
- Module: Select CgiModule from the drop-down list.
- Executable (Optional): Leave this field empty.
- Name: Enter “LONGVIEW CGI”.
- Click Request Restrictions.
- Click the Access tab.
- Select Execute and click OK.
- Restart IIS.
Determining the URL for Longview HTTP Proxy server
If you are using Longview HTTP Proxy server there are several configuration properties that must be specified with similar values related to the URL. The rule for specifying these values is that the end portion of the URL must match.
For example:
| Component | Parameter | URL Example |
|---|---|---|
HTTP Proxy Server |
HttpProxyServerListenerPortURL |
http://<serverName>:8080/clientproxy/ |
Data Server |
CLIENT_HTTP_PROXY |
https://<serverName>/clientproxy/ |
IIS URL Rewrite |
Pattern (Client rewrite) |
clientproxy/.* |
IIS URL Rewrite |
Rewrite URL (Client rewrite) |
http://<serverName>:8080/clientproxy/{R: 1} |
HTTP Proxy Server |
HttpProxyServerAdminPortURL |
http://<serverName>:8080/adminproxy/ |
Data Server |
ADMIN_HTTP_PROXY |
https://<serverName>/adminproxy/ |
IIS URL Rewrite |
Pattern (Admin rewrite) |
adminproxy/.* |
IIS URL Rewrite |
Rewrite URL (Admin rewrite) |
http://<serverName>:8080/adminproxy/{R: 1} |
Data Server |
WEB_SERVER_BRIDGE |
"/cgi-bin/<LongviewIdentifier>/lvweb.cgi" |
IIS URL Rewrite |
Pattern (Web Bridge Rewrite) |
cgi-bin/<LongviewIdentifier>/.* |
IIS URL Rewrite |
Rewrite URL (Web Bridge rewrite) |
http://<serverName>/{R: 0} |
Configuring the application request routing extension for IIS
If you are using the Longview HTTP Proxy Server, you must install and configure Microsoft’s Application Request Routing extension for IIS.
To configure the application request routing extension for IIS:
- On the web server, install Microsoft’s Application Request Routing extension for IIS. You can download this extension from: http://www.iis.net/downloads/microsoft/application-request-routing
- On the web server, open Internet Information Services (IIS) Manager.
- In the Connections pane, navigate to, and select the appropriate web server.
- In the content pane, double-click Application Request Routing Cache.
- In the Actions pane, right-click Server Proxy Settings.
- In the content pane, select Enable proxy.
- In the Actions pane, click Apply.
Preparing for Longview Data Server Web Services
If you plan to use Data Server Web Services to enable users to work with SOAP web services, you must perform some additional setup steps wherever the Web Services will be installed.
The following pre-requisites must be met:
- A supported version of the Java JDK must be installed.
- The JAVA_HOME environment variable must be set.
- If you have the JRE_HOME environment variable set, it must also be set to the same value as the JAVA_HOME environment variable.
Note: If you have multiple versions of Java installed, the latest version of the JDK must be first in the Path environment variable. For example, if you have JDK 12 and JRE 1.8 installed, JDK 12 must be before JRE 1.8 in the variable.