BMC Atrium Orchestra Tor 7.6.00 Installation Guide

BMC Atrium Orchestrator7.6.00Installation Manual

December 2009

www.bmc.com

Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com. From this website, you can obtaininformation about the company, its products, corporate offices, special events, and career opportunities.

United States and Canada

Address BMC SOFTWARE INC2101 CITYWEST BLVDHOUSTON TX 77042-2827 USA

Telephone 1 713 918 8800or1 800 841 2031

Fax 1 713 918 8000

Outside United States and Canada

Telephone +01 713 918 8800 Fax +01 713 918 8000

© Copyright 2005- 2009 BMC Software, Inc.BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., areregistered with the U.S. Patent and Trademark Office, and may be registered or pending registration inother countries. All other BMC trademarks, service marks, and logos may be registered or pendingregistration in the U.S. or in other countries. All other trademarks or registered trademarks are theproperty of their respective owners.

Notes is a trademark or registered trademark of International Business Machines Corporation in theUnited States, other countries, or both.

Linux is the registered trademark of Linus Torvalds.

JDK, JMX, JSP, Java, Solaris, and Sun are trademarks or registered trademarks of Sun Microsystems, Inc., inthe U.S. and other countries.

The information included in this documentation is the proprietary and confidential information of BMCSoftware, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditionsof the applicable End User License agreement for the product and to the proprietary and restricted rightsnotices included in the product documentation.

Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED—RIGHTS RESERVEDUNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any dataand computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FARSection 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC SOFTWARE INC, 2101CITYWEST BLVD, HOUSTON TX 77042-2827, USA. Any contract notices should be sent to this address.

http://www.bmc.com

Customer support

Support website

You can obtain technical support from BMC 24 hours a day, 7 days a week at http://www.bmc.com/support. From thiswebsite, you can

■ read overviews about support services and programs that BMC offers

■ find the most current information about BMC products

■ search a database for problems similar to yours and possible solutions

■ order or download product documentation

■ download products and maintenance

■ report a problem or ask a question

■ subscribe to receive proactive e-mail alerts

■ find worldwide BMC support center locations and contact information, including e-mail addresses, fax numbers, andtelephone numbers

Support by telephone or e-mail

In the United States and Canada, if you need technical support and do not have access to the web, call 800 537 1813 orsend an e-mail message to [email protected]. (In the subject line, enter SupID:yourSupportContractID, suchas SupID:12345). Outside the United States and Canada, contact your local support center for assistance.

Before contacting BMC

Have the following information available so that Customer Support can begin working on your issue immediately:

■ product information

― product name― product version (release number)― license number and password (trial or permanent)

■ operating system and environment information

― machine type― operating system type, version, and service pack or other maintenance level such as PUT or PTF― system hardware configuration― serial numbers― related software (database, application, and communication) including type, version, and service pack or

maintenance level

■ sequence of events leading to the problem

■ commands and options that you used

■ messages received (and the time and date that you received them)

― product error messages― messages from the operating system, such as file system full― messages from related software

3

http://www.bmc.com/support

mailto:[email protected]

License key and password information

If you have questions about your license key or password, contact BMC as appropriate for your location:

■ (USA or Canada) Contact the Order Services Password Team at 1 800 841 2031, or send an e-mail message [email protected].

■ (Europe, the Middle East, and Africa) Fax your questions to EMEA Contracts Administration at +31 20 354 8702, or sendan e-mail message to [email protected].

■ (Asia-Pacific) Contact your BMC sales representative or your local BMC office.

4 BMC Atrium Orchestrator 7.6.00 Installation Manual



ContentsConventions ............................................................................................................7Syntax statements ...................................................................................................9

Chapter 1 BMC Atrium Orchestrator solution overview 11

Chapter 2 System Requirements 17Ports requirements ..........................................................................................................22Time synchronization .....................................................................................................22

Chapter 3 Platform installation 23Typical installation .........................................................................................................23

Chapter 4 GUI Installation procedures 25Installing BMC Atrium Orchestrator Access Manager and the repository ............25

Verifying the BMC Atrium Orchestrator Access Manager installation . . .27

Installing BMC Atrium Orchestrator Access Manager only ....................................28Verifying the BMC Atrium Orchestrator Access Manager installation . . .30

Installing the repository only ........................................................................................32Verifying the repository installation .................................................................33

Installing a configuration distribution peer ................................................................34Installing a CDP with BMC Atrium Orchestrator Operator Control Panel and agraphing server ...............................................................................................................37

Verifying the configuration distribution peer installation ............................40Verifying the BMC Atrium Orchestrator Operator Control Panelinstallation .............................................................................................................41Verifying the graphing server installation .......................................................42

Installing an AP ...............................................................................................................43Installing a LAP ..............................................................................................................46Installing a HACDP .......................................................................................................48Verifying a peer installation ..........................................................................................50Installing the BMC Atrium Orchestrator Operator Control Panel ..........................51

Verifying the BMC Atrium Orchestrator Operator Control Panelinstallation .............................................................................................................54

Installing the graphing server .......................................................................................55Verifying the graphing server installation .......................................................57

Contents 5

New BMC Atrium Orchestrator Development Studio installation worksheet ..................................................................................................................................................58Installing BMC Atrium Orchestrator Development Studio .....................................59Installing content with the GUI installer .....................................................................60

Chapter 5 Silent installation properties 63Sample options files ........................................................................................................69Creating an options file ..................................................................................................82Executing a silent installation .......................................................................................84Silent installation upgrade .............................................................................................85

Using the silent installer to upgrade ................................................................87Silent installation verification .......................................................................................88

Chapter 6 BMC Atrium Orchestrator GUI installer upgrade 91Upgrade worksheets ......................................................................................................92Upgrading the platform .................................................................................................95Upgrading an activity peer ...........................................................................................97Upgrading a lightweight activity peer .....................................................................100Upgrading a high availability configuration distribution peer .............................101Upgrading BMC Atrium Orchestrator Development Studio .................................105Updating BMC Atrium Orchestrator content ...........................................................106

Chapter 7 Troubleshooting and log files 109Installation log files ......................................................................................................111Troubleshooting with the grid.log .............................................................................113Tomcat logs ....................................................................................................................114Logging configuration files .........................................................................................116Troubleshooting tips for starting the server .............................................................116

Appendix A Appendix 119Platform silent installation options file ......................................................................119


Conventions

This document uses the following special conventions:

■ All syntax, operating system terms, and literal examples arepresented in this typeface.

■ Variable text in path names, system messages, or syntax is displayed in italic text:testsys/instance/fileName

■ This document uses a symbol to show menu sequences. For example, Actions => Create Test instructs you to choose the Create Test command from the Actionsmenu.

Chapter 1 Conventions 7


Syntax statements

This topic explains conventions for showing syntax statements.

A sample statement follows:

COMMAND KEYWORD1 [KEYWORD2 | KEYWORD3] KEYWORD4={YES | NO} fileName…

Convention Example

Items in italic type represent variables that youmust replace with a name or value. If a variableis represented by two or more words, initialcapitals distinguish the second and subsequentwords.

alias

databaseDirectory

serverHostName

Brackets indicate a group of optional items. Donot type the brackets when you enter theoption. A comma means that you can chooseone or more of the listed options. You must usea comma to separate the options if you choosemore than one option.

[tableName, columnName, field]

[-full, -incremental, -level] (UNIX)

Braces indicate that at least one of the encloseditems is required. Do not type the braces whenyou enter the item.

{DBDName | tableName}

UNLOAD device={disk | tape, fileName |deviceName}

{-a | -c} (UNIX)

A vertical bar means that you can choose onlyone of the listed items. In the example, youwould choose either commit or cancel.

{commit | cancel}

{-commit | -cancel} (UNIX)

An ellipsis indicates that you can repeat theprevious item or items as many times asnecessary.

columnName…

Chapter 1 Syntax statements 9


BMC Atrium Orchestrator solutionoverview

BMC Atrium Orchestrator empowers operators with process-based control. Bydelivering workflow-based process templates, BMC Atrium Orchestrator helps yourapidly adapt and deploy functional design, ensuring consistent and appropriate,policy-based response across the enterprise. BMC Atrium Orchestrator provides aworkflow design modeling studio to easily and efficiently build, test, and maintainoperational activities that are customized to specific IT environments.

BMC Atrium Orchestrator provides the following features:

■ Information Technology Infrastructure Library (ITIL)-based business processdesign and development, using the graphical BMC Atrium OrchestratorDevelopment Studio

■ Technology-agnostic, seamless, standards-based integration with all of yourexisting IT system investments

■ Automation of operations activities, using your business processes

■ A highly available, highly scalable, operations-activity automation environmentusing grid technology

BMC Atrium Orchestrator architecture

The BMC Atrium Orchestrator system is a load-balancing, high-availabilitycomputer cluster architecture in which available servers or peers process requests. It

1


is referred to as a grid architecture, which you should not confuse with truecomputer or data grids. The following graphic illustrates the architecture.

Figure 1: Architecture diagram

Typically, clusters employ homogeneous nodes; however, BMC Atrium Orchestratoruses a heterogeneous set of nodes, or peer types. Each peer type has a specificpurpose and hosts a particular set of applications and services. The followingdescriptions of the peer types and components, and the distinctions between them,can help you plan and deploy them into your environment.

BMC Atrium Orchestrator Access Manager

BMC Atrium Orchestrator Access Manager is the security component of BMCAtrium Orchestrator. BMC Atrium Orchestrator Access Manager is an identitymanager that provides single sign-on services as well as authorization policyadministration and enforcement. It also provides an interface to manageconfigurations with external LDAP directories.

Repository

The repository stores BMC Atrium Orchestrator content such as adapters andmodules. Content stored in the repository is accessed by multiple developersthrough either BMC Atrium Orchestrator Grid Manager or BMC AtriumOrchestrator Development Studio. You can set the version number on content andthe repository maintains the revision numbers. The repository uses BMC AtriumOrchestrator Access Manager to set content read and write privileges, so the accessmanager must be installed in order to use the repository.


BMC Atrium Orchestrator Grid Manager

The BMC Atrium Orchestrator Grid Manager component resides on the CDP andprovides a user interface to add and maintain grids, peers, adapters, and processschedules. It also helps you to manage module deployment and activation.

You can configure multiple databases in BMC Atrium Orchestrator Grid Manager tostore audit records, grid metrics, process metrics, and business metrics. The databaseconfiguration requires an initialized instance of a database, designated for records ormetrics collection. Audit records, process metrics, grid metrics, and business metricscan be collected in a single database or in two databases.

BMC Atrium Orchestrator Development Studio

BMC Atrium Orchestrator Development Studio is the integrated developmentenvironment in which you design, develop, and test workflows. You set rules,schedules, and configuration of workflows in BMC Atrium OrchestratorDevelopment Studio. It is a stand-alone application that is installed on a MicrosoftWindows or Apple Macintosh computer. You can configure it to communicate withthe grid. BMC Atrium Orchestrator Development Studio uses the grid repository toaccess and store content.

communicate with the grid.

BMC Atrium Orchestrator Development Studio uses the grid repository to access and

store content.

You can use Source Code Management (SCM) systems like SVN and CVS with

BMC Atrium Orchestrator Development Studio. In

BMC Atrium Orchestrator Development Studio you can check workflow into andout of the

SCM system.

You can use Source Code Management (SCM) systems like SVN and CVS with BMCAtrium Orchestrator Development Studio. In BMC Atrium OrchestratorDevelopment Studio, you can check workflow into and out of the SCM system.

BMC Atrium Orchestrator Operator Control Panel

BMC Atrium Orchestrator Operator Control Panel enables you to execute operatorprocesses in an automated or semi-automated mode.


Graphing server and graphing components

The graphing server and graphing components render graphical representations ofprocess metrics contained in the databases configured in BMC Atrium OrchestratorGrid Manager.

Configuration distribution peer

The configuration distribution peer (CDP) is the overall configuration manager forthe BMC Atrium Orchestrator grid. A CDP houses the BMC Atrium OrchestratorGrid Manager application and manages overall distribution of software componentsto the peers across one or multiple grids. The CDP provides the same types ofservices and capabilities of those as the activity peer (AP), and it provides a centralpoint of administrative control and content distribution for all distributedcomponents in a grid. The CDP is a required component, and typically, only oneCDP in each grid can service multiple APs. Configuration information is centralizedin the CDP. The CDP stores and distributes the configuration information andcontent for the grid.

Activity peer

The activity peer (AP) handles workflow processing load distribution. The APaccepts and executes workflows and hosts external application adapters, providingboth the core workflow engine and a web container. An activity peer joins a gridupon startup to communicate with the other peers.

Lightweight activity peer

The lightweight activity peer (LAP) is installed on a third-party systems server. It isuseful when a third-party system requires an adapter to execute locally or theadapter requires libraries in a third-party application whose libraries cannot beinstalled outside of that application. The LAP extends the grid communication to thethird-party system. Unlike the other peer types, the LAP executes no workflows.Graphing components cannot be installed on an LAP.

High-availability configuration distribution peer

When you deploy multiple CDPs, you create a high-availability environment. Thehigh-availability configuration distribution peer (HACDP) is effectively a mirroredinstance of a primary CDP. The HACDP is not idle and participates in workflowexecution, so it provides active high-availability capabilities for the grid in which it isoperating.


BMC Atrium Orchestrator components

You can install BMC Atrium Orchestrator in many configurations with or withoutoptional components. At a minimum, your BMC Atrium Orchestrator installationshould include:

■ BMC Atrium Orchestrator Access Manager

■ The repository

■ BMC Atrium Orchestrator Grid Manager

■ BMC Atrium Orchestrator Development Studio



System RequirementsReview the system requirements prior to installing BMC Atrium Orchestratorversion 7.6.00. This section contains system requirements for hardware, memory,and disk space. To ensure a successful installation and implementation install theproduct on the supported operating systems listed in the requirements section. Thissection gives the hardware requirements, processor, memory, and disk space, foreach product component. The Microsoft Windows and Red Hat Linux platforms aresupported on dedicated servers and virtual machines (VM) in the VMwareenvironment. When a component is running in a VM, you must allocate sufficientresources to it. It is important to note that BMC Atrium Orchestrator should be theonly application running on the computer where it is installed.

Default requirements

These requirements are defined to optimize performance when activating anddeactivating modules. System performance is affect by the size of the module beingactivated not the amount of modules in the environment. The table below defines thedefault requirements for a BMC Atrium Orchestrator configuration for a 32-bitsystem running small loads. The configuration consists of:

■ BMC Atrium Orchestrator Access Manager

■ CDP

■ AP

■ LAP

Note The Microsoft Windows and Red Hat Linux platforms are supported on dedicated servers andvirtual machines (VMs) in the VMware environment. When a component is running in a VM, youmust allocate sufficient resources to it.

2

Chapter 2 System Requirements 17

Applications Memory Operating system or Internetbrowser

Type, number, andspeed of processors

Runtime andlog diskspacerequirements

Installation diskspacerequirements

BMC AtriumOrchestratorAccess Manager

1152 MBconsists of1024 MB Xmxand 128 MBPermGen.

Microsoft InternetExplorer 8.0 or laterMozilla Firefox 3.0 or laterAdobe Flash Player 9 plug-in or later

107 MB

Repository 768 MBconsists of128 MB Xmxand 896 MBPermGen

CDP 1536 MB thisconsists of1280 MB Xmxand 256 MBPermGen.1280 MB

Microsoft Windows 2003server 32-bitMicrosoft Windows Server2008 32-bitMicrosoft Windows XPSP2 32-bitMicrosoft Windows 7 32-bitRed Hat Linux AS/ES 4and 5 32 and 64-bitSun Solaris 9 and 10 32-bitand 64-bit

Pentium 4VM - One (1), 2.8GHzPhysical machine -Two (2), 2.8GHz

40 GB 140 MB

AP Microsoft Windows 2003server 32-bitMicrosoft Windows Server2008 32-bitMicrosoft Windows XPSP2 32-bitMicrosoft Windows 7 32-bitRed Hat Linux AS/ES 4and 5 32 and 64-bitSun Solaris 9 and 10 32-bitand 64-bit

Pentium 4 2.8 GHz 50 MB 136 MB

LAP Microsoft Windows 2003server 32-bitMicrosoft Windows Server2008 32-bitMicrosoft Windows XPSP2 32-bit

50 MB 130 MB






Microsoft Windows 7 32-bitRed Hat Linux AS/ES 4and 5 32 and 64-bitSun Solaris 9 and 10 32-bitand 64-bit

HACDP Microsoft Windows 2003server 32-bitMicrosoft Windows Server2008 32-bitWindows 2003 64-bitWindows Server 2008 32and 64-bitRed Hat Linux AS/ES 4and 5 32 and 64-bitSun Solaris 9 and 10 32-bitand 64-bit

60 MB 140 MB

BMC AtriumOrchestratorDevelopment Studio

Microsoft Windows XPSP2 32-bitMicrosoft Windows 7 32-bitMac OS X Leopard

Pentium 4 2.8 GHz 16 MB 100 MB

BMC AtriumOrchestratorOperator ControlPanel

768 MBconsists of128 MB Xmxand 896 MBPermGen.

Microsoft InternetExplorer 8.0 or laterMozilla Firefox 3.0 or laterAdobe Flash Player 9 plug-in or later

80 MB

Graphing server 768 MBconsists of128 MB Xmxand 896 MBPermGen.

85 MB

Base adapters up to 60MB

Applicationadapters

up to240 MB

Run books up to40 MB






Modules up to62 MB

BMC Software recommends using a 64-bit system for optimal performance. If yourBMC Atrium Orchestrator configuration will run medium or large loads, BMCSoftware recommends using a 64-bit system. For medium and large loads thememory settings are:

■ Medium loads - 64-bit system and 2 GB memory per peer

■ Large loads - 64-bit system and 4 GB memory

During runtime, each component creates at least one log files set, which will vary insize based on configuration. The CDP, AP, and BMC Atrium OrchestratorDevelopment Studio can also be configured to create a second log set. An individuallog file can retain up to 4 MB of data. Upon reaching log capacity, the active log fileis archived and a new active log is created. A standard log set may contain oneactive log and up to nine archive log files, requiring 40 MB of disk space.

Software requirements

Supported operating systems, Java VM, and Internet software are listed in table inthe Software requirements section. The table below describes the software requiredto run BMC Atrium Orchestrator and all components:

Note The Microsoft Windows and Red Hat Linux platforms are supported on dedicated servers andvirtual machines (VMs) in the VMware environment. When a component is running in a VM, youmust allocate sufficient resources to it.

Requirements Notes

JAVA

Sun JSE Development Kit 6.0 (JDK 6.0) update 16 The JDK version must be 1.6.X or later. BMC Softwarerecommends 1.6_16. BMC Software does not supportother versions.If you in install BMC Atrium Orchestrator DevelopmentStudio on a 64-bit OS then you must use a 64-bit VM.

Network software


Requirements Notes

Supported operating systems have built-in TCP/IP network software.Stand-alone named and default instancessupport the following network protocols:

■ Shared memory

■ Named pipes

■ TCP/IP

Network software requirements for BMC AtriumOrchestrator installations running on 64-bit OS are thesame as the requirements for those running on 32-bitversions.

Internet software

■ Microsoft Internet Explorer 8.0 or later

■ Mozilla Firefox 3.0 or later

■ Adobe Flash Player 9 plug-in or later

Only use these products and versions to run BMCAtrium Orchestrator Operator Control panel, BMCAtrium Orchestrator Grid Manager and BMC AtriumOrchestrator Access Manager.

Unix

■ Red Hat Linux AS/ES 4 and 5 32 and 64-bit

■ Sun Solaris 9 and 10 32-bit and 64-bit

Linux distributors may provide packages foryour distribution that have differentrequirements. BMC Atrium Orchestratorrequires the following libraries or packages onLinux:

BMC Atrium Orchestrator Grid Manager CDP/AP/LAP/AM/Repository

■ GTK+ 2.10 or higher,

■ GLib 2.12 or higher,

■ Pango 1.14 or higher,

■ X.Org 1.0 or higher.

For optimal functionality, BMC Softwarerecommends the following libraries or packages onLinux:

■ NetworkManager 0.7 or higher

■ DBus 1.0 or higher

■ HAL 0.5.8 or higher

■ GNOME 2.16 or higher.


Ports requirementsPeer communications are established through HTTP and TCP ports. BMC AtriumOrchestrator communications require unique port assignment, and each componenthas specific port requirements. The web server requires two ports: one for standardcommunications, and a second to receive shutdown commands. Differentcomponents can use the same port, provided they are installed on separate servers.A port number must be available exclusively on a server.

Note Port 1089, the JMX RMI service port, is set at installation prior to starting BMCAtrium Orchestrator. It is a hardcoded port value in the platform installation. Priorto installing BMC Atrium Orchestrator, ensure that port 1089 is not in use.

Port description Protocol Components Default port

HTTP port HTTP BMC Atrium Orchestrator AccessManager, repository, CDP, AP, graphingcomponents1

8080

Shutdown port HTTP CDP, repository1 8005

Peercommunications port

JMS with SSL CDP1 8081

HACDP 2 8083

AP -- listens on the first port available inthe range. The first available port in therange becomes the default port. 2

8083-8339

LAP -- listens on the first JMS portavailable in the range. The first availableport in the range becomes the default port.2

8083-8339

Communications port

SSL or TCP BMC Atrium Orchestrator AccessManager1

61616

1 You can set this port value during installation.

2 You cannot set this port value during installation.

Time synchronizationBMC Software recommends a network time protocol (NTP) server to managesynchronization. Verify that the date and time values for the servers housing BMCAtrium Orchestrator components are synchronized within a tolerance of fiveseconds. BMC Software recommends a network time protocol (NTP) server tomanage synchronization.

Ports requirements


Platform installationThis chapter describes the installation procedure.

Typical installationThis section describes a BMC Atrium Orchestrator typical installation and the orderin which you must install the components, are described in this section. In theplatform installation examples in this guide, a typical BMC Atrium Orchestratorinstallation consists of :

■ Access Manager

■ Repository

■ CDP

■ Optional components

— Graphing server

— Operator Control Panel.

Component installation order

To ensure a successful installation, you must be logged in as an administrator andinstall in the order described below:

1 Access Manager - You must install this component first. You can install AccessManager with the repository or in a separate directory.

3

Chapter 3 Platform installation 23

Note Access Manager and the repository are components available to multiple grids,they are not grid components, therefore, you must install Access Manager andthe repository separately from the CDP.

2 Repository - You can install this component in a separate directory or it can becombined with Access Manager in the same directory.

3 CDP - You can install this component only after successfully installing AccessManager and the repository.

4 Development Studio.

5 content.

Optional Components

1 High-availability configuration distribution peer (HACDP) - You must have aCDP installed prior to installing this peer

2 Activity peer (AP) - You must have a CDP installed prior to installing this peer.

3 Lightweight activity peer (LAP) - You must have a CDP installed prior toinstalling this component.

4 Operator Control Panel - This is an optional component that you can install with aCDP or an AP. You can also install the component in its own directory. You musthave a CDP or AP installed prior to installing this component.

5 Graphing server - This component is an optional component that you can installwith a CDP or an AP in the same directory or in a separate directory. You musthave a CDP or AP installed prior to installing this component.

Typical installation


GUI Installation proceduresThis chapter describes the graphical user interface installation procedures for BMCAtrium Orchestrator.

Installing BMC Atrium Orchestrator AccessManager and the repository

BMC Atrium Orchestrator Access Manager and the repository are componentsavailable to multiple grids; they are not grid components. You must install BMCAtrium Orchestrator Access Manager and the repository separately from the CDP.You must be logged on as an administrator and have administrator rights on thecomputer where you will install BMC Atrium Orchestrator.

To install BMC Atrium Orchestrator Access Manager and the repository

1 Navigate to and run the installer.

Note When running the installation programs in Microsoft Windows, the installermight display the following message instructing you to change your MicrosoftWindows computer to unrestricted mode:This machine has to be configured to allow running in unrestrictedmode.

Step 1: Go to the Start Menu -> Control Panel -> System. Selectthe Advanced tab and then the Settings button in Performancesection. Select the Data Execution Prevention tab.

Step 2: Add this application to DEP by clicking the Add button,and select path \<Installation directory>\<Installer file name>.Select Apply. Select OK.

Step 3: Reboot.

2 On the Welcome to BMC Atrium Orchestrator panel, click Next.

4

Chapter 4 GUI Installation procedures 25

3 At the BMC Atrium Orchestrator License Agreement panel, select I accept theterms of the License Agreement and click Next.

4 On the Installation Type panel, select Install new Orchestrator components andclick Next.

5 On the Directory selection panel perform one of the following actions:

■ Click Next to accept the default directory location.

■ Provide a directory in which to install BMC Atrium Orchestrator.

6 On the New installation feature selection panel, Access Manager and Repositoryare automatically selected, click Next.

7 On the Choose Java Virtual Machine panel, select the Java VM 1.6_16 for BMCAtrium Orchestrator to use.

Tip If the choices displayed are not correct, you can locate the Java VM 1.6_16 on yoursystem by clicking Search Another Location or Choose Java executable.

8 On the Web Server Settings panel you can either:

■ Provide the HTTP port and Shutdown port information then click Next.

■ Click Next to accept the default values.

Note The default value for the HTTP port is 8080. The default value for the Shutdownport is 8005.

9 On the Access Manager Communications Settings panel you can either:

■ Enter the host name or IP address and click Next to use the default values forcommunications port, web server protocol, and web server port.

■ Enter the settings for your system and click Next.

Communication settings Default value

Host name or IP address There is no default value.

Communications port The default value is 61616.

Web server protocol The default value is HTTP.

Web server port number The default value is 8080.

Installing BMC Atrium Orchestrator Access Manager and the repository


Note The installer verifies the communication settings. If you provide invalidinformation or if there is a port conflict the installation process halts and aninstallation panel describing the invalid information is displayed. After youprovide valid values the installation continues.

10 On the Installation preview panel review the features that you selected to installand clickNext.

11 On the Start Server panel, you can choose Yes to start the server.

12 On the Installation summary panel you have the choice to:

■ Click Done to exit the installer.

■ Click View Log to review the BAO_install_log.txt file and then click Done toexit the installer.

Verifying the BMC Atrium Orchestrator Access Managerinstallation

This section contains the steps to verify that BMC Atrium Orchestrator AccessManager is successfully installed.

To verify the BMC Atrium Orchestrator Access Manager installation

To verify that the installation is successful, launch BMC Atrium Orchestrator AccessManager.

1 Ensure that the BMC Atrium Orchestrator Access Manager server is started. Ifyou started the server at the end of the installation, skip to step 2.

a On Microsoft Windows, in the Services panel, right-click on BMC AtriumOrchestrator Access Manager and select Start.

b On Red Hat Linux and Sun Solaris in the console type:$AO_HOME/bin/server.sh start

2 In a web browser, launch BMC Atrium Orchestrator Access Manager by typing:

http://<hostname or IP>:<Web server port>/baoam/login.jsf

Installing BMC Atrium Orchestrator Access Manager and the repository


The hostname or IP indicates the IP address or host name used to install theproduct. The Web server port is the value entered during the installation. So if theIP address was 127.01.123.01 and the port was 7680 the URL would be:http://127.01.123.01:7680/baoam/login.jsf

Note The default credentials for BMC Atrium Orchestrator Access Manager are username admin and password admin123.After BMC Atrium Orchestrator launches, you have verified the installation.

If a problem occurs

If BMC Atrium Orchestrator Access Manager does not launch, use the following tipsto troubleshoot the issue.

■ Ensure that you started the service.

■ Verify the IP address or host name you used in the URL to launch BMC AtriumOrchestrator Access Manager.

■ Verify the port number you used in the URL to launch BMC Atrium OrchestratorAccess Manager.

■ Review the bao.options file to ensure the values you are using correspond to thevalues provided during installation.

■ Verify that the Internet browser used to launch BMC Atrium Orchestrator AccessManager is a supported browser type and version.

If you continue to experience difficulties launching BMC Atrium Orchestrator AccessManager contact BMC Software Customer Support.

Installing BMC Atrium Orchestrator AccessManager only

Use these steps to install BMC Atrium Orchestrator Access Manager. The BMCAtrium Orchestrator Access Manager component is available to multiple grids; theyare not grid components. You you must install BMC Atrium Orchestrator AccessManager separately from the CDP. BMC Atrium Orchestrator is the first componentinstalled in the BMC Atrium Orchestrator solution. The configuration informationprovided is used in subsequent component installations. You must be logged on asan administrator and have administrator rights on the computer where you installBMC Atrium Orchestrator Access Manager.

Installing BMC Atrium Orchestrator Access Manager only


Before you begin

To install BMC Atrium Orchestrator Access Manager only





Step 3: Reboot.

2 At the Welcome to BMC Atrium Orchestrator panel, review the information andclick Next.

3 On the BMC Atrium Orchestrator License Agreement panel, select I accept theterms of the License Agreement and then click Next.

4 On the Installation Type panel, select Install new Orchestrator components andthen click Next.

5 On the Directory selection panel, you can enter a destination directory or clickNext to accept the default destination directory.

6 On the New installation feature selection panel, select Access Manager Only andclick Next.


Tip If the choices displayed are not correct, you can locate the Java VM 1.6_16 on yoursystem by clicking Search Another Location or Java executable.

8 On the Web Server Settings, enter the HTTP port and Shutdown port informationor click Next to accept the default values.




9 On the Access Manager Communications Settings panel, you can use the defaultsettings or provide settings for the installer to use:

■ To accept the default settings, click Next.

■ Enter the settings for your system and click Next.

Access Manager Communication Settings Default value


Communications port - The default value is 61616.



Note The installer verifies the communication settings. If you provide invalidinformation the installation process halts until you provide valid values.

10 Review the installation summary on the Installation preview panel and clickNext.

The installation procedure starts.

11 On the Start Server panel, you can choose Yes to start the server.

12 On the Installation summary panel you can either click:

■ View Log to review the BAO_install_log.txt file.

■ Done to exit the installer.

Verifying the BMC Atrium Orchestrator Access Managerinstallation

This section contains the steps to verify that BMC Atrium Orchestrator AccessManager is successfully installed.



To verify the BMC Atrium Orchestrator Access Manager installation

To verify that the installation is successful, launch BMC Atrium Orchestrator AccessManager.

1 Ensure that the BMC Atrium Orchestrator Access Manager server is started. Ifyou started the server at the end of the installation, skip to step 2.

a On Microsoft Windows, in the Services panel, right-click on BMC AtriumOrchestrator Access Manager and select Start.

b On Red Hat Linux and Sun Solaris in the console type:$AO_HOME/bin/server.sh start

2 In a web browser, launch BMC Atrium Orchestrator Access Manager by typing:

http://<hostname or IP>:<Web server port>/baoam/login.jsf

The hostname or IP indicates the IP address or host name used to install theproduct. The Web server port is the value entered during the installation. So if theIP address was 127.01.123.01 and the port was 7680 the URL would be:http://127.01.123.01:7680/baoam/login.jsf

Note The default credentials for BMC Atrium Orchestrator Access Manager are username admin and password admin123.After BMC Atrium Orchestrator launches, you have verified the installation.

If a problem occurs

If BMC Atrium Orchestrator Access Manager does not launch, use the following tipsto troubleshoot the issue.


■ Verify the IP address or host name you used in the URL to launch BMC AtriumOrchestrator Access Manager.

■ Verify the port number you used in the URL to launch BMC Atrium OrchestratorAccess Manager.


■ Verify that the Internet browser used to launch BMC Atrium Orchestrator AccessManager is a supported browser type and version.



If you continue to experience difficulties launching BMC Atrium Orchestrator AccessManager contact BMC Software Customer Support.

Installing the repository onlyThe repository is a required component that is installed either with BMC AtriumOrchestrator Access Manager or on its own. You must supply the BMC AtriumOrchestrator Access Manager communication settings during the repositoryinstallation The installer verifies the communication settings you provide. If youprovide invalid information or if there is a port conflict the installation process haltsand an installation panel describing the invalid information is displayed. After youprovide valid values the installation continues.

To install the repository only

You must be logged in as an administrator and have administrator rights on themachine on which you install BMC Atrium Orchestrator.





Step 3: Reboot.

2 high availability configuration distribution peer high availability configurationdistribution peer On the Installation Type panel select Install new OrchestratorComponents; then click Next.


4 On the New installation feature selection panel, select Repository Only.

The feature set opens and the Web Server is automatically selected.

Installing the repository only


5 On the Choose Java Virtual Machine panel, select the Java VM; then click Next.

Note BMC Atrium Orchestrator requires Java VM 1.6_16.

6 On the Web Server Settings panel, click Next to accept the default web serverHTTP and shutdown ports or provide values and then click Next.

7 On the Access Manager Communications panel, you must provide the host nameor IP address and communications port number for BMC Atrium OrchestratorAccess Manager.

8 Review the information on the Installation preview panel, when you havefinished reviewing the preinstallation summary, click Install.

9 Click Yes when prompted to restart the server; then click Next.

10 When the installation finishes, you can view the log and click Done to exit theinstaller.

Verifying the repository installation

The repository does not have a separate interface. The repository interface isincorporated in BMC Atrium Orchestrator Grid Manager. To verify the repositoryinstallation you need to open the catalina log in the [PEER_HOME]/tomcatdirectory and see if errors are displayed in the file. If no errors are displayed in thefile, then the repository installed successfully.

To verify the repository installation

1 Start BMC Atrium Orchestrator Access Manager server or BMC AtriumOrchestrator Access Manager and Repository server.

2 In a text editor, open the catalina.<yyyy-mm-dd>.log.

The catalina<yyyy-mm-dd>.log is found in the [PEER_HOME]/tomcat/logsdirectory. This file records information from starting and running the server.

3 Review the log file for errors. If the repository did not install correctly, you willsee an error message that is displayed just beneath the logging messages for BMCAtrium Orchestrator Access Manager. If the repository is installed successfullythere will be no entry in the catalina<yyyy-mm-dd>.log. Contact BMC SoftwareCustomer Support if the repository did not install successfully.

Installing the repository only


In the following figure, the repository is not successfully installed.

Figure 2: Sample catalina log file with errors

Installing a configuration distribution peerThis section describes the procedure to install CDP only. You must install BMCAtrium Orchestrator Access Manager and the repository prior to installing the CDP.During installation, the installer searches for and uses the BMC Atrium OrchestratorAccess Manager and the repository configuration information. The installer verifiesthe communication settings you provide. If you provide invalid information or ifthere is a port conflict the installation process halts and an installation paneldescribing the invalid information is displayed. After you provide valid values theinstallation continues.

To install a CDP only


Installing a configuration distribution peer





Step 3: Reboot.

2 At the BMC Atrium Orchestrator License Agreement panel, select I accept theterms of the License Agreement; then click Next.

3 On the Installation Type panel select Install new Orchestrator components andclick Next.

4 On the Directory selection panel, you can use the default installation location orprovide an installation location.

■ Click Next to use the default installation directory.

■ Enter an installation directory and click Next.

5 On the New installation feature selection panel, select ConfigurationDistribution Peer and click Next.



7 On the Web Server Settings panel you can either:






8 On the Configuration Distribution Peer Settings panel, provide the settingsinformation and click Next.

configuration distribution settings Default value

CDP is primary This is the default selection.

CDP is secondary (HA)

Environment Name ENV1

Peer Name CDP1

Certificate Holder Name: My Company Name

Certificate Holder Password

Peer Communications Port Number 8081

9 On the Access Manager Communications Settings panel, enter values in the HostName or IP Address and the Communications Port Number click Next .

■ Tip

If you cannot remember your settings, open the bao.options file to see thesetting used during the BMC Atrium Orchestrator Access Manager installation.

10 On the Repository Communication Settings panel, verify the repository settingsand click Next.

11 The Graphing Server Communications panel displays even if you did not select toinstall a graphing server. On the Graphing Server Communications panel, youcan either:

a Do not provide values and click Next to continue.

b To install a graphing server, provide the host name or IP address and the webserver port number for the server and then click Next.

12 Review the information on the Installation Preview Panel. When you havefinished reviewing the pre-installation summary, click Install.

13 On the Installation summary panel you can either:

■ Click Done to exit the installer.



■ Click View Log to review the BAO_install_log.txt file.


Tip If you are installing many components, click No and do not start the server. Thismakes installing other components faster. You will need to start the server beforelaunching the CDP.

15 When the installation finishes click Done to exit.

Note To review the log file, click View log.

Installing a CDP with BMC AtriumOrchestrator Operator Control Panel and agraphing server

These steps enable you to install a configuration distribution peer with BMC AtriumOrchestrator Operator Control Panel and a graphing server. You must install BMCAtrium Orchestrator Access Manager and the repository prior to installing the CDPwith optional components. During installation, the installer searches for and uses theBMC Atrium Orchestrator Access Manager and the repository configurationinformation. The installer verifies the communication settings you provide. If youprovide invalid information or if there is a port conflict the installation process haltsand an installation panel describing the invalid information is displayed. After youprovide valid values the installation continues.

To install a CDP with BMC Atrium Orchestrator Operator Control Panel and agraphing server

Note You must be logged on with administrator rights on the server where you will installBMC Atrium Orchestrator.

1 Navigate to and then run the installer,

Installing a CDP with BMC Atrium Orchestrator Operator Control Panel and a graphing server


Note When running the installation programs in Microsoft Windows, the installer maydisplay the following message instructing you to change your MicrosoftWindows computer to unrestricted mode:This machine has to be configured to allow running in unrestrictedmode.


Step 2: Add this application to DEP by clicking the Add button,and select path \<installation directory>\<installer file name>.Select Apply. Select OK.

Step 3: Reboot.

2 At the Welcome to BMC Atrium Orchestrator panel, review the information andclick Next.

3 On the BMC Atrium Orchestrator License Agreement panel, select I agree to theterms of the License Agreement and then click Next.

4 On the Installation Type panel, select Install new Orchestrator components andthen click Next.


6 On the New installation feature selection panel, select ConfigurationDistribution Peer , Operator Control Panel and the graphing server, then clickNext.



8 On the Web Server Settings panel you can:






9 On the OCP to CDP Communications Settings panel, enter the communicationsettings:

OCP to CDP communication setting Default value

Web Server Protocol httpValid values: http, https

CDP IP Address The IP address of the current machine

Grid Name GRID1

10 On the Access Manager Communications Settings panel, you can use the defaultsettings or provide settings for the installer to use:

■ Enter the host name or IP address and click Next to use the default values forcommunicating port, web server protocol, and web server port.

■ Enter the settings for your system and click Next .

Communication settings Default value


Communications port The default value is 61616.



11 On the Repository Communications Settings panel, enter the settings for therepository, host name or IP address, communications port number and webserver protocol; then click Next.

12 On the Graphing Server Communications panel, provide the host name or IPaddress and the web server port number for the server and then click Next.

13 On the Installation preview panel review the features that you selected to installand clickNext.

14 On the Start Server panel you can choose Yes to start the server.




15 On the Installation summary panel

■ You can click Done to exit the installer.

■ You can click View Log to review the BAO_install_log.txt file.

Verifying the configuration distribution peer installation

To verify the CDP installation is successful, launch BMC Atrium Orchestrator GridManager. These steps describe the launch procedures.

To verify the configuration distribution peer installation

1 Ensure the BMC Atrium Orchestrator Access Manager and BMC AtriumOrchestrator Repository server are started.

2 Ensure the BMC Atrium Orchestrator Configuration Distribution Peer is started.If you started the server at the end of the installation, skip to step 2. Use thefollowing steps to start the server.

a On Microsoft Windows, in the Services panel, right-click on BMC AtriumOrchestrator Grid Manager and select Start.

b On Red Hat or Suse Linux and Sun Solaris in the console type:$AO_HOME/bin ./server.sh start

3 In a web browser, launch BMC Atrium Orchestrator Grid Manager by typing theURL:

http://<hostname or IP>:<Web server port>/baocdp/gm

The hostname or IP indicates the IP address or host name used to install the CDP.The Web server port is the value entered during the installation. For example, ifyou entered the IP address 127.01.123.01 and the port number 7680 duringinstallation, you would use the following URL to launch BMC AtriumOrchestrator Grid Manager:http://127.01.123.01:7680/baocdp/gm



Note The default credentials for BMC Atrium Orchestrator Grid Manager are username admin and password admin123.

After BMC Atrium Orchestrator Grid Manager launches you have verified theinstallation.

If a problem occurs

If you cannot launch BMC Atrium Orchestrator Grid Manager use the followingsuggestions to troubleshoot the issue.


■ Verify the IP address or host name you used in the URL to launch BMC AtriumOrchestrator Grid Manager.

■ Verify the port number you used in the URL to launch BMC Atrium OrchestratorGrid Manager.


■ Verify that the Internet browser used to launch BMC Atrium Orchestrator GridManager is a supported browser type and version.

If you continue to experience difficulties launching BMC Atrium Orchestrator GridManager contact BMC Software Customer Support.

Verifying the BMC Atrium Orchestrator Operator ControlPanel installation

To verify BMC Atrium Orchestrator Operator Control Panel Installation

To verify that BMC Atrium Orchestrator Operator Control Panel is successfullyinstalled you must launch the application. The steps below describe how to launchBMC Atrium OrchestratorOperator Control Panel.

If you do not have workflow exposed to BMC Atrium Orchestrator Operator ControlPanel and activated on the grid, then you will not see workflow in the BMC AtriumOrchestrator Operator Control Panel.

1 Prior to launching BMC Atrium Orchestrator Operator Control Panel ensure theserver is started.



a On Microsoft Windows, in the Services panel, right-click on BMC AtriumOrchestrator Operator Control Panel and select Start.


2 In a web browser, launch BMC Atrium Orchestrator Operator Control Panel bytyping:

http://<hostname or IP>:<Web server port>/baoocp/ocp.jsp

This URL is an example where hostname or IP indicates the IP address or hostname used during product installation. The Web server port is the value enteredduring the installation. For example, if you used the IP address 127.01.123.01 andthe port number 7680 during installation, you would launch BMC AtriumOrchestrator Operator Control Panel with the URL:http://127.01.123.01:7680/baocdp/ocp.jsp

After BMC Atrium Orchestrator Operator Control Panel launches you haveverified the installation.

Verifying the graphing server installation

To verify the graphing server installation you can launch the sample graphics files. Ifyou have enabled metric reporting in BMC Atrium Orchestrator Grid Manager. Thegraphing server provides reports in a pie-chart view showing the number of metricsrecorded by description, by status or by description and status, over a specified timeperiod. With the graphing server you can see these types of business and processmetrics reports:

■ Metrics by description


■ Metrics by status

■ Load by peer

■ Load by process

To verify the graphing server installation

1 Prior to launching the graphing server, ensure the server is started. If the server isnot started.



a On Microsoft Windows, in the Services panel, right-click on BMC AtriumOrchestrator Graphing Server and select Start.

b On Red Hat and Sun Solaris in the console type:$AO_HOME/bin/servers start

2 In BMC Atrium Orchestrator Grid Manager enable metrics reporting. See theBMC Atrium Orchestrator System Administrators guide for details.

Note To see actual data in the reports you need to have a database configured.

3 In a web browser, launch the graphing server to see the sample files by typing:

http://<hostname or IP>:<Graph server port>/barograph/server

This URL is an example where hostname or IP indicates the IP address or hostname used to install the product. The Graph server port is the value enteredduring the installation. So if the IP address was 127.01.123.01 and the port was7680 the URL would be:http://127.01.123.01:7680/baograph/server

4 Open the sample files, by typing the following command:http://<hostname or IP>:<Graph server port>/baograph/sample.jsp

This URL is an example where hostname or IP indicates the IP address or hostname used to install the product. The Graph server port is the value enteredduring the installation. So if the IP address was 127.01.123.01 and the port was7680 the URL would be:http://127.01.123.01:7680/baograph/sample.jsp

5 To access the metrics

Installing an APThe AP accepts and executes workflows and hosts external application adapters,providing both the core workflow engine and a web container. The installer verifiesthe communication settings you provide. If you provide invalid information or ifthere is a port conflict the installation process halts and an installation paneldescribing the invalid information is displayed. After you provide valid values theinstallation continues. You must have a BMC Atrium Orchestrator Access Manager,the repository, and a CDP installed and configured with grids and peers prior toinstalling a AP.

Installing an AP


To install an AP





Step 3: Reboot.


3 On the Installation Type panel, select Install a new Orchestrator; then click Next.




5 On the New installation feature selection panel, select Activity Peer.

6 On the Choose Java Virtual Machine panel, select the directory that contains theJava VM 1.6_16 for BMC Atrium Orchestrator to use.


7 On the Web Server Settings panel, do one of the following, either:



Installing an AP



8 On the Peer to CDP Communications Settings panel, do one of the following,either:

■ Check the Test peer configuration connection box to test the settings

■ Click Next to accept the default settings.

■ Enter the appropriate peer settings and click Next.

Peer to CDP Communication Settings Default value

Protocol HTTP

CDP user name The value from the CDP install

CDP password The password from the CDP install, not visible.

CDP IP address

CDP HTTP port the port provided when the CDP was installed

CDP web context baocdp

Grid name The grid in which the AP was created.

This peer's name The name created on the grid.

9 If you selected the Test peer configuration connection box, then the paneldisplays the connection sucess or failure message.

If the connection failed, you can close the dialog box and continue with theinstallation and resolve the issue later, or you can close the dialog box and clickPrevious to enter different settings.

10 On the Istallation preview panel, when you have finished reviewing thepreinstallation summary, click Install.


Tip If you are installing many components, click No and do not start the server. Thismakes installing other components faster. You will need to start the server beforelaunching.

12 When the installation finishes successfully, view the log and click Done.

Installing an AP


Installing a LAPThe lightweight activity peer (LAP) installs on a third pary systems server. The LAPextends the grid communication to the third-party system and does not executeworkflows. You cannot install graphing components on an LAP.You must have aCDP installed and configured with grids and peers prior to installing a LAP. Youinstall peers one at a time

To install a LAP





Step 3: Reboot.


3 On the Installation Type panel, select Install a new Orchestrator; then click Next.




5 On the New installation feature selection panel, select Lightweight Activity Peer.

6 On the Choose Java Virtual Machine panel, select the directory that contains JavaVM 1.6_16; then click Next.


Installing a LAP


7 On the Web Server Settings panel, enter the web server HTTP and Shutdown portsettings; then click Next.

■ Click Next to accept the default web server HTTP and shutdown ports. or

■ If you are installing using an existing web server the Deployment Server TypeSettings panel is displayed. Enter or click Browse to navigate to the web serverdeployment folder and click Next.

8 On the Peer to CDP Communications Settings panel, check the Test peerconfiguration connection box if you want to test the settings.

9 On the Peer to CDP Communications Settings panel, do one of the following:




Protocol HTTP

CDP user name The value from the CDP install

CDP password The password from the CDP install, not visible.

CDP IP address

CDP HTTP port the port provided when the CDP was installed




10 If you selected the Test peer configuration connection box then the paneldisplays the connection sucess or failure message.

11 On the installation preview panel, when you have finished reviewing thepreinstallation summary, click Install.



Installing a LAP


Installing a HACDPThis section describes the procedure to install a HACDP. You must install BMCAtrium Orchestrator Access Manager, the repository, and a CDP prior to installingthe haCDP. At installation, the high-availability configuration distribution peer(HACDP) searches for and uses the CDP, BMC Atrium Orchestrator AccessManager, and the repository configuration information. You must be logged on as anadministrator and have administrator rights for the machine on which you areinstalling. The installer verifies the communication settings. If you provide invalidinformation or if there is a port conflict the installation process halts and aninstallation panel describing the invalid information is displayed. After you providevalid values the installation continues.

To install a HACDP

1 Navigate to and then run the installer,

Note When running the installation programs in Microsoft Windows, the installer maydisplay the following message instructing you to change your MicrosoftWindows computer to unrestricted mode:This machine has to be configured to allow running in unrestrictedmode.


Step 2: Add this application to DEP by clicking the Add button,and select path \<installation directory>\<installer file name>.Select Apply. Select OK.

Step 3: Reboot.


3 On the Installation Type panel selectInstall new Orchestrator components andclick Next.




5 On the New installation feature selection panel, select ConfigurationDistribution Peer and click Next.

Installing a HACDP




7 On the Web Server Settings panel, do one of the following:




8 On the Configuration Distribution Peer Settings panel, click CDP is secondary(HA) and click Next.

Peer to CDP Communication settings Default value


CDP User Name admin

CDP Password

CDP IP Address Provide the IP address of the CDP.

CDP Web Server Port Number Provide the web server port number for the CDP.

CDP Web Context This is the web context used when installing the CDP.

This Peer's Name The name for the HACDP peer.

Tip If you cannot remember the CDP communiction settings, you can find the settingsin the bao.options file.

9 On the Access Manager Communications Settings panel, enter values in the HostName or IP Address and the Communications Port Number click Next .

Tip If you cannot remember your settings, open the bao.options file to see the settingused during the BMC Atrium Orchestrator Access Manager installation.

Installing a HACDP



11 On the Graphing Server Communications panel, enter the host name or IPaddress and the web server port number, then click Next.

Note If you are not installing a graphing server, skip this panel.You can enter settings to direct the CDP to a different repository, then click Next.

The installer verifies the communication settings. If you provide invalidinformation or if there is a port conflict the installation process halts and aninstallation panel describing the invalid information is displayed. After youprovide valid values the installation continues.

12 On the Installation Preview Panel, when you have finished reviewing the pre-installation summary, click Install.

13 On the Installation summary panel you can either:

■ Cick Done to exit the installer.

■ Click View Log to review the BAO_install_log.txt file.





Verifying a peer installation

To verify that the installation of an per is successful, you need to launch BMCAtrium Orchestrator Grid Manager. These steps describe the launch procedures.

■ Ensure that the server for BMC Atrium Orchestrator Grid Manager and the peer isrunning.

Verifying a peer installation


■ Launch BMC Atrium Orchestrator Grid Manager and create the peers.

■ Review the status of the peers in BMC Atrium Orchestrator Grid Manager.

To verify a peer installation

1 Ensure that the server for BMC Atrium Orchestrator Grid Manager and the peer,AP, LAP, HACDP, is running.

a On Microsoft Windows, in the Services panel, right-click on the server BMCAtrium Orchestrator Grid Manager, Activity Peer, Lightweight Activity Peer,or High Availability Peer, and select Start.


2 In a web browser, launch BMC Atrium Orchestrator Grid Manager by typing theURL:

http://<hostname or IP>:<Web server port>/baocdp/gm

In this URL hostname or IP indicates the IP address or host name used to installthe CDP. The Web server port is the value entered during the installation. Forexample, if you entered the IP address 127.01.123.01 and the port number 7680during installation, you would use the following URL to launch BMC AtriumOrchestrator Grid Manager:http://127.01.123.01:7680/baocdp/gm

Note The default credentials for BMC Atrium Orchestrator Grid Manager are username admin and password admin123.

3 Create the peers. See the BMC Atrium Orchestrator System Administrator Guidefor details.

4 Review the status of the peers in BMC Atrium Orchestrator Grid Manager

Installing the BMC Atrium OrchestratorOperator Control Panel

The Operator Control Panel is a web application that enables you to manipulate andcontrol workflow execution. This section describes installing the BMC AtriumOrchestrator Operator Control Panel with the GUI installer on Microsoft Windows,Red Hat Linux, or Sun Solaris.

Installing the BMC Atrium Orchestrator Operator Control Panel


Before you begin

■ You must have a CDP installed and configured.

■ You must have administrator rights when you install the software.

■ You must use the supported internet software:

— Microsoft Internet Explorer 8.0 or later

— Mozilla Firefox 3.0 or later

— Adobe Flash Player 9 plug-in or later

To install the BMC Atrium Orchestrator Operator Control Panel


Note When running the installation programs in Microsoft Windows, the installer maydisplay the following message instructing you to change your MicrosoftWindows computer to unrestricted mode.This machine has to be configured to allow running in unrestrictedmode.



Step 3: Reboot.

2 On the Welcome to BMC Atrium Orchestrator panel read the information andclick Next.


4 On the Installation Type panel, select Install new Orchestrator components; thenclick Next.

5 On the Directory selection panel, you can use the default installation location orspecifiy an installation location.

■ Click Next to use the default installation directory for Windows C:\Program Files\BMC Software\AO .




6 On the New installation feature selection panel, click the checkbox for OperatorControl Panel and then click Next.







9 On the OCP to CDP Communication Settings panel, Operator Control Panelfeature the Operator Control Panel to CDP Communication Settings panel isdisplayed. Click Next to accept the default settings or enter the appropriateOperator Control Panel to CDP communication settings and click Next.

OCP to CDP Communication settings Default value


CDP IP Address You must provide the IP address to the CDP.

CDP Web Server Port Number 8080

CDP Web Context baocdpYou must provide the web context used when theCDP was installed.

Grid Name The name of the grid on the CDP.

10 To test the peer configuration connection, click the Test peer configurationconnection check box.

If the installer validates the connection, then the installer continues to the nextpanel. If the installer cannot validate the connection, then you can continue with



the installation and troubleshoot the connection after installation or you providealternate communication settings.

11 On the Access Manager Communication Settings panel, provide the host name orIP address and the communications port number for BMC Atrium OrchestratorAccess Manager and click Next.

The installer verifies the communication settings. If the communication settingsare incorrect, then the installation pauses until the correct values are provided.

12 On the Installation preview panel, review the features to be installed and clickNext.

13 On the Start Server panel, click Yes to start the server.

Tip If you are installing many components, click No and do not start the server. Thismakes installing other components faster. You will need to start the server beforelaunching the CDP or BMC Atrium Orchestrator.




