bb c Preparing to Install LiveCycle ES

bb c Preparing to Install LiveCycle ES
bc
Preparing to Install LiveCycle® ES
(Server Cluster)
Adobe® LiveCycle® ES
November 19, 2010
Update 1 (8.2)
© 2009 Adobe Systems Incorporated. All rights reserved.
Adobe® LiveCycle® ES Update 2 (8.2) Preparing to Install LiveCycle® ES (Server Cluster)for Microsoft® Windows®, Linux®, and UNIX®
Edition 2.7, November 19, 2010
If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished
under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part
of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording,
or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected
under copyright law even if it is not distributed with software that includes an end user license agreement.
The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or
inaccuracies that may appear in the informational content contained in this guide.
Please remember that existing artwork or images that you may want to include in your project may be protected under copyright law. The
unauthorized incorporation of such material into your new work could be a violation of the rights of the copyright owner. Please be sure to
obtain any permission required from the copyright owner.
Any references to company names, company logos and user names in sample material or sample forms included in this documentation
and/or software are for demonstration purposes only and are not intended to refer to any actual organization or persons.
Adobe, the Adobe logo, Acrobat, Flash, Flex, Flex Builder, FrameMaker, LiveCycle, PageMaker, Photoshop, PostScript, and Reader are either
registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
AIX, DB2, IBM, and WebSphere are trademarks of International Business Machines Corporation in the United States, other countries, or both.
BEA WebLogic Server is a registered trademark of BEA Systems, Inc.
Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the U.S. and other countries.
Java, Solaris, and Sun are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. Products bearing
SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
JBoss and Red Hat are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft, Windows, Windows Server, and Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
Oracle is a trademark of Oracle Corporation and may be registered in certain jurisdictions.
Novell and SUSE are trademarks or registered trademarks of Novell, Inc. in the United States and other countries.
UNIX is a trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd.
All other trademarks are the property of their respective owners.
This product contains either BSAFE and/or TIPEM software by RSA Security, Inc.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes software developed by the IronSmith Project (http://www.ironsmith.org/).
This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).
This product includes software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/).
This product includes copyrighted software developed by E. Wray Johnson for use and distribution by the Object Data Management Group
(http://www.odmg.org/).
Portions © Eastman Kodak Company, 199- and used under license. All rights reserved. Kodak is a registered trademark and Photo CD is a
trademark of Eastman Kodak Company.
Powered by Celequest. Copyright 2005-2008 Adobe Systems Incorporated. All rights reserved. Contains technology distributed under license
from Celequest Corporation. Copyright 2005 Celequest Corporation. All rights reserved.
Single sign-on, extending Active Directory to Adobe LiveCycle ES provided by Quest Software “www.quest.comlidentity-management” in a
subsequent minor release that is not a bug fix (i.e., version 1.1 to 1.2 but not 1.1.1 to 1.1.2) of the Licensee Product that incorporates the
Licensed Product.
The Spelling portion of this product is based on Proximity Linguistic Technology.
©Copyright 1989, 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey
USA.
© Copyright 1990 Merriam-Webster Inc. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2003 Franklin Electronic Publishers Inc. © Copyright 2003 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 Franklin Electronic Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1991 Dr.Lluis de Yzaguirre I Maura © Copyright 1991 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1990 Munksgaard International Publishers Ltd. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1995 Van Dale Lexicografie bv © Copyright 1996 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1990 IDE a.s. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc.
Burlington, New Jersey USA.
© Copyright 2004 Franklin Electronics Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin
Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 1992 Hachette/Franklin Electronic Publishers, Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of
Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 Bertelsmann Lexikon Verlag © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 MorphoLogic Inc. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers,
Inc. Burlington, New Jersey USA.
© Copyright 1990 Williams Collins Sons & Co. Ltd. © Copyright 1990 All Rights Reserved Proximity Technology A Division of Franklin Electronic
Publishers, Inc. Burlington, New Jersey USA. © Copyright 1993-95 Russicon Company Ltd.
© Copyright 1995 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc. Burlington, New Jersey USA.
© Copyright 2004 IDE a.s. © Copyright 2004 All Rights Reserved Proximity Technology A Division of Franklin Electronic Publishers, Inc.
Burlington, New Jersey USA.
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.
Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101,
consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R.
§12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable,
the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users
(a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein.
Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA
95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if
appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of
1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60,
60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.
Contents
About This Document.................................................................................................................. 6
Before you start............................................................................................................................................................................... 6
What’s in this document?............................................................................................................................................................ 6
Who should read this document? ............................................................................................................................................ 6
1
Introduction to Application Server Clusters ............................................................................. 9
About clustering application servers ...................................................................................................................................... 9
Failover ......................................................................................................................................................................................10
Load balancing .......................................................................................................................................................................10
Scalability and availability...................................................................................................................................................10
Terminology ...................................................................................................................................................................................11
JBoss ...........................................................................................................................................................................................11
WebLogic ..................................................................................................................................................................................11
WebSphere...............................................................................................................................................................................11
Clustering LiveCycle ES ..............................................................................................................................................................11
Clustering LiveCycle ES on WebLogic ............................................................................................................................11
Clustering LiveCycle ES on WebSphere .........................................................................................................................12
Supported topologies.................................................................................................................................................................12
Combined web, application, and database servers ..................................................................................................12
Combined web and application servers with separate database server...........................................................13
Single web server with combined application and database server ..................................................................13
Separate web, application, and database servers......................................................................................................13
Adding additional web servers .........................................................................................................................................13
Adding additional application servers ...........................................................................................................................13
Multiple JVMs ..........................................................................................................................................................................14
JMS messaging .......................................................................................................................................................................14
Unsupported topologies ...........................................................................................................................................................16
2
System Requirements for Installing LiveCycle ES................................................................... 17
LiveCycle ES patch updates......................................................................................................................................................17
Third-party infrastructure support.........................................................................................................................................17
Microsoft Windows Server..................................................................................................................................................17
Red Hat Enterprise Linux and SUSE Linux.....................................................................................................................18
IBM AIX.......................................................................................................................................................................................20
Sun Solaris ................................................................................................................................................................................20
System requirements..................................................................................................................................................................21
Minimum hardware requirements ..................................................................................................................................21
Intel x86 compatibility .........................................................................................................................................................22
Recommended hardware requirements .......................................................................................................................22
Additional hardware requirement for LiveCycle Content Services ES................................................................23
Recommended hardware requirements for client-side machines ......................................................................24
Supported software ..............................................................................................................................................................25
Minimum database user permissions.............................................................................................................................29
Web browser support...........................................................................................................................................................30
Additional requirements for Linux or UNIX operating systems............................................................................31
Additional requirements for PDF Generator ES and PDF Generator 3D ES ......................................................31
4
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Contents
5
Additional requirements for Connector for IBM Content Manager ....................................................................35
LDAP configuration .....................................................................................................................................................................38
Global document storage directory ......................................................................................................................................38
Planning and creating the global document storage directory ...........................................................................38
Location of the global document storage directory .................................................................................................38
Sizing factors for the global document storage directory ......................................................................................39
Securing the global document storage directory......................................................................................................39
Backing up the global document storage directory .................................................................................................39
LiveCycle ES Business Activity Monitoring requirements..............................................................................................40
Basic requirements ................................................................................................................................................................40
Creating the Business Activity Monitoring metadata database ...........................................................................41
JBoss requirements ...............................................................................................................................................................41
WebLogic requirements ......................................................................................................................................................42
WebSphere requirements...................................................................................................................................................43
Synchronizing clock times ........................................................................................................................................................44
Installation considerations........................................................................................................................................................44
Installing from network drives ..........................................................................................................................................44
Using LiveCycle ES with a Luna HSM cluster................................................................................................................44
Manual use of Acrobat restricted .....................................................................................................................................44
Restricted use of unlicensed Process Management ES functionality..................................................................44
LiveCycle ES IPv6 support ...................................................................................................................................................45
Processes with document form variables and digital signatures.........................................................................45
3
LiveCycle ES Credentials and Certificates................................................................................ 46
Obtaining the Reader Extensions ES Rights credential ..................................................................................................46
Obtaining digital certificates for use with Digital Signatures ES.................................................................................47
4
Creating the LiveCycle ES Database......................................................................................... 48
Database configuration requirements .................................................................................................................................48
Creating an Oracle database ....................................................................................................................................................48
Creating a SQL Server database..............................................................................................................................................49
Installing the SQL Server database driver .....................................................................................................................50
Setting up SQL Server for LiveCycle ES ..........................................................................................................................50
Sizing your SQL Server database......................................................................................................................................51
Creating the LiveCycle ES database user, schema, and login................................................................................52
Creating a DB2 database ...........................................................................................................................................................54
DB2 user account ...................................................................................................................................................................54
Additional DB2 requirements for LiveCycle Content Services ES.........................................................................56
About This Document
Before you start
Ensure that you have the most current version of the LiveCycle ES documentation.
What’s in this document?
This document contains the following types of information:
●
All hardware and software requirements and configurations that must be already in place to ensure a
successful LiveCycle ES installation process
Who should read this document?
This document provides information for administrators or developers who are responsible for preparing
the application and database servers for development, staging, and production environments before
installing, configuring, administering, and deploying LiveCycle ES. The information provided is based on
the assumption that anyone reading this document is familiar with application servers, Red® Hat® Linux®,
SUSE™ Linux, Microsoft® Windows®, IBM AIX®, or Sun™ Solaris™ operating systems, Oracle®, IBM DB2®, or
SQL Server database servers, and web environments.
6
Adobe LiveCycle ES
About This Document
Preparing to Install LiveCycle ES (Server Cluster)
Conventions used in this document
Conventions used in this document
This guide uses the following naming conventions for common file paths.
Name
Description
Default value
[appserver root]
The home directory of the
application server that runs
the LiveCycle ES services.
JBoss on Windows: C:\jboss
JBoss on Linux, Solaris: /opt/jboss
WebSphere on Windows:
C:\Program Files\IBM\WebSphere\AppServer
WebSphere on Linux and Solaris:
/opt/IBM/WebSphere/AppServer
WebSphere on AIX:
/usr/IBM/WebSphere/AppServer, or,
/opt/IBM/WebSphere/AppServer
WebLogic on Windows:
C:\bea\weblogic92\
C:\bea\wlserver_10.1
WebLogic on Linux and UNIX:
/opt/bea/weblogic92
/opt/bea/wlserver_10.1
BEA_HOME
The install directory for WebLogic
as specified for the BEA_HOME
environment variable.
WebLogic on Windows C:\bea
WebLogic on Linux and UNIX: /opt/bea
[appserverdomain]
The domain that you configured
WebLogic on Windows:
on WebLogic. The default domain C:\bea\user_projects\domains\base_domain
is called base_domain.
WebLogic on Linux and UNIX:
/opt/bea/user_projects/domains/base_domain
[dbserver root]
The location where the
LiveCycle ES database server is
installed.
Depends on the database type and your
specification during installation.
Most of the information about directory locations in this document is cross-platform (all file names and
paths are case-sensitive on Linux and UNIX®). Any platform-specific information is indicated as required.
7
Adobe LiveCycle ES
About This Document
Preparing to Install LiveCycle ES (Server Cluster)
Additional information
Additional information
The resources in this table can help you learn about LiveCycle ES.
For information about
See
LiveCycle ES and the solution components
in general
LiveCycle ES Overview
What’s new in this LiveCycle ES release
What’s New for LiveCycle ES
LiveCycle ES terminology
LiveCycle ES Glossary
Other services and products that integrate
with LiveCycle ES
http://www.adobe.com/products/livecycle
Other LiveCycle ES solution components
Adobe Development Center
All documentation that is available for
LiveCycle ES
Adobe LiveCycle ES documentation
LiveCycle ES release information and
last-minute changes that occur to the
product
LiveCycle ES Release Notes
Patch updates, technical notes, and
additional information about this product
version
LiveCycle Technical Support
8
1
Introduction to Application Server Clusters
This section describes clustered application servers and the benefits and issues that are associated with
setting up clusters.
About clustering application servers
A cluster is a group of application server instances that run simultaneously, which act like a single system,
enabling high availability and load balancing. Within a cluster, multiple server instances can run on the
same computer (known as a vertical cluster) or can be located on different computers (known as a
horizontal cluster), or they can form a combination of both horizontal and vertical clusters. With clustering,
client work can be distributed across several nodes instead of handled by a single application server.
In a clustered configuration, application server instances are server members of the cluster, all of which
must have identical application components deployed on them. However, other than the configured
applications, cluster members do not have to share any other configuration parameters. For example, you
can cluster multiple server instances on one computer, with a single instance on another computer,
provided they are all running the same version of application server.
By clustering, you can achieve one or more of the following benefits. How you implement clustering
determines which benefits are achieved:
●
Failover
●
Load balancing
●
Scalability
9
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Introduction to Application Server Clusters
Failover
10
Failover
Failover allows one or more application server instances to act as backup to a failed application server
instance and resume processing the task, therefore enabling another application server to carry on
processing. However, if an application server fails during a transaction, the backup application server does
not recover the state of the failed instance. If a server fails when a user enters data into a form, for example,
the data may have to be reentered.
Load balancing
Load balancing is a technique used to distribute work across a number of systems so that no single device
is overwhelmed. If one server starts to get congested or overloaded, requests are forwarded to another
server that has more capacity.
Application server load balancing
Application server load balancing is useful for managing the load between application servers. Application
servers can be configured to use a weighted round-robin routing policy that ensures a balanced routing
distribution based on the set of server weights that are assigned to the members of a cluster. Configuring
all servers in the cluster to have the same weight produces a load distribution in which all servers receive
approximately the same number of requests. Weighting some servers more heavily sends more requests
to these servers than to those that are weighted less heavily.
Preferred routing configurations can also be configured to ensure, for example, that only cluster members
on that node are selected (using the round-robin weight method) and cluster members on remote nodes
are selected only if a local server is not available. Application server load balancing is best used when
balancing is needed between tiers.
Web server load balancing
Web server load balancing is useful for queuing and throttling requests. For the Apache HTTP Server, the
most commonly used method for load balancing is Round-Robin DNS.
Round-Robin DNS is a relatively simple method of load balancing, where a domain name system (DNS)
server provides a name to address resolution and is always involved when a host name is included in a
URL. A Round-Robin DNS server can resolve one single host name into multiple IP addresses such that
requests for a single URL (containing a host name) actually reference different web servers. The client
requests a name resolution for the host name but, in fact, receives different IP addresses, therefore
spreading the load among the web servers. In a simple configuration, the Round-Robin DNS server cycles
through the list of available servers.
Scalability and availability
Scalability in a cluster means that an administrator can increase the capacity of the application dynamically
to meet the demand without interrupting or negatively impacting service. Clusters allow administrators to
remove nodes from a cluster in order to upgrade components, such as memory, or to add nodes to the
cluster without bringing down the cluster itself.
Adobe LiveCycle ES
Introduction to Application Server Clusters
Preparing to Install LiveCycle ES (Server Cluster)
Terminology
11
Terminology
Each application server vendor uses specific terminology, which is defined here to avoid confusion.
JBoss
server: Represents an instance of a Java™ virtual machine (JVM™).
cluster: Represents a logical grouping of multiple application servers for administration, application
deployment, load balancing, and failover purposes.
WebLogic
server: Represents an instance of a Java™ virtual machine (JVM™).
machine: Represents a physical system running one or more instances of WebLogic Server.
cluster: Represents a logical grouping of multiple application servers within a domain for
administration, application deployment, load balancing, and failover purposes.
WebSphere
server: Represents an instance of a Java™ virtual machine (JVM™).
node: Represents a physical system running one or more instances of WebSphere Application Server.
cell: Represents a logical grouping of multiple nodes for administrative purposes.
federation: The process of joining a stand-alone WebSphere node to a WebSphere cell.
cluster: Represents a logical grouping of multiple application servers within a cell for administration,
application deployment, load balancing, and failover purposes.
Clustering LiveCycle ES
If you install a LiveCycle ES component on an application server cluster, here are some things you must
know:
●
Each application server in the cluster on which you deploy LiveCycle ES must have a homogeneous
topology (that is, all nodes in the cluster must be configured identically). You can ensure that all
modules are configured identically by configuring run-time properties in the single-installation staging
area.
●
The configuration is deployed by using the single entity approach; all nodes in a cluster are deployed as
if deploying to a single node.
Setting up a clustered environment for LiveCycle ES involves the tasks that follow.
Clustering LiveCycle ES on WebLogic
You must perform the following tasks to deploy LiveCycle ES on a WebLogic Server cluster:
1. Prepare the hardware as per your requirements.
2. Install the operating system and update it with all necessary patches and service packs.
3. Install and configure the database server.
Adobe LiveCycle ES
Introduction to Application Server Clusters
Preparing to Install LiveCycle ES (Server Cluster)
Clustering LiveCycle ES on WebSphere
12
4. Install and configure the application server.
5. Configure the JMS resources.
6. Install LiveCycle ES solution components and configure LiveCycle ES for deployment.
7. Deploy LiveCycle ES to WebLogic Server.
Clustering LiveCycle ES on WebSphere
You must perform the following tasks to deploy LiveCycle ES on a WebSphere Application Server cluster:
1. Install WebSphere Application Server Network Deployment software.
2. Install WebSphere Application Server software on each node of the cluster.
3. Install the HTTP Server (IBM HTTP Server).
4. Set up the cluster:
●
Create a deployment server profile and create the Deployment Manager.
●
Create managed application server profiles on all the nodes.
●
Start all servers on all nodes that will become members of the cluster.
●
Federate nodes to the Deployment Manager.
●
Create the cluster.
●
Start the cluster.
●
Configure cluster resources.
5. Deploy applications.
6. Generate the WebSphere HTTP plug-in.
7. Start the HTTP server.
Supported topologies
The following sections discuss various topologies, both clustered and non-clustered, that you can employ.
For additional information about configuring your application server in a cluster, go to one of the
following websites, as applicable to your application server:
●
(WebLogic Server) Supported Configurations for WebLogic Platform 9.2
●
(WebSphere Application Server) WebSphere Application Server (Distributed platforms and Windows)
●
(JBoss Application Server) High Availability Enterprise Services via JBoss Clusters
Combined web, application, and database servers
This topology consists of a web server, an application server, and a database server on the same node. This
topology is the simplest one and must be used for development only.
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Introduction to Application Server Clusters
Combined web and application servers with separate database server
13
Combined web and application servers with separate database server
This topology can be considered for production in case the load on the user interface (including the web
tier) is minimal, with a small number of users.
Combining the web and application servers means that all Enterprise JavaBeans™ (EJB) look-ups are local,
and therefore reduces the overhead of doing a remote look-up. Also, this topology reduces the network
overhead of a round trip between the web tier and the application tier.
However, with both servers on the same node, if the web tier is compromised, both tiers are compromised.
If the web tier experiences a heavy load, the application server processing is affected and vice versa. User
response time is usually affected in situations when users need to wait a significant amount of time to get
a page back due to all server resources (that is, CPU and/or memory) being consumed by the application
server. If the web tier has a large session size, the application could be deprived of the memory required to
process messages off the Java Message Service (JMS) layer.
Single web server with combined application and database server
The simplest topology that should be considered for a production environment is a web server and
combined application server with a database server. Use this topology only if you are sure that your
database load will be minimal. In this scenario, the web server is providing a redirection to the application
server. The advantages of this topology are low cost, low complexity, and no need for load balancing. The
disadvantages of this topology are little redundancy, low scalability, inability to perform updates and
upgrades, and possible low performance due to too many CPU processes.
Separate web, application, and database servers
This topology is the most common in production systems because it allows allocation of separate
resources to each of the tiers. In this case, the web server acts as a proxy to the web tier on the application
server that hosts the web components. This level of indirection provides additional security by securing
the application server even if the web server is compromised.
Adding additional web servers
You can add additional web servers for scalability and failover. When using multiple web servers, the
WebLogic/WebSphere HTTP plug-in configuration file must be applied to each web server. Failure to do so
after introducing a new application will likely cause a “404 File Not Found” error to occur when a user tries
to access the web application.
Adding additional application servers
This topology is used in most large-scale production systems where the application servers are clustered
to provide high availability and, based on the topology, failover and load balancing.
Clustering application servers has these benefits:
●
You can use cheaper hardware configurations and still achieve higher performance
●
You can upgrade software on servers without down time
●
Provides higher availability (that is, if one server fails, the other nodes in the cluster pick up the
processing)
Adobe LiveCycle ES
Introduction to Application Server Clusters
Preparing to Install LiveCycle ES (Server Cluster)
●
Multiple JVMs
14
Provides the ability to leverage load-balancing algorithms on the web server (by using load balancers)
as well as on the EJB tier for processing requests
LiveCycle ES components are typically CPU-bound. As a result, performance gains are better achieved by
adding more application servers than by adding more memory or disk space to an existing server.
Multiple JVMs
Vertical scaling of multiple JVMs offers the following advantages:
Increased processing power efficiency: An instance of an application server runs in a single JVM
process. However, the inherent concurrency limitations of a JVM process prevent it from fully using the
memory and processing power of multi-CPU systems. Creating additional JVM processes provides
multiple thread pools, each corresponding to the JVM process that is associated with each application
server process. This correspondence avoids concurrency limitations and lets the application server use
the full processing power of the computer.
Load balancing: Vertical scaling topologies can use the WebLogic Server or WebSphere Application
Server workload management facility.
Process failover: A vertical scaling topology also provides failover support among application server
cluster members. If one application server instance goes offline, the other instances on the computer
continue to process client requests.
JMS messaging
The following sections describe JMS topologies.
WebLogic
You can configure embedded JMS in various topologies:
●
Single instance of WebLogic Server with a single JMS server
●
Multiple instances of WebLogic Server with a single JMS server
●
Multiple instances of WebLogic Server, each with their own JMS servers
A single JMS server in a single or multiserver environment is simple to configure and does not require JMS
Server Management. However, it can only handle low volumes. Because the data store (where messages
are stored) is not available for tuning and/or management, the single JMS server cannot be tuned as it is
started and cannot it be managed by WebLogic Server.
WebSphere
The recommended JMS topology to provide high availability and load distribution in a production
environment is to employ separate clusters for LiveCycle ES instances and the JMS messaging engine. The
two clusters should be separate but can run on the same computers.
This illustration shows the logical topology.
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Introduction to Application Server Clusters
JMS messaging
15
The illustration that follows shows an example of how to employ this topology on the physical hardware
computers that host the cluster. Take notice of these configurations:
●
Locating JMS instances on multiple computers provides high availability for JMS. Only two JMS
instances are required to provide high availability for the messaging engine cluster (one instance
active, the second instance inactive but available for failover). However, you may choose to create
additional JMS instances on each computer of your cluster.
Running the JMS cluster on only two computers is the most efficient configuration. However,
extending the JMS cluster across all computers of the cluster simplifies administration (because the
JMS messaging engine cluster mirrors the LiveCycle ES cluster) and helps ensure that a JMS server
instance is available even if many computers of the JMS cluster fail.
You can choose either configuration, as appropriate for the specific needs and preferences for a
particular LiveCycle ES deployment.
●
Locating multiple LiveCycle ES instances on a single computer provides load distribution for
LiveCycle ES processes.
●
Locating LiveCycle ES instances on separate computers provides high availability for LiveCycle ES
processes.
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Introduction to Application Server Clusters
Unsupported topologies
16
Unsupported topologies
The following topologies are not supported for LiveCycle ES.
Splitting the web container from the EJB container
Splitting LiveCycle ES servers into presentation/business logic tiers and running them on distributed
computers is not supported.
Geographically distributed configuration
Many applications locate their systems geographically to help distribute the load and provide an added
level of redundancy. LiveCycle ES does not support this configuration because LiveCycle ES components
cannot be pulled apart to run on different hosts; LiveCycle ES is deployed as a monolithic application.
Most of the information about directory locations in this document is cross-platform (all file names and
paths are case-sensitive on Linux and UNIX). Platform-specific information is indicated as required.
2
System Requirements for Installing LiveCycle ES
This section provides the information that you need before you begin installing LiveCycle ES, including
system requirements, deployment topology information, and a list of the information about the target
installation environment that you need to have during installation.
LiveCycle ES patch updates
Before you install LiveCycle ES, ensure that you download any required patch updates, which are located at
LiveCycle Technical Support.
Third-party infrastructure support
This section summarizes the referenced platform and database combinations for JBoss® Application Server
4.0.3 SP1 and 4.2.0, BEA WebLogic Server® 9.2 and 10.1, and IBM WebSphere® Application Server 6.1.0.7. To
facilitate the use of WebLogic for joint Adobe and BEA customers, BEA has provided the BEA Download
site from which you can download the exact version of WebLogic that LiveCycle ES requires.
Microsoft Windows Server
LiveCycle ES supports the following Microsoft Windows operating system:
●
Windows Server 2003 Standard and Enterprise Edition SP2 and later (32-bit and 64-bit)
●
Windows Server 2003 R2 Standard SP2 and later (32-bit and 64-bit)
●
Windows Server 2003 Enterprise Edition R2 SP2 and later running on 32-bit, 64-bit, and VMWare
ESX/GSX architectures
Note: Microsoft Windows XP is supported for nonproduction environments.
This table lists the supported application server, Java™ Development Kit (JDK), and database
configurations for this operating system.
OS/JVM
architecture
Application server
JDK
Red Hat JBoss Application
Server 4.0.3 SP1
Sun JDK 5.0
Update 11 or
later updates to
5.0
32-bit OS and
32-bit JVM™
Sun JDK 5.0
Update 11 or
later updates to
5.0
64-bit OS and
64-bit JVM
Red Hat JBoss Application
Server 4.2.0
Database
●
IBM DB2 8.2, 9.1
●
Oracle 9i, 10g
●
Microsoft SQL Server 2005 SP2
●
IBM DB2 8.2, 9.1
●
Oracle 9i, 10g
●
Microsoft SQL Server 2005 SP2
17
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Red Hat Enterprise Linux and SUSE Linux
Application server
JDK
BEA WebLogic 9.2 (Advantage
& Premium)
BEA JRockit®
JDK supplied
with application
server
BEA WebLogic 10.1 MP1
(Advantage & Premium)
BEA JRockit JDK
BEA WebLogic 10.1 MP1
(Advantage & Premium)
BEA JRockit JDK
IBM WebSphere 6.1.0.7 (Base &
Network Deployment Edition)
Note: It is recommended that
WebSphere installations
use the latest Fixpack
and SR.
JDK 1.5 SR4
available for
download from
IBM
OS/JVM
architecture
32-bit OS and
32-bit JVM
18
Database
●
IBM DB2 8.2, 8.1 FixPack 7a
●
Oracle 9i, 10g
●
Microsoft SQL Server 2005 SP2
●
64-bit OS and
64-bit JVM all
others.
32-bit OS and
32-bit JVM
or
●
IBM DB2 8.2, 9.1
●
Oracle 9i, 10g
●
Microsoft SQL Server 2005 SP2
●
IBM DB2 8.2, 9.1
●
Oracle 9i, 10g
●
Microsoft SQL Server 2005 SP2
64-bit OS and
64-bit JVM
Note: When using PDF Generator ES with a 64-bit application server, an additional 32-Bit JVM must be
installed. For a detailed list of the supported database editions, see “Supported software” on
page 25.
Red Hat Enterprise Linux and SUSE Linux
LiveCycle ES supports the following Red Hat Enterprise Linux and SUSE Linux operating systems:
●
Red Hat Enterprise Linux AS or ES 4.0 (x86/EDT/AMD64 32-bit architectures)
●
Red Hat Enterprise Linux AS or ES 5.0 (EDT/AMD64 64-bit architectures)
●
SUSE Linux Enterprise Server 9.0 (x86/EDT/AMD64 32-bit architectures)
●
SUSE Linux Enterprise Server 10.0 (EDT/AMD64 64-bit architectures)
This table lists the supported application server, JDK, and database configurations for the Red Hat
Enterprise Linux AS or ES 4.0 and SUSE Linux Enterprise Server 9.0 operating systems.
Application server
JDK
OS/JVM architecture
Database
Red Hat JBoss Application
Server 4.0.3 SP1
(Red Hat Linux) Sun JDK
5.0 Update 11 or later
updates to 5.0.
32-bit OS and 32-bit
JVM
●
IBM DB2 8.2, 9.1
●
Oracle 9i, 10g
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Red Hat Enterprise Linux and SUSE Linux
Application server
JDK
OS/JVM architecture
Database
BEA WebLogic 9.2
(Advantage & Premium)
BEA JRockit JDK
32-bit OS and 32-bit
JVM
●
Oracle 9i, 10g
IBM WebSphere 6.1.0.7 (Base
& Network Deployment
Edition 6)
JDK 1.5 SR4 available for
download from IBM
32-bit OS and 32-bit
JVM
●
IBM DB2 8.2, 9.1
●
Oracle 9i, 10g
Note: It is recommended
that WebSphere
installations use the
latest Fixpack and SR.
Note: When using PDF Generator ES with a 64-bit application server, an additional 32-Bit JVM must be
installed. For a detailed list of the supported database editions, see “Supported software” on
page 25.
This table lists the supported application server, JDK, and database configurations for the Red Hat
Enterprise Linux AS or ES 5.0 and SUSE Linux Enterprise Server 10.0 operating systems.
Application server
JDK
OS/JVM
architecture
Red Hat JBoss Application
Server 4.2.0
Sun JDK 5.0 Update 11
or later updates to 5.0.
64-bit OS and
64-bit JVM
Database
●
IBM DB2 8.2, 9.1 (Red
Hat only)
●
Oracle 9i, 10g
BEA WebLogic 10.1 MP1
(Advantage & Premium)
BEA JRockit JDK
64 bit OS and
64-bit JVM
●
Oracle 9i, 10g
IBM WebSphere 6.1.0.7 (Base
& Network Deployment
Edition)
JDK 1.5 SR4 available for
download from IBM
64-bit OS and
64-bit JVM
●
IBM DB2 8.2, 9.1
●
Oracle 9i, 10g
Note: It is recommended
that WebSphere
installations use the
latest Fixpack and SR.
19
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
IBM AIX
IBM AIX
LiveCycle ES supports the following IBM AIX operating system:
●
AIX 5L 5.3 (64-bit and 32-bit architectures)
Note: It is recommended using the 64-bit architecture for AIX even when using the 32 bit JDK.
This table lists the supported application server, JDK, and database configurations for this operating
system.
Application server
JDK
OS/JVM
architecture
IBM WebSphere 6.1.0.7 (Base &
Network Deployment Edition)
JDK 1.5 SR4 available for
download from IBM
64-bit OS and
64-bit JVM
●
IBM DB2 8.2, 9.1
●
Oracle 9i, 10g
IBM WebSphere 6.1.0.7 (Base &
Network Deployment Edition)
JDK 1.5 SR4 available for
download from IBM
64-bit OS and
32-bit JVM
●
IBM DB2 8.2, 9.1
●
Oracle 9i, 10g
Database
Note: It is recommended that
WebSphere installations use
the latest Fixpack and SR.
Note: For a detailed list of the supported database editions, see “Supported software” on page 25.
Sun Solaris
LiveCycle ES supports the Sun Solaris 9, 10 (SPARC® architectures) operating systems.
Caution: Do not use the Solaris tar command to extract files or errors (such as missing files) will occur.
Download the GNU tar tool and use it to extract all files on a Solaris environment.
This table lists the supported application server, JDK, and database configurations for these operating
systems.
Application server
JDK
OS/JVM
architecture
(Solaris 10 only) Red Hat JBoss
Application Server 4.2.0
Sun JDK 5.0 Update 11
or later updates to 5.0.
64-bit OS and
64-bit JVM
●
Oracle 9i, 10g
BEA WebLogic 9.2 (Advantage &
Premium)
Sun JDK 5.0 Update 11
or later updates to 5.0.
64-bit OS and
32-bit JVM
●
Oracle 9i, 10g
(Solaris 10 only) BEA WebLogic 10.1
MP1 (Advantage & Premium)
Sun JDK supplied with
application server.
64-bit OS and
64-bit JVM
●
Oracle 9i, 10g
IBM WebSphere 6.1.0.7 (Base &
Network Deployment Edition)
JDK 1.5 SR4 available for
download from IBM.
64-bit OS and
64-bit JVM only
on Solaris 10
●
IBM DB2 8.2, 9.1
●
Oracle 9i, 10g
Note: It is recommended that
WebSphere installations use
the latest Fixpack and SR.
64-bit OS and
32-bit JVM on
Solaris 9 and 10
Database
20
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
System requirements
21
Note: For a detailed list of the supported database editions, see “Supported software” on page 25.
System requirements
This section provides the minimum and recommended hardware requirement for LiveCycle ES.
Minimum hardware requirements
This table provides the minimum hardware requirements that LiveCycle ES supports.
Operating system
Minimum hardware requirement
Microsoft Windows Server® 2003 Enterprise
Edition or Standard Edition SP2 and R2
(32-bit and 64-bit architectures)
Intel® Pentium® 4, 2.8 GHz processor
VMWare ESX 3.0 and 3.5 or VMWare Server 1.0 (formerly
GSX)
RAM:
●
2 GB (32-bit OS)
●
3 GB (64-bit OS)
Free disk space: 5.4 GB of temporary space plus 3.4 GB
for LiveCycle ES
Sun Solaris 9 and 10
UltraSPARC® IIe, 650 MHz processor
RAM:
●
3GB (64-bit OS with 64 bit JVM)
●
2GB (64-bit OS with 32 bit JVM)
Free disk space: 5.4 GB of temporary space plus 3.4 GB
for LiveCycle ES
IBM AIX 5L 5.3
P4 pSeries 615 (Model 6C3) 7029-6C3, 1.2 GHz processor
RAM:
●
3GB (64-bit OS with 64 bit JVM)
●
2GB (64-bit OS with 32 bit JVM)
Free disk space: 5.4 GB of temporary space plus 3.4 GB
for LiveCycle ES
SUSE Linux Enterprise Server 9.0
(32-bit edition only)
Pentium 4 or x86 equivalent, 1 GHz processor
RAM:
●
2 GB (32-bit OS)
Free disk space: 5.4 GB of temporary space plus 3.4 GB
for LiveCycle ES
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Intel x86 compatibility
Operating system
Minimum hardware requirement
SUSE Linux Enterprise Server 10.0
(64-bit edition only)
Pentium 4 or x86 equivalent, 1 GHz processor
VMWare ESX 3.0 and 3.5 or VMWare Server 1.0 (formerly
GSX)
RAM:
●
3GB (64-bit OS with 64 bit JVM)
Free disk space: 5.4 GB of temporary space plus 3.4 GB
for LiveCycle ES
Red Hat Enterprise Linux AS or ES 4.0
(32-bit edition only)
Pentium 4 or x86 equivalent, 1 GHz processor
VMWare ESX 3.0 and 3.5 or VMWare Server 1.0 (formerly
GSX)
RAM:
●
2 GB (32-bit OS)
Free disk space: 5.4 GB of temporary space plus 3.4 GB
for LiveCycle ES
Red Hat Enterprise Linux AS or ES 5.0
(64-bit edition only)
Pentium 4 or x86 equivalent, 1 GHz processor
VMWare ESX 3.0 and 3.5 or VMWare Server 1.0 (formerly
GSX)
RAM:
●
3GB (64-bit OS with 64 bit JVM)
Free disk space: 5.4 GB of temporary space plus 3.4 GB
for LiveCycle ES
Intel x86 compatibility
On supported Windows and Linux environments, LiveCycle ES supports Intel EDT64 and AMD64
compatible chipsets running either 32-bit or 64-bit supported operating systems.
Recommended hardware requirements
In addition to the minimum hardware requirements listed previously, here are the recommended
hardware requirements for a small production environment:
Intel environments: Pentium 4, 2.8 GHz or greater. Using a dual core processor will further enhance
performance.
Sun SPARC environments: UltraSPARC V or later.
IBM AIX environments: Power4 or later
Memory requirements: 4 GB of RAM.
22
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
System Requirements for Installing LiveCycle ES
Additional hardware requirement for LiveCycle Content Services ES
23
Additional hardware requirement for LiveCycle Content Services ES
If you are installing LiveCycle Content Services ES for use with a DB2 database, you must have a minimum
of 2 GB of RAM on the LiveCycle ES database computer.
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Recommended hardware requirements for client-side machines
Recommended hardware requirements for client-side machines
The following minimum RAM requirements are recommended for client-side computers that are used
either for development or for end-user interactions. These computers will need adequate resources for
running applications (such as LiveCycle Workbench ES, LiveCycle Workspace ES, Adobe Flash Player,
Adobe Reader) according to the tasks they will perform.
Development environment hardware requirements:
●
Workbench ES: 1 GB of RAM
●
Adobe Flex® Builder 2.0.1 Hot Fix 2 or later, or Flex SDK 2.0.1 Hot Fix 2 or later: 1 GB of RAM (2 GB
recommended)
●
Adobe Flash Player 9 or later: 512 MB of RAM (1 GB recommended)
●
Adobe Acrobat® Professional and Acrobat Pro Extended, versions 7.0 to 9.0: 1 GB of RAM
Note: For more information, see Installing Your Development Environment.
End-user hardware requirements:
●
LiveCycle Workspace ES: 1 GB of RAM (includes requirements for Adobe Flash and Adobe Reader)
●
Adobe Flash Player 9 or later: 512 MB of RAM (1 GB recommended)
●
Adobe Reader 7.0.9: 128 MB of RAM (256 MB recommended)
Note: For web browser requirements, see “End-user user interface” on page 30.
24
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Supported software
25
Supported software
This table provides a summary of the application servers, web browsers, databases, database drivers, JDK
versions, and LDAP servers that LiveCycle ES supports.
Required software
Supported version
Operating system
●
●
Application server
Microsoft Windows
●
Standard Server 2003 SP2 and later
●
Enterprise Edition SP2 and later
●
Standard Server R2 SP2 and later
●
Enterprise Edition R2 SP2 and later running on 32-bit, 64-bit, and
VMWare ESX/GSX architectures
(Workbench ES) Microsoft Windows
●
Windows Vista 32 bit and 64 bit
●
XP Professional SP2 and above Platform 32 bit
●
XP Tablet PC SP2 and above 32 bit
●
2003 Server SP1 and above 32 bit and 64 bit
●
Sun Solaris 9 and 10
●
IBM AIX 5L 5.3
●
SUSE Linux Enterprise Server 9.0 (32-bit edition only)
●
Red Hat Enterprise Linux AS or ES 4.0 (32-bit edition only) or ES 5.0
(64-bit edition only)
●
JBoss 4.0.3 SP1
●
JBoss 4.2.0
●
IBM WebSphere 6.1.0.7 (Base and Network Deployment editions)
●
BEA WebLogic 9.2 (Advantage and Premium editions)
●
BEA WebLogic 10.1 MP1 (Advantage and Premium editions)
Note: To facilitate the use of WebLogic for joint Adobe and BEA customers,
BEA provides the BEA Download site from which you can download
the exact version of WebLogic that LiveCycle ES requires.
Note: It is recommended that WebSphere installations use the latest
FixPack and SR.
Web browser
For a list of web browsers, see “Web browser support” on page 30.
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Supported software
Required software
Supported version
JDK
●
JBoss on all platforms: Sun JDK 1.5.0_11 (or later version of the 1.5.0
release) available at Sun Developer Network.
●
WebLogic on all platforms except Solaris: BEA JRockit SDK 1.5.0_06 or
later updates of 1.5.0
●
WebLogic on Solaris: Sun JDK 1.5.0_04. Requires the Daylight Savings
Time (TZ) update, available at Sun Updater Tool, to be run in North
America.
●
WebSphere on all platforms except Solaris: IBM JDK 1.5.0 SR4 (available
for download from IBM).
●
WebSphere on Solaris: Sun JDK 1.5.0_09
For more information about JDKs, see “LDAP configuration” on page 38.
To use AES 256 encryption, obtain and install the Java Cryptography
Extension (JCE) Unlimited Strength Jurisdiction Policy files from the Java SE
Downloads.
Note: These requirements are optional and required only if you need to use
Advanced Encryption Standard (AES) 256.
32-bit JDK (required
for 64-bit Java
application server
only)
●
Database
●
Sun JDK 1.5.0_11 (or later version of the 1.5.0 release) available at Sun
Developer Network.
●
IBM DB2 8.2 or IBM DB2 9.1
Note: If you are using WebLogic 10.1 MP1 with DB2 9.1 you need to contact
BEA to obtain a custom patch that fixes a DB2 9.1 driver issue;
otherwise, the JDBC connection does not function properly.
●
Microsoft SQL Server 2005 SP2 (Standard and Enterprise Edition)
●
Oracle 9i or 10g (Standard and Enterprise Editions)
Note: LiveCycle ES is compliant with the database vendors' compatibility
statements. (See the vendors' websites.)
Database driver
●
IBM DB2 9.1 driver is required for all supported versions of DB2:
db2jcc.jar and db2jcc_license_cu.jar
●
SQL Server 2005 JDBC 1.1: sqljdbc.jar
●
Oracle 9i and 10g: ojdbc14.jar, Release 2 (10.2.0.2 Thin or later update of
10.2)
Note: All LiveCycle ES Business Activity Monitoring metadata databases
use the drivers listed above.
26
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Supported software
Required software
Supported version
LDAP server
●
Sun ONE 5.1
●
Sun ONE 5.2
●
Microsoft Active Directory 2000
●
Microsoft Active Directory 2003
●
Novell® eDirectory 8.7.3
●
IBM Tivoli Directory Server 6.0
●
IBM Domino Enterprise Server 8.0 and later updates of 8.0
●
Microsoft Exchange 2000
●
Microsoft Exchange 2003
●
Microsoft Exchange 2007
●
Lotus Notes/Domino 6/7
●
SendMail (included with Red Hat 4/5 and SUSE 9)
●
Novel GroupWise 6/7
●
Adobe Flex® Builder™ 2.0.1 Hot Fix 2 or later
Email servers
LiveCycle
Data Services ES
or
●
Flex SDK 2.0.1 Hot Fix 2 or later
●
Flex is required for these tasks:
●
Using LiveCycle Data Services ES
●
Customizing form guides in LiveCycle Designer ES
●
Customizing LiveCycle Workspace ES
●
Creating Flex applications for LiveCycle Workspace ES
●
Calling LiveCycle ES APIs using Flex
27
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Supported software
Required software
Supported version
LiveCycle ES
connector
Connector for EMC® Documentum®:
●
EMC Documentum Content Server 5.3 (and later service packs)
●
EMC Documentum Content Server 6.0 (and later service packs)
In addition, on your LiveCycle ES server, install the version of EMC
Documentum Foundation Classes (DFC) that corresponds to your version of
Content Server. (See Documentum Foundation Classes Installation Guide
available from EMC Documentum.)
Connector for IBM FileNet:
●
IBM FileNet P8 Content Engine 3.5.x
●
IBM FileNet P8 Content Engine 4.0.x
●
IBM FileNet P8 Process Engine 3.5.x
●
IBM FileNet P8 Process Engine 4.0.x
Note: The version of Process Engine should correspond to the version of
your Content Engine (for example, Process Engine 3.5.x for Content
Engine 3.5.x).
In addition, on your LiveCycle ES server, install the version of IBM FileNet P8
Content Java API that corresponds to your version of Content Engine (for
example, 3.5.x Content Java API or 4.0.x Content Engine Java API). For a list
of the required JAR files, see Content Java API Developer's Guide available
from IBM FileNet.
Connector for IBM Content Manager:
●
IBM Content Manager 8.3 (and later fix packs)
In addition, on your LiveCycle ES server, install the version of IBM software
that corresponds to your version of IBM Content Manager:
●
DB2 Universal Database Client (not required if IBM Content Manager is
on same server as the LiveCycle ES server)
●
Information Integrator for Content (II4C) available from IBM
Note: IBM Content Manager running on Oracle database is not supported.
28
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Minimum database user permissions
Required software
Supported version
PDF client
●
Adobe Acrobat® Professional and Acrobat Pro Extended, versions 7.0 to
9.0 (for securing documents with policies and opening policy-protected
documents)
●
Adobe Reader, versions 7.0 to 9.0 (for opening policy-protected
documents)
●
Acrobat Reader 6.0: The following limitations apply:
●
●
LiveCycle Reader Extensions ES supports only UB3, which works
down to Adobe Reader 7.0. Adobe Reader 6.0 supports UB2;
LiveCycle ES does not generate files from UB2.
●
Files from previous versions of Reader Extensions ES work for
submitting forms online or by email.
●
Designer ES, version 8.2, can create PDF forms that support
Adobe Reader 6.0.2 and later.
●
Workspace ES requires Adobe Reader 7.0.5 (and later), 8.0 (and later),
8.1 (and later), and 9.0 (and later).
29
Apple® QuickTime 7 Player or Pro (for converting embedded video to
PDF multimedia)
Minimum database user permissions
This section outlines the minimum database permissions required by the user performing the LiveCycle ES
database initialization and by runtime users.
Database
Initialization permissions
Runtime permissions
Oracle
CREATE SESSION
CREATE SESSION
CREATE CLUSTER
CREATE CLUSTER
CREATE TABLE
UNLIMITED TABLE SPACE
CREATE VIEW
CREATE SEQUENCE
UNLIMITED TABLE SPACE
SQL Server - DB level
Create Table
Create View
Connect
Connect
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Web browser support
Database
Initialization permissions
Runtime permissions
SQL Server - Schema
level
Alter
Insert
Insert
Select
References
Update
Select
Delete
Update
Delete
Refer to “DB2 user account” on
Refer to “DB2 user account” on
page 54 for a complete description. page 54 for a complete description.
DB2
Web browser support
This section outlines the supported web browsers for the LiveCycle ES user interfaces.
End-user user interface
End-user components include these solution components:
●
LiveCycle Workspace ES (Flash Player required)
●
Adobe Flash Player 9.0.115.0 or later is required for Workspace ES or for using form guides in
Workspace ES.
●
LiveCycle Reader Extensions ES (Flash Player required)
●
LiveCycle Rights Management ES (browser only)
●
LiveCycle PDF Generator ES and LiveCycle PDF Generator 3D ES (browser only)
Operating system
Flash Player
Supported browser
Microsoft Windows Vista™
Flash Player 9*
Microsoft Internet Explorer 7 or later(1)
Firefox 2.0.0.1 or later(1)
Windows 2000
Flash Player 9*
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
Windows XP
Flash Player 9*
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
Windows Server 2003
Flash Player 9*
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
OS X v 10.4.x (PowerPC)
Flash Player 9*
Safari 2.x or later (Workspace ES requires version
3.0.3 or later)(2)
OS X v 10.4.x (Intel)
Flash Player 9*
Safari 2.x or later (Workspace ES requires version
3.0.3 or later)(2)
30
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Additional requirements for Linux or UNIX operating systems
31
(1)
“or later” includes maintenance revisions. For example, LiveCycle ES supports Microsoft Internet Explorer
7 and Firefox 2.0.0.1 and maintenance versions of these releases.
(2)
Workspace ES supports Internet Explorer and Firefox on Windows but only Safari 3.0.3 or later on the
Mac platform.
Administrator user interface
This table outlines the supported web browsers for the LiveCycle Administration Console user interface.
Operating system
Flash Player
Supported browser
Microsoft Windows Vista
N/A
Internet Explorer 7 or later(1)
Firefox 2.0.0.1 or later(1)
Windows 2000
N/A
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
Windows XP
N/A
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
Windows Server 2003
N/A
Internet Explorer 6 or later(1)
Firefox 2.0.0.1 or later(1)
OS X v 10.4.x (Intel)
N/A
Safari 2.x or later(1)
(1)“or later” includes major revisions. For example, Microsoft Internet Explorer 6.0 or later also covers
Microsoft Internet Explorer 7.0
Additional requirements for Linux or UNIX operating systems
The installer for LiveCycle ES requires the bc tool to be available on the Linux or UNIX system. Usually, the
bc tool (an arbitrary precision calculator language) is present by default. Ensure that this tool is installed on
the system before you run the installer. If the tool is not present, error messages occur that warn about the
lack of disk space because the bc tool is used to compute whether or not enough disk space is available
before starting the installation. Your operating system vendor may provide the bc tool, or you can get the
GNU bc tool at www.gnu.org.
Note: To verify that the tool is available, execute which bc from the shell. If the tool is available, the path
to the program is displayed.
Additional requirements for PDF Generator ES and PDF Generator 3D ES
This section applies only if your LiveCycle ES installation includes LiveCycle PDF Generator ES or
LiveCycle PDF Generator 3D ES. If you are not installing PDF Generator ES, proceed to “Additional
requirements for Connector for IBM Content Manager” on page 35.
User account on Windows
You must use the same user account for the following tasks:
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Additional requirements for PDF Generator ES and PDF Generator 3D ES
●
Installing Microsoft Office
●
Installing PDF Generator ES or PDF Generator 3D ES
●
Installing Acrobat 9.0 Professional Extended for PDF Generator ES or PDF Generator 3D ES
●
Running the application server process
32
Using 64-bit application servers with PDF Generator ES and
PDF Generator 3D ES
If you are using a 64-bit application server on a Windows or UNIX system with PDF Generator ES or
PDF Generator 3D ES, you must ensure that a supported 32-bit Java 5 JDK is installed in addition to the
64-bit one the application server uses. You must set the following environment variable.
JAVA_HOME_32
Note: PDF Generator 3D ES is supported on Windows environments only.
➤ To set the Windows JAVA_HOME_32 variable:
1. Select Start > Control Panel > System.
2. Click the Advanced tab.
3. Click Environment Variables and, under System Variables, click New.
4. Enter the environment variable JAVA_HOME_32. This directory is the directory that contains the JDK.
For example, type the following code:
D:\Program Files\Java\jdk1.5.0_14
➤ To set the JAVA_HOME_32 environment (UNIX and Linux):
Set the JAVA_HOME_32 variable for the supported Java SDK for Borne and Bash shells as shown in this
example:
JAVA_HOME_32=/opt/jdk1.5.0_11
export JAVA_HOME_32
Note: The specific path varies based on the installation directory you specified and the operating system
you are installing on.
➤ To set the PATH environment variable (UNIX and Linux):
Set the PATH variable for Borne and Bash shells as shown in this example:
PATH=$JAVA_HOME/bin:$PATH
export PATH
Native file conversion software installation
Before you install PDF Generator ES or PDF Generator 3D ES, install the software that supports the file
formats for which PDF conversion support is required and manually activate the licenses for the software.
You must activate one license on each LiveCycle ES server of your cluster for each native application that
PDF Generator ES or PDF Generator 3D ES supports. Refer to the individual licensing agreement for each
native application that your LiveCycle ES deployment will support, and ensure that your LiveCycle ES
deployment meets the licensing requirements specified. Typically, each LiveCycle ES user who will use
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
System Requirements for Installing LiveCycle ES
Additional requirements for PDF Generator ES and PDF Generator 3D ES
33
native application support must also have an activated license on their own computer for the native
application.
PDF Generator ES or PDF Generator 3D ES can be extended to convert these additional file types to PDF
files by using the following applications:
●
Microsoft Office 2000, XP, or 2003 (DOC, XLS, PPT, RTF, TXT)
●
Microsoft Office 2007 (DOC, XLS, PPT, RTF, TXT, Microsoft Office open XML Formats)
●
Microsoft Office Visio 2003, 2007 (VSD)
●
Microsoft Publisher 2003, 2007 (PUB)
●
Microsoft Project 2003, 2007 (MPP)
●
AutoCAD 2005, 2006, 2007, 2008 (DWG, DXF, DWF)
●
Corel WordPerfect 12 (WPD)
●
Adobe Photoshop® CS2
●
Adobe FrameMaker® 7.2, 8 (FM)
●
Adobe PageMaker® 7.0 (PMD, PM6, P65, PM)
●
OpenOffice 2.4 and 3.x (ODT, ODP, ODS, ODG, ODF, SXW, SXI, SXC, SXD)
You do not need to install a native software application to convert the following native file formats:
●
Print files (PS, PRN, EPS)
●
Web files (HTML)
●
Image files (JPEG, GIF, BMP, TIFF, PNG)
Acrobat
PDF Generator ES or PDF Generator 3D ES requires that Acrobat 9 Pro Extended is installed. You must
install Acrobat before you run the LiveCycle ES installer. Acrobat Pro Extended is provided with the
LiveCycle ES media or as an option for ESD downloads.
You also need to update the Acrobat_PATH environment variable and restart the application server.
Note: The Acrobat_PATH environment variable is case-sensitive.
To use AES 256 encryption, you must obtain and install the Java Cryptography Extension (JCE) Unlimited
Strength Jurisdiction Policy files from Java SE Downloads.
Note: These requirements are optional and required only if you need to use Advanced Encryption
Standard (AES) 256 with Acrobat 9 Pro Extended.
QuickTime 7
PDF Generator ES or PDF Generator 3D ES requires that QuickTime 7 (Player or Pro) is installed if you want
to convert video embedded in files, such as PowerPoint presentations to PDF multimedia files. This
application is available from the Apple Downloads site.
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Additional requirements for PDF Generator ES and PDF Generator 3D ES
34
Setting Windows environment variables
You must set the environment variables in Windows if you plan to create PDF documents from
applications such as FrameMaker, Photoshop, PageMaker, WordPerfect, and Acrobat.
The names of these environment variables are listed here:
●
FrameMaker_PATH
●
Notepad_PATH
●
OpenOffice_PATH
●
PageMaker_PATH
●
Photoshop_PATH
●
WordPerfect_PATH
These environment variables are optional and need to be set only if you plan to use the corresponding
application to convert PDF files through PDF Generator ES or PDF Generator 3D ES. The value of the
environment variable should contain the absolute path of the executable that is used to start the
corresponding application.
For example, the variable Photoshop_PATH may contain the value D:\Program Files\Adobe\
Adobe Photoshop CS3\Photoshop.exe. However, OpenOffice_PATH is different from others. This
variable must be set to the OpenOffice installation folder (instead of the path to the executable). A typical
value of OpenOffice_PATH on Windows would be C:\Program Files\OpenOffice.org 2.0\.
Paths for Microsoft Office applications such as Word, PowerPoint, Excel, Visio, and Project or for AutoCAD
are not required. The Generate PDF service starts these applications automatically if they are installed on
the server.
➤ To set the Windows environment variables:
1. Select Start > Control Panel > System.
2. Click the Advanced tab.
3. Click Environment Variables and, under System Variables, click New.
4. Enter the environment variable name you need to set (for example, Photoshop_PATH). This directory
is the directory that contains the executable file. For example, type the following code:
D:\Program Files\Adobe\Adobe Photoshop CS3\Photoshop.exe
IPP Client installation
PDF Generator ES includes an Internet Printing Protocol (IPP) client installer for installation of the
PDF Generator ES Internet printer. After the installation is completed, a PDF Generator ES printer is added
to the list of existing printers on the clients computer. This printer can then be used to send documents for
conversion to PDF. For more information about installing the IPP client, see Installing and Deploying
LiveCycle ES document for your application server.
Note: The PDF Generator ES IPP Client is only supported on the following 32-bit Windows platforms:
Windows XP, Windows 2000, Windows Server 2003, Windows Vista.
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Additional requirements for Connector for IBM Content Manager
35
Service Control Manager command line tool
Before you complete an automatic installation of PDF Generator ES on Windows, ensure that the Service
Control Manager command line tool, sc.exe, is installed in the Windows environment. Some Windows
servers do not have this software preinstalled. By default, the sc.exe file is installed in the
C:\Windows\system32 directory. Most OS installations have this tool installed. If you do not have the tool
installed, it is available in the Windows Resource Kit for your specific version of Windows. To confirm that
the tool is installed on your server, type sc.exe from a command prompt. The tools usage is returned.
Headless mode configuration
If you are running PDF Generator ES in a headless mode environment (that is, on a server without a
monitor, keyboard, or mouse), the x11 libraries must be installed. Some flavors of Linux do not install these
libraries by default; therefore, you must obtain the libraries and install them manually. For more
information, see the Help system for your operating system.
Additional requirements for Connector for IBM Content Manager
These requirements are optional and required only if you are installing
LiveCycle ES Connector for IBM Content Manager.
LiveCycle ES Connector for IBM Content Manager requires the following software installed (both available
from the IBM website):
●
DB2 Universal Database Client
●
IBM Information Integrator for Content (II4C)
The following sections describe how to configure these applications. Specific application server
configurations are described in the “Post-Deployment Activities” chapter in the Installing and Deploying
LiveCycle ES document for your application server.
➤ To configure the connection for a single IBM Content Manager datastore:
1. Start the DB2 Configuration Assistant.
2. Click Selected > Add Database Using Wizard.
3. Select Manually Configure a Connection to a Database and click Next.
4. Select TCP/IP and click Next.
5. Specify the following TCP/IP communication options and then click Next:
●
In the Host Name box, type the host name of the server hosting DB2 Content Manager.
●
Leave the Service Name box empty.
●
In the Port Number box, type the port number. The default DB2 Content Manager port number is
50000.
6. In the Database Name box, type the IBM Content Manager datastore name and, in the Database Alias
box, type the alias name for the datastore and then click Next.
7. Click Next to accept the default data source settings.
8. In the Operating System list, select the operating system you are using and then click Next.
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Additional requirements for Connector for IBM Content Manager
36
9. Specify the following system options and then click Next:
●
In the System Name box, type the server name hosting DB2. If you click Discover, DB2 Content
Manager searches for the system name you specified and, if the system is not found, all of the DB2
instances are listed.
●
In the Host Name box, type the name of the host, or click View Details to show the domain and IP
address of the system you named in the previous step.
●
In the Operating System list, select the operating system (Windows, Linux, or AIX) on which you
deployed DB2 Content Manager.
10. (Optional) To specify Security options, select Use Authentication Value in Server’s DBM
Configuration and click Finish.
11. In the Test Connection dialog box, test the connection as required.
➤ To configure connections for multiple IBM Content Manager datastores:
1. Configure the initial connection by following the steps in “To configure the connection for a single IBM
Content Manager datastore:” on page 35.
2. Add additional database connections by modifying the cmbicmsrvs.ini file (the file that stores the
datastore information) as follows:
●
From a command prompt window, change the directory to [II4C home]/bin (for example,
C:\program files\db2cmv8\ on Windows or /opt/IBM/db2cmv8 on Linux or UNIX).
●
Run the cmbenv81.bat (Windows) or cmbenv81.sh (UNIX/Linux) file to set the environment and the
classpath for the Java Utilities of II4C.
●
Change the directory to [II4C working directory]/cmgmt/connectors where [II4C working directory] is
one of the following paths:
(Windows) C:/Program Files/db2cmv8
(Linux, AIX) /home/ibmcmadm
(Solaris) /export/home/ibmcmadm
●
Run the command java com.ibm.mm.sdk.util.cmbsrvsicm -a add -s <library
server database name> -sm <database schema name>, where <library server
database name> is the same as Database Alias configured in step 6 above.
Note: The following procedure allows users without DB2 rights to share the connection credentials
through the cmbicmenv.ini file.
➤ To configure a multiuser connection to the IBM Content Manager datastore:
1. From a command prompt window, change the directory to [II4C home]/bin (for example, C:\program
files\db2cmv8\ on Windows or /opt/IBM/db2cmv8 on Linux or UNIX).
2. Run the cmbenv81.bat (Windows) or cmbenv81.sh (UNIX/Linux) file to set the environment and the
classpath for the Java Utilities of II4C.
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Additional requirements for Connector for IBM Content Manager
37
3. Change the directory to [II4C working directory]/cmgmt/connectors, where [II4C working directory] is
one of the following paths:
(Windows) C:/Program Files/db2cmv8
(Linux, AIX) /home/ibmcmadm
(Solaris) /export/home/ibmcmadm
4. Run the command java com.ibm.mm.sdk.util.cmbenvicm -a add -s <library server
database name> -u <database user ID> -p <database password>, where <library
server database name> is the same as Database alias configured in step 6 above.
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
LDAP configuration
38
LDAP configuration
This configuration is optional and required only if you are using an LDAP directory to authenticate users.
When you upgrade LiveCycle Policy Server 7.x or Rights Management ES 8.0, LDAP configuration settings
are automatically migrated.
Install and configure your LDAP server and database according to the vendor’s documentation. For a list of
supported LDAP servers, see “Supported software” on page 25. Make note of the LDAP administrator
name and password to use during the LiveCycle ES configuration process. Configure LiveCycle ES to
connect with the LDAP database after you install and deploy your LiveCycle ES services. This configuration
is done by using the User Manager service. See the Installing and Deploying LiveCycle ES document for your
application server.
Global document storage directory
The global document storage (GDS) directory is used to store long-lived files that are used within a process
as well as critical LiveCycle ES product components. The lifetime of long-lived files is intended to span
multiple restarts of a LiveCycle ES system, and can span for days and even years. These files may include
PDF files, policies, or form templates. Long-lived files are a critical part of the overall state of many
LiveCycle ES deployments. If some or all long-lived documents are lost or corrupted, the LiveCycle ES
server may become unstable. Input documents for asynchronous job invocation are also stored in the GDS
directory and must be available in order to process requests. Therefore, it is important that you consider
the reliability of the file system that hosts the GDS directory.
Planning and creating the global document storage directory
You should plan the location, size, access rights, and security aspects of your GDS directory in advance (see
“Location of the global document storage directory” on page 38, “Sizing factors for the global document
storage directory” on page 39, and “Securing the global document storage directory” on page 39). You
should also plan the backup strategy and practices that you will implement (see “Backing up the global
document storage directory” on page 39).
Create a shared file system for the GDS directory on any computer that is accessible by each node in the
LiveCycle ES cluster, and ensure that all nodes of the cluster have read and write permissions for the
directory.
You must create the GDS directory before you initialize the LiveCycle ES database.
Location of the global document storage directory
You configure the location of your GDS directory with LiveCycle Configuration Manager after you install
LiveCycle ES. The GDS directory you specify should be highly available and should have low access time to
enhance performance.
You must specify the shared directory that you create for GDS. You cannot use the default location in a
cluster environment.
You can change the GDS directory location after completing the installation (see Administering
LiveCycle ES), but this is not a trivial procedure. Plan an appropriate location for the GDS directory that will
be long-lived.
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
System Requirements for Installing LiveCycle ES
Sizing factors for the global document storage directory
39
Caution: Component deployment will fail on Windows if the GDS directory is at the drive root (for
example, D:\). For GDS, you must make sure that the directory is not located at the root of the
drive but is located in a subdirectory. For example, the directory should be D:\GDS and not
simply D:\.
Sizing factors for the global document storage directory
The size of the shared directory depends on expected LiveCycle ES usage factors for the deployment. You
should allocate a minimum of 10 GB of disk space for the GDS directory, but the following factors also
affect the sizing:
●
The typical volume of documents that LiveCycle ES processes. Processing high volumes of documents
requires a larger GDS directory.
●
The typical size of documents that LiveCycle ES processes. Processing large documents requires a
larger shared GDS directory.
●
The complexity of documents that LiveCycle ES processes. Processing complex documents (that is,
documents that are processed by multiple LiveCycle ES services or are processed by different members
of the cluster) requires a larger GDS directory.
Securing the global document storage directory
Access to the GDS directory must be secure. The long-lived documents in this directory may contain
sensitive user information, such as information that requires special credentials when accessed by using
the LiveCycle ES SDK or user interfaces.
Use a security method that is appropriate to your operating system. It is recommended that only the
operating system account that is used to run the application server has read and write access to this
directory.
Note: Incorrectly deleting files or directories from the GDS directory can render the LiveCycle ES
installation inoperative.
Backing up the global document storage directory
The GDS directory should be backed up to allow administrators to restore LiveCycle ES in case of failure.
(See Administering LiveCycle ES.)
If the GDS directory becomes unavailable or is lost due to failure, LiveCycle ES will not run until the GDS
directory and database are restored by a consistent back up or LiveCycle ES is reinitialized with a new
installation.
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
System Requirements for Installing LiveCycle ES
LiveCycle ES Business Activity Monitoring requirements
40
LiveCycle ES Business Activity Monitoring requirements
The following recommendations are required only if you are installing the
LiveCycle ES Business Activity Monitoring solution component.
Basic requirements
This section describes the basic requirements for installing, deploying, and running
Business Activity Monitoring. It covers the following requirements:
●
Dedicated JVM
●
Client memory
●
Web browser
●
Mail server
Dedicated JVM
Business Activity Monitoring requires a dedicated JVM. If you are deploying LiveCycle ES and
Business Activity Monitoring on the same computer, be aware that Business Activity Monitoring must run
on a dedicated JVM. This requires that Business Activity Monitoring is deployed separately from
LiveCycle ES as follows:
●
If deployed on JBoss, the two applications must be deployed on two completely separate JBoss
implementations.
●
If deployed on WebLogic or WebSphere, the two applications must be deployed on completely
separate server definitions.
Client memory
The client computer that accesses Business Activity Monitoring should have a minimum of 512 MB RAM
(1.0 GB is recommended).
Web browser
Business Activity Monitoring is tested for Microsoft Internet Explorer 6.0 (with patch 828750) or later
browser for accessing BAM Workbench.
Note: You must also install Adobe Flash, version 8.0 or later.
Note: If your implementation of Business Activity Monitoring is running in an Asian language, you must
configure the browser for the appropriate language support. See the documentation for Internet
Explorer or Windows.
Mail Server
Business Activity Monitoring requires a running Simple Mail Transfer Protocol (SMTP) email server for
delivering email notifications. The server is external to Business Activity Monitoring and is managed by
your email system administrator. Contact that administrator to set up an account specifically for
Business Activity Monitoring. You need an account and password for sending mail, an address to use in the
From address field, and the name of the email server host.
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Creating the Business Activity Monitoring metadata database
41
Creating the Business Activity Monitoring metadata database
You must create a Business Activity Monitoring metadata database to store the definitions of the process
metrics that BAM Server monitors, as well as the details of any alerts and object run-time data that need to
be persisted to disk.
Because Business Activity Monitoring metadata can grow quite large, you must allocate at least 50 MB for
the BAM Server metadata database. For production deployments, allocate at least 200 MB.
BAM Server can require specific settings for some aspects of the BAM Server metadata database
configuration. The settings depend on the type of application server that is hosting BAM Server and the
type of database server that is used to store the BAM Server metadata.
The following three tables provide information about which databases are supported for BAM Server
metadata databases for JBoss, Weblogic, and WebSphere.
You need to create a user account that BAM Server can use to connect to the BAM Server metadata
database. For database permissions, see “Minimum database user permissions” on page 29.
JBoss requirements
The following tables describe the database and system requirements for installing and deploying
Business Activity Monitoring on JBoss Application Server.
Disk space: 115 MB
Metadata database:
Database
JDBC driver
DB2 8.2
●
db2jcc.jar
●
db2jcc_license_cu.jar
●
Oracle thin driver (ojdbc14.jar)
●
Oracle thick driver (OCI)
Oracle 9.2 or later
Note: Use the Oracle 10G JDBC driver
for both configurations.
MS SQL Server 2000
●
sqljdbc.jar
OR
●
mssqlserver.jar
●
msbase.jar
●
/msutil.jar
Note: The sqljdbc.jar driver is
backward-compatible to version
2000.
MS SQL Server 2005
●
sqljdbc.jar
Note: Ensure that the version 2000
drivers are not in the classpath.
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
WebLogic requirements
42
Note: A Microsoft issue exists with the sqljdbc.jar driver, which is addressed in the Microsoft Knowledge
Base Article 917054.
Note: The sqljdbc.jar driver is backward-compatible to version 2000. However, if you use the 2005 driver
(sqljdbc.jar), ensure that the version 2000 drivers are not in the classpath.
WebLogic requirements
The following table describes the database and system requirements for installing and deploying
Business Activity Monitoring on WebLogic Server.
Disk space: 750 MB
Metadata database:
Database
JDBC driver
IBM DB2
db2jcc.jar
db2jcc_license_cu.jar
SQL Server 2000 plus SP3 or later Embedded BEA drivers for MS SQL
Server
SQL Server 2005
Embedded BEA drivers for MS SQL
Server
Oracle 9.2 or later
Embedded BEA drivers for Oracle thin or
thick drivers
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
WebSphere requirements
WebSphere requirements
The following table describes the database and system requirements for installing and deploying
Business Activity Monitoring on WebSphere Application Server.
Metadata database:
Database
JDBC driver
IBM DB2
●
db2jcc.jar
●
db2jcc_license_cu.jar
●
mssqlserver.jar
●
msbase.jar
●
msutil.jar
MS SQL Server 2000
MS SQLServer 2005
Use the native WebSphere drivers.
(WebSphere 6.1.x only)
Oracle
ojdbc14.jar (from version 10g)
Note: You can use either the OCI (thick)
or thin driver. Use of the thick
driver requires installation of the
Oracle Client.
43
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Synchronizing clock times
44
Synchronizing clock times
You must ensure that all computers in a horizontal cluster synchronize their clock times regularly. Your
LiveCycle ES installation may encounter problems if the node times differ by more than a few seconds.
Apply the standard time synchronization practices employed by your network to all computers of the
LiveCycle ES cluster.
Installation considerations
This section includes considerations for administrators when installing LiveCycle ES.
Installing from network drives
It is recommended that you install LiveCycle ES only from the installation media or a local disk drive.
Attempting to install the software over a network results in considerable delays in starting and installing. It
is also likely that installing from a network drive will add to the length of the directory path, which will
cause the LiveCycle ES installer to prevent the installation from proceeding.
Using LiveCycle ES with a Luna HSM cluster
When using a SafeNet Luna ethernet-attached Hardware Security Module (HSM) cluster, you must ensure
HAOnly mode is enabled on the device.
➤ To enable HAOnly mode on the Luna device
1. Use the vtl tool shipped with the Luna client to determine if HAOnly mode is enabled. Type:
vtl haAdmin –HAOnly -show
2. 1) If HAOnly mode is not enabled, type:
vtl haAdmin –HAOnly -enable
Manual use of Acrobat restricted
If you installed the PDF Generator ES or PDF Generator 3D ES for native document conversion, use of the
bundled Acrobat installation is restricted to the Generate PDF and Generate 3D PDF services and is not
licensed for any other use.
Restricted use of unlicensed Process Management ES functionality
When you install LiveCycle ES in a production environment without licensing Process Management ES,
some core Process Management ES functionality is available but not the following notable exceptions:
●
Run a long-lived process
●
Use a “User Task” in a process
●
Access Workspace ES
If you require any of these features, you must purchase the appropriate license.
Adobe LiveCycle ES
System Requirements for Installing LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
LiveCycle ES IPv6 support
45
LiveCycle ES IPv6 support
LiveCycle ES 8.2 introduces IPv6 support. The default configurations defined in the installation
documentation for LiveCycle ES set IPv4 as the default IP protocol because this protocol has the most
compatibility with third-party infrastructure. It is recommended that IPv6 is not enabled unless there is a
specific requirement for it in your deployment. The number of supported platform configurations is
reduced when enabling IPv6 support with LiveCycle ES. It is recommended that you verify that all
third-party software, hardware, and networks that you plan to use have IPv6 support before you attempt
to enable IPv6.
Caution: When installing on a pure IPv6 WebSphere Application Server environment (that is, no IPv4
addresses at all), you must configure and deploy the LiveCycle ES EAR files manually. The tasks
required are as follows:
●
Run LiveCycle Configuration Manager to configure LiveCycle ES
●
Manually configure WebSphere
●
Manually deploy the LiveCycle ES EAR files
Once these tasks are done, run the following tasks on LiveCycle Configuration Manager:
●
Initialize the LiveCycle ES database
●
Deploy the LiveCycle ES components
●
Validate the LiveCycle ES component deployment
Processes with document form variables and digital signatures
If you are upgrading from a previous version of LiveCycle and changing your LiveCycle ES server, you may
disrupt any processes that use the document form variable or digital signatures. The reason is because
these forms are rendered only once, setting the submit URL. Changing the server breaks the certificate.
Here are possible solutions for avoiding this problem; choose the method that is most appropriate for your
LiveCycle ES environment:
Solution 1: Complete all processes that use a form document variable before you upgrade or move to
the remote server. You might choose this method if you maintain legacy LiveCycle servers after the
upgrade. This approach also eliminates the need for throw-away work to be done to manage the
redirection of the form submissions. This method is not practical if you have many outstanding
processes.
Solution 2: If the server being upgraded is not being decommissioned, a reverse proxy approach is
preferable. With this method, you maintain the reverse proxy on the old system until all the migrated
processes are completed.
Solution 3: You can use the Apache mod_rewrite module to modify the embedded URLs in each
form as they are delivered to the client.
3
LiveCycle ES Credentials and Certificates
This chapter describes how to do the following tasks:
●
Obtain the Adobe LiveCycle Reader Extensions ES Rights credential
●
Obtain digital certificates for use with Adobe LiveCycle Digital Signatures ES
Obtaining the Reader Extensions ES Rights credential
The LiveCycle Reader Extensions ES Rights credential is a digital certificate that is specific to
Reader Extensions ES that enables Adobe Reader usage rights to be activated in PDF documents. If the
credential is not installed, Reader Extensions ES users cannot apply usage rights to documents. You cannot
use a standard digital certificate for this function; you must use the dedicated Rights credential.
The Rights credential extends the usage rights of each PDF file that Reader Extensions ES processes. It is a
critical part of the software licensing and should be stored carefully in a secure environment.
The following types of Rights credentials are available:
Customer Evaluation: A credential with a short validity period that is provided to customers who
want to evaluate Reader Extensions ES. Usage rights applied to documents using this credential expire
when the credential expires. This type of credential is valid only for two to three months.
Production: A credential with a long validity period (currently until 2028) that is provided to customers
who purchased the full product. Production credentials are unique to each customer but can be
installed on multiple systems.
The Rights credential is delivered as a digital certificate that contains the public key, the private key, and
the password used to access the credential.
If your organization orders an evaluation version of Reader Extensions ES, you receive an evaluation Rights
credential from the sales representative you ordered the product from or from the website where you
downloaded the evaluation product.
If your organization purchases a production version of Reader Extensions ES, the production Rights
credential is delivered by Electronic Software Download (ESD). A production Rights credential is unique to
your organization and can enable the specific usage rights that you require.
If you obtained Reader Extensions ES through a partner or software provider who integrated
Reader Extensions ES into their software, the Rights credential is provided to you by that partner who, in
turn, receives this credential from Adobe.
Note: The Rights credential cannot be used for typical document signing or assertion of identity. For these
applications, you can use a self-sign certificate or acquire an identity certificate from a Certificate
Authority (CA).
46
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
LiveCycle ES Credentials and Certificates
Obtaining digital certificates for use with Digital Signatures ES
47
Obtaining digital certificates for use with Digital Signatures ES
Digital certificates are required for use with Digital Signatures ES. Although you can configure and manage
digital certificates after you install and configure LiveCycle ES, obtaining them before you install ensures
that you are ready to use LiveCycle ES when it is deployed.
Digital certificates are obtained from a Certificate Authority (CA) and sent to you by email or over the web
as a certificate file. This certificate file contains the public keys (also called certificates) and references to
private keys (also called credentials) that are used for encrypting and signing documents. Certificates do
not contain actual private keys; instead, they contain a reference to the identity of the user who keeps the
private keys securely stored in an encrypted file or HSM.
You can use Internet Explorer (Windows) or OpenSSL (UNIX) to export PFX, P12, and CER files for
certificates that are stored in any compatible certificate store that is available on your computer. PFX files
can be exported only as the certificate store or the credential itself permits. CER files that hold the public
key that corresponds to a credential can also be exported from PFX files by using either Internet Explorer
or OpenSSL.
Note: You can configure and manage certificates, credentials, and Certification Revocation Lists (CRLs) for
use with LiveCycle ES by using Trust Store Management, which is accessible through the web-based
LiveCycle Administration Console. (See LiveCycle ES Trust Store Management Help.)
The CRL distribution point describes where you can download the CRL that corresponds to a particular
CER or PFX file.
The following file types are supported:
Certificates: DER-encoded X509v3 and base64-encoded certificate (.cer) files. Certificates that verify
the trust.xml file can be either DER-encoded or base64-encoded.
Credentials: RSA and DSA credentials up to 4096 bits in standard PKCS12 format (.pfx and .p12 files).
CRLs: Base64-encoded and DER-encoded CRLfiles.
Maintaining the security of private keys (credentials) is critical to ensuring the stability of sensitive
information. A physical storage device, often called a Hardware Security Module (HSM), typically provides
the maximum level of security for private keys. If you do not use a physical device, it is important to store
highly sensitive private keys and certificates in encrypted files in a safe place.
Digital Signatures ES supports the industry-standard PKCS #11 interface to communicate with HSMs. An
HSM vendor can provide the resources and tools that you need to install and configure an HSM storage
system.
4
Creating the LiveCycle ES Database
This section describes how to set up the database for use with LiveCycle ES.
The database will contain these elements:
●
LiveCycle ES solution component services
●
LiveCycle ES run-time configurations
●
LiveCycle ES process data
●
Customer process definitions and templates
●
Application server managed data, such as JMS tables
Before you create the database, you must ensure that you read the pre-installation requirements and have
the required software installed. (See “System Requirements for Installing LiveCycle ES” on page 17.)
If this is the first installation of LiveCycle ES, you must create an empty database. All the tables required to
support LiveCycle ES are created when you initialize the LiveCycle ES database using LiveCycle
Configuration Manager. (See the Installing and Deploying LiveCycle ES document for your application
server.)
For information about creating the LiveCycle ES Business Activity Monitoring (BAM) metadata database for
LiveCycle Process Management ES, see the Installing and Deploying LiveCycle ES document for your
application server.
Database configuration requirements
This section describes special tables, indexes, and other properties that are required in the LiveCycle ES
database that are not configured by LiveCycle Configuration Manager.
Creating an Oracle database
If you prefer not to use the default database that was created when you installed Oracle 9i or Oracle 10g,
create a new database by using the Database Configuration Assistant tool. LiveCycle ES supports Oracle 9i
and Oracle 10g with WebLogic 9.2, WebLogic 10.1 MP1, WebSphere 6.1.0.7, JBoss 4.0.3 SP1, and JBoss
4.2.0.
These requirements are for creating your Oracle database:
●
The initial database size must be a minimum of 1175 MB (You must increase this initial size if you are
deploying LiveCycle ES Content Services).
●
The database must support UTF-8 encoding.
●
The Database Character Set is Unicode (AL32UTF8), and the National Character Set is AL16UTF16
(Unicode UTF-16 universal character set).
●
The database setting NLS_LENGTH_SEMANTICS is set to BYTE. The database initialization fails if you set
any other value.
48
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
●
Creating the LiveCycle ES Database
Creating a SQL Server database
49
You must install Oracle using Transaction Processing and set the connection mode for the server to
Dedicated Processing.
You must also create a new user account on the database and assign it the following system privileges:
●
CREATE SEQUENCE
●
CREATE VIEW
●
UNLIMITED TABLESPACE
●
CREATE TABLE
●
CREATE CLUSTER
●
CREATE SESSION
For deployments on Linux, the user name must not exceed 8 characters; on Windows, it must not exceed
12 characters.
You need the following information when you configure the data source on the application server:
●
SID (Service ID)
●
User name and password of the Oracle user account
●
Host name or IP address of the database server
●
Oracle port number (default is 1521)
For information about using Oracle 9i or Oracle 10g, see the appropriate user documentation.
Creating a SQL Server database
You can create a SQL Server database that LiveCycle ES will use to store run-time and configuration data.
For information about creating a SQL Server database, refer to the SQL Server documentation. LiveCycle ES
supports SQL Server 2005 SP1 (English and Japanese) with JBoss 4.0.3 SP1 and JBoss 4.2.0, BEA WebLogic
9.2, BEA WebLogic 10.1 MP1, and IBM WebSphere 6.1.0.7.
Create a SQL Server database, and create a user account and assign it DB_OWNER privileges for use when
configuring the data source on the application server. For information about creating the database and
user, see the SQL Server documentation.
You need the following information when you configure the data source on the application server:
●
Database name
●
User name and password of the SQL Server user account
●
Host name or IP address of database server
●
SQL Server port number
The SQL Server database can be configured with the Windows or SQL Server authentication types.
However, for LiveCycle ES, the authentication type must be set to SQL Server.
Adobe LiveCycle ES
Preparing to Install LiveCycle ES (Server Cluster)
Creating the LiveCycle ES Database
Installing the SQL Server database driver
50
Installing the SQL Server database driver
If you have not done so already, download the SQL Server 2005 JDBC Driver 1.1 from the Microsoft
Download Center location on the Microsoft website.
Follow the instructions on the website for downloading and installing the driver. Make a note of the
directory location where you install the driver on your system.
Setting up SQL Server for LiveCycle ES
Before you create the LiveCycle ES database, optimize SQL Server by changing these settings.
Increasing memory
The default SQL Server settings do not aggressively allocate memory. This situation significantly affects
performance on most deployments of a SQL Server database.
Note: This section is recommended but optional.
➤ To increase the memory for SQL Server:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you will host
the LiveCycle ES database.
2. Right-click the database connection and select Properties.
3. Select the Memory page and enter a size in the Minimum Server Memory (in MB) box that is equal to
the size of the free memory on the server.
4. Restart the SQL Server database.
Setting processor priority
On dedicated database servers, which are recommended for production installations of LiveCycle ES, the
SQL Server process is configured so that it does not consume too much of the system CPU resources.
Note: This section is recommended but optional.
➤ To set the processor priority:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you will host
the LiveCycle ES database.
2. Right-click the database connection and select Properties.
3. Select the Processors page and select Boost SQL Server Priority.
4. Restart the SQL Server database.
Adobe LiveCycle ES
Creating the LiveCycle ES Database
Preparing to Install LiveCycle ES (Server Cluster)
Sizing your SQL Server database
51
Increasing the recovery interval
This setting specifies the amount of time the deployment waits for recovery after a crash. The SQL Server
default setting is one minute. Increasing this setting to a larger value improves performance because it
causes the server to write changes from the database log to the database files less frequently. This setting
does not compromise the transactional behavior; however, it does affect the size of the log file that is
replayed on startup.
Note: This section is recommended but optional.
➤ To increase the recovery interval:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you will host
the LiveCycle ES database.
2. Right-click the database connection and select Properties.
3. Select the Database Settings page and type 5 in the Recovery Interval (Minutes) box.
4. Restart the SQL Server database.
Sizing your SQL Server database
The default database sizes that SQL Server provides are too small for LiveCycle ES. Even if the database is
set to auto-grow, unintended effects can occur, such as reduced performance when the database grows or
the growth begins to fragment the disk. It is best to preallocate the database size at creation to reflect your
deployment requirements:
Medium size deployments: Environments where the LDAP directory has approximately 100,000 users
and 10,000 groups. Set Database Data Initial Size to 1 GB, and set autogrowth to 250 MB.
Large size deployments: Environments where the LDAP directory has approximately 350,000 users
and more than 10,000 groups. Set Database Data Initial Size to 2 GB, and set autogrowth to 1 GB.
Note: Database growth is always restricted to a certain size. Administrators should monitor the resource
usage of the LiveCycle ES database to ensure that it does not lose its restricted space or the space
available on the disks where the database resides.
Adobe LiveCycle ES
Creating the LiveCycle ES Database
Preparing to Install LiveCycle ES (Server Cluster)
Creating the LiveCycle ES database user, schema, and login
52
Creating the LiveCycle ES database user, schema, and login
You are now ready to create the LiveCycle ES database user, schema, and login.
Caution: Ensure that you use the SQL_Latin1_General_CP1_CI_AS collation (or the Japanese_CI_AS
collation if your database will run in a Japanese environment) when you create the database
instance for LiveCycle ES. Any other collation may cause your database initialization to fail. The
collation for your LiveCycle ES database instance can be different from the collation used when
creating the SQL Server database.
➤ To create the LiveCycle ES database:
1. Using Microsoft SQL Server Management Studio, click Server, and then right-click Database and select
New Database.
2. Enter the database name of your choice.
Note: The database name is very important, and the name chosen must be consistently used in the
following procedures where a reference to database_name exists.
3. Ensure that Use Full-Text Indexing is deselected.
4. In the Database Data Initial Size MB box, enter the appropriate value:
●
For small development or small production systems, specify 200 MB.
●
For larger systems, see “Sizing your SQL Server database” on page 51.
5. In the Database Data Autogrowth box, enter 50%.
6. In the Database Log Initial Size box, enter the appropriate value:
●
For small development or small production systems, specify 20 MB.
●
For larger systems, see “Sizing your SQL Server database” on page 51.
7. In the Database Log Autogrowth box, enter 50%.
Creating the LiveCycle ES user in SQL Server
In the following procedure, [database_name] represents the name you specified when you created your
database, and [database_username] represents the name you must specify for the new user.
➤ To create the LiveCycle ES user:
1. Using Microsoft SQL Server Management Studio, connect to the database server where you created the
LiveCycle ES database.
2. Click Server > Security, and then right-click Logins and select New Login.
3. Enter the login name [database_username], and then select SQL Server Authentication and type a
new password.
4. Ensure that Enforce Password Expiration. User must change password on next login is also
deselected.
5. Leave the default database as Master, and click OK.
Adobe LiveCycle ES
Creating the LiveCycle ES Database
Preparing to Install LiveCycle ES (Server Cluster)
Creating the LiveCycle ES database user, schema, and login
53
6. Click Server > Databases > [database_name] > Security, and then right-click Schemas and select
New Schema.
7. In the Schema Name box, type [database_username], and click OK.
8. Click Server > Databases > [database_name] > Security, and then right-click Users and select New
User.
9. In the New User dialog box, type the login name and user name [database_username].
10. Set the default schema to [database_username].
Note: The schema name should be the same as the [database_username].
11. In the Schemas Owned By This User area, select the schema [database_username].
12. In the Database Role Membership area, select db_owner.
Associating the LiveCycle ES user with the database
After you create the LiveCycle ES user, associate it with the LiveCycle ES database.
➤ To associate the LiveCycle ES user with the database:
1. Click Security > Logins, and then right-click [database_username] and select Properties.
2. In Login Properties, on the General page, set the user’s default database to [database_name].
3. Select the User Mapping page and, in the Users Mapped To This Login section, verify that
[database_name] is selected, User is set to [database_username], and Default Schema is set to
[database_username].
4. Ensure that [database_name] is selected in the Users Mapped To This Login table, and ensure that
db_owner and public are selected in the Database Role Membership For [database_name] table.
Setting the isolation level for the LiveCycle ES database
SQL Server 2005 provides some new isolation levels. LiveCycle ES requires a specific isolation level to
manage deadlocking when long-running transactions occur at the same time as numerous shorter reads.
➤ To set the isolation level:
1. Click Databases, and then right-click [database_name] and select New Query.
Note: [database_name] represents the name you specified when you created your database.
2. In the Query panel, type the following text:
ALTER DATABASE [database_name]
SET READ_COMMITTED_SNAPSHOT ON
GO
3. Click Execute. A response is displayed in the messages panel.
Adobe LiveCycle ES
Creating the LiveCycle ES Database
Preparing to Install LiveCycle ES (Server Cluster)
Creating a DB2 database
54
Creating a DB2 database
Create a DB2 database by running the script provided in this section. The script is tuned for a system that
will use 1 GB of memory for the database. If your system has less memory dedicated for the database, see
the DB2 documentation for details about configuring your system settings. LiveCycle ES supports DB2
with WebSphere 6.1.0.7, JBoss 4.0.3 SP1, JBoss 4.2.0, WebLogic 9.2, and WebLogic 10.1.
You need the following information when you configure the data source on the application server:
●
Database name
●
User name and password of the DB2 user account
●
Host name or IP address of the database server
●
DB2 port number
DB2 user account
LiveCycle ES requires a dedicated system database account. If the account is the schema owner no other
privileges are required. The schema owner can alter, create and drop any object in the schema. If the
account is not the schema owner then the ALTERIN,CREATEIN AND DROPIN schema privileges are
required. The user will also have to belong to the DB2USERS group.
The DB2 user account needs to have schema owner rights to create tables both at product installation
time and system runtime. The application server may add further requirements to the database user and
schema due to its internal use of the database.
For information about creating a user account, see the DB2 documentation.
For deployments on Linux and UNIX, the user name must not exceed 8 characters; on Windows, it must not
exceed 12 characters.
➤ To create a DB2 database:
1. On the computer that hosts DB2, create a new text file that includes the following DB2 script:
Note: The following text contains formatting characters for line breaks. If you copy this text to a
location outside this document, remove the formatting characters when you paste it to the new
location.
create database dbname using codeset utf-8 territory default;
connect to dbname;
CREATE BUFFERPOOL BP8K SIZE 50000 PAGESIZE 8192 NOT EXTENDED STORAGE;
connect reset;
connect to dbname;
CREATE TEMPORARY TABLESPACE DBNAME_TEMP_8K IN DATABASE PARTITION GROUP
IBMTEMPGROUP PAGESIZE 8192 MANAGED BY SYSTEM USING
('DB2_root\DBNAME_TEMP') EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL BP8K;
CREATE REGULAR TABLESPACE DBNAME_DATA_8K IN DATABASE PARTITION GROUP
IBMDEFAULTGROUP PAGESIZE 8192 MANAGED BY DATABASE USING
(FILE'DB2_root\DBNAME_DATA'64000) EXTENTSIZE 16 PREFETCHSIZE 16
BUFFERPOOL BP8K;
commit work;
connect reset;
connect to dbname;
alter bufferpool ibmdefaultbp immediate size 96000;
Adobe LiveCycle ES
Creating the LiveCycle ES Database
Preparing to Install LiveCycle ES (Server Cluster)
DB2 user account
55
alter bufferpool bp8k immediate size 32000;
commit work;
connect reset;
update db cfg for dbname using dbheap 4000;
update db cfg for dbname using logbufsz 2048;
update db cfg for dbname using locklist 2000;
update db cfg for dbname using chngpgs_thresh 40;
update db cfg for dbname using logfilsiz 4000;
deactivate database dbname;
activate database dbname;
2. (Content Services ES only) If you are using Content Services ES with any of the other solution
components, use the following script:
Note: The following text contains formatting characters for line breaks. If you copy this text to a
location outside this document, remove the formatting characters when you paste it to the new
location.
create database dbname using codeset utf-8 territory default;
connect to dbname;
CREATE BUFFERPOOL BP8K SIZE 50000 PAGESIZE 8192 NOT EXTENDED STORAGE;
CREATE BUFFERPOOL BP32K SIZE 4000 PAGESIZE 32768 NOT EXTENDED STORAGE;
connect reset;
connect to dbname;
CREATE TEMPORARY TABLESPACE DBNAME_TEMP_8K IN DATABASE PARTITION GROUP
IBMTEMPGROUP PAGESIZE 8192 MANAGED BY SYSTEM USING
('DB2_root\DBNAME_TEMP')
EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL BP8K;
CREATE REGULAR TABLESPACE DBNAME_DATA_8K IN DATABASE PARTITION GROUP
IBMDEFAULTGROUP PAGESIZE 8192 MANAGED BY DATABASE USING
(FILE'DB2_root\DBNAME_DATA'64000) EXTENTSIZE 16 PREFETCHSIZE 16
BUFFERPOOL BP8K;
commit work;
connect reset;
connect to dbname;
CREATE TEMPORARY TABLESPACE DBNAME_TEMP_32K IN DATABASE PARTITION GROUP
IBMTEMPGROUP PAGESIZE 32768 MANAGED BY SYSTEM USING
('DB2_root\DBNAME32k_TEMP') EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL BP32K;
CREATE REGULAR TABLESPACE DBNAME_DATA_32K IN DATABASE PARTITION GROUP
IBMDEFAULTGROUP PAGESIZE 32768 MANAGED BY DATABASE USING
(FILE'DB2_root\DBNAME32k_DATA'9000) EXTENTSIZE 16
PREFETCHSIZE 16 BUFFERPOOL BP32K;
alter bufferpool ibmdefaultbp immediate size 96000;
alter bufferpool bp8k immediate size 32000;
commit work;
connect reset;
update db cfg for dbname using dbheap 4000;
update db cfg for dbname using logbufsz 2048;
update db cfg for dbname using locklist 2000;
update db cfg for dbname using chngpgs_thresh 40;
update db cfg for dbname using logfilsiz 4000;
deactivate database dbname;
activate database dbname;
3. Make the following changes to the script:
Adobe LiveCycle ES
Creating the LiveCycle ES Database
Preparing to Install LiveCycle ES (Server Cluster)
Additional DB2 requirements for LiveCycle Content Services ES
56
●
Replace the instances of dbname and DBNAME with the name you want for the LiveCycle ES
database.
●
Replace DB2_root with the path to the root directory where DB2 is installed.
●
Ensure that no commands include line breaks and each command is terminated by a semicolon (;).
●
Change 9000 in the following line based on your database size:
(FILE'DB2_root\DBNAME_DATA'9000)
This number specifies the minimum number of pages required to initialize the database. You can
also change this number by using the DB2 administration tools after you initialize the database.
4. Save the text file in a location that DB2 Command Line Processor can access.
5. Open a DB2 command prompt and type the following command to run the script:
db2 -tf <path_to_script_file>/<script_file_name>
➤ To add a user to the new database:
1. Log in to the IBM Control Center.
2. Click [database_name] > User and Group Objects > DB Users.
3. Select Add User and select the user.
4. Under Authorities, select Connect to database, Create tables, and Database administration
authority, and then select Grant.
5. Click OK.
Additional DB2 requirements for LiveCycle Content Services ES
The script described in step 2 in “To create a DB2 database:” on page 54 creates an additional DB2
database page size and sets it to 32 KB. If LiveCycle Content Services ES is not being deployed, the default
DB2 database page size of 8 KB is acceptable.
.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement