bbc Configuring LiveCycle Application Server Clusters Using WebLogic Adobe LiveCycle June 2007 Version 7.2

(1)

bb

c

Configuring LiveCycle

®

Application

Server Clusters Using WebLogic

Adobe

®

LiveCycle

®

(2)

Adobe® LiveCycle® 7.2 Configuring LiveCycle Application Server Clusters Using WebLogic for Microsoft® Windows®, Linux®, and UNIX® Edition 2.0, June 2007

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 and company logos in sample material or in the sample forms included in this software are for demonstration purposes only and are not intended to refer to any actual organization.

Adobe, the Adobe logo, LiveCycle, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

BEA WebLogic Server is a registered trademark of BEA Systems, Inc.

DB2 is a trademark of International Business Machines Corporation in the United States, other countries, or both. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Microsoft and Windows 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.

SUSE is a trademark of Novell, Inc. in the United States and other countries.

Sun, Java, and Solaris are trademarks or registered trademark of Sun Microsystems, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group in the US and other countries.

All other trademarks are the property of their respective owners.

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.

(3)

3

Installing the Application Servers ... 15

Preparing to install...15

Installing WebLogic Server ...15

Configuring anonymous admin lookup ...17

Configuring the WebLogic transaction time-out ...18

Creating an endorsed directory...19

Copying LiveCycle JAR files ...19

Increasing the WebLogic Server thread count ...19

Copying and editing files ...20

3

Configuring the Database... 22

Creating the database ...22

Creating an Oracle database...22

Creating a SQL Server database...22

Installing JTA stored procedures...23

Enabling XA transactions for Windows Server 2003...24

Installing database drivers...24

(4)

Adobe LiveCycle Contents

Configuring LiveCycle Application Server Clusters Using WebLogic 4

4

Setting Up WebLogic Clusters ... 28

Creating the WebLogic cluster ...28

Starting the cluster ...31

Starting the Administration Server...31

Configuring Node Manager ...31

Starting Node Manager ...33

Starting Node Manager as a service ...33

Starting Node Manager with a script...33

Command syntax for starting Node Manager...33

Starting Managed Servers...34

Configuring WebLogic Managed Servers...34

Configuring server resources ...35

Configuring JDBC resources ...35

Configuring JDBC resources for LiveCycle Policy Server...35

Configuring JDBC resources for all products except LiveCycle Policy Server ...37

Configuring JMS resources...39

Configuring queue and topic throttling...44

5

Maintaining WebLogic Clusters... 46

Performing a graceful shutdown of all servers...46

Performing a forced shutdown of all servers ...46

Creating a new server ...47

Starting all Managed Servers ...47

Adding a server to the cluster...48

Removing a server from the cluster...48

6

Installing the Web Servers ... 49

Preparing for installation...49

Installing the web server under Linux or UNIX...49

Installing the web server under Windows...50

7

Common Components ... 52

Large document handling ...52

Queues and topics ...52

JMS connection pool sizes...52

JMS stores ...52

Queue and topic throttling ...52

Distributed destinations...53

Common elements between LiveCycle products ...53

Configuring LiveCycle Workflow properties ...54

Scheduler property definition and values that can be added...54

Cache configuration properties...55

Configuring caching properties for User Management...57

Adding property definitions ...57

Email receiver configuration...58

8

Clustering LiveCycle Products ... 59

About deploying LiveCycle products to a cluster ...59

Summary of deployable components ...59

Deploying LiveCycle products...60

Viewing log files...61

Bootstrapping LiveCycle products...62

(5)

Adobe LiveCycle Contents

Configuring LiveCycle Application Server Clusters Using WebLogic 5

9

Issues with Clustering ... 65

LiveCycle Forms preferences do not get propagated ...65

LiveCycle Reader Extensions UI is not supported in a cluster...65

(6)

6

Preface

This document explains how to deploy an Adobe® LiveCycle® server product individually in a clustered environment.

Who should read this guide?

This guide provides information for administrators or developers responsible for installing, configuring, administering, or deploying LiveCycle products. The information provided is based on the assumption that anyone reading this guide is familiar with BEA WebLogic Server® application servers, RedHat Linux®, SUSE™ Linux, Microsoft® Windows®, or Sun™ Solaris™ operating systems, MySQL, Oracle®, DB2®, or SQL Server database servers, and web environments.

Versions

This document describes clustering for LiveCycle 7.2.

Conventions used in this guide

This guide uses the following naming conventions for common file paths.

Name Default value Description

[LiveCycle root] Windows:

C:\Adobe\LiveCycle\ Linux and UNIX®: /opt/adobe/livecycle/

The installation directory that is used for all LiveCycle products. The installation directory contains subdirectories for Adobe Configuration Manager, product SDKs, and each LiveCycle product installed (along with the product documentation).

[appserver root] Windows:

C:\bea\weblogic81\ Linux and UNIX: /opt/bea/weblogic81

The home directory of the application server that runs the LiveCycle products.

BEA_HOME Windows C:\bea Linux, UNIX: /opt/bea

The install directory for WebLogic as specified for the BEA_HOME environment variable.

(7)

Adobe LiveCycle Preface Configuring LiveCycle Application Server Clusters Using WebLogic Related documentation 7

Most of the information about directory locations in this guide is cross-platform (all file names and paths are case-sensitive on Linux). Any platform-specific information is indicated as required.

Updated LiveCycle product information

Adobe Systems has posted a Knowledge Center article to communicate any updated LiveCycle product information with customers. You can access the article at:

(9)

9

1

Overview

This section describes clustered application servers and the benefits and issues associated with setting up clusters.

About clustering application servers

A cluster is a group of application server instances running 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 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 being 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 BEA WebLogic Server 8.1.

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

(10)

Adobe LiveCycle Overview Configuring LiveCycle Application Server Clusters Using WebLogic Failover 10

Failover

Failover allows one application server instance to act as a backup to a failed application server instance and resume processing the task, thereby enabling one 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. Some products, such as LiveCycle Workflow, can recover process states at the step and process levels.

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 with 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 have been 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 roughly 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, thus 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. WebLogic 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.

(11)

Adobe LiveCycle Overview Configuring LiveCycle Application Server Clusters Using WebLogic Terminology 11

Terminology

WebLogic uses specific terminology, which is defined here to avoid confusion:

Server: Represents an instance of a Java™ virtual machine (JVM).

Machine: Represents a physical system running one or more WebLogic Servers.

Cluster: Represents a logical grouping of multiple application servers within a domain for administration, application deployment, load balancing, and failover purposes.

Clustering LiveCycle products

If you install a LiveCycle product on an application server cluster, here are a few things you must know:

● (All LiveCycle products except LiveCycle PDF Generator Professional and

LiveCycle PDF Generator Elements) You are required to install the product only on the server that runs the WebLogic domain Administration Server.

● (LiveCycle PDF Generator Professional and LiveCycle PDF Generator Elements) You must install the

product on each machine in the cluster.

● LiveCycle must be clustered by using a homogeneous topology (all nodes in the cluster must be

configured identically) on each application server it is deployed to. You can ensure that all modules are configured identically by configuring run-time properties in the single-installation staging area.

● The configuration is deployed using the single entity approach; all nodes in a cluster are deployed as if

deploying to a single node.

For more information, see the appropriate chapter in this guide for the LiveCycle product you are clustering.

Clustering LiveCycle products involves the following tasks: 1. Installing instances of WebLogic Server

2. Setting up the cluster

● Creating the cluster

● Running the Administration Server ● Starting Node Manager

● Running Managed Servers 3. Installing the web servers 4. Configuring resources

● Configuring the JDBC resources ● Configuring the JMS resources 5. Configuring HTTP server failover

(12)

Adobe LiveCycle Overview Configuring LiveCycle Application Server Clusters Using WebLogic Supported topologies 12

Supported topologies

The following sections discuss various topologies, both clustered and non-clustered, that you can employ. For additional information on configuring WebLogic in a cluster, see