Tip The BAO_install_log.txt file is stored in the temporary directory used for theinstallation.

Verifying the BMC Atrium Orchestrator Operator ControlPanel installation

To verify BMC Atrium Orchestrator Operator Control Panel Installation

To verify that BMC Atrium Orchestrator Operator Control Panel is successfullyinstalled you must launch the application. The steps below describe how to launchBMC Atrium OrchestratorOperator Control Panel.

If you do not have workflow exposed to BMC Atrium Orchestrator Operator ControlPanel and activated on the grid, then you will not see workflow in the BMC AtriumOrchestrator Operator Control Panel.



1 Prior to launching BMC Atrium Orchestrator Operator Control Panel ensure theserver is started.

a On Microsoft Windows, in the Services panel, right-click on BMC AtriumOrchestrator Operator Control Panel and select Start.


2 In a web browser, launch BMC Atrium Orchestrator Operator Control Panel bytyping:

http://<hostname or IP>:<Web server port>/baoocp/ocp.jsp

This URL is an example where hostname or IP indicates the IP address or hostname used during product installation. The Web server port is the value enteredduring the installation. For example, if you used the IP address 127.01.123.01 andthe port number 7680 during installation, you would launch BMC AtriumOrchestrator Operator Control Panel with the URL:http://127.01.123.01:7680/baocdp/ocp.jsp

After BMC Atrium Orchestrator Operator Control Panel launches you haveverified the installation.

Installing the graphing serverThe Operator Control Panel is a web application that enables you to manipulate andcontrol workflow execution.

Before you begin

■ You must have a CDP installed and configured.

■ You must have administrator rights when you install the software.

To install the graphing server


Installing the graphing server





Step 3: Reboot.


3 On the Installation Type panel, select Install new Orchestrator components; thenclick Next.

4 On the New installation feature selection panel, select Graphing Server and clickNext.

5 On the Choose Java Virtual Machine panel, select the Java VM 1.6_16 file to use.


6 On the Web Server Settings panel:




7 On the Installation preview panel, review the information and click Install.











Verifying the graphing server installation

To verify the graphing server installation you can launch the sample graphics files. Ifyou have enabled metric reporting in BMC Atrium Orchestrator Grid Manager. Thegraphing server provides reports in a pie-chart view showing the number of metricsrecorded by description, by status or by description and status, over a specified timeperiod. With the graphing server you can see these types of business and processmetrics reports:



■ Metrics by status

■ Load by peer

■ Load by process

To verify the graphing server installation

1 Prior to launching the graphing server, ensure the server is started. If the server isnot started.

a On Microsoft Windows, in the Services panel, right-click on BMC AtriumOrchestrator Graphing Server and select Start.

b On Red Hat and Sun Solaris in the console type:$AO_HOME/bin/servers start



2 In BMC Atrium Orchestrator Grid Manager enable metrics reporting. See theBMC Atrium Orchestrator System Administrators guide for details.

Note To see actual data in the reports you need to have a database configured.

3 In a web browser, launch the graphing server to see the sample files by typing:

http://<hostname or IP>:<Graph server port>/barograph/server

This URL is an example where hostname or IP indicates the IP address or hostname used to install the product. The Graph server port is the value enteredduring the installation. So if the IP address was 127.01.123.01 and the port was7680 the URL would be:http://127.01.123.01:7680/baograph/server

4 Open the sample files, by typing the following command:http://<hostname or IP>:<Graph server port>/baograph/sample.jsp

This URL is an example where hostname or IP indicates the IP address or hostname used to install the product. The Graph server port is the value enteredduring the installation. So if the IP address was 127.01.123.01 and the port was7680 the URL would be:http://127.01.123.01:7680/baograph/sample.jsp

5 To access the metrics

New BMC Atrium Orchestrator DevelopmentStudio installation worksheet

Use this checklist when installing BMC Atrium Orchestrator Development Studio. Inthe checklist, record the information specific to your system. The installationparameters in the table correspond to parameters in the installation program.

Installation parameter Value

Installation type Install a new Development Studio

Java VM - 1.6_16 The directory with the Java VM 1.6_16.

Destination direction Windows - C:\Program Files\BMC Software\AO\StudioMac - Applications/BMC Software/AO/Studio

Directory to store yourwork

Windows - C:\Documents and Settings\username\DevStudioMac -

New BMC Atrium Orchestrator Development Studio installation worksheet


Installation parameter Value

Where would you like tocreate product icons?Choose the option thatworks best for yourorganization.

In a new Program Group: BMC

Create icons for all users Unchecked is the default value.

Installing BMC Atrium OrchestratorDevelopment Studio

BMC recommends that you install and configure the CDP prior to installingDevelopment Studio. After installing Development Studio you connect to anenvironment on a CDP and import the modules from the grid or repository. Youmust be logged in as an administrator and have administrator rights on thecomputer on which you install BMC Atrium Orchestrator Development Studio.

To install BMC Atrium Orchestrator Development Studio

1 After you have downloaded the installer file navigate to and then run theinstaller,



Step 2: Add this application to DEP by clicking the Add button,and select path \Installers\bao_studio_installer_7_6_00_00. SelectApply. Select OK.

Step 3: Reboot.


3 In the Installation Type panel, select Install a new Development Studio; then clickNext.

Installing BMC Atrium Orchestrator Development Studio


4 In the Choose Java Virtual Machine panel, select the Java VM; then click Next.

Note Development Studio requires Java VM 1.6_16.

5 In the Directory selection panel, click Nextto select the default destinationdirectory or enter a directory and click Next

6 In the Workspace Location panel, click Next to use the default directory or select aworking directory where you will store your work and click Next.

7 In the Choose Shortcut Folder panel, select where you want to create producticons. If you want icons for all users, click the Create Icons for All Userscheckbox; then click Next.

8 In the Installation preview panel, review the summary and click Install.

9 In the Installation summary panel, you can click View Logto view the install logfile BAO_studio_install_log.txt or select Done to exit the installer.

Where to go from here

To ensure the installation is successful, launch BMC Atrium OrchestratorDevelopment Studio.

Installing content with the GUI installerThe content installer is used to install base adapters, adapters, modules, andsolutions. You install content on a CDP and BMC Atrium Orchestrator 7.6.00 storesthe content in the repository. From the repository you enable content on the grid.The file BAO_content_install_log contains the logs of the content installation andcan be used for troubleshooting.

To install content with the GUI installer


Installing content with the GUI installer





Step 3: Reboot.

2 On the Welcome panel, read the information and click Next.

3 On the BMC Atrium Orchestrator License Agreement panel, select I accept theterms of the License Agreement; then click Next.

4 On the Directory selection panel, click Next to accept the default installation path,or browse to select a different CDP folder.

The target path for the content must contain a CDP. You install content onto a CDP.

5 On the Installation Type panel, select Custom feature set, and click Next.

Note If you select existing application adapters or base adapters, they will be updatedto the current version.

6 On the Adapter feature selection panel, select the adapters you want to install andclick Next.

If you click the Adapters check box then you select all adapters. If you select theBase Adapters, BMC application adapters or Third party adapters check box,then you select all the adapters in that group.

7 On the Module feature selection panel, select the run books and managementmodules and core modules you want to install and click Next.

If you click the Modules check box then you select all modules. If you select theRun books, Management modules or Core modules check box, then you selectall the adapters in that group.

8 On the Installation preview panel, review the features. When you have finishedreviewing the summary, click Install.



9 After the installation finishes successfully, click Done.



Silent installation propertiesThe silent installer executes from a command line. The silent installer options file is asimple text file that defines all the required properties for the installation in the formof a prefix tag followed by a key-value pair. You can use the silent installers onLinux, Solaris, and Windows installations. On Windows computers, the silentinstaller does not produce console output, however, on Linux computers, a shortstartup message and a console representation of a progress meter display. Theinstallation completes without comment. Linux computers may output debuglogging to the console by exporting LAX_DEBUG=true. The options file is not requirewhen using the silent installer; however, BMC Software recommends that you use anoptions file when executing a silent installation.

Installation type

The valid installation types are install_new; upgrade_new. To validate the upgradepath of an earlier installation and the destination path of a 7.6.00 installation, specifythe installation type.

Option Description Sample command

install_new Used to install a new version 7.6.00 install. -J AO_INSTALL_TYPE=install_new

upgrade_new You can use this option to do the following:

■ Upgrade a version a 7.5.00 installation to aversion 7.6.00 installation

■ Repair a version 7.6.00 installation.

■ Add new features to version 7.6.00 installation

-J AO_INSTALL_TYPE=upgrade_new

5

Chapter 5 Silent installation properties 63

Silent installation properties

In the options file, the AO_INSTALLING_FEATURES property specifies whichfeatures to include in the silent installation. Combinations of feature names andcomponents for this property are defined in the table below.

Property Description

AO_INSTALLING_FEATURES Specifies the peer type to install.Valid values : Access Manager, REPO, CDP, HACDP, AP, LAP, OCP,GRAPH, WEBSERVERThis property specifies installing BMC Atrium Orchestrator AccessManager-J INSTALLING_FEATURES_SELECTIONS=AM,REPO

This property specifies installing a CDP and BMC Atrium OrchestratorOperator Control Panel.-J INSTALLING_FEATURES_SELECTIONS=CDP,OCP

AO_START_SERVER_ON_SUCCESS

Specifies whether or not to start the server after a successfulinstallation. The expected values are true or false.-J AO_START_SERVER_ON_SUCCESS=true

BMC Atrium Orchestrator Access Manager

AO_SECURITY_COMM_HOST Specifies the host name or IP address for Access Manager. The valuecannot be a loopback address.-J AO_SECURITY_COMM_HOST=<Host name or IP address>

AO_SECURITY_COMM_PORT Specifies the Access Manager agent communications port. Theexpected value is <port number>.Defalut value: 61616-J AO_SECURITY_COMM_PORT=61616

AO_SECURITY_COMM_PROTOCOL

Specifies the protocol used. The valid values are http, https, or ssl.Default value: ssl-J AO_SECURITY_COMM_PROTOCOL=ssl

AO_SECURITY_WEB_PROTOCOL

Specifies the protocol used for BMC Atrium Orchestrator AccessManager. This value is used in the URL to launch BMC AtriumOrchestrator Access Manager.Default value: http.Valid values: http, https-J AO_SECURITY_WEB_PROTOCOL=http

AO_SECURITY_WEB_PORT Specifies the port used for BMC Atrium Orchestrator Access Manager.This value is used in the URL to launch BMC Atrium OrchestratorAccess Manager. The expected value is <port number>.-J AO_SECURITY_WEB_PORT=8080



Repository installation

AO_WEBSERVER_PORT Specifies the port number for the web sever. The expected value is<port number>.Default value: 8080-J AO_WEBSERVER_PORT=8080

AO_WEBSERVER_SHUTDOWN_PORT

Specifies the web server shut down port. The expected value is <portnumber>.Default value: 8005-J AO_WEBSERVER_SHUTDOWN_PORT=8005

-J AO_REPOSITORY_HOST Specifies the host name or IP address for the repository. The valuecannot be a loopback address.-J AO_REPOSITORY_HOST=<host>

-J AO_REPOSITORY_PORT Specifies the port used for the Access Manager login page. Theexpected value is <port number>.Default value: 8080-J AO_REPOSITORY_PORT=<port>

-JAO_REPOSITORY_PROTOCOL

Specifies the protocol used for the Access Manager login page.Default value: httpValid values: http or https.-J AO_REPOSITORY_PROTOCOL=<http or https>

-JAO_REPOSITORY_USER_NAME

Specifies the user name required to login. The default value is admin.The expected value is <CDP login name>.-J AO_REPOSITORY_USER_NAME=<username>

-JAO_REPOSITORY_PASSWORD

Specifies the password that corresponds to the user name. <password>.Note: The password value is encypted and is not stored in theinstallation log.-J AO_REPOSITORY_PASSWORD=<password>

BMC Atrium Orchestrator peers

AO_CDP_IS_PRIMARY Specifies whether the installation is for the initial CDP. If the CDP isnot primary, then the installation is HACDP.Valid values: true, false-J AO_CDP_IS_PRIMARY=true

AO_JAVA_HOME Specifies the path to the Java VM. The expected value is a path, such as /Java/jre6/bin/java.exe.-J AO_JAVA_HOME=<file path>

The following is an example of the AO_JAVA_HOME property.-J AO_JAVA_HOME=C:/Program Files/Java/jre6/bin/java.exe



Note: BMC Atrium Orchestrator only supports Java VM 1.6_16. Allother versions are not supported.

AO_PEER_NAME Specifies the name of the CDP. The expected value is <a name>.Default value: CDP1-J AO_PEER_NAME=CDP1

AO_CERT_PRINCIPAL Specifies if the certificate principal is the owner of the license. Theexpected value is a company name.-J AO_CERT_PRINCIPAL=My Company Name

AO_CERT_PASSWORD Specifies a password that is at least six characters in length.-J AO_CERT_PASSWORD=mypassword

AO_PEER_COMM_PORT Specifies the grid peer communications port number.Default value: 8081-J AO_PEER_COMM_PORT=8081

AO_WEBSERVER_PORT Specifies the port number for the web sever. The expected value is<port number>.Default value: 8080-J AO_WEBSERVER_PORT=8080

AO_WEBSERVER_SHUTDOWN_PORT

Specifies the web server shut down port. This property is usedinstalling a web server. The expected value is <port number>. Thedefault value is 8005.-J AO_WEBSERVER_SHUTDOWN_PORT=8005

BMC Atrium Orchestrator Operator Control Panel

AO_OCP_DEPLOYMENT_CONTEXT

This is an optional property used to specify the web context for theBMC Atrium Orchestrator Operator Control Panel. This property isused in the URL when launching BMC Atrium OrchestratorGridManager.Default values: baoocpSample property specifying web context for a OCP-J AO_OCP_DEPLOYMENT_CONTEXT=baoocp

Graphing Server

AO_GRAPH_DEPLOYMENT_CONTEXT

This is an optional property used to specify the web context for thegraphing server. This property is used in the URL when launching thegraphing server.-J AO_GRAPH_DEPLOYMENT_CONTEXT=baograph

AO_GRAPH_SERVER_HOST Specifies the host name or IP address of the graphing server.-J AO_GRAPH_SERVER_HOST=172.21.126.144



AO_GRAPH_SERVER_PORT Specifies the port number for the graphing server. The expected valueis <port number>.-J AO_GRAPH_SERVER_PORT=8080

Peer configuration

AO_PEER_NET_CONFIG_CDP_HOST

Specifies the host name or IP address of the CDP.-J AO_PEER_NET_CONFIG_CDP_HOST=<Host name or IP address>

AO_PEER_NET_CONFIG_CDP_PORT

Specifies the web communication port for the CDP. The expectedvalue is <port number>.-J AO_PEER_NET_CONFIG_CDP_PORT=8080

AO_PEER_NET_CONFIG_CDP_USER

Specifies the user name required to login. The default value is admin.The expected value is <CDP login name>.-J AO_PEER_NET_CONFIG_CDP_USER=admin

AO_PEER_NET_CONFIG_CDP_PASSWORD

Specifies the password that corresponds to the user name. Theexpected value is <password>.Default value: admin123Note: The password value is encypted and is not stored in theinstallation log.-J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123

AO_PEER_NET_CONFIG_CDP_CONTEXT

Specifies the peer URL application context. The default value isbaocdp. The expected value is <peer context>.-J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp

AO_PEER_NET_CONFIG_GRID_NAME

Specifies the name of the grid to join. The expected value is <gridname>.Default value: GRID1-J AO_PEER_NET_CONFIG_GRID_NAME=GRID1

AO_PEER_NET_CONFIG_PEER_NAME

Specifies the name of the CDP. The expected value is <peer name>.-J AO_PEER_NET_CONFIG_PEER_NAME=CDP1

AO_PEER_NET_CONFIG_NEW_PEER_NAME

Specifies the name of the new peer to install. The expected value is<peer name>.-J AO_PEER_NET_CONFIG_NEW_PEER_NAME=AP1

AO_PEER_NET_CONFIG_PROTOCOL

Specifies the protocol. The valid values are http or https.Valid values: http, httpsDefault value: http-J AO_PEER_NET_CONFIG_PROTOCOL=http

Note: Only set the value to https if you have configured the webserver container for SSL.

Peer-to-CDP or OCP-to-CDP communication validation



AO_PEER_NET_CONFIG_VALIDATE

The default value is true, which enables the silent installer to test thepeer-to-CDP or OCP-to-CDP communication configuration. Tocontinue the installation without validating the peer communicationconfigurations, change the value to false in the options file.-J AO_PEER_NET_CONFIG_VALIDATE=true

Content installationYou must install a CDP prior to content installation. The installation target path must contain a CDPinstallation.

AO_INSTALLING_FEATURES= Used with the content installer. This property specifies to install allcontent for BMC Atrium Orchestrator. This property does not work forsolution installation, where you must provide the name of the solution . -J AO_INSTALLING_FEATURES=ALL

To specify the adapter set to install use one of the following values:

■ ALL - installs all base and application adapters

■ BASE - installs all base adapters and does not include anyapplication adapters

■ APP - installs all application adapters; does not include base adapters

-J AO_INSTALLING_FEATURES=APP,adapter-http,adapter-jms

To specify the module set to install use one of the following values:

■ ALL - installs all platform and task management modules

■ PLAT - installs all platform modules

■ TASK - installs all task management modules; does not includeplatform modules

-J AO_INSTALLING_FEATURES=ALL

-J AO_INSTALLING_FEATURES=PLAT

-J AO_INSTALLING_FEATURES=TASK

BMC Atrium Orchestrator Development Studio

AO_DEVSTUDIO_WORKSPACE_DIR

Specifies the workspace folder path. This is the folder where BMCAtrium Orchestrator Development stores your work.-J AO_DEVSTUDIO_WORKSPACE_DIR=<file path> c:\DevStudioWork


Sample options filesThis section contains sample options files that demonstrate the silent installation ofBMC Atrium Orchestrator Access Manager, repository, configuration distributionpeer, BMC Atrium Orchestrator Operator Control Panel, graphing server, BMCAtrium Orchestrator Development Studio, and content. You can use the options fileto install BMC Atrium Orchestrator on additional peers. If you use the options filefor additional installations, you may need to edit the properties to meet therequirements for that server.

Best practice To ensure a successful installation, BMC Software recommends that you use anoptions file in conjunction with the silent installer and that you logon as anadministrator on the computer on which you are installing the product.

Note The following options files contain sample values. You must provide the actualvalues for your system in the options file you create. When installing content, theinstallation path must contain a CDP installation. You must install the CDP prior toinstalling content.

Platform silent installation options file

################################################################################# Options File##Product Name: BMC Atrium Orchestrator#Product Version: 7.6.00##Invoke the installer in silent mode with an options file:##1. Create a text file called BAOoptions.txt#2. Use the installation worksheets in the Installation Guide as a guide for# setting the options. Remove the comment markers (#) from the options you# want to include.#3. Run the installer with the -i silent option.# On Microsoft Windows, enter:# # On Red Hat Linux or Sun Solaris, enter:################################################################################################################################################################## New Installation Features## The following features correspond to the feature selection tree in the installer.## --New installation feature selection# |--Access Manager and Repository# |--Access Manager Only# |--Repository Only# |--Configuration Distribution Peer# | |--Operator Control Panel# | |--Graphing Components

Sample options files


# |--Activity Peer# | |--Operator Control Panel# | |--Graphing Components# |--Lightweight Activity Peer# |--Operator Control Panel# | |--Graphing Components# |--Graphing Server################################################################################################################################################################### Feature Installation order# You cannot install all components at one time. You will need to run the installer# multiple times to complete the platform installation.# 1. BMC Atrium Orchestrator Access Manager# 2. Repository# 3. Configuration distribution peer# a. BMC Atrium Orchestrator Operator Control Panel# b. Graphing server# 4. BMC Atrium Orchestrator Development Studio# 5. Content# 6. Optional components# a. Activity peer (AP)# 1. BMC Atrium Orchestrator Operator Control Panel# 2. Graphing server# b. Lightweight activity peer (LAP)# c. High availability configuration distribution peer (HACDP)# d. BMC Atrium Orchestrator Operator Control Panel# e. Graphing server################################################################################# Product Install Location## Use the -P option to specify a valid directory into which the product should# be installed, and use the -J options to specify Java properties.## -P installLocation=/opt/bmc/bao/am# -P installLocation=/Applications/bmc/ao/repo# -P installLocation=/opt/bmc/ao/cdp# -P installLocation=/opt/bmc/ao/cdp,OCP,GRAPH## Installation type specification to install new features#-J AO_INSTALL_TYPE=install_new# # Installation type specification to upgrade version 7.6.00 by# adding features or updating features#-J AO_INSTALL_TYPE=upgrade_new## Installation type specification to upgrade version 7.5.00 to# version 7.6.00#-J AO_INSTALL_TYPE=upgrade_new## ########################################################################################################################################## BMC Atrium Orchestrator Access Manager installation properties# This command installs BMC Atrium Orchestrator Access Manager only.## -J AO_INSTALLING_FEATURES=AM# # This command installs BMC Atrium Orchestrator Access Manager and# the repository,



## -J AO_INSTALLING_FEATURES=AM,REPO# # needs to be replaced with the AM hostname or IP#-J AO_SECURITY_COMM_HOST=<host name or IP address>#-J AO_SECURITY_COMM_PORT=61616#-J AO_SECURITY_COMM_PROTOCOL=<ssl, http, https>#-J AO_SECURITY_WEB_PORT=8080#-J AO_SECURITY_WEB_PROTOCOL=<http, https>#-J AO_CERT_PASSWORD=ABC123#-J AO_CERT_PRINCIPAL=ABC Software#-J AO_ENVIRONMENT_NAME=ENV1#-J AO_START_SERVER_ON_SUCCESS=<true, false>#-J AO_WEBSERVER_PORT=8080#-J AO_WEBSERVER_SHUTDOWN_PORT=8005#-J AO_WEBSERVER_SSL_ENABLED=<true or false>############################################################################################################################################ Repository properties# To install reposiory with BMC Atrium Orchestrator Access Manager,# add these properties and the BMC Atrium Orchestrator Access Manager# properties.## To install the repository separately, use this property with the# AO_WEBSERVER and AO_SECURITY properties listed above to the# repository options listed below.## -J AO_INSTALLING_FEATURES=REPO## Repository options##-J AO_REPOSITORY_HOST=<host>#-J AO_REPOSITORY_PORT=<port>#-J AO_REPOSITORY_PROTOCOL=<http or https> #-J AO_REPOSITORY_USER_NAME=<username> #-J AO_REPOSITORY_PASSWORD=<password>#-J AO_REPOSITORY_URL=http://<Host name or IP address>:<port>/baorepo############################################################################################################################################# Configuration Distribution peer properties### To install the CDP, first install BMC Atrium Orchestrator Access# Manager and repository. Use these properties with the AO_WEBSERVER,# AO_SECURITY, and AO_REPOSITORY properties listed above.## -J AO_INSTALLING_FEATURES=CDP## To install the CDP with OCP and Graphing server, first install# BMC Atrium Orchestrator Access Manager and repository. Use this# command with the AO_WEBSERVER, AO_SECURITY, and AO_REPOSITORY# properties listed above and the BMC Atrium Orchestrator Operator# Control Panel and Graphing server properties listed below.## -J AO_INSTALLING_FEATURES=CDP,OCP,GRAPH## CDP options# #-J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp#-J AO_CDP_IS_PRIMARY=true#-J AO_PEER_NAME=CDP#-J AO_PEER_NET_CONFIG_CDP_HOST=<Host name or IP address> #-J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123



#-J AO_PEER_NET_CONFIG_CDP_PORT=<default of 8080 or port number>#-J AO_PEER_NET_CONFIG_CDP_USER=<default of admin or user name>#-J AO_PEER_NET_CONFIG_GRID_NAME=<default of GRID1 or grid name>#-J AO_PEER_NET_CONFIG_PEER_NAME=<default of CDP1 or peer name>#-J AO_PEER_NET_CONFIG_PROTOCOL=<http, https>############################################################################################################################################### BMC Atrium Orchestrator Operator Control Panel properties## To install the BMC Atrium Orchestrator Operator Control Panel,# first install BMC Atrium Orchestrator Access Manager, repository,# and CDP.# Use the AO_WEBSERVER, AO_SECURITY, and # AO_REPOSITORY, and AO_PEER_NET_CONFIG properties listed above and# the BMC Atrium Orchestrator Operator Control Panel options listed# below.##-J AO_INSTALLING_FEATURES=OCP,WEBSERVER## BMC Atrium Orchestrator Operator Control Panel options################################################################################################################################################ Graphing server properties # # To install the BMC Atrium Orchestrator graphing server,# first install BMC Atrium Orchestrator Access Manager, repository,# and CDP. Use the AO_WEBSERVER, AO_SECURITY,# AO_REPOSITORY, and AO_PEER_NET_CONFIG properties listed above and# the graphing options listed below.# Replace the sample values with the Graphing Engine hostname or IP.# #-J AO_GRAPH_SERVER_HOST=<host name or IP address>#-J AO_GRAPH_SERVER_PORT=<default of 8080 or port number>#-J AO_PEER_COMM_PORT=<default of 8081 or port number>############################################################################################################################################### Activity peer properties### To install the BMC Atrium Orchestrator Activity peer,# first install BMC Atrium Orchestrator Access Manager, repository,# and CDP.# Use the AO_WEBSERVER, AO_REPOSITORY, and AO_PEER_NET_CONFIG# properties listed above and the activity peer options listed below.# Replace the values in this example.## -P installLocation=C:\Program Files\BMC Software\AO\AP# -J AO_INSTALL_TYPE=install_new# -J AO_INSTALLING_FEATURES=AP,WEBSERVER# -J AO_WEBSERVER_PORT=8080 -J AO_WEBSERVER_SHUTDOWN_PORT=8005# -J AO_START_SERVER_ON_SUCCESS=false# -J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp# -J AO_PEER_NET_CONFIG_CDP_HOST=172.21.126.144# -J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123# -J AO_PEER_NET_CONFIG_CDP_PORT=8080# -J AO_PEER_NET_CONFIG_CDP_USER=admin# -J AO_PEER_NET_CONFIG_GRID_NAME=GRID1# -J AO_PEER_NET_CONFIG_PEER_NAME=CDP1# -J AO_PEER_NET_CONFIG_NEW_PEER_NAME=AP1



# -J AO_PEER_NET_CONFIG_PROTOCOL=http###########################################################################

Options file to install BMC Atrium Orchestratorplatform

################################################################################# Options File##Product Name: BMC Atrium Orchestrator#Product Version: 7.6.00##Invoke the installer in silent mode with an options file:##1. Create a text file called BAOoptions.txt#2. Use the installation worksheets in the Installation Guide as a guide for# setting the options. Remove the comment markers (#) from the options you# want to include.#3. Run the installer with the -i silent option.# On Microsoft Windows, enter:# # On Red Hat Linux or Sun Solaris, enter:################################################################################################################################################################## New Installation Features## The following features correspond to the feature selection tree in the installer.## --New installation feature selection# |--Access Manager and Repository# |--Access Manager Only# |--Repository Only# |--Configuration Distribution Peer# | |--Operator Control Panel# | |--Graphing Components# |--Activity Peer# | |--Operator Control Panel# | |--Graphing Components# |--Lightweight Activity Peer# |--Operator Control Panel# | |--Graphing Components# |--Graphing Server################################################################################################################################################################### Feature Installation order# You cannot install all components at one time. You will need to run the installer# multiple times to complete the platform installation.# 1. BMC Atrium Orchestrator Access Manager# 2. Repository# 3. Configuration distribution peer# a. BMC Atrium Orchestrator Operator Control Panel# b. Graphing server# 4. BMC Atrium Orchestrator Development Studio



# 5. Content# 6. Optional components# a. Activity peer (AP)# 1. BMC Atrium Orchestrator Operator Control Panel# 2. Graphing server# b. Lightweight activity peer (LAP)# c. High availability configuration distribution peer (HACDP)# d. BMC Atrium Orchestrator Operator Control Panel# e. Graphing server################################################################################# Product Install Location## Use the -P option to specify a valid directory into which the product should# be installed, and use the -J options to specify Java properties.## -P installLocation=/opt/bmc/bao/am# -P installLocation=/Applications/bmc/ao/repo# -P installLocation=/opt/bmc/ao/cdp# -P installLocation=/opt/bmc/ao/cdp,OCP,GRAPH## Installation type specification to install new features#-J AO_INSTALL_TYPE=install_new# # Installation type specification to upgrade version 7.6.00 by# adding features or updating features#-J AO_INSTALL_TYPE=upgrade_new## Installation type specification to upgrade version 7.5.00 to# version 7.6.00#-J AO_INSTALL_TYPE=upgrade_new## ########################################################################################################################################## BMC Atrium Orchestrator Access Manager installation properties# This command installs BMC Atrium Orchestrator Access Manager only.## -J AO_INSTALLING_FEATURES=AM# # This command installs BMC Atrium Orchestrator Access Manager and# the repository, ## -J AO_INSTALLING_FEATURES=AM,REPO# # needs to be replaced with the AM hostname or IP#-J AO_SECURITY_COMM_HOST=<host name or IP address>#-J AO_SECURITY_COMM_PORT=61616#-J AO_SECURITY_COMM_PROTOCOL=<ssl, http, https>#-J AO_SECURITY_WEB_PORT=8080#-J AO_SECURITY_WEB_PROTOCOL=<http, https>#-J AO_CERT_PASSWORD=ABC123#-J AO_CERT_PRINCIPAL=ABC Software#-J AO_ENVIRONMENT_NAME=ENV1#-J AO_START_SERVER_ON_SUCCESS=<true, false>#-J AO_WEBSERVER_PORT=8080#-J AO_WEBSERVER_SHUTDOWN_PORT=8005#-J AO_WEBSERVER_SSL_ENABLED=<true or false>############################################################################################################################################ Repository properties# To install reposiory with BMC Atrium Orchestrator Access Manager,# add these properties and the BMC Atrium Orchestrator Access Manager# properties.



## To install the repository separately, use this property with the# AO_WEBSERVER and AO_SECURITY properties listed above to the# repository options listed below.## -J AO_INSTALLING_FEATURES=REPO## Repository options##-J AO_REPOSITORY_HOST=<host>#-J AO_REPOSITORY_PORT=<port>#-J AO_REPOSITORY_PROTOCOL=<http or https> #-J AO_REPOSITORY_USER_NAME=<username> #-J AO_REPOSITORY_PASSWORD=<password>#-J AO_REPOSITORY_URL=http://<Host name or IP address>:<port>/baorepo############################################################################################################################################# Configuration Distribution peer properties### To install the CDP, first install BMC Atrium Orchestrator Access# Manager and repository. Use these properties with the AO_WEBSERVER,# AO_SECURITY, and AO_REPOSITORY properties listed above.## -J AO_INSTALLING_FEATURES=CDP## To install the CDP with OCP and Graphing server, first install# BMC Atrium Orchestrator Access Manager and repository. Use this# command with the AO_WEBSERVER, AO_SECURITY, and AO_REPOSITORY# properties listed above and the BMC Atrium Orchestrator Operator# Control Panel and Graphing server properties listed below.## -J AO_INSTALLING_FEATURES=CDP,OCP,GRAPH## CDP options# #-J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp#-J AO_CDP_IS_PRIMARY=true#-J AO_PEER_NAME=CDP#-J AO_PEER_NET_CONFIG_CDP_HOST=<Host name or IP address> #-J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123#-J AO_PEER_NET_CONFIG_CDP_PORT=<default of 8080 or port number>#-J AO_PEER_NET_CONFIG_CDP_USER=<default of admin or user name>#-J AO_PEER_NET_CONFIG_GRID_NAME=<default of GRID1 or grid name>#-J AO_PEER_NET_CONFIG_PEER_NAME=<default of CDP1 or peer name>#-J AO_PEER_NET_CONFIG_PROTOCOL=<http, https>############################################################################################################################################### BMC Atrium Orchestrator Operator Control Panel properties## To install the BMC Atrium Orchestrator Operator Control Panel,# first install BMC Atrium Orchestrator Access Manager, repository,# and CDP.# Use the AO_WEBSERVER, AO_SECURITY, and # AO_REPOSITORY, and AO_PEER_NET_CONFIG properties listed above and# the BMC Atrium Orchestrator Operator Control Panel options listed# below.##-J AO_INSTALLING_FEATURES=OCP,WEBSERVER## BMC Atrium Orchestrator Operator Control Panel options#



############################################################################################################################################### Graphing server properties # # To install the BMC Atrium Orchestrator graphing server,# first install BMC Atrium Orchestrator Access Manager, repository,# and CDP. Use the AO_WEBSERVER, AO_SECURITY, and # AO_REPOSITORY, and AO_PEER_NET_CONFIG properties listed above and# the graphing options listed below.3 Replace the sample values with the Graphing Engine hostname or IP.# #-J AO_GRAPH_SERVER_HOST=<host name or IP address>#-J AO_GRAPH_SERVER_PORT=<default of 8080 or port number>#-J AO_PEER_COMM_PORT=<default of 8081 or port number>############################################################################################################################################### Activity peer properties### To install the BMC Atrium Orchestrator Activity peer,# first install BMC Atrium Orchestrator Access Manager, repository,# and CDP.# Use the AO_WEBSERVER, AO_SECURITY, and AO_REPOSITORY, and AO_PEER_NET_CONFIG# properties listed above and the activity peer options listed below.# Replace the values in this example.## -P installLocation=C:\Program Files\BMC Software\AO\AP# -J AO_INSTALL_TYPE=install_new# -J AO_INSTALLING_FEATURES=AP,WEBSERVER# -J AO_WEBSERVER_PORT=8080 -J AO_WEBSERVER_SHUTDOWN_PORT=8005# -J AO_START_SERVER_ON_SUCCESS=false# -J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp# -J AO_PEER_NET_CONFIG_CDP_HOST=172.21.126.144# -J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123# -J AO_PEER_NET_CONFIG_CDP_PORT=8080# -J AO_PEER_NET_CONFIG_CDP_USER=admin# -J AO_PEER_NET_CONFIG_GRID_NAME=GRID1# -J AO_PEER_NET_CONFIG_PEER_NAME=CDP1# -J AO_PEER_NET_CONFIG_NEW_PEER_NAME=AP1# -J AO_PEER_NET_CONFIG_PROTOCOL=http#

Options file to install BMC Atrium OrchestratorAccess Manager

#Install BMC Atrium Orchestrator Access Manager features in a managed web server.#Replace the values in this example.-P installLocation=/opt/bmc/bao/am-J AO_INSTALL_TYPE=install_new-J AO_INSTALLING_FEATURES=AM Feeds to be replaced with the AM hostname or IP-J AO_SECURITY_COMM_HOST=<host name or IP address>-J AO_SECURITY_COMM_PORT=61616-J AO_SECURITY_COMM_PROTOCOL=<ssl, http, https>-J AO_SECURITY_WEB_PORT=8080-J AO_SECURITY_WEB_PROTOCOL=<http, https>-J AO_CERT_PASSWORD=ABC123



-J AO_CERT_PRINCIPAL=ABC Software-J AO_ENVIRONMENT_NAME=ENV1-J AO_START_SERVER_ON_SUCCESS=<true, false>-J AO_WEBSERVER_PORT=8080-J AO_WEBSERVER_SHUTDOWN_PORT=8005-J AO_WEBSERVER_SSL_ENABLED=<true or false>

Options file to install the repository

#You must provide actual values.-P installLocation=/Applications/bmc/ao/repo-J AO_REPOSITORY_HOST=<host or IP address>-J AO_REPOSITORY_PORT=<port>-J AO_REPOSITORY_PROTOCOL=<http or https> -J AO_REPOSITORY_USER_NAME=<username> -J AO_REPOSITORY_PASSWORD=<password>-J AO_REPOSITORY_URL=http://<Host name or IP address>:<port>/baorepo-J AO_SECURITY_COMM_HOST=<BMC Atrium Orchestrator Access Manager host name or IP address>-J AO_SECURITY_COMM_PORT=<BMC Atrium Orchestrator Access Manager communications port>-J AO_SECURITY_COMM_PROTOCOL=<BMC Atrium Orchestrator Access Manager communications protocol>-J AO_SECURITY_WEB_PORT=<BMC Atrium Orchestrator Access Manager web port>-J AO_SECURITY_WEB_PROTOCOL=<BMC Atrium Orchestrator Access Manager web protocol>-J AO_WEBSERVER_SSL_ENABLED=<Value from BMC Atrium Orchestrator Access Manager installation>-J AO_WEBSERVER_PORT=<Value from BMC Atrium Orchestrator Access Manager installation>-J AO_WEBSERVER_SHUTDOWN_PORT=<Value from BMC Atrium Orchestrator Access Manager installation>

Options file to install a configuration distributionpeer with a graphing server and BMC AtriumOrchestrator Operator Control Panel

# The values in the options files are sample values.#You must replace the sample values with actual values.# Configuration Distribution peer installation. # Replace sample values with the CDP hostname or IP#-P installLocation=/opt/bmc/ao/cdp#-J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp#-J AO_CDP_IS_PRIMARY=true#-J AO_PEER_NAME=CDP#-J AO_PEER_NET_CONFIG_CDP_HOST=<Host name or IP address> #-J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123#-J AO_PEER_NET_CONFIG_CDP_PORT=<default of 8080 or port number>#-J AO_PEER_NET_CONFIG_CDP_USER=<default of admin or user name>#-J AO_PEER_NET_CONFIG_GRID_NAME=<default of GRID1 or grid name>#-J AO_PEER_NET_CONFIG_PEER_NAME=<default of CDP1 or peer name>#-J AO_PEER_NET_CONFIG_PROTOCOL=<http, https>## You must provide the BMC Atrium Orchestrator Access Manager information#-J AO_SECURITY_COMM_HOST=<BMC Atrium Orchestrator Access Manager host name or IP address>#-J AO_SECURITY_COMM_PORT=<BMC Atrium Orchestrator Access Manager communications port>



#-J AO_SECURITY_COMM_PROTOCOL=<BMC Atrium Orchestrator Access Manager communications protocol>#-J AO_SECURITY_WEB_PORT=<BMC Atrium Orchestrator Access Manager web port>#-J AO_SECURITY_WEB_PROTOCOL=<BMC Atrium Orchestrator Access Manager web protocol>#-J AO_WEBSERVER_SSL_ENABLED=<Value from BMC Atrium Orchestrator Access Manager installation>#-J AO_WEBSERVER_PORT=<Value from BMC Atrium Orchestrator Access Manager installation>#-J AO_WEBSERVER_SHUTDOWN_PORT=<Value from BMC Atrium Orchestrator Access Manager installation># BMC Atrium Orchestrator Operator Control Panel installation## Graphing server information. Replace the sample values with the# Graphing Engine hostname or IP.#-J AO_GRAPH_SERVER_HOST=<host name or IP address>#-J AO_GRAPH_SERVER_PORT=<default of 8080 or port number>#-J AO_PEER_COMM_PORT=<default of 8081 or port number>

Options file to install BMC Atrium OrchestratorDevelopment Studio

Note The silent installer does not install BMC Atrium Orchestrator Development Studioon Mac OS.

#Replace the values in this example.-P installLocation=c:\program files\bmc\ao\Studio-J AO_INSTALL_TYPE=install_new-J AO_DEVSTUDIO_WORKSPACE_DIR=c:\DevStudioWork

Options file to install a CDP#To install the CDP you must provide the BMC Atrium Orchestrator Access Manager system information.-P installLocation=/Applications/BMC/AO/-J AO_INSTALL_TYPE=install_new-J AO_INSTALLING_FEATURES=CDP-J AO_CDP_IS_PRIMARY=true-J AO_CERT_PASSWORD=-J AO_CERT_PRINCIPAL=My Company Name-J AO_ENVIRONMENT_NAME=ENV1-J AO_START_SERVER_ON_SUCCESS=false-J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp-J AO_PEER_NAME=CDP1-J AO_SECURITY_COMM_HOST=<BMC Atrium Orchestrator Access Manager host name or IP address>-J AO_SECURITY_COMM_PORT=<BMC Atrium Orchestrator Access Manager communications port>-J AO_SECURITY_COMM_PROTOCOL=<BMC Atrium Orchestrator Access Manager communications protocol>-J AO_SECURITY_WEB_PORT=<BMC Atrium Orchestrator Access Manager web port>-J AO_SECURITY_WEB_PROTOCOL=<BMC Atrium Orchestrator Access Manager web protocol>-J AO_WEBSERVER_SSL_ENABLED=<Value from BMC Atrium Orchestrator Access Manager installation>-J AO_WEBSERVER_PORT=<Value from BMC Atrium Orchestrator Access Manager



installation>-J AO_WEBSERVER_SHUTDOWN_PORT=<Value from BMC Atrium Orchestrator Access Manager installation>-J AO_PEER_COMM_PORT=<port number>-J AO_WEBSERVER_DETECTED_OLD_SETTINGS=false-J AO_REPOSITORY_HOST=<Host name or IP address>-J AO_REPOSITORY_PORT=<Value from repository installation>-J AO_REPOSITORY_PROTOCOL=<Value from repository installation>-J AO_REPOSITORY_USER_NAME=<Value from repository installation>-J AO_REPOSITORY_PASSWORD=<Value from repository installation>-J AO_REPOSITORY_URL=<Value from repository installation>

Options file to install an AP#Replace the values in this example.-P installLocation=C:\Program Files\BMC Software\AO\AP -J AO_INSTALL_TYPE=install_new -J AO_INSTALLING_FEATURES=AP,WEBSERVER -J AO_WEBSERVER_PORT=8080 -J AO_WEBSERVER_SHUTDOWN_PORT=8005 -J AO_START_SERVER_ON_SUCCESS=false -J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp -J AO_PEER_NET_CONFIG_CDP_HOST=172.21.126.144 -J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123 -J AO_PEER_NET_CONFIG_CDP_PORT=8080 -J AO_PEER_NET_CONFIG_CDP_USER=admin -J AO_PEER_NET_CONFIG_GRID_NAME=GRID1 -J AO_PEER_NET_CONFIG_PEER_NAME=CDP1 -J AO_PEER_NET_CONFIG_NEW_PEER_NAME=AP1 -J AO_PEER_NET_CONFIG_PROTOCOL=http

Options file to install BMC Atrium OrchestratorOperator Control Panel and graphing server to anexisting AP#Replace the values in this example.-P installLocation=C:\Program Files\BMC Software\AO\AP-J AO_INSTALL_TYPE=upgrade_new-J AO_INSTALLING_FEATURES=AP,WEBSERVER,OCP,GRAPH-J AO_WEBSERVER_PORT=8080-J AO_WEBSERVER_SHUTDOWN_PORT=8005-J AO_START_SERVER_ON_SUCCESS=false-J AO_PEER_NET_CONFIG_CDP_HOST=172.21.126.144-J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123-J AO_PEER_NET_CONFIG_CDP_PORT=8080-J AO_PEER_NET_CONFIG_CDP_USER=admin-J AO_PEER_NET_CONFIG_GRID_NAME=GRID1-J AO_PEER_NET_CONFIG_PEER_NAME=CDP1-J AO_PEER_NET_CONFIG_NEW_PEER_NAME=AP1-J AO_PEER_NET_CONFIG_PROTOCOL=http

Content silent installation

################################################################################# Options File##Product Name: BMC Atrium Orchestrator#Product Version: 7.6.00#



#Invoke the installer in silent mode with an options file:##1. Create a text file called BAOoptions.txt#2. Use the installation worksheets in the Installation Guide as a guide for# setting the options. Remove the comment markers (#) from the options you# want to include.#3. Run the installer with the -i silent option. ## On Microsoft Windows, enter:# sh ./content_installer.bin -i silent-DOPTIONS_FILE=/home/bmcuser/content.options## On Red Hat Linux or Sun Solaris, enter:# content_installer.exe -i silent -DOPTIONS_FILE=# "C:\Program Files\BAO\BAOcontent.options"################################################################################################################################################################## New Installation Features## The following features correspond to the feature selection tree in the installer.#################################################################################### Product Install Location## Use the -P option to specify a valid directory into which the product should# be installed, and use the -J options to specify Java properties. The # installation target directory must contain a CDP.## Red Hat Linux example# -P installLocation=/opt/bmc/bao/cdp## Microsoft Windows example# -P installLocation=C:\Program Files\BMC Software\AO\CDP############################################################################### Installation type# There are two types of installations solution or custom. The BMC Atrium # Orchestrator Installation Guide uses the custom type to install content.## -J AO_CONTENT_INSTALL_TYPE=INSTALL_TYPE_CUSTOM############################################################################### Feature selections#



Options file to install selected base adapters Note

The installation path must contain a CDP installation.

-P installLocation=/opt/bmc/ao/cdp-J AO_INSTALLING_FEATURES=adapter-http,adapter-jms,adapter-powershell,adapter-windows-command

Options file to install all base adapters Note


-P installLocation=/opt/bmc/ao/cdp-J AO_INSTALLING_FEATURES=BASE

Options file to install the feature set for allapplication adapters

Note The installation path must contain a CDP installation.

-P installLocation=C:\Program Files\BAO\CDP-J AO_INSTALLING_FEATURES=APP

Options file to install all application adapters Note


-P installLocation=C:\Program Files\AO\CDP-J AO_INSTALLING_FEATURES=ALL

Options file to install selected adapters Note


-P installLocation=C:\Program Files\AO\CDP-J AO_INSTALLING_FEATURES=APP-J AO_INSTALLING_FEATURES=adapter-email,adapter-http,adapter-jms,adapter-snmp,



adapter-windows-command,adapter-ws, adapter-active-directory,adapter-ars,adapter-bmc-atrium-cmdb

Options file to install selected modules Note


-P installLocation=/Applications/bmc/ao/cdp-J AO_INSTALLING_FEATURES=AutoPilot-AD-Utilities,AutoPilot-OA-Applications_Utilities,AutoPilot-OA-Common_Utilities,AutoPilot-OA-Directory_Services_Utilities,AutoPilot-OA-File_Utilities,AutoPilot-OA-Network_Utilities,AutoPilot-OA-Operating_System_Utilities

Options file to install run books Does anyone have asample? No idea how to do this.

Note The installation path must contain a CDP installation.

-P installLocation=C:\BMC\AO\CDP-J AO_INSTALLING_FEATURES=FullStackServerProvisioning-J AO_CONTENT_INSTALL_TYPE=INSTALL_TYPE_SOLUTIONS-J INSTALL_REMEDY_ITSM_INTEGRATIONS=true-J REMEDY_PORT_NUMBER=3005-J REMEDY_USER_NAME=Demo-J REMEDY_HOSTNAME=vlm-vm22-J REMEDY_PASSWORD=<password>-J ITSM_AUTHORING_COMPANY=MyCompany-J ITSM_AUTHORING_ORGANIZATION=Org Two-J ITSM_AUTHORING_GROUP=Group1

Creating an options fileThe silent installer options file is a simple text file that defines the requiredproperties for the installation in the form of a prefix tag followed by a key-value pair.It is not required to use an options file with the silent installer. For a single serverplatform installation, you will need to run the installer at least two times to completethe installation of BMC Atrium Orchestrator including BMC AtriumOrchestratorAccess Manager, the repository, a configuration distribution peer, BMCAtrium Orchestrator Operator Control Panel and a graphing server.

To create the options file

1 Open a text editor.

Creating an options file


This sample options file installs BMC Atrium Orchestrator Access Manager andrepository-P installLocation=/Applications/BMC/AO/7600-J AO_INSTALL_TYPE=install_new-J AO_INSTALLING_FEATURES=,AM,REPO,WEBSERVER-J AO_SECURITY_COMM_HOST=SILVERBUG-J AO_SECURITY_COMM_PORT=61616-J AO_SECURITY_COMM_PROTOCOL=ssl-J AO_SECURITY_WEB_PORT=8080-J AO_SECURITY_WEB_PROTOCOL=http-J AO_WEBSERVER_SSL_ENABLED=false-J AO_WEBSERVER_PORT=8080-J AO_WEBSERVER_SHUTDOWN_PORT=8005-J AO_WEBSERVER_DETECTED_OLD_SETTINGS=false-J AO_REPOSITORY_HOST=SILVERBUG-J AO_REPOSITORY_PORT=8080-J AO_REPOSITORY_PROTOCOL=http-J AO_REPOSITORY_USER_NAME=admin-J AO_REPOSITORY_PASSWORD=-J AO_CDP_IS_PRIMARY=true-J AO_CERT_PASSWORD=-J AO_CERT_PRINCIPAL=My Company Name-J AO_ENVIRONMENT_NAME=ENV1-J AO_START_SERVER_ON_SUCCESS=false-J AO_OCP_DEPLOYMENT_CONTEXT=baoocp-J AO_GRAPH_DEPLOYMENT_CONTEXT=baograph-J AO_PEER_NAME=CDP1-J AO_PEER_COMM_PORT=28081

Note In the options file, you must specify a valid directory in which to install BMCAtrium Orchestrator.

2 Make the first property in the options file the installation directory.-P installLocation=/Applications/BMC/AO/7600

-P installLocation=C:\Program Files\AO\CDP

3 Make the second property the installation type. You have installation choices of:install_new; upgrade_new.

Installation property type Description

install_new Specifies that this is a new BMC Atrium Orchestratorinstallation.

upgrade_new Specifies that this is an adds new features to a BMCAtrium Orchestrator version 7.6.00 or upgradesversion 7.5.00 to version 7.6.00

-J AO_INSTALL_TYPE=<install_new, upgrade_new>

4 Add properties to install. See “Silent installation properties” on page 64

Creating an options file


Note BMC Atrium Orchestrator Access Manager must be the first component installed.You must install the repository with BMC Atrium Orchestrator Access Manageror after BMC Atrium Orchestrator Access Manager. You can install the CDP onlyafter installing BMC Atrium Orchestrator Access Manager and the repository.

5 Save the file with a name that indicates the purpose of the installationbao.options. For example, if you create an options file to install BMC AtriumOrchestrator Access Manager and the repository, you could name the options filebaoAM_REPO.options

6 To use the options file with the installer, specify the exact path to the options filein the installer command.

This example launches the silent installer and uses the options filebaoAM_REPO.options located in the /home/bmcuser/ directory.sh ./ao_installer.bin -i silent -DOPTIONS_FILE=/home/bmcuser/baoAM_REPO.options

Executing a silent installationThe silent installer is run from the command line and does not prompt for input. OnRed Hat Linux or Sun Solaris operating systems, you can output debug logging tothe console window by exporting LAX_DEBUG=true. You use the same command tolaunch the silent installer for all components. The options file controls whatcomponent is installed and its properties.

To run the silent installer

Best practice To ensure a successful installation, BMC Software recommends that you use anoptions in conjunction with the silent installer.

1 From the command line, execute the installer with the following command:

For Red Hat Linux and Sun Solaris operating systems, type the followingcommand in the console.

sh ./bao_platform_installer_7_6_00_00.bin -I silent -DOPTIONS_FILE=/<home>/<bmcuser>/<baoAM.options>

Executing a silent installation


Sample installation commands for Red Hat Linux or Sun Solaris. The option filename indicates the component being installed.sh ./bao_base_platform_7.6.00_installer.bin -I silent -DOPTIONS_FILE=/home/bmcuser/baoCDP.optionssh ./bao_platform_7.6.00_installer.bin -I silent -DOPTIONS_FILE=/home/bmcuser/baoAM.optionssh ./bao_studio_7.6.00_installer.bin -I silent -DOPTIONS_FILE=/home/bmcuser/devstudio.optionssh ./bao_content_7.6.00_installer.bin -I silent -DOPTIONS_FILE=/home/bmcuser/content.options

For Windows type the following command at the command prompt.bao_platform_installer_7_6_00_00.exe -I silent -DOPTIONS_FILE="C:\Documents andSettings\<user name>\Desktop\<baoAM.options>"

Note You must give a full path to the options file or it will not be processed.

You must install BMC Atrium Orchestrator Access Manager prior to all othercomponents.

Since the installer executes without prompts, use the following steps to verify thesuccess of the silent installation:

■ Launch the application.

■ Verify the information in the installation log files. On Red Hat Linux or SunSolaris, the installation log is in the /tmp directory. On Windows, the installationlog file is usually located in the C:\Documents and Settings\<user name>\LocalSettings\Temp directory. The log file name matches the name of the productinstaller. For example, the platform installation log is named BAO_install_log.txt,the BMC Atrium Orchestrator Development Studio log file would beBAO_studio_install_log.txt. The BAO_install_log.txt file contains the CDP,repository, and BMC Atrium Orchestrator Access Manager installation information.

■ Look for the expected file and structure folder on the system.

Silent installation upgradeYou can upgrade BMC Atrium Orchestrator using the silent installation method. Theupgrade procedure varies depending on the BMC Atrium Orchestrator installed inyour environment.

Silent installation upgrade


Determine the upgrade roadmap

When you upgrade to BMC Atrium Orchestrator 7.6.00 your environment receivesan updated CDP, BMC Atrium Orchestrator Access Manager, and a new feature, therepository. Unlike previous versions, BMC Atrium Orchestrator 7.6.00 requires thatthe CDP and BMC Atrium Orchestrator reside separately from one another. Thisnew configuration requires attention to detail during the upgrade process. Whenyou upgrade from an environment that has BMC Atrium Orchestrator AccessManager and the configuration distribution in the same instance, the installer createsa new BMC Atrium Orchestrator Access Manager and you must manually copy thefiles from the old directory to the new directory.

Upgrading the BMC Atrium Orchestrator solution is a multiple-step process.Complete the installation steps in the order presented in this document.

■ Install a new BMC Atrium Orchestrator Access Manager and the repository.

— Do not start the server when the installation completes.

■ Run the installer to upgrade the CDP from version 7.5.00 to version 7.6.00. Ensurethat the BMC Atrium Orchestrator Access Manager host and port settings point tothe new installation of BMC Atrium Orchestrator Access Manager.

— Do not start the CDP when the installation completes.

■ Copy the am folder in the CDP installation directory to the directory of the newBMC Atrium Orchestrator Access Manager.

■ Examine the contents of the am directory. Delete the file am.ks if it is in the directory.

■ Start the BMC Atrium Orchestrator Access Manager and repository server.

■ Launch BMC Atrium Orchestrator Access Manager.

■ Start the BMC Atrium Orchestrator Configuration Distribution Peer server.

■ Launch BMC Atrium Orchestrator Grid Manager to verify the CDP installation.

Note If you have customized server.sh or BMC Atrium Orchestrator.lax, the installer willrename the existing file to server.sh.bk or BMC Atrium Orchestrator.lax.bk andcreate a new file. You will need to re-apply the customization to the file after theupgrade process completes.



Using the silent installer to upgrade

This section describes how use the silent installer to install or upgrade or add newfeatures. The silent installer is run from the command line and does not prompt forinput. On Red Hat Linux or Sun Solaris operating systems, you can output debuglogging to the console window by exporting LAX_DEBUG=true. You use the samecommand to launch the silent installer for all components. The options file controlswhat component is installed and its properties.

Before you begin

Please review the system requirements section to ensure your server complies. Youmust be logged on as an administrator and have administrator rights on thecomputer where you will install BMC Atrium Orchestrator.

To use the silent installer to upgrade from a CDP only installation to a singleserver installation

1 Create an options file and install one of the following:

a BMC Atrium Orchestrator Access Manager and the repository together.

b BMC Atrium Orchestrator Access Manager only.

Do not start the BMC Atrium Orchestrator Access Manager server during theupgrade.

2 If you installed the repository with BMC Atrium Orchestrator Access Manager,skip to step 3, otherwise create an options and run the silent installer to installrepository only.

Do not start the BMC Atrium Orchestrator Repository server during the upgrade.

3 Copy the contents of the BMC Atrium Orchestrator 7.5.00 Access Manager folderto the directory containing BMC Atrium Orchestrator 7.6.00 Access Manager andrepository. If you do not have a previous installation BMC Atrium OrchestratorAccess Manager, go to step 4.

4 Create an options file and upgrade the CDP. Ensure that the options file providesthe information required for communication to the BMC Atrium OrchestratorAccess Manager and repository. You can choose to install some optionalcomponents with the CDP.

Do not start the new BMC Atrium Orchestrator Configuration Distribution serverduring the upgrade.



a If you need to upgrade the BMC Atrium Orchestrator Operator Control Paneladd the options to the options file.

b If you need to upgrade the graphing server add the options to the options file.

5 Start the BMC Atrium Orchestrator Access Manager server, or the BMC AtriumOrchestrator Access Manager and Repository server.

6 Start the BMC Atrium Orchestrator Repository server, if not started already.

7 Start the BMC Atrium Orchestrator Configuration Distribution Peer server.





Silent installation verification











BMC Atrium Orchestrator GUIinstaller upgrade

The upgrade procedure for BMC Atrium Orchestrator version 7.6.00 involvesinstalling a new BMC Atrium Orchestrator Access Manager and repository and thenupgrading the CDP. If you have an existing BMC Atrium Orchestrator AccessManager, you will need to copy files to the new BMC Atrium Orchestrator AccessManager directory. For BMC Atrium Orchestrator version 7.6.00, BMC AtriumOrchestrator Access Manager and the repository are components available tomultiple grids, they are not grid components and you must install BMC AtriumOrchestrator Access Manager and the repository separately from the CDP.

Upgrade steps

Upgrading the BMC Atrium Orchestrator solution is a multiple-step process.Complete the installation steps in the order presented in this document.

1 Install one of the following, a new:

■ BMC Atrium Orchestrator Access Manager only.

■ BMC Atrium Orchestrator Access Manager and the repository.

■ Do not start the BMC Atrium Orchestrator Access Manager server when theinstallation completes.

2 Install the repository, if not installed with new BMC Atrium Orchestrator AccessManager.

■ Do not start the new BMC Atrium Orchestrator Repository server.

3 Run the installer to upgrade the CDP from version 7.5.00 to version 7.6.00. Ensurethat the BMC Atrium Orchestrator Access Manager host and port settings point tothe new installation of BMC Atrium Orchestrator Access Manager. You mustinclude the repository settings also.

6

Chapter 6 BMC Atrium Orchestrator GUI installer upgrade 91

■ If the BMC Atrium Orchestrator version 7.5.00 included the BMC AtriumOrchestrator Operator Control Panel or the graphing server you can upgradethem with the CDP.

■ Do not start the CDP when the installation completes.

4 Copy the am folder in the CDP installation directory to the directory of the newBMC Atrium Orchestrator Access Manager.

5 Examine the contents of the am directory. Delete the file am.ks if it is in the directory.

6 Start the BMC Atrium Orchestrator Access Manager and repository server.

7 Launch BMC Atrium Orchestrator Access Manager.

8 Start the BMC Atrium Orchestrator Configuration Distribution Peer server.

9 Launch BMC Atrium Orchestrator Grid Manager to verify the CDP installation.

Note If you have customized server.sh or BMC Atrium Orchestrator.lax, the installer will rename theexisting file to server.sh.bk or BMC Atrium Orchestrator.lax.bk and create a new file. You willneed to re-apply the customization to the file after the upgrade process completes.

Upgrade worksheetsThe following worksheet lists the parameters that you need to provide during theBMC Atrium Orchestrator upgrade. The worksheet includes default parametervalues where applicable.

To prepare for the upgrade, print a copy of the worksheet and record the parametervalues for your site in the column to the right. If defaults appear in this column, youcan use them or record the values you enter. Review the worksheet during theupgrade process.

To upgrade the platform note the settings

1 Installation type

2 Default destination directory

3 Web Server settings

a HTTP port (8080)

Upgrade worksheets


b Shutdown port (8085)

c Deployment Server Type settings

d Select a web server deployment folder

4 CDP installations: Configuration Distribution Peer Settings

a CDP is (primary (not HA))

b Environment name (ENV1)

c Peer name (CDP1)

d Certificate holder name (My Company Name)

e Certificate holder password

f Peer communications port (8081)

5 AP or LAP installations: Peer to CDP Communication Settings

a Protocol (http)

b CDP user name (admin)

c CDP password

d CDP ip address

e CDP http port (8080)

f CDP web context (baocdp)

g Grid name (GRID1)

h This peer’s name

1 AP1 (default if installing an AP)

2 LAP1 (default if installing an LAP)

i Platform installation log file location

6 OCP installations: OCP to CDP Communication Settings

a Protocol (http)

Upgrade worksheets


b CDP ip address

c CDP http port (8080)

d CDP web context (baocdp)

e Grid name (GRID1)

7 Access Manager Communication Settings

a Host name or ip

b Communications port (61616)

c Web server protocol (http)

d Web server port (8080)

e Platform installation log file location

To upgrade adapters

1 IDefault destination directory

2 BMC Atrium Orchestrator Adapters Selection, under the Application adapterssection (All Base adapters)

3 Adapter installation log file location

To upgrade modules

1 Default destination directory

2 BMC Atrium Orchestrator Modules Selection (all Utility modules)

3 Adapter installation log file location

To upgrade run books

1 Destination directory

2 BMC Atrium Orchestrator Run Books selection

3 Run books installation log file location

Upgrade worksheets


Worksheet for upgrading Development Studio

1 Installation type

2 Java VM

3 Destination directory (C:\Program Files\BMC Software\AO\Studio)

