Chapter 4
Configuring on Windows

[p]This chapter contains the installation and configuration instructions for Lasso Professional Server on Microsoft Windows. It also contains information on Lasso Professional Server components and how they can be manually installed or modified. [/p]

• System Requirements lists the minimum system requirements for Lasso Professional Server.
• Web Browser Requirements lists the Web browser requirements for administering Lasso Professional Server.
• Installation Instructions includes step-by-step instructions for installing and initializing Lasso Professional Server, and establishing a basic setup.
• Running Lasso Professional Server describes how to start and stop Lasso Service, and how to check if it is running properly.
• Extended Configuration describes how to manually configure IIS for Lasso Professional Server, and how to set up a Lasso Professional Server distributed architecture.
• Installation Contents lists every file installed with Lasso Professional Server.
• Uninstalling Lasso Professional Server includes step-by-step instructions for removing Lasso Professional Server from your system.

System Requirements

[p]Lasso Professional Server will run on systems which meet the following minimum requirements. Although Lasso Professional Server may run on machines which do not meet these requirements, those installations will not be supported. [/p]

• 300 MHz or higher Pentium-compatible CPU.
• 512 MB of RAM. More recommended. (Requires an additional 64 MB of available RAM for each additional site. See the Setting Up Sites chapter for more information.)
• Windows XP Professional, Windows 2000 family (Professional, Server and Advanced Server editions), or Windows Server 2003 family (Web, Standard, Enterprise and Datacenter editions).
• Microsoft Internet Information Services (IIS) 5 or 6 (included with the versions of Windows listed above), or Apache 2.
• Java Virtual Machine compatible with Sun’s JRE 1.4 (Java 2). This is required for the use of LJAPI modules, JDBC data sources, and all Lasso tags which are dependent upon Java. For details on which Lasso tags are dependent upon Java, see the Lasso 8 Reference. For more information on LJAPI, see the Lasso 8.5 Language Guide.

[note][b]Note: [/b]ImageMagick is automatically installed with Lasso Professional 8.5.2 and higher. [/note]

Web Browser Requirements

[p]This section describes the basic Web browser requirements needed to successfully set up and administer Lasso Professional Server. [/p]

• Microsoft Internet Explorer 5.0 or higher, FireFox, or compatible browser.
• Javascript enabled.
• Cookies enabled.
• Cascading Style Sheets enabled.

[p]If these criteria are not met, then a browser check dialog box will be shown when trying to access Site Administration. You may proceed into the interface without meeting all these criteria, however some elements may not work properly. It is highly recommended that a browser that meets the listed requirements be used. [/p]

Installation Instructions

[p]This section discusses installation procedures for Lasso Professional Server, and initializing Server Administration for the first run. This section will introduce the following: [/p]

• Installing Java describes installing the Java components necessary for Lasso Professional Server Java-based features to function properly.
• Installing Lasso Professional Server describes how to install Lasso Professional Server using the auto-installation program.
• Initialization describes the initialization of Lasso Professional Server for running the first time.

[note][b]Important: [/b]Instructions for upgrading from Lasso Professional 5, 6, or 7 are included in the Upgrading chapter in this section. [/note]

Installing Java

[p]This section discusses installing Sun’s Java Runtime Environment (JRE) 6. This installation is required to successfully use the Java-based features available in Lasso Professional Server. These include LJAPI modules, JDBC data source connectivity, and Lasso tags which are dependent upon Java. For details on which Lasso tags are dependent upon Java, see the Lasso 8.5 Reference. It is unnecessary to install Java if these features will not be used. [/p]

To install JRE 6:

1. Download Sun’s JRE installer at the following address:

[pre]http://java.sun.com/javase/downloads/index.jsp [/pre]

2. Double-click the JRE installer application, and then follow the instructions to install the JRE.

3. Restart your system for the changes to take effect.

[p]The Java components needed to run the Java-based features in Lasso Professional Server are now installed. The Java-based features of Lasso Professional Server can be set up, enabled, and tested within Site Administration. See the Setting Site Preferences chapter Java section for more information. [/p]

Installing Lasso Professional Server

[p]Use the Lasso Professional Server Installer to ensure that all of the Lasso Professional Server files are installed in the proper location. The following procedure assumes IIS will be used as the Web server. [/p]

[note][b]Upgrading [/b][b]Note[/b]: A previous installation of Lasso Professional 8 or 8.5 must be removed prior to installing the new version. Use the Remove option in the installer to remove the previous installation then re-run the installer to install the new version. No databases or settings files will be removed by this procedure. [/note]

To install Lasso Professional Server for IIS:

• 1 From the installation CD or the electronic download, double-click the [code]Lasso Pro 8.5 Installer.msi[/code] application. This launches the [code]Lasso Professional Server Setup[/code] window.

2. You must agree to the license agreement before installing Lasso. The release notes screen includes some late-breaking information that may not be contained in the documentation.

3. Select the drive and destination folder to which Lasso Professional Server will be installed. This is [code]C:Program FilesOmniPilot SoftwareLasso Professional 8[/code] by default. To ensure all features in Lasso Professional Server to work properly, it is strongly recommended that the names of these folders not be changed. Select [code]Next[/code].

4. A message will be displayed stating that Lasso Professional Server is ready to be installed. Select the [code]Back[/code] button to check or modify any of the previous steps. Select [code]Next[/code] to install Lasso Professional Server.

5. Select [code]Finish[/code] when the installer has completed.

[p]Lasso Service will automatically start after the installer has finished and a Web browser window will automatically open to the [code]Lasso Initialization [/code]page, which is described in the next section. [/p]

Windows Server 2003 Configuration

[p]Windows Server 2003 requires additional configuration of IIS 6. Lasso must be explicitly allowed in the Web Service Extensions configuration in order for IIS to serve [code].lasso[/code] or [code].lassoapp[/code] files. [/p]

1. Open the [code]Internet Information Services (IIS) Manager[/code].

2. Expand the local computer item and select [code]Web Service Extensions[/code].

3. Select [code]Add a new Web service extension…[/code] from the tasks list or the [code]Action[/code] menu.

4. Type [code]Lasso Professional[/code] for the [code]Extension Name[/code]. Click the [code]Add…[/code] button and locate the file at the path below; Check the [code]Set extension status to Allowed[/code] checkbox. Click [code]OK[/code] to continue.

[pre]C:WINDOWSsystem32Lasso8ConnectorforIIS.dll [/pre]

5. A new item [code]Lasso Professional[/code] with status [code]Allowed[/code] is created.

Additional Configuration

[p]These additional steps are necessary to finish configuring IIS. [/p]

1. Get [code]Properties[/code] on the [code]WebSites[/code] folder in the [code]Internet Information Services (IIS) Manager[/code]. Under the [code]ISAPI Filters[/code], make sure there is a [code]LassoFilter[/code] and its priority is [code]High[/code].

2. On the [code]Home Directory[/code] tab under [code]Configuration[/code], make sure that both [code].lasso[/code] and [code].LassoApp[/code] are listed. Make sure that both [code]Extensions[/code] point to the [code]C:WINDOWSsystem32Lasso8ConnectorforIIS.dll[/code]. For the [code].LassoApp[/code] extension, make sure that the [code]Check that File Exists[/code] box is not checked.

3. Repeat the instructions in step 2 for the [code]Home Directory[/code] of the [code]Default Site[/code] as well.

[note][b]Note: [/b]Setting the option [code]All Unknown ISAPI Extensions[/code] to [code]Allow[/code] will also allow Lasso processed Web pages to be served by IIS, but is not recommended since it essentially defeats the Web Service Extensions security feature offered by IIS 6. [/note]

Installing Lasso Professional Server With Apache 2

[p]Use the Lasso Professional Server Installer to ensure that all of the Lasso Professional Server files are installed in the proper location. The following procedure includes the additional steps necessary to install Lasso with Apache 2 support. [/p]

[note][b]Note: [/b]If you have already installed Lasso 8 with IIS support then you may need to run the installer again and [code]Modify[/code] your installation to add the [code]Lasso Connector for Apache 2[/code]. Then skip down to step 7 to complete the installation. [/note]

To install Lasso Professional Server for Apache 2:

• 1 From the installation CD or the electronic download, double-click the [code]Lasso Pro 8.5 Installer.msi[/code] application. This launches the [code]Lasso Professional Server Setup[/code] window.

2. You must agree to the license agreement before installing Lasso. The release notes screen includes some late-breaking information that may not be contained in the documentation.

3. Select the drive and destination folder to which Lasso Professional Server will be installed. This is [code]C:Program FilesOmniPilot SoftwareLasso Professional 8[/code] by default. To ensure all features in Lasso Professional Server to work properly, it is strongly recommended that the names of these folders not be changed. Select [code]Next[/code].

4. Select the [code]Custom…[/code] button to change the installer options. Disable the option to install the [code]Lasso Connector for IIS[/code] and enable the option for [code]Lasso Connector for Apache 2[/code].

5. A message will be displayed stating that Lasso Professional Server is ready to be installed. Select the [code]Back[/code] button to check or modify any of the previous steps. Select [code]Next[/code] to install Lasso Professional Server.

6. Select [code]Finish[/code] when the installer has completed.

7. Open the Lasso Professional 8 application folder (located in [code]C:Program FilesOmniPilot SoftwareLasso Professional 8 [/code]by default). Open the [code]Extensions[/code] folder and the [code]Lasso Connector for Apache 2[/code] folder.

8. The file [code]Lasso Connector for Apache 2.dll[/code] must be placed in your Apache modules folder which is usually at [code]C:Program FilesApache GroupApache2modules[/code].

9. The contents of the lasso8.conf file must be merged into your Apache 2 [code]httpd.conf[/code] file which is usually in [code]C:Program FilesApache GroupApache2conf[/code].

10. Restart the Apache 2 service using the Services control panel.

11. Access the following URL in order to initialize Lasso 8.

[pre]http://localhost/ServerAdmin.LassoApp [/pre]

Initialization

[p]The [code]Intialize[/code] page is launched in a Web browser after Lasso Professional Server Installer has completed. The [code]Initialize[/code] page is where the server administrator enters the Lasso Professional Server serial number, and sets the site administrator username and password for the first time. If this page does not launch automatically, then make sure Lasso Service is running and visit [code]http://127.0.0.1/ServerAdmin.LassoApp[/code] in a Web browser. For instructions on how to start and stop Lasso Service, see the Running Lasso Professional Server section of this chapter. [/p]

[note][b]Troubleshooting: [/b]If in the event that the [code]Lasso Initialization[/code] page does not load, make sure that Lasso Service and SQLite have started properly as described in the Running Lasso Professional Server section of this chapter. Otherwise, make sure that the installer was able to successfully configure IIS as described in the Extended Configuration > Lasso Connector for IIS section of this chapter. Also, make sure that the IIS Admin Service and World Wide Web Publishing Service have restarted properly. [/note]

Initializing Lasso Professional Server

[p]The [code]Welcome to Lasso Professional Server[/code] panel displays a message listing the steps required to initialize Lasso. This involves entering the serial number, setting the server administrator username and password, and establishing the SMTP preferences. [/p]

Figure 1: Initialize Page

[p]If no serial number is entered then Lasso will default to Lasso Developer functionality which allows the development of Lasso-based Web sites. Lasso Developer will five IPs to connect and has a per minute limit on the number of connections which it will serve. A Lasso Professional Server serial number is required to deploy Web sites with Lasso. [/p]

[p]An evaluation serial number can be used to test the full functionality of Lasso for a limited time prior to purchase. To request an evaluation serial number, select the [code]Request Evaluation Serial Number[/code] button. This will take one to the LassoSoft Web site, where an evaluation serial number can be obtained. [/p]

[p]Once a serial number is obtained, Lasso Professional Server can be initialized by following the procedure below. [/p]

To initialize Lasso Professional Server:

1. Enter the Lasso Professional Server serial number in the [code]Serial Number[/code] field. This must be entered exactly as it appears in your LassoSoft invoice or email using the following format:

[pre]LP8.5-WIN-123456789 [/pre]

• Serial numbers are case-sensitive. Make sure that all capitalization is correct and that all letters and numbers are entered, including the [code]LP8.5[/code] prefix.

2. Enter your desired server administrator username in the [code]Administrator Username [/code]field. This username will be used by the Lasso server administrator to log in to the administration interface, as discussed in the Using Server Administration chapter.
3. [note][b]Note: [/b]The server administrator username and password in Server Administration are independent of Mac OS X administrator usernames and passwords, and do not have to match. [/note]

3. Enter your desired server administrator password in the [code]Administrator Password [/code]field and re-enter the server administrator password in the [code]Confirm Password [/code]field.

4. Select [code]Submit Information[/code] to continue.

[p]After the initialization information has been successfully submitted, an[code] Initialization Complete [/code]panel is displayed stating that Lasso Professional Server has been successfully initialized. [/p]

[p]Selecting the [code]Open Server Administration [/code]button will open Server Administration, where server preferences can be established. Server Administration also provides access to the Site Administration interface for the default site. [/p]

Figure 2: Server Administration

[p]At this point, Lasso Professional Server has been initialized and is ready to be used. Lasso Professional Server provides a convenient, Web-based interface for configuring Lasso site settings, instantly managing and editing databases, configuring Lasso Security, monitoring events, and much more. It is within this interface that all Lasso settings and databases are set up and configured. [/p]

[p]For a full description of Server Administration and how to use it, see the Using Server Administration chapter. [/p]

[p]The following describes where to go for more information on setting up and testing external data sources, and starting development. [/p]

• Setting up existing FileMaker Pro, MySQL, and JDBC data sources for use with Lasso Professional Server is described in the Setting Up Data Sources chapter.
• For an overview of setting up Lasso Security for databases, Lasso tags, files, and solutions, see the Setting Up Security chapter.
• To learn how to write custom Lasso solutions using Lasso code, see the Lasso 8.5 Language Guide.

[note][b]Security [/b][b]Note[/b]: Lasso Professional Server uses port [code]14552[/code] for Lasso Service. Lasso Service cannot be accessed by anonymous users, however, to protect Lasso Service it is recommended that system administrators block these ports from incoming requests from IP addresses other than the IP address of the Web server using Lasso Professional Server. [/note]

Enabling Auto Recovery

[p]Windows can be set to automatically restart Lasso Service if it crashes. This is done by configuring the options in the [code]Services[/code] control panel. [/p]

To configure auto recovery of Lasso Service:

1. From the Windows Task Bar, select Start > Settings > Control Panel > Administrative Tools > Services.

2. Right click on [code]Lasso Professional Server 8[/code], then select [code]Properties[/code] (or double-click on the [code]Lasso Service[/code] line).

3. Select the [code]Recovery[/code] tab.

4. Set the action on each failure to [code]Restart the Service[/code].

Running Lasso Professional Server

[p]Lasso Service is the core executable of Lasso Professional Server. It is implemented as a service application which can be started and stopped independently from the Web server. Lasso Service can be started and stopped within the [code]Services[/code] menu in Windows. [/p]

To start or stop Lasso Service:

1. From the Windows Task Bar, select Start > Settings > Control Panel > Administrative Tools > Services.

2. Right click on [code]Lasso Professional Server 8[/code], then select [code]Start[/code] to start Lasso Service, or [code]Stop [/code]to stop Lasso Service.

[p]In Windows, one also has the ability to start Lasso Service in console mode. This allows one to view the Lasso Professional Server status window, which shows all Lasso Professional Server actions that are currently being performed, as well as actions that have been performed since start up. This is useful for monitoring and troubleshooting purposes. [/p]

To start Lasso Service in console mode:

1. Stop Lasso Service if it is running.

2. Browse to the [code]Program FilesOmniPilot SoftwareLasso Professional Server[/code] folder on your hard drive.

3. Double-click on [code]LassoService.exe[/code].

Extended Configuration

[p]This section discusses the changes the Lasso Professional Server installer makes to IIS, and how to configure Lasso Professional Server for a distributed architecture with IIS. This section describes the following: [/p]

• Lasso Connector for J2EE describes how to manually install and configure Lasso’s support for J2EE servers.
• Lasso Connector for IIS describes configuring the module that installs into Microsoft IIS and provides connectivity to Lasso Service.
• Remote IIS Configuration describes manually configuring Lasso Service to run on a separate machine from the Windows Web server with IIS (distributed architecture).
• Setting Up Redundant Lasso Professional Server Servers provides tips for setting up multiple Lasso Professional Server servers in a RAIC.

[note][b]Important: [/b]It is not required that the instructions in this section be followed as part of a default installation or configuration process. The installer will configure a basic installation of Lasso Professional Server properly without any additional modification. This section is intended as an extended configuration reference for experienced administrators. [/note]

Lasso Connector for J2EE Web Server

[p]The Lasso Connector for J2EE provides a means for serving Lasso solutions in a Java 2 Enterprise Edition environment. The connector is a standard Java servlet and can be hosted by any Java HTTP server or servlet container conforming to the Servlet API Specification v2.3 or later. [/p]

[p]The connector can be found in the Extensions folder in the Lasso Professional Server application folder. The connector consists of three files: [/p]

• [code]Lasso8ConnectorforJ2EE.jar[/code] – This Java archive includes the connector itself.
• [code]commons-fileupload.jar[/code] – This Java archive includes the upload component for the connector. This file is necessary if [code][File_Upload][/code] support is desired.
• [code]web.xml[/code] – An example XML configuration file.

[note][b]Note: [/b]If the [code]Extensions[/code] folder was not installed then run the installer again and [code]Modify[/code] the installation to add the [code]Lasso Connector for J2EE.[/code] [/note]

[p]The installation procedure may vary between different server products, both in terms of location and deployment method (“packed” versus “unpacked”). [/p]

[p]Servers that conform to the Servlet API Specification v2.2 (or later) are required to accept a Web Application Archive in a standard format, which is discussed further below. [/p]

[p]A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its “unpacked” form, where each directory and file exists in the filesystem separately, or in a “packed” form known as a Web Archive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed. [/p]

[p]A special directory exists within the application hierarchy named [code]WEB-INF[/code]. This directory contains all things related to the application that aren’t in the document root of the application. No file contained in the [code]WEB-INF[/code] directory is served directly to a client. [/p]

[p]The contents of the [code]WEB-INF[/code] directory are: [/p]

[p]• [code]/WEB-INF/classes/[/code] directory for servlet and utility [code].class[/code] files. [/p]

[p]• [code]/WEB-INF/lib/[/code] directory for [code].jar[/code] (Java Archive) files which contain servlets, Javabeans, and other utility classes useful to the web application. [/p]

[p]• [code]/WEB-INF/web.xml[/code] web application deployment descriptor file in XML format [/p]

[p]The Lasso Connector archive [code]Lasso8ConnectorforJ2EE.jar[/code] and supporting file upload component [code]commons-fileupload.jar[/code] must be placed in the [code]/WEB-INF/lib/[/code] folder located in your web application directory. [/p]

[p]Additionally, the web application descriptor [code]web.xml[/code] must be edited to provide connector configuration parameters. By default, the sample web.xml file is configured to process [code].lasso[/code] and [code].LassoApp[/code] files only. If one wishes a web server to process Lasso files with alternate file extensions other than [code].lasso[/code] or [code].LassoApp[/code], perform the procedure below. [/p]

Java Server Configuration

[p]This section describes setting up the J2EE connector where Lasso Service runs on the same machine as the Java server. [/p]

To setup Lasso Connector for J2EE on a remote server:

1. Stop [code]Lasso Professional Server 8[/code] using the [code]Services[/code] control panel.

2. Stop the Java Web service if it is running. The instructions for stopping the Java Web service will vary depending on what Java Web service is being used.

3. On the machine running Lasso Service, locate the [code]Lasso8ConnectorforJ2EE.jar[/code] file and move it into the [code]WEB-INF/lib/[/code] folder on the remote server.

4. If your Lasso solution requires HTTP file upload functionality, move optional [code]commons-fileupload.jar[/code] file into the [code]WEB-INF/lib/[/code] folder on the remote server.

5. If you are adding Lasso support to an existing web application, copy the settings contained within the [code]<web-app>[/code] tags in the example [code]web.xml[/code] file into the same location in the existing [code]web.xml[/code] file. When deploying an entirely new web application, simply move the example deployment descriptor into [code]WEB-INF/[/code] directory on the remote Web server.

6. To configure the server to process alternate file extensions with Lasso, insert additional [code]<servlet-mapping>[/code] tags in the [code]web.xml[/code] file, providing your custom file extension in the [code]url-pattern[/code] attribute:

[pre]<servlet-mapping servlet-name='lasso-connector' url-pattern='*.myExt' /> [/pre]

Remote Java Server Configuration

[p]This section describes setting up Lasso Professional Server in a distributed architecture where Lasso Service runs on a separate machine from the Java server. [/p]

To setup Lasso Connector for J2EE on a remote server:

1. On the machine running Lasso Service, stop [code]Lasso Professional Server 8[/code] using the [code]Services[/code] control panel.

2. On the machine running Lasso Service, stop Java web service if it is running. Since the Lasso Connector for J2EE is being moved to a remote machine, all Lasso pages and LassoApps (including Lasso Administration) should no longer be served from this machine.

3. On the machine running Lasso Service, locate the [code]Lasso8ConnectorforJ2EE.jar[/code] file and move it into the [code]WEB-INF/lib/[/code] folder on the remote server.

4. If your Lasso solution requires HTTP file upload functionality, move optional [code]commons-fileupload.jar[/code] file into the [code]WEB-INF/lib/[/code] folder on the remote server.

5. If you are adding Lasso support to an existing web application, copy the settings contained within the [code]<web-app>[/code] tags in the example [code]web.xml[/code] file into the same location in the existing [code]web.xml[/code] file. When deploying an entirely new web application, simply move the example deployment descriptor into [code]WEB-INF/[/code] directory on the remote Web server.

6. Modify the host attribute of the servlet [code]init-param[/code] tag in the [code]web.xml[/code] file, supplying the IP address or host name of the computer running the Lasso Professional Server.

7. To configure the server to process alternate file extensions with Lasso, insert additional [code]<servlet-mapping>[/code] tags in the [code]web.xml[/code] file, providing your custom file extension in the [code]url-pattern[/code] attribute:

[pre]<servlet-mapping servlet-name='lasso-connector' url-pattern='*.myExt' /> [/pre]

Lasso Connector for IIS

[p]Lasso Connector for IIS is one of the default Web server connectors included with Lasso Professional Server. This section describes what settings Lasso Professional Server adds to Microsoft IIS, and how to manually perform these setting changes. Lasso Professional Server adds the following settings to Microsoft IIS: [/p]

• Adds [code]LassoFilter[/code] to [code]ISAPI filters for Web server.[/code]
• Configures the [code].Lasso[/code] and [code].LassoApp[/code] extensions in [code]WWW Service Application Configuration[/code].

[p]All files required to use Lasso Connector for IIS are located in the [code]WindowsSystem32[/code] and [code]InetPubwwwroot[/code] folders, as described earlier in this chapter. Do not remove any of these files as doing so will cause Lasso Connector for IIS not to work. Always check the Lasso Professional Server release notes for the most current configuration information. [/p]

[note][b]Certification [/b][b]Note[/b]: Lasso Professional Server is certified to work only with default Windows installations of IIS. Altered versions of IIS may work with Lasso Professional Server, but are not officially supported. [/note]

Adding the ISAPI Filter

[p]The [code]Lasso8ConnectorforIIS.dll[/code] file is the ISAPI filter that allows Microsoft IIS to recognize Lasso actions. Follow the procedure below to add or verify the ISAPI filter in the [code]Internet Services Manager[/code], located in Start > Settings > Control Panel > Administrative Tools from the [code]Windows Task Bar[/code]. [/p]

1. Using the [code]Internet Services Manager[/code], right-click on the local computer name and select [code]Properties [/code]in Windows 2000, or right-click on the [code]Web Sites[/code] folder and select [code]Properties [/code]in Windows XP.

2. Select the [code]Edit[/code] button to edit the [code]WWW Services Master[/code] properties.

3. Select the [code]ISAPI Filters[/code] tab.

4. If L[code]assoFilter[/code] does not appear in the list, click the [code]Add[/code] button.

5. Enter [code]LassoFilter[/code] in the [code]Filter Name[/code] field.

6. Select the [code]Browse[/code] button and browse to the [code]WindowsSystem32[/code] directory, and select [code]Lasso8ConnectorforIIS.dll[/code].

7. Select the[code] OK[/code] button on all open dialogs to apply the changes.

8. Right-click on the computer name in the [code]Internet Services Manager[/code] and select [code]Restart IIS[/code].

Configuring the .Lasso and .LassoApp Extensions

[p]The [code].lasso[/code] and [code].LassoApp[/code] extensions must be added to the Microsoft IIS Application Configuration screen in order to process Lasso pages. [/p]

1. Using the [code]Internet Services Manager[/code], right-click on the local computer name and select [code]Properties [/code]from the pop-up menu.

2. Select the [code]Edit[/code] button to edit the [code]WWW Services Master [/code]properties.

3. Select the [code]Home Directory[/code] tab.

4. Under [code]Application Settings[/code], select the [code]Configuration…[/code] button.

5. In the [code]Application Configuration[/code] window, select the [code]App Mappings[/code] tab.

6. If the [code].lasso[/code] extension does not appear under [code]Application Mappings[/code], select the [code]Add [/code]button.

7. Next to the [code]Executable[/code] field, select the [code]Browse[/code] button and navigate to the [code]WindowsSystem32[/code] directory, then select [code]Lasso8ConnectorforIIS.dll[/code].

8. Enter [code].lasso[/code] in the [code]Extension[/code] field.

9. Under [code]Verbs[/code], select the [code]All Verbs[/code] radio button.

10. Check the [code]Scripts engine[/code] check box.

11. Select [code]OK[/code] to apply the changes.

12. Repeat steps [code]6[/code] through [code]11[/code] for the [code].LassoApp[/code] extension.

13. Right-click on the computer name in the [code]Internet Services Manager[/code] and select [code]Restart IIS[/code].

[note][b]File [/b][b]Extensions Note[/b]: Lasso can be configured to process file extensions other than [code].lasso[/code] or [code].LassoApp[/code] by entering a different extension name in step 6. However, the .[code]lasso[/code] and [code].LassoApp[/code] extension must be configured, as not doing so will prevent access to required files for Lasso Professional Server, such as the administration LassoApp. [/note]

Remote IIS Configuration

[p]This section describes setting up Lasso Professional Server for a distributed architecture where Lasso Service runs on a separate Windows computer from the IIS Web server. The first step in setting up a distributed architecture is copying the necessary files to the remote Web server, and disabling the Lasso Web server connector on the local machine. To do this, follow the procedure below. [/p]

To setup Lasso Connector for IIS on a remote IIS Web server:

1. On the machine running Lasso Service, stop Lasso Service using the [code]Services[/code] menu in Windows.

2. On the machine running Lasso Service, stop IIS using the [code]Services[/code] menu in Windows. Since the Lasso Connector for IIS is being moved to a remote machine, all Lasso pages and LassoApps (including Site Administration) should no longer be served from this machine.

3. On the machine running Lasso Service, locate the [code]Lasso8ConnectorforIIS.dll [/code]file, located in the [code]WindowsSystem32[/code] folder or [code]WinNTSystem32[/code] folder (depending on the system), and move it to the [code]WindowsSystem32[/code] folder or [code]WinNTSystem32[/code] folder on the remote IIS Web server.

4. On the machine running Lasso Service, locate the [code]Lasso8ISAPI.conf [/code]file, located in the [code]WindowsSystem32[/code] folder or [code]WinNTSystem32[/code] folder (depending on the system), and move it to the [code]WindowsSystem32[/code] folder or [code]WinNTSystem32[/code] folder on the remote IIS Web server.

5. On the remote IIS server, configure IIS for Lasso Professional Server as specified in the previous Lasso Connector for IIS section.

6. On the remote server, open the[code] Lasso8ISAPI.conf [/code]file located in the [code]WindowsSystem32[/code] folder or [code]WinNTSystem32[/code] folder in a plain text editor.

7. Next to [code]Server[/code], replace [code]127.0.0.1[/code] with the correct host name or IP address of the computer running Lasso Service.

8. On the machine running Lasso Service, start Lasso Service using the [code]Services[/code] menu.

9. On the remote Web server, restart IIS using the [code]Services[/code] menu.

[note][b]Note: [/b]In Lasso Professional Server, only one Web server may connect to the machine running Lasso Service at a time. [/note]

Setting Up Redundant Lasso Professional Server Servers

[p]For load balancing purposes, multiple Web servers running Lasso Professional Server may be set up in a RAIC (Redundant Array of Independent Components) in the same manner as other Web servers. There are a variety of ways to do this depending on the networking hardware and software available, and instructions for setting up a RAIC are beyond the scope of this guide. [/p]

[p]However, there is one setting in Lasso Professional Server that must be adjusted in order for Lasso sessions to persist across a RAIC, and that is to point each instance of Lasso Professional Server to a single MySQL sessions server. For instructions on how to do this, please see the Setting Site Preferences chapter. [/p]

Installation Contents

[p]This section contains a list of all files and folders that are installed during Lasso Professional Server installation. [/p]

[note][b]System [/b][b]User Note: [/b]The Lasso Professional Server installer automatically configures Lasso Service under the [code]System[/code] user account in Windows. The privileges of this user are invoked whenever Lasso needs to read, write, execute, or create files or folders on the hard drive. [/note]

Start Menu

[p]Lasso Professional Server installs the [code]Uninstaller[/code] application in the [code]Start MenuOmniPilot SoftwareLasso Professional Server[/code] folder in the Windows hard drive. The [code]Uninstaller[/code] application allows one to make changes to an existing installation of Lasso Professional Server, or remove Lasso Professional Server from the system. [/p]

Program Files

[p]Lasso Professional Server installs the following files and folders in the [code]Program FilesOmniPilot SoftwareLasso Professional 8[/code] folder in the Windows hard drive. [/p]

• [def]Chart FX folder[/def] – Contains additional documentation about the Chart FX module and the Chart FX for Java Designer which can be used to create Chart FX template files.
• Documentation folder – Contains all Lasso Professional Server documentation in PDF format, which can be viewed with Adobe Acrobat Reader. The following files and folders are contained in this folder. It is highly recommended that the documentation be read in this order.
• [code]1-ReadMeFirst[/code] folder – Contains [code]Release Notes.txt[/code] and [code]License Agreement.txt[/code]. Read this documentation in this folder first before proceeding to configure Lasso Professional Server.
• [code]2-SetupGuide [/code]folder – Contains [code]Lasso 8.5 Setup Guide.pdf[/code].
• [code]3-LanguageGuide[/code] folder – Contains [code]Lasso 8.5 Language Guide.pdf, [/code]and the [code]LassoApps[/code], [code]LCP[/code], [code]LCAPI[/code], and [code]LJAPI[/code] folders.
• Extensions folder – Contains additional optional components.
• [code]J2EE[/code] folder – Contains the Lasso Connector for J2EE which is required for Java Enterprise Server support.
• [code]Apache [/code][code]2[/code] folder – Contains the Lasso Connector for Apache 2 which is required for manual installation of support for Apache 2.
• [code]Apache [/code][code]2.2[/code] folder – Contains the Lasso Connector for Apache 2.2 which is required for manual installation of support for Apache 2.2.
• [code]OS [/code][code]Process[/code] folder – Contains the [code][OS_Process][/code] module which allows access to the shell or other processes running natively on each platform.
• ImageMagick Libraries – The libraries for ImageMagick 6.2.9 are installed in the Lasso Professional 8 folder directly. These libraries are used to power the [code][Image][/code] tags in Lasso 8. For more information, see the Images and Multimedia chapter in the Lasso 8.5 Language Guide.
• JavaLibraries folder – Any extra Java libraries (usually .jar files) can be placed in this folder. They will be loaded when Lasso starts Java, but no JDBC drivers or tag modules will be loaded from them. JavaBeans can also be installed in this folder.
• [code]iText.jar[/code] – Required library for the [[code]PDF_…][/code] tags.
• JDBCDrivers folder – Drivers for JDBC data sources are placed here (empty by default). For instructions on how to use this folder while configuring JDBC data sources, see the Setting Up Data Sources chapter.
• Lasso Admin folder – Contains files and folders used for administering Lasso Professional Server.
• [code]BuildLassoApps [/code]folder – Is a folder used to build LassoApps. For more information, see the Administration Utilities chapter.
• LassoApps folder – Contains LassoApps for on-demand loading. When a LassoApp file is requested this folder is checked first and the LassoApp is loaded from here if it exists. This allows LassoApps to be served without placing them in the Web server root.
• LassoLibraries folder – Contains LassoApps and [code].Lasso[/code] pages for on-demand loading. Each file should have the name of the namespace it defines. When Lasso tries to execute an unknown tag it checks here to see if it can load the tag before continuing.
• LassoModules folder – Contains all default Lasso modules included with Lasso Professional Server as listed below. All data source connectors (including third-party connectors) and tag modules should go here.
• [code]chartfx.lasso.jar [/code]– Implements Chart FX support.
• [code]FMPConnector.dll [/code]– Data source connector module for FileMaker Pro data sources.
• [code]FMSAConnector.dll [/code]– Data source connector module for FileMaker Server data sources.
• [code]ImageTag.dll[/code] – Implements support for the image tags..
• [code]LDAPConnector.dll[/code] – Implements support for querying LDAP data sources.
• [code]LJAPI.jar[/code] – Implements core support for all LJAPI modules and includes the data source connector for JDBC data sources.
• [code]LJAPI.dll[/code] – Implements support for LJAPI modules.
• [code]MySQLConnector.dll[/code] – Data source connector module for MySQL data sources.
• [code]NSLookup.class[/code] – Java class file for [code][NSLookup][/code] tag.
• [code]OpenBaseConnector.dll[/code] – Data source connector module for OpenBase data sources.
• [code]PDF.jar[/code] – Required library for the [[code]PDF_…][/code] tags.
• [code]SQLConnector.dll[/code] – Implements support for SQL-based data sources including Oracle, PostgreSQl, and Microsoft SQL Server.

1. [note][b]Note: [/b]There is no separate module for the Lasso data source connector for SQLite. This is built into the core Lasso Service code. [/note]

• LassoService.exe – Lasso Service is the core executable of Lasso Professional Server. It is implemented as a service application which can be started and stopped independently from the Web server. Lasso Service is the Lasso Web Data Engine.
• LassoStartup folder – Contains the [code]Startup.LassoApp[/code] file and [code]sites[/code] folder, which are used by Lasso Service during startup. All Lasso pages and LassoApps which need to be launched during startup should be placed here. For information on how to use the [code]LassoStartup[/code] folder, see the Lasso pages chapter of the Lasso 8.5 Language Guide. For additional discussion of the [code]LassoStartup[/code] folder, see the Lasso 8.5 Language Guide.
• SQLiteDBs folder – Contains SQLite databases used to store Lasso Professional Server settings and preferences.

Web Server Root

[p]Lasso Professional Server does not install any files in the Web server root. All of Lasso’s administration tools are loaded on-demand from the [code]LassoApps[/code] folder so do not need to be located in this folder. [/p]

Windows System Files

[p]Lasso Professional Server installs the following files in the [code]WindowsSystem32[/code] directory of the Windows hard drive. The files installed in this folder allow Lasso Professional Server to function properly. Lasso Web server connectors are also located here by default. [/p]

• [def]Lasso8ConnectorforIIS.dll[/def] – The ISAPI filter that allows Lasso Service to communicate with Microsoft IIS version 5 and 6.
• [def]Lasso8ISAPI.conf [/def]– The Web server configuration file for [code]Lasso Connector for IIS[/code]. This file is not created by default.

Uninstalling Lasso Professional Server

[p]Lasso Professional Server can be uninstalled using the uninstaller program provided in the [code]Lasso Professional Server[/code] folder. Using the uninstaller program will automatically remove all core program and system files, and is the only recommended way to uninstall Lasso Professional Server. [/p]

[note][b]Note: [/b]The uninstaller program will not remove any non-default files created after the time of install. See the following section for more information. [/note]

To uninstall Lasso Professional Server:

1. Select the [code]Uninstall[/code] program, located in Program Files > OmniPilot Software > Lasso Professional Server in the Windows Start Menu. This launches the [code]Lasso Professional Server Setup[/code] window.

2. Select the [code]Remove[/code] radio button, and then select[code] Next[/code]. [code]Lasso Professional Server Setup[/code] displays a confirmation message for removing the application

3. Select [code]Next[/code] in the confirmation screen. This will automatically uninstall Lasso Professional Server.

4. Select [code]Finish[/code] when the uninstaller has completed.

Files and Folders Not Removed

[p]The uninstaller program will not remove any non-default files created after the time of install, or any default Lasso files modified since the time of install. These files include the SQLite databases, Lasso log files, Lasso setups, and custom Lasso pages and LassoApps. These files and folders may be backed up for preservation, or may be deleted to completely remove Lasso Professional Server and all settings from the system. [/p]

• Application folder – The [code]C:Program FilesOmniPilot SoftwareLasso Professional Server[/code] folder is left on the Windows hard drive, which contains the following folders:
• [code]JavaLibraries[/code] – Contains any Java libraries installed by the administrator. This folder will be removed if no extra Java libraries were installed.
• [code]JDBCDrivers[/code] – Contains any JDBC drivers installed by the administrator. This folder will be removed if no JDBC drivers were installed.
• [code]LassoApps[/code] – Contains LassoApps for on-demand loading. This folder will be removed if no extra LassoApps were installed.
• [code]LassoLibraries[/code] – Contains tag libraries for on-demand loading. This folder will be removed if no extra tag libraries were installed.
• [code]LassoModules[/code] – Contains data sources connectors, Java libraries, and any third-party Lasso modules.
• [code]LassoSites[/code] – Contains the site level folders for each defined site. The site level folders have the same structure as the master level folders described here. Each site might have its own [code]JavaLibraries[/code], [code]JDBCDrivers[/code], [code]LassoApps[/code], [code]LassoLibraries[/code], [code]LassoModules[/code], and [code]SQLiteDBs[/code].
• [code]SQLiteDBs[/code] – Contains all default SQLite databases, which contain serial numbers, passwords, database settings, logs, and permissions from the previous setup of Lasso Professional Server.
• Web Server Root folder – The Web server root folder retains all Lasso pages created or modified since the time of installation. Customized Lasso pages, Web pages, and scripts will not be deleted during uninstallation.

[note][b]Reinstallation [/b][b]Note[/b]: Any files remaining on the system from a previous installation of Lasso Professional Server will not be overwritten by installing a newer version. Therefore, all previous settings will be retained if a newer version of Lasso Professional Server is installed over the files not removed during the uninstallation of the previous version. [/note]