Chapter 3
Configuring on Mac OS X

[p]This chapter contains the installation and configuration instructions for Lasso Professional Server on Mac OS X. It also contains information on Lasso Professional Server components and how to 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 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 Apache for Lasso Professional Server, and how to set up a Lasso Professional Server distributed architecture.
• Installation Contents lists the files 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 minimum requirements listed below. Although Lasso Professional Server may run on machines which do not meet these requirements, those installations are not supported. [/p]

• Macintosh computer with Intel, or PowerPC G5, G4, or G3 processor.
• 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.)
• Standard installation of Mac OS X 10.5, 10.4, or 10.3.9 or Mac OS X Server 10.5, 10.4, or 10.3.9 with an HFS+ formatted hard drive with BSD subsystem option. UFS systems are not supported.
• Mac OS X build of Apache Web Server 1.3, 2.0, or 2.2 included with Mac OS X 10.5, 10.4, or 10.3.9. Or, the latest version of WebSTAR V.
• X11 for Mac OS X must be installed for the [code][Image][/code] tags in Lasso Professional Server to function. For information on obtaining and installing X11, see the Mac OS X install DVD or the following URL:

[pre][code]http://www.apple.com/macosx/x11/[/code] [/pre]

[note][b]Certification [/b][b]Note[/b]: Lasso Professional Server is certified to work with default installations of the requirements described above. Modified versions of Apache and customized [code]httpd.conf[/code] configuration files may work with Lasso Professional Server, but are not officially supported. [/note]

Web Browser Requirements

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

• Safari 2.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 Server or 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 provides installation instructions for Lasso Professional Server and its required components and describes how to initialize Server Administration for the first run. For best results, please perform the procedures in the following sections in the order they are presented. [/p]

• Installing X11 describes how to install X11, which is required prior to installing Lasso Professional Server on Mac OS X.
• Installing Lasso Professional Server describes how to install Lasso Professional Server.
• 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 X11

[p]X11 (X Window System version 11) for Mac OS X must be installed in order for the image manipulation features of Lasso Professional Server to work (implemented via the [code][Image][/code] tags). X11 can be optionally installed as part of Mac OS X 10.4/10.5. It is recommended that X11 be installed prior to installing Lasso Professional Server. If X11 is not installed, errors will be logged to Lasso’s error log whenever Lasso Service is started and errors will be returned whenever the [code][Image][/code] tags are used. [/p]

To install X11 for Mac OS X:

• Mac OS X 10.4/10.5 users should install X11 from the installation DVD.
• Mac OS X 10.3.9 users can download the X11 installer at the following address:

[pre]http://www.apple.com/support/downloads/x11formacosx.html [/pre]

• Double-click the X11 installer application, and then follow the instructions to install X11.

Installing Lasso Professional Server

[p]Use the Lasso Professional Server Installer application ([code]Lasso Pro 8.5 Installer.mpkg[/code]) to ensure that all of the Lasso Professional Server files are installed in the proper location with the proper permissions. The Lasso Professional Server installer applications supports several different Web server configurations on Mac OS X: [/p]

• Apache – The default Web server included with Mac OS X and Mac OS X Server. Also referred to as Personal Web Sharing. This will automatically install into Apache 1.3 on Mac OS X 10.4 and lower and on Apache 2.2 in Mac OS X 10.5.
• Complete Apache 2 – Popular Apache 2 binary distribution for Mac OS X. For more information, see [code]http://serverlogistics.com/apache2.php[/code].
• iAssist Apache 2 – Popular Apache 2 binary distribution for Mac OS X. For more information, see [code]http://www.maxum.com/iAssist/WebServices.html[/code].
• Mac OS X Server Apache 2 – Apache 2 distribution included as an optional installation with Mac OS X Server 10.4 and lower. Note that Mac OS X Server 10.5 users should install the default option.
• WebSTAR V – WebSTAR Server Suite V. This Web server is no longer supported by its developer. Users of WebSTAR should consider migrating to the built-in Apache Web server on Mac OS X.

[p]The following procedures describe how to install Lasso Professional Server for each of the Web server configurations above. [/p]

To install Lasso Professional Server:

1. Double-click the [code]Lasso Pro 8.5 Installer.mpkg[/code] application. This launches the [code]Lasso Professional Server[/code] window.

