1. Now that you have checked the certificate file, you can import it using the keytool utility. To do this, type the following command at the command prompt:
keytool -import -v -trustcacerts -file
<name_of_file.cert.cer> -keystore
<Tomcat_Dir\conf\loskeystore>-alias
<ALIAS_NAME>
NOTE: Replace <name_of_file.cert.cer> with the path and name of the new certificate file.
Replace <ALIAS_NAME> with the server alias that you used on the SSL Certificate Configuration window during installation.
2. When asked for a password, type the same one that you inserted during install to generate the SSL key certificate.
3. When asked, “Trust this certificate? [no]:”, type “y” or “yes”.
4. For more information, please refer to the Certificate Authority's site for support or documentation.
I NSTALL MS O UTLOOK
I NTEGRATION
This step is optional. MS Outlook integration allows users to access LiquidOffice forms from MS Outlook.
1. Make sure you have the appropriate software.
Outlook Integration requires:
• Windows XP
• Outlook 2003
2. Go to the extras/looutlook directory of your LiquidOffice Server after installation. There are two files in the looutlook directory.
• http://MyLiquidOfficeServer/extras/
looutlook/config.ini
• http://MyLiquidOfficeServer/extras/
looutlook/LOutlook.msi
3. The config.ini and LOutlook.msi files must both be in the same directory on a network share.
4. Open the config.ini file and edit ServerURL:
http://myserver.mydomain.com/ to the appropriate URL(s) of the LiquidOffice server(s) that will integrate with MS Outlook.
5. Open the LOutlook.msi file to run the installation after the config.ini file has been properly edited.
An administrator has the option to allow clients to install via network installation or to push the install to a group of clients using group policies.
62 Installing Service Packs
I NSTALLING S ERVICE P ACKS
See the following sections for detailed information on installing Service Packs to different operating systems and platforms:
• All Cluster Updates
• Windows
• Solaris
• Linux
• WebLogic on page 66
• WebSphere on page 67
All Cluster Updates
The following requirements must be met when installing a Service Pack to a cluster, regardless of the operating system/platform:
1. All members of the server cluster must be offline before the service pack installer is run.
2. The LiquidOffice Database must be accessible when installing to a server cluster.
3. The service pack must be run on ALL servers in the cluster.
Windows
1. Double-click the .exe file in the LiquidOffice/
Server/Windows directory on the install disc or in the directory to which the Service Pack was downloaded.
2. The Service Pack will be installed. Follow any instructions from install in regard to restarting the server(s).
Solaris
1. Install the latest Solaris OS patches.
2. Go to the Server — Solaris directory of the disc or the directory to which the update was downloaded.
3. Type “sh loserver<version#>_sp<#>.bin LAX_VM /<original server installation location>/jre/bin/java” to launch the install program.
4. The update will be installed. Follow any
instructions from the install in regard to restarting the server(s).
5. Log out and log back in as root.
6. Run the los_post.sh script located in the xmlserver directory.
Linux
1. Install the latest Linux OS patches.
2. Go to the Server — Linux directory of the disc or the directory to which the update was downloaded.
3. Type “sh loserver<version#>_sp<#>.bin LAX_VM /<original server installation location>/jre/bin/java” to launch the install program. For example, you might type sh loserver40.bin LAX_VM /usr/local/cardiff/
liquidoffice/server/jre/bin/java.
4. The default location of the LiquidOffice Server is:
“/usr/local/cardiff/liquidoffice/xmlserver”.
1. Log out and log back in as root.
2. Run the los_post.sh script located in the xmlserver directory.
3. Run the service iptables save command.
WebLogic
Before installing a Service Pack, you must disable the lopserver.war file.
1. Login to the BEA WebLogic Administration Console.
2. In the upper left hand corner click the Lock & Edit button under the Change Center heading.
3. Click Deployments in the left hand navigation bar.
4. In the right hand window select lopserver and click the Delete button.
5. When the Delete Application Assistant screen appears in the right window, click Yes.
6. At the next screen in the upper left hand corner click the Activate Changes button under the Change Center heading.
7. The lopserver.war file will be disabled.
8. You will need to redeploy the lopserver.war file after the Service Pack or Hotfix has been installed.
For instructions on how to redeploy the lopserver.war file, see Deploy on WebLogic on page 58.
WebSphere
Before installing a Service Pack, you must disable the lopserver.war file.
1. Login to the WebSphere Administrative Console.
2. Click on Applications in the left hand navigation menu, then click on Enterprise Applications.
3. Mark the checkbox to select the lopserver application.
4. Click Stop.
5. Mark the checkbox to select the lopserver application again.
6. Click Uninstall.
7. At the Uninstall Application page, click OK. It may take a moment for the uninstall to complete.
8. Once the uninstall is complete, click Save in the Messages box at the top of the page at the next page.
9. Close the Administrative Console.
10. The lopserver.war file will be disabled. You will need to redeploy the lopserver.war file after the Service Pack or Hotfix has been installed. For instructions on how to redeploy the lopserver.war file, see Deploy on WebSphere on page 59.
64 Uninstalling
U NINSTALLING
This section covers the following topics:
• Uninstalling on Windows
• Uninstalling on Solaris and Linux
Uninstalling on Windows
1. Shut down the LiquidOffice Server.
2. Select Cardiff LiquidOffice Server from the Add/Remove Programs window.
3. The InstallAnywhere Uninstaller screen appears.
4. Click Uninstall.
5. The Uninstall Complete dialog appears.
6. Click Done.
7. Any items not removed will be listed on the Uninstall LiquidOffice Server dialog. These files should be deleted manually if you plan to reinstall LiquidOffice.
8. Manually delete any directories that were not removed by the uninstall.
Uninstalling on Solaris and Linux
1. Login as ROOT.
2. Shut down the LiquidOffice Server.
3. Run the los_post_remove.sh script.
4. At the Command Line, type:
<server_home>/uninstall 4.1 Then type:
sh uninstall
5. The InstallAnywhere Uninstaller screen appears.
6. Click Uninstall.
7. The Uninstall Complete dialog appears.
8. Click Done.
9. Any items not removed will be listed on the Uninstall LiquidOffice Server dialog. These files should be deleted manually if you plan to reinstall LiquidOffice.
10. Manually delete any directories that were not removed by the uninstall.
66 Uninstalling
CHAPTER 4 Silent Installation
A BOUT THIS C HAPTER
This section covers the following topics:
• What is a Silent Install?
• Silent Install of LiquidOffice Form Designer on page 68
• Silent Install of the LiquidOffice Server on page 69
• Silently Installing Service Packs and HotFixes on page 73
• Silent Uninstallation on page 73
• Moving Server to Production on page 74
W HAT IS A S ILENT I NSTALL ?
A Silent Install is controlled by a response file. During the installation, no user input is required. All settings will be configured based on the contents of the response file.
Silent Uninstallation and Cluster Warning
The Silent Install protocol can also be used to uninstall LiquidOffice Server. In a single-server application, there is no limitation to the use of the “Silent” option.
However, a Cluster Server can be adversely affected if a “Silent” uninstall is performed incorrectly.
If the Silent Uninstall begins removing LiquidOffice Server from the “first” server in the cluster, it will also wipe out the Shared Resources directory on that server.
Any servers in the cluster that you intended to remain operational will fail without this directory. Therefore, you should make sure that the Silent Uninstall option targets the appropriate servers in the cluster. You may want to use the standard Uninstall program, which prompts you to remove or leave the Shared Resources
68 Silent Install of LiquidOffice Form Designer
S ILENT I NSTALL OF L IQUID O FFICE
F ORM D ESIGNER
To perform a silent install you will first need to create a response file by running through the installation process manually. The response file must then be placed on the machine where the silent install will be run.
NOTE: Java 2 Runtime Environment 1.4.2 must be installed.
Creating a Response File
1. Open the Command Prompt and type the location of the SETUP file in the Bin directory on the LiquidOffice disc, followed by the -r command
EXAMPLE:
Bin\setup.exe -r 2. You will be asked to run through the setup
manually and the response file will be created once the manual setup is complete.
3. The response file, SETUP.ISS, will be located in the Windows directory (C:\Windows\setup.iss) for Windows XP or in the WINNT
(C:\WINNT\setup.iss) directory for Windows 2000.
Launching a Silent Install
To run the response file and launch a silent install:
1. Place the setup.iss file in a custom directory on the machine you want to run a silent install on.
EXAMPLE: C:\temp\setup.iss
2. Open the Command Prompt and type the location of the SETUP file on the LiquidOffice disc, followed by the -r and the -f1 command. The -f1 command should be followed by the location of the setup.iss file.
EXAMPLE: Bin\setup.exe -r -f1 C:\temp\setup.iss
3. To add a log file, add f2C:\temp\setup.log to the above command.
Bin\setup.exe -r -f1 C:\temp\setup.iss f2
C:\temp\setup.log
4. The above command will place a log file in the C:\temp directory. If the Result Code in the log file is 0 then the install was successful. If the result code in the log file is a negative number then the install failed. For more information go to:
http://support.installshield.com/
S ILENT I NSTALL OF THE
L IQUID O FFICE S ERVER
See these sections before proceeding with a Silent Install:
• Before Installation on page 32
• Before Installing to a Cluster on page 40 In addition to using the installer, you can install the LiquidOffice Server in silent mode.
There are 5 steps to this process: