Chapter 5
Configuring on Linux

[p]This chapter contains the installation and configuration instructions for Lasso Professional Server on Red Hat Enterprise Linux 4. 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.
• Required Packages lists the packages that Lasso Professional Server requires.
• 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, these 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.)
• Standard installation of Red Hat Enterprise Linux 4 with network support.
• Red Hat Linux installation of Apache Web Server 2 (included with Red Hat Enterprise Linux 4).
• Sun’s Java Runtime Environment (JRE) 6 for Red Hat Linux is required for Java-based tags and JDBC data sources to function. Installation instructions are included below.

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

[note][b]Certification [/b][b]Note:[/b] Lasso Professional Server is certified to work with Red Hat Enterprise Linux version 4 with the default installation of Apache Web server 2. Modified versions of any required components may work with Lasso Professional Server, but can not be officially supported. [/note]

Required Packages

[p]Several packages are required in Red Hat Enterprise Linux 4 for all features in Lasso Professional Server to function. Many of these packages should be installed with server installations of Red Hat Enterprise Linux 4 by default. The required packages are summarized in the following table. [/p]

[p]To view a list of packages that are required by the Lasso Professional Server installer, execute the following command in the terminal. The following command assumes you are currently in the same folder as the Lasso Professional Server installer. [/p]

[pre]rpm -qpR Lasso-Service-8.5.0-1.i386.rpm [/pre]

[p]If a package requirement is not met, then the [code]Lasso-Service-8.5.0-1.i386.rpm[/code] file will indicate the packages that are missing upon installation. These packages may be installed from the Red Hat Enterprise Linux 4 installation CDs, or may be downloaded from URLs indicated in the release notes. [/p]

Required Packages

[p]Lasso requires the following packages be installed before Lasso’s RPMs are installed. All RPMs are provided by the Red Hat Enterprise Linux 4 installation CDs or the Red Hat Enterprise 4 Extras CD (Bonus Disc). The [code]java-1.4.2-ibm[/code] RPMs in particular are provided on the Red Hat Enterprise Linux Extras CD. [/p]

Table 1: Lasso Service Required Packages

[table][tr][th]Package[/th][th]Version[/th][th] [/th][/tr]

[tr][td]bzip2-libs[/td][td]1.0.2 [/td][/tr]

[tr][td]curl[/td][td]7.12.1 [/td][/tr]

[tr][td]e2fsprogs[/td][td]1.35 [/td][/tr]

[tr][td]freetype[/td][td]2.1.9 [/td][/tr]

[tr][td]glibc[/td][td]2.3.4 [/td][/tr]

[tr][td]krb5-libs[/td][td]1.3.4 [/td][/tr]

[tr][td]libgcc[/td][td]3.4.3 [/td][/tr]

[tr][td]libidn[/td][td]0.5.6 [/td][/tr]

[tr][td]libjpeg[/td][td]6b [/td][/tr]

[tr][td]libstdc++[/td][td]3.4.3 [/td][/tr]

[tr][td]libtiff[/td][td]3.6.1 [/td][/tr]

[tr][td]libtool-libs[/td][td]1.5.6 [/td][/tr]

[tr][td]libxml2[/td][td]2.6.16 [/td][/tr]

[tr][td]libxslt[/td][td]1.1.11 [/td][/tr]

[tr][td]openssl[/td][td]0.9.7a [/td][/tr]

[tr][td]pcre[/td][td]4.5 [/td][/tr]

[tr][td]xorg-x11-libs[/td][td]6.8.1 [/td][/tr]

[tr][td]zlib[/td][td]1.2.1.2 [/td][/tr]

[/table]

Table 2: Lasso Connector for Apache 2 Required Packages

[table][tr][th]Package[/th][th]Version[/th][th]Notes [/th][/tr]

[tr][td]httpd[/td][td]2.0.52 [/td][/tr]

[tr][td]libstdc++[/td][td]3.4.3 [/td][/tr]

[tr][td]glibc[/td][td]2.3.4 [/td][/tr]

[tr][td]libgcc[/td][td]3.4.3 [/td][/tr]

[/table]

[p]See also the Installation Instructions that follow for notes about some specific packages that need to be installed. [/p]

Web Browser Requirements

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

• Konquerer 3.0 or higher, FireFox, or compatible browser.
• Javascript enabled.
• Cookies enabled.
• Cascading Style Sheets support.
• Monitor capable of 800 x 600 resolution.

[p]If these criteria are not met, then a browser check dialog box will be shown when trying to access Lasso 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 Lasso Administration for the first run. This section will introduce the following: [/p]

• Installing Java describes installing the Java components necessary for Lasso Professional Server’s 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 when running for the first time.

Installing Java

[p]This section discusses installing Sun’s Java Runtime Environment (JRE) 6 for Red Hat Linux. JRE 6 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 not necessary to install Java if these features will not be used. [/p]

To install JRE 6:

1. Download Sun’s JRE installer for Linux at the following URL. Download the “Linux RPM in self extracting file” e.g. j[code]re-6-linux-i586-rpm.bin[/code].

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

2. Use the following commands to decompress and install the RPM:

[pre]chmod a+x jre-[code]6-linux-i586-rpm[/code].bin
sudo ./jre-[code]6-linux-i586-rpm[/code].bin
sudo rpm -ivh jre-[code]6-linux-i586-rpm[/code].bin [/pre]

[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 Lasso Administration. See the Setting Site Preferences chapter Java section for more information. [/p]

Alternate JRE Versions

[p]Lasso will look in the following location for the latest installation of Java. If a different version of Java is installed then a symlink can be created to select what version of Java Lasso finds. Lasso expects to find [code]libawt.so[/code], [code]libjava.so[/code], and [code]libverify.so[/code] in this directory and [code]libjvm.so[/code] in a [code]server[/code] subdirectory. [/p]

[pre]/usr/java/latest/lib/i386/ [/pre]

[note][b]Certification [/b][b]Note[/b]: While versions of Java other than JRE 6 may work with Lasso Professional Server, not all can be officially supported. [/note]

Installing Lasso Professional Server

[p]The Lasso Professional Server installer for Red Hat Linux is distributed as three RPM files. These must be installed from the Red Hat Linux command line or console application. [/p]

• Lasso-Service-8.5.0-1.i386.rpm – This package will install the Lasso Service and Modules as all support files for Lasso Professional Server 8. This does not install the Web Server connector or the documentation for Lasso Professional Server.
• Lasso-Documentation-8.5.0-1.i386.rpm – This package will install the documentation and source files for LassoApps and Modules.
• Lasso-Apache2Connector-8.5.0-1.i386.rpm – This package will install the appropriate files and configure Apache 2 to connect to Lasso Professional Server 8.

[p]The RPMs will install all required files for Lasso Professional Server, and will automatically start Lasso Service and Apache upon completion. [/p]

To install Lasso Professional Server:

1. Copy the three Lasso rpm files ([code]Lasso-Service-8.5.0-1.i386.rpm[/code], [code]LassoDocumentation-8.5.0-1.i386.rpm[/code], Lasso-[code]Apache2Connector-8.5.0-1.i386.rpm[/code]) to the Red Hat Linux hard drive into the same folder. These files are unpacked from the [code]Lasso_Pro_8_Linux.tar.gz[/code] archive along with the release notes.

2. Log in as the root user of the Red Hat Linux machine. This is done by entering [code]su[/code] in the command prompt, then entering the root password. The hyphen loads the environment for the root user in the resulting shell.

[pre]su - [/pre]

3. Install the Lasso packages. This can be accomplished using the following shortcut or with individual commands for each RPM file.

• Enter the following command to install all three packages for Lasso Professional Server. The [code]rpm[/code] command is called with the [code]-i[/code] command to perform an install, the [code]-v[/code] command for verbose feedback, and [code]-h[/code] command to display a progress indicator.

[pre]rpm -ivh Lasso*.rpm [/pre]

• Enter the following commands to install each package for Lasso Professional Server. The [code]rpm[/code] command is called with the [code]-i[/code] command to perform an install, the [code]-v[/code] command for verbose feedback, and [code]-h[/code] command to display a progress indicator.

[pre]rpm -ivh Lasso-Service-8.5.0-1.i386.rpm
rpm -ivh Lasso-Documentation-8.5.0-1.i386.rpm
rpm -ivh Lasso-Apache2Connector-8.5.0-1.i386.rpm [/pre]

[p]After Lasso Professional Server is installed and Lasso Service is successfully started, a message will appear with a URL address for initializing Lasso Professional Server in a Web browser. This is described in the next section. [/p]

Initialization

[p]The Initialize Web page is where the administrator enters the Lasso Professional Server serial number, and sets the global administrator username and password for the first time. [/p]

To launch the Initialize page:

1. Launch a Web browser application. See the System Requirements section earlier in this chapter for Web browser requirements in Red Hat Linux.
2. [note][b]Web [/b]Browser Note: Because Lasso Administration is Web-based, initialization and administration of Lasso Professional Server can be performed from a separate machine and operating system from the installation. [/note]

2. If on the same machine as the Lasso Professional Server installation, go to the following URL.

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

• If on a different machine from the Lasso Professional Server installation, go to the following URL. Replace [code]www.example.com[/code] with the domain name or IP address of the server running Lasso Professional Server.

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

1. [note][b]Troubleshooting: [/b]In the event the Lasso Initialization 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, make sure that Apache is running, and that the installer was able to successfully edit the Apache configuration file ([code]httpd.conf[/code]) as described in the Extended Configuration > Lasso Connector for Apache section of this chapter. [/note]

Initializing Lasso Professional Server

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

Figure 1: Server Initialize Page

[p]For evaluation versions of Lasso Professional Server, an evaluation serial number is required to complete initialization. To request an evaluation serial number, select the Request Evaluation Serial Number button. This will take you to the LassoSoft Web site, where an evaluation serial number can be obtained. 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 Serial Number field. This must be entered exactly as it appears in your LassoSoft invoice using the following format:

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

• Serial numbers are case-sensitive. Make sure that all capitalization is correct and that all letters and numbers are entered, including the LP8.5 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. 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 Apache Web server. Lasso Service is started and stopped using the [code]lasso8ctl[/code] command or the shell scripts provided in the [code]/usr/local/Lasso Professional 8/Tools[/code] folder. [/p]

To start Lasso Service:

[p]Log in as the root user of the Red Hat Linux machine. This is done by entering [code]su[/code] in the command prompt, then entering the root password. [/p]

[pre]su - [/pre]

• Use the [code]lasso8ctl[/code] command to start Lasso Service.

[pre]/usr/sbin/lasso8ctl start [/pre]

• Alternately, [code]cd[/code] into the [code]Tools[/code] folder and run the [code]startLassoService.sh[/code] shell script.

[pre]cd "/usr/local/Lasso Professional 8/Tools"
./startLassoService.sh [/pre]

[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]Log in as the root user of the Red Hat Linux machine. This is done by entering su in the command prompt, then entering the root password. Then cd into the Tools folder and run the consoleLassoService.sh shell script. [/p]

[pre]su -
cd "/usr/local/Lasso Professional 8/Tools"
./consoleLassoService.sh [/pre]

[p]The terminal window contains all of the output of the Lasso Service console. Closing the shell 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. [/p]

[pre]/usr/sbin/lasso8ctl[code] restart[/code] [/pre]

To start Lasso Service:

[p]Log in as the root user of the Red Hat Linux machine. This is done by entering su in the command prompt, then entering the root password. [/p]

[pre]su - [/pre]

• Use the [code]lasso8ctl[/code] command to stop Lasso Service.

[pre]/usr/sbin/lasso8ctl stop [/pre]

• Alternately, [code]cd[/code] into the [code]Tools[/code] folder and run the [code]stopLassoService.sh[/code] shell script.

[pre]cd "/usr/local/Lasso Professional 8/Tools"
./stopLassoService.sh [/pre]

To see if Lasso Service is running:

[p]Log in as the root user of the Red Hat Linux machine. This is done by entering su in the command prompt, then entering the root password. [/p]

[pre]su - [/pre]

• Use the [code]lasso8ctl[/code] command to check whether Lasso Service is running.

[pre]/usr/sbin/lasso8ctl status [/pre]

• Alternately, run the following command to check for Lasso Service in the list of current processes.

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

[note][b]Note: [/b]More than one [code]Lasso8Service[/code] process will be shown due to the fact that Lasso Service is multi-threaded. Once Lasso Service is stopped using [code]lasso8ctl[/code] or the [code]stopLassoService.sh[/code] file, all [code]Lasso8Service[/code] threads are killed. [/note]

Extended Configuration

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

• 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).
• 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 Apache

[p]Lasso Connector for Apache is the default Web server connector included with Lasso Professional Server for Red Hat Linux. 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 these settings changes. [/p]

[p]The Lasso Professional Server installer will automatically perform all necessary changes to the [code]/etc/httpd/conf/httpd.conf[/code] file via an included [code]lasso.conf[/code] file. After the altering the [code]httpd.conf[/code] file to include the lasso.conf file, the installer makes a backup of the original file named [code]httpd.conf.lassobackup[/code]. The following procedure describes viewing the changes the Lasso Professional Server installer makes to the Apache configuration file. [/p]

To view changes made to the Apache configuration file:

1. Log in as the root user of the Red Hat Linux machine. This is done by entering su in the command prompt, then entering the root password.

[pre]su - [/pre]

2. At the command prompt, enter the following to open the [code]lasso.conf[/code] file in the VI text editor.

[pre]vi /etc/httpd/conf/lasso8.conf [/pre]

3. This file should contain the following lines:

[pre]LoadModule lasso8_module modules/Lasso8ConnectorforApache2.so
AddHandler lasso8-handler lasso
AddHandler lasso8-handler lassoapp [/pre]

• The [code]AddHandler[/code] lines tell Apache to process files with the extensions [code].lasso[/code] and [code].lassoapp[/code] with Lasso Service.

1. [note][b]File [/b][b]Extensions Note[/b]: Apache can be set up to process alternate file extensions with Lasso Service by adding additional lines using the following format: [code]AddHandler lasso-handler extension[/code]. Replace extension with the file extension you wish to be processed by Lasso Service (e.g. [code]htm[/code], [code]html[/code], etc.). [/note]

4. Save the [code]lasso8.conf[/code] file.

5. Restart Apache Web Server for any changes to take place. This is done by entering the following at the command prompt:

[pre]/usr/sbin/apachectl restart [/pre]

Remote Apache Configuration

[p]This section describes setting up Lasso Professional Server in a distributed architecture where Lasso Service runs on a separate Red Hat Linux machine from the Red Hat Linux 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 stopLassoService.sh 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 Lasso Administration) should no longer be served from this machine.

3. On the machine running Lasso Service, move the Lasso folder from the Web server root folder (e.g. [code]/usr/www/html[/code]) to the Web server root folder on the remote server.

4. On the machine running Lasso Service, locate the [code]/etc/httpd/conf/lasso8.conf[/code] file and move it into the [code]/etc/httpd/conf/[/code] folder on the remote server.

5. On the machine running Lasso Service, locate the [code]/etc/httpd/modules/Lasso8ConnectorforApache2.so[/code] file and move it into the [code]/etc/httpd/modules[/code] folder on the remote server.

6. On the machine running Lasso Service, locate the [code]/etc/lasso/lassoapache.conf[/code] file and move it into the [code]/etc/lasso[/code] folder on the remote server.

7. On the remote Web server, log in as the root user of the Red Hat Linux machine. This is done by entering [code]su[/code] in the command prompt, then entering the root password.

[pre]su - [/pre]

8. At the command prompt, enter the following to open the [code]httpd.conf[/code] file in the VI text editor:

[pre]vi /etc/httpd/conf/httpd.conf [/pre]

9. Add the following line to the end of the Apache configuration file ([code]httpd.conf[/code]):

[pre]Include /etc/httpd/conf/lasso.conf [/pre]

10. Save and close the [code]httpd.conf[/code] file.

11. At the command prompt, enter the following to open the [code]lassoapache.conf[/code] file in the VI text editor:

[pre]vi /etc/lasso/lasso8apache.conf [/pre]

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

13. Save and close the [code]lasso8apache.conf[/code] file.

14. On the remote server, restart Apache Web Server. This is done by entering the following command in the terminal:

[pre]/usr/sbin/apachectl restart [/pre]

