Web Methods Installation Guide 7.1.1

Title Page

webMethodsInstallation Guide

Version 7.1.x

January 2008

webMethods

Copyright& Docu‐ment ID
This document applies to webMethods Product Suite Version 7.1.x and to all subsequent releases.

Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions.

© Copyright Software AG 2005‐2008.

All rights reserved.

The name Software AG and/or all Software AG product names are either trademarks or registered trademarks of Software AG. Other company and product names mentioned herein may be trademarks of their respective owners.

Document ID: WEBM-IG-71x-20080128

Table of Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1. Development Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Integration Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Process Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Portlet and Web Application Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Monitoring and Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2. Software and Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Operating Systems, JDKs, Browsers, RDBMSs, and Drivers . . . . . . . . . . . . . . . . . . . . . . . 20Standard Product Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 20Special Product Hardware Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Trading Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3. International Operating Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Extended Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Browsers and JDK Font Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4. Using the Wizard for Simple Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5. Preparing for Advanced Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Prepare for Installation on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Prepare for Installation on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . 38

Prepare for Installation on a Remote Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Prepare the Machine on Which to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Prepare to Install webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

webMethods Installation Guide Version 7.1.x 3

Table of Contents

Installation Scripts and Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Installation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Installation Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6. Using the Wizard for Advanced Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Start the Installer on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Start the Installer and Specify a Different System Temp Directory . . . . . . . . . . . . . . . . 45After You Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Start the Installer on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Start the Installer and Specify a Different Temporary Directory . . . . . . . . . . . . . . . . . . 47After You Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Use Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Create, Install from, or Edit an Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Create or Install from an Installation Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Use a Proxy Server to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Change Logging Level and File, and Add Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Overwrite Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

How to Choose Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Complete Product Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Configure Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Configure Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Configure Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Configure Infrastructure Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Configure Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Configure webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Configure My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

7. Using Console Mode for Advanced Product Installation . . . . . . . . . . . . . . . . . . . . . . . . 69Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Start the Installer and Specify a Different Temporary Directory . . . . . . . . . . . . . . . . . . 71Start the Installer Using Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Specify Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Specify User Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

4 webMethods Installation Guide Version 7.1.x

Table of Contents

Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75How to Select Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Complete Product Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Configure Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Configure Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Configure Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Configure the Infrastructure Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Configure Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Configure webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Configure My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

8. Preparing for Database Component Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83webMethods Products and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Database Users and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Database Administrator Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Character Set and Sort Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Page and Block Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Set Database Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Download the Database Scripts and Database Component Configurator . . . . . . . . . . . . . . 88Change Environment Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Default Storage Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Database Component Descriptions and Installation Requirements . . . . . . . . . . . . . . . . . . 90

Cross Reference, Document History, IS Internal, and IS Core Audit Log Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Process Audit Log Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Process Engine Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Archive Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Metadata Reasoner and Metadata Repository Database Components . . . . . . . . . . . . 92My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Trading Networks and Trading Networks Archive Database Components . . . . . . . . . . 92Analysis and Process Tracker Database Components . . . . . . . . . . . . . . . . . . . . . . . . 92Staging and Reporting Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Infrastructure Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93


Table of Contents

9. Creating and Dropping Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Use the Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Create Database Components and Create a Database User and Storage . . . . . . . . . 97Drop Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Drop the Storage and Revoke Database User Permissions . . . . . . . . . . . . . . . . . . . . . 100

Use the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Database Component Configurator Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Use Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Create a Database User and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Drop Storage and Revoke Database User Permissions . . . . . . . . . . . . . . . . . . . . . . . . 110Create Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Drop Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

10. Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Configure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Complete the webMethods Broker Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Make Sure the Broker Server is Running and the Default Broker Exists . . . . . . . . . . . 115Adjust Per-Process Thread Limit and Set Per-Process and Kernel Limit on

HP-UX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Configure Broker Monitors to Start Automatically on UNIX Systems . . . . . . . . . . . . . . 115Set Locale on UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Enable Full Core Dumps on AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Complete the Integration Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Increase PermGen Space on UNIX, IBM i5, and Mac Systems . . . . . . . . . . . . . . . . . . 116Increase File Descriptors and Change Permissions on UNIX, IBM i5, and

Mac Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Start Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Prevent Memory Problems on IBM i5 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Streamline Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Drop Redundant Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Complete the Metadata Library Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Configure Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Set up JDK on AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Complete the Monitor Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Set Up Graphical Display on UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Complete the Optimize Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Configure Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Drop Redundant Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Connect Products to Each Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Connect Optimize Analytic Engines to My webMethods Server . . . . . . . . . . . . . . . . . . 123Connect Process Engines to Task Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Connect Process Engines to Optimize Analytic Engines . . . . . . . . . . . . . . . . . . . . . . . 125Connect Integration Server to webMethods Broker and Metadata Library . . . . . . . . . . 125


Table of Contents

Connect Monitor to My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Connect Trading Networks Server to My webMethods Server . . . . . . . . . . . . . . . . . . . 128Connect Designer to Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Connect Deployer to Source and Target webMethods Products . . . . . . . . . . . . . . . . . 128

Connect Products to Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Database Connections for Integration Server and Trading Networks Server . . . . . . . . 129Define a Connection Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Point a Function at a Connection Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Installed JDKs and Product JDK Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Configure Products to Use 64-Bit Mode on Solaris and HP-UX Systems . . . . . . . . . . 134Redirect Products to Use a Non-Default JRE or JDK . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Complete the Installation for Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

11. Uninstalling Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Uninstall on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Uninstall on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Complete the Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Complete the webMethods Broker Uninstallation on UNIX Systems . . . . . . . . . . . . . . 144Complete the Deployer Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

A. Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146


Table of Contents


About This Guide

This guide is for users who are installing or uninstalling the webMethods products below.

Typically, to install webMethods products, you download the webMethods Installer and the files for each product from the webMethods Advantage Web site at http://advantage.webmethods.com. If you cannot download software, webMethods Customer Operations can provide the webMethods products for which you have purchased licenses on a CD or through a private FTP site. Contact webMethods Customer Operations at [email protected].

If you must perform certain configuration tasks before you can start a webMethods product, this guide also explains those configuration tasks. For information on starting products and configuring them after they are started, see the product documentation. For instructions on installing and uninstalling webMethods products that are not covered in this guide, see the documentation for those products.

Product Release

Fair Isaac Blaze Advisor 6.5.3

webMethods Broker 7.1

webMethods Designer 7.1.1

webMethods Developer 7.1.1

webMethods Integration Server 7.1.1

webMethods Metadata Library 7.1.1

webMethods Monitor 7.1

My webMethods Server 7.1.1

webMethods Optimize 7.1

webMethods Optimize Infrastructure Data Collector

7.1.1

webMethods Trading Networks 7.1.1

Important! Information in this guide might have been updated since you last downloaded it. Go to the webMethods Bookshelf for the latest version of the guide.

If you want to upgrade these products, you must use the instructions in the appropriate upgrade procedure. The instructions in this installation guide do not cover upgrades, so following the instructions in this guide for upgrades would have unpredictable results.


http://advantage.webmethods.com

http://advantage.webmethods.com/bookshelf

About This Guide

Document Conventions

Additional InformationThe webMethods Advantage Web site at http://advantage.webmethods.com provides you with important sources of information about webMethods products:

Troubleshooting Information. The webMethods Knowledge Base provides troubleshooting information for many webMethods products.

Documentation Feedback. To provide feedback on webMethods documentation, go to the Documentation Feedback Form on the webMethods Bookshelf.

Additional Documentation. Starting with 7.0, you have the option of downloading the documentation during product installation to a single directory called “_documentation,” located by default under the webMethods installation directory. In addition, you can find documentation for all webMethods products on the webMethods Bookshelf.

Convention Description

Bold Identifies elements on a screen.

Italic Identifies variable information that you must supply or change based on your specific situation or environment. Identifies terms the first time they are defined in text. Also identifies service input and output variables.

Narrow font Identifies storage locations for services on the webMethods Integration Server using the convention folder.subfolder:service.

Typewriter font

Identifies characters and values that you must type exactly or messages that the system displays on the console.

UPPERCASE Identifies keyboard keys. Keys that you must press simultaneously are joined with the “+” symbol.

\ Directory paths use the “\” directory delimiter unless the subject is UNIX‐specific.

[ ] Optional keywords or values are enclosed in [ ]. Do not type the [ ] symbols in your own code.



http://advantage.webmethods.com/kb_top

http://advantage.webmethods.com/docfeedback

http://advantage.webmethods.com/Bookshelf

http://advantage.webmethods.com/Bookshelf

1 Development Environments

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Integration Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Process Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Portlet and Web Application Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Monitoring and Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17



OverviewThis chapter lists the webMethods products to install to create various webMethods environments. Each section in this chapter lists the superset of products you can install; if you have not purchased licenses for all of the products, simply install the ones you have.

The chapter also lists the database components to install for each environment. A webMethods database component is a grouping of database objects that can be used by one or more webMethods products. For information on the products that write to or read from each database component, and the contents of each database component, see “Database Component Descriptions and Installation Requirements” on page 90.

To design your webMethods production environments, work with your administrators, Software AG Professional Services, webMethods GEAR methodology, and webMethods best practices documentation.

Integration DevelopmentDeveloper and Trading Networks Console

Integration Server with Trading Networks Server and Monitor

webMethods Broker

My webMethods Server, and My webMethods user interfaces for Monitor, Trading Networks, and Broker and JMS

Database Component Configurator

Documentation

TN Server

Integration Server

webMethods Broker

Monitor Monitor interfaceBroker and JMS interfaceDeveloper

Trading Networks ConsoleTrading Networks interface

databaseMy webMethods Server



Below are additional options.

The table below lists the database components you must or can include in an integration development environment. The database components are versioned differently than the products. For descriptions of database components, see “Database Component Descriptions and Installation Requirements” on page 90.

If you want to... Install this product...

Log webMethods Broker documents Integration Server Logging Utility

Store Integration Server and Trading Networks keys and certificates securely

Integration Server PKI Support package

Maintain Developer elements in Microsoft Visual Sourcesafe or IBM Rational ClearCase

Integration Server VSS Support orIntegration Server ClearCase Support

Monitor your run times Optimize for Infrastructure (see “Monitoring and Administration” on page 16)

Product Required Database ComponentsOptional Database Com-ponents

Integration Server

IS Core Audit Log v11, Process Audit Log v30

IS Internal v20 (required if not using the embedded IS Internal database; see “Configure Integration Server” on page 61)

Cross Reference v10 (required when using cross referencing in publish‐and‐subscribe solutions, if you are not using the embedded IS Internal database)

Document History v10 (required when using exactly‐once document processing in publish‐and‐subscribe solutions)

Note: For information on cross referencing and exactly‐once processing, see the Publish‐Subscribe Developer’s Guide.

Archive v20 (with Operation Management v15, IS Core Audit Log v11, and Process Audit Log v30)

My webMethods Server

My webMethods Server v20

Trading Networks Server

Trading Networks v20 Trading Networks Archive v20



Process DesignDesigner (all components)

Blaze Advisor

Developer with Blaze Rule Service Plug‐in

Integration Server with Blaze Rule Service Support, Monitor, and Process Engine

For collaboration among developers, Metadata Library

webMethods Broker

My webMethods Server with Task Engine, and My webMethods user interfaces for Central Configurator, Monitor, and Broker and JMS


Documentation

Below are additional options.

If you want to... Install this product...

Store Integration Server keys and certificates securely

Integration Server PKI Support package

Maintain Developer elements in Microsoft Visual Sourcesafe or IBM Rational ClearCase

Integration Server VSS Support orIntegration Server ClearCase Support

Monitor your business processes Optimize for Process (see “Monitoring and Administration” on page 16)


Designer

Developer

Blaze Advisor

MonitorProcess Engine

Integration Server

Monitor interface

Blaze

webMethods Broker

Broker and JMS interface

Task EngineCentral Configurator interfaceMetadata Library

database



The table below lists the database components you must or can include in a process design environment. The database components are versioned differently than the products. For descriptions of database components, see “Database Component Descriptions and Installation Requirements” on page 90.

Portlet and Web Application DevelopmentDesigner Composite Applications Development and My webMethods Server Support



Documentation

The table below lists the database components you must or can include in a portlet and Web application development environment. The database components are versioned differently than the products. For descriptions of database components, see “Database Component Descriptions and Installation Requirements” on page 90.

Product Required Database ComponentsOptional Database Components

Integration Server

IS Core Audit Log v12, Process Audit Log v30

IS Internal v25 (required if not using the embedded IS Internal database; see “Configure Integra‐tion Server” on page 61)

Archive v20 (with Opera‐tion Management v15, IS Core Audit Log v11, andProcess Audit Log v30)

Reporting v10, Staging v10

Metadata Library Metadata Repository v30, Metadata Reasoner v30



Process Engine Process Engine v30, Process Audit Log v30

Task Engine Process Audit Log v30

Product Required Database Components

My webMethods Server My webMethods Server v20

My webMethods ServerDesigner database



Monitoring and AdministrationOptimize Analytic Engine and Prediction Engine

To collect data about webMethods products, Optimize Infrastructure Data Collector and webMethods Broker

To collect data about custom applications, Optimize Web Service Data Collector and webMethods Broker

Integration Server with Monitor

My webMethods Server with Task Engine, and My webMethods user interfaces for Optimize for Infrastructure, Optimize for Process, Central Configurator, Broker and JMS, Monitor, and Optimize for B2B


Documentation

Analytic Engine

Prediction Engine

webMethods BrokerInfrastructure Data Collector

Web Service Data Collector

Optimize and Central Configurator interfaces

Broker and JMS interface

Optimize for B2B interfaceMonitor interface

Task Engine

My webMethods ServerIntegration Server

Monitordatabase



The table below lists the database components you must or can include in a monitoring and administration environment. The database components are versioned differently than the products. For descriptions of database components, see “Database Component Descriptions and Installation Requirements” on page 90.

DeployerDeployer is a tool you use to deploy items that reside on source webMethods servers to target webMethods servers. For example, you might want to deploy items you have developed on servers in a development environment to servers in a test or production environment. Deployer 7.1 works with 7.1 webMethods Broker, Designer, Integration Server, My webMethods Server, Optimize, and Trading Networks.

Deployer is a package you install on an Integration Server. If no firewall separates your source and target environments, install Deployer and its host Integration Server on a machine that can access all source and target servers. If a firewall separates the environments, install Deployer and its host Integration Server on a machine in the source environment that can access all source servers and in the target environment on a machine that can access all target servers.

Product Required Database ComponentsOptional Database Components

Optimize Analytic Engine, Prediction Engine, and Infrastructure Data Collector

Analysis v30 (with Distributed Locking v20 and Operation Management v15) Data Purge v15Process Tracker v30 (with Opera‐tion Management)

Process Audit Log v30 Archive v20 (with Opera‐tion Management v15, IS Core Audit Log v11, andProcess Audit Log v30)




2 Software and Hardware Support and Requirements

Operating Systems, JDKs, Browsers, RDBMSs, and Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Standard Product Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Special Product Hardware Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21



Operating Systems, JDKs, Browsers, RDBMSs, and DriversFor information on operating systems, browsers, RDBMSs, and database drivers that are supported by the webMethods product suite, see the webMethods System Requirements.

The webMethods Installer automatically installs appropriate JDKs on most operating systems. For information on the JDK each webMethods product uses by default on each type of system, see “Installed JDKs and Product JDK Usage” on page 133.

Standard Product Hardware Support and RequirementsThe table below lists the minimum and recommended hardware requirements for each webMethods product. Recommended amounts are shown in parentheses.

Important! The hardware requirements below are for webMethods products only. They do not include requirements for supporting software such as databases. You must determine the overall hardware requirements for each of your machines based on the overall requirements of your operating system and software.

ProductHard Drive Space (MB) RAM (MB)

Virtual/Swap (MB) CPUs

Infrastructure (shared code, such as JDKs)

200

Blaze Advisor 200 1024 (2048) 1

webMethods Broker 750 (1250)* 512 (2048) 1

Database Component Configurator 60

Designer 700 1024 (2048) 1

Developer 100 (200) 128 (256) 1

Documentation

Adapters and eStandards Modules

60

Core Product Guides 160

readmes 1

Integration Server 200 (350) 256 (512) 1

Metadata Library 100 (500)** 512 (2048) 1024 1

Monitor Nothing beyond the host Integration Server.*More hard drive space might be required if your documents are large, or if your clients use many guaranteed documents.

**More hard drive space might be required if you use debug level or higher logging.



Special Product Hardware ConsiderationsThis section describes special requirements you must consider when determining actual hardware requirements for the indicated products.

webMethods BrokerOn a Windows system, you can only install webMethods Broker on a local hard drive. You cannot install webMethods Broker on a network‐mounted drive.

DeployerDeployer requires additional hard drive space for the deployment projects you create. When allocating space, allow for the number of projects to increase over time.

My webMethods Server 300 1024 (2048) 1

Optimize

Analytic Engine 500 1024 (2048) 1024 1

Prediction Engine 500 1024 (2048) 1024 1

Infrastructure Data Collector 300 2048 (4096) 1024 1

Web Service Data Collector 100** 128 (256) 128 1

Process Engine Nothing beyond the host Integration Server.

Task Engine Nothing beyond the host My webMethods Server.

Trading Networks

Console 25 128 (256)

Server 50 1

ProductHard Drive Space (MB) RAM (MB)

