ZL 6.0 Win2K32K8 32 64-Bit IG
ZL 6.0 Win2K32K8 32 64-Bit IG
2 ZL UA Installation Guide
About This Guide
The ZL UNIFIED ARCHIVE (UA) (UA) module provides organizations with the ability to
archive project files with enterprise-level capabilities.
Audience
This document is for system administrators in charge of setting up the ZL UA module.
Conventions Used
Text in Courier indicates:
Filenames, commands, and programs
Text that you enter
Text that the system displays
Words printed in italics are generic terms representing names to be devised by you.
Square brackets [] mean the material inside them is optional.
Braces {} mean that you must choose from the options listed inside them. If there is only one
option in the braces, the braces mean the option can be repeated.
If a command line does not fit across the page, a backward slash (\) appears at the end of the
line, and the command continues on the next line.
Where the following steps ask you to do something as root, log in as a normal user and then
switch to super-user mode.
ZL UA Installation Guide 3
Related Documentation
Table 1 describes the ZL UNIFIED ARCHIVE (UA) 6.0.6 documentation set.
TABLE 1.
ZLUA 6.0 Manual Exchange 2003 Archiving Configuration Describes how to configure Microsoft Exchange 2003
Guide integration with ZL UNIFIED ARCHIVAL. The procedures in
this document are prerequisites for mail administrators using
Exchange 2003 on their corporate network with ZL UA.
ZLUA 6.0 Manual Exchange 2007 Archiving Configuration Describes how to configure Microsoft Exchange 2007
Guide integration with ZL UNIFIED ARCHIVAL. The procedures in
this document are prerequisites for mail administrators using
Exchange 2007 on their corporate network with ZL UA.
ZLUA 6.0 Archiving Administration Guide Describes how to configure ZL UNIFIED ARCHIVAL for
archiving end-user mailbox and journaled mail.
ZLUA 6.0 Domino Email Server Configuration Guide Describes how to configure Lotus Domino Server integration
with ZL UNIFIED ARCHIVAL. The procedures in this
document are prerequisites for mail administrators using
Domino Server on their corporate network with ZL UA.
4 ZL UA Installation Guide
Table of Contents
Chapter 1: Installation Overview .............................................................................7
Required Software ...............................................................................................................................7
Windows ..........................................................................................................................................7
Installation Checklist ...........................................................................................................................8
ZL UA Installation Guide 5
Appendix A: Encrypting Your Database Password ............................................ 37
6 ZL UA Installation Guide
Chapter 1
Installation Overview
This guide provides you with the procedures you need to follow to install the ZL UA server
core and associated components. When you are finished, using this guide, you will have your
ZL UA system operational and ready to manage your mail servers.
To install ZL UNIFIED ARCHIVE (UA):
1. Choose a Hardware configuration according to the guidelines set in Technical Note: ZL UA
System Requirements.
2. Make sure you have all software defined in the “Required Software”section shown below.
3. Install the ZL UA server software and all the necessary additional components as described
in "Installing ZL UA on Windows,” on page 9.
Required Software
The following software and versions are required for Windows 2003:
ZL UNIFIED ARCHIVE (UA), Version 6.0.6, distributed as ZLTI-V6.0.6-b198.zip
ZL UA OEM software package, distributed as ZL_OEM_Components_CD.zip
Apache Tomcat v5.5.20 or higher, including connectors to all standard Web servers
including IIS and Apache – ZL UA can support other servlet containers, but this guide
only discusses Tomcat.
KeyView v10.4.0.1 to parse attachments
Microsoft Internet Information Services (IIS), Version 6
Sun JDK v1.6.0_04 or higher – The Sun Java SE Development Kit (JDK), Version 6, can be
downloaded from http://java.sun.com/javase/downloads/index.jsp.
You must have obtained the ZL_OEM_Components_CD.zip file, which is available for download
from ZL TECHNOLOGIES Support. You should unzip this file to a temporary directory, which
will be referred to as %ZL_OEM_DIR%.
Windows
ZL UA runs on Windows 2003 (32 bit and 64 bit) servers. ZL TECHNOLOGIES recommends
you update your system with the latest stable service packs and updates, but this is not necessary
for running the software. Install IIS 6 if it is not already installed. Make sure that all current
SMTP listeners (such as the SMTP listener component of IIS) have been disabled on your
installation server.
If you are planning to install ZL UA on a 64-bit Windows system, you should refer to the
corresponding section of this guide.
Installation Checklist
These are the steps you must follow when installing ZL UA. All of the following procedures
are described in subsequent chapters in this manual.
Install IIS
Dot Net Framework 2 SP1 or later [Applicable only for 64-bit installation]
Configure IIS
Install ZL UA Software
Configure ZL UA Applications
Installing ZL UA on Windows
This chapter contains instructions on installing ZL UA and its required 3rd party components
on Windows. Please check that version of the operating system you are using matches this target
specification:
Operating System – Microsoft Windows Server 2003
Version – Standard Edition or Enterprise Edition
Installed Updates – Latest Service Pack / updates
Server Architecture – 32-bit or 64-bit
Disk Space – 60GB or more available [C:\ - O/S - 15 GB; D:\ - Application, Mail Queue,
and Logs- 45 GB]. This size may vary for larger deployments.
Disk Drives – 2 minimum [recommended]
ZL TECHNOLOGIES recommends that you install ZL UA on a separate physical disk drive
from the server operating system. For more information, see Technical Note: ZL UA System
Requirements for additional details.
Setting up your full ZL UA server is essentially a matter of assembling the external utility and
service modules used by ZL UA, configuring them to operate with the server core, and then
installing and configuring the server core itself.
Installing the Java Virtual Machine
Installing and configuring the Tomcat JSP module
Customizing the Windows web server for ZL UA
Installing the ZL UA server components
Creating your system archive database
Installing the ZL UA service components
Starting up ZL UA for the first time and configuring the running server
Please note that this is a logical description of the layers or phases of the installation process,
not a sequential outline of the actual steps. In some cases you will install initial components of a
module, then complete the installation and configuration later in the procedure.
You must have the Windows Internet Information Services package installed and running prior
to beginning this installation procedure. Look for the Internet Information Services (IIS)
Manager in the Administrative Services menu in the Windows Control Panel.
ZL UA requires one of the server-version Java virtual machines listed in Technical Note: ZL
UA System Requirements in order to operate. The software can be downloaded from
http://java.sun.com/javase/downloads/index.jsp.
1. Download the following JDK/JSE installation package software and copy it to your server.
32-bit alone for 32-bit server architecture.
32-bit and 64-bit for 64-bit server architecture. .
2. Start the 32-bit installer and follow the installation instructions provided by Sun.
3. You will see the module selection panel. The installer includes the Java virtual machine by
default, as part of the Public JRE module. Check to make sure that this module is selected.
Make sure that the Public JRE module icon is not labeled with the “Install Upon 1st Use”
icon ( )
As shown above, you do not need to install the Demos and Samples, Source Code or Java
DB modules on your server.
Also, make note of the JDK installation folder displayed in the lower left corner. ZL UA
does not require that you install the JDK in the standard Windows location, the Program
Files folder. However, you need to make note of the exact location for Step 8 on page 11.
Click on the Next > button to continue.
5. You are next presented with a panel for installing optional modules for the JDK. Since ZL
UA does not require any of these components, you may click the Next > button again to
continue to the next step.
6. The installer now finishes copying individual components into the appropriate system
folders and the JDK installation directory.
8. At the end of the installation, set the system environment variable JAVA_HOME for 32-bit
and JAVA_HOME_32 for 64-bit server architectures respectively to the directory in which the
JDK was installed:
From the Start menu, right-click on My Computer and select Properties. Select the
Advanced tab, then select Environment Variables.
Create a new system environment variable by clicking New in the System variables box.
In the New System Variable dialog, enter JAVA_HOME (for 32-bit) or JAVA_HOME_32
(for 64-bit) as the Variable name and the JDK path as the Variable value, using the path
you noted in Step 3 on page 10. Then click OK to complete the configuration.
For example, for 32-bit, it could be C:\Program Files\java\jdk1.6.0_13 as
shown below.
Note: It is very important that this is set as a system environment variable, not as a user environment
variable. Also note that the Apache Tomcat service you will install next uses this directory to set up
its own configuration.
9. Repeat the above installation procedure by double-clicking the 64-bit JDK/JSE installer
icon (applicable only for 64-bit server architecture)
10. Set the second environment variable, applicable only to 64-bit installation, JAVA_HOME and
use the path where the second JDK/JSE is installed. For example, this could be
C:\Program Files\Java\jdk1.6.0_13.
Note: For 64-bit server architecture run normal 32-bit Tomcat installer and follow additional
instructions as follows.
If you have not already unpacked your ZL UA installation archive, as described on page 7, do
so now.
1. In your temporary directory,%ZL_OEM_DIR%, navigate to the following directory win32 F
apache F tomcat F 5.5.
2. To start the Tomcat installer, double-click on the installer icon named apache-tomcat-
5.5.20.exe. If you see an Open File - Security Warning dialog box, click Run to
proceed. Click Next > to continue, followed by I Agree to accept the license terms.
3. Select Minimum as the type of install. Also deselect Documentation and Examples, as
they are not necessary. If Service (under Tomcat) is selected, deselect that as well. Click
Next > to go to the next step.
4. Accept the default Tomcat Install Location, as provided in the example below, and make a
note of it for Step 5 on page 23.
For 32-bit
C:\Program Files\Apache Software Foundation\Tomcat 5.5
For 64-bit
C:\Program Files (x86)\Apache Software Foundation\Tomcat 5.5
Click Next > to continue.
5. Accept the default HTTP/1.1 Connector Port value 8080. Keep the default Administrator
Login User Name and set a password. Click Next > to continue the installation.
6. Check the Java Virtual Machine path and ensure it is showing a reference to a JDK/JSE
directory, not a JRE. The default typically points to a JRE. To change this, click the ... button
to browse to the path of the JVM installed on your system making sure it matches the
JAVA_HOME environment variable set previously. (For example, for 32-bit, C:\Program
Files\Java\jdk1.6.0_XX, and for 64-bit it could be C:\Program Files
(x86)\Java\jdk1.6.0_XX), Click Install to continue.
7. Deselect Run Apache Tomcat and Show Readme. Click Finish.
Installing the IIS Tomcat Connector (Jakarta ISAPI Redirector) for 32-Bit
Systems
Installing the IIS Tomcat Connector (Jakarta ISAPI Redirector) for 64-Bit
Systems
6. Return to your installation package folder in %ZL_OEM_DIR%. From the root directory, go to
win64 F apache F tomcat-connectors F jk-1.2.26. Copy the file isapi-redirect-
1.2.26.dll to the bin directory in the Jakarta installation directory, for example:
C:\Program Files\Apache Software Foundation\Jakarta ISAPI Redirector
Note that you will be overwriting existing files.
7. Go to your Jakarta installation directory, then open the bin folder. Double-click on
isapi_redirect.reg to register the 64-bit version of the redirector.
Note: In this installation, the %ZL_OEM_DIR% variable represents the ZL UA temporary installation
directory.
This section describes how to set up the base web browser interface used by ZL UA.
Effectively, you are configuring IIS to use Apache Tomcat as the generic service handler for
JSP-based web content. Later you will customize this service for ZL UA.
To configure IIS 6 for Windows 2003:
1. Run the Internet Information Services (IIS) Manager, located in the Administrative
Tools entry which can be reached from the Control Panel in the Start menu.
2. If it is not already expanded, left-click the plus sign (+) to the left of your local computer
name to expand it.
3. Add a new web service extension by right-clicking Web Service Extensions and selecting
Add a new Web service extension....
4. Enter the extension name as Jakarta ISAPI Redirector.
5. Click Add under Required files to specify the file to incorporate. For example, you would
browse to:
C:\Program Files\Apache Software Foundation\Jakarta ISAPI Redirector\bin
select isap_redirect.dll and click OK.
7. Under your local computer name, expand Web Sites F Default Web Site. Right-click on
Default Web Site and select Properties.
8. In the Default Web Site Properties window, select the Home Directory tab.
9. In the Home Directory tab, under Local path check Script source access. To the right of
Execute permissions, use the pull-down menu to select Scripts and Executables. Click
OK to save your changes. If one or more Inheritance Overrides dialog boxes appear, click
OK to continue.
10. In the IIS Manager, under your local computer name, expand Web Sites F Default Web
Site F jakarta. Select jakarta, right-click, and select Properties.
11. In the jakarta Properties window, verify that the Local path is set to:
C:\Program Files\Apache Software Foundation\Jakarta Isapi Redirector\bin
To the right of Execute permissions, use the pull-down menu to select Scripts and
Executables. Click OK to save your changes.
Unpacking ZL UA on Windows
2. Set the system environment variable ZIPLIP_HOME to the ZL installation directory. Refer to
previous example on how to set a system environment variable.
-Djava.library.path=C:\ZipLip\ZLKeyViewConvertor\bin\vdc10\FilterSDK\bin
C:\ZipLip\ZLKeyViewConvertor\bin\vdc10\ExportSDK\bin
Note: * This service is only applicable only if Mailbox management module needs to be enabled and
that too only in a Microsoft Exchange Environment. Initially this service is installed to run as Local
System account. This may need to be changed and refer to ZL Exchange Archiving configuration
and ZL Exchange administration guide for more details.
Note: ** This service is only applicable only if Mailbox management module needs to be enabled
and that too only in a Lotus Domino Server Environment. Initially this service is installed to run as
Local System account. This may need to be changed and refer to ZL Domino Email Server
configuration guide and ZL Archiving administration guide for more details.
In this file the pathname delimiters can be either forward slashes or backslashes (e.g.,
“D:\ZipLip\zlserver”
3. [For 64-bit alone] Copy the folder:
C:\Program Files (x86)\Apache Software Foundation
which containts Tomcat 5.5 and Jakarta Isapi Redirector directories into:
C:\Program Files\
Note: You will most likely overwriting or adding files, so click OK to proceed.
4. [For 64-bit alone] Copy the folder:
%ZIPLIP_OEM_DIR%\win64\win64\apache\tomcat\5.5\bin
into:
Enter the CATALINA_HOME as the Variable name and the corresponding Tomcat directory
as the Variable value, using the path you noted in Step 4 on page 13, then click OK.
Note: It is very important that this is set as a system environment variable, not as a user environment
variable.
6. [For 32-bit & 64-bit] Now you will install the ZLTomcat service connector:
Open a Windows Command Prompt window.
Enter the following command:
%CATALINA_HOME%\bin\zltomcatservice.bat install
This executes a batch file that installs the ZLTomcat service connector.
7. [For 32-bit & 64-bit] Run/Open the %CATALINA_HOME%\bin\zltomcatw.exe:
Refer to Appendix D for setting up MS SQL, Oracle, and DB2 database tables that ZL UA uses
to manage different types of e-mail messages.
Now you need to start up ZL UA for the first time. The server is controlled with the zltc
command:
To shutdown your server, open the Windows Start menu, select Run and enter:
%ZIPLIP_HOME%\bin\zltc stop and this command can be run from anywhere if
%ZIPLIP_HOME% is already set.
You will see an MS-DOS window displaying the shutdown status messages.
To restart your ZL server, open the Windows Start menu, select Run and enter:
%ZIPLIP_HOME%\bin\zltc start and this command can be run from anywhere if
%ZIPLIP_HOME% is already set.
You will see an MS-DOS window displaying the startup status messages.
The ZL server automatically creates the file %ZIPLIP_HOME%\Logs\ConfigDebug.out when it
starts. A batch file in the %ZIPLIP_HOME%\bin directory named logs.bat enables you to type
“logs” at a command prompt to go directly to the logs directory to monitor this file.
When the ZL server is up and running properly, the file ConfigDebug.out is approximately
3.5~3.7MB in size; meaning the system is ready to be bootstrapped.
The initial startup may take a few minutes to depending on the speed of and number of
processors in your system. If ConfigDebug.out is significantly less than 2.5 MB, examine it
along with the other %ZIPLIP_HOME%\Logs files, as well as Windows System or Application
Events logs for exceptions.
Bootstrapping ZL UA
ZL UNIFIED ARCHIVE (UA) enables your company to archive, retrieve, and search e-mail
messages and text message transcripts.
Follow these instructions to bootstrap the ZL UA module.
1. Open a browser window and enter the following URL to begin the basic installation:
http://localhost/ps/install.jsp
Note: If you enter the URL and ZL UA is already installed, a message appears telling you the
installation has already been done. Instead, click Login at the bottom of the screen to log into the
Unified Archival Admin application.
7. Check the box to the left of Yes on the following lines to enable the following features as
appropriate for your site:
Enable Lotus Journaling and Archiving – This enables integration with Lotus e-mail
servers.
Enable Exchange Journaling and Archiving – This enables integration with Microsoft
Exchange e-mail servers.
Note: Exchange archiving and journaling requires Microsoft Outlook to be installed on the ZL UA
server. Also, if you enable Exchange archiving, allow for extra disk space because the Exchange log
files grow significantly as they ingest archived files. For information on Microsoft Outlook and
Exchange compatibility, see http://www.microsoft.com/exchange/evaluation/features/
ExchangeCompatibility.mspx.
Enable Gateway Journaling – Do not check this box; this is not relevant to Mailbox
Management.
When you have finished selecting options, click Next to continue to the Confirm ZL UA
Installation screen.
Click Next, and in the pop-up box asking “Are you sure you wish to continue installation?”,
click OK. A screen appears confirming the installation.
Restart ZL UA by stopping and restarting the ZL Tomcat server. When ZL Tomcat has finished
restarting, the installation is complete.
Note: There is also a command called zltc you can run to start (zltc start) and stop (zltc
stop) all the required processes for ZL UA respectively. zltc restart first stops and then start
automatically.
c. Open a command prompt on the first ZL server and change directory to the bin
subdirectory where the files were unzipped.
D:\> C:
C:\> cd ZLPatch\ZLUpgrade\bin
d. Run the batch file upgrade.bat with the simulate command line argument:
Firewall Rules
As a result of using the JDBC connector to connect to the database server, the ZL UA server
must be able to communicate with the database server over the appropriate port number. The ZL
UA server must also be able to name resolve the database server; this requires DNS and port 53
access.
For ZL UA to perform between an SMTP Gateway and the internet or another SMTP server,
port 25 (SMTP) must be open to and from the ZL UA server, assuming the ZL UA server is in
the mail flow. ZL UA uses port 143 (the IMAP port) to communicate with an Exchange or
Lotus mail server.
To get the full benefit of load balancing and failover protection of the ZL UA servers when
clustered, port 80 must be able to communicate with the Global Coordinator so it can tell when
one of the servers is down.
Clustering is when multiple servers are used for the same thing so if one of them goes down, the
other servers can pick up the jobs the down server would have been processing. Within a clustered
ZL UNIFIED ARCHIVE (UA) environment, the ZL UA servers must be able to access port 139
because the ZL UA servers need to be able to read and write to the same file structure.
ZL UA must have some communication with the Domain Controllers. This can be done by
allowing port 139 or 445 for communication between the ZL UA server and the domain
controllers.
All systems attempting to send mail to or through the ZL UA server must also be forward and
reverse name resolved.
If ZL UA is interfacing with Exchange, port 389 (or 689 for secure LDAP) is required for
LDAP Discovery of users.
If IIS and Tomcat are installed on different servers and a firewall is between them, port 8009 is
required for communication between IIS and Tomcat.
Port 80 or 443 is required to the ZL UA server for web based administration and user access.
The following network diagram may prove useful when configuring for the ZL UA server.
ZL UNIFIED ARCHIVE (UA) uses a password to access your archive database i.e for the ZL
UA schema. It is defined in the pmapp.cfg configuration file. ZL TECHNOLOGIES
recommends that you secure these passwords by encrypting them prior to using your server in a
production environment.
The following steps describe how to encrypt your database passwords:
1. In the Sysadmin interface, select Admin Tools F Encryption/Decryption.
2. You will see the Password Protector panel. Set the Action tab to Encrypt, type the text of
your SmDs password into the Plain Text: box, then click Go.
The following table contains common exceptions in ConfigDebug.out and their causes.
Note: The IIS Tomcat Connector must be installed and IIS must be configured before you add any
alternate Web sites to your ZL servers.
5. In the Web Site Description screen, enter a description of the Web site, in the IP Address
and Port Settings screen, accept the default settings and click Next to continue.
6. In the Web Site Home Directory screen, click Browse, then Browse For Folder pop-up
window, navigate to and select the directory represented by %ZL_HOME%\htdocs. Click
OK to return to the Web Site Home Directory screen.
7. In the completed Web Site Home Directory screen, leave Allow anonymous access to this
Web site checked. Click Next to continue.
8. In the Web Site Access Permissions screen, leave Read checked; also check Run scripts
(such as ASP). Click Next to complete the wizard.
10. Right click on the new Web site and select New->Virtual Directory.
16. In the Web Site Properties window, select the ISAPI Filters tab.
17. In the ISAPI Filters tab, click Add.
18. In the Add/Edit Filter Properties browse to the Redirector bin directory: For example:
C:\Program Files\Apache Software Foundation\Jakarta Isapi Redirector\bin
Select the file isapi_redirect.dll and click Open.
19. In the Add/Edit Filter Properties pop-up window, enter Jakarta as the Filter Name and
click OK. The filter now exists but has not yet been started.
22. In the Computer Management window, start the new Web site by right clicking on it and
selecting Start.
Database Configuration
This appendix contains information on configuring supported databases with ZL UA.
MSSQL Configuration
Make sure the Authentication method is set to SQL Server and Windows on your SQL server.
1. Copy the %ZIPLIP_HOME%\database\mssql directory and its child directory structure to the
system running SQL server.
Oracle Configuration
In this section you will create the SQL database tables that ZL UA uses to manage different
types of e-mail messages.
Note: This section assumes that you have the database instance up and running and some client
interface available for accessing your Oracle 11g database system. The instructions that follow use
SQL*Plus as the command-line interface.
1. First you need to create a folder in your Oracle installation that will serve as the top-level
directory for your ZL UA database files. Go to your Oracle home folder and look for a
folder named oradata. Inside of oradata, create your database root directory folder.
The default access ID name used by ZL UA is ZLDB, so the target directory is also usually
named ZLDB. Within the target directory, create a directory named data.
2. Also create a temporary working directory within Oracle and copy the SQL script files
ZLTables.sql and setupDB.sql from %ZIPLIP_HOME%\database\oracle. These are your
archive database set-up files. Make sure there is no space in the directory name for this
temporary location.
3. Edit the setupDB.sql database script. It contains a path declaration for each tablespace
creation command included, and all the path declarations must be updated to reference the
data folder in your database target directory. An excerpt of an updated version of
setupDB.sql is shown below.
Note: Make sure you change the path delimiter characters from a forward slash (/) to a backslash (\).
You must use fully qualified paths as well.
Once you are done editing the script, run it using Oracle SQL*Plus as the pfuser account
since this user will own the ZL UA schema:
sql> @D:\oracle\zl_install_temp\ZLTables.sql;
5. To verify the database schema tables have been created, run the following SQL command as
the pfuser account using SQL*Plus or equivalent:
sql> select table_name from user_tables;
This will display a list of active tables. Verify the presence of the following tables to ensure
the schema creation process has been completed successfully:
pfuser.zldual
pfuser.zlpmessages
6. Now you need to configure the database initialization file pmapp.cfg, in
%ZIPLIP_HOME%\zlserver\WEB-INF\config\runnable\pmapp\pmapp.cfg.
7. Under Default Datasource Type, note that the database type is set to Oracle by default.
8. Enter the correct server name and port (and if necessary, the database name) for the default
URL corresponding to your database.
A. Enter the correct server name and port (and if necessary, the database name) for the
Oracle database.
B. Edit the following line:
SmDsURL=jdbc:oracle:thin:@localhost:1521:orcl
to the appropriate JDBC URL by specifying the hostname of your ZL UA server:
SmDsURL=jdbc:oracle:thin:@zldbserver:1521:orcl
9. Define the password for the pfuser account. Find the parameter SmDsPwd in pmapp.cfg.
Change the default password pfpass to be the password for pfuser that you entered in
Step 3 on page 49. You will need to delete the encrypted default password.
DB2 Configuration
If you are running a DB2 database, follow the instructions described in this section logged in as
the pfuser user.
Note: For DB2 installation instructions, please consult the documentation provided by IBM.
Follow the steps in this section to configure DB2 to run with ZL UA on a Windows system.
1. On the system on which the DB2 database resides, create the Windows account pfuser;
give this user read and write access (ownership) to the database and data files.
Note: ZipLip recommends you set the system environment variable %DB2_HOME% to the directory
containing the DB2 database files for the installation.
2. If you are running the database on a system other than the ZL UA server:
Create a directory for the ZL UA database instance on the system running the database
(%ZIPLIP_HOME%\database\db2).
Copy the directory %ZIPLIP_HOME%\database\db2 and its subdirectories from the
system running ZL UA to the system running the DB2 server. ZLTI recommends you set
the system environment variable %DB2_HOME% to this directory for the installation.
3. In a command window on the system where the DB2 server resides, change directory to:
%DB2_HOME%
4. Create a target directory for the DB2 data:
mkdir %DB2_HOME%\data
5. On the system running the DB2 server, edit:
%DB2_HOME%\CreateDb.sql
Set the parameters to suit your environment. The default database user is pfuser with
password pfpass; these can be changed in ZipLip.sql.
Change all paths to correspond to the data path desired for your environment using absolute
paths:
DB2_HOME\data
Make sure the database name and path and the ZL UA database username and password are
set properly. Edit this file to make sure all the slashes (“/”) are changed to backslashes (“\”).
6. Run the setupDB.bat script. This script creates the database and sets up a user pfuser to be
used by the ZL UA server to connect to the DB2 server.
7. Follow the steps in the section “Configuring DB2 After Installation” on page 53.
To extend a tablespace that is running low, enter the following from the DB2 command line
interface, replacing DB2_HOME with the absolute path to your DB2_HOME directory and x
with the name of the tablespace.
On Windows:
ALTER TABLESPACE ZL_x EXTEND (FILE ‘DB2_HOME\data\ZLx’ 12800);
To set the tablespace to a size that is double the ZLTI-provided default, enter the following from
the DB2 command line interface, replacing DB2_HOME with the absolute path to your
DB2_HOME directory and x with the name of the tablespace:
On Windows:
ALTER TABLESPACE ZL_x RESIZE (FILE ‘DB2_HOME\data\ZLx’ 25600);
Z
ZipLip
starting 25
unpacking on Windows 19
%ZIPLIP_HOME%
value 22
ZL UA
load balancing 35