edocs.bea.com/platform/suppconfigs/configs81/81_over/overview.html

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.

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 Java Bean (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 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 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.

(13)

Adobe LiveCycle Overview Configuring LiveCycle Application Server Clusters Using WebLogic Adding additional application servers 13

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 application server capabilities, failover and load balancing. Clustering application servers has these benefits:

● Allows you to use cheaper hardware configurations and still achieve higher performance ● Allows you to upgrade software on servers without downtime

● Provides higher availability (that is, if one server fails, the other nodes in the cluster pick up the

processing)

● 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 products are typically CPU-bound and, 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 utilizing the processing power of a machine. Creating additional JVM processes provides multiple thread pools, each corresponding to the JVM process associated with each application server process. This

correspondence avoids concurrency limitations and lets the application server use the full processing power of the machine.

Load balancing: Vertical scaling topologies can use the WebLogic 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 machine continue to process client requests.

JMS messaging

You can configure embedded JMS in various topologies:

● Single WebLogic Server, with a single JMS server ● Multiple WebLogic Servers, with a single JMS server

● Multiple WebLogic Servers, 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, nor can it be managed by WebLogic Server.

Using multiple WebLogic Servers with a single embedded JMS server is not supported by many LiveCycle products, such as LiveCycle Workflow and LiveCycle Form Manager. Each node requires its own

(14)

Adobe LiveCycle Overview Configuring LiveCycle Application Server Clusters Using WebLogic Unsupported topologies 14

Unsupported topologies

The following topologies are not supported for LiveCycle.

Splitting the web container/EJB container

Splitting LiveCycle 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 does not support this configuration because LiveCycle components cannot be pulled apart to run on different hosts; LiveCycle is deployed as a monolithic application.

(15)

15

2

Installing the Application Servers

You can install WebLogic Server on each machine in the cluster or you can install the application server on a single machine. The Administration Server should be installed on one of the servers, but not necessarily on one of the servers in the cluster.

Preparing to install

Before installing WebLogic, the following configuration tasks must be performed:

Disk space: Ensure that the partition that will hold the application server has a minimum of 10 GB of free disk space.

IP address settings: All of the computers must have a fixed IP address managed through a single DNS.

IP multicast: All of the computers must fully support IP multicast packet propagation, which means all routers and other tunneling technologies must be configured to propagate multicast messages to clustered server instances. The network latency must be low enough to ensure that most multicast messages reach their final destination within 200 to 300 milliseconds. Finally, the multicast

Time-To-Live (TTL) value for the cluster must be high enough to ensure that routers do not discard multicast packets before they reach their final destination.

Versions: All of the computers in the cluster must have the same version and same service pack of WebLogic Server software.

Installing WebLogic Server

The following procedure details how to install WebLogic Server. It is assumed that you have downloaded and unzipped the installation file to an installation directory, and have opened a system terminal and navigated to that directory.

For each WebLogic Server, perform the following procedure.

➤ To install WebLogic Server 8.1:

1. Run the installation program appropriate for your operating system:

● (Windows) platform815_win32.exe ● (Linux) platform815_linux.bin

● (Solaris) platform815_solaris.bin

2. In the Welcome window, click Next.

3. In the BEA License Agreement window, select Yes and click Next.

4. In the BEA Home Directory box, type the home directory for your WebLogic installation and click

Next.

(16)

Adobe LiveCycle Installing the Application Servers Configuring LiveCycle Application Server Clusters Using WebLogic Installing WebLogic Server 16

6. In the Choose Product Directory window, in the Product Installation Directory box, type the installation directory for this server installation and click Next.

7. In the Installation Complete window, deselect Run Quickstart and click Done.

➤ To create a WebLogic domain:

1. From a command prompt, start the WebLogic Configuration Wizard by navigating to the

[appserver root]/common/bin directory and entering the following command:

● (Windows) config.cmd ● (Linux, UNIX) config.sh

2. On the Create or Extend a Configuration screen, select Create a new WebLogic configuration and click Next.

3. On the Select a Configuration Template screen, select Basic WebLogic Server Domain and click Next. 4. On the Choose Express or Custom Configuration screen, select Express and click Next.

5. Type your user name and password, confirm the password by retyping it, and then click Next. 6. In the left panel, select Production Mode.

7. In the right panel, select BEA Supplied SDKs and Sun SDK 1.4.2_08@[BEA_HOME]/jdk142_08, and then click Next.

8. On the Create WebLogic Configuration screen, from the Summary View list, select Deployment and click Create. You have the option of changing the default domain from mydomain; however, all machines in the cluster must use the same domain name.

9. On the Creating Configuration screen, when the configuration creation is 100% complete, do the following step:

● (Windows) Select Start Admin Server and click Done.

● (Linux, UNIX) Click Done. Start the server by navigating, from a command prompt, to the

[appserverdomain] and entering startWebLogic.sh

Note: You must provide execute permissions on the startWeblogic.sh script in the mydomain

directory.

10. When prompted, enter the WebLogic administrative user name and password you provided in step 5.

➤ To create a new WebLogic Managed Server:

1. If WebLogic Administration Server is not already running, from a command prompt, navigate to the

BEA_HOME\user_projects\domains\[domainname] directory, and enter the following command:

● (Windows) startWebLogic.cmd

● (Linux, UNIX) startWebLogic.sh

2. Start WebLogic Administration Console by typing http://[host name]:7001/console in the URL line of a web browser.

3. Type the user name and password that were used in creating this WebLogic configuration, and then click Sign In.

(17)

Adobe LiveCycle Installing the Application Servers Configuring LiveCycle Application Server Clusters Using WebLogic Configuring anonymous admin lookup 17

4. Right-click Servers and select Configure a New Server.

5. Name the new server (for example, server1) and, in the Listen Port box, type a different value, such as 8001. (Port 7001 is already being used by the Administration Server.)

6. Click Create.

7. From a command prompt, stop WebLogic by navigating to the

BEA_HOME\user_projects\domains\[domainname] directory, and entering the following command:

● (Windows) stopWebLogic.cmd adminusername

● (Linux, UNIX) stopWebLogic.sh adminusername

8. When prompted, type the administrator password and press Enter.

9. Start WebLogic Administration Server by entering the following command:

● (Windows) startWebLogic.cmd ● (Linux, UNIX) startWebLogic.sh

10. Start Node Manager by navigating to the [appserver root]/server/bin directory and entering the following command:

● (Windows) startNodeManager.cmd ● (Linux, UNIX) startNodeManager.sh

11. Start WebLogic Server Administration Console by typing http://[host name]:7001/console in the URL line of a web browser.

12. In the navigation tree, click Machines. 13. Click Configure a New Machine.

14. Type a name for the new machine, and then click Create.

15. Select Servers, click the WebLogic Managed Server you just created, and then select the machine you just created.

16. Click Apply.

17. Start the WebLogic Managed Server by selecting mydomain > Control Tab and clicking Start all Managed Servers.

Configuring anonymous admin lookup

You must enable anonymous admin lookup on the application server. This section only applies to the Administration Server.

➤ To enable anonymous admin lookup:

1. Start WebLogic Server Administration Console by typing http://[host name]:7001/console in the URL line of a web browser.

(18)

Adobe LiveCycle Installing the Application Servers Configuring LiveCycle Application Server Clusters Using WebLogic Configuring the WebLogic transaction time-out 18

3. In the General tab of the Configuration tab, select Anonymous Admin Lookup Enabled and click

Apply.

4. Stop the Managed Server by clicking Domain > Control, and then click Start/Stop. 5. Once stopped, restart the server by clicking Start/Stop.

Configuring the WebLogic transaction time-out

You must increase the WebLogic transaction time-out value. The default value of 30 seconds is insufficient for running your applications. This time-out value must be higher than the value configured at the Job Source (through Administrator). The recommended value is 84600 seconds.

This section only applies to the Administration Server.

➤ To set the WebLogic transaction time-out:

1. Start the WebLogic Server Administration Console by typing

http://[host name]:[port]/console in the URL line of a web browser.

2. Type the user name and password that you created for the WebLogic domain, and then click Sign In. 3. In the navigation tree, select [domain name], click the Configuration tab, and then click the JTA tab.

4. In the Timeout Seconds box, type 84600, and then click Apply.

5. In the navigation tree, select [domain name] > Servers > [servername] and click the Tuning tab.

6. In the Stuck Thread Max Time box, type 1200 and click Apply.

7. Shut down the servers by selecting Domain > Control > Graceful Shutdown of all Managed Servers. Once the shutdown has completed, open a command prompt to the bea domain folder and run the following command:

● (Windows) stopWeblogic.cmd <username> ● (Linux, UNIX) stopWeblogic.sh <username>

Enter the password when prompted.

8. Once stopped, restart the server by running the following command:

● (Windows) startWebLogic.cmd

● (Linux, UNIX) startWebLogic.sh

Enter the user name and password when prompted.

9. When the server is started, log in to the WebLogic Server Administration Console and start the Managed Server by selecting Domain > Control > Start all Managed Servers.

(19)

Adobe LiveCycle Installing the Application Servers Configuring LiveCycle Application Server Clusters Using WebLogic Creating an endorsed directory 19

Creating an endorsed directory

Once all LiveCycle products have been installed, you must create an endorsed directory and copy Java library files to the directory. This directory is required to ensure that the Java run-time environment (JRE) that runs WebLogic uses the classes from the libraries in the endorsed directory instead of the

same-named classes that are identified in the system classpath. Repeat this procedure for each machine to be added to the cluster.

➤ To create an endorsed directory:

1. Navigate to the BEA_HOME/jdk142_08/jre/lib directory and create a directory called endorsed. 2. Copy the following files from the [LiveCycle root]/components/um/endorsed directory to the endorsed

directory you just created:

● dom3-xercesImpl-2.4.0.jar ● dom3-xml-apis-2.4.0.jar ● xalan-2.4.1.jar

Copying LiveCycle JAR files

You need to copy one or more LiveCycle JAR files from the LiveCycle installation directories to the WebLogic directories.

Repeat this procedure for each machine to be added to the cluster.

➤ To copy LiveCycle JAR files:

1. In the [appserverdomain] directory, create a directory called lib. 2. Copy the DocumentServicesLibrary.jar file from the

[LiveCycle root]/components/csa/weblogic/lib/adobe directory to the [appserverdomain]/lib directory.

Increasing the WebLogic Server thread count

Before deploying LiveCycle products to WebLogic Server, you must increase the server thread count. The default value of 25 is insufficient for running your applications.

Repeat this procedure for each Managed Server instance (each server to be added to the cluster).

➤ To increase the WebLogic Server thread count:

1. Start WebLogic Server Administration Console by typing http://[host name]:[port]/console in the URL line of a web browser.

2. Type the user name and password that you created for the WebLogic domain, and then click Sign In. 3. Select Servers, right-click the Managed Server name, and select View Execute Queues.

4. Click weblogic.kernel.Default.

5. In the Thread Count box, type 40 and click Apply.

6. Restart the Managed Server instance by selecting Domain > Control > Graceful Shutdown. Start the server by selecting Domain > Control, and then click Start/Stop.

(20)

Adobe LiveCycle Installing the Application Servers Configuring LiveCycle Application Server Clusters Using WebLogic Copying and editing files 20

Copying and editing files

This section applies to LiveCycle Policy Server only.

To complete the configuration, you will have to copy several files to the server and modify your startup scripts.

➤ To copy and edit files:

1. Create a directory named lib in the [appserverdomain] directory.

2. Copy the appropriate database jar files from the [LiveCycle root]/components/policyserver/common/ lib/thirdparty directory to the [appserverdomain]/lib directory:

● db2jcc.jar

● db2jcc_license_cu.jar ● mysql-connector-java.jar ● ojdbc14.jar

● nls_charset12.jar

3. Copy the endorsed directory from the [LiveCycle root]/PolicyServer/sdk/lib/Weblogic directory to the

[appserverdomain]/lib directory. Ensure that the following files have been copied:

● dom3-xercesImpl-2.4.0.jar ● dom3-xml-apis-2.4.0.jar

● xalan-2.4.1.jar

Note: Only perform this step if LiveCycle Policy Server is the only product being installed; otherwise

these files were copied to an endorsed directory previously.

4. Copy the edc-server-spi.jar file from the [LiveCycle root]/PolicyServer/sdk/spi-lib directory to the

[appserverdomain]/lib directory.

5. Copy the jax-qname.jar file from the [LiveCycle root]/PolicyServer/sdk/lib/Weblogic directory to the

6. Copy the jaas.config file from the [LiveCycle root]/PolicyServer/weblogic-conf/jaas/ directory to the

7. In a text editor, edit the jaas.config file by configuring the user.provider.url, userDNPrefix, and userDNSuffix entries, and then save the file. For example, edit jaas.config:

UsernamePwd_Auth { com.adobe.edc.server.provider.authentication.login.LDAPLoginModule required debug="true" java.naming.factory.initial="com.sun.jndi.ldap.LdapCtxFactory" user.provider.url="ldap://dirsj.corp.adobe.com:389" java.naming.security.authentication="simple" userDNPrefix="uid=" userDNSuffix=",ou=people,o=adobe.com"; };

(21)

Adobe LiveCycle Installing the Application Servers Configuring LiveCycle Application Server Clusters Using WebLogic Copying and editing files 21

8. Copy the following file from the [LiveCycle root]\policyserver\ weblogic-conf\scripts\ directory to the

[appserverdomain] directory:

● (Windows) startWebLogic.cmd and startManagedWebLogic.cmd ● (Linux and UNIX) startWebLogic.sh and startManagedWebLogic.sh

9. Edit the startWebLogic command:

● (Windows Administration Server) [appserverdomain]\startWebLogic.cmd ● (Windows Managed Server) [appserverdomain]\startManagedWebLogic.cmd

● (Linux and UNIX Administration Server) [appserverdomain]/startWebLogic.sh

● (Linux and UNIX Managed Server) [appserverdomain]/startManagedWebLogic.sh

10. Ensure that the following properties are configured:

set EDC_DOMAIN_DIR=%BEA_HOME%\user_projects\domains\mydomain set SERVER_NAME=myserver

11. Ensure that JAVA_HOME points to BEA_JDK (version 1.4.2_08) and that the bin directory for JAVA_HOME is included in the path.

12. Ensure that edc-server-spi.jar, jax-qname.jar, and the database drivers are in the classpath. 13. Add the following in Java arguments:

(Only LiveCycle Policy Server)

-Djava.endorsed.dirs=%WL_DOMAIN_DIR%/lib/endorsed

-Djava.security.auth.login.config=”%WL_DOMAIN_DIR%/lib/jaas.config” (LiveCycle Policy Server deployed with other LiveCycle products)

-Djava.security.auth.login.config=”%WL_DOMAIN_DIR%/lib/jaas.config” 14. Save your changes to the file.

15. Edit the startup scripts for all the nodes.

16. Restart the Managed Server instance by selecting Domain > Control > Graceful Shutdown. Then start the server by selecting Domain > Control, and click Start/Stop.

(22)

22

3

Configuring the Database

Before installing any LiveCycle product to the cluster, the database must be configured. You must have a database server installed and a database created. For more information on creating and installing databases for LiveCycle products, see the installation and configuration guide for the LiveCycle product you are clustering.

Creating the database

This section describes how to set up the database that stores LiveCycle configuration information and run-time data. If deploying LiveCycle Forms (without User Management), LiveCycle Reader Extensions, or LiveCycle Document Security, you do not need to complete this section.

If this is the first installation of a LiveCycle product, you must create an empty database. All of the tables required to support LiveCycle products will be created by Configuration Manager when you initialize the database.

Before creating the database, you must ensure that you have read the pre-installation requirements and have the required software installed.

Creating an Oracle database

If you prefer not to use the default database that was created when you installed Oracle 9i or 10g, create a new database using the Database Configuration Assistant tool. You must create a database that uses the UTF-8 character set if the LiveCycle user records database authenticates against an LDAP directory that uses UTF-8 characters.

You must also create a new user on the database. For deployments on Linux and UNIX, the user name must not exceed 8 characters and, on Windows, it must not exceed 12 characters. This user name and password will be used again when you create the data source.

For both Oracle 9i and Oracle 10g, the user account must be assigned both the CONNECT and RESOURCE roles. For Oracle 9i, the user account must be granted CREATE VIEW system privileges. For Oracle 10g, the user account must be granted the CREATE SESSION, CREATE SYNONYM, and CREATE VIEW system

privileges.

Optionally, for both Oracle 9i and 10g, UNLIMITED TABLESPACE can be granted. However, an initial 500 MB table space size can be allocated instead, with the option that this size will grow over time and should be monitored using administration utilities inside of Oracle, such as alarms. For information about using Oracle9i or 10g, see the Oracle 9i or 10g user documentation.

Creating a SQL Server database

You can create a SQL Server database that LiveCycle products use to store run-time and configuration data. For information on creating a SQL Server database, refer to the SQL Server documentation. LiveCycle products support SQL Server 2000 using SP3a or SP4.

(23)

Adobe LiveCycle Configuring the Database Configuring LiveCycle Application Server Clusters Using WebLogic Creating a SQL Server database 23

Create a SQL Server database and create a user with DB_OWNER privileges that can be used when configuring the data source on the application server. For information about creating the database and user, see the SQL Server documentation.

The SQL Server database can be configured with the Windows or SQL Server authentication types. If the WebLogic host computer belongs to a Windows workgroup, the SQL Server host computer must belong to a workgroup and not a domain.

You must also install JTA stored procedures on SQL Server. (See “Installing JTA stored procedures” on page 23.) If SQL Server runs on Windows 2003, you need to enable XA transactions at the operating system level. (See “Enabling XA transactions for Windows Server 2003” on page 24.)

Installing JTA stored procedures

LiveCycle products deployed on WebLogic use a database driver to connect to the SQL Server database. This driver requires stored procedures for JTA on the SQL Server computer. You need to obtain and install updated SQL Server install files for JTA stored procedures.

➤ To install JTA stored procedures:

1. Obtain and install SQL Server 2000 Driver for JDBC SP3 from the

http://www.microsoft.com/technet/prodtechnol/sql/2000/downloads/default.mspx website.

2. Copy the sqljdbc.dll file from the Microsoft SQL Server 2000 Driver for JDBC\SQLServer JTA directory to the [install directory]\Microsoft SQL Server\MSSQL\Binn directory, where [install directory] is the location where SQL Server is installed.

3. Log in to SQL Server 2000 Query Analyzer using a user account that is a member of the sysadmin group. The default member is sa.

4. In the menu of available databases, ensure that master is selected.

Note: Changes made to the Master database are global and affect all databases in the instance.

5. Open the instjdbc.sql file from the Microsoft SQL Server 2000 Driver for JDBC\SQLServer JTA directory, and then execute it.

If you are running this query for the first time, you will see several messages that indicate “xp_xxx” cannot be dropped. These messages are warnings and do not indicate that the installation failed. The last message should read “instxa.sql completed successfully”.

The instjdbc.sql script generates many messages. In general, these messages can be ignored; however, the system administrator should scan the output for any messages that may indicate an execution error. The last message should indicate that instjdbc.sql ran successfully. The script fails when there is insufficient space available in the master database to store the JDBC XA procedures or to log changes to existing procedures.

6. Ensure that MS DTC is started for SQL Server 2000:

● Start SQL Server Service Manager.

● In the Services list, select Distributed Transaction Coordinator. ● Click Start/Continue.

● If you want MS DTC to start automatically when the computer starts, select Auto-start service

(24)

Adobe LiveCycle Configuring the Database Configuring LiveCycle Application Server Clusters Using WebLogic Installing database drivers 24

Enabling XA transactions for Windows Server 2003

If you are running SQL Server 2000 on the Windows Server 2003 Enterprise Edition operating system, XA transactions must be enabled at the operating system level. Before you perform the tasks in this section, you must verify that XA transactions are already enabled for Windows Server 2003.

To enable XA transactions on the operating system, you need to perform the following tasks:

● Enable XA transactions for the MS DTC.

● Create a registry entry for the sqljdbc.dll database drivers file that you are using.

➤ To enable XA transactions for MS DTC:

1. Select Start > Programs > Administrative Tools > Component Services. 2. Select Component Services > Computers.

3. Right-click the computer name that you want to support for XA transactions and click Properties. 4. Click the MSDTC tab and click Security Configuration.

5. Under Security Settings, select Enable XA Transactions.

➤ To create registry entries for the driver file:

1. Use a registry editor (such as regedit) to navigate to the registry key named HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL.

2. Create a new String Value registry named value that has the following properties:

● Name: sqljdbc.dll

● Type: String (REG_SZ)

● Value: The full path name (including the file name) of the DLL file:

[install directory]\Microsoft SQL Server\MSSQL\Binn\sqljdbc.dll 3. Restart the computer so that the changes to the registry take effect.

Installing database drivers

You must now install your database drivers. The server referred to in this section is the Managed Server.

➤ To install the Oracle driver:

1. From a browser, navigate to

http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc_10201.html 2. Under Oracle Database 10g Release 2 (10.2.0.1.0) JDBC Drivers, download the ojdbc14.jar file. 3. Under the [WebLogic root]/server/ directory, create a new directory called db_drivers.

(25)

Adobe LiveCycle Configuring the Database Configuring LiveCycle Application Server Clusters Using WebLogic Installing database drivers 25

5. Start the WebLogic Server Administration Console by typing: http://[host name]:[port]/console

in the URL line of a web browser.

7. In the navigation tree, select [domain name], click Servers, and then click the server you created.

8. Click the Remote Start tab on the Configuration tab. 9. Add the following text to the Class Path box:

● (Windows) %WL_HOME%\server\db_drivers\ojdbc14.jar; ● (Linux and UNIX) ${WL_HOME}/server/db_drivers/ojdbc14.jar:

Note: Use the “;” separator (Windows) or the “:” separator (Linux and UNIX).

10. Save your changes.

➤ To install the SQL Server driver:

4. Click the Remote Start tab on the Configuration tab. 5. Add the following text to the Class Path box:

● (Windows)

%WL_HOME%\server\lib\wlbase.jar;%WL_HOME%\server\lib\wlsqlserver.jar; %WL_HOME%\server\lib\wlutil.jar;

● (Linux and UNIX)

${WL_HOME}/server/lib/wlbase.jar:${WL_HOME}/server/lib/wlsqlserver.jar :${WL_HOME}/server/lib/wlutil.jar:

(26)

Adobe LiveCycle Configuring the Database Configuring LiveCycle Application Server Clusters Using WebLogic Registering required JAR files and turning on Remote Start 26

Registering required JAR files and turning on Remote Start

You must configure WebLogic to use the JAR files that you copied to the WebLogic computer. The server referred to in this section is the Managed Server.

➤ To modify the startManagedWebLogic command:

4. Click the Remote Start tab on the Configuration tab.

5. In the Java Home box, type the path to the jdk142_08 directory. For example, type C:\bea815\jdk142_08.

6. In the BEA Home box, type the path to the WebLogic installation directory. For example, type C:\bea815. 7. In the Class Path box, type the paths to the DocumentServicesLibrary.jar file and the database drivers.

For example:

[appserverdomain]/lib/DocumentServicesLibrary.jar;

[appserver root]<database driver>;

[BEA_HOME]/jdk142_08/lib/tools.jar; (LiveCycle Policy Server only)

[appserverdomain]/lib/edc-server-spi.jar

[appserverdomain]/lib/jax-qname.jar

The [appserver root]<database drivers> refers to the database drivers you previously added to the class path in “Installing database drivers” on page 24.

8. In the Arguments box, type the following text:

-Dweblogic.Name=[servername] -Dweblogic.ProductionModeEnabled=true -Djava.endorsed.dirs=[BEA HOME]/jdk142_08/jre/lib/endorsed

-Dadobeidp.RootDirectory=[BEA HOME]/user_projects/domains/[yourDomain]

-Djava.security.policy=[BEA HOME]/weblogic81/server/lib/weblogic.policy (LiveCycle Form Manager) Add the following text in the argument:

-Dcom.adobe.fm.lucene.enabled=false

(Solaris, LiveCycle Form Manager) Also add the following argument: -XX:NewRatio=8.

(LiveCycle Policy Server) Add the following arguments:

-Djava.security.auth.login.config={WL_Domain}/lib/jaas.config

Caution: These commands must all be on one line with one space between them and no other

separators. If you are copying and pasting text directly from this document, remove any hard returns or extraneous text that may get copied along with the required code.

(27)

Adobe LiveCycle Configuring the Database Configuring LiveCycle Application Server Clusters Using WebLogic Registering required JAR files and turning on Remote Start 27

9. In the User Name box, type the WebLogic user name.

10. In the Password and Confirm Password boxes, type the WebLogic user password. 11. Click Apply.

Note: Ensure that the yellow /!\ icon flashes after you click Apply. This flash indicates that the changes

have been applied. If the icon does not flash, click Apply again.

12. Restart the Managed Server instance by selecting Domain > Control > Graceful Shutdown.Start the server by selecting Domain > Control, and clicking Start/Stop.

(28)

28

4

Setting Up WebLogic Clusters

To deploy the cluster in this chapter, use the WebLogic configuration wizard to create the domain, servers, and cluster. WebLogic Server supports and provides capabilities to create a cluster on a single computer as well as remote, networked computers.

For more information on any topic, see the WebLogic online documentation at http://e-docs.bea.com/wls/docs81.

Creating the WebLogic cluster

To set up a WebLogic cluster you will need to perform the following tasks:

● Install Weblogic on all nodes that are to be part of the cluster. ● On one of the nodes, create a cluster domain.

● Create a Managed Server on all machines that will host Managed Servers. ● In the WebLogic Server Administrative Console, define the cluster.

➤ To create the WebLogic cluster:

1. Start the configuration wizard on the system that will be running the Administration Server. For example:

● (Windows) Select Start > Programs > BEA WebLogic Platform 8.1 > Configuration Wizard. ● (UNIX) Open a console, navigate to BEA_HOME/weblogic81/common/bin and run config.sh.

2. Click Create a new WebLogic configuration.

3. Select Basic WebLogic Server Domain template, click Next, and then select Custom configuration. 4. In the Name box, type an alphanumeric name that will appear in the Administration Console, such as AdminServer. Each server within a domain must have a unique name. You use this name to identify the server when using the Administration Console or APIs.

5. In the Listen Address box, specify the IP address of the Administration Server.

6. In the Listen Port box, type a numeric value for the listen port. The default port is 7001, and the range is between 1 and 65535.

7. Select SSL Enabled to enable Secure Socket Layer. By default, the server instance uses demonstration certificates for SSL communication. In a production environment, you must configure the server to use certificates from a certificate authority.

8. In the SSL Listen Port box, enter a numeric value for the SSL listen port. The range is between 1 and 65535.

9. On the Managed Servers, Clusters, and Machines Options screen, select Yes.

(29)

Adobe LiveCycle Setting Up WebLogic Clusters Configuring LiveCycle Application Server Clusters Using WebLogic Creating the WebLogic cluster 29

11. In the Name box, type an alphanumeric name. Each server within a domain must have a unique name. 12. In the Listen Address box, specify the IP address of the Managed Server.

13. In the Listen Port box, type a numeric value for the listen port. While the default port is 7001, you must select a different port than was entered in step 6, such as 8001. The range is between 1 and 65535. 14. Select SSL Enabled to enable Secure Socket Layer. By default, the server instance uses demonstration

certificates for SSL communication. In a production environment, you must configure the server to use certificates from a certificate authority.

15. In the SSL Listen Port box, enter a numeric value for SSL listen port. The range is between 1 and 65535.

Note: If you plan to add more Managed Servers on the same computer, define a new port number.

16. Repeat steps 10 to 15 for each Managed Server, even if the other server is created on another machine. 17. On the Configure Clusters page, click Add.

18. In the Cluster Name box, type an alphanumeric name. Each cluster within a domain must have a unique name.

19. In the MultiCast Address box, enter a multicast address for the cluster. A multicast address is an IP address in the range from 224.0.0.0 to 239.255.255.255. For example, type 237.0.0.101.

20. In the MultiCast Port box, enter a numeric value for the multicast port. While the default port is 7001, you must select a different port than was entered in step 6, such as 8050. The range is between 1 and 65535.

21. (Optional) In the Cluster Address box, enter the cluster address. The cluster address forms the host name portion of URLs for requests directed to the cluster. If the cluster address is not set, EJB handles may not work properly.

For production use, enter a DNS name that maps to the individual IP addresses of the Managed Servers in the cluster.

For testing or development purposes, use a comma-separated list of the IP addresses and ports assigned to the Managed Servers (this is the default entry). For example,

IPaddress1:port1,IPaddress2:port2,IPaddress3:port3

22. On the Assign Servers to Clusters screen, select all servers in the server list, then click the move arrow button to move the servers to the cluster list, and then click Next.

23. In the Configure Machines screen, add the entries for the Managed Servers you created in step 11.

Note: When creating the cluster on a UNIX machine, click the Unix Machine tab and then add the

entries for the Managed Servers that you created in step 11.

24. For each Managed Server, click Add, and then, in the Name box, type the host name (or IP address) of the Managed Server, and in the Node Manager Listen Address box, type the IP address of the Managed Server. Keep the default listening port as 5555.

25. (Optional) If you plan to use Node Manager on the computer, in the Node Manager Listen Address

(30)

Adobe LiveCycle Setting Up WebLogic Clusters Configuring LiveCycle Application Server Clusters Using WebLogic Creating the WebLogic cluster 30

26. (Optional) If you plan to use Node Manager on the computer, in the Node Manager Listen Port box, enter the port on which Node Manager listens for requests. The default listening port for Node Manager is 5555.

The Administration Server uses the listen address and listen port to connect to Node Manager running on the remote computer. The Administration Server can then ask Node Manager to start a server instance on the computer. For servers that are in a cluster, WebLogic Server uses the machines that you configure to determine the optimum server to which certain tasks, such as HTTP session replication, are delegated.

27. Repeat steps 25 to 26 for each WebLogic host that will run servers in the domain.

28. On the Assign Servers to Machines page, in the Machine list, select a machine that you created. 29. In the Server list, select a server to run on the machine selected in step 28. A server can be an

Administration Server or a Managed Server.

30. Click the right arrow to assign the server to the machine.

31. Repeat steps 26 to 30 for each WebLogic Server running on a machine.

32. Skip subsequent pages (JDBC Options and JMS Options) until the wizard displays the Configure Administrative Username and Password page.

33. On the Configure Administrative Username and Password page, enter a user name and password. This user becomes the initial administrative user for the domain. Under Configure Additional Users, Groups, And Global Roles, select No and then click Next.

34. (Windows) The Configuration Wizard prompts you to create an item on the Windows Start menu. If you want the wizard to lead you through the process of configuring a shortcut for the servers in your domain, click Yes.

35. (Windows) The Configuration Wizard prompts you to install the Administration Server as a Windows service. If you want the Administration Server to start automatically when you boot the Windows computer, click Yes.

36. In the Weblogic Startup Mode, select Production Mode. 37. Select Sun JDK, and then browse to JDK install directory.

38. On the Create WebLogic Configuration page, click Create. By default, the wizard creates a domain with the following characteristics:

● The domain is named mydomain.

● The domain's Administration Server is named myserver. ● The root directory for the Administration Server is located in

WL_HOME\user_projects\domains\mydomain. 39. When the domain creation is complete, click Done.

(31)

Adobe LiveCycle Setting Up WebLogic Clusters Configuring LiveCycle Application Server Clusters Using WebLogic Starting the cluster 31

40. To start the Administration Server in this domain, from a command prompt, navigate to

WL_HOME\user_projects\domains\mydomain and run the script appropriate to your operating system:

To access the Administration Console for the domain, use any of the following URLs:

● From the same computer on which the Administration Server is running:

http://localhost:7001/console

● From any computer:

http://DNS-name:7001/console

where DNS-name is the DNS name of the computer on which the Administration Server is running.

● From any computer:

http://IP-Address:7001/console

where IP-Address is an IP address of the computer on which the Administration Server is running.

Starting the cluster

Starting the cluster requires configuring and starting Node Manager, Administration Server, and all Managed Servers.

Starting the Administration Server

➤ To start the Administration Server:

1. Open a command prompt on the server.

2. Navigate to the BEA_HOME\user_projects\domains\mydomain directory. 3. Run the script appropriate to your operating system:

Configuring Node Manager

Node Manager is a stand-alone Java program provided with WebLogic Server and is useful for starting a Managed Server that resides on a computer different from its Administration Server. Node Manager also provides features that help increase the availability of Managed Servers in your cluster.

You must perform the following procedure on each machine running Node Manager.

➤ To configure and start Node Manager:

1. Generate certificates to configure Node Manager. Node Manager uses SSL to communicate with the Administration Server.

(32)

Adobe LiveCycle Setting Up WebLogic Clusters Configuring LiveCycle Application Server Clusters Using WebLogic Configuring Node Manager 32

2. From a command prompt, navigate to the BEA_HOME\weblogic81\server\bin directory and run the script appropriate to your operating system:

● (Windows) startNodeManager.cmd ● (Linux, UNIX) startNodeManager.sh

Running this command creates several files under the

BEA_HOME\weblogic81\common\NodeManager directory.

3. Navigate to the BEA_HOME\weblogic81\common\NodeManager directory and open the nodemanager.properties file in a text editor. Add the following lines:

ReverseDnsEnabled=true

KeyStores = DemoIdentityAndDemoTrust ListenAddress=<servername>

ListenPort=<port>

ReverseDnsEnabled: Specifies whether entries in the trusted hosts file can contain DNS names (instead of IP addresses).

Keystores: Specifies the use of the demonstration Identity and Trust keystores located in the

BEA_HOME\server\lib directory that are configured by default. The demonstration Trust keystore trusts all of the certificate authorities in the Java Standard Trust keystore

(JAVA_HOME\jre\lib\security\cacerts).

ListenAddress: Specifies the IP address on which the machine running Node Manager can listen for connection requests. This argument deprecates the weblogic.nodemanager.listen address.

ListenPort: Specifies the TCP port number on which Node Manager listens for connection requests. This argument deprecates weblogic.nodemanager.listenPort. The default port number is 5555.

4. Open the nodemanager.hosts file in a text editor and add the DNS names of the Managed Servers you created for the cluster as follows:

Server1 Server2

Node Manager accepts commands from Administration Servers running on the same machine and on trusted hosts. Trusted hosts are identified by IP address or DNS name in the nodemanager.hosts file, which is created the first time you start Node Manager in the directory where you run it.

Note: Each time you start Node Manager, it looks for the nodemanager.hosts file in the current

directory, and creates the file if it does not exist in that directory.

By default, the nodemanager.hosts file is empty. To add trusted hosts, edit the file with a text editor, and add one line for each Managed Server’s host name. If you want Node Manager to accept

commands from any host, put an asterisk in the hosts file. If you identify a trusted host by its DNS name, you must enable reverse DNS lookup when starting Node Manager. By default, reverse DNS lookup is disabled.

Note: You do not have to restart Node Manager after changing the nodemanager.hosts file.

If the computer name does not work, change it to the IP addresses.

When performing steps 1 to 4 on other computers (for example, Server2), use ListenAddress=Server2 (the computer name itself ).

(33)

Adobe LiveCycle Setting Up WebLogic Clusters Configuring LiveCycle Application Server Clusters Using WebLogic Starting Node Manager 33

Starting Node Manager

These sections describe methods of starting Node Manager, required environment variables, and command line arguments.

Starting Node Manager as a service

The WebLogic Server installation process automatically installs Node Manager as a service, so that it starts up automatically when the system boots. By default, Node Manager will listen on localhost. If you want Node Manager to accept commands from remote systems, you must uninstall the default Node Manager service, and then reinstall it to listen on a non-localhost Listen Address.

Starting Node Manager with a script

Although running Node Manager as an operating system service is recommended, you can also start Node Manager manually from a command prompt using a script. The environment variables Node Manager requires are described in Node Manager Environment Variables. Command line options are described in Node Manager Properties. Sample start scripts for Node Manager are installed in the WL_HOME\server\bin directory, where WL_HOME is the top-level installation directory for WebLogic Server.

Use startNodeManager.cmd on Windows systems and startNodeManager.sh on UNIX systems. The scripts set the required environment variables and start Node Manager in

WL_HOME/common/nodemanager. Node Manager uses this directory as a working directory for output and log files. To specify a different working directory, edit the start script with a text editor and set the value of the NODEMGR_HOME variable to the required directory.

Edit the sample start script to make sure that the command qualifiers set the correct listen address and port number for your Node Manager process.

Command syntax for starting Node Manager

In WebLogic Server 8.1, you can enter Node Manager properties on the command line or define them in the nodemanager.properties file, which is installed in the directory where you start Node Manager. Values supplied on the command line override the values in nodemanager.properties.

This is the syntax for starting Node Manager:

java [java_property=value...] -D[nodemanager_property=value] -D[server_property=value] weblogic.NodeManager

Note:WebLogic Server 8.1 provides a new wrapper to weblogic.nodeManager.NodeManager. The new

wrapper is weblogic.NodeManager.

In the command line, a java_property indicates a direct argument to the java executable, such as -Xms or -Xmx. If you did not set the CLASSPATH environment variable, use the -classpath option to identify required Node Manager classes.

Node Manager communicates with Administration Servers and Managed Servers using two-way SSL. When you start Node Manager, you must supply startup arguments that identify security components related to SSL communication.

Note:If you run Node Manager on a UNIX operating system other than Solaris or HP UX, you cannot have

any white space characters in any of the parameters that will be passed to the Java command line when starting Node Manager.

(34)

Adobe LiveCycle Setting Up WebLogic Clusters Configuring LiveCycle Application Server Clusters Using WebLogic Starting Managed Servers 34

Starting Managed Servers

To run Managed Servers from a command prompt, n