2. The Lasso Professional Server release notes will be displayed. The release notes contain important late breaking information that might not be covered in the documentation. After reading the release notes which describe what is included with Lasso Professional Server, select [code]Continue[/code].

3. The Lasso Professional Server License Agreement will be displayed. After reading and agreeing to the terms, select the [code]Continue[/code] and then the [code]Agree[/code] button.

4. Select the drive you wish to install Lasso Professional Server on. This should be the drive that Mac OS X or Mac OS X Server is installed on. Then select [code]Continue[/code].

5. The next steps depends on which of the supported Web servers is being used.

• Most users will want to simply select the [code]Install[/code] or [code]Upgrade[/code] button. This will install the connector for the default version of Apache included with Mac OS X 10.5 or Mac OS X Server 10.5, Mac OS X 10.4, or Mac OS X 10.3.9.
• Users with Mac OS X Server 10.4, Mac OS X Server 10.3.9, or with one of the other supported Apache 2 installations or WebSTAR V should select the [code]Customize[/code] button. Deselect [code]Lasso Connector for Apache[/code] and select the appropriate Web server connector (see above for descriptions). Finally, select the [code]Install[/code] or [code]Upgrade[/code] button.

6. An authentication dialog will prompt for an administrator name and password. Enter the username and password of a Mac OS X user on the machine who has administrative rights. Select [code]Continue[/code].

7. Select [code]Quit[/code] when the installer has completed. Upon quit the installer automatically restarts the Apache Web server and starts Lasso Service.

[p]After the installers has finished, it will automatically open a Web browser window and attempt to launch the [code]Lasso Initialization [/code]page, which is described in the following Initialization section. [/p]

Initialization

[p]The[code] Initialize[/code] page is where the administrator enters the Lasso Professional Server serial number, and sets the site administrator username and password for the first time. To launch the[code] Initialize[/code] page, make sure Lasso Service is running and visit [code]http://localhost/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 has started properly as described in the Running Lasso Professional Server section of this chapter. Otherwise, consult the Extended Configuration section to ensure that the installer has configured the Web server correctly (i.e. Apache, WebSTAR). [/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 and setting the server administrator username and password. [/p]

Figure 1: Server 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]

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-MAC-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 use. 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. For a description of Site Administration and how to use it see the Using Site 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 ports [code]14552[/code] for Lasso Service. Lasso Service cannot be directly accessed by anonymous users, however, it is recommended that system administrators block this port from incoming requests from IP addresses other than the IP address of the Web server using Lasso Professional Server. [/note]

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 is started and stopped using the [code]lasso8ctl[/code] command or the terminal command files provided in the [code]/Applications/Lasso Professional 8/Tools[/code] folder. [/p]

To start Lasso Service:

• Type the following command into the Mac OS X Terminal application. You will be prompted for your password. This command must be accessed from an administrator account.

[pre]sudo lasso8ctl start [/pre]

• Alternately, open the [code]Tools[/code] folder in the Lasso Professional Server application folder and double click on the [code]startLassoService.command[/code] file. This will launch a terminal window that prompts you for your password and starts Lasso Service.

[p]Lasso Service can also be run in console mode within the terminal. This allows the administrator 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. Lasso Service should be started this way whenever startup, stability, or performance problems are encountered in Lasso Professional Server. [/p]

To start Lasso Service in console mode:

[p]Open the [code]Tools[/code] folder in the Lasso Professional Server application folder and double click on the [code]consoleLassoService.command[/code] file. This will launch a terminal window that prompts you for your password and starts Lasso Service. [/p]

[p]The terminal window contains all of the output of the Lasso Service console. Closing the terminal window will stop Lasso Service. To restart Lasso Service as a background service type [code]Ctrl-C[/code] in the terminal to stop Lasso Service. Then type the following command. You will be prompted for your password. This command must be accessed from an administrator account. [/p]

[pre][code]sudo lasso8ctl restart[/code] [/pre]

To stop Lasso Service:

• Type the following command into the Mac OS X Terminal application. You will be prompted for your password. This command must be accessed from an administrator account.

[pre]sudo lasso8ctl stop [/pre]

• Alternately, open the [code]Tools[/code] folder in the Lasso Professional Server application folder and double click on the [code]startLassoService.command[/code] file. This will launch a terminal window that prompts you for your password and starts Lasso Service.

To see if Lasso Service is running:

• Type the following command into the Mac OS X Terminal application. You will be prompted for your password. This command must be accessed from an administrator account.

[pre]sudo lasso8ctl status [/pre]

• Look for a process named [code]Lasso8Servic[/code]e in the Mac OS X Process Viewer utility application.
• Alternately, run the following command in the Mac OS X Terminal to check for Lasso Service in the list of current processes.

[pre]ps -ax | grep Lasso8Service [/pre]

[note][b]Terminal [/b][b]Note[/b]: See the [code]Mac OS X Tips.pdf[/code] file in the Lasso Professional Server application folder Documentation folder[code] [/code]for instructions on how to do this. [/note]

Extended Configuration

[p]This section discusses the changes the Lasso Professional Server installer makes to the various Web servers it supports, how to configure Lasso Professional Server for a distributed architecture, how to configure WebSTAR V file permissions, and how to install Lasso with J2EE support. This section describes the following: [/p]

• Remote Installation describes how to install Lasso Professional Server on a remote server.
• Lasso Connector for J2EE describes how to manually install and configure Lasso’s support for J2EE servers.
• Lasso Connector for Apache describes configuring the module that installs into Apache and provides connectivity to Lasso Service.
• Remote Apache Configuration describes manually configuring Lasso Service to run on a separate machine from Apache Web server (distributed architecture).
• Lasso Connector for WebSTAR describes configuring the module that installs into WebSTAR and provides connectivity to Lasso Service
• Remote WebSTAR Configuration describes manually configuring Lasso Service to run on a separate machine from WebSTAR V (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]

Remote Installation

[p]For UNIX administrators that desire it, Lasso Professional Server can be installed remotely using ssh. This is useful if you do not have direct access to the Web server where Lasso will be installed, or if the Web server is not set up with a monitor, keyboard, or mouse. [/p]

To install Lasso Professional Server on a remote server:

1. Copy the [code]Lasso Pro 8.5 Installer.mpkg[/code] installer to a location on your remote server. This can be done using any remote file transfer method, such as file sharing, ftp, or scp.

2. Use the terminal to ssh into remote server using an administrative user account. An example ssh login command is shown below.

[pre]ssh administrator@www.example.com [/pre]

3. To install Lasso Professional Server, enter the following command. Replace [code]/path-to-installer/[/code] with the full UNIX folder path to the Lasso Professional Server installer. Enter the administrative user password if prompted.

[pre]sudo installer -pkg "/path-to-installer/Lasso Pro 8.5 Installer.mpkg" -target / [/pre]

4. Once the installer is finished, open your browser and access the remote server default Web page to initialize Lasso Service.

[pre]http://www.example.com/ServerAdmin.LassoApp [/pre]

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.

[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 Lasso Service using the [code]stopLassoService.command[/code] file in the Lasso Professional Server [code]Tools[/code] folder.

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 Lasso Service using the [code]stopLassoService.command[/code] file in the Lasso Professional Server [code]Tools[/code] folder.

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 Apache

[p]Lasso Connector for Apache is one of the default Web server connectors included with Lasso Professional Server. This section describes what settings Lasso Professional Server adds to the Apache configuration file ([code]httpd.conf[/code]), and how to view or manually change the Apache settings. [/p]

Apache Configuration

[p]The Lasso Professional Server installer creates a file named [code]lasso8.conf[/code], which is automatically included in the [code]httpd.conf[/code] file whenever Apache starts up. This file includes Lasso’s default settings and should not be edited. [/p]

[p]The following procedure describes viewing and editing the [code]lasso8.conf[/code] file, which contains Apache’s settings for Lasso. [/p]

To view or edit changes made to Apache:

1. Start the Mac OS X terminal application, located in [code]Applications/Utilities [/code]by default. Expand the terminal window to be as large as possible on the screen for best results.

2. Enter the following command to open the [code]lasso8.conf [/code]file via the terminal depending on which version of Mac OS X you are using.

• Mac OS X 10.5 and Mac OS X 10.5 Server include Apache 2.2 and should use the following command.

[pre]sudo pico /etc/apache2/other/lasso8.conf [/pre]

• Mac OS X 10.4 and Mac OS X 10.3.9 include Apache 1.3 and should use the following command.

[pre]sudo pico /etc/httpd/users/lasso8.conf [/pre]

• Other installations of Apache 2 will be similar, but may store their configuration files in a different location. Consult the documentation of the installation on the server for more information.

1. [note][b]Note: [/b]This file is locked by default, and one must be logged in as the root user to edit it. See the [code]Mac OS X Tips.pdf[/code] file in the Lasso Professional Server [code]Documentation[/code] folder for instructions on how to perform these tasks using the terminal. [/note]

3. Apache can be set up to process alternate file extensions with Lasso Service by adding lines to the [code]lasso8.conf [/code]file using the following format: [code]AddHandler lasso8-handler extension[/code]. Replace [code]extension[/code] with the file extension you wish to be processed by Lasso Service (e.g. .[code]htm[/code], .[code]html[/code], etc.)
4. [note][b]Note: [/b]The [code]lasso8.conf [/code]file contains three lines which define the default settings for Lasso, as shown below. The last two lines tell Apache to process files with the extensions [code].lasso[/code] and [code].lassoapp[/code] with Lasso Service. [/note]

• Mac OS X 10.5 and Mac OS X 10.5 Server include Apache 2.2 and should use the following configuration directives. Note that additional URLs can be sent to Lasso for processing by adding them using additional location directives.

[pre]LoadModule lasso8_module /usr/libexec/apache2/Lasso8ConnectorforApache.so
Location ~ "^.*.[Ll][Aa][Ss][Ss][Oo]$">
SetHandler lasso8-handler
</Location>
<Location ~ "^.*.[Ll][Aa][Ss][Ss][Oo][Aa][Pp][Pp]$">
SetHandler lasso8-handler
</Location> [/pre]

• Mac OS X 10.4 and Mac OS X 10.3.9 include Apache 1.3 and should use the following configuration directives. Note that additional URLs can be sent to Lasso for processing by adding them using additional location directives.

[pre]LoadModule lasso8_module /usr/libexec/httpd/Lasso8ConnectorforApache.so
Location ~ "^.*.[Ll][Aa][Ss][Ss][Oo]$">
SetHandler lasso8-handler
</Location>
<Location ~ "^.*.[Ll][Aa][Ss][Ss][Oo][Aa][Pp][Pp]$">
SetHandler lasso8-handler
</Location> [/pre]

• Other installations of Apache 2 will be similar, but may store their configuration files in a different location. Consult the documentation of the installation on the server for more information.

4. Save the [code]lasso8.conf[/code] file after making any changes.

5. Restart Apache Web Server for any changes to take place. This is done by accessing [code]System Preferences/File Sharing[/code] in Mac OS X, and then turning [code]Web Sharing [/code]off and then on again. Alternately, one can restart Apache Web Server by entering the following command in the terminal:

[pre]sudo apachectl graceful [/pre]

Remote Apache Configuration

[p]This section describes setting up Lasso Professional Server in a distributed architecture where Lasso Service runs on a separate Mac OS X computer from the Mac OS X Apache Web server. To do this, follow the procedure below. [/p]

To set up Lasso Connector for Apache on a remote server:

1. On the machine running Lasso Service, stop Lasso Service using the [code]stopLassoService.command[/code] file.

2. On the machine running Lasso Service, stop Apache if it is running. Since the Lasso Connector for Apache 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]Lasso8ConnectorforApache.so [/code]file and move it into the corresponding [code]/usr/libexec/httpd [/code]folder or [code]/usr/libexec/apache2[/code] on the remote server. For instructions how to move hidden system files, see the [code]Mac OS X Tips.pdf[/code] document.

4. On the machine running Lasso Service, locate the [code]lasso8.conf [/code]file and move it into the corresponding [code]/etc/httpd/users [/code]folder or [code]/etc/apache2/other[/code] folder on the remote server. For instructions how to move hidden Unix files, see the [code]Mac OS X Tips.pdf[/code] document.

5. On the machine running Lasso Service, locate the [code]editLassoApacheconf.command[/code] file in the [code]/Applications/Lasso Professional 8/Tools[/code] folder, and move it to any location on the remote Web server.

6. On the remote server, open the copied [code]Lasso8Apache.conf[/code] file in the Pico file editor using the following command:

[pre]sudo pico /etc/lasso/lasso8apache.conf [/pre]

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

8. Press [code]Ctrl-X[/code]. This will ask you if you want to save the file.

9. Enter[code] y[/code]. This saves and closes the file.

10. On the remote server, restart Apache Web Server. This is done by accessing System Preferences > File Sharing in Mac OS X, and then turning [code]Web Sharing [/code]off and then on again. Alternately, one can restart Apache Web Server by entering the following command in the terminal:

[pre]sudo apachectl graceful [/pre]

11. On the machine running Lasso Service, start Lasso Service. This can be done using the [code]startLassoService.command[/code] file described in the Running Lasso Professional Server section of this chapter.

[note][b]Note: [/b]Only one Web server may connect to the machine running Lasso Service at a time. [/note]

Lasso Connector for WebSTAR V

[p]The Lasso Connector for WebSTAR V is represented by a file named [code]Lasso8ConnectorforWebSTARV.so[/code] that is installed to the WebSTAR V [code]Plug-Ins[/code] folder. This file automatically adds all Lasso settings to WebSTAR V. [/p]

[p]Some additional configuration may be necessary in order to allow both WebSTAR and Lasso to access files. WebSTAR runs as the user [code]webstar[/code] and Lasso runs as the user [code]lasso[/code] in the group [code]staff[/code]. Once permissions have been set up properly the WebSTAR installer should maintain those permissions on re-installs. [/p]

To configure permissions so files can be read by WebSTAR and Lasso:

• Change the [code]4DWebSTAR[/code], [code]4DWebSTAR/WebServer[/code], and [code]4DWebSTAR/WebServer/DefaultSite[/code] folders to have world read and execute permissions. This may need to be applied to other sites you have running in the [code]4DWebSTAR/WebServer[/code] folder, and possibly files contained in those folders.
• The following commands can be typed into the Terminal in order to modify the permissions of the folders. Enter the machine’s administrator password when prompted.

[pre] sudo chmod o+rx /Applications/4DWebSTAR
sudo chmod o+rx /Applications/4DWebSTAR/WebServer
sudo chmod o+rx /Applications/4DWebSTAR/WebServer/DefaultSite [/pre]

• Change the group on all files in the [code]4DWebSTAR[/code] folder to [code]staff[/code]. The [code]lasso[/code] user is part of the [code]staff[/code] group and making this change would allow Lasso to access the files. Unfortunately, users not in the staff group would not be able to get in. In Mac OS X 10.2 all users belonged to the staff group, but in 10.3.9, no users are added to the staff group when they are created.
• The following command can be typed into the Terminal in order to modify the group owner of all files within the [code]4DWebSTAR[/code] folder. Enter the machine’s administrator password when prompted.

[pre]sudo chgrp -R staff /Applications/4DWebSTAR [/pre]

[p]By default, Lasso Connector for WebSTAR V is configured to process [code].lasso [/code]and [code].LassoApp[/code] files only. These extensions are built into Lasso Connector for WebSTAR V and cannot be changed. If one wishes WebSTAR to process Lasso files with alternate file extensions other than [code].lasso[/code] or [code].LassoApp[/code], perform the procedure below. [/p]

To configure WebSTAR to process alternate file extensions with Lasso:

1. Launch the 4D WebSTAR Admin Client application and connect to the 4D WebSTAR Admin Server.

2. To make global changes to all Web sites, select the[code] Admin[/code] option from the list of available virtual hosts. Otherwise, select [code]DefaultSite[/code] (or another virtual host).

3. Select the[code] Select [/code]button.

3. Select [code]Suffix Mappings[/code] option from the [code]Web Server [/code]section on the left panel of the [code]Administration[/code] window.

4. In the [code]Editable Suffix Mappings[/code] panel, add as many suffix mappings as necessary by specifying the filename extension, MIME type, and choosing the [code]Lasso[/code] action from the popup menu at the bottom of the window.

5. When finished, select the [code]Save[/code] button to save the changes.

Remote WebSTAR V Configuration

[p]This section describes setting up Lasso Professional Server in a distributed architecture where Lasso Service runs on a separate Mac OS X computer from the WebSTAR V server[code].[/code] [/p]

To setup Lasso Connector for WebSTAR V on a remote server:

1. On the machine running Lasso Service, stop Lasso Service using the [code]stopLassoService.command[/code] file in the [code]Lasso Professional Server/Tools[/code] folder.

2. On the machine running Lasso Service, stop WebSTAR V if it is running. Since the Lasso Connector for WebSTAR V 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]Lasso8ConnectorforWebSTAR.bundle [/code]file and move it into the [code]4DWebSTAR/WebServer/Plug-Ins[/code] folder on the remote server.

4. On the machine running Lasso Service, locate the hidden [code]Lasso8WebSTAR.conf[/code] file in the [code]/etc/lasso[/code] folder, and copy it to the [code]/etc/lasso[/code] folder on the remote Web server.

5. On the remote server, open the copied [code]Lasso8WebSTAR.conf[/code] file in the Pico file editor using the following command:

[pre]sudo pico /etc/httpd/users/Lasso8WebSTAR.conf [/pre]

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

7. Press [code]Ctrl-X[/code]. This will ask you if you want to save the file.

8. Enter[code] y[/code]. This saves and closes the file.

9. On the remote Web server, launch WebSTAR V.

10. On the machine running Lasso Service, start Lasso Service using the [code]startLassoService.command[/code] file or [code]consoleLassoService.command[/code] file, as described in the Running Lasso Professional Server section of this chapter.

[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]Lasso [/b][b]User Note[/b]: The Lasso Professional Server installer creates a hidden [code]Lasso[/code] user in Mac OS X that is used to read, write, and execute files related to Lasso Professional Server. This user is installed automatically, and no configuration for this user is required. Do not attempt to configure or change the settings for this user as it will affect the functionality of Lasso Professional Server. For more information about the [code]Lasso[/code] user, see the [code]Mac OS X Tips.pdf[/code] file. [/note]

Application Files

[p]Lasso Professional Server installs the following files and folders in the [code]Applications/Lasso Professional Server[/code] folder on the Mac OS X 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. 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], [code]License Agreement.txt[/code], and [code]Mac OS X Tips.pdf[/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 folder – Contains an installation of ImageMagick, which is 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.
• [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.
• LassoAdmin 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 Site Administration Utilities chapter.
• [code]Lasso8Service.sh [/code]–[code] [/code]This is the “watchdog” script for Lasso Professional Server. This file continuously queries Lasso Service to make sure that it is running when it is supposed to be, and automatically restarts Lasso Service if it inadvertently quits. When it does this, a log entry is added to the standard system log file (traditionally [code]/var/log/system.log[/code]) in Mac OS X. If the number of restarts exceeds 20 per hour, the script stops attempting to start Lasso Service until the problem is fixed manually and the machine is rebooted.

1. [note][b]Note: [/b]While Lasso Service is running, the [code]Lasso8Service.sh[/code] file will temporarily place a file named [code]LassoService8.pid[/code] in the [code]/tmp/[/code] folder. This file is a helper file for [code]Lasso8Service.sh[/code]. [/note]

• 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.dylib [/code]– Data source connector module for FileMaker Pro data sources.
• [code]FMSAConnector.dylib [/code]– Data source connector module for FileMaker Server data sources.
• [code]ImageTag.dylib[/code] – Implements support for the image tags..
• [code]LDAPConnector.dylib[/code] – Implements support for querying LDAP data sources.
• [code]LJAPI.dylib[/code] – Implements core support for all LJAPI modules and includes the data source connector for JDBC data sources.
• [code]LJAPI.jar[/code] – Implements core support for all LJAPI modules.
• [code]MySQLConnector.dylib[/code] – Data source connector module for MySQL data sources.
• [code]NSLookup.class[/code] – Java class file for [code][NSLookup][/code] tag.
• [code]OpenBaseConnector.dylib[/code] – Data source connector module for OpenBase data sources.
• [code]PDF.jar[/code] – Required library for the [[code]PDF_…][/code] tags.
• [code]SpotlightConnector.dylib[/code] – Implements support for querying the spotlight disk indexing in Mac OS X 10.4/10.5.
• [code]SQLConnector.dylib[/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 Connector for SQLite. This is built into the core Lasso Service code. [/note]

• Lasso8Service – [code]Lasso8Service[/code] 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.
• LassoSites folder – Contains the site level folders for each site that has been created. By default contains a default-1 folder for the default site. This folder contains most of the same folders as the Lasso Professional Server application folder (called the master level). In general, the site level is checked before the master level when Lasso needs to find a resource.
• 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.
• Tools folder – Contains Mac OS X terminal command files for performing various tasks with Lasso Professional Server. These command files allow users to perform tasks using the terminal by simply double-clicking on the command files.
• [code]consoleLassoService.command[/code] – Starts Lasso Service as an application in the terminal. Useful for viewing the startup log and troubleshooting. For instructions on how to use this file, see the Running Lasso Professional Server section of this chapter.
• [code]startLassoService.command[/code] – Starts Lasso Service via the terminal. For instructions on how to use this file, see the Running Lasso Professional Server section of this chapter.
• [code]stopLassoService.command[/code] – Stops Lasso Service via the terminal. For instructions on how to use this file, see the Running Lasso Professional Server section of this chapter.

StartupItems

[p]The [code]Library/StartupItems [/code]folder contains files that are used to auto-start Lasso Service at boot time. [/p]

• [def]LassoPro8[/def] – Contains the [code]LassoPro8[/code] and [code]StartupParameters.plist[/code] files which are used to auto-start Lasso Service at boot time.

Framework

[p]The [code]Library/Frameworks [/code]folder contains the [code]Lasso.Framework[/code]. [/p]

• [def]Lasso.Framework[/def] – Contains code that Lasso Service needs to execute properly. Most of Lasso’s functionality is implemented within this framework.

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]

System Files

[p]Lasso Professional Server installs the following files in various system locations on the Mac OS X hard drive. [/p]

[note][b]Note: [/b]These files are hidden unless viewed in the terminal application, or via a file editor capable of viewing hidden system files. [/note]

• [def]Lasso8ConnectorforApache.so[/def] – This file is the Lasso Web server connector for Apache 1.3, which is installed in the in [code]/user/libexec/httpd[/code] folder for default installations of Mac OS X 10.4 or Mac OS X 10.3.9.
• [def]Lasso8ConnectorforApache2.2.so[/def] – This file is the Lasso Web server connector for Apache 2.2, which is installed in the in [code]/user/libexec/apache2[/code] folder for default installations of Mac OS X 10.5 or Mac OS X Server 10.5.
• [def]Lasso8ConnectorforApache2.so[/def] – This file is the Lasso Web server connector for Apache 2, which is installed in different locations if one of the Apache 2 options is selected during installation.
• [def]Lasso8ConnectorforWebSTAR.bundle[/def] – This file is the Lasso Web server connector for WebSTAR V, which is installed in the WebSTAR [code]Plug-Ins[/code] folder if the option is selected during installation.
• [def]lasso8.conf[/def] – Lasso Professional Server adds an Apache configuration file to the [code]/etc/httpd/users[/code] folder. This file is dynamically included in the main Apache configuration file ([code]httpd.conf[/code]).
• [def]lasso8apache.conf[/def] – The Web server configuration file for the Apache connectors, located in the [code]/etc/lasso[/code] folder.
• [def]lasso8webstar.conf[/def] – The Web server configuration file for [code]Lasso Connector for WebSTAR[/code], located in the [code]/etc/lasso[/code] folder.
• [def]• [/def][def]ICU Libraries[/def] – These required files are installed to the [code]/private/tmp/lassoicu/[/code] folder. These are necessary for Unicode support.

Uninstalling Lasso Professional Server

[p]Lasso Professional Server should be uninstalled using the uninstaller application provided as part of the Lasso Professional Server package. Following the procedure below will ensure that all custom settings and databases will be preserved. [/p]

To uninstall Lasso Professional Server:

1. Perform an export of your current Server Administration settings using the Setup > Site > Import/Export section of Server Administration. Save the exported file somewhere on your hard drive.

1. Double-click the [code]Lasso Pro 8 Uninstaller.mpkg[/code] application. This launches the [code]Lasso Professional Server[/code] window. An authentication dialog will prompt for an administrator name and password.

2. Enter the username and password of a Mac OS X user on the machine who has administrative rights.

3. Select [code]Continue[/code]. This will display special information about what the unintaller will do.

4. Select [code]Continue[/code], then select the drive you wish to uninstall Lasso Professional Server from.

7. Select [code]Continue[/code] button, then select [code]Upgrade[/code]. This will remove Lasso Professional Server from your system.

8. Select [code]Quit[/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 setup files, 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]Applications/Lasso Professional Server[/code] folder is left on the 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]