Installing Longview Servers

The Longview Platform Installer allows you to install all the platform components in a step-by-step process or using a silent install approach.

This section contains information on these main topics:

• "Using the step-by-step process to install Longview Servers"
• "Using the silent option to install Longview Servers"
• Installing the Java JDK
• Updating the Longview Data Server configuration file
• Configuring database OS authentication
• Configuring a redirection for the Longview sign-on URL
• Configuring Single Sign-On (Web) for on-premises servers
• Configuring Additional Post-installation components

Note: If you are installing the Longview Web Bridge on a different machine than the data servers, you will need to run the Longview Installer separately for Database and Executables, and Web on each target machine.

Using the step-by-step process to install Longview Servers

To install Longview Servers using the step-by-step process:

1. Double-click the Longview Installer-23.4.exe received from Longview. The Longview Setup wizard opens. Click Next.

   1. You can also open an administrator command prompt and execute the installer with the /SAVEINF=<filename> parameter to save the choices you make during install to a configuration file that can be used with silent install.

      Note: Depending on your system, a User Account Control dialog may prompt you to allow the installer to make changes to the computer. Click Yes

2. The Licensing Agreement for Longview software page opens.
   1. Read through the agreement and check “I accept the terms of the license agreement” to proceed.
   2. Click Next.
3. The Specify Installation Details page opens.
   1. Enter the Instance Name.
   2. Select Create New Instance.
   3. Check French under additional languages if you want French application components installed.
   4. Click Next.
4. The Select Destination Location page opens.
   1. By default, new server instances install in the C:\Longview directory. To select an alternate destination folder, follow these steps.
   1. Click Browse. The Browse for Folder dialog opens.
   2. Navigate to the destination folder in the tree pane, and select it, or click Make New Folder to create a new folder.

      Caution: Folders in the destination path cannot contain spaces.

   3. Click OK.
   4. Click Next. If the folder selected already exists, you will be asked to confirm the selected folder. Click Yes to continue or No to return to Step 4.
5. The Select Components page opens.
   1. Select the components to install.

      Component	Notes
      Executables	The data server executable files and solutions framework
      Database	The Longview database
      Web	The Longview web bridge, click-once applications and help files Note: Do not select Web with any other components if you are using the TCP communication protocol as Web must be installed separately in this case.
      Proxy	The Longview HTTP Proxy Server

   2. Click Next. Depending on the components selected the remaining steps will vary.
6. Executables / Database selected: The Select RDBMS Type page opens.
   1. Select SQL Server or Oracle
   2. Click Next.
7. Database selected: The Configure Database account page opens.
1. Complete these fields:
2. Select Windows Authentication, or
3. Select Database Authentication.
   1. Enter the Username
   2. Enter the Password.
4. Click Next.
8. Executables / Database selected: The Configure Data Server page appears.

   Note: The Database Server Name, Database Name, DBO User Name, or DBO Password cannot contain the pound sign ( # ), percent sign ( % ), angle brackets ( < > ), forward slash ( / ), colon ( : ), question mark ( ? ), asterisk ( * ), double quotation mark ( “ ) or pipe( | )

9. Database selected: The Configure the User Reporting Component page opens.
   1. Complete these fields:

      Field	Description
      Use the DBO user	To increase security, Longview recommends that you create a new user as the View User and do not use the DBO. Select this option to populate the view username and password with the DBO username and password that you specified in the previous dialog. Note: If you specify the DBO user as the view user, the DBO user can query all tables as well as views.
      View User Name	Specify the username for the view user.
      View User Password	Specify the password for the view user.
      View User Password Confirm	Confirm the password to use for the View User.

   2. Click Next.
10. Database selected: The Database file locations page opens.

    Note:

    • The defaults are based on the RDBMS configuration.
    • If Cloud Provider Managed was selected this page will not appear.
    1. SQL SERVER: Complete these fields:

       Field	Description
       Primary File	Specify the name and location of the system database file.
       KLX_BASE_DAT File	Specify the name and location of the base (leaf) data file.
       KLX_DERIVED_DAT File	Specify the name and location of the derived (calculated) data file.
       Log File	Specify the name and location of the database log file.

    2. ORACLE: Complete these fields:

       Field	Description
       Tablespace Directory	Enter or select the directory for the table space. The default for this field is read from the Oracle RDBMS configuration.
       Tablespace Size	The initial tablespace size (in megabytes). The default value for this field is 1000.

    3. Click Next.
11. Database selected: The Configure Dimensions page opens.
    1. Complete these fields:

       Field	Description
       Number of Base Dimensions	Enter the number of base dimensions. For Longview Close this must be at least 6. For Longview Tax this must be set to 8. For Longview Transfer Pricing this must be set to 8.
       Number of Extra Dimensions	Enter the number of schedule dimensions. The default of 3 is generally used for all implementations
       Number of Partitions	Enter the number of partitions the data table will be divided into. If you do not know, leave it as 1 as it can be adjusted later.

    2. Click Next.
12. Database selected: The Configure Dimensions page opens.
    1. For Longview Close, enter the following for the first four dimensions:
       1. ACCOUNTS
       2. TIMEPERIODS
       3. ENTITIES
       4. DATAVIEWS
    2. For Longview Close, enter the following for the last two dimensions:
       1. SCENARIOS
       2. CURRENCIES
       3. SCENARIOS
       4. CURRENCIES
    3. For Longview Tax, enter the following for the dimensions:
       1. ACCOUNTS
       2. TIMEPER
       3. ENTITIES
       4. DETAILS
       5. CURRENCY
       6. SEGMENTS
       7. ELEMENTS
       8. CONTROLS
13. Executables selected: The Data Server Configuration page opens.
    1. Complete these fields:

       Field	Description
       Identifier	Enter the identifier for Longview data server. The default for this field is Longview.
       Administrator Port	Enter the port for administrator connections to use. The default for this field is 27999.
       Listener Port	Enter the port for client connections to use. This is normally one larger than the Administrator Port. The default for this field is 28000.
       Web Listener Port	Enter the port for web connections to use. This is normally one larger than the Listener Port. The default for this field is 28001.
       Application Server	Enter the name of the Application Server. This defaults to the machine on which the installer is being executed.
       ODBC Data Source	SQL Server: Enter the name of the ODBC Data Source. This is normally the same as the Identifier.

    2. Click Next.
14. Executables selected: The Data Server Config File page opens.
    1. Enter the name of the JDK file that will be used. This file needs to be placed in the software folder of the data server working directory.

       Field	Description
       Java File Name	Specify the Name of the JRE file that you will place in the SOFTWARE folder when Installing the Java JDK.
       Custom Files Path	Specify the location of where custom files and customer specific files will be stored. For example: applications, config, export, logs,templates, web, and workflow.
       Client HTTP Proxy	If you are using HTTP proxy specify the secure listener port URL for your HTTP Proxy Server. See Determining the URL for Longview HTTP Proxy server for details.
       Admin HTTP Proxy	If you are using HTTP proxy specify the secure admin port URL for your HTTP Proxy Server. See Determining the URL for Longview HTTP Proxy server for details.
       Local Admin Group	If you want to start and stop your Longview Servers using a Windows local group, then specify the name of a local group that will be created during install or select an existing group from the drop list. The user currently signed into the server running the install will be added to this group. Note: Local Admin Group will not work with a Windows default local group.

15. Web selected: The Web Server Configuration page opens.
    1. Complete these fields:

       Field	Description
       Web Type	Specify the web communication protocol. IPC – for inter-process communication. This can only be used if the web server and data server are on the same machine. TCP – for transmission control protocol. This can only be selected if the install component selected is only Web. This must be used if the web server is on a different machine than the data server.
       Destination Folder	Specify the location to install the web bridge and click once client files. Default is c:\inetpub\wwwroot\cgi-bin\<Instance Name> (web only) or <Identifier> (executables and web)
       Web Server Name	Enter the name of the web server. This field defaults to the machine on which the installer is being executed.

    2. Click Next.
16. Proxy selected: The Proxy Server Configuration page opens.
    1. Complete these fields:

       Field	Description
       Local Folder	Specify the location to install the HTTP Proxy server files. Default is <Destination Location>\ProxyServers\<Instance Name> (proxy only) or <Identifier> (executables and proxy)
       Data Server Host	Specify the Data Server host for the HTTP proxy. This value matches the APPLICATION_SERVER parameter in the data server configuration file.
       Data Server Listener Port	Specify the Data Server Listener port. This value matches the LISTENER_PORT parameter in the data server configuration file.
       Data Server Administrator Port	Specify the Data Server Admin port. This value matches the administrator port specified during the installation of the Data Server.
       Proxy Client URL	Specify the listener port URL for the HTTP Proxy Server. The last part of the URL must match the last part of the CLIENT_HTTP_PROXY parameter in the Data Server configuration file. See Determining the URL for Longview HTTP Proxy server for details.
       Proxy Administrator URL	Specify the administrator port URL for the HTTP Proxy Server. The last part of the URL must match the last part of the ADMIN_HTTP_PROXY parameter in the Data Server configuration file. See Determining the URL for Longview HTTP Proxy server for details.
       Proxy Service Name	Enter the name of the Longview Proxy service. The default for this field is LongviewProxy.

    2. Click Next.
17. The Ready to Install page opens.
    1. Confirm the information in the summary.
    2. Click Install.
18. Database selected: A prompt will appear to review repository scripts before proceeding. If you have any changes to make edit the files in the DataServerRepositories\<Instance> folder.

    Note: If you are installing Longview Close you will need to modify the file SCHEMA_LV_DATASERVER.sql before clicking OK.
    Change: INSERT INTO [dbo].[KLX_ATTR_DEFS] VALUES(0, 6, 'SGPCurrencyDimension', 5, 0.000000, 'CURRENCY' , 'WR' );, to make CURRENCY match the name of your currencies dimension and save the file.

    1. Click OK.
19. The Completing Longview Setup page opens.
    1. Optionally, check View install log file
    2. Database selected: Optionally, check View database log file
    3. Click Finish.

Using the silent option to install Longview Servers

To install Longview Servers using the silent option:

1. Create an install configuration file
   • See Sample install configuration file for SQL Server for SQL Server
   • See Sample install configuration file for Oracle for Oracle

   See Appendix B: The Installation Configuration File for details on the configuration parameters

2. Open an administrator command prompt
3. Execute the Longview Installer-23.4.exe with the /LOADINF=<config.ini>
   1. Specify /silent or /verysilent
      1. /silent will display installation progress
      2. /verysilent will run installation completely in the background
   2. Optionally specify /SAVEINF=<SavedFileName.ini> to save a resolved version of this configuration file. The saved configuration file will contain actual values for any parameters that were set to (Default) in the original configuration file.

Note: If you are installing Longview Close you will need to update the default value for the SGPCurrencyDimension attribute after the installation is complete. You can do this with the following statement:
Update [dbo].[KLX_ATTR_DEFS] set ATTR_STR = ' CURRENCY '
where CLASS_ID = 0 and ATTR_ID = 6;, to make CURRENCY match the name of your currencies dimension.

Sample install configuration file for SQL Server

[Setup]

Lang=English

Dir=C:\Longview

Group=(Default)

NoIcons=0

SetupType=full

Components=executables,database,web,proxy

Tasks=

[Instance]

InstanceName=(Default)

InstallType=New

InstallLanguages=en,fr

[Data Server]

LongviewID=(Default)

DataServerHost=(Default)

DataServerAdminPort=(Default)

DataServerListenerPort=(Default)

DataServerWebListenerPort=(Default)

DataServerDataSource=(Default)

ApplicationServer=(Default)

[Data Server Configuration]

DataServerConfigFile=

JAVA_FILENAME=openjdk-20_windows-x64_bin.zip
FILES_CUSTOM_ROOT_PATH=(Default)

CLIENT_HTTP_PROXY=https://localhost/client

ADMIN_HTTP_PROXY=https://localhost/admin

[Database]

BaseDimensions=(Default)

ScheduleDimensions=(Default)

Partitions=(Default)

DimensionNames=(Default)

DimensionDescriptions=(Default)
FrenchDimensionDescriptions=(Default)

SQLServerUseWindowsAuth=Yes

SQLServerUser=system

SQLServerPassword=

DBOUser=lvdbo

DBOPassword=Longview7

DatabaseViewUseDBOAuth=No

DatabaseViewUser=lvviewuser

DatabaseViewPassword=Longview7

DBMS=SQL Server

SQLServerInstanceName=(Default)

DatabaseName=(Default)

OnDatabaseExists=Terminate

ContainedDatabase=No
CloudProviderManaged=No

RepoPrimaryFile=(Default)

RepoBaseFile=(Default)

RepoDerivedFile=(Default)

RepoLogFile=(Default)

[Web]

WebType=IPC

WebServerHost=(Default)

WebDirectory=(Default)

[Longview HTTP-RPC Proxy Server]

ProxyDirectory=(Default)

ProxyClientURL=https://localhost:8080/client/

ProxyAdminURL=https://localhost:8080/admin/

ProxyServiceName=(Default)

Sample install configuration file for Oracle

[Setup]

Lang=English

Dir=C:\Longview

Group=(Default)

NoIcons=0

SetupType=full

Components=executables,database,web,proxy

Tasks=

[Instance]

InstanceName=(Default)

InstallType=New

InstallLanguages=en,fr

[Data Server]

LongviewID=(Default)

DataServerHost=(Default)

DataServerAdminPort=(Default)

DataServerListenerPort=(Default)

DataServerWebListenerPort=(Default)

DataServerDataSource=(Default)

ApplicationServer=(Default)

[Data Server Configuration]

DataServerConfigFile=

JAVA_FILENAME=openjdk-20_windows-x64_bin.zip

FILES_CUSTOM_ROOT_PATH=(Default)

CLIENT_HTTP_PROXY=https://localhost/client

ADMIN_HTTP_PROXY=https://localhost/admin

[Database]

BaseDimensions=(Default)

ScheduleDimensions=(Default)

Partitions=(Default)

DatabaseServer=(Default)

DimensionNames=(Default)

DimensionDescriptions=(Default)

FrenchDimensionDescriptions=(Default)

OracleUser=system

OraclePassword=

DBOUser=lvdbo

DBOPassword=Longview7

DatabaseViewUseDBOAuth=No

DatabaseViewUser=lvviewuser

DatabaseViewPassword=Longview7

DBMS=Oracle

OracleServiceName=orclpdb

TablespaceName=(Default)

TablespaceDirectory=(Default)

TablespaceSize=1000

OnTablespaceExists=Terminate

OnDatabaseExists=Terminate

[Web]

WebType=IPC

WebServerHost=(Default)

WebDirectory=(Default)

[Longview HTTP-RPC Proxy Server]

ProxyDirectory=(Default)

ProxyClientURL=https://localhost:8080/client/

ProxyAdminURL=https://localhost:8080/admin/

ProxyServiceName=(Default)

Installing the Java JDK

Some Longview components require 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 place it in the appropriate folder of the Longview Data Servers.

To configure the Java JDK:

1. Obtain a supported version of the Java JDK in .zip file format.
   1. This should be the file you specified for the JAVA_FILENAME option during install.
2. Copy the Java JDK zip file to the \software folder of the Longview Data Servers working directory.

Updating the Longview Data Server configuration file

Before you set up program components, you must modify certain settings in the Longview Data Server configuration file.

This chapter contains the following sections:

1. Settings for all systems
2. Settings for Longview Tax and Longview Transfer Pricing
3. Settings for Longview Close

To modify the Longview Data Server configuration file:

1. In the …\<FilesCustomRootPath>\<LongviewIdentifier>\config directory, right-click the lvsrvr.cfg file, and open it in your preferred text editor.
2. Set the following parameters to the suggested values as listed below.
3. Once the changes have been made, save, and close the lvsrvr.cfg file.
4. If the Longview Servers are already running, stop and restart them.

Settings for all systems

Caution: File locations listed are automatically created when unpacking your zip files for the components. After saving the lvsrvr.cfg file do not start the servers until AFTER the component files are extracted or create them manually.

Settings for Longview Tax and Longview Transfer Pricing

Settings for Longview Close and Plan

Configuring database OS authentication

If your company prefers to use an OS-authenticated Database Owner, you can configure OS authentication.

When you are using an OS-authenticated Database Owner, the following apply:

• You must set up an OS-authenticated Database Owner set up for your SQL or Oracle database before you configure OS authentication.
• All Longview tables, indexes, and procedures must be owned by the user who is signed in.

To configure OS authentication:

1. Stop your Longview Data Server.
2. Stop the Longview_LID service.
3. Right-click the Longview_LID service, and click Properties.
4. Click the Log On tab.
5. Select This Account, and then type the name of the OS authenticated user.
6. For Password, type the password for the OS authenticated user.
7. Start the Longview_LID service.
8. Navigate to your server machine Data Server working directory. For example, E:\Longview\DataServers\LongviewDEV.
9. If you haven’t already done so, copy the existing lvsrvr.cfg file, and save it with a new name.
10. Open the lvsrvr.cfg file in your preferred text editor.
11. In the General System Parameters section, modify the following parameters as follows:

    Parameter	Value
    DATABASE_DBO	system
    DATABASE_PWD

12. Save and close the lvsrvr.cfg file.
13. Start your Longview Data Server.
14. In Longview Application Administrator, create a new user with the ID of the Windows-authenticated user that you specified n step 5. For more information on creating users, see the Longview Application Administrator’s Guide.
15. Grant this user authorization to start and stop the server.
16. If you want your Start.bat file to start the servers, complete the following steps:
    1. In your server machine Data Server working directory, right-click the Start.bat file, and open it in your preferred text editor.
    2. Update the file to use system for the User name. For example, lvmgrl "bind localhost 3548" "user system" "start"
    3. Save the file.
    4. Repeat step a to step c for the Stop.bat file.
17. Update your ODBC Driver to use integrated Windows authentication.

Configuring a redirection for the Longview sign-on URL

To provide your users with a simple URL to sign on to Longview Dashboard, Longview suggests that you create a redirection. Once you have configured a redirection, users can access the sign on page from http://<servername>/<LID> instead of having to use the full URL. <LID> is the Longview Identifier, which was defined during Longview installation.

1. In File Explorer, navigate to the root directory (typically C:\Inetpub\wwwroot), and create a new directory with the same name as the Longview Identifier (LID), as specified by the SERVER_NAME parameter in the lvsrvr.cfg file.
2. In Internet Information Services (IIS) Manager, select the new directory located under Default Web Site.
3. Double-click HTTP Redirect. The HTTP Redirect page opens in the content pane.
4. Select Redirect requests to this destination and the appropriate URL into the field.

   • For IPC, enter:

     /cgi-bin/<LID>/lvweb.cgi?LongviewIdentifier=<LID>

     &LongviewAction=GetSignon

     &LongviewLangCode=EN

     &LongviewClientID=<LID>

     &LongviewAuthMode=<AuthMode>

   • For TCP, enter:

     /cgi-bin/<LID>/ks_iweb.dll?LongviewIdentifier=<LID>

     &LongviewAction=GetSignon

     &LongviewLangCode=EN

     &LongviewClientID=<LID>

     &LongviewAuthMode=<AuthMode>

     Where

         <LID> is the Longview Identifier for your system.

     <AuthMode> is optional and is the default authentication method. Specify WinAuth for Windows Authentication, LVAuth for Longview authentication, or 3rdAuth for third-party web authentication.

5. Click Apply in the Actions pane.
6. Restart IIS.
7. To test the configuration, open a supported browser, and navigate to http://<ServerHost>/<LID>. The Longview sign on page should appear.

Configuring Single Sign-On (Web) for on-premises servers:

Single Sign-On (Web) can be configured with on-premises servers using customer specific security software.

Note: USE_THIRD-PARTY_AUTH must be set to TRUE in the data server configuration file

To configure SSO:

1. Locate the .cgi or the .dll file serving as the communication bridge between the Web Server and the Data Server.
2. Create a new copy of the communication file using the same name and extension and append “_SSO” to the end of the file name. For example, if the communication bridge file was bridge.dll, name the new copy bridge_SSO.dll.
3. In the Sign On URL, locate the .cgi or the .dll communication file name and append “_SSO” to the end of the file name. For example, if the Sign on URL is http://www.LongviewTest.com/bridge.dll/signon, change it to http://www.LongviewTest.com/bridge_SSO.dll/signon.
4. In the Sign On URL, you can optionally add the web variable LongviewAuthOptions and assign it a value to specify the authentication options to display on the Parameter Value Sign On page. For more information, see “Understanding Web variables” in the Longview Dashboard Guide.
5. Configure your security software that protects this URL to inject an HTTP header that matches the THIRD-PARTY_HTTP_VARIABLE parameter value (default is LONGVIEW_SSO_USER) in the lvsrvr.cfg file.
6. To verify the configuration, access the correct Sign On page by connecting to the modified URL.

Configuring Additional Post-installation components

Depending on your installation and whether you are using the Longview HTTP Proxy server and/or TCP web protocol there may be additional post-installation configuration steps.

Configuring Longview Web Bridge for ISAPI (TCP Communication Protocol)

If you are using ISAPI with TCP, you must perform additional configuration steps.

To configure for TCP communication protocol:

1. Navigate to the IIS root directory (typically C:\Inetpub\wwwroot) and open the folder cgi-bin\<LongviewIdentifier>.
2. Open the lvweb.xml file in your preferred text editor.
3. Edit the following parameters in the lvweb.xml file:

   Parameter	Description
   KOServer	Specify the name of the Longview application server where the Data Server component exists.
   KOPort	Specify the web listener port used by the Longview Data Server on the application server. Change the 9000 value to match the port setting assigned to the WEB_LISTENER_PORT parameter in the lvsrvr.cfg file.
   KOPoolSize	Specifies the number of threads to use with Web communications. Leave this value at 5.

4. Save and close the lvweb.xml file.
5. Open the Longview Data Server configuration file (lvsrvr.cfg), found in the working directory of the data server installation.
1. Set the parameter WEB_SERVER to the name of the machine the web bridge is installed on
2. Set the parameter WEB_AGENT_PROTOCOL to TCP
3. Set the parameter WEB_SERVER_BRIDGE to /cgi-bin/<LongviewIdentifier>/ks_iweb.dll
6. Save and close the lvsrvr.cfg file.
7. The Longview Data Server needs to be restarted for this change to take effect.

Configuring IIS URL rewrite for HTTP proxy connections

If you are using Longview HTTP Proxy Server, you must configure IIS URL rewrite, which is responsible for sending requests to Longview HTTP Proxy Server.

To configure the IIS URL rewrite:

1. On the web server, install Microsoft’s URL rewrite extension for IIS. You can download this extension from: http://www.iis.net/download/URLRewrite
2. On the web server, open Internet Information Services (IIS) Manager.
3. Navigate to, and select, the appropriate web site.
4. In the content pane, double-click URL Rewrite.
5. In the Action pane, click Add Rule. The Add Rule(s) dialog opens.
6. In the Inbound Rules category, double-click Blank rule.
7. Specify a Name for the new rule.

   Note: Longview recommends that you prepend your inbound rule names with the Longview Identifier for the system.

8. Add a rule that rewrites client requests to the Longview HTTP Proxy Server by completing these fields:

   Field	Description
   Pattern	Specify the string to match. This string must match the end portion of the HttpProxyServerListenerPortURL value in the HTTP Proxy Server configuration.
   Rewrite URL	Specify the rewrite URL for the rule. This string should match the HttpProxyServerListenerPortURL appended with /{R:1}.
   Stop processing of subsequent rules	Select this option.

9. Click Apply.
10. Click back to Rules.
11. In the Action pane, click Add Rule. The Add Rule(s) dialog opens.
12. In the Inbound Rules category, double-click Blank rule.
13. Specify a Name for the new rule.

    Note: Longview recommends that you prepend your inbound rule names with the Longview Identifier for the system.

14. Add a rule that rewrites admin requests to the Longview HTTP Proxy Server by completing these fields:

    Field	Description
    Pattern	Specify the string to match. This string must match the end portion of the HttpProxyServerAdminPortURL value in the HTTP Proxy Server configuration.
    Rewrite URL	Specify the rewrite URL for the rule. This string should match the HttpProxyServerAdminPortURL appended with /{R:1}.
    Stop processing of subsequent rules	Select this option.

15. Click Apply.
16. Click back to Rules.
17. In the Action pane, click Add Rule. The Add Rule(s) dialog opens.
18. In the Inbound Rules category, double-click Blank rule.
19. Specify a Name for the new rule.

    Note: Longview recommends that you prepend your inbound rule names with the Longview Identifier for the system.

20. Add a rule that rewrites requests to the Longview Web Bridge.

    Field	Description
    Pattern	Specify the string to match. This string must match the path specified by WEB_SERVER_BRIDGE
    Rewrite URL	Specify the rewrite URL for the rule. This string should match the HttpProxyServerAdminPortURL appended with /{R:1}.

21. Click Apply.

Additional configuration for HTTP Proxy Server

The Longview HTTP Proxy Server is installed with a default configuration.

To modify the configuration for Longview HTTP Proxy Server:

1. Open the configuration file (Longview.HttpProxyServer.exe.config) in your preferred text editor.
2. Specify the value for each element under appSettings:
   

   Key	Value
   Logging	Specify whether to use logging for the HTTP Proxy Server. You can specify one of the following values: TRUE—Turns on logging for the HTTP Proxy Server. FALSE—Turns off logging for the HTTP Proxy Server.
   LogMaxSize	If logging is set to TRUE, specific the maximum log file size in kilobytes. The log file will be archived each time it reaches or this size.
   MaxPollingInterval	This parameter applies to admin port requests for Longview Application Administrator and Longview Server Manager. Specify the maximum wait time, in seconds, before connected client’s poll for the status of the original request. Longview recommends using an integer between 1 and 60.
   LogFileName	Specify the name for the log file. By default, this log file is saved to the directory containing the Longview.HttpProxyServer.exe.config file.

3. Save the file.
4. Open the Services manager and right-click on the new service (Longview_<ServiceName>).
5. Click Restart to have the changes take effect.