4 Directory to store your work (C:\Documents and Settings\username\DevStudio

5 Where would you like to create product icons? (In a new Program Group: BMC)

6 Create icons for all users (unchecked)

Upgrading the platformThe procedures in this section describe upgrading a BMC Atrium Orchestrator 7.5.00CDP only system to BMC Atrium Orchestrator 7.6.00 containing BMC AtriumOrchestrator Access Manager, the repository, and a CDP. Use the upgradeworksheets to record your system settings and as an aide during the upgradeprocess. You must run the installer at least two times to upgrade to BMC AtriumOrchestrator 7.6.00; the first time you install BMC Atrium Orchestrator AccessManager and the repository; the second time you run the installer to upgrade theCDP. If you install the repository separately from BMC Atrium Orchestrator AccessManager, then you will need to run the installer three times to install BMC AtriumOrchestrator Access Manager, the repository and the CDP.BMC Atrium Orchestrator 7.5.00 installed all components in the same directory andBMC Atrium Orchestrator Access Manager was an optional feature. In BMC AtriumOrchestrator 7.6.00, BMC Atrium Orchestrator Access Manager and the repositoryare required. These components must reside apart from the CDP, which is installedin its own directory.

Note You must be logged in as an administrator and have administrator rights for themachine that contains the CDP.

To upgrade the platform

1 Install BMC Atrium Orchestrator Access Manager and the repository, see “Installing BMC Atrium Orchestrator Access Manager and the repository” onpage 25 or “Installing BMC Atrium Orchestrator Access Manager only” on page28 and “Installing the repository only” on page 32.

2 Run the installer again to upgrade the CDP.

Upgrading the platform




5 On the Installation Type panel, select Upgrade or add features to existingOrchestrator; then click Next.

6 On the Directory selection panel:

■ Click Next to accept the default directory location.

■ Provide a directory in which to install BMC Atrium Orchestrator then clickNext.

7 Select the CDP as the feature to upgrade; then click Next.

Note You have an option to upgrade BMC Atrium Orchestrator Operator Control Paneland the graphing server with the CDP.

8 On the Choose Java Virtual Machine panel select the Java VM 1.6_16 directory.


9 If you choose to install BMC Atrium Orchestrator Operator Panel, the OCP toCDP Communications Settings panel is displayed. Enter the communicationsettings:




Grid Name GRID1

10 On the Access Manager Communications Settings panel, enter the BMC AtriumOrchestrator Access Manager host name or IP address and the communicationsport number; then click Next to proceed.

Upgrading the platform



11 On the Repository Communications Settings panel, enter the settings for therepository, host name or IP address, communications port number and webserver protocol; then click Next.

12 If you are not installing a graphing server, skip this panel. On Graphing ServerCommunications panel, if you want to install the graphing server, enter the hostname or IP address and the web server port number, then click Next.

Note

The Graphing Server Communications panel displays even if you do not select toinstall the graphing server.


13 When you have finished reviewing the installation preview, click Install.


15 When the installation finishes successfully, click Done.

Upgrading an activity peerThe procedures in this section describe upgrading a BMC Atrium Orchestratoractivity peer. You must be logged in as an administrator and have administratorrights for the machine that contains the AP.

To upgrade an AP


2 Upgrade the CDP.

Upgrading an activity peer


3 Run the installer to upgrade the AP.

Note When running the installation programs in Windows, the installer may displaythe following message instructing you to change your Windows computer tounrestricted mode.This machine has to be configured to allow running in unrestrictedmode.


Step 2: Add this application to DEP by clicking the Add button,and select path \<installation directory>\<installer file name>Select Apply. Select OK.

Step 3: Reboot.





■ Click Next to accept the directory location.

■ Provide a directory in which to upgrade BMC Atrium Orchestrator peer andthen click Next.

8 On the Upgrade existing installation features selection panel, you have an optionto upgrade the AP and the BMC Atrium Orchestrator Operator Control Panel andgraphing components on that peer. Select the options and then click Next.

a Click Next to upgrade the AP without options.

b If you want to upgrade the AP andBMC Atrium Orchestrator Operator ControlPanel and graphing components on the peer, select the options and click Next.

9 On the Choose Java Virtual Machine panel select the Java VM 1.6_16 directory.




10 On the Peer to CDP Communications Settings panel:

■ Check the Test peer configuration connection box to test the settings




Web Server Protocol HTTP

CDP user name

CDP password

CDP IP address

CDP HTTP port The port provided when the CDP was installed








Grid Name GRID1

12 On the Access Manager Communications Settings panel, enter the BMC AtriumOrchestrator Access Manager host name or IP address and the communicationsport number; then click Next to proceed.


13 If you selected to install the graphing component, on Graphing ServerCommunications panel, enter the host name or IP address and the web serverport number, then click Next.



Note


14 When you have finished reviewing the installation preview, click Install.


16 When the installation finishes successfully, click Done.

Upgrading a lightweight activity peerUse these steps to upgrade a lightweight activity peer. You must be logged in as anadministrator and have adminstrator rights for the machine on which you install theLAP.

To upgrade a LAP


2 Upgrade the CDP.

3 Navigate to and then run the installer to upgrade the LAP.



Step 2: Add this application to DEP by clicking the Add button,and select path \<installation directory>\<installer name> SelectApply. Select OK.

Step 3: Reboot.

Upgrading a lightweight activity peer




6 On the Directory selection panel, if the directory displayed on the panel is correctclick Next, or provide an upgrade location and click Next.

7 On the Upgrade existing installation features selection panel, LightweightActivity Peer is selected; click Next.

8 On the Choose Java Virtual Machine panel, select the directory that contains JavaVM 1.6_16; then click Next.


9 Review the information on the installation preview panel. When you havefinished reviewing the preinstallation summary, click Install.



Upgrading a high availability configurationdistribution peer

At installation, the high availability configuration distribution peer (HACDP)searches for and uses the CDP, BMC Atrium Orchestrator Access Manager, and therepository configuration information. You must install or upgrade BMC AtriumOrchestrator Access Manager, the repository, and CDP prior to installing the HACDP.

To upgrade a HACDP


2 Upgrade the CDP.

Upgrading a high availability configuration distribution peer


3 Run the installer to upgrade the AP.



Step 2: Add this application to DEP by clicking the Add button,and select path \<installation directory>\<installer file name>Select Apply. Select OK.

Step 3: Reboot.


5 On the Installation Type panel select Upgrade or add features to an existingOrchestrator and click Next.


■ Click Next to accept the directory location.

■ Provide a directory in which to upgrade BMC Atrium Orchestrator peer andthen click Next.

7 On the Upgrade existing installation features selection panel, you have an optionto upgrade the CDP and theBMC Atrium Orchestrator Operator Control Paneland graphing components on that peer. Select the options and then click Next.

a Click Next to upgrade the HACDP without options.

b If you want to upgrade the HACDP and the BMC Atrium OrchestratorOperator Control Panel and graphing components on the peer, select theoptions and click Next.

8 On the Choose Java Virtual Machine panel select the Java VM 1.6_16 for BMCAtrium Orchestrator to use.








10 On the Configuration Distribution Peer Settings panel, click CDP is secondary(HA) and click Next.

Tip If you cannot remember the CDP communiction settings, you can find the settingsin the bao.options file.

11 On the Peer to CDP Communications settings panel, provide the communicationsettings:

Peer to CDP Communication settings Default value


CDP User Name admin

CDP Password

CDP IP Address

CDP Web Server Port Number 8080

CDP Web Context baocdp

This Peer's Name CDP2





Grid Name GRID1



13 On the Access Manager Communications Settings panel enter values in the HostName or IP Address and the Communications Port Number click Next .

Tip If you cannot remember your settings, open the bao.options file to see the settingused during the BMC Atrium Orchestrator Access Manager installation.



Note You can enter settings to direct the CDP to a different repository, then click Next.


15 On the Graphing Server Communications panel, enter the host name or IPaddress and the web server port number, then click Next.

Note If you are not installing a graphing server, skip this panel.You can enter settings to direct the CDP to a different repository, then click Next.













Upgrading BMC Atrium OrchestratorDevelopment Studio

BMC recommends that you upgrade the CDP prior to upgrading BMC AtriumOrchestrator Development Studio. You must be logged in as an administrator andhave adminstrator rights on the computer on which you upgrade Development Studio.

To upgrade BMC Atrium Orchestrator Development Studio in Windows

1 Navigate to and then run the installer.

Note The BMC Atrium Orchestrator Development Studio installer might display thefollowing message instructing you to change your computer to unrestricted mode.This machine has to be configured to allow running in unrestrictedmode.


Step 2: Add this application to DEP by clicking the Add button,and select path \Installers\bao_devstudio_installer_7_6_00.exe.Select Apply. Select OK.

Step 3: Reboot.

Upgrading BMC Atrium Orchestrator Development Studio



3 In the Installation Type panel, select Upgrade an exisitng Development Studio;then click Next.

4 In the Choose Java Virtual Machine panel, select the Java VM; then click Next.

Note Development Studio requires Java VM 1.6_16.

5 In the Directory selection panel click Nextto select the destination directory.

If the correct directory is not displayed enter or browse to the correct directoryand then click Next.

6 In the Workspace Location panel, click Next to use the default directory or select aworking directory where you will store your work and click Next.

7 In the Choose Shortcut Folder panel, select where you want to create producticons. If you want icons for all users, click the Create Icons for All Userscheckbox; then click Next.

8 In the Installation preview panel, review the summary and click Install.

9 In the Installation summary panel, you can click View Logto view the install logfile BAO_studio_install_log.txt or select Done to exit the installer.


To ensure the installation is successful, launch BMC Atrium OrchestratorDevelopment Studio.

Updating BMC Atrium Orchestrator contentBMC recommends that you upgrade the CDP prior to content. Your existing contentis not altered, newer versions are added to the installation. BMC AtriumOrchestrator version 7.6.00 maintains the existing versions of workflow. If youattempt to run BMC Atrium Orchestrator version 7.5.00 workflow, you will beprompted to update the workflow. Content resides in the repository however thetarget directory for the content must contain a CDP.

Updating BMC Atrium Orchestrator content


Before you begin

You must be logged in as an administrator and have adminstrator rights on thecomputer on which you install content.

To update content with the GUI installer

1 Navigate to and then run the installer.

Note The BMC Atrium Orchestrator Development Studio installer might display thefollowing message instructing you to change your computer to unrestricted mode.This machine has to be configured to allow running in unrestrictedmode.


Step 2: Add this application to DEP by clicking the Add button,and select path \Installers\bao_devstudio_installer_7_6_00.exe.Select Apply. Select OK.

Step 3: Reboot.

2 On the computer where you want to install the BMC Atrium Orchestratorcontent, extract the installer zip file to a temporary directory.

3 Navigate to and then run the 7.6.00_bao_content_installer file.

Note On Windows machines, the installer might display the following messageinstructing you to change your computer to unrestricted mode.This machine has to be configured to allow running in unrestrictedmode.


Step 2: Add this application to DEP by clicking the Add button,and select path \Installers\AO_Installers_7.6.00\7.6.00_bao_content_installer.exe. SelectApply. Select OK.

Step 3: Reboot.


5 On the BMC Atrium Orchestrator License Agreement panel, select I accept theterms of the License Agreement; then click Next.



6 On the Directory selection panel, click Next to accept the default installation path,or browse to select a different CDP folder.

The target path for the content must contain a CDP. You install content onto a CDP.

7 On the Installation Type panel select Custom feature set, and click Next.

Note If you select existing application adapters or base adapters, they will be updatedto the current version.

8 On the Adapter feature selection panel select the adapters you want to install orupdate and click Next.

If you click the Adapters check box then you select all adapters. If you select theBase Adapters, BMC application adapters or Third party adapters check box,then you select all the adapters in that group.

9 On the Module feature selection panel select the run books and managementmodules and core modules you want to install or update and click Next.

If you click the Modules check box then you select all modules. If you select theRun books, Management modules or Core modules check box, then you selectall the adapters in that group.

10 On the Installation preview panel review the features. When you have finishedreviewing the summary, click Install.

11 After the installation finishes successfully, click Done.


To ensure the installation is successful, launch BMC Atrium Orchestrator GridManager.



Troubleshooting and log filesLog files are the one of the primary methods used to troubleshoot issues in BMCAtrium Orchestrator. When you contact BMC Customer Support for help with anissue, BMC Customer Support will request specific log files like the grid.log, catalinalogs, or processes.log. BMC Atrium Orchestratoruses log files to record grid, process,configuration, and installation information. Log files are stored in the BMC AtriumOrchestrator home directory, the tomcat directory, or the directory where you storeBMC Atrium Orchestrator Development Studio information. The most importantlogs for installation troubleshooting are the install logs and the grid.log. The grid.logis essential for troubleshooting BMC Atrium Orchestrator.There are many logging levels that are described in the BMC Atrium OrchestratorSystem Administration Guide. By default logging levels are set to WARN and thesamples in this section describes the WARN logging level. The log files recordinformation in chronological order within the file. The log file name matches thename of the component installer.

Log file names and locations

File Location Description

grid.log $AO_HOME/tomcat/logs

BMC Atrium Orchestrator creates the grid.log file created shortlyafter the peer is started for the first time. If a peer is running forfive minutes, and this file does not appear, then there is probablysomething wrong with the default logging, or someone haschanged the logging configuration. This is the most important logfile that BMC Atrium Orchestrator generates.If you report an issue, it is useful to have an excerpt of this log,starting from the point that the process started, to the point thatthe failure occurred.

processes.log $AO_HOME/tomcat/logs

Contains logging generated by BMC Atrium Orchestratorworkflow.

catalina.logs $AO_HOME/tomcat/logs

Contains log messages on actions by the container actions onstartup and shutdown, and any actions taken to load a webapplication.

am.log $AO_HOME/am/logs Contains logging information for BMC Atrium OrchestratorAccess Manager.

repository.log $AO_HOME/repository/logs

Contains logging information for the repository.

7

Chapter 7 Troubleshooting and log files 109

File Location Description

aoocp.log $AO_HOME/tomcat/logs

Contains logging information for BMC Atrium OrchestratorOperator Control Panel.

Installation logs If the Installation is successful,BMC Atrium Orchestrator copiesinstaller logs to the installation target folder. However, if theinstallation is not successful, the Installation log file stays in thetemporary directories.

Platforminstaller logs

BAO_install_log.txt

DevelopmentStudio installer

BAO_studio.txt

Contentinstaller

BAO_content.txt When you install a solution, the content installer creates BMCRemedy logs in the <install folder>/import-logs directory.

Viewing logs using the GUI installer

If you are using the GUI installers, the installation summary panel displays the logfile location. You can read the log in a graphical log viewer from this panel byclicking View Log.The log displays entries in a table format, which can be sortedbased on any column. To sort entries by ascending order, click the column heading.Sort the entries in descending order by holding Shift while clicking once on thecolumn heading. Each installation instance is logged in a separate tab, with the mostrecent installation displayed first. The log displays information events, configurationevents, warnings, and errors. Entry details appear in the lower section of the panel.

Viewing logs using the Maintenance Tool

The Maintenance Tool for any product can be found both on the installer's directoryand also within the < installation folder >MaintainBMCAO directory. TheMaintenance Tool provides a dashboard for all utilities that are delivered with BMCAtrium Orchestrator.

The Maintenance Tool for any product can be found both on the installer's directoryand also within the < installation folder >MaintainBMCAO directory. TheMaintenance Tool provides a dashboard for all utilities that are delivered with BMCAtrium Orchestrator.

You can use the Maintenance Tool to review logs or configuration parameters. Toview the logs from the Maintenance Tool, open the Maintenance Tool, select theLogs tab, and then select the log you want to view.

You can also use the Log Zipper utility to collect log files and operating systeminformation that can aid installation issue diagnosis. To access the Log Zipper, open


the Maintenance Tool, select the Logs tab. Click Zip Logs to save into thisinformation in a zip file, which can be sent to Customer Support if needed.

Installation log filesInstallation log files are the used to troubleshoot installation issues in BMC AtriumOrchestrator and it is essential to include them when you submit issues to BMCCustomer Support. To troubleshoot installation errors, you should review theinstallation logs for messages indicating components did not install or installed witherrors. Installation log files for each component are created during the installationprocess. You can view the installation log files in the log viewer when the installationprocess complete or in a text editor. The installation log files reside in the temporarydirectory created during installation. For example in windows the installation log filewould be in C:\Documents and Settings\<user name>\local settings\temp. Theinstallation logs are:

■ BAO_install_log.txt

■ BAO_studio_install_log.txt

■ BAO_content_install_log.txt

Log message format

The main log message types in the installation log are: LOG EVENT, PROGRESSEVENT, THROWABLE EVENT, and Summary section. The propertyFAILED_INSTALL_FEATURES lists features that failed during installation andprovides a reason for the failure. The general format of all the log messages is:

<time_of_event>,<severity_of_event>,<source_of_event>,<event_message_content> The text start of <event_message_content> indicates the type of message

Log file messages have the following severity levels: SEVERE, WARNING, INFO,CONFIG, FINE, FINER, FINEST. When you view the installation log file in the fileview the SEVERE level displays with a red highlight and WARNING log leveldisplays with a yellow highlight. The message below indicates a LOG EVENTmessage that happened at 1:10:28 AM with a severity level of CONFIG from a sourceclass InstallationTaskAction.

(Jul 17 2008 01:10:28 AM\-0500),CONFIG,com.bmc.install.builder.installanywhere.InstallationTaskAction,LOGEVENT{Description=\[CREATED

Installation log files


InstallationTask\],Detail=[com.bmc.install.product.arsuitekit.ARSuiteKitProjectInitializationInstallationTask\]

The table below describes the message types in the installation logs.

Log message types Description

LOG EVENT Records the installation properties settings, the start and end ofinstallation tasks and installation panels. The structure andcontent of the message is different on Windows, Mac, and Linuxor Solaris operating systems. Typcially, this information does notrequire further investigation.

PROGRESS EVENT Details how much of a task is completed. Typically, thisinformation does not require further investigation.

THROWABLE EVENT Records failures through the use of stack traces. If you receivethrowable events, contact BMC Customer Support.

Summary section This message type is displayed at the end of the log andprovides the data from the Installation Summary panel, forexample, messages indicating if the install was successful orunsuccessful. If the message indicates that the installation didnot succeed, then the Summary section describes whichcomponents failed to install. Information about componentinstallation failures is useful when contacting BMC CustomerSupport.

Installation log file examples

Installation log files


This is an example of install.log.txt from a Microsoft Windows installation.

Figure 3: Sample install.log.txt

Troubleshooting with the grid.log

BMC Atrium Orchestrator creates the grid.log file created shortly after the peer isstarted for the first time. If a peer is running for five minutes, and this file does notappear, then there is probably something wrong with the default logging, orsomeone has changed the logging configuration. This is the most important log filethat BMC Atrium Orchestrator generates. The grid.log file constantly receivesinformation and can became large. The once the file reaches 10 Mb the file is rolledover to a sequentially numbered file, grid#.log and a BMC Atrium Orchestratorcreates a new grid.log. The rolled over file, grid#.log no longer receives logginginformation. Over time, it is normal to see many grid#.log files in the [AO_HOME]/tomcat/logs directory

Troubleshooting with the grid.log


If you launch BMC Atrium Orchestrator Grid Manager and the web application doesnot display, you can open the grid.log in a text editor and review the file formessages that warrant attention.

Sample grid.log file

Figure 4: Grid.log file

Tomcat logs

Tomcat logging is useful when troubleshooting issues like the container fails to start,a web application does not seem to come up, or if the server crashes unexpectedly.Information about the failure may be logged in the catalina or the localhost logs.Tomcat is a servlet container. By default a Tomcat server is installed in the[PEER_HOME]/tomcat directory. Tomcat logs are recorded in the directory[PEER_HOME]/tomcat/logs.

Tomcat logs include:

■ admin.<date>.log

■ aoocp.log

■ catalina.<date>.log

■ grid.log

■ host-manager.<date>.log

■ localhost.<date>.log

■ manager.<date>.log

■ processes.log

Tomcat logs


catalina log

The catalina log contains log messages on actions by the container actions on startupand shutdown, and any actions taken to load a web application. The example belowshows a log message for a failure to start a web application are logged in the catalinalog.

SEVERE: Context [/aoam] startup failed due to previous error

Web contexts are used to identify the BMC Atrium Orchestrator applications in thecatalina log files. You will not see terms like CDP, Activity Peer, or Grid Manager.During installation you can specify alternate names for the web context and thecatalina log reflects the web contexts you provided during installation. The defaultweb context names are:

■ baocdp for a Configuration Distribution Peer (CDP)

■ baoap for an Activity Peer (AP)

■ baolap for a Lightweight Activity Peer (LAP)

■ baoam for Access Manager

■ baoocp for Operator Control Panel (OCP)

■ baograph for the Graphing server component

Sample localhost log

The localhost logs are used to troubleshoot startup and shutdown errors. Thelocalhost logs appear in the same directory as catalina logs. By default, the localhostlogs are logged with a date in the file name, for example: localhost.2008-12-12.log.

Sample catalina log file

Figure 5: Catalina.<yyyy-mm-dd>.log

Tomcat logs


Logging configuration files

BMC Atrium Orchestrator uses log4j logging framework. You can review thelogging properties for the components in these files.

This table shows where you can find the logging configuration files for eachcomponent. For server components the log paths in the table are given relative to[TOMCAT_HOME], and assume that the default context name is used. The path is[TOMCAT_HOME] is [AO_HOME]/tomcat.

WARNING Do not change the settings in the log4j files without assistance by BMC CustomerSupport. To adjust logging levels use BMC Atrium Orchestrator Grid Manager.

Component Configuration file

Development Studio [STUDIO_HOME]/log4j.xml

CDP, Grid Manager, ReportingJSP

webapps/baocdp/WEB-INF/classes/log4j.properties

AP webapps/baoap/WEB-INF/classes/log4j.properties

LAP webapps/baolap/WEB-INF/classes/log4j.properties

OCP webapps/baoocp/WEB-INF/classes/log4j.properties

Access Manager webapps/baoam/WEB-INF/classes/log4j.properties

Troubleshooting tips for starting the serverCommon troubleshooting steps when the server does not start.

1 Ensure you are using jvm 1.6_16.

2 Ensure you can communicate with the server, for example ping the server.

3 Ensure Java VM 1.6_16 is in the environment path.

Note If the Java VM 1.6_16 is not in the path then the server will not start.

4 Examine for port conflicts in the grid.log.

Logging configuration files


5 Examine the catalina out file for server errors.

6 Search for common peer startup messages like No store configured and ERRORmessages like java_bind which indicates that the port is already in use byanother application.

7 Ensure you installed BMC Atrium Orchestrator on a supported platform andoperating system.

Troubleshooting tips for starting the server


Troubleshooting tips for starting the server


AppendixThis appendix describes optional procedures to configure the BMC AtriumOrchestrator product.

Platform silent installation options fileBMC Software recommends that you use an options file with the silent installer. Youmust run the silent install in the proper component installation order. You must belogged in as an administrator and have administrator rights for the computer onwhich you are installing the product. To use the options file, uncomment the lines,remove the (#) symbol, for the properties you need.


################################################################################# Options File##Product Name: BMC Atrium Orchestrator#Product Version: 7.6.00##Invoke the installer in sile mode with an options file:##1. Create a text file called BAOoptions.txt#2. Use the installation worksheets in the Installation Guide as a guide for# setting the options. Remove the comment markers (#) from the options you# want to include.#3. Run the installer with the -i silent option.# On Microsoft Windows, enter:# # On Red Hat Linux or Sun Solaris, enter:#################################################################################

################################################################################# New Installation Features## The following features correspond to the feature selection tree in the installer.## --New installation feature selection

A

Appendix A Appendix 119

# |--Access Manager and Repository# |--Access Manager Only# |--Repository Only# |--Configuration Distributution Peer# | |--Operator Control Panel# | |--Graphing Components# |--Activity Peer# | |--Operator Control Panel# | |--Graphing Components# |--Lightweight Activity Peer# |--Operator Control Panel# | |--Graphing Components# |--Graphing Server################################################################################################################################################################### Feature Installation order# You cannot install all components at one time. You will need to run the installer# multiple times to complete the platform installation.# 1. BMC Atrium Orchestrator Access Manager# 2. Repository# 3. Configuration distribution peer# a. BMC Atrium Orchestrator Operator Control Panel# b. Graphing server# 4. BMC Atrium Orchestrator Development Studio# 5. Content# 6. Optional components# a. Activity peer (AP)# 1. BMC Atrium Orchestrator Operator Control Panel# 2. Graphing server# b. Lightweight activity peer (LAP)# c. High availability configuration distribution peer (HACDP)# d. BMC Atrium Orchestrator Operator Control Panel# e. Graphing server################################################################################# Product Install Location## Use the -P option to specify a valid directory into which the product should# be installed, and use the -J options to specify Java properties.## -P installLocation=/opt/bmc/bao/am# -P installLocation=/Applications/bmc/ao/repo# -P installLocation=/opt/bmc/ao/cdp# -P installLocation=/opt/bmc/ao/cdp,OCP,GRAPH## Installation type specification to install new features#-J AO_INSTALL_TYPE=install_new# # Installation type specification to upgrade version 7.6.00 by# adding features or updating features#-J AO_INSTALL_TYPE=upgrade_new## Installation type specification to upgrade version 7.5.00 to# version 7.6.00#-J AO_INSTALL_TYPE=upgrade_old## ########################################################################################################################################## BMC Atrium Orchestrator Access Manager installation properities



# This command installs BMC Atrium Orchestrator Access Manager only.## -J AO_INSTALLING_FEATURES=AM# # This command installs BMC Atrium Orchestrator Access Manager and# the repository, ## -J AO_INSTALLING_FEATURES=AM,REPO# # needs to be replaced with the AM hostname or IP#-J AO_SECURITY_COMM_HOST=<host name or IP address>#-J AO_SECURITY_COMM_PORT=61616#-J AO_SECURITY_COMM_PROTOCOL=<ssl, http, https>#-J AO_SECURITY_WEB_PORT=8080#-J AO_SECURITY_WEB_PROTOCOL=<http, https>#-J AO_CERT_PASSWORD=ABC123#-J AO_CERT_PRINCIPAL=ABC Software#-J AO_ENVIRONMENT_NAME=ENV1#-J AO_START_SERVER_ON_SUCCESS=<true, false>#-J AO_WEBSERVER_PORT=8080#-J AO_WEBSERVER_SHUTDOWN_PORT=8005#-J AO_WEBSERVER_SSL_ENABLED=<true or false>############################################################################################################################################ Repository properties# To install reposiory with BMC Atrium Orchestrator Access Manager,# add these properties and the BMC Atrium Orchestrator Access Manager# properties.## To install the repository separately, use this property with the# AO_WEBSERVER and AO_SECURITY properties listed above to the# repository options listed below.## -J AO_INSTALLING_FEATURES=REPO## Repository options##-J AO_REPOSITORY_HOST=<host>#-J AO_REPOSITORY_PORT=<port>#-J AO_REPOSITORY_PROTOCOL=<http or https> #-J AO_REPOSITORY_USER_NAME=<username> #-J AO_REPOSITORY_PASSWORD=<password>#-J AO_REPOSITORY_URL=http://<Host name or IP address>:<port>/baorepo############################################################################################################################################# Configuration Distribution peer properties### To install the CDP, first install BMC Atrium Orchestrator Access# Manager and repository. Use these properties with the AO_WEBSERVER,# AO_SECURITY, and AO_REPOSITORY properties listed above.## -J AO_INSTALLING_FEATURES=CDP## To install the CDP with OCP and Graphing server, first install# BMC Atrium Orchestrator Access Manager and repository. Use this# command with the AO_WEBSERVER, AO_SECURITY, and AO_REPOSITORY# properties listed above and the BMC Atrium Orchestrator Operator# Control Panel and Graphing server properties listed below.## -J AO_INSTALLING_FEATURES=CDP,OCP,GRAPH## CDP options



# #-J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp#-J AO_CDP_IS_PRIMARY=true#-J AO_PEER_NAME=CDP#-J AO_PEER_NET_CONFIG_CDP_HOST=<Host name or IP address> #-J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123#-J AO_PEER_NET_CONFIG_CDP_PORT=<default of 8080 or port number>#-J AO_PEER_NET_CONFIG_CDP_USER=<default of admin or user name>#-J AO_PEER_NET_CONFIG_GRID_NAME=<default of GRID1 or grid name>#-J AO_PEER_NET_CONFIG_PEER_NAME=<default of CDP1 or peer name>#-J AO_PEER_NET_CONFIG_PROTOCOL=<http, https>############################################################################################################################################### BMC Atrium Orchestrator Operator Control Panel properties## To install the BMC Atrium Orchestrator Operator Control Panel,# first install BMC Atrium Orchestrator Access Manager, repository,# and CDP.# Use the AO_WEBSERVER, AO_SECURITY, and # AO_REPOSITORY, and AO_PEER_NET_CONFIG properties listed above and# the BMC Atrium Orchestrator Operator Control Panel options listed# below.##-J AO_INSTALLING_FEATURES=OCP,WEBSERVER## BMC Atrium Orchestrator Operator Control Panel options################################################################################################################################################ Graphing server properties # # To install the BMC Atrium Orchestrator graphing server,# first install BMC Atrium Orchestrator Access Manager, repository,# and CDP. Use the AO_WEBSERVER, AO_SECURITY, and # AO_REPOSITORY, and AO_PEER_NET_CONFIG properties listed above and# the graphing options listed below.# Replace the sample values with the Graphing Engine hostname or IP.# #-J AO_GRAPH_SERVER_HOST=<host name or IP address>#-J AO_GRAPH_SERVER_PORT=<default of 8080 or port number>#-J AO_PEER_COMM_PORT=<default of 8081 or port number>############################################################################################################################################### Activity peer properties### To install the BMC Atrium Orchestrator Activity peer,# first install BMC Atrium Orchestrator Access Manager, repository,# and CDP.# Use the AO_WEBSERVER, AO_SECURITY, and AO_REPOSITORY, and AO_PEER_NET_CONFIG# properties listed above and the activity peer options listed below.# Replace the values in this example.## -P installLocation=C:\Program Files\BMC Software\AO\AP# -J AO_INSTALL_TYPE=install_new# -J AO_INSTALLING_FEATURES=AP,WEBSERVER# -J AO_WEBSERVER_PORT=8080 -J AO_WEBSERVER_SHUTDOWN_PORT=8005# -J AO_START_SERVER_ON_SUCCESS=false# -J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp# -J AO_PEER_NET_CONFIG_CDP_HOST=172.21.126.144



# -J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123# -J AO_PEER_NET_CONFIG_CDP_PORT=8080# -J AO_PEER_NET_CONFIG_CDP_USER=admin# -J AO_PEER_NET_CONFIG_GRID_NAME=GRID1# -J AO_PEER_NET_CONFIG_PEER_NAME=CDP1# -J AO_PEER_NET_CONFIG_NEW_PEER_NAME=AP1# -J AO_PEER_NET_CONFIG_PROTOCOL=http########################################################################### ############################################################################# Lightweight peer properties# To install the BMC Atrium Orchestrator Ligthweight activity peer,# first install BMC Atrium Orchestrator Access Manager, repository,# and CDP.# Use the AO_WEBSERVER, AO_SECURITY, and AO_REPOSITORY, and AO_PEER_NET_CONFIG# properties listed above and the activity peer options listed below.# Replace the values in this example.## -P installLocation=C:\Program Files\BMC Software\AO\AP# -J AO_INSTALL_TYPE=install_new# -J AO_INSTALLING_FEATURES=AP,WEBSERVER# -J AO_WEBSERVER_PORT=8080 -J AO_WEBSERVER_SHUTDOWN_PORT=8005# -J AO_START_SERVER_ON_SUCCESS=false# -J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp# -J AO_PEER_NET_CONFIG_CDP_HOST=172.21.126.144# -J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123# -J AO_PEER_NET_CONFIG_CDP_PORT=8080# -J AO_PEER_NET_CONFIG_CDP_USER=admin# -J AO_PEER_NET_CONFIG_GRID_NAME=GRID1# -J AO_PEER_NET_CONFIG_PEER_NAME=CDP1# -J AO_PEER_NET_CONFIG_NEW_PEER_NAME=AP1# -J AO_PEER_NET_CONFIG_PROTOCOL=http########################################################################### # # High availablity configuration distribution peer## To install the BMC Atrium Orchestrator high availablity configuration distribution peer,# first install BMC Atrium Orchestrator Access Manager, repository,# and CDP.# Use the AO_WEBSERVER, AO_SECURITY, and AO_REPOSITORY, and AO_PEER_NET_CONFIG# properties listed above and the activity peer options listed below.# Replace the values in this example.##-J AO_PEER_NET_CONFIG_CDP_CONTEXT=baocdp#-J AO_CDP_IS_PRIMARY=false#-J AO_PEER_NAME=CDP#-J AO_PEER_NET_CONFIG_CDP_HOST=<Host name or IP address> #-J AO_PEER_NET_CONFIG_CDP_PASSWORD=admin123#-J AO_PEER_NET_CONFIG_CDP_PORT=<default of 8080 or port number>#-J AO_PEER_NET_CONFIG_CDP_USER=<default of admin or user name>#-J AO_PEER_NET_CONFIG_GRID_NAME=<default of GRID1 or grid name>#-J AO_PEER_NET_CONFIG_PEER_NAME=<default of CDP1 or peer name>#-J AO_PEER_NET_CONFIG_PROTOCOL=<http, https>########################################################################### #





Index

-P 82:installing

server in Linux or Solaris 37, 48, 59

Aabout

BMC Atrium Orchestrator 11logs 109Maintenance Tool 110options file 63silent installations 63

Access Manager and repository in the samedirectory 87

activity peer 14adapters

upgrading 61, 108AO_INSTALLING_FEATURES 64architecture overview 11

BBAO_content_install_log.txt 111BAO_install_log.txt 111BAO_studio_install_log.txt 111BMC Atrium Orchestrator

architecture 11installation logs 109

BMC Atrium Orchestrator Access Manager 12BMC Atrium Orchestrator Access Manager and

repository same directory upgrade 87BMC Atrium Orchestrator Access Manager launch

27, 31BMC Atrium Orchestrator Access Manager, verify

installation 27, 30BMC Atrium Orchestrator Development Studio 13BMC Atrium Orchestrator Grid Manager 13BMC Atrium Orchestrator Operator Control Panel

13

CCDP

only 34checklist

upgrade 91communication ports 22Component installation order 23configuration distribution peer 14Content installer 60Content Installer

BAO_content_install_log.txt 109installation logs 109

conventions, documentation 7

DDefault requirements 17Development Studio 13

BAO_studio.txt 109installation logs 109installing 59, 107new installation worksheet 58

Development studio, installing 59disk space

requirements 20

FFAILED_INSTALL_FEATURES 111feature selection

options file 64

GGraphing server and graphing components 14Graphing server, verify installation 42, 57GUI installation 25

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Index 125

GUI installerlogs 110

GUI installersupgrading with 91

Hhigh availability configuration distribution peer 48,

101high-availability configuration distribution peer 14

IIndex Term 23, 119install_new 63installation

HACDP 48, 101Lightweight Activity Peer (LAP) 43, 46repository 32worksheet 58

installation locationoptions file 82

installation log file examples 112Installation log files 111installation logs

BAO_content.txt 109BAO_install_log.txt 109BMC Atrium Orchestrator 109

installation typeoptions file 63

Installation, BMC Atrium Orchestrator AccessManager only 28

installingDevelopment Studio 59, 107silent 63

InstallingBMC Atrium Orchestrator Access Manager and

the repository 25CDP 34Content 60

Installing BMC Atrium Orchestrator AccessManager 28

Installing BMC Atrium Orchestrator OperatorControl Panel 51

installLocation 82

JJava VM requirements 17

LLaunch, BMC Atrium Orchestrator Access

Manager. 27, 31lightweight activity peer 14Log file messages 111Log message format 111Log Zipper 110log4j 116logging configuration files 116logs

about 109GUI installer 110viewing 110

MMaintenance Tool

about 110Log Zipper 110viewing logs 110

NNTP server 22

Ooptions file 82

-P 82about 63feature selection 64installation location 82installation type 63installLocation 82

Options file samples 69Options file to install a configuration distribution

peer with a graphing server and BMCAtrium Orchestrator Operator ControlPanel 77

Options file to install Access Manager 76Options file to install Access Manager and

repository 73Options file to install Development Studio and

Content 78Options file to install the repository 77



Pplatform installation examples of typical

installation 23platform installation methods 23ports

web server 22

RRed Hat Linux silent installation 84Repository 32requirements

disk space 20software 20

requirements, installation 20runtime requirements 20

SSample options file 69server

installing in Linux or Solaris 37, 48, 59Server, starting troubleshooting tips 117silent installation 84Silent installation options file 119silent installation verification 84silent installation, options file 82Silent installation, options file 119silent installation, run 84Silent installation, verifying 89silent installations 63

about 63silent upgrades 63software

requirements 20Software requirements 17Starting the server troubleshooting tips 117Sun Solaris silent installation 84synchronization 22syntax statement conventions 9System requirements 17

Ttime

synchronization 22To install a CDP in Windows 101To install a CDP only 34To install a HACDP 48

To install a LAP 100To install a LAP in Windows or Mac 46To install a repository 32To use the silent installer to upgrade 87To verify Access Manager installation 27, 31To verify the graphing server installation 42, 57Troubleshooting 109

grid.log 109Troubleshooting tips, starting the server 117

Uupgrade 92

silent 63worksheets 92

UpgradeLightweight Activity Peer (LAP) 100

Upgrade to same directory BMC AtriumOrchestrator Access Manager andrepository 87

upgrade_new 63upgrade_old 63upgrading

adapters 61, 108Development Studio 105in a Windows environment 95, 97using GUI installers 91

VVerifiy the BMC Atrium Orchestrator Access

Manager installation 27, 30Verify installation, graphing server 42, 57verify silent installation 84Verifying the graphing server installation 42, 57Verifying, silent installation 89viewing

logs 110viewing logs

Maintenance Tool 110

Wweb server

ports 22Windows

installing a CDP in a Windows environment 37installing a HACDP 101installing in a Lightweight Activity Peer (LAP)

43, 46Windows silent installation 84worksheets 92


Index 127

Zzip

logs 110



Third-party product terms

The following terms apply to third-party products that are included with or in a BMC Software product asdescribed in the BMC Software, Inc., License Agreement that is applicable to the product.

ANTLR License

Copyright (c) 2005, Terence Parr

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted providedthat the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and thefollowing disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.

Neither the name of the author nor the names of its contributors may be used to endorse or promoteproducts derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSSOF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVENIF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Eclipse Public License

Short description for the concept topic.

This product may be distributed with one or more of the following software applications licensed under theEclipse Public License Version 1.0 ("EPL"): (collectively the "EPL Software"). A copy of the EPL is included inthe documentation for this BMC product. The terms and conditions of the BMC software agreementapplicable to this product do not apply to the EPL Software. For and on behalf of any and all "Contributors"to the EPL Software (as defined in the EPL), all warranties and conditions of the BMC software agreement,express and implied, including but not limited to warranties or conditions of title and non-infringement andimplied warranties or conditions of merchantability and fitness for a particular purpose, are expresslydisclaimed. None of the Contributors to the EPL Software shall be liable for any damages, including direct,indirect, special, incidental and consequential damages, such as lost profits, with respect to the EPLSoftware. The terms and conditions of the BMC software agreement applicable to this BMC product areoffered by BMC alone and not by any other party. Upon written request, BMC or its designee will provideunder the terms of the EPL a copy of the source code of any EPL Software distributed with this BMCproduct along with a copy of the EPL; such requests should identify the EPL Software with particularity,should specifically state that source code for that software is requested, and should be sent postage paid tothe following address: BMC Software, Inc. 2101 CityWest Blvd., Houston, TX 77042.

Eclipse Public License - v 1.0

THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLICLICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAMCONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.

1. DEFINITIONS

"Contribution" means:

a) in the case of the initial Contributor, the initial code and documentation distributed under thisAgreement, and

b) in the case of each subsequent Contributor:

i) changes to the Program, and

ii) additions to the Program;

where such changes and/or additions to the Program originate from and are distributed by that particularContributor. A Contribution 'originates' from a Contributor if it was added to the Program by suchContributor itself or anyone acting on such Contributor's behalf. Contributions do not include additions tothe Program which: (i) are separate modules of software distributed in conjunction with the Program undertheir own license agreement, and (ii) are not derivative works of the Program.

"Contributor" means any person or entity that distributes the Program.

"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by theuse or sale of its Contribution alone or when combined with the Program.

"Program" means the Contributions distributed in accordance with this Agreement.

"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.

2. GRANT OF RIGHTS

a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive,worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display,publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivativeworks, in source code and object code form.

b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive,worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import andotherwise transfer the Contribution of such Contributor, if any, in source code and object code form. Thispatent license shall apply to the combination of the Contribution and the Program if, at the time theContribution is added by the Contributor, such addition of the Contribution causes such combination to becovered by the Licensed Patents. The patent license shall not apply to any other combinations which includethe Contribution. No hardware per se is licensed hereunder.

c) Recipient understands that although each Contributor grants the licenses to its Contributions set forthherein, no assurances are provided by any Contributor that the Program does not infringe the patent orother intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipientfor claims brought by any other entity based on infringement of intellectual property rights or otherwise. Asa condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes soleresponsibility to secure any other intellectual property rights needed, if any. For example, if a third partypatent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility toacquire that license before distributing the Program.

d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, ifany, to grant the copyright license set forth in this Agreement.

3. REQUIREMENTS

A Contributor may choose to distribute the Program in object code form under its own license agreement,provided that:

a) it complies with the terms and conditions of this Agreement; and

b) its license agreement:

i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied,including warranties or conditions of title and non-infringement, and implied warranties or conditions ofmerchantability and fitness for a particular purpose;

ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect,special, incidental and consequential damages, such as lost profits;

iii) states that any provisions which differ from this Agreement are offered by that Contributor alone andnot by any other party; and

iv) states that source code for the Program is available from such Contributor, and informs licensees how toobtain it in a reasonable manner on or through a medium customarily used for software exchange.

When the Program is made available in source code form:

a) it must be made available under this Agreement; and

b) a copy of this Agreement must be included with each copy of the Program.

Contributors may not remove or alter any copyright notices contained within the Program.

Each Contributor must identify itself as the originator of its Contribution, if any, in a manner thatreasonably allows subsequent Recipients to identify the originator of the Contribution.

4. COMMERCIAL DISTRIBUTION

Commercial distributors of software may accept certain responsibilities with respect to end users, businesspartners and the like. While this license is intended to facilitate the commercial use of the Program, theContributor who includes the Program in a commercial product offering should do so in a manner whichdoes not create potential liability for other Contributors. Therefore, if a Contributor includes the Program ina commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend andindemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs(collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party againstthe Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributorin connection with its distribution of the Program in a commercial product offering. The obligations in thissection do not apply to any claims or Losses relating to any actual or alleged intellectual propertyinfringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the CommercialContributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperatewith the Commercial Contributor in, the defense and any related settlement negotiations. The IndemnifiedContributor may participate in any such claim at its own expense.

For example, a Contributor might include the Program in a commercial product offering, Product X. ThatContributor is then a Commercial Contributor. If that Commercial Contributor then makes performanceclaims, or offers warranties related to Product X, those performance claims and warranties are suchCommercial Contributor's responsibility alone. Under this section, the Commercial Contributor would haveto defend claims against the other Contributors related to those performance claims and warranties, and if acourt requires any other Contributor to pay any damages as a result, the Commercial Contributor must paythose damages.

5. NO WARRANTY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "ASIS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIEDINCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient issolely responsible for determining the appropriateness of using and distributing the Program and assumesall risks associated with its exercise of rights under this Agreement , including but not limited to the risksand costs of program errors, compliance with applicable laws, damage to or loss of data, programs orequipment, and unavailability or interruption of operations.

6. DISCLAIMER OF LIABILITY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANYCONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATIONLOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANYRIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7. GENERAL

If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect thevalidity or enforceability of the remainder of the terms of this Agreement, and without further action by theparties hereto, such provision shall be reformed to the minimum extent necessary to make such provisionvalid and enforceable. If Recipient institutes patent litigation against any entity (including a cross-claim or

counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program withother software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted underSection 2(b) shall terminate as of the date such litigation is All Recipient's rights under this Agreement shallterminate if it fails to comply with any of the material terms or conditions of this Agreement and does notcure such failure in a reasonable period of time after becoming aware of such noncompliance. If allRecipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of theProgram as soon as reasonably practicable. However, Recipient's obligations under this Agreement and anylicenses granted by Recipient relating to the Program shall continue and survive.

Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistencythe Agreement is copyrighted and may only be modified in the following manner. The Agreement Stewardreserves the right to publish new versions (including revisions) of this Agreement from time to time. No oneother than the Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is theinitial Agreement Steward. The Eclipse Foundation may assign the responsibility to serve as the AgreementSteward to a suitable separate entity. Each new version of the Agreement will be given a distinguishingversion number. The Program (including Contributions) may always be distributed subject to the version ofthe Agreement under which it was received. In addition, after a new version of the Agreement is published,Contributor may elect to distribute the Program (including its Contributions) under the new version. Exceptas expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectualproperty of any Contributor under this Agreement, whether expressly, by implication, estoppel orotherwise. All rights in the Program not expressly granted under this Agreement are reserved.

This Agreement is governed by the laws of the State of New York and the intellectual property laws of theUnited States of America. No party to this Agreement will bring a legal action under this Agreement morethan one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.

The information included in this documentation is the proprietary and confidential information of BMCSoftware, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions ofthe applicable End User License agreement for the product and to the proprietary and restricted rightsnotices included in the product documentation.

BMC SOFTWARE INC

2101 CITYWEST BLVD, HOUSTON TX 77042-2827, USA• 713 918 8800

Customer Support: 800 537 1813 (United States and Canada) or contact your local support center

Corda License Agreement

PopChart/OptiMap/Highwire Software License Agreement

Copyright 1997-2005 Corda Technologies, Inc.

IMPORTANT NOTICE

THIS IS A LEGAL AGREEMENT between "you" the end user of this Software, and Corda Technologies, Inc.,a Utah corporation having an office at 350 South 400 West, Suite 100, Lindon, Utah 84042 ("Corda"). Use ofthe software you are about to download or install indicates your acceptance of these terms. You also agreeto accept these terms by so indicating at the appropriate screen, prior to the download or installationprocess. As used in this License, the capitalized term "Software" means the PopChart(tm) graphingcomputer software and/or OptiMap(tm) mapping computer software and/or Highwire(tm) documentgeneration and/or Corda Builder(tm) graph design software to be downloaded or installed, together withany and all enhancements, upgrades, and updates that may be provided to you in the future by Corda. IFYOU DO NOT AGREE TO THESE TERMS AND CONDITIONS, YOU SHOULD SO INDICATE AT THEAPPROPRIATE SCREEN AND PROMPTLY DISCONTINUE THE INSTALLATION AND DOWNLOADPROCESS.

1. Ownership. The Software and any accompanying documentation are owned by Corda or its licensors andare protected under U.S. copyright laws and international treaty provisions. Ownership of the Software, andall copies, modifications, and merged portions thereof shall at all times remain with Corda or its licensors.Copies are provided to you only to allow you to exercise your rights under this License. This License doesnot constitute a sale of the Software or related documentation, or any portion thereof. Without limiting thegenerality of the foregoing, you do not receive any rights to any patents, copyrights, trade secrets,trademarks or other intellectual property rights to the software or related documentation. All rights notexpressly granted to you under this License are reserved by Corda.

2. Grant of License. Corda grants to you and you accept, subject to the terms and conditions set out in thisLicense, a limited, nonexclusive, nontransferable, nonsublicensable, and revocable right to use the Softwaresolely and strictly in accordance with the conditions and restrictions applicable to the license type for whichyou have paid, as follows:

A.Number of Licensed Machines. Unless you have purchased a multiple copy license, you are authorized touse a single copy of the Software on a single Licensed Machine. If you have purchased a multiple copylicense, you are authorized to use the number of copies for which you have paid, each on a single LicensedMachine. If this License is for a Corda Builder product, the term "Licensed Machine" means a stand alonecomputer owned or leased by you. Once the Software has been installed on a Licensed Machine, it may beused on another machine only if it is first completely removed from the first machine.

B.Commercial Corda Builder Products. If this License is for a Commercial Corda Builder product, you areauthorized to use the Software to construct graph or map definitions or templates (appearance files) for 1)deployment with PopChart, OptiMap and/or Highwire servers provided that your use of the relevantapplication conforms in all respects with the terms and conditions of the license pursuant to which you areauthorized to use it; and/or 2) publishing of graphs, maps or PDF documents using Corda Builder. You areonly authorized to use a Corda Builder product to create definitions or templates (appearance files) for theuse by persons who have a valid license for PopChart, OptiMap and/or Highwire server and/or CordaBuilder in accordance with licenses covering those applications. The graphs, maps and/or PDF filesgenerated by PopChart, OptiMap and/or Highwire server and/or Corda Builder are freely distributable.

C.Evaluation Version. If this License is for an evaluation version of any Corda software, you are authorizedto use the Software only for evaluation purposes for a single evaluation period not to exceed 30 days,commencing on the day on which you accept this License. Should you require an evaluation periodexceeding thirty (30) days, you may contact Corda for an extended evaluation license. Graphs, charts ormaps produced by Software configured with an evaluation version must contain symbols and text providedby Corda indicating that the graph, chart or map was produced with an evaluation version of the Software.You are not authorized to obtain more than one license for an evaluation version of any Corda software bysubsequent downloads or installations.

D.Developer Version. If this License is for a Developer version of any Corda software, you are authorized touse the Software only for internal development and testing purposes and not for general use on the Internet,an intranet or any application which is accessible to those other than the developers creating an applicationor those who are directly approving an application as it is developed. All Server-based Developer softwareis limited to and licensed for the creation of no more than 1,000 charts or maps or no more than 500Highwire documents during any single day.

E.Staging/Testing/Pre-Production License. If this License is for a Staging/Testing/Pre-Production versionof any Corda software, you are authorized to use those licensed copies of the Software only for internal staging/testing/pre-production purposes and not for general use on the Internet, an intranet or any applicationwhich is accessible to those other than the developers testing an application or those who are directlyapproving an application as it is tested. No restrictions on the number of charts, maps or Highwiredocuments is made for a Staging/Testing/Pre-Production version of the software. Staging/Testing/Pre-Production Licenses are limited to the number of servers and CPU's licensed by you for full use hereunder.

F.CPU License. If this license is for a server product, this license restricts the use of the software to thenumber of CPU licenses bought with/for the software. Absent a purchase of additional CPU rights, thissoftware may be used only on a computer containing two (2) or fewer CPU's. One CPU license is requiredfor each CPU of the server(s) running the software. Additional CPU licenses can be purchased from Corda.Regardless of where or how the software is loaded, all CPU's that serve up output from the software mustbe licensed.

G.User License. If this license is for a server product, this license restricts the use of the software to thenumber of user licenses bought with/for the software. Absent a purchase of additional User Licenses or aLicense for more than twenty-five (25) users, this software may be used by up to twenty-five (25) users.Additional user licenses can be purchased from Corda. A User License is valid for one individual accessingthe output from the software over an Intranet/Extranet or over the Internet on a non-anonymous basis, e.g.as an authenticated, identified user. A user is subject to the User License requirements if he/she has accessto the output of the software through a computer information system.

H.Public Internet License. If this license is for a server product, this license does not permit the use of thesoftware on the public internet unless a Public Internet License is purchased from Corda.

I.Applications Service Provider. This license does not permit you to utilize the Software as all or a part of anApplications Service Provider (ASP) service offering whereby you provide web-based software and hosting

of that software for use by third parties for a fee. Corda offers ASP licenses under a separate ASP LicenseAgreement.

J.The specific Corda software licensed by you, including the number of servers, CPU's, users, etc., includedin your license may be reflected in an invoice for the software created by Corda or another documentcreated by Corda with the intent that such document reflect the specific licenses granted to you. Upon yourrequest, Corda will provide such a document reflecting the specific licenses granted to you for your records.

Creative Commons License

THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CREATIVECOMMONS PUBLIC LICENSE ("CCPL" OR "LICENSE"). THE WORK IS PROTECTED BY COPYRIGHTAND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS AUTHORIZEDUNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED.

Body text.

BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BEBOUND BY THE TERMS OF THIS LICENSE. THE LICENSOR GRANTS YOU THE RIGHTS CONTAINEDHERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.

1. Definitions

"Collective Work" means a work, such as a periodical issue, anthology or encyclopedia, in which the Workin its entirety in unmodified form, along with a number of other contributions, constituting separate andindependent works in themselves, are assembled into a collective whole. A work that constitutes aCollective Work will not be considered a Derivative Work (as defined below) for the purposes of this License.

"Derivative Work" means a work based upon the Work or upon the Work and other pre-existing works,such as a translation, musical arrangement, dramatization, fictionalization, motion picture version, soundrecording, art reproduction, abridgment, condensation, or any other form in which the Work may be recast,transformed, or adapted, except that a work that constitutes a Collective Work will not be considered aDerivative Work for the purpose of this License. For the avoidance of doubt, where the Work is a musicalcomposition or sound recording, the synchronization of the Work in timed-relation with a moving image("synching") will be considered a Derivative Work for the purpose of this License.

"Licensor" means the individual or entity that offers the Work under the terms of this License.

"Original Author" means the individual or entity who created the Work.

"Work" means the copyrightable work of authorship offered under the terms of this License.

"You" means an individual or entity exercising rights under this License who has not previously violated theterms of this License with respect to the Work, or who has received express permission from the Licensor toexercise rights under this License despite a previous violation.

2. Fair Use Rights. Nothing in this license is intended to reduce, limit, or restrict any rights arising from fairuse, first sale or other limitations on the exclusive rights of the copyright owner under copyright law orother applicable laws.

3. License Grant. Subject to the terms and conditions of this License, Licensor hereby grants You aworldwide, royalty-free, non-exclusive, perpetual (for the duration of the applicable copyright) license toexercise the rights in the Work as stated below: to reproduce the Work, to incorporate the Work into one ormore Collective Works, and to reproduce the Work as incorporated in the Collective Works; to create andreproduce Derivative Works; to distribute copies or phonorecords of, display publicly, perform publicly,and perform publicly by means of a digital audio transmission the Work including as incorporated inCollective Works; to distribute copies or phonorecords of, display publicly, perform publicly, and performpublicly by means of a digital audio transmission Derivative Works.

For the avoidance of doubt, where the work is a musical composition: Performance Royalties Under BlanketLicenses. Licensor waives the exclusive right to collect, whether individually or via a performance rightssociety (e.g. ASCAP, BMI, SESAC), royalties for the public performance or public digital performance (e.g.webcast) of the Work.

Mechanical Rights and Statutory Royalties . Licensor waives the exclusive right to collect, whetherindividually or via a music rights agency or designated agent (e.g. Harry Fox Agency), royalties for any

phonorecord You create from the Work ("cover version") and distribute, subject to the compulsory licensecreated by 17 USC Section 115 of the US Copyright Act (or the equivalent in other jurisdictions).

Webcasting Rights and Statutory Royalties . For the avoidance of doubt, where the Work is a soundrecording, Licensor waives the exclusive right to collect, whether individually or via a performance-rightssociety (e.g. SoundExchange), royalties for the public digital performance (e.g. webcast) of the Work, subjectto the compulsory license created by 17 USC Section 114 of the US Copyright Act (or the equivalent in otherjurisdictions).

The above rights may be exercised in all media and formats whether now known or hereafter devised. Theabove rights include the right to make such modifications as are technically necessary to exercise the rightsin other media and formats. All rights not expressly granted by Licensor are hereby reserved.

4. Restrictions. The license granted in Section 3 above is expressly made subject to and limited by thefollowing restrictions:

You may distribute, publicly display, publicly perform, or publicly digitally perform the Work only underthe terms of this License, and You must include a copy of, or the Uniform Resource Identifier for, thisLicense with every copy or phonorecord of the Work You distribute, publicly display, publicly perform, orpublicly digitally perform. You may not offer or impose any terms on the Work that alter or restrict theterms of this License or the recipients' exercise of the rights granted hereunder. You may not sublicense theWork. You must keep intact all notices that refer to this License and to the disclaimer of warranties. Youmay not distribute, publicly display, publicly perform, or publicly digitally perform the Work with anytechnological measures that control access or use of the Work in a manner inconsistent with the terms of thisLicense Agreement. The above applies to the Work as incorporated in a Collective Work, but this does notrequire the Collective Work apart from the Work itself to be made subject to the terms of this License. If Youcreate a Collective Work, upon notice from any Licensor You must, to the extent practicable, remove fromthe Collective Work any credit as required by clause 4(b), as requested. If You create a Derivative Work,upon notice from any Licensor You must, to the extent practicable, remove from the Derivative Work anycredit as required by clause 4(b), as requested.

If you distribute, publicly display, publicly perform, or publicly digitally perform the Work or anyDerivative Works or Collective Works, You must keep intact all copyright notices for the Work and provide,reasonable to the medium or means You are utilizing: (i) the name of the Original Author (or pseudonym, ifapplicable) if supplied, and/or (ii) if the Original Author and/or Licensor designate another party or parties(e.g. a sponsor institute, publishing entity, journal) for attribution in Licensor's copyright notice, terms ofservice or by other reasonable means, the name of such party or parties; the title of the Work if supplied; tothe extent reasonably practicable, the Uniform Resource Identifier, if any, that Licensor specifies to beassociated with the Work, unless such URI does not refer to the copyright notice or licensing information forthe Work; and in the case of a Derivative Work, a credit identifying the use of the Work in the DerivativeWork (e.g., "French translation of the Work by Original Author," or "Screenplay based on original Work byOriginal Author"). Such credit may be implemented in any reasonable manner; provided, however, that inthe case of a Derivative Work or Collective Work, at a minimum such credit will appear where any othercomparable authorship credit appears and in a manner at least as prominent as such other comparableauthorship credit.

5. Representations, Warranties and Disclaimer

UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING, LICENSOR OFFERSTHE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KINDCONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING,WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY, FITNESS FOR A PARTICULARPURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY,OR THE PRESENCE OF ABSENCE OF ERRORS, WHETHER OR NOT DISCOVERABLE. SOMEJURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO SUCHEXCLUSION MAY NOT APPLY TO YOU.

6. Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENTWILL LICENSOR BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL,CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THEUSE OF THE WORK, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCHDAMAGES.

7. Termination

This License and the rights granted hereunder will terminate automatically upon any breach by You of theterms of this License. Individuals or entities who have received Derivative Works or Collective Works fromYou under this License, however, will not have their licenses terminated provided such individuals or

entities remain in full compliance with those licenses. Sections 1, 2, 5, 6, 7, and 8 will survive anytermination of this License.

Subject to the above terms and conditions, the license granted here is perpetual (for the duration of theapplicable copyright in the Work). Notwithstanding the above, Licensor reserves the right to release theWork under different license terms or to stop distributing the Work at any time; provided, however that anysuch election will not serve to withdraw this License (or any other license that has been, or is required to be,granted under the terms of this License), and this License will continue in full force and effect unlessterminated as stated above.

8. Miscellaneous

Each time You distribute or publicly digitally perform the Work or a Collective Work, the Licensor offers tothe recipient a license to the Work on the same terms and conditions as the license granted to You under thisLicense.

Each time You distribute or publicly digitally perform a Derivative Work, Licensor offers to the recipient alicense to the original Work on the same terms and conditions as the license granted to You under this License.

If any provision of this License is invalid or unenforceable under applicable law, it shall not affect thevalidity or enforceability of the remainder of the terms of this License, and without further action by theparties to this agreement, such provision shall be reformed to the minimum extent necessary to make suchprovision valid and enforceable.

No term or provision of this License shall be deemed waived and no breach consented to unless such waiveror consent shall be in writing and signed by the party to be charged with such waiver or consent.

This License constitutes the entire agreement between the parties with respect to the Work licensed here.There are no understandings, agreements or representations with respect to the Work not specified here.Licensor shall not be bound by any additional provisions that may appear in any communication from You.This License may not be modified without the mutual written agreement of the Licensor and You.

Creative Commons is not a party to this License, and makes no warranty whatsoever in connection with theWork. Creative Commons will not be liable to You or any party on any legal theory for any damageswhatsoever, including without limitation any general, special, incidental or consequential damages arisingin connection to this license. Notwithstanding the foregoing two (2) sentences, if Creative Commons hasexpressly identified itself as the Licensor hereunder, it shall have all rights and obligations of Licensor.

Except for the limited purpose of indicating to the public that the Work is licensed under the CCPL, neitherparty will use the trademark "Creative Commons" or any related trademark or logo of Creative Commonswithout the prior written consent of Creative Commons. Any permitted use will be in compliance withCreative Commons' then-current trademark usage guidelines, as may be published on its website orotherwise made available upon request from time to time.

Creative Commons may be contacted at http://creativecommons.org/.

Apache Software License, Version 2.0

This product includes the Apache software product found at http://www.apache.org/ , and the Apachesoftware product is distributed to us pursuant to the following terms and conditions:

Copyright (c) 2000-2004 The Apache Software Foundation. All rights reserved.

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions."

"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting theLicense.

"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by,or are under common control with that entity. For the purposes of this definition, "control" means (i) thepower, direct or indirect, to cause the direction or management of such entity, whether by contract or

http://creativecommons.org

otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficialownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications, including but not limited to softwaresource code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of a Sourceform, including but not limited to compiled object code, generated documentation, and conversions to othermedia types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under theLicense, as indicated by a copyright notice that is included in or attached to the work (an example isprovided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derivedfrom) the Work and for which the editorial revisions, annotations, elaborations, or other modificationsrepresent, as a whole, an original work of authorship. For the purposes of this License, Derivative Worksshall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, theWork and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including the original version of the Work and anymodifications or additions to that Work or Derivative Works thereof, that is intentionally submitted toLicensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized tosubmit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form ofelectronic, verbal, or written communication sent to the Licensor or its representatives, including but notlimited to communication on electronic mailing lists, source code control systems, and issue trackingsystems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving theWork, but excluding communication that is conspicuously marked or otherwise designated in writing bythe copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution hasbeen received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor herebygrants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright licenseto reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute theWork and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor herebygrants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated inthis section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer theWork, where such license applies only to those patent claims licensable by such Contributor that arenecessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with theWork to which such Contribution(s) was submitted. If You institute patent litigation against any entity(including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporatedwithin the Work constitutes direct or contributory patent infringement, then any patent licenses granted toYou under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in anymedium, with or without modifications, and in Source or Object form, provided that You meet the followingconditions:

(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,trademark, and attribution notices from the Source form of the Work, excluding those notices that do notpertain to any part of the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that Youdistribute must include a readable copy of the attribution notices contained within such NOTICE file,excluding those notices that do not pertain to any part of the Derivative Works, in at least one of thefollowing places: within a NOTICE text file distributed as part of the Derivative Works; within the Sourceform or documentation, if provided along with the Derivative Works; or, within a display generated by theDerivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICEfile are for informational purposes only and do not modify the License. You may add Your own attribution

notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text fromthe Work, provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or differentlicense terms and conditions for use, reproduction, or distribution of Your modifications, or for any suchDerivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwisecomplies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionallysubmitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of thisLicense, without any additional terms or conditions. Notwithstanding the above, nothing herein shallsupersede or modify the terms of any separate license agreement you may have executed with Licensorregarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, orproduct names of the Licensor, except as required for reasonable and customary use in describing the originof the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides theWork (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIESOR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warrantiesor conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULARPURPOSE. You are solely responsible for determining the appropriateness of using or redistributing theWork and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence),contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) oragreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect,special, incidental, or consequential damages of any character arising as a result of this License or out of theuse or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage,computer failure or malfunction, or any and all other commercial damages or losses), even if suchContributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof,You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liabilityobligations and/or rights consistent with this License. However, in accepting such obligations, You may actonly on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only ifYou agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claimsasserted against, such Contributor by reason of your accepting any such warranty or additional liability.

GNU Lesser General Public License

Certain software used by this program is:

Provided by Bruno Lowagie and is subject to its copyrights and those of its licensors;

Copyright (C) 1991, 1999 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307USA

The above component is licensed under the terms of the GNU Lesser General Public License version 2.1which is included on the distribution media.

NO WARRANTY

BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THELIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATEDIN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THELIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OFALL NECESSARY SERVICING, REPAIR OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANYCOPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THELIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL,

SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITYTO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEINGRENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OFTHE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHERPARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

GNU LESSER GENERAL PUBLIC LICENSE

Version 2.1, February 1999

Copyright (C) 1991, 1999 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307USA

JDOM License

Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved.


1. Redistributions of source code must retain the above copyright notice, this list of conditions, and thefollowing disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and thedisclaimer that follows these conditions in the documentation and/or other materials provided with thedistribution.

3. The name "JDOM" must not be used to endorse or promote products derived from this software withoutprior written permission. For written permission, please contact <request_AT_jdom_DOT_org>.

4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name,without prior written permission from the JDOM Project Management <request_AT_jdom_DOT_org>.

In addition, we request (but do not require) that you include in the end-user documentation provided withthe redistribution and/or in the software itself an acknowledgement equivalent to the following:

"This product includes software developed by the JDOM Project (http://www.jdom.org/)."

Alternatively, the acknowledgment may be graphical using the logos available at http://www.jdom.org/images/logos.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOMAUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, ORPROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OFTHE POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of the Java DocumentObject Model Project and was originally created by Jason Hunter <jhunter_AT_jdom_DOT_org> and BrettMcLaughlin <brett_AT_jdom_DOT_org>. For more information on the JDOM Project, please see <http://www.jdom.org/>.

Bouncy Castle License

Copyright (c) 2000 - 2006 The Legion Of The Bouncy Castle (http://www.bouncycastle.org)

Body text.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associateddocumentation files (the "Software"), to deal in the Software without restriction, including without

http://www.jdom.org/)

http://www.jdom.org/images/logos

http://www.jdom.org/images/logos

limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of theSoftware, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portionsof the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR APARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS ORCOPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHERIN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR INCONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Sun License

Copyright 1994-2006 Sun Microsystems, Inc. All Rights Reserved.


Redistribution of source code must retain the above copyright notice, this list of conditions and thefollowing disclaimer.

Redistribution in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.

Neither the name of Sun Microsystems, Inc. or the names of contributors may be used to endorse orpromote products derived from this software without specific prior written permission.

This software is provided "AS IS," without a warranty of any kind. ALL EXPRESS OR IMPLIEDCONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, AREHEREBY EXCLUDED. SUN MICROSYSTEMS, INC. ("SUN") AND ITS LICENSORS SHALL NOT BELIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING ORDISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES. IN NO EVENT WILL SUN OR ITS LICENSORSBE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL,CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESSOF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE THISSOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

You acknowledge that this software is not designed, licensed or intended for use in the design, construction,operation or maintenance of any nuclear facility.

SAX license

Copyright Status

SAX is free!

In fact, it's not possible to own a license to SAX, since it's been placed in the public domain.

Sun Microsystems, Inc. Binary Code License Agreement

1. LICENSE TO USE. Sun grants you a non-exclusive and non-transferable license for the internal use onlyof the accompanying software and documentation and any error corrections provided by Sun (collectively"Software"), by the number of users and the class of computer hardware for which the corresponding fee hasbeen paid.

2. RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated intellectualproperty rights is retained by Sun and/or its licensors. Except as specifically authorized in anySupplemental License Terms, you may not make copies of Software, other than a single copy of Software for

archival purposes. Unless enforcement is prohibited by applicable law, you may not modify, decompile, orreverse engineer Software. Licensee acknowledges that Licensed Software is not designed or intended foruse in the design, construction, operation or maintenance of any nuclear facility. Sun Microsystems, Inc.disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to anytrademark, service mark, logo or trade name of Sun or its licensors is granted under this Agreement.

3. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date ofpurchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will befree of defects in materials and workmanship under normal use. Except for the foregoing, Software isprovided "AS IS". Your exclusive remedy and Sun's entire liability under this limited warranty will be atSun's option to replace Software media or refund the fee paid for Software.

4. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS ORIMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIEDWARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS AREHELD TO BE LEGALLY INVALID.

5. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUNOR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL,INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSEDREGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF ORINABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCHDAMAGES. In no event will Sun's liability to you, whether in contract, tort (including negligence), orotherwise, exceed the amount paid by you for Software under this Agreement. The foregoing limitationswill apply even if the above stated warranty fails of its essential purpose.

6. Termination. This Agreement is effective until terminated. You may terminate this Agreement at any timeby destroying all copies of Software. This Agreement will terminate immediately without notice from Sun ifyou fail to comply with any provision of this Agreement. Upon Termination, you must destroy all copies ofSoftware.

7. Export Regulations. All Software and technical data delivered under this Agreement are subject to USexport control laws and may be subject to export or import regulations in other countries. You agree tocomply strictly with all such laws and regulations and acknowledge that you have the responsibility toobtain such licenses to export, re-export, or import as may be required after delivery to you.

8. U.S. Government Restricted Rights. If Software is being acquired by or on behalf of the U.S. Governmentor by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights inSoftware and accompanying documentation will be only as set forth in this Agreement; this is in accordancewith 48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR2.101 and 12.212 (for non-DOD acquisitions).

9. Governing Law. Any action related to this Agreement will be governed by California law and controllingU.S. federal law. No choice of law rules of any jurisdiction will apply.

10. Severability. If any provision of this Agreement is held to be unenforceable, this Agreement will remainin effect with the provision omitted, unless omission would frustrate the intent of the parties, in which casethis Agreement will immediately terminate.

11. Integration. This Agreement is the entire agreement between you and Sun relating to its subject matter. Itsupersedes all prior or contemporaneous oral or written communications, proposals, representations andwarranties and prevails over any conflicting or additional terms of any quote, order, acknowledgment, orother communication between the parties relating to its subject matter during the term of this Agreement.No modification of this Agreement will be binding, unless in writing and signed by an authorizedrepresentative of each party.

JAVA(TM) INTERFACE CLASSES JAVA API FOR XML-BASED RPC API

CLASS FILES, VERSION 1.1 SUPPLEMENTAL LICENSE TERMS

These supplemental license terms ("Supplemental Terms") add to or modify the terms of the Binary CodeLicense Agreement (collectively, the "Agreement"). Capitalized terms not defined in these SupplementalTerms shall have the same meanings ascribed to them in the Agreement. These Supplemental Terms shallsupersede any inconsistent or conflicting terms in the Agreement, or in any license contained within theSoftware.

1. Software Internal Use and Development License Grant.

Subject to the terms and conditions of this Agreement, including, but not limited to Section 3 (Java(TM)Technology Restrictions) of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable,limited license to reproduce internally and use internally the binary form of the Software, complete andunmodified, for the sole purpose of designing, developing and testing your Java applets and applications("Programs").

2. License to Distribute Software. In addition to the license granted in Section 1 (Software Internal Use andDevelopment License Grant) of these Supplemental Terms, subject to the terms and conditions of thisAgreement, including but not limited to Section 3 (Java Technology Restrictions), Sun grants you a non-exclusive, non-transferable, limited license to reproduce and distribute the Software in binary form only,provided that you (i) distribute the Software complete and unmodified and only bundled as part of yourPrograms, (ii) do not distribute additional software intended to replace any component(s) of the Software,(iii) do not remove or alter any proprietary legends or notices contained in the Software, (iv) only distributethe Software subject to a license agreement that protects Sun's interests consistent with the terms containedin this Agreement, and (v) agree to defend and indemnify Sun and its licensors from and against anydamages, costs, liabilities, settlement amounts and/or expenses

3. Java Technology Restrictions. You may not modify the Java Platform Interface ("JPI", identified as classescontained within the "java" package or any subpackages of the "java" package), by creating additionalclasses within the JPI or otherwise causing the addition to or modification of the classes in the JPI. In theevent that you create an additional class and associated API(s) which (i) extends the functionality of the JavaPlatform, and (ii) is exposed to third party software developers for the purpose of developing additionalsoftware which invokes such additional API, you must promptly publish broadly an accurate specificationfor such API for free use by all developers. You may not create, or authorize your licensees to createadditional classes, interfaces, or subpackages that are in any way identified as "java", "javax", "sun" orsimilar convention as specified by Sun in any naming convention designation.

4. Trademarks and Logos. You acknowledge and agree as between you and Sun that Sun owns the SUN,SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, andiPLANET-related trademarks, service marks, logos and other brand designations ("Sun Marks"), and youagree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit.

5. Source Code. Software may contain source code that is provided solely for reference purposes pursuant tothe terms of this Agreement. Source code may not be redistributed unless expressly provided for in thisAgreement.

6. Termination for Infringement. Either party may terminate this Agreement immediately should anySoftware become, or in either party's opinion be likely to become, the subject of a claim of infringement ofany intellectual property right.

For inquiries please contact: Sun Microsystems, Inc. 4150

Network Circle, Santa Clara, California 95054

(LFI#136499/Form ID#011801)

Java Service License

Copyright (c) 2000, Alexandria Software Consulting

All rights reserved. Redistribution and use in source and binary forms, with or without modification, arepermitted provided that the following conditions are met:

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLEFOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSEDAND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

END-USER LICENSE AGREEMENT FOR JIDE SOFTWARE, INC.'S PRODUCTS

IMPORTANT - READ CAREFULLY: This JIDE Software, Inc. ("JIDE") End-User License Agreement("EULA") is a legal agreement between you (an individual developer of software applications) and JIDE forthe JIDE software product accompanying this EULA, which includes computer software and may includeassociated source code, media, printed materials, and "on-line" or electronic documentation ("SOFTWAREPRODUCT"). By installing, copying, or otherwise using the SOFTWARE PRODUCT, you agree to be boundby the terms of this EULA. If you do not agree to the terms of this EULA, do not install, use, distribute inany manner, or replicate in any manner, any part, file or portion of the SOFTWARE PRODUCT.

The SOFTWARE PRODUCT is protected by copyright laws and international copyright treaties, as well asother intellectual property laws and treaties. The SOFTWARE PRODUCT is licensed, not sold.

RIGOROUS ENFORCEMENT OF INTELLECTUAL PROPERTY RIGHTS. If the licensed right of use for thisSOFTWARE PRODUCT is purchased by you with any intent to reverse engineer, decompile, createderivative works, and the exploitation or unauthorized transfer of, any JIDE intellectual property and tradesecrets, to include any exposed methods or source code where provided, no licensed right of use shall exist,and any products created as a result shall be judged illegal by definition of all applicable law. Any sale orresale of intellectual property or created derivatives so obtained will be prosecuted to the fullest extent of alllocal, federal and international law.

GRANT OF LICENSE. This EULA, if legally executed as defined herein, licenses and so grants you thefollowing rights:

Single Developer License. You may install and use multiple copies of the SOFTWARE PRODUCT or anyprior version legally licensed once a single developer license ("Single Developer License") has been obtainedfrom JIDE or a reseller authorized by JIDE, generally via some form of registration. A Single DeveloperLicense for the SOFTWARE PRODUCT may not be shared or used concurrently by more than oneindividual developer. In a project that uses the SOFTWARE PRODUCT, each individual developer on theproject requires a separate Single Developer License as long as they need to access JIDE's products anddocuments.

Deployment License. If either cases below is true, in addition to the developer licenses you purchased, youneed to purchase deployment licenses.

You exposed the API (application program interface) provided by JIDE to your end users. That is your enduser will use our APIs directly to create application through the purchase of your product which includesJIDE.

The number of your application deployments is larger than 1000 times of the number of developer licensesyou purchased. And you are not willing to show JIDE name and logo in about dialog, or splash screen orany other places where users can easily notice.

Source Code License. In addition to the license and rights granted above, JIDE grants you the right to useand modify the JIDE source provided you licensed source code. Different from developer license, sourcecode license is licensed to a project. Each project only need to purchase one copy of source code license.

JIDE shall retain all right, title and interest in and to all updates, modifications, enhancements andderivative works, in whole or in part, of the JIDE Source Code created by you, including all copyrightssubsisting therein, to the extent such modifications, enhancements or derivative works containcopyrightable code or expression derived from the JIDE source code; provided, however, that JIDE grants toyou a fully-paid, royalty free license, to use copy and modify such updates, modifications, enhancementsand derivative works or copies thereof for use as authorized in this LICENSE.

You may not distribute the JIDE source code, or any modified version or derivative work of the JIDE sourcecode, in source code form.

JIDE require all developers in your project who plan to access JIDE source code signing on the source codelicense. As long as they signed, they become registered developers. An alternative to this is to let a delegatesigns source code license as an organization. The delegate will be responsible for letting other developerswho plan to access the source code reviewing this license agreement first before releasing them the access.

The source code contained herein and in related files is provided to the registered developer for thepurposes of education and troubleshooting. Under no circumstances may any portion of the source code bedistributed, disclosed or otherwise made available to any third party without the express written consent ofJIDE.

Under no circumstances may the source code be used in whole or in part, as the basis for creating a productthat provides the same, or substantially the same, functionality as any JIDE products.

The registered developer acknowledges that this source code contains valuable and proprietary trade secretsof JIDE. The registered developer agrees to expend every effort to insure its confidentiality. For example,under no circumstances may the registered developer allow to put the source code on an internal networkwhere he or she has no control.

Due to the insecurity of Java byte-code, if you plan to use classes that built from the source code directly,you must agree to obfuscate the classes before distributing it to your customers.

SOURCE CODE IS SOLD AS IS. JIDE DOES NOT PROVIDE ANY TECHNICAL SUPPORT FOR SOURCECODE.

DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.

Not for Resale Software. If the SOFTWARE PRODUCT is labeled and provided as "Not for Resale" or "NFR",then, notwithstanding other sections of this EULA, you may not resell, distribute, or otherwise transfer forvalue or benefit in any manner, the SOFTWARE PRODUCT or any derivative work using the SOFTWAREPRODUCT. You may not transfer, rent, lease, lend, copy, modify, translate, sublicense, time-share orelectronically transmit the SOFTWARE PRODUCT, media or documentation. This also applies to any andall intermediate files, source code, and compiled executables.

Limitations on Reverse Engineering, Decompilation, and Disassembly. You may not reverse engineer,decompile, create derivative works, modify, translate, or disassemble the SOFTWARE PRODUCT, and onlyto the extent that such activity is expressly permitted by applicable law notwithstanding this limitation. Youagree to take all reasonable, legal and appropriate measures to prohibit the illegal dissemination of theSOFTWARE PRODUCT or any of its constituent parts and redistributables to the fullest extent of allapplicable local, US Codes and International Laws and Treaties regarding anti-circumvention, including butnot limited to, the Geneva and Berne World Intellectual Property Organization (WIPO) DiplomaticConferences.

Rental. You may not rent, lease, or lend the SOFTWARE PRODUCT.

Separation of Components, Their Constituent Parts and Redistributables. The SOFTWARE PRODUCT islicensed as a single product. The SOFTWARE PRODUCT and its constituent parts and any providedredistributables may not be reverse engineered, decompiled, disassembled, nor placed for distribution, sale,or resale as individual creations by you or any individual not expressly given such permission by JIDE. Theprovision of source code, if included with the SOFTWARE PRODUCT, does not constitute transfer of anylegal rights to such code, and resale or distribution of all or any portion of all source code and intellectualproperty will be prosecuted to the fullest extent of all applicable local, federal and international laws. AllJIDE libraries, source code, redistributables and other files remain JIDE's exclusive property. You may notdistribute any files, except those that JIDE has expressly designated as Redistributable.

The SOFTWARE PRODUCT may include certain files ("Redistributables") intended for distribution by youto the users of programs you create. Redistributables include jar file (or class files if you intend to packageall JIDE classes into your own jar). Developer Guide of SOFTWARE PRODUCT (if any) or any otherdocuments (such as javadoc) which are intended to teach you how to use the SOFTWARE PRODUCT, andsample code are not considered as redistributables. Subject to all of the terms and conditions in this EULA,you may reproduce and distribute exact copies of the Redistributables, provided that such copies are madefrom the original copy of the SOFTWARE PRODUCT or the copy transferred to a hard disk. Copies ofRedistributables may only be distributed with and for the sole purpose of executing application programspermitted under this EULA that you have created using the SOFTWARE PRODUCT. You may reformat orrecombine the original distribution format of redistributables provided by JIDE. However JIDE will notsupport or have any liability for such use.

Installation and Use. The license granted in this EULA for you to create your own compiled programs anddistribute your programs and the Redistributables (if any), is subject to all of the following conditions:

All copies of the programs you create must bear a valid copyright notice, either your own or the JIDEcopyright notice that appears on the SOFTWARE PRODUCT.

You may not remove or alter any JIDE copyright, trademark or other proprietary rights notice contained inany portion of JIDE libraries, source code, Redistributables or other files that bear such a notice.

JIDE provides no warranty at all to any person, and you will remain solely responsible to anyone receivingyour programs for support, service, upgrades, or technical or other assistance, and such recipients will haveno right to contact JIDE for such services or assistance.

Your programs containing the SOFTWARE PRODUCT must be written using a licensed, registered copy ofthe SOFTWARE PRODUCT.

Your programs must add primary and substantial functionality, and may not be merely a set or subset ofany of the libraries, code, Redistributables or other files of the SOFTWARE PRODUCT.

Support Services. JIDE may provide you with support services related to the SOFTWARE PRODUCT("Support Services"). Use of Support Services is governed by JIDE policies and programs described in theuser manual, in on-line documentation and/or other JIDE provided materials. Any supplemental softwarecode provided to you as part of the Support Services shall be considered part of the SOFTWARE PRODUCTand subject to the terms and conditions of this EULA. With respect to technical information you provide toJIDE as part of the Support Services, JIDE may use such information for its business purposes, including forproduct support and development.

1.Software Transfer. You may NOT permanently or temporarily transfer ANY of your rights under thisEULA to any individual or entity. Regardless of any modifications which you make and regardless of howyou might compile, link, and/or package your programs, under no circumstances may the libraries,redistributables, and/or other files of the SOFTWARE PRODUCT (including any portions thereof) be usedfor developing programs by anyone other than you. Only you as the licensed end user have the right to usethe libraries, redistributables, or other files of the SOFTWARE PRODUCT (or any portions thereof) fordeveloping programs created with the SOFTWARE PRODUCT. In particular, you may not share copies ofthe Redistributables with other co-developers.

-Termination. Without prejudice to any other rights or remedies, JIDE will terminate this EULA upon yourfailure to comply with all the terms and conditions of this EULA. In such event, you must destroy all copiesof the SOFTWARE PRODUCT and all of its component parts including any related documentation, andmust remove ANY and ALL use of such technology with the next generally available release from anyapplications using technology contained in the SOFTWARE PRODUCT developed by you, whether innative, altered or compiled resultt.

Time Limitation: There is no time limitation on using the SOFTWARE PRODUCT as long as you don'tviolate this license agreement.

UPGRADES. If the SOFTWARE PRODUCT is labeled as an upgrade, you must be properly licensed to usethe SOFTWARE PRODUCT identified by JIDE as being eligible for the upgrade in order to use theSOFTWARE PRODUCT. A SOFTWARE PRODUCT labeled as an upgrade replaces and/or supplements theSOFTWARE PRODUCT that formed the basis for your eligibility for the upgrade, and together constitute asingle SOFTWARE PRODUCT. You may use the resulting upgraded SOFTWARE PRODUCT only inaccordance with all the terms of this EULA.

COPYRIGHT. All title and copyrights in and to the SOFTWARE PRODUCT (including but not limited toany images, demos, source code, intermediate files, packages, photographs, animations, video, audio, music,text, and "applets" incorporated into the SOFTWARE PRODUCT), the accompanying printed materials, andany copies of the SOFTWARE PRODUCT are owned by JIDE or its subsidiaries. The SOFTWAREPRODUCT is protected by copyright laws and international treaty provisions. Therefore, you must treat theSOFTWARE PRODUCT like any other copyrighted material except that you may install the SOFTWAREPRODUCT for use by you, a single developer. You may not copy any printed materials accompanying theSOFTWARE PRODUCT.

GENERAL PROVISIONS. This EULA may only be modified in writing signed by you and an authorizedofficer of JIDE. If any provision of this EULA is found void or unenforceable, the remainder will remainvalid and enforceable according to its terms.

MISCELLANEOUS. If you acquired this product in the United States, this EULA is governed by the laws ofthe State of CA.

If this SOFTWARE PRODUCT was acquired outside the United States, then you, agree and ascend to theadherence to all applicable international treaties regarding copyright and intellectual property rights whichshall also apply. In addition, you agree that any local law(s) to the benefit and protection of JIDE ownershipof, and interest in, its intellectual property and right of recovery for damages thereto will also apply.

Should you have any questions concerning this EULA, or if you desire to contact JIDE for any reason, pleasecontact us via our support web pages at http://www.jidesoft.com/.

NO WARRANTIES. JIDE EXPRESSLY DISCLAIMS ANY WARRANTY FOR THE SOFTWARE PRODUCT.THE PRODUCT AND ANY RELATED DOCUMENTATION IS PROVIDED "AS IS" WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION,THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ORNONINFRINGEMENT. THE ENTIRE RISK ARISING OUT OF USE OR PERFORMANCE OF THEPRODUCT REMAINS WITH YOU.

LIMITATION OF LIABILITY. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NOEVENT SHALL JIDE OR ITS SUPPLIERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, ORCONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGESFOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION,ANY OTHER PECUNIARY LOSS, ATTORNEY FEES AND COURT COSTS) ARISING OUT OF THE USEOF OR INABILITY TO USE THE SOFTWARE PRODUCT OR THE PROVISION OF OR FAILURE TOPROVIDE SUPPORT SERVICES, EVEN IF JIDE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCHDAMAGES.

BSD License

All rights reserved.

Redistribution and use of this software in source and binary forms, with or without modification, arepermitted provided that the following conditions are met:

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSSOF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVENIF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Jaxen License

Copyright 2003 (C) The Werken Company. All Rights Reserved.

Redistribution and use of this software and associated documentation ("Software"), with or withoutmodification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain copyright statements and notices. Redistributions must alsocontain a copy of this document.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or other materials provided with the distribution.

3. The name "jaxen" must not be used to endorse or promote products derived from this Software withoutprior written permission of The Werken Company. For written permission, please contact [email protected].

4. Products derived from this Software may not be called "jaxen" nor may "jaxen" appear in their nameswithout prior written permission of The Werken Company. "jaxen" is a registered trademark of The WerkenCompany.

5. Due credit should be given to The Werken Company. (http://jaxen.werken.com/).

THIS SOFTWARE IS PROVIDED BY THE WERKEN COMPANY AND CONTRIBUTORS "AS IS'' ANDANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE WERKEN COMPANY OR ITS CONTRIBUTORS BE LIABLEFOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSEDAND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Clearthought Software License, Version 2.0

Copyright (c) 2001 Daniel Barbalace. All rights reserved

Body text.

Project maintained at https://tablelayout.dev.java.net

I. Terms for redistribution of original source and binaries

Redistribution and use of unmodified source and/or binaries are permitted provided that the followingcondition is met:

1. Redistributions of original source code must retain the above copyright notice and license. You are notrequired to redistribute the original source; you may choose to redistribute only the binaries.

Basically, if you distribute unmodified source, you meet automatically comply with the license with noadditional effort on your part.

II. Terms for distribution of derived works via subclassing and/or composition.

You may generate derived works by means of subclassing and/or composition (e.g., the Adaptor Pattern),provided that the following conditions are met:

1. Redistributions of original source code must retain the above copyright notice and license. You are notrequired to redistribute the original source; you may choose to redistribute only the binaries.

2. The original software is not altered.

3. Derived works are not contained in the info.clearthought namespace/package or any subpackage ofinfo.clearthought.

4. Derived works do not use the class or interface names from the info.clearthought... packages

For example, you may define a class with the following full name:org.nameOfMyOrganization.layouts.RowMajorTableLayout

However, you may not define a class with the either of the following full names:

III. Terms for redistribution of source modified via patch files.

You may generate derived works by means of patch files provided that the following conditions are met:

1. Redistributions of original source code must retain the above copyright notice and license. You are notrequired to redistribute the original source; you may choose to redistribute only the binaries resulting fromthe patch files.

2. The original source files are not altered. All alteration is done in patch files.

3. Derived works are not contained in the info.clearthought namespace/package or any subpackage ofinfo.clearthought. This means that your patch files must change the namespace/package for the derivedwork. See section II for examples.

4. Derived works do not use the class or interface names from the

info.clearthought... packages. This means your patch files

must change the names of the interfaces and classes they alter.

See section II for examples.

5. Derived works must include the following disclaimer. "This work is derived from Clearthought'sTableLayout, https://tablelayout.dev.java.net, by means of patch files rather than subclassing orcomposition. Therefore, this work might not contain the latest fixes and features of TableLayout."

IV. Terms for repackaging, transcoding, and compiling of binaries.

You may do any of the following with the binaries of the original software.

1. You may move binaries (.class files) from the original .jar file to your own .jar file.

2. You may move binaries from the original .jar file to other resource containing files, including but notlimited to .zip, .gz, .tar, .dll, .exe files.

3. You may backend compile the binaries to any platform, including but not limited to Win32, Win64, MACOS, Linux, Palm OS, any handheld or embedded platform.

4. You may transcribe the binaries to other virtual machine byte code protocols, including but not limitedto .NET.

V. License Disclaimer.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR,AFFILATED BUSINESSES, OR ANYONE ELSE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISINGIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.

The BSD License for the JGoodies Looks

Copyright (c) 2001-2004 JGoodies Karsten Lentzsch. All rights reserved.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSSOF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVENIF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associateddocumentation files (the "Software"), to deal in the Software without restriction, including withoutlimitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of theSoftware, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portionsof the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR APARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS ORCOPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHERIN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR INCONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE

GNU General Public License, version 2, with the Classpath Exception The GNUGeneral Public License (GPL) Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.

59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is notallowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast,the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the FreeSoftware Foundation's software and to any other program whose authors commit to using it. (Some otherFree Software Foundation software is covered by the GNU Library General Public License instead.) You canapply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses aredesigned to make sure that you have the freedom to distribute copies of free software (and charge for thisservice if you wish), that you receive source code or can get it if you want it, that you can change thesoftware or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to askyou to surrender the rights. These restrictions translate to certain responsibilities for you if you distributecopies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give therecipients all the rights that you have. You must make sure that they, too, receive or can get the source code.And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which givesyou legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there isno warranty for this free software. If the software is modified by someone else and passed on, we want itsrecipients to know that what they have is not the original, so that any problems introduced by others willnot reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger thatredistributors of a free program will individually obtain patent licenses, in effect making the programproprietary.

To prevent this, we have made it clear that any patent must be licensed for everyone's free use or notlicensed at all.

The precise terms and conditions for copying, distribution and modification follow.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holdersaying it may be distributed under the terms of this General Public License. The "Program", below, refers toany such program or work, and a "work based on the Program" means either the Program or any derivativework under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim orwith modifications and/or translated into another language. (Hereinafter, translation is included withoutlimitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outsideits scope. The act of running the Program is not restricted, and the output from the Program is covered onlyif its contents constitute a work based on the Program (independent of having been made by running theProgram). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in anymedium, provided that you conspicuously and appropriately publish on each copy an appropriatecopyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to theabsence of any warranty; and give any other recipients of the Program a copy of this License along with theProgram.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warrantyprotection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based onthe Program, and copy and distribute such modifications or work under the terms of Section 1 above,provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changed the files and thedate of any change.

b) You must cause any work that you distribute or publish, that in whole or in part contains or is derivedfrom the Program or any part thereof, to be licensed as a whole at no charge to all third parties under theterms of this License.

c) If the modified program normally reads commands interactively when run, you must cause it, whenstarted running for such interactive use in the most ordinary way, to print or display an announcementincluding an appropriate copyright notice and a notice that there is no warranty (or else, saying that youprovide a warranty) and that users may redistribute the program under these conditions, and telling theuser how to view a copy of this License. (Exception: if the Program itself is interactive but does not normallyprint such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are notderived from the Program, and can be reasonably considered independent and separate works inthemselves, then this License, and its terms, do not apply to those sections when you distribute them asseparate works. But when you distribute the same sections as part of a whole which is a work based on theProgram, the distribution of the whole must be on the terms of this License, whose permissions for otherlicensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you;rather, the intent is to exercise the right to control the distribution of derivative or collective works based onthe Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a workbased on the Program) on a volume of a storage or distribution medium does not bring the other workunder the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code orexecutable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributedunder the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge nomore than your cost of physically performing source distribution, a complete machine-readable copy of thecorresponding source code, to be distributed under the terms of Sections 1 and 2 above on a mediumcustomarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code.(This alternative is allowed only for noncommercial distribution and only if you received the program inobject code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For anexecutable work, complete source code means all the source code for all modules it contains, plus anyassociated interface definition files, plus the scripts used to control compilation and installation of theexecutable. However, as a special exception, the source code distributed need not include anything that isnormally distributed (in either source or binary form) with the major components (compiler, kernel, and soon) of the operating system on which the executable runs, unless that component itself accompanies theexecutable.

If distribution of executable or object code is made by offering access to copy from a designated place, thenoffering equivalent access to copy the source code from the same place counts as distribution of the sourcecode, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under thisLicense. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and willautomatically terminate your rights under this License. However, parties who have received copies, orrights, from you under this License will not have their licenses terminated so long as such parties remain infull compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grantsyou permission to modify or distribute the Program or its derivative works. These actions are prohibited bylaw if you do not accept this License. Therefore, by modifying or distributing the Program (or any workbased on the Program), you indicate your acceptance of this License to do so, and all its terms andconditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automaticallyreceives a license from the original licensor to copy, distribute or modify the Program subject to these termsand conditions.

You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You arenot responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (notlimited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise)that contradict the conditions of this License, they do not excuse you from the conditions of this License. Ifyou cannot distribute so as to satisfy simultaneously your obligations under this License and any otherpertinent obligations, then as a consequence you may not distribute the Program at all.

For example, if a patent license would not permit royalty-free redistribution of the Program by all those whoreceive copies directly or indirectly through you, then the only way you could satisfy both it and thisLicense would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balanceof the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or tocontest validity of any such claims; this section has the sole purpose of protecting the integrity of the freesoftware distribution system, which is implemented by public license practices. Many people have madegenerous contributions to the wide range of software distributed through that system in reliance onconsistent application of that system; it is up to the author/donor to decide if he or she is willing todistribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or bycopyrighted interfaces, the original copyright holder who places the Program under this License may add anexplicit geographical distribution limitation excluding those countries, so that distribution is permitted onlyin or among countries not thus excluded. In such case, this License incorporates the limitation as if writtenin the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public Licensefrom time to time. Such new versions will be similar in spirit to the present version, but may differ in detailto address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of thisLicense which applies to it and "any later version", you have the option of following the terms andconditions either of that version or of any later version published by the Free Software Foundation. If theProgram does not specify a version number of this License, you may choose any version ever published bythe Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditionsare different, write to the author to ask for permission. For software which is copyrighted by the FreeSoftware Foundation, write to the Free Software Foundation; we sometimes make exceptions for this.

Our decision will be guided by the two goals of preserving the free status of all derivatives of our freesoftware and of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THEPROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISESTATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THEPROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY ANDPERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE,YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANYCOPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THEPROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANYGENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE ORINABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATABEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A

FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDEROR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best wayto achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source fileto most effectively convey the exclusion of warranty; and each file should have at least the "copyright" lineand a pointer to where the full notice is found.

One line to give the program's name and a brief idea of what it does.

Copyright (C) <year> <name of author>

This program is free software; you can redistribute it and/or modify it under the terms of the GNU GeneralPublic License as published by the Free Software Foundation; either version 2 of the License, or (at youroption) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; withouteven the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See theGNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, writeto the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NOWARRANTY; for details type 'show w'. This is free software, and you are welcome to redistribute it undercertain conditions; type 'show c' for details.

The hypothetical commands 'show w' and 'show c' should show the appropriate parts of the General PublicLicense. Of course, the commands you use may be called something other than 'show w' and 'show c'; theycould even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a"copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program 'Gnomovision' (which makes passesat compilers) written by James Hacker.

signature of Ty Coon, 1 April 1989

Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary programs. If yourprogram is a subroutine library, you may consider it more useful to permit linking proprietary applicationswith the library. If this is what you want to do, use the GNU Library General Public License instead of thisLicense.

"CLASSPATH" EXCEPTION TO THE GPL

Certain source files distributed by Sun Microsystems, Inc. are subject to the following clarification andspecial exception to the GPL, but only where Sun has expressly included in the particular source file'sheader the words "Sun designates this particular file as subject to the "Classpath" exception as provided bySun in the LICENSE file that accompanied this code."

Linking this library statically or dynamically with other modules is making a combined work based on thislibrary. Thus, the terms and conditions of the GNU General Public License cover the whole combination.

As a special exception, the copyright holders of this library give you permission to link this library withindependent modules to produce an executable, regardless of the license terms of these independentmodules, and to copy and distribute the resulting executable under terms of your choice, provided that youalso meet, for each linked independent module, the terms and conditions of the license of that module. Anindependent module is a module which is not derived from or based on this library. If you modify this

library, you may extend this exception to your version of the library, but you are not obligated to do so. Ifyou do not wish to do so, delete this exception statement from your version.

Java HTML Tidy - JTidy

HTML parser and pretty printer

Copyright (c) 1998-2000 World Wide Web Consortium (Massachusetts Institute of Technology, InstitutNational de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved.

Contributing Author(s):

Dave Raggett <[email protected]>

Andy Quick <[email protected]> (translation to Java)

Gary L Peskin <[email protected]> (Java development)

Sami Lempinen <[email protected]> (release management)

Fabrizio Giustina <fgiust at users.sourceforge.net>

Vlad Skarzhevskyy <vlads at users.sourceforge.net>

The contributing author(s) would like to thank all those who helped with testing, bug fixes, and patience.This wouldn't have been possible without all of you.

COPYRIGHT NOTICE:

This software and documentation is provided "as is," and the copyright holders and contributing author(s)make no representations or warranties, express or implied, including but not limited to, warranties ofmerchantability or fitness for any particular purpose or that the use of the software or documentation willnot infringe any third party patents, copyrights, trademarks or other rights.

The copyright holders and contributing author(s) will not be liable for any direct, indirect, special orconsequential damages arising out of any use of the software or documentation, even if advised of thepossibility of such damage.

Permission is hereby granted to use, copy, modify, and distribute this source code, or portions hereof,documentation and executables, for any purpose, without fee, subject to the following restrictions:

1. The origin of this source code must not be misrepresented.

2. Altered versions must be plainly marked as such and must not be misrepresented as being the originalsource.

3. This Copyright notice may not be removed or altered from any source or altered source distribution.

The copyright holders and contributing author(s) specifically permit, without fee, and encourage the use ofthis source code as a component for supporting the Hypertext Markup Language in commercial products. Ifyou use this source code in a product, acknowledgment is not required but would be appreciated.

49532*106816*