Virtual/Swap (MB) CPUs

*More hard drive space might be required if your documents are large, or if your clients use many guaranteed documents.

**More hard drive space might be required if you use debug level or higher logging.



Optimize

Additional Hardware Information for the Analytic Engine and Prediction EngineIn a production environment, each engine’s disk subsystem requirements are a redundant array of independent disks (RAID 5), an UltraWide SCSI, and 10‐to‐15K RPM drives. Each engine requires additional hard drive space for log files. The recommended amount is 100MB. Each engine requires 7MB of hard drive space for each log file.

In a development environment, each engine has these hardware requirements:

Additional Hardware Information for Web Service Data CollectorsIn a production environment, each Web Service Data Collector requires additional hard drive space for log files. The recommended amount is 75MB. Each Web Service Data Collector requires 5MB of hard drive space for each log file.

Additional Hardware Information for the Infrastructure Data CollectorEach Infrastructure Data Collector supports up to 5000 objects, but for optimal performance, Software AG recommends that each Infrastructure Data Collector manage no more than 3500 objects. To manage an environment with 3500 objects or less, an Infrastructure Data Collector requires at least 2GB of RAM. To manage an environment with 10,000 objects, you need at least two Infrastructure Data Collectors; Software AG recommends using three. Each Infrastructure Data Collector should run on a separate machine that satisfies the hardware requirements.

The default heap space for the Infrastructure Data Collector is 512MB. When managing larger environments, the Infrastructure Data Collector needs greater heap space and physical memory to function optimally. If you plan for the Infrastructure Data Collector to manage close to the 5,000‐object limit, do the following:

1 Go to the Infrastructure Data Collector_directory\bin directory and open the server.{bat|sh} file in a text editor.

2 Increase the Infrastructure Data Collector’s heap space. Locate the JAVA_MAX_MEM parameter and set it to JAVA_MAX_MEM=1536M.

3 Save and close the file.

4 Increase the physical memory available for the Infrastructure Data Collector to 4GB.

For more information about scaling Infrastructure Data Collectors to manage a larger number of objects, see the webMethods Optimize for Infrastructure Administrator’s Guide.

Hard Drive Space (MB) RAM (MB)

Virtual/Swap (MB) CPUs Disk Subsystem

100 1000 1000 Intel Pentium III processor 400MHz or higher

10GB available free space



Trading NetworksThe hard drive space listed in “Standard Product Hardware Support and Requirements” on page 20 identifies only the amount of space Trading Networks Server requires for normal processing. It does not account for the space required to temporarily save large documents during processing. To use large document handling, you must define hard disk drive space on which Trading Networks Server can temporarily save documents (rather than store them in memory). The amount of space you need to temporarily save documents varies based on the number of documents you process concurrently and the size of the documents you process. For example, if your typical concurrent document load is 10, you would need hard disk drive space that is 10 to 15 times the combined size of the documents being processed concurrently. For more information, see the webMethods Trading Networks User’s Guide.


3 International Operating Environments

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Extended Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Browsers and JDK Font Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27



OverviewwebMethods products are designed for use anywhere in the world, and enable you to exchange data with systems and users who speak languages other than your own.

webMethods products use the Universal Character Set (ISO/IEC 10646‐2, or Unicode) as the character set for all internal operations. At minimum, the products support the requirements of Unicode 3.0. webMethods HTML content, including administration tools, uses Unicode UTF‐8 encoding.

For specific information on the testing, configuration, capabilities, and limitations of any webMethods product, see the product’s readme.

Language PacksThe webMethods Installer always installs the U.S. English files necessary to run webMethods products. However, for many products, you can also install language packs that provide translated user interfaces, messages, help, and documentation. Language packs are available for webMethods products on all operating systems that the webMethods product suite supports except IBM i5 and Mac.

Most products support multiple languages at a time; you can install as many language packs as you need. For products that support multiple languages, your client setup (that is, browser language preference, default locale in which the product is started, and locale selected in your user profile) will determine which language you see. If you operate a product in a locale for which language packs are not available or installed, you will see U.S. English.

Extended Character Set The webMethods Installer offers an extended character set that extends Javaʹs java.nio.Charset class to support additional installable character encodings and adds more than 870 custom character encodings. The extended character set allows you to use custom character encodings such as EBCDIC and OEM character encodings with Integration Server, adapters, and services.



Browsers and JDK Font ConfigurationSome HTML interfaces for webMethods products detect the language setting for your browser. If you have installed webMethods language packs on your webMethods products, those interfaces try to supply the user interface, messages, and data in that language. You can indicate which of the installed languages to display in your browser as follows:

Your Java run‐time environment might require modification to display non‐ASCII data. If you see hollow boxes or black squares where you would expect to see non‐ASCII characters, you might need to modify your JDKʹs font configuration file to provide an appropriate font for displaying these characters. For example, you might install a full Unicode font, such as Arial Unicode MS, or you can install a font for a particular language. For information on modifying font configuration file, see J2SE 5.0 at http://java.sun.com/j2se/1.5.0/docs/guide/intl/fontconfig.html

Browser Action

Firefox 1.x and 2.x Go to Tools Options Advanced General. Click Edit Languages and add the language you want to use to the top of the list.

Internet Explorer 6.x and 7.x

Go to Tools Internet Options. Click Languages and add the language you want to use to the top of the list.


http://java.sun.com/j2se/1.5.0/docs/guide/intl/fontconfig.html

4 Using the Wizard for Simple Product Installation

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36



OverviewThis chapter explains how to install webMethods products locally using the webMethods Installer wizard on any supported system in a U.S. English locale. To support the wizard, UNIX systems must have an X Windows environment.

The installer writes product, version, and build information to an audit history log file named history.text in the webMethods_directory\install\history\history.txt directory. If errors or warnings occur during installation, the installer writes them to a file named WmInstallLog.txt and stores the file in the main installation directory (by default, webMethods7).

If you want to install using any other options than those covered in this chapter, or if you need complete information on any topic mentioned here, see the chapters on advanced product installation.

Before You Begin1 Prepare your machine as follows:

a Make sure the machine has about 100MB of available disk space in its system temp directory (Windows) or temporary directory (all other systems) and about 256MB of available virtual memory.

b Install a JRE or JDK 1.5 of the bit mode indicated below to run the webMethods Installer:

Note: When you run the webMethods Installer on an IBM i5 system, the installer experiences display problems. While these display problems will not adversely affect the installation process, Software AG strongly recommends that you minimize the problems by running the installer from an IBM i5 client for Windows rather than from a telnet client.

System JRE or JDK Bit Mode

UNIX 32 or 64

IBM i5 64

Mac 32 or 64

Important! On IBM i5 and Mac systems, the installer will automatically configure the webMethods products you install to use the JRE or JDK you install to run the installer. For information on whether products require a JRE or a JDK, see “Redirect Products to Use a Non‐Default JRE or JDK” on page 135.



c Download the webMethods Installer. Go to the webMethods Advantage Web site and log in, then download the installer for Windows or UNIX, as appropriate.

d If the machine is running anti‐virus software, the software will scan all the files the installer downloads. This scan can take a long time. If you do not want the software to scan the files, shut down the anti‐virus software.

e Shut down all webMethods products that are running on the machine.

2 The Broker Server for Solaris, HP‐UX, and AIX systems is a 64‐bit binary application. If you are going to install webMethods Broker on one of these systems, you must configure the operating system kernel to run in 64‐bit mode. You cannot run the 64‐bit Broker Server on an operating system kernel configured to run in 32‐bit mode.

Start the Installer1 If you are installing on a Windows system, you must have Windows system

administrator privileges.

If you are installing on a UNIX system, log in as the non‐root user.

2 Go to the directory that contains the webMethods Installer and start the installer as follows:

System Action

Windows Double‐click the webMethodsInstaller7.exe file.

Other Run this command: java -Xmx512m -Xincgc -jar webMethodsInstaller7.jar


http://advantage.webmethods.com/sdc


The installer takes several seconds to unzip and launch its JVM, then displays the welcome panel.

You can resize the wizard as necessary. Click Next.



Specify Release, User Name, and Password

In the Release list, click 7.1.x and higher. Provide the requested user name and password. Click Next. The installer connects to the webMethods server to download the webMethods products for which you have purchased licenses.



Specify the Installation Directory

Provide the requested information and then click Next.

Windows only



Select Products to Install

The installer lists the webMethods products for which you have purchased licenses and that are supported on the target operating system. The highest level shows product names and releases and the lower levels show the items that make up or can be used with the product. You can choose the products to install using these methods:

Choose one or more development desktop installations from the Role list. The installer automatically selects the appropriate products and items for that role in the tree. You can also choose additional items. The products and items in each role are listed in Chapter 1, “Development Environments”.

Choose every product and the minimum recommended set of items for each of those products by clicking Select Defaults.

Choose individual products and items directly from the product tree. When you choose a product, the installer automatically chooses the minimum recommended set of items for that product.

When you choose a product, the installer always automatically chooses other products and items that the selected product requires on the same machine. For example, Trading Networks Server depends on Integration Server. If you select Trading Networks Server, the installer automatically selects Integration Server.



Click Next. If language packs are available for products you are installing or have already installed, the installer displays the language packs panel.

Click Next.

Read the license agreement. If you accept the terms, select the check box and click Next.

Configure ProductsIf you are installing Trading Networks Server, Integration Server, Optimize, Infrastructure Data Collector, Metadata Library, webMethods Broker, or My webMethods Server, the installer displays configuration panels. Go to “Configure Products” on page 59, and then remain in that chapter to complete the installation.

If you are not installing any of these products, go to “Review and Install” on page 68.


5 Preparing for Advanced Product Installation

Prepare for Installation on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Prepare for Installation on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Installation Scripts and Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41



Prepare for Installation on a Windows SystemPrepare the machine on which you are going to install as follows:

1 Download the webMethods Installer. Go to the webMethods Advantage Web site and log in, then download the installer for Windows.

2 If you are going to install in a locale other than U.S. English, or if you are going to install webMethods Broker and run it in a locale other than U.S. English, set the Windows system locale to the proper locale.

a On the Start menu, go to Control Panel Regional and Language Options.

b Click the Advanced tab. In the Language for non-Unicode programs area, click the language to use. Click OK.

c Restart Windows.

3 If the machine is running anti‐virus software, the software will scan all the files the installer downloads. This scan can take a long time. If you do not want the software to scan the files, shut down the anti‐virus software.

4 Shut down all webMethods products that are running on the machine.

Prepare for Installation on a UNIX, IBM i5, or Mac System

Prepare for Installation on a Remote MachineIf you are going to install webMethods products on a remote machine and you want to install using the webMethods installer wizard, using an installation image, or using an installation script that uses the wizard, follow these steps:

1 Enable the display of the local machine using the command shown below, where remote_host is the remote machine on which you are going to install:

2 Log on to the remote machine.

3 Set the DISPLAY variable on the remote machine to point to the local machine. For example, if you are using a bash shell and are installing from a local machine named installmachine and want to set the DISPLAY to the default device, enter:

Note: The instructions below are for Windows XP. Instructions for other Windows systems vary slightly.

xhost +remote_host

export DISPLAY=installmachine:0.0




Prepare the Machine on Which to InstallPrepare the machine on which you are going to install as follows:

1 Download the webMethods Installer. Go to the webMethods Advantage Web site and log in, then download the installer for UNIX.

2 Install a JRE or JDK 1.5 of the bit mode indicated below to run the webMethods Installer:

3 If you are going to install in a locale other than U.S. English, or if you are going to install webMethods Broker and run it in a locale other than U.S. English, set your shell to the proper locale by setting the LANG environment variable as follows:

4 If the machine is running anti‐virus software, the software will scan all the files the installer downloads. This scan can take a long time. If you do not want the software to scan the files, shut down the anti‐virus software.

5 Shut down all webMethods products that are running on the machine.

System JRE or JDK Bit Mode

UNIX 32 or 64

IBM i5 64

Mac 32 or 64

Important! On IBM i5 and Mac systems, the installer will automatically configure the webMethods products you install to use the JRE or JDK you install to run the installer. For information on whether products require a JRE or a JDK, see “Redirect Products to Use a Non‐Default JRE or JDK” on page 135.

Shell Commands

sh LANG=locale; export LANG

csh setenv LANG locale




Prepare to Install webMethods Broker

Install on a UNIX SystemOn UNIX systems, information about the webMethods Broker installations is stored in the BrokerInstallations.txt file in the /var/opt/webMethods directory. Make sure you have write permission to the /var/opt/ directory.

Install on a Solaris, HP-UX, or AIX SystemThe Broker Server for Solaris, HP‐UX, and AIX systems is a 64‐bit binary application. If you are going to install webMethods Broker on one of these systems, you must configure the operating system kernel to run in 64‐bit mode. You cannot run the 64‐bit Broker Server on an operating system kernel configured to run in 32‐bit mode.

NFS-Mounted PartitionIf you are going to configure Broker Server to create data files on an NFS‐mounted partition, mount the partition using the command below. The options on the command help protect data integrity.

Suppose the partition you want to mount is on a machine named netappca, the data directory on the partition is wmbroker_data, and you want to mount the partition on the local file system at /var/opt/wmbroker_data. The command would be as follows:

For information on other ways to protect data integrity, see your NFS server documentation.

mount -o hard,nointr,proto=tcp host:/path /mount_point

mount -o hard,nointr,proto=tcp netappca:/wmbroker_data /var/opt/wmbroker_data

Option Descriptionhard By default, if the NFS server does not respond to requests from the

Broker Server, the Broker Server tries a few times and then fails. The hard option forces the Broker Server to keep retrying until the NFS server responds. The Broker Server hangs during this period.

nointr Prevents users from killing the Broker Server while it is hung waiting for the NFS server to respond.

proto=tcp By default, the NFS‐mounted partition uses the user datagram protocol (UDP) protocol to communicate with the Broker Server. The proto=tcp option forces the partition to use transmission control protocol (TCP) instead. TCP is more reliable than UDP.



Installation Scripts and ImagesThe webMethods Installer offers advanced options you can use to create and install from installation scripts and images.

Installation ScriptsIf you need to create identical installations on multiple machines, you can create a script of the installation on one machine, then run the script to create the same installation on each of the other machines.

To create a script, you select the webMethods products to install and specify all installation options (for example, target installation directory). You can choose to actually create the desired installation on the current machine as you create the script, or you can create the script without creating the installation.

When you run the script, it automatically downloads and installs the webMethods products you selected and uses the installation options you specified.

If you later find that a script requires a change, you can edit the script. You can also create a script by editing an existing script and saving it under a new name.

Installation ImagesIf you need to create installations on machines that cannot go outside your corporate firewall to the webMethods Advantage Web site, you can download webMethods products into an installation image, and then use that image to install the desired subsets of products onto each machine.

Each image is designed for one type of operating system. You can create each image for any type of system, from any type of system. For example, you can create an image for a Solaris system from a Windows system, or vice versa.

Images do not include information on installation options such as target installation directory, because those options can vary by machine. You specify installation options for each machine when you install from the image.



6 Using the Wizard for Advanced Product Installation

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Start the Installer on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Start the Installer on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Use Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54



Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58


Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68



OverviewThis chapter explains how to do the following on any system using the webMethods Installer wizard:

Install webMethods products

Create an installation script or image from which to install webMethods products

Install webMethods products from an installation script or image

You can use the wizard to install locally or remotely. To support the wizard, UNIX systems must have an X Windows environment.

The installer writes product, version, and build information to an audit history log file named history.text in the webMethods_directory\install\history\history.txt directory. If errors or warnings occur during installation, the installer writes them to a file named WmInstallLog.txt and stores the file in the main installation directory (by default, webMethods7). You can change logging behavior; for instructions, see “Change Logging Level and File, and Add Targets” on page 52.

Note: When you run the webMethods Installer on an IBM i5 system, the installer experiences display problems. While these display problems will not adversely affect the installation process, Software AG strongly recommends that you minimize the problems by running the installer from an IBM i5 client for Windows rather than from a telnet client.

When you run the webMethods Installer on an AIX system, you might receive Java messages during installation. You can ignore these messages.



Start the Installer on a Windows SystemThe machine on which you are installing must have about 256MB of available virtual memory. If you are going to install many products or create an installation image for a Windows system, the installer needs more memory; if you are going to create an installation image for a different type of system, the installer needs still more memory.

The machine’s system temp directory must have about 100MB of available disk space. If you are going to install from an image, the directory must have enough additional available disk space to accommodate the image. For example, if the image is 200MB, the directory must have at least 250MB of available disk space. If necessary, you can specify a different directory to use as the system temp directory when you start the installer (see “Start the Installer and Specify a Different System Temp Directory” on page 45)

Start the InstallerTo run the installer on a Windows system, you must have Windows system administrator privileges.

Open Windows Explorer, go to the directory to which you downloaded the installer, and double‐click the webMethodsInstaller7.exe file.

By default, when you start the installer using the webMethodsInstaller7.exe file, the installer launches with the JVM options ‐Xmx512m and ‐Xincgc. The ‐Xmx option specifies the amount of memory to allow Java to use, while the ‐Xincgc option enables incremental garbage collection. If you want to allow Java to use more memory (for example, because you are creating an image), install a 32‐bit JRE or JDK 1.5, then go to the webMethods Advantage Web site, log in, download the webMethods Installer for UNIX, and enter this command, where amount is greater than 512:

Start the Installer and Specify a Different System Temp DirectoryTo run the installer on a Windows system, you must have Windows system administrator privileges.

Install a 32‐bit JRE or JDK 1.5, then go to the webMethods Advantage Web site, log in, download the webMethods Installer for UNIX, and enter this command:

The ‐Xmx option allows Java to use more memory than it uses by default, while the ‐Xincgc option enables incremental garbage collection. If you want to allow Java to use more memory (for example, because you are creating an image), increase the amount you specify on the ‐Xmx option.

java -Xmxamountm -Xincgc -jar webMethodsInstaller7.jar

java -Xmx512m -Xincgc -Djava.io.tmpdir=/different_directory-jar webMethodsInstaller7.jar





After You Start the InstallerThe installer takes several seconds to unzip and launch its JVM, then displays the welcome panel.

You can resize the wizard as necessary.

If you want to install using a proxy server, create or run an installation script or image, or change logging options, click Advanced Options and go to “Use Advanced Options” on page 49. If you want to install webMethods products without using any advanced options, click Next and go to “Specify Release, User Name, and Password” on page 54.



Start the Installer on a UNIX, IBM i5, or Mac SystemTo run the installer, the machine on which you are installing must have about 80MB of available virtual memory. If you are going to install many products or create an installation image for the same type of system on which you are running the installer, the installer needs more memory. If you are going to create an installation image for a different type of system, the installer needs still more memory.

The machine’s temporary directory must have about 100MB of available disk space. If you are going to install from an image, the directory must have enough additional available disk space to accommodate the image. For example, if the image is 200MB, the directory must have at least 250MB of available disk space. If necessary, you can specify a different directory to use as the temporary directory (see “Start the Installer and Specify a Different Temporary Directory” on page 47).

The commands shown below use the JVM options ‐Xmx512m and ‐Xincgc. The ‐Xmx option specifies the amount of memory to allow Java to use, while the ‐Xincgc option enables incremental garbage collection. If you want to allow Java to use more memory (for example, because you are creating an image), increase the amount you specify on the ‐Xmx option.

Start the InstallerLog in as the non‐root user. Open a command window, go to the directory to which you downloaded the installer, and start the installer by entering this command:

Start the Installer and Specify a Different Temporary DirectoryLog in as the non‐root user. Open a command window, go to the directory to which you downloaded the installer, and start the installer by entering this command:

java -Xmx512m -Xincgc -jar webMethodsInstaller7.jar -console

java -Xmx512m -Xincgc -Djava.io.tmpdir=/different_directory -jar webMethodsInstaller7.jar -console



After You Start the InstallerThe installer takes several seconds to unzip and launch its JVM, then displays the welcome panel.

You can resize the wizard as necessary.

If you want to install using a proxy server, create or run an installation script or image, or change logging options, click Advanced Options and go to “Use Advanced Options”, below. If you want to install webMethods products without using any advanced options, click Next and go to “Specify Release, User Name, and Password” on page 54.



Use Advanced OptionsWhen are you done setting advanced options, click OK. The installer closes the dialog box and returns to the welcome panel, where you can click Next to continue.

Create, Install from, or Edit an Installation ScriptFor information on installation scripts, see “Installation Scripts and Images” on page 41.

You can do the following from this panel:

Note: You can ignore the JVM tab. It is not used in this release.

To do this... Follow these steps...

Create script and install

Click Create script. In the Script file name field, enter the fully qualified name of the file in which to save the new script. You can specify any name, and you do not have to specify an extension.

Create script without installing

Click Edit script. In the Script file name field, enter the fully qualified name of the file in which to save the script. You can specify any name, and you do not have to specify an extension.



Create or Install from an Installation ImageFor information on installation images, see “Installation Scripts and Images” on page 41.

Create script from existing script without installing

Click Install from script. In the adjacent Script file name field, type the fully qualified name of the file that contains the existing script to use as a template for the new script.

Click Create script. In the adjacent Script file name field, type the the fully qualified name of the file to which to write the new script.

Install from script Click Install from script. In the Script file name field, type the fully qualified name of the file from which to install.

Note: If errors occur while the script is running, installation fails.

Edit script Click Edit script. In the Script file name field, type the fully qualified name of the file that contains the script to edit.

To do this... Follow these steps...

fully qualified name of file in which to save image (no file name extension required; if file does not exist, installer creates it

system for which to create image; can create image for any system from any system

fully qualified name of file that contains image from which to install



Use a Proxy Server to InstallIf your company connects to the Internet through an HTTP or Socks proxy server, you must use that proxy server to install. Your network administrator can provide information on your company’s proxy servers.

host name or fully qualified IP address

user name and password for installer to use to log on to proxy server

host name or fully qualified IP address



Change Logging Level and File, and Add TargetsBy default, the installer writes errors and warnings that occur during installation to a file named WmInstallLog.txt in the main installation directory (by default, webMethods7). You can increase or decrease the amount of information that is written, the file name, or the file location, and can choose to also write to standard out and standard error.

Verbose produces a 10 to 20MB file



Overwrite ProductsIf one or more of your webMethods products has been corrupted, or if you accidentally deleted some product files, you can replace the products by overwriting them.

If you want to save files you have created or customized, copy them to a different directory before using this option, then move the files back after the overwrite is complete.

Important! Only overwrite products in the most extreme cases. Overwriting not only overwrites a product, it overwrites all related files you have created or customized for the product. Never use this option to upgrade any product.



Specify Release, User Name, and Password

In the Release list, click 7.1.x and higher Provide the requested user name and password. Click Next. The installer connects to the webMethods server to download the webMethods products for which you have purchased licenses.



Specify the Installation Directory

Provide the requested information and then click Next.

If you are installing on a UNIX system as a non‐root user and are installing webMethods Broker, the userid under which you are logged in must have full read and write permissions to the directory you specify (for example, your home directory).

Windows only



Select Products to Install

The installer lists the webMethods products for which you have purchased licenses and that are supported on the target operating system. The highest level shows product names and releases and the lower levels show the items that make up or can be used with the product. If you have already installed a product or item in the specified installation directory, the item name is followed by the text (Installed) and the item name and its check box are grayed out.

Choose the webMethods products to install.

How to Choose ProductsYou can choose products using these methods:

Choose one or more development installations from the Roles list. The installer automatically selects the appropriate products and items for that task area in the product tree. You can then unselect items and choose other items. The products and items in each task area are listed in Chapter 1, “Development Environments”.

Choose every product and the minimum recommended set of items for each of those products by clicking Select Defaults.



Choose individual products and items directly from the product tree. When you choose a product, the installer automatically chooses the minimum recommended set of items for that product.

When you choose a product or item, the installer always automatically chooses other products and items that the selected product or item requires on the same machine, if those products and items do not already exist in the specified installation directory. For example, Trading Networks Server depends on Integration Server. If you select Trading Networks Server, and Integration Server does not already exist in the specified installation directory, the installer automatically selects Integration Server. If you are creating an installation image, you can unselect products and items that you are sure already exist on the target machine.

Some products require other products and items but not necessarily on the same machine. For example, in a production environment, you might install user interfaces and My webMethods Server on a machine other than the machines that host the products to which the user interfaces belong. The installer does not automatically select these required products and items. You must select them when you are installing on the proper machine.

Complete Product SelectionWhen you are done, click Next. If language packs are available for products you are installing or have already installed, the installer displays the language packs panel; if you want to install one or more, go to “Select Language Packs”, below.

If no language packs are available or you do not want to install any, read the license agreement that displays next. If you accept the terms, select the check box and click Next. If you are installing Trading Networks Server, Integration Server, Optimize, Infrastructure Data Collector, Metadata Library, webMethods Broker, or My webMethods Server, the installer displays configuration panels. Go to “Configure Products” on page 59 for instructions on completing the panels. If you are not installing any of these products, go to “Review and Install” on page 68.



Select Language Packs

webMethods products support multiple languages. You can install as many language packs as you want, and all of the languages installed (including the default, U.S. English) will be available to users. Select the language packs to install, and then click Next.

Read the license agreement. If you accept the terms, select the check box and click Next.

If you are installing Trading Networks Server, Integration Server, Optimize, Infrastructure Data Collector, Metadata Library, webMethods Broker, or My webMethods Server, the installer displays configuration panels. Go to “Configure Products”, below, for instructions on completing the panels. If you are not installing any of these products, go to “Review and Install” on page 68.



Configure ProductsIf you are installing any of the products listed below, the installer displays configuration panels.

Configure Trading Networks Server

Configure Integration Server

Configure Optimize

Configure Infrastructure Data Collector

Configure Metadata Library

Configure webMethods Broker

Configure My webMethods Server

For panels that include database connection parameters, the values you enter on one panel will be reflected on the next as you go forward through the installer the first time.

Some products require you to supply database connection information. For DB2, if the product will connect to a schema other than the default schema for the specified database user, you must specify these connection options in the URL:;AlternateId=schema;InitializationString="SET CURRENT PATH=schema"

AlternateID is the name of the default schema that is used to qualify unqualified database objects in dynamically prepared SQL statements.




database connection from Trading Networks Server to Trading Networks database component




If you are installing on a Windows system and will be using a version control system with Developer, you must install Integration Server as an application rather than a service.

You can install multiple Integration Servers on the same machine. On a Windows system, you can install only one of the Integration Servers as a service, but you can switch Integration Servers that you installed as applications to services after installation. For instructions, see the webMethods Integration Server Administrator’s Guide.

If you are going to use Integration Server as a standalone server (for example, as a reverse HTTP gateway or as the run time for an adapter), or you do not have an external RDBMS, or you want to get Integration Server up and running quickly, you can click Internal database. If you are going to cluster Integration Servers, if you need to create the IS Core Audit Log, Process Audit Log, Document History, or Process Engine database component (see Chapter 1, “Development Environments”), or if you want to use an external RDBMS for all Integration Server data, click External RDBMS and define the database connection.

start/shut down manually (Windows only)start/shut down automatically when start/shut down system (Windows only)

optional, can be supplied at startup



Configure OptimizeOptimize provides a central configurator that allows you to configure Optimize components from a central machine. Provide the port you want the central configurator to use to communicate with each Optimize component you are installing. Each port must be unique. If you install multiple instances of a component on the same machine, the port for each instance must be unique.

Note: You can switch from the embedded internal database to an external RDBMS later if necessary. For instructions, see the webMethods Integration Server Administrator’s Guide.

if you have multiple network interfaces, identify the one to use; default is default network interface for local machine; do not use localhost



Configure Infrastructure Data Collector

optional, can be supplied at startup

Broker for Infrastructure Data Collector to use to communicate with Optimize Analytic Engine




Important! If you specify the database connection, the Database user and Password are required.

start/shut down manually (WIndows only)start/shut down automatically when start/shut down system (Windows only)

database connection from Metadata Library to Metadata Reasoner, Metadata Repository database components




Create a Broker Server ConfigurationYou would not create the Broker Server configuration at this time (that is, using the installer) if you want to use a different storage size than is offered on the panel or if you want to create a combined storage session for configuration and run‐time data. If you do not need to back up configuration data without shutting down your Broker Server, using a combined session might save you a small amount of disk space. If you choose to not create the Broker Server configuration at this time, you must use create it after installation is complete, using instructions in the webMethods Broker Administrator’s Guide.

You would create the Broker Server at this time (that is, using the installer) if you want to use a storage size that is offered on the panel and you want to create separate storage sessions for configuration (metadata) and run‐time data. Using separate storage sessions minimizes the risk of corruption that goes with a combined storage location and enables you to back up configuration data without having to shut down your Broker Server. (For information about the webMethods Broker online configuration data backup tool, see the webMethods Broker Administrator’s Guide.)

Important! Software AG recommends creating separate sessions. You cannot later change from a combined session to separate sessions or vice versa.

if multiple Broker Servers on this machine, use different port for eachfull path to directory for Broker Server data; if multiple Broker Servers on one machine, use different data directory for each

if multiple Broker Monitors on this machine, use different port for each



Select a preconfigured storage session for the Broker Server that can handle your expected usage needs, as follows:

When determining the appropriate size for the log file, the factors to balance are Broker Server startup time and the desired maximum transaction size. The smaller the log file, the faster the startup; however, with a larger log file, you can send larger messages (that is, one larger‐sized single document or a batch of documents). If necessary, you can remove or replace log files after installation, and you can increase or decrease their size.

Startup time does not depend on the size of the storage file; additional storage capacity merely prevents the Broker Server from running out of room. After installation, if the amount of storage allocated turns out to be insufficient, you can add storage files and increase their size. You cannot remove storage files or decrease their size.

The webMethods Broker Administrator’s Guide provides instructions on working with log files and storage files.

Files Created When to UseBroker Server Startup Time

Small Configuration32MB log file 512MB storage file

Ideal for running development Broker Servers or relatively few production integrations, low document volumes, and no document logging

Fastest of all configurations

Medium Configuration64MB log file 4GB storage file

Standard deployment size, fits more cases than Small; larger maximum transaction size and twice the storage capacity of Small

Up to twice as long as for Small

Large Configuration128MB log file 8GB storage file

Suitable for production deployments with many integrations running at relatively high document volumes, possibly using document logging as well

Two times longer than for Medium; four times longer than for Small

*For complete information on Broker Server storage sessions, see the webMethods Broker Administrator’s Guide.)




start/shut down manually (WIndows only)start/shut down automatically when start/shut down system (Windows only)

database connection between My webMethods Server and My webMethods Server database component



Review and Install

Review the list of products and items you have selected for install. If the list is not correct, click Back until you reach the panel on which you chose the products to install and correct the choices. If the list is correct, click Next. The installer installs the products and related items, then displays the installation complete panel. Click Close.


7 Using Console Mode for Advanced Product Installation

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Specify Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Specify User Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74



Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76


Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81



OverviewThis chapter explains how to do the following on a UNIX, IBM i5, or Mac system using webMethods Installer console mode:

Install webMethods products from the webMethods Installer

Create an installation script or image from which to install webMethods products

Install webMethods products from an installation script or image.

You can use console mode to install locally or remotely on a UNIX or IBM i5 system, or locally on a Mac system.

The installer writes product, version, and build information to an audit history log file named history.text in the webMethods_directory\install\history\history.txt directory. If errors or warnings occur during installation, the installer writes them to a file named WmInstallLog.txt and stores the file in the main installation directory (by default, webMethods7). You can change logging behavior; for instructions, see “Start the Installer Using Advanced Options” on page 71.

Start the InstallerTo run the installer, the machine on which you are installing must have about 80MB of available virtual memory. If you are going to install many products or create an installation image for the same type of system on which you are running the installer, the installer needs more memory. If you are going to create an installation image for a different type of system, the installer needs still more memory.

The machine’s temporary directory must have about 100MB of available disk space. If you are going to install from an image, the directory must have enough additional available disk space to accommodate the image. For example, if the image is 200MB, the directory must have at least 250MB of available disk space. If necessary, you can specify a different directory to use as the temporary directory (see “Start the Installer and Specify a Different Temporary Directory” on page 71).

The commands shown below use the JVM options ‐Xmx512m and ‐Xincgc. The ‐Xmx option specifies the amount of memory to allow Java to use, while the ‐Xincgc option enables incremental garbage collection. If you want to allow Java to use more memory (for example, because you are creating an image), increase the amount you specify on the ‐Xmx option.

Note: When you run the webMethods Installer on an AIX system, you might receive Java messages during installation. You can ignore these messages.



Start the InstallerLog in as the non‐root user. Open a command window, go to the directory to which you downloaded the installer, and start the installer by entering this command:

Start the Installer and Specify a Different Temporary DirectoryLog in as the non‐root user. Open a command window, go to the directory to which you downloaded the installer, and start the installer by entering this command:

Start the Installer Using Advanced OptionsYou can add the parameters listed below in any order after ‐jar webMethodsInstaller7.jar.

Create, Install from, or Edit an Installation ScriptFor information on installation scripts, see “Installation Scripts and Images” on page 41.

java -Xmx512m -Xincgc -jar webMethodsInstaller7.jar -console

java -Xmx512m -Xincgc -Djava.io.tmpdir=/different_directory -jar webMethodsInstaller7.jar -console

Parameter Variables

Create a script and install-writeScript script_file Fully qualified name of the file in which to save the

script.

Create a script without installing-editScript script_file Fully qualified name of the file in which to save the

script.

Create a script from an existing script without installing-readScript script_file Fully qualified name of the file that contains the

existing script to use as a template.-writeScript script_file Fully qualified name of the file in which to save the

new script.

Edit a script-editScript script_file Fully qualified name of the file that contains the

script to edit.



Create or Install from an Installation Image For information on installation images, see “Installation Scripts and Images” on page 41.

Install from a script-readScript script_file Fully qualified name of the file that contains the

installation script from which to install.

Important! If any errors occur while an installation script is running, the installation fails.

Parameter Variables

Create an image-writeImage image_file Fully qualified name of the file in which to save the

installation image.-imagePlatform system System for which you are creating the image. You

can create an image for any system from any system. Valid values are as listed below. The default is the system on which you are running the installer.

System Value

Windows x86 WNT

Window AMD64, EM64T W64

Solaris SPARC SOL

Solaris AMD Opteron, Solaris for Intel x86

SOLAMD64

IBM AIX AIX

HP‐UX PA‐RISC HP11

HP‐UX Itanium 2 HP11IT

Linux x86 LNX

Linux AMD64, EM64T LNXAMD64

IBM i5 AS400

Mac OSX

Install from a image-readImage image_file Fully qualified name of the file that contains the

installation image from which to install.

Parameter Variables



Use a Proxy Server to InstallIf your company connects to the Internet through an HTTP or Socks proxy server, you must use that proxy server to install. Your network administrator can provide information on your company’s proxy servers.

Change Logging Level and File, and Add TargetsBy default, the installer writes errors and warnings that occur during installation to a file named WmInstallLog.txt in the main installation directory (by default, webMethods7). You can increase or decrease the amount of information that is written, the file name, or the file location, and can choose to also write to standard out and standard error.

Parameter Variables

Use an HTTP proxy server to install-proxyHost host Host name or fully qualified IP address of the

proxy server.-proxyPort port Port used by the proxy server.-proxyUser user User name for the installer to use to log on to the

proxy server.-proxyPass password Password for user.

Use a Socks proxy server to install-socksProxyHost host Host name or fully qualified IP address of the

proxy server.-socksProxyPort port Port used by the proxy server.

The default is the system on which you are running the installer.

Parameter Variables-debugLvl number Amount of information to log. Valid values are as

follows:

Amount of information to log Value

None 0

Errors only 5

All (verbose); produces a 10 to 20MB file

10

-debugFile debug_file Fully qualified name of the file to contain the logging information.

-debugOut Writes logging information to standard out as well as to file.



Overwrite ProductsIf one or more of your webMethods products has been corrupted, or if you accidentally deleted some product files, you can replace the products by overwriting them.

If you want to save files you have created or customized, copy them to a different directory before using this option, then move the files back after the overwrite is complete.

Specify ReleaseChoose to install from the 7.1.x and higher release.

Specify User Name and PasswordProvide the user name and password you use to log in to the webMethods Advantage Web site.

Specify the Installation DirectorySpecify the directory into which to install webMethods products.

If you are installing as a non‐root user and are installing webMethods Broker, the userid under which you are logged in must have full read and write permissions to the directory you specify (for example, your home directory).

-debugErr Writes logging information to standard error as well as to file.

-debug number Shorthand way to specify -debugErr -debugLvl number.

Important! Only overwrite products in the most extreme cases. Overwriting not only overwrites a product, it overwrites all related files you have created or customized for the product. Never use this option to upgrade any product.

Parameter Variables-overwriteInstall None.

Parameter Variables



Select Products to InstallThe installer lists the products for which you have purchased licenses and that are supported on the target operating system. The highest level shows product names and releases and the lower levels show the items that make up or are related to the product. If you have already installed an item in the specified installation directory, the item name is followed by a letter I.

Choose the webMethods products to install.

How to Select ProductsThe installer can display only a limited number of lines in the product tree at a time. To page forward through the product tree, enter a plus sign (+). To page backward through the product tree, enter a minus sign (‐). To search for a specific product or item, enter S, then enter the name of the product or item. Enter S again to find the next occurrence of the product or item.

You can choose products using these methods in any combination:

Choose a development installation from the Roles list that appears at the top of the product tree. The products and items in the task areas are listed in Chapter 1, “Development Environments”. Enter the number that appears next to the role. The installer automatically selects and shows an X next to each of the appropriate products and items for that task area in the product tree.

Choose the minimum recommended set of items for a product. Enter the number that appears next to the product heading (for example, enter the number for Integration Server). The installer automatically selects and shows an X next to each of the items listed under the product that have been designated as recommended.

Choose individual items from the product tree. Enter the number for each of the items (for example, enter the number for Program Files under Integration Server). You must enter each number on a separate line. The installer shows an X next to each item you select.

When you select all items listed under a product, the installer shows an X next to the product heading. If you select only some of the items listed under a product, the installer shows a pound sign (#) next to the product heading.

When you choose a product or item, the installer always automatically chooses other products and items that the selected product or item requires on the same machine, if those products and items do not already exist in the specified installation directory. For example, Trading Networks Server depends on Integration Server. If you select Trading Networks Server, and Integration Server does not already exist in the specified installation directory, the installer automatically selects Integration Server. If you are

Note: You might not see the selections until you page forward through the product tree.



creating an installation image, you can unselect products and items that you are sure already exist on the target machine.

Some products require other products and items but not necessarily on the same machine. For example, in a production environment, you might install user interfaces and My webMethods Server on a machine other than the machines that host the products to which the user interfaces belong. The installer does not automatically select these required products and items. You must select them when you are installing on the proper machine.

Complete Product SelectionWhen you are done, press ENTER twice. If language packs are available for products you are installing or have already installed, the installer prompts you to choose packs to install; if you want to install one or more, go to “Select Language Packs”, below.

If no language packs are available or you do not want to install any, read the license agreement and indicate whether you accept the terms. If you are installing Trading Networks Server, Integration Server, Optimize, Infrastructure Data Collector, Metadata Library, webMethods Broker, or My webMethods Server, the installer prompts for configuration information. Go to “Configure Products” on page 77 for instructions on providing the information. If you are not installing any of these products, go to “Review and Install” on page 81.

Select Language PackswebMethods products support multiple languages; you can install as many language packs as you want, and all of the languages installed (including the default, U.S. English) will be available to users. Select the language packs to install.

Read the license agreement and indicate whether you accept the terms.

If you are installing Trading Networks Server, Integration Server, Optimize, Infrastructure Data Collector, Metadata Library, webMethods Broker, or My webMethods Server, the installer prompts for configuration information. Go to “Configure Products”, below, for instructions on providing the information. If you are not installing any of these products, go to “Review and Install” on page 81.

Note: To see the entire license agreement, you might have to increase the number of lines that are visible in your console window.



Configure ProductsIf you are installing any of the products listed below, the installer prompts for configuration information.



Configure Optimize

Configure the Infrastructure Data Collector




Some products require you to supply database connection information; sample URL formats are shown below.

For DB2, if the product will connect to a schema other than the default schema for the specified database user, you must specify these connection options in the URL:;AlternateId=schema;InitializationString="SET CURRENT PATH=schema"


Configure Trading Networks ServerDefine the database connection for Trading Networks Server to use to connect to the Trading Networks database component. If you do not do so, Trading Networks will not start after installation.

RDBMS Sample URL Format

Oracle jdbc:wm:oracle://server:{1521|port};serviceName=service[;option=value …]

Oracle configured for RAC

jdbc:wm:oracle://server:{1521|port};serviceName=service;AlternateServers=(server:{1521|port};,…);ConnectionRetry=value; ConnectionDelay=value;LoadBalancing=value [;option=value …]

SQL Server jdbc:wm:sqlserver://server:{1433|port};databaseName=database [;option=value …]

DB2 for Linux, UNIX, Windows

jdbc:wm:db2://server:{50000|port};databaseName=database[;option=value …]

DB2 for iSeries jdbc:wm:db2://server:{446|port};locationName=location[;option=value …]



Configure Integration Server1 You can provide the Integration Server license key now, or you can provide it after

you start Integration Server.

2 Choose the database for Integration Server to use.

If you are going to use Integration Server as a standalone server (for example, as a reverse HTTP gateway or as the run time for an adapter), or you do not have an external RDBMS, or you want to get Integration Server up and running quickly, you can choose the embedded internal database.

If you are going to cluster Integration Servers; if you need to create the IS Core Audit Log, Process Audit Log, Document History, or Process Engine database component (see Chapter 1, “Development Environments”); or if you want to use an external RDBMS for all Integration Server data, choose the external RDBMS and define the database connection. If you do not provide the connection information, Integration Server will start after installation, but some features will not work.

Configure Optimize1 If you have multiple network interfaces, identify the one to use. Do not use localhost.

2 Optimize offers a central configurator that allows you to configure Optimize components from a single machine. Provide the port you want the central configurator to use to communicate with each Optimize component you are installing. Each port must be unique. If you install multiple instances of a component on the same machine, the port for each instance must be unique.

Configure the Infrastructure Data Collector1 You can provide the Infrastructure Data Collector license key now, or you can provide

it after you start Infrastructure Data Collector.

2 Identify the Broker for Infrastructure Data Collector to use to communicate with the Optimize Analytic Engine.

Configure Metadata Library1 Provide the port to use for the Metadata Library, or accept the default.

2 Define the database connection for Metadata Library to use to connect to the Metadata Repository and Metadata Reasoner database components. The database user and password are required. If you do not do specify the database connection, Metadata Library will not start after installation.

Note: You can switch from the embedded internal database to an external RDBMS later if necessary. For instructions, see the webMethods Integration Server Administrator’s Guide.



Configure webMethods Broker1 Identify the port on which to run the Broker Monitor. The default port is 6850. If you

install multiple Broker Monitors on this machine, specify a different port for each.

2 By default, Broker Monitor will bind to all IP addresses on the local machine. If necessary, bind Broker Monitor to a specific IP address instead.

3 Indicate whether you want to create the Broker Server.

You would not create the Broker Server configuration at this time (that is, using the installer) if you want to use a different storage size than is offered on the panel or if you want to create a combined storage session for configuration and run‐time data. If you do not need to back up configuration data without shutting down your Broker Server, using a combined session might save you a small amount of disk space. If you choose to not create the Broker Server configuration at this time, you must use create it after installation is complete, using instructions in the webMethods Broker Administrator’s Guide.

You would create the Broker Server at this time (that is, using the installer) if you want to use a storage size that is offered on the panel and you want to create separate storage sessions for configuration (metadata) and run‐time data. Using separate storage sessions minimizes the risk of corruption that goes with a combined storage location and enables you to back up configuration data without having to shut down your Broker Server. (For information about the webMethods Broker online configuration data backup tool, see the webMethods Broker Administrator’s Guide.) If you choose to create the Broker Server at this time, continue to step 4.

4 Enter the webMethods Broker license key provided by Software AG.

5 Identify the port on which to run the Broker Server. The default port is 6849. If you install multiple Broker Servers on this machine, specify a different port for each.

6 Provide the full path to the data directory in which to store Broker Server data. If you install multiple Broker Servers on this machine, specify a different data directory for each.

Important! Software AG recommends creating separate sessions. You cannot later change from a combined session to separate sessions or vice versa.



7 Select a preconfigured storage session for the Broker Server that is adequate for your expected usage needs.

When determining the appropriate size for the log file, the factors to balance are Broker Server startup time and the desired maximum transaction size. The smaller the log file, the faster the startup; however, with a larger log file, you can send larger messages (that is, one larger‐sized single document or a batch of documents). If necessary, you can remove or replace log files after installation, and you can increase or decrease their size.

Startup time does not depend on the size of the storage file; additional storage capacity merely prevents the Broker Server from running out of room. After installation, if the amount of storage allocated turns out to be insufficient, you can add storage files and increase their size. You cannot remove storage files or decrease their size.

The webMethods Broker Administrator’s Guide provides instructions on working with log files and storage files.

8 Specify where to install the Broker Monitor. The Broker Monitor controls the Broker Server; when the Broker Monitor starts or shuts down, it starts or shuts down the Broker Server.

Files Created When to UseBroker Server Startup Time

Small Configuration32MB log file 512MB storage file

Ideal for running development Broker Servers or relatively few production integrations, low document volumes, and no document logging

Fastest of all configurations

Medium Configuration64MB log file 4GB storage file

Standard deployment size, fits more cases than Small; larger maximum transaction size and twice the storage capacity of Small

Up to twice as long as for Small

Large Configuration128MB log file 8GB storage file

Suitable for production deployments with many integrations running at relatively high document volumes, possibly using document logging as well

Two times longer than for Medium; four times longer than for Small

*For complete information on Broker Server storage sessions, see the webMethods Broker Administrator’s Guide.



Configure My webMethods Server1 Provide the port to use for My webMethods Server, or accept the default.

2 Define the database connection for My webMethods Server to use to connect to the My webMethods Server database component. If you do not do so, My webMethods Server will not start after installation.

Review and InstallReview the list of products you have chosen to install. If the list is correct, press ENTER. The installer installs the products and related items.


8 Preparing for Database Component Configuration

webMethods Products and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Database Users and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Database Administrator Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Character Set and Sort Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Page and Block Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Set Database Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Download the Database Scripts and Database Component Configurator . . . . . . . . . . . . . . . . . . 88

Change Environment Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Default Storage Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Database Component Descriptions and Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . 90



webMethods Products and DatabaseswebMethods products use Java Database Connectivity (JDBC) to interact with databases; specifically, to query and update data in webMethods database components. A webMethods database component is a grouping of database objects that can be used by one or more webMethods products. For example, Integration Servers write process status data to the Process Audit Log database component; My webMethods Server reads the data from the Process Audit Log database component and passes it to My webMethods to display.

You must use the DataDirect Connect JDBC 3.6 driver with webMethods products. All webMethods products come with the client component of this driver; it is a Type 4 JDBC native‐protocol driver that does not have a server component. The products use the driver to convert JDBC requests from Java programs directly into the vendor‐specific database protocol that each type of RDBMS can understand. webMethods products execute DDL commands at install time and sometimes design time for each RDBMS with which they interact.

To enable webMethods products to interact with a database component, you provide database connection parameters, usually during product installation, and the installer uses the parameters to configure JDBC connection pools. After product installation and database component creation is complete, you set up the products to use the appropriate connection pools. For some products, such as Optimize, you configure the JDBC connection pools after product installation. Tasks you perform after product installation are covered in Chapter 10, “Completing the Installation”.

For the list of RDBMSs supported by the webMethods product suite, see the webMethods System Requirements.

Database Users and StorageYou can create a single database user for all webMethods database components or you can create a database user for each database component. You can create all database component objects in the same storage or you can create the objects for each database component in its own storage. The following chapters provide instructions for creating database users and storage.

Note: If you want webMethods products to exchange data with non‐webMethods databases, you can use the webMethods JDBC Adapter. For more information, see the webMethods JDBC Adapter documentation.



Database Administrator AccountYou need DBA access only if you want to use the webMethods Database Component Configurator to create the necessary database users and storage objects.

webMethods products are designed to use the database users you create for the database components.

Character Set and Sort OrderwebMethods products are globalized and support Unicode. Software AG strongly recommends choosing a Unicode encoding for your database and the most appropriate sort order for your environment. A database character set determines which languages a database can represent. Database sort order determines collation and comparison behavior.

The sections below list the most appropriate Unicode character encoding and sort order for each RDBMS that the webMethods product suite supports. If you want to use a different character set or sort order than recommended below, consult your database administrator and your RDBMS vendor’s documentation so you can carefully choose a database character set that supports the languages your data is in.

If you use the webMethods Database Component Configurator to create your database components, you can check whether the selected RDBMS is configured for the Unicode character set. If the RDBMS does not support Unicode, the configurator lists the character set the RDBMS does support.

OraclewebMethods database schemas for Oracle use character data types. For character data types, Oracle supports the UTF8 and AL32UTF8 Unicode encodings. While UTF8 is CESU‐8‐compliant and supports the Unicode 3.0 UTF‐8 Universal character set, AL32UTF8 conforms to the Unicode 3.1 or higher UTF‐8 Universal character set. For nchar data types, Oracle supports the AL32UTF8 and AL16UTF16 Unicode encodings. The supported Unicode version for AL32UTF8 depends on the Oracle database version. webMethods’ Oracle database schemas do not have linguistic indexes. Software AG recommends these character sets and sort order:

Important! You must set character set and sort order before creating webMethods storage.

For... Software AG recommends...

Character set AL32UTF8

Nchar character set AL16UTF16

Sort order Binary



You can check database configuration and session settings by viewing the SYS.NLS_DATABASE_PARAMETERS or V$NLS_PARAMETERS parameter.

SQL ServerwebMethods database schemas for SQL Server use nchar data types. SQL Server provides support for UTF‐16 through its nchar data types. Since nchar data types are always in UTF‐16, you do not have to perform any special database configuration and can choose the most appropriate code page for your environment as a database character set. Software AG recommends these character sets and sort order:

You can check the database configuration using the sp_helpdb database stored procedure.

DB2webMethods database schemas for DB2 use character data types. DB2 supports UTF‐8 for character data types and UTF‐16 for graphic data types. Software AG recommends these character sets and sort order:


Character set The appropriate encoding for the languages your data is in.

Nchar character set UTF‐16

Sort order Any case‐insensitive collation type.

Important! If you do not choose a case‐insensitive sort order, you will not be able to create some database components in SQL Server.


Character set CCSID 1208 (UTF‐8)

Note: My webMethods Server requires this character set.

Graphic Character Set UTF‐16

Sort order IDENTITY_16BIT

Note: This sort order ensures the same sorting result for both character and graphic data types. This option is only available for DB2 for Linux, Unix, Windows. For DB2 for iSeries, sort order is always binary order when the database character set is UTF‐8.



You can check the database configuration by using the following:

Page and Block SizeUse the page and block sizes specified below for each type of RDBMS.

Set Database Options

OracleFor webMethods products to function properly, you must set the NLS_LENGTH_SEMANTICS initialization parameter to BYTE.

SQL ServerThe following database settings are required for webMethods products to function properly:ALTER DATABASE database_name SET ALLOW_SNAPSHOT_ISOLATION ON;ALTER DATABASE database_name SET READ_COMMITTED_SNAPSHOT ON;

By default, SQL Server uses case‐insensitive collations. If you create the My webMethods Server database component, do not change this option from the default; My webMethods Server does not support case‐sensitive collations.

RDBMS Use...

DB2 for Linux, Unix, Windows

GET DATABASE CONFIGURATION command

DB2 for iSeries DSPFD command to check the database file description

RDBMS Required Page and Block Size Default

Oracle 8k page/block size 8k

SQL Server 8k page/block size 8k

DB2 32k page size 4k

Important! webMethods uses BYTE rather than CHAR semantics because BYTE is the default configuration of Oracle database and is used by most Oracle users. If you try to use webMethods products with CHAR semantics, unexpected results might occur. For example, since CHAR semantics allow storage of longer data than BYTE semantics (for Japanese, varchar(12 byte) takes four characters in UTF8 while varchar(12 char) takes 12), using CHAR semantics could cause the buffer in some products to overflow.



Download the Database Scripts and Database Component ConfiguratorThe database scripts and the Database Component Configurator are available through the webMethods Installer. For complete instructions on using the webMethods Installer, see previous chapters in this guide.

1 Download the webMethods Installer from the webMethods Advantage Web site to the appropriate machine, as follows:

2 Start the webMethods Installer.

3 In the product selection list, select Database Component Configurator.

If you are going to create database components using... Download the webMethods Installer to...

Scripts A machine equipped with the database client for your type of RDBMS


Any machine on the same network as your database server




Change Environment SettingsThe Database Component Configurator has the default environment settings shown below. If necessary, you can change them as described below.

1 Go to the webMethods_directory\common\db\bin directory.

2 Open the setEnv.{bat|sh} file in the text editor and edit the fields as necessary.


Default Storage ConventionBy default, all webMethods database components follow this storage convention:

If you want to use a different storage convention during database component creation, modify the values listed above in the database component SQL scripts. The scripts are located in the webMethods_directory\ common\db\scripts directory.

You can modify webMethods storage convention by directly modifying the scripts. Commercial and public domain utilities provide search and replace functionality across subdirectories. The webMethods product suite supports all tablespace configurations deployed by customers.

SettingDetermines whether the Database Component Configurator... Default

‐DtermOutOn Writes execution information to the console.

true

‐DspoolOn Logs execution information. true

‐DlogLevel Sets the log level to INFO (high‐level information) or DEBUG (more detailed information, including internal processing and SQL calls).

INFO

‐Dlog.dir This setting specifies the full path to the directory in which to store the log files. Make sure you have permission to write to this directory.

webMethods_directory\common\db\logs

RDBMS Data Storage Unit Index Storage Unit BLOB Storage Unit

Oracle tablespaces WEBMDATA WEBMINDX WEBMDATA

SQL Server filegroups Primary Primary Primary

DB2 for Linux, UNIX, Windows tablespaces

WEBMDATA WEBMINDX WEBMBLOB

DB2 for iSeries Default Default Default



Database Component Descriptions and Installation RequirementsEach section below provides brief descriptions of database components, followed by installation requirements.

Cross Reference, Document History, IS Internal, and IS Core Audit Log Database Components

If you are clustering Integration Servers, create one of each of the following database components for the cluster to share: IS Internal, Cross Reference, Document History, and IS Core Audit Log.

If you are not clustering Integration Servers, create a separate Cross Reference database component, Document History database component, and IS Internal database component for each Integration Server. You can create a separate IS Core Audit Log database component for each Integration Server or you can create a single IS Core Audit Log database component for the Integration Servers to share.

Note: For detailed information on concepts mentioned in the sections below, see the relevant product documentation.

Note: If you chose to use the embedded IS Internal database during installation, you can skip this section.

Database Component Data that Integration Server Writes

IS Internal Scheduled tasks and client certificate mappings, and run‐time data for pub.storage services, guaranteed delivery, trigger joins, and the scheduler.

Cross Refer‐ence

Cross‐referencing data for publish‐and‐subscribe solutions.

Document History

Document history information for exactly‐once processing in publish‐and‐subscribe solutions. Integration Server uses the information to detect and reject duplicate documents.

IS Core Audit Log

Error, guaranteed delivery, service, and session audit data. If you are using triggers, Integration Server also stores documents that are in doubt, have failed, and or have exhausted trigger retries. Integration Server Administrator and My webMethods display different parts of the data.



Process Audit Log Database ComponentProcess Engines write process status data and Task Engines write task status data to the Process Audit Log database component. Third‐party products can also send process execution data to this database component. Optimize Analytic Engines read process data so they can analyze capabilities such as transition duration and write data about analysis‐enabled processes. My webMethods displays the data.

If you are clustering Process Engines, create a single Process Audit Log database component for the cluster to share. If you are not clustering Process Engines, you can create either a separate Process Audit Log database component for each Process Engine or a single Process Audit Log database component for the Process Engines to share.

Create a single Process Audit Log database components for all Task Engines to share.

If you are using Process Engines, Task Engines, Optimize Analytic Engines, or some combination of these, create a single Process Audit Log database component for all to share.

Process Engine Database ComponentProcess Engines write process execution data to this database component.

If you are clustering Process Engines, create a single Process Engine database component for the cluster to share. If you are not clustering Process Engines, create a separate Process Engine database component for each Process Engine.

Archive Database ComponentArchiving functionality available through Monitor can archive data from the IS Core Audit Log database component, the Process Audit Log database component, or both to the Archive database component.

The Archive database component creates a copy of the IS Core Audit Log and Process Audit Log database components in the same database or schema; it archives the data from the sources to these copies. You must create Archive in the same type of RDBMS as the source IS Core Audit Log and Process Audit Log database components.

If you are using DB2, you must create Archive in the same database as the source IS Core Audit Log and Process Audit Log database components.

If you are using Oracle or SQL Server, you can create Archive in a different database server than the source IS Core Audit Log and Process Audit Log database components, and then create a DBlink name for Archive to use to link to each source. If IS Core Audit Log and Process Audit Log are on the same database server, Archive can use the same DBLink to connect to both sources.



Metadata Reasoner and Metadata Repository Database ComponentsMetadata Library writes and reads metadata required to find or reuse assets to and from these database component. The metadata can come from Designer, Integration Server, or a UDDI registry. The metadata in the two database components differs in that it is optimized for different operations.

Create one Metadata Reasoner database component and one Metadata Repository database component for Metadata Library.

My webMethods Server Database ComponentMy webMethods Server writes data about deployment, configuration, security, portal pages, and run‐time operations to this database component; it uses this data to manage My webMethods user interfaces. The Task Engine writes task status, task distribution, and business data.

If you are clustering My webMethods Servers, create a single My webMethods Server database component for the cluster to share. If you are not clustering My webMethods Servers, create a separate My webMethods Server database component for each My webMethods Server.

Trading Networks and Trading Networks Archive Database ComponentsTrading Networks Server writes metadata (partner profiles, trading partner agreements, document types, processing rules, and partner profile groups) and run‐time data (documents; document content parts, attributes, and delivery information) to the Trading Networks database component. Trading Networks Server also logs entries about document processing steps. Trading Networks Console displays data. Trading Networks archiving functionality can archive data from the Trading Networks database component to the Trading Networks Archive database component.

If you are clustering Trading Networks Servers, create a single Trading Networks database component for the cluster to share. If you are not clustering Trading Networks Servers, create a separate Trading Networks database component for each Trading Networks Server. Create the Trading Networks Archive database component in the same database as the source Trading Networks database component.

Analysis and Process Tracker Database ComponentsOptimize Analytic Engines write computed analytics and process and monitoring data received from Infrastructure Data Collectors and Web Service Data Collectors to the Analysis database component. Optimize Prediction Engines evaluate the data and generate prediction events. My webMethods displays the data.



Optimize Analytic Engines write business and process data received from Process Engines and Web Service Data Collectors to the Process Tracker database component. My webMethods displays the data.

Create a single Analysis database component and a single Process Tracker database component for all Optimize Analytic Engines to share.

Staging and Reporting Database ComponentsMonitor populates these database components with data from the Process Audit Log database component. You can then generate reports that contain aggregated data about processes and tasks.

You can create the Reporting and Staging database components in the same database. However, the services that populate the Reporting database component consume large amounts of CPU. For best performance, install the Reporting or Staging database components on a database server that will not adversely affect the Process Audit Log or the Process Engine database components.

Infrastructure Database ComponentsThe table below lists infrastructure database components that are automatically created when you create product‐related database components.

The Storage database component creates default webMethods storage structures, such as tablespaces and user credentials, for all database components.

Database Component and Version Description

Component Tracker

Tracks the database components that are created or dropped.

DataPurge Provides a common method for purging data from the Analysis and Process Tracker database components.

Database Management

Provides core routines for data purge functionality.

Distributed Locking

Coordinates access to resources across a distributed collection of servers and processes. Resources can be locked for exclusive use, to prevent another server from accessing the resource as it is being updated, or for shared use, to prevent another server from updating the resource as it is being accessed.

Operation Management

Provides a common method for configuration, logging, and error handling for any database component.


9 Creating and Dropping Database Components

Use the Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Use the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Use Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110



Use the Graphical User InterfaceThis section explains how to use the Database Component Configurator graphical user interface to create or drop a database user and storage, and to create or drop webMethods database components. Each run of the configurator operates on a single schema.

When specifying the URL for DB2, if the product will connect to a schema other than the default schema for the specified database user, you must specify these connection options in the URL:;AlternateId=cschema;InitializationString="SET CURRENT PATH=schema"


The configurator writes execution information to the Results tab and to a log file named dcc_yyyymmddHHMMss in the webMethods_directory\common\ db\logs directory.



Create Database Components and Create a Database User and StorageYou can use the configurator to create a database user and storage in Oracle, SQL Server, and DB2 for Linux, UNIX, Windows. For DB2 for iSeries, you must create the database user and storage using scripts (see “Use Database Scripts” on page 110).

1 On the Start menu, go to Programs webMethods7 Tools Database Component Configurator.

Initially, some of the fields on the the Inputs tab show values you entered for the same fields in the webMethods Installer during product installation. You can change these values and specify other field values.

If you intend to run the configurator more than once, you can set the current field values as the defaults for subsequent runs by clicking Save Settings as Default. You can also export field values to .xml files by clicking Export, then later import the values from a file by clicking Import Configuration. In each case, the values for the two Password fields are not saved.



2 In the Action Type list, click the action to perform, as follows:

3 In the Database Component list, select a product whose database components to create, select one database component to create, or choose to create all database components.

The product options map to the database components listed below.

4 The contents of the Version list vary based on your choice in the Database Component list, as follows:

If you selected a product in the Database component list, click 7.1 in the Version list.

If you selected a database component in the Database component list, click the proper version for your product (see Chapter 1, “Development Environments”).

If you selected ALL in the Database component list, click Latest in the Version list. The will create the latest version of all the webMethods database components.

Option Action

catalog Displays existing database components on the Results tab.create Creates the database components you select in the Database

component list, and lets you create a database user and storage.recreate Drops, then re‐creates, the database components you select in the

Database component list.checkEncoding Checks whether your RDBMS is configured for the Unicode

character set. If it is not, lists the character set the RDBMS does support on the Results tab.

Product Database Components

Integration Server IS Core Audit Log, IS Internal, Process Audit Log, Document History, Process Engine, Staging, Reporting, and Cross Reference

Metadata Library Metadata Repository and Metadata Reasoner

My webMethods Server My webMethods Server

Optimize Analysis, Process Tracker, and Process Audit Log

Trading Networks Trading Networks



5 Specify the connection for the configurator to use to connect to the RDBMS.

a In the RDBMS list, click the RDBMS in which to create the database components.

b In the URL field, provide the URL for the RDBMS. Sample URL formats are displayed.

c If you are going to create a database user and storage in Oracle or SQL Server, specify the database user and password to create. If you are going to create a database user and storage in DB2 for Linux, UNIX, Windows, specify the OS user to which to grant permissions. If you are not going to create a database user and storage, specify an existing database user and password.

6 If you selected create in the Action Type list, you can create a database user and storage.

a Select the Create tablespaces and database user check box.

b In the Admin ID field, identify the database user or operating system user that has database administrator credentials to create the database user and storage. Supply the password for the user in the Admin password field.

c For DB2 for Linux, UNIX, Windows, in the Tablespace directory field, identify the directory in which to create the tablespaces.

For Oracle, use the Tablespace directory field only if the DB_CREATE_FILE_DEST parameter is not set for your Oracle instance.

For SQL Server, in the Database field, specify the database to create.

7 Click Execute. The execution information is displayed on the Results tab and is written to the log file dcc_yyyymmddHHMMss in the webMethods_directory\common\db\logs directory.

Drop Database ComponentsBefore dropping, shut down all webMethods products that are connected to the database component and back up the database component.


2 In the Action list, click the action to perform, as follows:

Important! If you are using Oracle, and are going to create storage and the Data Purge database component, you must specify the sysLoginRole connection option on the URL (for example, ;sysLoginRole=sysdba).

Value Action

catalog Displays existing database components on the Results tab.drop Drops the database components you select in the Database component

list.



3 In the Database Component list, select a product whose database components to drop, select one database component to drop, or choose to drop all database components.

4 The contents of the Version list vary based on your choice in the Database Component list, as follows:

If you selected a product in the Database component list, click 7.1 in the Version list.

If you selected a database component in the Database component list, click the proper version for your product (see Chapter 1, “Development Environments”).

If you selected ALL in the Database component list, click Latest in the Version list.


a In the RDBMS list, click the RDBMS from which to drop the database components.


c Specify the database user and password to use to connect to the RDBMS in the User ID and Password fields.


Drop the Storage and Revoke Database User PermissionsIf you drop all database components in a schema, you can drop the storage and revoke the database user permissions.

You can use the configurator to drop the storage for Oracle, SQL Server, and DB2 for Linux, UNIX, Windows. For DB2 for iSeries, you must drop the database user and storage using a script (see “Use Database Scripts” on page 110).


2 In the Action list, click drop.

3 In the Database component list, click ALL.


a In the RDBMS list, click the RDBMS from which to drop the database components.


c Specify the database user and password to use to connect to the RDBMS in the User ID and Password fields.



5 Select the Drop tablespaces and database user check box.

a In the Admin ID field, identify the database user or operating system user that has database administrator credentials to drop the database user and storage. Supply the password for the database user in the Admin password field.

b For DB2 for Linux, UNIX, Windows, and Oracle, in the Tablespace directory field, identify the directory that contains the tablespaces to drop. For SQL Server, in the Database field, specify the database to create.


Use the Command LineThis section explains how to use Database Component Configurator command line mode to create or drop a database user and storage, and to create or drop webMethods database components. Each run of the configurator operates on a single schema.

Command line mode lets you create a database user and storage in Oracle, SQL Server, and DB2 for Linux, UNIX, Windows. For DB2 for iSeries, you must create the database user and storage using scripts (see “Use Database Scripts” on page 110).

Before dropping any database component, shut down all webMethods products that are connected to the database component.

If you have dropped all the database components from a schema, you can drop the storage and revoke the database user permissions. You can use the command line to drop storage for Oracle, SQL Server, and DB2 for Linux, UNIX, Windows. For DB2 for iSeries, you must drop storage using scripts (see “Use Database Scripts” on page 110).



Database Component Configurator CommandYou can perform an action on one database component or on all database components, or on the database components for one webMethods product, using the command below. You run the command from the webMethods_directory\common\db\bin directory.

dbConfigurator.{bat|sh} {-a|--action} action {-d|--dbms} {oracle|sqlserver|db2luw|db2i}{{-c|--component} db_component {-v|--version} version | {-pr|--product} product {-v|--version} release}{-l|--url} RDBMS_URL{-u|--user} db_user {-p|--password} password[{-au|--admin_user} db_admin_user {-ap|--admin_password} password]

Additional Parameters:[-r|--runCatalog][-t|--tablespacedir][-n|--dbname][-h|--help][-ab|--about][-pa|--printActions] [-pd|--printDatabase] [-pc|--printComponents][-pp|--printProducts] [-pe][{-e|--export|-i|--import} {-dir|--configdir} directory {-file| --configfile} file]

Parameter Entry{-a|--action} action Action to perform.

Value Action

catalog Displays existing database components.create Creates db_component or the database

components for product.drop Drops db_component or the database

components for product.

Important! Before dropping, you must shut down all webMethods products that are connected to the database component and back up the database component.

recreate Drops db_component or the database components for product, then creates db_component or the database components for product.

checkEncoding Checks whether the RDBMS specified on the command is configured for the Unicode character set. If it is not, lists the supported character set.



{-d|--dbms} {oracle|sqlserver|db2luw|db2i}

RDBMS on which to perform action.

Value DBMS

oracle Oraclesqlserver SQL Serverdb2luw DB2 for Linux, UNIX, Windowsdb2i DB2 for iSeries

{-c|--component} db_component {-v|--version} version

Database component version for which to perform action.

For db_component, you can specify the database component code or name.

Code Name

ALLANLARCCTRXRFDTPDBMDSLIDRISCISIMTRMTDMWSOPMPRAPREPTRPRPPSTSTRTNSTNA

All database componentsAnalysisArchiveComponentTrackerCrossReferenceDataPurgeDatabaseManagementDistributedLockingDocumentHistoryISCoreAuditISInternalMetadataReasonerMetadataRepositoryMywebMethodsServerOperationManagementProcessAuditProcessEngineProcessTrackerReportingStagingStorageTradingNetworksTradingNetworksArchive

Parameter Entry



For version, you can specify these values.

Value Description

latest If you specified one database component for db_component, perform action for the latest version of db_component.

If you specified ALL for db_component, you must specify latest for db_component_version. The configurator will create the latest version of each database component.

version If you are performing action on a database component other than Storage, specify the version of the database component (see Chapter 1, “Development Environments”).

{-pr|--product} product {-v|--version} release

Product release for whose database components to perform action.

For product, you can specify the product code or name.

Code or Product Maps to These Database Components

IS or Integration Server

IS Core Audit Log, IS Internal, Process Audit Log, Document History, Process Engine, Staging, Reporting, and Cross Reference

ML or Metadata Library

Metadata Repository and Metadata Reasoner

MWS or My webMethods Server


OPTI or Optimize

Analysis, Process Tracker, and Process Audit Log

TN or Trading Networks

Trading Networks

Parameter Entry



For release, you can specify the values below.

Value Description

latest Perform action on the database components for the latest release of product.

release Release of the product for whose database components to perform action. The configurator will create the correct versions of the database components for the specified release.

{-l|--url} RDBMS_URL URL for the RDBMS.

RDBMS Sample Format

Oracle jdbc:wm:oracle://server:{1521|port};serviceName=service[;option=value …]

Important! If are going to create storage and the Data Purge database component, you must specify the sysLoginRole connection option on the URL (for example, ;sysLoginRole=sysdba).

SQL Server jdbc:wm:sqlserver://server:{1433|port};databaseName=database[;option=value …]



DB2 for iSeries jdbc:wm:db2://server:{446|port};locationName=location[;option=value …]

Parameter Entry



Important! When working with database components on UNIX systems, you must enclose the URL in double quotes.

Important! For DB2, if you are creating database components in a schema other than the default schema for the specified database user, you must specify these connection options in the URL:

;AlternateId=schema;InitializationString="SET CURRENT PATH=schema"


{-u|--user} db_user {-p|--password} password

If you are creating a database user and storage in Oracle or SQL Server, specify the database user and password to create. If you are creating a database user and storage in DB2 for Linux, UNIX, Windows, specify the OS user to which to grant permissions.

If you are not creating a database user and storage, specify an existing database user and password.

[{-au|--admin_user} db_admin_user{-ap|--admin_password} password]

If you are creating a database user and storage, specify the database user or operating system user and password that has the necessary database administrator credentials.

Additional Parameters[-r|--runCatalog] Runs the catalog action at the end of every execution.[-t|--tablespacedir] If you are creating a database user and storage, and want to

create a tablespace directory for DB2 for Linux, UNIX, Windows, or Oracle, full path to the directory. For Oracle, use this parameter only if the DB_CREATE_FILE_DEST parameter is not set for your Oracle instance.

[-n|--dbname] If you are creating a database user and storage in SQL Server, name of the target database.

[-h|--help] Prints command line help.[-ab|--about] Prints information about the Database Component

Configurator.[-pa|--printActions] Lists the actions you can perform, like create or drop.[-pd|--printDatabase] Prints RDBMS the configurator supports.[-pc|--printComponents] Prints database components the configurator supports.

Parameter Entry



Examples

Create a Database User and StorageThis command creates the two webMethods tablespaces and the database user for Oracle:

This command creates the webMethods database and database user for SQL Server:

This command creates the webMethods bufferpool and tablespaces, and grants permissions for DB2:

[-pp|--printProducts] Prints webMethods products the configurator supports.[-pe] Prints command line examples.{-e|--export}{-dir|--configdir} directory{-file|--configfile} file

Exports values for all required parameters except the password parameters to an .xml file.

{-i|--import}{-dir|--configdir} directory{-file|--configfile} file

Imports values for all parameters from an .xml file.

Note: Password parameters are not saved, so you must specify them on the command.

Important! On UNIX systems, you must enclose the RDBMS URL in double quotes.

dbConfigurator.bat -a create -d oracle -c storage -v latest -l jdbc:wm:oracle://DBserver:1521;serviceName=myservicename -au adminuser -ap adminpass -u webmuser -p w3bmpass -t tablespace_dir

dbConfigurator.bat -a create -d sqlserver -c storage -v latest -l jdbc:wm:sqlserver://DBserver:1433;databaseName=master -u webmuser -p w3bmpass -au sa -ap sa_password -n webmdb

dbConfigurator.bat -a create -d db2luw -c storage -v latest -l jdbc:wm:db2://vmxpdb01:50000;databaseName=amol -u webmuser -au adminuser -ap admin_password -t tablespace_dir

Parameter Entry



Drop the Storage and Revoke Database User PermissionsIf you drop all database components in a schema, you can drop the storage and revoke the database user permissions.

You can use the configurator to drop the storage for Oracle, SQL Server, and DB2 for Linux, UNIX, Windows. For DB2 for iSeries, you must drop the database user and storage using a script (see “Use Database Scripts” on page 110).

This command drops the two webMethods tablespaces for Oracle:

This command drops the webMethods database for SQL Server:

This command drops the webMethods bufferpool and tablespaces, and revokes permissions for DB2:

Create Database ComponentsThis command creates Process Audit Log v30 in Oracle:

This command recreates (drops and then creates) the latest versions of all database components in SQL Server:

This command displays the database components that currently exist in DB2 for Linux, UNIX, Windows:

dbConfigurator.bat -a drop -d oracle -c storage -v latest -l jdbc:wm:oracle://DBserver:1521;serviceName=myservicename -au adminuser -ap adminpass -u webmuser -p w3bmpass -t tablespace_dir

dbConfigurator.bat -a drop -d sqlserver -c storage -v latest -l jdbc:wm:sqlserver://DBserver:1433;databaseName=master -u webmuser -p w3bmpass -au sa -ap sa_password -n webmdb

dbConfigurator.bat -a drop -d db2luw -c storage -v latest -l jdbc:wm:db2://vmxpdb01:50000;databaseName=amol -u webmuser -au adminuser -ap admin_password -t tablespace_dir

dbConfigurator.bat -a create -d oracle -c processaudit -v 30 -l jdbc:wm:oracle://DBserver:1521;serviceName=myservicename -u webmuser-p w3bmpass

dbConfigurator.bat -a recreate -d sqlserver -c all -v latest -l jdbc:wm:sqlserver://DBserver:1433;databaseName=webmdb -u webmuser -p w3bmpass

dbConfigurator.bat -a catalog -d db2udb -l jdbc:wm:db2://DBserver:50000;databaseName=webmdb -u webmuser -p w3bmpass



This command creates the latest database components in DB2 when creating in ALTSCHEMA rather than the default schema for the specified database user:


You cannot drop the Component Tracker database component using the configurator; you must use a script. For instructions, see “Use Database Scripts” on page 110.

This command drops Process Audit Log v30 from Oracle:

This command drops the latest versions of all database components from SQL Server:

The command drops the latest version of the Analysis database component from DB2 for Linux, UNIX, Windows:

This command drops the latest version of the Analysis database component from DB2 when dropping from ALTSCHEMA rather than the default schema for the specified database user:

dbConfigurator.bat -a create -d db2luw -c all -v latest -l “jdbc:wm:db2://DBserver:50000;databaseName=webmdb;AlternateId=ALTSCHEMA;InitializationString=\”SET CURRENT PATH=ALTSCHEMA\”” -u webmuser -p w3bmpass

dbConfigurator -a drop -d oracle -c processaudit -v 30 -l jdbc:wm:oracle://myserver:1521;serviceName=myservicename -u webmuser -p w3bmpass

dbConfigurator.bat -a drop -d sqlserver -c core -v latest -l jdbc:wm:sqlserver://myserver:1433;databaseName=webmdb -u webmuser -p w3bmpass

dbConfigurator.bat -a drop -d db2luw -c analysis -v latest -l jdbc:wm:db2://DBserver:50000;databaseName=webmdb -u webmuser -p w3bmpass

dbConfigurator.bat -a drop -d db2luw -c analysis -v latest -l jdbc:wm:db2://DBserver:50000;databaseName=webmdb;AlternateId=ALTSCHEMA;InitializationString="SET CURRENT PATH=ALTSCHEMA" -u webmuser -p w3bmpass



Use Database ScriptsThis section explains how to use SQL scripts provided by webMethods to create a database user and storage, drop storage and revoke the database user permissions, and to create or drop webMethods database components. You run the scripts, stored in the webMethods_directory\common\db\scripts directory, from your database client.

To determine which scripts to run, go to the webMethods_directory\common\db\bin directory and run the appropriate command below. The order in which the scripts are listed is the order in which you should run them. For explanations of the fields in the commands below, see “Database Component Configurator Command” on page 102.

Create a Database User and StorageTo list the scripts for creating a database user and storage, run this command:

Drop Storage and Revoke Database User PermissionsIf you have dropped all database components from a schema, you can drop the database user and storage.

To list the scripts for dropping storage and revoking database user permissions, run this command:

Create Database ComponentsCreate the proper versions of the database components for your product (see Chapter 1, “Development Environments”).

To list the scripts for creating individual database components, or all database components, run this command:

To list the scripts for creating the database components for a certain webMethods product, run this command:

dbConfigurator.{bat|sh} -a print -d {oracle|sqlserver|db2luw|db2i} -c storage -v latest

dbConfigurator.{bat|sh} -a print -d {oracle|sqlserver|db2luw|db2i} -c storage -v latest

dbConfigurator.{bat|sh} -a print -d {oracle|sqlserver|db2luw|db2i} -c db_component -v db_component_version

dbConfigurator.{bat|sh} -a print -d {oracle|sqlserver|db2luw|db2i} -pr product -v product_release




To list the scripts for dropping individual database components, or all database components, run this command:

To list the scripts for dropping the database components for a certain webMethods product, run this command:

dbConfigurator.{bat|sh} -a print -d {oracle|sqlserver|db2luw|db2i} -c db_component -v db_component_version

dbConfigurator.{bat|sh} -a print -d {oracle|sqlserver|db2luw|db2i} -pr product -v product_release


10 Completing the Installation

Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Configure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Complete the webMethods Broker Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Complete the Integration Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Complete the Metadata Library Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Complete the Monitor Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Complete the Optimize Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Connect Products to Each Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Connect Products to Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Installed JDKs and Product JDK Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Complete the Installation for Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139



Post-Installation ChecklistThe checklist below identifies tasks you need to perform to make an installation of webMethods products operational. Subsequent sections in this chapter or book provide detailed instructions. Additional sections in this chapter provide detailed instructions for optional tasks you might want to perform.

Configure LoggingYou can log various types of data for webMethods products. For detailed information and instructions on setting up logging, see the webMethods Logging Guide.

Product Task Page

webMethods Broker Make sure the Broker Server is running and the default Broker exists

115

On HP‐UX systems, adjust per‐process thread and kernel limits

115

On UNIX systems, configure Broker Monitor to start automatically when you start the system

115

Integration Server On UNIX, IBM i5, and Mac systems, if you are using a Sun JDK, increase PermGen space

116

On UNIX, IBM i5, and Mac systems, increase file descriptors

117

On IBM i5 Systems, prevent memory problems 118

Metadata Library If you will use the Central Configurator to manage Metadata Library, configure Metadata Library (see the webMethods Metadata Library User’s Guide)

On AIX systems, redirect Metadata Library to use the Java 5 32‐bit IBM JDK 1.5

120

Monitor On UNIX systems, if you are not using SVG, set up graphical display

121

Optimize Configure Optimize (see the webMethods Central Configuration and Deployment Guide)

Most products Connect products to each other 122

Most products Connect products to webMethods database components

129


https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=dka&S_PKG=aix32j5b&S_TACT=105AGX05&S_CMP=JDK


Complete the webMethods Broker Installation

Make Sure the Broker Server is Running and the Default Broker ExistsAfter installation, Broker Monitor starts automatically and then starts Broker Server, which begins running with a default Broker. Make sure the Broker Server is running and the default Broker exists by running this command:

You can also use My webMethods to make sure the Broker Server is running and the default Broker exists (see the webMethods Broker Administrator’s Guide).

Adjust Per-Process Thread Limit and Set Per-Process and Kernel Limit on HP-UX SystemsIf you installed webMethods Broker on an HP‐UX system, ask your system administrator to adjust the per‐process thread limit and set the per‐process and kernel limit for the maximum number of open files. For instructions, see the HP‐UX system manual.

Configure Broker Monitors to Start Automatically on UNIX SystemsBy default, Broker Monitors run as applications that you start and shut down manually. If you installed webMethods Broker on a UNIX system, and you want your Broker Monitors to start and shut down automatically when your system starts and shuts down, you must configure the Broker Monitors to run as daemons.

1 Go to the webMethods Broker_directory\Broker directory.

2 Copy each Broker Monitor startup script wm_broker71 to the appropriate UNIX startup directory.

3 Replace the “wm” in wm_broker71 with “Snumber,” where number is the run, or priority, level (for example, S45_broker71). If you configure multiple Broker Monitors to run as daemons, make the name for each Broker Monitor startup script unique among the startup scripts in the UNIX startup directory (for example, S45_broker71_1, S45_broker71_2, and so on).

broker_status [Broker #1@]Broker Server_host[:Broker Server_port]



Set Locale on UNIX SystemsIf you are going to run webMethods Broker in a locale other than U.S. English, you set your shell to the proper locale before installation. However, this setting only affects the way the webMethods Installer starts your Broker Server during installation. When you restart the Broker Server, the Broker Server will use the default locale, U.S. English. ON UNIX systems, if you want to set the Broker Server to run using a different locale, set the environment variables LC_ALL and LANG to that locale.

Enable Full Core Dumps on AIX SystemsOn AIX systems, by default, the ability to perform full core dumps is not enabled. If you want to enable this ability, do one of the following:

Run this command:

Use the AIX System Management Interface Tool (SMIT). Run the command smitty chgsys and set the value of Enable full CORE dump to true.

You do not have to reboot the AIX system for this change to take effect.

Complete the Integration Server Installation

Increase PermGen Space on UNIX, IBM i5, and Mac SystemsIf you are using a Sun JDK with Integration Server, you must increase the permanent generation (PermGen) space from the default of 64 MB to at least 128 MB. By default, the webMethods Installer installs a Sun JDK for Integration Server 7.1.1 on Linux and Solaris systems. If you are using the default JDK on those systems, or if you are using your own Sun JDK on one of those systems, another UNIX system, or an IBM i5 or Mac system, complete the steps below.

1 Go to the Integration Server_directory/bin directory and open the server.sh file in a text editor.

2 Uncomment these lines by removing the pound sign (#):#JAVA_MAX_PERM_SIZE=128M#JAVA_PERM_SIZESET=-XX:MaxPermSize=${JAVA_MAX_PERM_SIZE}


chdev -l sys0 -a fullcore=true

Note: If you receive java.lang.OutOfMemoryError: PermGen space exceptions when running Integration Server, set the PermGen space higher than 128 MB.



Increase File Descriptors and Change Permissions on UNIX, IBM i5, and Mac SystemsOn UNIX, IBM i5, and Mac systems, Integration Server’s ability to handle traffic is constrained by the number of file descriptors available to the Integration Server process. On most systems, 64 file descriptors are available to each process by default. webMethods recommends that you ask your system administrator to increase the number of file descriptors available to the Integration Server process to at least 1024.

If you installed Integration Server on a UNIX, IBM i5, or Mac system and non‐root users will be running Integration Server, you might want to change the ownership of the installed files to allow a single non‐root user to run Integration Server (chown), change the file group to the group of users who will run Integration Server (chgrp), or change file permissions to allow all users to run Integration Server (chmod).

Start Integration ServerThe tasks below require you to start Integration Server.

Open Integration Server Administrator in either of these ways:

On the Windows Start menu, go to Programs webMethods7 Integration Server Administrator.

Enter the URL below in an Internet browser. The default port for Integration Server is 5555.http://Integration Server_host:Integration Server_port

Log in under the default user name and password, Administrator and manage.

Important! You might have to increase this number depending on the number of files Integration Server needs to have open at one time. It is dangerous to set the rlim_fd_max value higher than 1024 because of limitations with the select function, so if Integration Server requires more file descriptors, ask the system administrator to set the setrlimit value directly.

System Action

Windows application

On the Start menu, go to Programs webMethods7 Servers Integration Server.

Windows service

Go to the Services window and start the service webMethods Integration Server 7.1.

All other systems

Go to the Integration Server_directory/bin directory and run the server.sh script.



Prevent Memory Problems on IBM i5 SystemsIf you installed Integration Server on an IBM i5 system, prevent memory problems by following the steps below.

1 Limit the size of the port queue available to the TCP/IP stack, as follows:

a If you have not yet started Integration Server, start it now. Integration Server creates the server.cnf files when it starts for the first time.

b Shut down Integration Server.

c Go to the Integration Server_directory/config directory and open the server.cnf file in a text editor. Add this line:watt.server.portQueue=511

Save and close the file.

2 On IBM i5 systems, the JAVA_MIN_MEM setting acts as a garbage collection threshold. Prevent the JVM that Integration Server is using from running out of memory by doing the following:

a Go to the Integration Server_directory/bin directory and open the server.sh file in a text editor.

b Locate the JAVA_MIN_MEM parameter and set it as follows:JAVA_MIN_MEM=64M

c Locate the JAVA_MEMSET parameter and set it as follows:JAVA_MEMSET="-ms${JAVA_MIN_MEM}"

d Save and close the file.

Note: This setting is based on an IBM i5 system that hosts an Integration Server and a DB2 for iSeries database. The optimal value for initial heap size might be higher or lower based on your system’s configuration.



Streamline Integration ServerBy default, Integration Server is equipped with several packages that provide different types of functionality. If you want to streamline Integration Server (for example, because you are using it only to run adapters, or because you are running it as a Reverse HTTP Gateway server), you can disable many of these packages.

1 Review the table below and determine which packages you can safely disable.

Package Contents

WmART Services that Integration Server uses to run webMethods adapters that are version 6.0 or later.

Important! Do not disable this package unless you are also disabling WmARTExtDC, or WmARTExtDC will not load.

WmARTExtDC Services the Infrastructure Data Collector uses to discover and monitor adapters installed on Integration Server.

WmAssetPublisher Services that Integration Server uses to extract and publish metadata about its services to Metadata Library.

WmFlatFile Services that enable you to process flat files and use file polling ports.

WmISExtDC Services the Infrastructure Data Collector uses to discover and monitor Integration Server.

Important! Do not disable this package unless you are also disabling WmTNExtDC and WmARTExtDC, or those packages will not load.

WmPRT, WmDesigner, WmOptimize, WmTaskClient

Services that support business processes and tasks.

WmTomcat Services that support the servlet 2.4 and JSP 2.0 specifications.

WmTNExtDC Services the Infrastructure Data Collector uses to discover and monitor Trading Networks Server.

WmUDDI Services that enable you to query and publish to a UDDI v2 directory.

Note: This package has been deprecated and will not be available in the next release. You should use Developer to interact with UDDI v3 directories.

WmVCS Services that enable you to store Developer elements in a source control system.



2 Start Integration Server and open Integration Server Administrator (see “Increase File Descriptors and Change Permissions on UNIX, IBM i5, and Mac Systems” on page 117).

3 Go to the Packages Management page and disable each package you do not need. To do so, locate the row for the package in the table, then click Yes in the Enabled column in that row. The Yes changes to No.

Drop Redundant Database ComponentIf you used the Database Component Configurator to install database components, and you installed the Integration Server database component set and the Optimize database component set in two different schemas, you will have two instances of the Process Audit Log database component. Configure Integration Server and Optimize to point to the same instance using instructions in “Connect Products to Database Components” on page 129 and the webMethods Central Configuration and Deployment Guide, respectively. You can then drop the other instance (see the database chapters in this guide).

Complete the Metadata Library Installation

Configure Metadata LibraryIf you are going to use the Central Configurator to manage Metadata Library, you must configure Metadata Library using the Central Configurator. For instructions, see the webMethods Metadata Library User’s Guide.

Set up JDK on AIX SystemsIf you installed Metadata Library on an AIX system, you must redirect Metadata Library to use the Java 5 32‐bit IBM JDK 1.5. For instructions, see “Redirect Products to Use a Non‐Default JRE or JDK” on page 135.

WmWin32 Services that enable you to call methods on COM objects. Also contains Windows‐specific samples, such as sample Visual Basic services.

Note: This package has been deprecated and will not be available in the next release.

WmXSLT Services that enable you to write XSLT services.

Important! Never disable the WmRoot or WmPublic package.

Package Contents




Complete the Monitor Installation

Set Up Graphical Display on UNIX SystemsMonitor contains Java Swing and AWT components that require a graphical display utility to load. If you installed Monitor on a UNIX system and you are not using SVG, you must do one of the following:

Use a utility such as an X‐Server or a virtual X‐Server such as Xvfb. The UNIX system must have access to the graphical display utility, and you must set the machineʹs DISPLAY setting to identify the host machine on which the utility is running.

Modify Integration Server’s startup file to use the ‐Djava.awt.headless option, as follows:

a Go to the Integration Server_directory/bin directory and open the server.sh file in a text editor.

b Locate this line:JAVA_MEMSET="-ms${JAVA_MIN_MEM} -mx${JAVA_MAX_MEM}"

c Add the argument shown below to the line:JAVA_MEMSET="-Djava.awt.headless=true -ms${JAVA_MIN_MEM} -mx${JAVA_MAX_MEM}

Complete the Optimize Installation

Configure OptimizeYou must configure Optimize using its Central Configurator. For instructions, see the webMethods Central Configuration and Deployment Guide.

Drop Redundant Database ComponentIf you used the Database Component Configurator to install database components, and you installed the Integration Server database component set and the Optimize database component set in two different schemas, you will have two instances of the Process Audit Log database component. Configure Integration Server and Optimize to point to the same instance using instructions in “Connect Products to Database Components” on page 129 and the webMethods Central Configuration and Deployment Guide, respectively. You can then drop the other instance (see the database chapters in this guide).

Note: If the JAVA_MEMSET line already includes the ‐server option, add the ‐Djava.awt.headless option after the ‐server option.



Connect Products to Each OtherThis section explains how to do the following:

Connect Optimize Analytic Engines to My webMethods Server

Connect Process Engines to Task Engine

Connect Process Engines to Optimize Analytic Engines

Connect Integration Server to webMethods Broker and Metadata Library

Connect Monitor to My webMethods Server

Connect Trading Networks Server to My webMethods Server

Connect Designer to Other Products (for example, Metadata Library)

Connect Deployer to Source and Target webMethods Products

Start Integration Server and open Integration Server Administrator (see “Increase File Descriptors and Change Permissions on UNIX, IBM i5, and Mac Systems” on page 117).

Start My webMethods Server:

My webMethods Server takes about five minutes to initialize the first time you start it. Open My webMethods in either of these ways:

On the Windows Start menu, go to Programs webMethods7 My webMethods.

Enter the URL below in an Internet browser. The default port for My webMethods Server is 8585.http://My webMethods Server_host:My webMethods Server_port

Log in under the default user name and password, Administrator and manage.

System Action

Windows application

On the Start menu, go to Programs webMethods7 Servers My webMethods Server.

Windows service

Go to the Services window and start the service webMethods My webMethods Server 7.1.

All other systems

Go to the My webMethods Server_directory/bin directory and run this command: mws -s default start



Connect Optimize Analytic Engines to My webMethods ServerYou must connect the Optimize Analytic Engines to the My webMethods Server that hosts the Optimize user interfaces so My webMethods can display Optimize data.

Note: All Analytic Engines share the same database components, so My webMethods Server need only communicate with one to communicate with all.

Identify an Analytic Engine to My webMethods Server...

Identify My webMethods Server to the Analytic Engines...

1 On the My webMethods Server that hosts the Optimize user interfaces, go to the Administration My webMethods

System Settings page.

2 In the Server Settings area, under Analytic Engine Host, identify an Analytic Engine, as follows:

a If a blank row is not available, click Add to add one.

b Provide the host and port for the Analytic Engine. The default port for Analytic Engines is 12503.

c If My webMethods Server should use SSL to communicate with the Analytic Engine, select the Use SSL check box.

3 Click Save.

If you configured Optimize using the Central Configurator, you already identified the My webMethods Server that hosts the Optimize user interfaces to your Analytic Engines. If not, do so using the instructions in the webMethods Central Configuration and Deployment Guide.



Connect Process Engines to Task EngineYou must connect your Process Engines to the Task Engine so the Task Engine can provide results of process steps that required human intervention to running processes.

Note: All Process Engines in a Process Engine cluster share a Broker, the same database component, or both, so the Task Engine need only communicate with one Process Engine to communicate with all.

Identify the Process Engines to the Task Engine... Identify the Task Engine to the Process Engines...

1 On the My webMethods Server that hosts the Task Engine, go to the Administration My webMethods System Settings page.

2 In the Integration Server (Process Engine host) area, identify an Integration Server that hosts a Process Engine in your Process Engine cluster. The default port for Integration Server is 5555.

3 If My webMethods Server should use SSL to communicate with the Integration Server, select the Use SSL check box.

4 Click Save.

1 In the Integration Server Administrator for an Integration Server that hosts a Process Engine in your Process Engine cluster, go to the Packages Management page and click for the WmTaskClient package.

2 In the Task Server URL field, type the URL of the My webMethods Server that hosts the Task Engine (for example, http://myserver:8585).

3 In the Task Server Username and Task Server Password fields, accept the default values sysadmin and manage.

4 Click Save.

5 Reload the WmTaskClient package by returning to the Packages Management page and clicking in the WmTaskClient row.



Connect Process Engines to Optimize Analytic EnginesIf processes are enabled for analysis, you must connect your Process Engines to the Optimize Analytic Engines so My webMethods can display the process metrics.

A Broker connects the Process Engines to the Analytic Engines. By default, the URL provided to the Process Engines for this Broker is broker://localhost:6849/Broker #1/analysis. If this Broker is not on the same machine as a Process Engine, or the port it is using is not 6849, or its name is not Broker #1, you must modify this URL.

1 In Integration Server Administrator for an Integration Server that hosts a Process Engine, go to the Packages Management page and click for the WmOptimize package.

2 In the Broker URL field, change localhost to the correct host, 6849 to the correct port, Broker #1 to the correct Broker name, or any combination of these, as necessary.

3 Click Submit.

4 Reload the WmOptimize package by returning to the Packages Management page and clicking in the WmOptimize row.

5 Repeat these steps for every Integration Server that hosts a Process Engine.

Connect Integration Server to webMethods Broker and Metadata Library

Connect Integration Server to the Default Broker1 In Integration Server Administrator, go to the Settings Messaging Broker Settings

page and click Edit Broker Settings.

2 Click Configured on the left side of the page and complete the fields as shown below.

Important! Do not change the broker:// or /analysis parts of the URL.

Field Setting

Broker Host Name (DNSname:port or IPaddress:port) of the machine that hosts the Broker Server.

Broker Name Name of the Broker to which Integration Server should connect, as defined on Broker Server. The default Broker is Broker #1.

Client Group Broker Server client group to which Integration Server should connect. If the specified client group does not exist, Integration Server creates it when it connects to the Broker.



3 Click Save Changes, then restart Integration Server.

Connect Integration Server to the Metadata Library1 In Integration Server Administrator, go to the Solutions Asset Publisher page.

2 Click Configuration, then click Edit Configuration and complete the fields below.

3 Click Save Changes.

Client Prefix String that identifies Integration Server to the Broker. By default, Integration Server uses its license key for the prefix. You can define your own, shorter, prefix. If the Integration Server is part of a cluster, all Integration Servers in the cluster must use the same client prefix.

My webMethods displays this prefix for each client it creates for Integration Server. (The Broker creates multiple clients for each Integration Server that connects to it.)

Use SSL Indicates whether to use SSL to communicate with the Broker.

Keystore Full path to Integration Server’s keystore file.

Keystore Type File type of the keystore file (PKCS12 or JKS).Truststore Full path to Integration Server’s trust store file.

Truststore Type File type of the trust store file (JKS).Password Password to use to access the SSL certificate in Integration

Server’s keystore file.

Encryption Whether to encrypt the connection between Integration Server and the Broker.

Field Setting

IS Host Name Name you assign to this Integration Server to identify it to Designer.

Protocol Communication protocol. If you configured the Metadata Library to use SSL, click HTTPS. Otherwise, click HTTP.

Host Name or IP address of the machine that hosts the Metadata Library.

Port Port Metadata Library uses to communicate. The default is 8090.

User Name Name of a user authorized to access the Metadata Library. The default is Developer.

Password Password for the user. The default is develop.

Field Setting



Connect Monitor to My webMethods ServerYou must connect Monitor to the My webMethods Server that hosts the Monitor user interface so My webMethods can display Monitor data.

Identify Monitor to My webMethods Server... Identify My webMethods Server to Monitor...

1 On the My webMethods Server that hosts the Monitor user interface, go to the Administration My webMethods System Settings page.

2 In the Server Settings area, under Integration Server (Monitor) Host, identify an Integration Server that hosts Monitor, as follows:

a If a blank row is not available, click Add to add one.

b In the Name field, supply a unique name for the Integration Server.

c Provide the host and port for the Integration Server. The default port for Integration Server is 5555.

d If My webMethods Server should use SSL to communicate with the Integration Server, select the Use SSL check box.

3 If you want to identify other Integration Servers that host Monitor, repeat the previous step as necessary, and choose the Integration Server to serve as the default for users. Users can override this choice later.

4 If you want to check whether the identified Integration Servers are currently running, click Display Server Status.

5 Click Save.

1 In Integration Server Administrator for the Integration Server that hosts Monitor, go to the Packages Management page and click for the WmMonitor package.

2 In the MWS Password field, type the password for Monitor to use to connect to the My webMethods Server that hosts the Monitor user interface. The default is manage.

3 If the My webMethods Server is not on the same machine as the Integration Server, edit the MWS Host and MWS Port fields to identify the My webMethods Server host machine and port.

4 If you need to edit any other fields, see the webMethods Monitor User’s Guide.

5 Click Submit.

6 Reload the WmMonitor package by returning to the Packages Management page and clicking in the WmMonitor row.



Connect Trading Networks Server to My webMethods ServerYou must connect Trading Networks Server to the My webMethods Server that hosts the Trading Networks user interface so My webMethods can display Trading Networks data.

1 On the My webMethods Server that hosts the Trading Networks user interface, go to the Administration Integration B2B Settings Administrative Preferences page.

2 In the Trading Networks Server area, identify the Integration Server that hosts Trading Networks Server. Then click Save.

Connect Designer to Other ProductsFor instructions on connecting Designer to products other than Metadata Library, see the Designer online help.

Connect Designer to the Metadata Library1 Start Designer. On the Start menu, go to Programs webMethods7 Tools Designer.

2 In Designer, click Window Preferences.

3 In the tree, go to webMethods Metadata Library.

4 Clear the Disable Metadata Library Connection check box and complete the fields below.

5 Click Test Connection.

6 Click OK.

7 If you configured the Metadata Library to use SSL, you must perform additional steps. For instructions, see the Designer online help.

Connect Deployer to Source and Target webMethods ProductsConfigure communication between Deployer and the source webMethods products from which you want to deploy items, and between Deployer and the target webMethods products to which you want to deploy items. For instructions, see the webMethods Deployer User’s Guide.

Field Setting

Host Name or IP address of the machine that hosts the Metadata Library. Do not include the protocol prefix (for example, “http://”).

Port Port the Metadata Library uses to communicate.

User name Name of a user authorized to access the Metadata Library. The default is Developer.

Password Password for the user. The default is develop.



Connect Products to Database ComponentsThis section explains how to define the database connections for Integration Server to use to connect to the IS Core Audit Log, IS Internal, Process Audit Log, Archive, Document History, Process Engine, Reporting and Staging, and Cross Reference database components, and for Trading Networks Server to use to connect to the Trading Networks database component.

You might have defined the database connections for My webMethods Server and Metadata Library during installation. If you did not, or if you need to edit the database connections, see the My webMethods Server Administrator’s Guide and the webMethods Metadata Library User’s Guide, respectively.

For instructions on defining the database connections for the Optimize database components, see the webMethods Central Configuration and Deployment Guide.

Database Connections for Integration Server and Trading Networks ServerYou use Integration Server Administrator to connect Integration Server and Trading Networks Server to database components, as follows:

Define JDBC database connection pools for Integration Server and Trading Networks Server to use to connect to database components. Each pool specifies the connection to a database server that hosts database components.

Integration Server Administrator provides a function that corresponds to each database component (for example, an IS Core Audit Log function, a Trading Networks function, and so on). Direct the functions to write to the corresponding database components by pointing each function at the appropriate connection pool.

If the same database server hosts multiple database components, define one connection pool for the database server and point the corresponding functions at that pool. Integration Server will create a separate instance of the connection pool for each database component at run time.

If you chose an external RDBMS and defined the database connection during Integration Server installation, the installer created a connection pool and pointed the IS Core Audit Log, IS Internal, and Process Audit Log functions at that pool. You can edit the pool using the instructions in this section, or you can create separate pools for the functions. If you created the Document History, Cross‐Reference, Process Engine, and Archive database components, you must point those functions at the appropriate connection pools as well.

If you chose the embedded IS Internal database during Integration Server installation, the installer created a connection pool called Embedded Database Pool and pointed the IS Internal function at that pool.

If you defined the database connection for the Trading Networks database component during product installation, you can edit the connection using the instructions in this section.



Define a Connection Pool1 Start Integration Server and open Integration Server Administrator (see “Increase File

Descriptors and Change Permissions on UNIX, IBM i5, and Mac Systems” on page 117).

2 Go to the Settings JDBC Pools page. Click Create a new Pool Alias Definition and complete the fields as follows:

Field Entry

Alias Name Name for the connection pool. The name can include any characters that are valid for a file name in your operating system.

Alias Description

Description for the pool.

Associated Driver Alias

Database driver to use.

Database URL

URL for the database server. Below are sample formats.

Oraclejdbc:wm:oracle://server:{1521|port};serviceName=service[;option=value …]

Oracle configured for RACjdbc:wm:oracle://server:{1521|port};serviceName=service; AlternateServers=(server:{1521|port};,…);ConnectionRetry=value; ConnectionDelay=value; LoadBalancing=value [;option=value …]

SQL Server

jdbc:wm:sqlserver://server:{1433|port};databaseName=database[;option=value …]



DB2 for iSeries

jdbc:wm:db2://server:{446|port};locationName=location[;option=value …]

Important! For DB2, if Integration Server will connect to a schema other than the default schema for the specified database user, you must specify these connection options in the URL:

AlternateId=schema;InitializationString="SET CURRENT PATH=schema"




3 Click Save Settings.

User Id Database user for Integration Server to use to communicate with the database.

Password Password for the database user.

Minimum connections

Minimum number of connections the pool must keep open at all times.

If you use this pool alias for more than one function, each pool instance keeps the specified number of connections open. For example, if you specify keeping at least 3 connections open, and the IS Core Audit Log and the Document History database components both use this pool, the pool keeps a total of 6 connections open ‐ 3 for the IS Core Audit Log pool instance and 3 for the Document History pool instance.

If your logging volume has sudden spikes, you can improve performance by making sure the connections needed to handle the increased volume open quickly. You can minimize connection startup time during spikes by setting this value higher, so that more connections remain open at all times.

Maximum connections

Maximum number of connections the pools can have open at one time.

Calculate this value as part of the total possible nuber of connections that could be opened simultaneously by all functions and applications that write to the database. Make sure the total number does not exceed the database’s connection limit. If one of the applications opens more connections than the database allows, the database will reject subsequent requests for connections from any application.

However, if Trading Networks also writes to the database and has a pool that could open up to 5 connections, you could specify only 17 as the maximum number of connections for the current pool. The IS Core Audit Log pool instance could use up to 17 connections, and the Document History pool instance could use the remaining 5 connections.

You must coordinate the value for the temporary store property watt.server.auditMaxPool with this value. For instructions, see the webMethods Logging Guide.

Idle Timeout Period of time, in milliseconds, the pool can keep an unused connection open. After the specified period of time, the pool closes unused connections that are not neded to satisfy the Minimum connections value.

Field Entry



Point a Function at a Connection Pool1 In Integration Server Administrator, go to the Settings JDBC Pools page.

2 In the Functional Alias Definitions area, scroll right to the Edit Association column for a function and click Edit in that column.

3 In the Associated Pool Alias list, click the pool to which you want the function to point.

4 Click Save Settings. Integration Server Administrator returns to the Settings JDBC Pools page.

5 Initialize the connection pool. In the Functional Alias Definitions area, scroll right to the Restart Function column for the function and click Restart in that column.

6 Make sure Integration Server can connect to the database. In the Test column (next to the Restart Function column) for the function, test the connection by clicking .

7 Restart Integration Server.



Installed JDKs and Product JDK UsageThe table below lists the JDKs installed by the webMethods Installer on each operating system that the webMethods product suite supports. The indicated products use the installed JDK by default.

Integration Server and Trading Networks Server also support 64‐bit IBM i5 and Mac systems. The installer does not install a JDK on these systems. However, you installed an appropriate JDK to run the installer, and the installer automatically configured the products to use that JDK.

You can redirect the products to use another JRE or JDK. For instructions, see “Redirect Products to Use a Non‐Default JRE or JDK” on page 135.

Products

32 Bit 64 Bit

Windows Linux Windows Solaris HP-UX Linux AIX

Blaze Advisor, Designer

Developer,Trading Networks Console

64‐bit Sun

1.5.0_12

Metadata Library,webMethods Broker Java and JMS APIs

32‐bit Sun 1.5.0_12

32‐bit Sun

1.5.0_12

32‐bit Sun 1.5.0_12

with 64‐bit extension*

32‐bit HP 1.5.0_08 with 64‐bit

extension*

64‐bit Sun 1.5.0_12

64‐bit IBM 1.5.0.0.125

Integration Server,Trading Networks Server,My webMethods Server,Optimize

64‐bit Sun

1.5.0_12

*By default, these JDKs run in 32‐bit mode. You can switch to 64‐bit mode. For instructions, see “Configure Products to Use 64‐Bit Mode on Solaris and HP‐UX Systems” on page 134.

**Metadata Library on an AIX system requires the Java 5 32‐bit IBM JDK 1.5. You must download and install JDK yourself.

Important! You should apply maintenance updates to the installer JDK from the appropriate vendor on a regular basis, as you would for JDKs you install yourself.



Configure Products to Use 64-Bit Mode on Solaris and HP-UX SystemsOn 64‐bit Solaris and HP‐UX, the installer installs a 32‐bit JDK with a 64‐bit extension. By default, this JDK runs in 32‐bit mode. You can switch to 64‐bit mode.

Run-time Product Steps

Integration Server (and packages)

1 Go to the Integration Server_directory/bin directory and open the server.sh file in a text editor.

2 Locate the line #JAVA_D64=”‐d64” and uncomment it, as follows:JAVA_D64=”-d64”



1 Go to the My webMethods Server_directory/bin directory and open the setenv.sh file in a text editor.

2 Locate the line {rem|#} JAVA_D64=‐d64 and uncomment, as follows:JAVA_D64=-d64


Optimize Analytic Engine

1 Go to the Optimize_directory/analysis/bin directory and open the startupAnalyticEngine.sh file in a text editor.

2 Locate the line GLUE_OPTS=ʺ$GLUE_OPTS ‐Xss256kʺ and add ‐d64, as follows:GLUE_OPTS="$GLUE_OPTS –d64 -Xss256k"


Optimize Prediction Engine

1 Go to the Optimize_directory/prediction/bin directory and open the startupPredictionEngine.sh file in a text editor.





Redirect Products to Use a Non-Default JRE or JDKBy default, all webMethods products use the JDKs installed by the webMethods Installer on your systems. You can redirect each product to use a non‐default JRE or JDK.

If you use a non‐default JRE or JDK, your JVM must contain Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 5.0. webMethods products need these files to be able to encrypt and decrypt SSL certificates. You can download the JCE files for a Sun or Hewlett‐Packard JDK from the Sun Web site at http://java.sun.com/javase/downloads/index_jdk5.jsp. You can download the JCE files for an IBM JDK from the IBM Web site at http://www.ibm.com/developerworks/java/jdk/security/index.html. Install the files using the instructions in the vendor documentation.

Optimize Web Service Data Collector

1 Go to the Optimize_directory/dataCollector/bin directory and open the startupDataCollectorEngine.sh file in a text editor.



Optimize Infrastructure Data Collector

1 Go to the Infrastructure Data Collector_directory/bin directory and open the server.sh file in a text editor.

2 Locate the line #JAVA_D64=”‐d64” and uncomment it, as follows:JAVA_D64=”-d64”


Note: Software AG tests webMethods products only with the JDKs installed by the webMethods Installer.

Run-time Product Steps


http://java.sun.com/javase/downloads/index_jdk5.jsp

http://www.ibm.com/developerworks/java/jdk/security/index.html


Run-time Products

Product Steps to Redirect to a Non-Default JRE or JDK

webMethods Broker Java and JMS APIs

Require JDK 1.5.

In the steps below, command is any command other than server_config, awcert, awbroker, or awbrokermon.webMethods Broker_directory\bin\command -DJAVA_HOME-=JDK_path host:port

On a Windows system, the command might look like this: C:\Program Files\webMethods7\Broker\bin\broker_status -DJAVA_HOME-=C:\jdk1.5 localhost

On a UNIX system, the command might look like this:/opt/webMethods7/Broker/bin/broker_status -DJAVA_HOME=/opt/java1.5 localhost

Integration Server (and packages, including Deployer, Monitor, Process Engine, and Trading Networks Server)

Requires JRE 1.5, unless you are using it with Developer. In this case, Integration Server requires JDK 1.5.

Go to the Integration Server_directory\bin directory and open the server.bat or server.sh file in a text editor. Edit the JAVA_DIR parameter to point to the JRE or JDK installation directory, then save and close the file.



Metadata Library Requires JDK 1.5. On an AIX system, requires specifically the Java 5 32‐bit IBM JDK 1.5; you must download and install the JDK yourself.

On a Windows system:

1 Go to the Metadata Library_directory\library\bin directory and open the setJava.bat file in a text editor.

2 If you want Metadata Library to use the JDK specified by the JAVA_HOME environment parameter, use the rem command to comment out the set JAVA_DIR line (that is, rem set JAVA_DIR=path_to_webMethods_JDK).

If you want Metadata Library to use a different JDK, comment out the set JAVA_DIR line as explained above, and then add a new line just beneath it that specifies the path to the JDK to use (that is, set JAVA_DIR=path_to_JDK).


On a UNIX system:

1 Go to the Metadata Library_directory\library\bin directory and open the library.conf file in a text editor.

2 On the JAVA_HOME variable, specify the path to the JDK to use. If the JAVA_HOME variable is commented out, uncomment it by removing the # sign.



Requires JDK 1.5.

Go to the My webMethods Server_directory\bin directory and open the setenv.bat or setenv.sh file in a text editor. Edit the JAVA_HOME parameter to point to the JDK installation directory, then save and close the file.






Optimize Analytic Engine, Prediction Engine, and Web Service Data Collector

Require JDK 1.5.

1 Log on to the host machine for the component.

2 Go to the Optimize directory\component\bin directory and open the kenobiEnv.bat or kenobiEnv.sh file in a text editor.

3 Edit the JAVA_HOME parameter to point to the JDK installation directory, then save and close the file.

4 If the engines were installed as Windows Services, do the following for each:

a Go to the Optimize directory\component\bin directory and open the wrapper.conf file in a text editor.

b Edit the wrapper.java.command property to point to the JDK_directory/bin/java executable.

c Edit the wrapper.java.classpath.1 property to point to the JDK_directory/lib/tool.jar library.

d Save and close the file

e Run the uninstallNTsvc.bat program.

f Run the installNTsvc.bat program.

Optimize Infrastructure Data Collector

Requires JRE 1.5.

Go to the Infrastructure Data Collector_directory/bin directory and open the server.bat or server.sh file in a text editor. Edit the JAVA_DIR parameter to point to the JRE installation directory, then save and close the file.




Development Products

Complete the Installation for Other ProductsSome products not covered in this chapter have tasks you must complete that are beyond the scope of this guide. Make sure you check the product user’s guides for such tasks before starting the products.


Blaze Advisor Requires JRE 1.5. You cannot redirect it from the default.

Designer Requires JRE 1.5.

Go to the Designer_directory\bin directory and open the designer.bat file in a text editor. Edit the JAVA_DIR parameter to point to the JRE installation directory, then save and close the file.

Developer (and plug‐ins)

Requires JRE 1.5.

Go to the Developer_directory\bin directory and open the developer.bat file in a text editor. Edit the JAVA_DIR parameter to point to the JRE installation directory, then save and close the file.

Trading Networks Console

Requires JRE 1.5.

Go to the Trading Networks Console_directory\bin directory and open the console.bat file in a text editor. Edit the JAVA_ROOT parameter to point to the JRE installation directory, then save and close the file.

Note: When you launch Developer from Trading Networks Console, Developer runs in the same JVM as Trading Networks Console. If you decide to use a different JRE for Trading Networks Console, the JRE must be suitable for Developer as well as Trading Networks Console.


11 Uninstalling Products

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Uninstall on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Uninstall on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Complete the Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144



OverviewUninstall webMethods products using the webMethods Uninstaller. The webMethods Installer installed all files you need to run the uninstaller.

You can run the uninstaller using different modes, as follows:

To uninstall using the wizard on a UNIX system, your system must have an X Windows environment.

The installer writes product, version, and build information into an audit history log file named history.text in the webMethods_directory\install\history\history.txt directory. If errors or warnings occur during the uninstallation, the uninstaller writes the errors and warnings to a file named WmUninstallLog.txt and stores the file in the main installation directory (by default, webMethods7). You can change logging behavior; for instructions, see “Change Logging Level and File, and Add Targets” on page 52 or “Start the Installer Using Advanced Options” on page 71.

Uninstall on a Windows SystemTo uninstall webMethods products on a Windows system, you must have Windows system administrator privileges.

1 Shut down all webMethods products and all other applications that are running on your machine.

2 Use the Windows Add/Remove Programs utility, available from the Control Panel, to start the uninstaller.

3 Select webMethods release_installation_directory as the program to uninstall. The uninstaller starts; it looks almost identical to the installer.

4 Choose the products to uninstall.

System Mode

Windows wizard

UNIX or Mac wizard or console mode

IBM i5 console mode

Important! If you do not shut down all products and applications, the uninstaller will not be able to remove key files that are locked by the operating system.

Important! When you choose a product, the uninstaller asks whether it should also uninstall all products that depend on the product. Read the messages carefully to avoid uninstalling products accidentally.



Uninstall on a UNIX, IBM i5, or Mac System

1 Log on as the same user that installed the webMethods products.

2 If the webMethods products you are uninstalling are located on a remote machine and you want to use a graphical uninstaller, follow these steps:

a Enable the display of the local machine using the command shown below, where remote_host is the remote machine from which to uninstall:

b Log on to the remote machine.

c Set the DISPLAY variable on the remote machine to point to the local machine. For example, if you are using a bash shell and uninstalling from a local machine named uninstaller and want to set the DISPLAY to the default device, enter:

3 Shut down all webMethods products and all other applications that are running on the machine that contains the webMethods products you are uninstalling.

4 Go to the webMethods_directory/bin directory and enter the appropriate command, as follows:

The uninstaller starts; it looks almost identical to the installer.

5 Choose the products to uninstall.

Important! When you run the webMethods Uninstaller on an IBM i5 system, the uninstaller experiences display problems. While these display problems will not adversely affect the uninstallation process, Software AG strongly recommends that you minimize the problems by running the uninstaller from an IBM i5 client for Windows rather than from a telnet client.

xhost +remote_host

export DISPLAY=uninstaller:0.0

Important! If you do not shut down all products and applications, the uninstaller will not be able to remove key files that are locked by the operating system.

Uninstall Mode Command

Wizard uninstall

Console mode uninstall -console

Important! When you choose a product, the uninstaller asks whether it should also uninstall all products that depend on the product. Read the messages carefully to avoid uninstalling products accidentally.



Complete the UninstallationFor most products, the uninstaller does not delete files created after you installed the product (for example, user‐created or configuration files), nor does it delete the directory structure that contains the files. If you do not want to save the files, delete the product installation directory.

Complete the webMethods Broker Uninstallation on UNIX SystemsOn a UNIX system, if you configured your Broker Monitor to run as a daemon so it would start and shut down automatically when your system starts and shuts down, you moved the Broker Monitor startup script to the appropriate UNIX startup directory. The script is named Snumber_broker71 (for example, S45_broker71). If you configured multiple Broker Monitors to run as daemons, you moved multiple startup scripts, and the names will have an additional character at the end to make them unique (for example, S45_broker71_1, S45_broker71_2, and so on). You can delete these scripts from the UNIX startup directories.

Complete the Deployer UninstallationUninstall the Deployer communications component from source and target Integration Servers, including those called ProcessModel servers. If the Integration Server is not running, go to the Integration Server_directory/packages directory and delete all of the WmDeployerResource folder. If the Integration Server is running, follow these steps:

1 In the Integration Server Administrator for an Integration Server that hosts the resource package, go to the Packages Management page.

2 Delete the WmDeployerResource package.


A Default Ports

Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146


A Default Ports

Default Ports

Component Default Port Protocol/Port Type

webMethods BrokerBroker Server 6849 (SSL not

enabled)6848 (SSL enabled)6847 (SSL authenticated)

TCP

Default Broker 6849 TCP

Broker Monitor 6850 TCP

Central Configuration 16000‐16025 HTTP

Dashboard application server 8080 HTTP

Integration Server and all packages 5555 HTTP

Data port for communication among clustered Integration Servers

24547 Proprietary binary protocol over TCP

Diagnostics 9999 HTTP

Metadata Library 8090 HTTP/HTTPS

My webMethods ServerJava debugger (available when My webMethods Server is stared with ‐d option)

5000 HTTP

AJP13 ‐ Jetty listens to external Web server, if using one (not enabled by default)

8009 AJP13

Jetty HTTP Web server and webMethods product user interfaces

8585 HTTP

Jetty HTTPS Web server (not enabled by default)

8443 HTTPS

Communication with Central Configuration

15002 HTTP


A Default Ports

OptimizeAnalytic Engine

Communication with Central Configuration

15000 HTTP/HTTPS

Broker client JMS API 6849 TCP/IP

My webMethods Server 8585 HTTP

Internal Web service registry 12503 HTTP

Infrastructure Data Collector 5555 HTTP

Prediction EngineCommunication with Central Configuration

15003 HTTP/HTTPS



Web Service Data CollectorCommunication with Central Configuration

15001 HTTP/HTTPS



Component Default Port Protocol/Port Type


A Default Ports


Web Methods Installation Guide 7.1.1

Documents

Transcript of Web Methods Installation Guide 7.1.1