15. On the machine running Lasso Service, start Lasso Service. This can be done using the [code]lasso8ctl[/code] start command or the [code]startLassoService.sh [/code]shell script described in the Running Lasso Professional Server section of this chapter.
16. [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 lasso (lowercase) user and group account in Red Hat Linux 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. [/note]

Application Files

[p]Lasso Professional Server installs the following files and folders in the[code] /usr/local/ Lasso Professional 8[/code] folder on the Red Hat Linux 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 6.2.9, 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.so [/code]– Data source connector module for FileMaker Pro data sources.
• [code]FMSAConnector.so [/code]– Data source connector module for FileMaker Server data sources.
• [code]ImageTag.so[/code] – Implements support for the image tags..
• [code]LJAPI.so[/code] – Implements core support for all LJAPI modules and includes the data source connector for JDBC data sources.
• [code]LDAPConnector.so[/code] – Implements support for querying LDAP data sources.
• [code]LJAPI.jar[/code] – Implements core support for all LJAPI modules.
• [code]MySQLConnector.so[/code] – Data source connector module for MySQL data sources.
• [code]NSLookup.class[/code] – Java class file for [code][NSLookup][/code] tag.
• [code]OpenBaseConnector.so[/code] – Data source connector module for OpenBase data sources.
• [code]PDF.jar[/code] – Required library for the [[code]PDF_…][/code] tags.
• [code]SQLConnector.so[/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.sh[/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.sh[/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.sh[/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.

Startup Files

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

• [code]lasso8ctl[/code] – Auto-starts Lasso Service at boot time. A symbolic link to this file is also placed in [code]/etc/rc.d/init.d/[/code].

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 Red Hat Linux hard drive. [/p]

• httpd.conf – Lasso Professional Server modifies the Apache configuration file ([code]httpd.conf[/code]) located in the [code]/etc/httpd/conf[/code] folder.
• lasso8apache.conf – The Web server configuration file for Lasso Connector for Apache, located in the [code]/etc/lass[/code]o folder.
• Lasso8ConnectorforApache2.so – This file is the Lasso Web server connector for Apache, located in [code]/etc/httpd/modules[/code] folder.
• Lasso8Service.pid – This file is placed in the [code]/tmp[/code] folder while Lasso Service is running.

Uninstalling Lasso Professional Server

[p]Lasso Professional Server can be uninstalled using the procedure below. This will automatically remove all core program and system files, and is the only recommended way to uninstall Lasso Professional Server. [/p]

[note][b]Warning: [/b]The RPM will remove all files installed by the RPM, including the [code]lasso_internal[/code] database which stores all Lasso Administration settings. For preservation of settings, it is recommended that these database be backed up before uninstalling. [/note]

To uninstall Lasso Professional Server:

1. Log in as the root user of the Red Hat Linux machine. This is done by entering [code]su[/code] in the command prompt, then entering the root password.

[pre]su - [/pre]

2. Stop Lasso Service using the [code]lasso8ctl[/code] command as follows.

[pre]/usr/sbin/lasso8ctl stop [/pre]

3. Uninstall the Lasso packages. This can be accomplished using the following shortcut command to remove all Lasso packages or by removing the three Lasso packages individually.

• Enter the following command to uninstall all three packages for Lasso Professional Server. This command lists all installed rpm files, filters the list for those that contain [code]Lasso[/code], and then pipes the list to the [code]rpm[/code] program with the remove option [code]-e[/code].

[pre]rpm -qa | grep Lasso | xargs rpm -e [/pre]

• Enter the following three commands to remove each Lasso package individually. Note that the remove command does not require the version number for each package to be specified.

[pre]rpm -e Lasso-Service
rpm -e Lasso-Documentation
rpm -e Lasso-Apache2Connector [/pre]

Files and Folders Not Removed

[p]The RPM will not remove any non-default files created after the time of install. These files include new SQLite databases, Lasso log files, Lasso setups, and custom Lasso pages and LassoApps. These files remain in the following locations: [/p]

• Applications Folder – The [code]/usr/local/Lasso Professional 8[/code] folder is left on the Red Hat Linux hard drive, which contains the following folders:
• [code]Admin[/code] – Contains exported Lasso setup information, MySQL backup tables, exported text data, and LassoApp build files from Lasso Administration.
• [code]JDBCDrivers[/code] – Contains any JDBC drivers installed to Lasso Professional Server by the administrator.
• [code]LassoModules[/code] – Contains data sources connectors, Java libraries, and any customized Lasso modules.
• [code]SQLiteDBs[/code] – Contains any new SQLite databases created since the original installation.
• Web Server Root Folder – The [code]/var/www/html/[/code] 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.
• Linux Folders – The [code]/etc/lasso[/code] folder remains on the Red Hat Linux hard drive.

[p]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]

[note][b]Reinstallation [/b][b]Note:[/b] Any non-default files remaining on the system from a previous installation of Lasso Professional Server will not be overwritten by installing a newer installation. Therefore, any exported Lasso Administration settings and SQLite databases from a previous installation may be imported and used in a newer installation of Lasso Professional Server without having to move files. [/note]