Web Methods Installation Guide 7 1 2 and 7 2

Title Page
webMethods
Installation Guide
Version 7.1.2 and 7.2
May 2009
Copyright
& Docu-
ment ID
This document applies to webMethods Product Suite Version 7.1.2 and 7.2 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 © 2005-2009 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America, and/or
their suppliers. All rights reserved.
The name Software AG, webMethods, and all Software AG product names are either trademarks or registered trademarks of Software AG
and/or Software AG USA, Inc. Other company and product names mentioned herein may be trademarks of their respective owners.
Document ID: WEBM-IG-712_72-20090501

Table of Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
webMethods Central Documentation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
webMethods Advantage Bookshelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Software AG Developer Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Development Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Integration Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Process Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Portlet and Web Application Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Integration Server Data Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Embedded Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
External RDBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Integration Development Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2. Software and Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Operating Systems, JDKs, Browsers, RDBMSs, and Drivers . . . . . . . . . . . . . . . . . . . . . . . 28
Standard Product Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Special Product Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Trading Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3. International Operating Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Extended Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Browsers and JDK Font Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4. Using the Wizard for Simple Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
webMethods Installation Guide Version 7.1.2 and 7.2 3

Table of Contents
Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5. Preparing for Advanced Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Prepare for Installation on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Prepare for Installation on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . 46
Prepare for Installation on a Remote Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Prepare the Machine on Which to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Prepare to Install webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Installation Scripts and Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Installation Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Installation Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Inter-product Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6. Using the Wizard for Advanced Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Start the Installer on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Start the Installer and Specify a Different System Temp Directory . . . . . . . . . . . . . . . . 53
After You Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Start the Installer on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Start the Installer and Specify a Different Temporary Directory . . . . . . . . . . . . . . . . . . 55
After You Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Use Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Create, Install from, or Edit an Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Create or Install from an Installation Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Use a Proxy Server to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Change Logging Level and File, and Add Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Overwrite Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
How to Choose Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Complete Product Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configure Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Configure Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Configure Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Configure Infrastructure Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configure Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Configure webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configure My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4 webMethods Installation Guide Version 7.1.2 and 7.2

Table of Contents
7. Using Console Mode for Advanced Product Installation . . . . . . . . . . . . . . . . . . . . . . . . 77

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Start the Installer and Specify a Different Temporary Directory . . . . . . . . . . . . . . . . . . 79
Start the Installer Using Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Specify Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Specify User Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
How to Select Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Complete Product Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Configure Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Configure Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Configure the Infrastructure Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Configure webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Configure My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8. Preparing for Database Component Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

webMethods Products and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Database Users and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Database Administrator Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Character Set and Sort Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Page and Block Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Set Database Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Download the Database Scripts and Database Component Configurator . . . . . . . . . . . . . . 94
Change Environment Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Default Storage Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Database Component Descriptions and Installation Requirements . . . . . . . . . . . . . . . . . . 96
Cross Reference, Document History, IS Internal, and IS Core Audit Log Database
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Process Audit Log Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Process Engine Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Archive Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Metadata Reasoner and Metadata Repository Database Components . . . . . . . . . . . . 97

Table of Contents
My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Trading Networks and Trading Networks Archive Database Components . . . . . . . . . . 98
Analysis and Process Tracker Database Components . . . . . . . . . . . . . . . . . . . . . . . . . 98
Staging and Reporting Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Infrastructure Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9. Creating and Dropping Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Use the Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Create Database Components and Create a Database User and Storage . . . . . . . . . 102
Drop Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Drop the Storage and Revoke Database User Permissions . . . . . . . . . . . . . . . . . . . . . 107
Use the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Database Component Configurator Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Use Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Create a Database User and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Drop Storage and Revoke Database User Permissions . . . . . . . . . . . . . . . . . . . . . . . . 117
Create Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Drop Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
10. Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Configure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Complete the webMethods Broker Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Make Sure the Broker Server is Running and the Default Broker Exists . . . . . . . . . . . 121
Adjust Per-Process Thread Limit and Set Per-Process and Kernel Limit on
HP-UX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Configure Broker Monitors to Start Automatically on UNIX Systems . . . . . . . . . . . . . . 121
Set Locale on UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Enable Full Core Dumps on AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Complete the Integration Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Increase PermGen Space on UNIX, IBM i5, and Mac Systems . . . . . . . . . . . . . . . . . . 122
Increase File Descriptors and Change Permissions on UNIX, IBM i5, and
Mac Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Start Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Prevent Memory Problems on IBM i5 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Streamline Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Drop Redundant Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Complete the Metadata Library Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Set up JDK on AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Complete the Monitor Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Set Up Graphical Display on UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Table of Contents
Complete the Optimize Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Drop Redundant Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Complete the Trading Networks Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Prevent Memory Problems on AS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Connect Products to Each Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Start Integration Server and My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Connect Process Engine to Task Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Connect Monitor to My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Connect Optimize Analytic Engine to My webMethods Server . . . . . . . . . . . . . . . . . . 132
Connect Process Engine to Optimize Analytic Engine . . . . . . . . . . . . . . . . . . . . . . . . . 133
Connect Integration Server to webMethods Broker Default Broker . . . . . . . . . . . . . . . 133
Connect Trading Networks Server to My webMethods Server . . . . . . . . . . . . . . . . . . . 134
Connect Integration Server to the Metadata Library . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Connect Designer to Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Connect Deployer to Source and Target webMethods Products . . . . . . . . . . . . . . . . . 136
Connect Products to Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Database Connections for Integration Server and Trading Networks Server . . . . . . . . 136
Define a Connection Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Point a Function at a Connection Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Installed JDKs and Product JDK Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Configure Run-Time Products to Use 64-Bit Mode on Solaris and
HP-UX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Redirect Products to Use a Non-Default JRE or JDK . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Complete the Installation for Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
11. Uninstalling Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Uninstall on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Uninstall on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Complete the Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Complete the webMethods Broker Uninstallation on UNIX Systems . . . . . . . . . . . . . . 150
Complete the Deployer Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
A. Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Table of Contents

About This Guide
This guide is for users who are installing or uninstalling the webMethods products
below.
Product Release
Fair Isaac Blaze Advisor 6.5.5
webMethods Broker 7.1.2
webMethods Deployer 7.1.2
webMethods Designer 7.1.2 or 7.2
webMethods Developer 7.1.2
webMethods Integration Server 7.1.2
webMethods Metadata Library 7.1.1
webMethods Monitor 7.1.2
My webMethods Server 7.1.2
webMethods Process Engine 7.1.2
webMethods Optimize 7.1.2
webMethods Optimize Infrastructure Data Collector 7.1.2
webMethods Task Engine 7.1.2
webMethods Trading Networks 7.1.2
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 custops@webmethods.com.
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.
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.

About This Guide
Document Conventions
Convention Description
Bold Identifies elements on a user interface.
Narrow font Identifies storage locations for services on webMethods Integration
Server, using the convention folder.subfolder:service.
UPPERCASE Identifies keyboard keys. Keys you must press simultaneously are
joined with a plus sign (+).
Italic Identifies variables for which you must supply values specific to your
own situation or environment. Identifies new terms the first time they
occur in the text.
Monospace Identifies text you must type or messages displayed by the system.
font
{} Indicates a set of choices from which you must choose one. Type only
the information inside the curly braces. Do not type the { } symbols.
| Separates two mutually exclusive choices in a syntax line. Type one of
these choices. Do not type the | symbol.
[] Indicates one or more options. Type only the information inside the
square brackets. Do not type the [ ] symbols.
... Indicates that you can type multiple options of the same type. Type
only the information. Do not type the ellipsis (...).
Additional Information
You can find additional information about webMethods products at the locations
described below.
webMethods Central Documentation Directory

During product installation, you can download the webMethods product documentation
to a single directory called “_documentation.” This directory is located by default under
the webMethods installation directory.

About This Guide
webMethods Advantage Bookshelf

The 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. You can find documentation for all webMethods products on
the webMethods Bookshelf.
Software AG Developer Community

Additional articles, demos, and tutorials are available on the webMethods portion of the
Software AG Developer Community. The various Developer Communities feature
technical information, useful resources, and online discussion forums, moderated by
Software AG professionals, to help you do more with webMethods technology.
With the Software AG Developer Communities, you can:
 Use the online discussion forums to exchange best practices and chat with other
experts.
 Expand your knowledge with product documentation, code samples, articles, online
seminars and tutorials.
 Link to external sites on open standards and many Web technology topics.
 See how other customers are streamlining their operations with technology from
Software AG.

About This Guide

1 Development Environments
 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
 Integration Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
 Process Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
 Portlet and Web Application Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
 Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
 Integration Server Data Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Overview
This 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 96.
To design your webMethods production environments, work with your administrators,
Software AG Professional Services, webMethods GEAR methodology, and webMethods
best practices documentation.
Integration Development
 Developer 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
webMethods Broker
Integration Server
Developer
Broker and JMS interface
Trading Networks Console TN Server Monitor Monitor interface
Trading Networks interface
My webMethods Server
database

Below are additional options.
If you want to... Install this product...

Store Integration Server and Trading Integration Server PKI Support package
Networks keys and certificates securely
Maintain Developer elements in Integration Server VSS Support or
Microsoft Visual Sourcesafe or IBM ClearCase Support
Rational ClearCase
For information on storing data written by Integration Server, see “Integration Server
Data Storage” on page 22.

Process Design
 Designer (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
Blaze Advisor
webMethods Broker
Developer Integration Server
Blaze
Designer
Process Monitor
Engine Monitor interface
Central Configurator interface
Metadata Library
Task Engine
database
Below are additional options.
If you want to... Install this product...

Store Integration Server keys and Integration Server PKI Support package
certificates securely
Maintain Developer elements in Microsoft Integration Server VSS Support or
Visual Sourcesafe or IBM Rational ClearCase Support
ClearCase
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 96.

Optional Database
Product Required Database Components Components
Integration IS Core Audit Log v12, Process Archive v20 (with Opera-
Server Audit Log v30 tion Management v15,
IS Core Audit Log v11, and
IS Internal v25 (required if not
Process Audit Log v30)
using the embedded database; see
“Configure Integration Server” on
page 69)
Metadata Library Metadata Repository v30, Metadata
Reasoner v30
Monitor Reporting v10, Staging v10
My webMethods My webMethods Server v20
Server
Process Engine Process Engine v30
Task Engine Process Audit Log v30

Portlet and Web Application Development

 Designer Composite Applications Development and My webMethods Server Support
 My webMethods Server
 Documentation
Designer My webMethods Server database
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 96.
Product Required Database Components

My webMethods Server My webMethods Server v20
If you want your portlet or Web applications to call services that are available through
other products in the webMethods product suite, add the following:
 Blaze Advisor
 Developer with Blaze Rule Service Plug-in
 Integration Server with Blaze Rule Service Support and Monitor
 For collaboration among developers, Metadata Library
 My webMethods user interfaces for Central Configurator and Monitor
Metadata Library
Blaze Advisor Integration Server

Blaze database
Designer
Monitor
Central Configurator interface

Monitor interface

Optional Database
Integration IS Core Audit Log v12, Process Archive v20 (with Opera-
Server Audit Log v30 tion Management v15,
IS Internal v25 (required if not
using the embedded database; see
“Configure Integration Server” on
page 69)
Metadata Library Metadata Repository v30, Metadata
Reasoner v30

Monitoring
 Optimize 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, and My webMethods user interfaces for Optimize for
Infrastructure, Optimize for Process, Central Configurator, Broker and JMS, Monitor,
and Optimize for B2B
 Documentation
Prediction Engine
Infrastructure Data Collector

Analytic Engine webMethods Broker
Web Service Data Collector
Optimize and Central

Configurator interfaces
Monitor interface
Optimize for B2B interface
database Integration Server
Monitor

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 96
.
Optional Database
Optimize Analytic Analysis v30 (with Distributed
Engine, Prediction Locking v20 and Operation
Engine, and Management v15) Data Purge v15
Infrastructure Data
Process Tracker v30 (with Opera-
Collector
tion Management)
Process Audit Log v30 Archive v20 (with Opera-
tion Management v15,
Server
Deployer
Deployer 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.2 works with 7.1.2 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.

Integration Server Data Storage

Integration Server can persist these types of data:
Integration Server
writes this data
Type of Data Content when...
IS Internal Scheduled tasks, client certificate mappings, run- You are using these
time data for pub.storage services, audit log of features
guaranteed delivery transactions, and trigger*
joins.
IS Core  Error, guaranteed delivery, service, security, Logging is enabled
Audit Log and session audit data. (see the webMethods
Logging Guide)
 Documents that are in doubt, have failed, or You are using
have exhausted trigger* retries. triggers
Cross Refer- Cross-referencing data* for publish-and-sub- You are using pub-
ence scribe solutions. lish-and-subscribe
solutions
Document Document history data for exactly-once You are using
History* processing* in publish-and-subscribe solutions. exactly-once
Integration Server uses the data to detect and processing
reject duplicate documents.
*For information on triggers, cross referencing, exactly-once processing, and publish-subscribe solutions, see the
Publish-Subscribe Developer’s Guide.
When you install Integration Server, the installer asks whether you want Integration
Server to write data to an embedded database or an external RDBMS. The sections below
explain when you would choose each option.
Embedded Database
The embedded database is SQL based. You can use the embedded database when 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)
 Do not have an external RDBMS
 Are not installing in a production environment with high transaction volumes or
large datasets
If you choose the embedded database, Integration Server will write IS Internal and Cross
Reference data to that database, and will write IS Core Audit Log data to flat files. For
information about the flat files, see the webMethods Logging Guide.

If you later decide to write IS Internal and Cross Reference data to an external RDBMS
instead of the embedded database, you can install the necessary database components
(see the database chapters in this guide) and redirect Integration Server (see the
webMethods Integration Server Administrator’s Guide).
If you later decide to write IS Core Audit Log data to an external RDBMS instead of flat
files, you can install the necessary database components (see the database chapters in this
guide)and redirect Integration Server (see “Connect Products to Database Components”
on page 136). You must write IS Core Audit Log data to an external RDBMS in these cases:
 If you are working with business processes, Integration Server writes Process Audit
Log data, and that data can only be written to an external RDBMS. If Integration
Server writes Process Audit Log data to an external RDBMS, it must also write IS
Core Audit data to an external RDBMS; it cannot write IS Core Audit Log data to flat
files and Process Audit Log data to an external RDBMS.
 If you are using triggers, Integration Server writes the documents that are in doubt,
have failed, and or have exhausted trigger retries to the IS Core Audit Log.
Documents can only be written to an external RDBMS; they cannot be written to flat
files.
 If you are using Monitor. Monitor can only read from an RDBMS.
 If you want services to post user-defined progress messages at specified points in
their execution (for example, to indicate whether certain segments of code ran
successfully).
Document History data can only be written to an external RDBMS. For instructions, see
see the database chapters and “Connect Products to Database Components” on page 136
in this guide.
External RDBMS
You must use an external RDBMS if you are going to:
 Cluster Integration Servers
 Use exactly-once processing in publish-and-subscribe solutions (that is, write
Document History data)
 Work with business processes (that is, write Process Audit Log and Process Engine
data)
 Use triggers; Integration Server must write documents that are in doubt, have failed,
and or have exhausted trigger retries (IS Core Audit Log data) to an external RDBMS
 Install in a production environment with high transaction volumes or large datasets
 Use Monitor.
 Have services post user-defined progress messages at specified points in their
execution (for example, to indicate whether certain segments of code ran
successfully).

If you choose an external RDBMS, the installer asks you to supply the database
connection. From this information, the installer creates a JDBC connection pool, and
configures Integration Server to write IS Internal, IS Core Audit Log, Process Audit Log,
and Process Engine data to the external RDBMS using that pool.
Note: Process Audit Log data is only written when you are using business processes.
However, if Integration Server writes IS Core Audit Log data to an external RDBMS,
it must be configured to also write Process Audit Log data to an external RDBMS,
even if you are not writing that data.
When you use an external RDBMS, you create webMethods database components. A
webMethods database component is a grouping of database objects. Each database
component is named by the type of data; for example, the database component for IS
Core Audit Log data is called the IS Core Audit Log database component. After
installation, you will create the IS Internal, IS Core Audit Log, and Process Audit Log
database components in your external RDBMS. For instructions, see the database
chapters in this guide. You will also create other database components you need (such as
the Cross Reference, Document History, and Process Engine database components) and
create connection pools for them manually, as described later in this guide. For
instructions on creating connection pools, see “Connect Products to Database
Components” on page 136.
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 IS Internal database
component for each Integration Server. You can create a separate IS Core Audit Log
database component, Cross Reference database component, and Document History
database component for each Integration Server, or you can create a single one of each of
those database components for the Integration Servers to share.
Integration Development Database Components

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 information on the Integration Server and other database components you
must or can include in the other development environments (for example, the Process
Design development environment), see the appropriate sections in this chapter.

Product Database Components Optional Database Components

Integration IS Core Audit Log v11* Archive v20 (with Operation
Server Management v15,
Process Audit Log v30
IS Core Audit Log v11, and Process
IS Internal v20 Audit Log v30)
Cross Reference v10
Document History v10
Server
Trading Trading Networks v20 Trading Networks Archive v20
Networks Server
*For help determining whether you need to install each of the Integration Server database components in this table cell,
see “Integration Server Data Storage” on page 22.


2 Software and Hardware Support and Requirements
 Operating Systems, JDKs, Browsers, RDBMSs, and Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

 Standard Product Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
 Special Product Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Operating Systems, JDKs, Browsers, RDBMSs, and Drivers

For 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 140.
Standard Product Hardware Support and Requirements

The 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.
Hard Drive
Product Space (MB) RAM (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) 1
Monitor Nothing beyond the host Integration
Server.
My webMethods Server 300 1024 (2048) 1
*1024 in development environments.
†Intel Pentium III processor 400MHz or higher.

Hard Drive
Product Space (MB) RAM (MB) CPUs
Optimize
Analytic Engine 100 2048* 1†
Prediction Engine 100 2048* 1†
Infrastructure Data Collector 300 2048 1
Web Service Data Collector 100** 256 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
*1024 in development environments.
†Intel Pentium III processor 400MHz or higher.
Special Product Hardware Requirements

This section describes special requirements you must consider when determining actual
hardware requirements for the indicated products.
webMethods Broker
webMethods Broker might require additional hard drive space if your documents are
large, or if your clients use many guaranteed documents.
On a Windows system, you can only install webMethods Broker on a local hard drive.
You cannot install webMethods Broker on a network-mounted drive.
Deployer
Deployer requires additional hard drive space for the deployment projects you create.
When allocating space, allow for the number of projects to increase over time.
Metadata Library
In addition to the hardware requirements in the table above, Metadata Library requires
1024MB virtual swap space. Metadata Library might require more hard drive space if
you use debug level or higher logging.

Optimize
Analytic Engine and Prediction Engine
Each engine requires 1024MB virtual swap space and a disk subsystem with 10GB
available free space. In a production environment, the disk subsystem must have a
redundant array of independent disks (RAID 5), an UltraWide SCSI, and 10K to 15K RPM
drives.
Also in a production environment, 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.
Web Service Data Collectors

Each Web Service Data Collector requires 128MB of virtual swap space. In 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. More hard drive space might be required if you
use debug level or higher logging.
Infrastructure Data Collector

Each 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.
Each Infrastructure Data Collector requires 128MB of virtual swap space. 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.

Trading Networks
To use large document handling, you need additional 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 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
 Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
 Extended Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
 Browsers and JDK Font Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Overview
webMethods 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 Packs
The 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 Configuration

Some 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:
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 Go to ToolsInternet Options. Click Languages and add the
and 7.x language you want to use to the top of the list.
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


4 Using the Wizard for Simple Product Installation
 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
 Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
 Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
 Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
 Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
 Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Overview
This 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.
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.
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 Begin

1 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 If you are installing on a UNIX, IBM i5, or Mac system, install a 32- or 64-bit JRE
or JDK 1.5 to run the webMethods Installer.
Important! On IBM i5 and Mac systems, the installer will automatically

configure the webMethods products you install to use this JRE or JDK. For
information on whether your products require a JRE or a JDK, see “Redirect
Products to Use a Non-Default JRE or JDK” on page 142.
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 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 Installer

1 If you are installing on a Windows system, you must have Windows system
administrator privileges. On a UNIX system, log in as a 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
The installer takes several seconds to unzip and launch its JVM, then displays the
welcome panel.
Note: If the progress bar on the installer launcher (called Zipfusion) stops showing
progress, your anti-virus software might be interfering. Start the installer using
the jar file with the JVM -Xmx option set to at least 512 (see “Start the Installer” on
page 53).
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
Windows only
Provide the requested information and then click Next.

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.
Important! The installer does not distinguish among versions (Windows) or flavors
(UNIX) of an operating system. Make sure you install products only on supported
operating systems, as specified in the webMethods System Requirements.
The highest level in the product selection tree shows product names and releases, while
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 Products
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 67, 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 76.


5 Preparing for Advanced Product Installation
 Prepare for Installation on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

 Prepare for Installation on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
 Installation Scripts and Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Prepare for Installation on a Windows System

Prepare 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.
Note: The instructions below are for Windows XP. Instructions for other Windows
systems vary slightly.
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 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 Machine

If 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:
xhost +remote_host
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:
export DISPLAY=installmachine:0.0

Prepare the Machine on Which to Install

Prepare 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 32- or 64-bit JRE or JDK 1.5 to run the webMethods Installer.
Important! On IBM i5 and Mac systems, the installer will automatically configure
the webMethods products you install to use this JRE or JDK. For information on
whether your products require a JRE or a JDK, see “Redirect Products to Use a
Non-Default JRE or JDK” on page 142.
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:
Shell Commands
sh LANG=locale; export LANG
csh setenv LANG locale
4 Shut down all webMethods products that are running on the machine.
Prepare to Install webMethods Broker

Install on a UNIX System
On 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 System

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.
NFS-Mounted Partition
If 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.
mount -o hard,nointr,proto=tcp host:/path /mount_point

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:
mount -o hard,nointr,proto=tcp netappca:/wmbroker_data /var/opt/wmbroker_data
Option Description
hard 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.
For information on other ways to protect data integrity, see your NFS server
documentation.
Installation Scripts and Images

The webMethods Installer offers advanced options you can use to create and install from
installation scripts and images.
Installation Scripts
If 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 Images
If 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.
Inter-product Dependencies
Some webMethods products require the presence of other webMethods products in the
same installation directory. For example, Trading Networks Server requires Integration
Server in the same installation directory.
When you install on the local machine or create a script, the installer manages these
product dependencies for you. The installer scans the target installation directory you
specify for existing webMethods products. When you select products to install, the
installer automatically chooses all other required products that do not yet exist in the
target installation directory.
When you create an image, the target machine and installation directory are not
specified, so the installer cannot determine whether products exist there or not. You must
therefore select all required products yourself.
Before you create an image, you can run the installer as if to install in an empty directory
on the local machine. Select the product to install and note the required products that the
installer automatically selects. When you create the image, use your knowledge of the
target machine and installation directory to determine which required products you
must add to the image.
When you actually install from the image, the installer manages product dependencies as
it does when you install on the local machine or create a script; it scans the target
installation directory and automatically chooses required products. If a required product
does not already exist in the target installation directory and is not selected in the image,
the installer displays messages to that effect.


6 Using the Wizard for Advanced Product Installation
 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
 Start the Installer on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
 Start the Installer on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
 Use Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
 Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
 Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
 Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Overview
This 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.
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.
Note: When you run the webMethods Installer on an AIX system, you might receive
Java messages during installation. You can ignore these messages.
webMethods7). You can change logging behavior; for instructions, see “Change Logging
Level and File, and Add Targets” on page 60.

Start the Installer on a Windows System

The 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 53)
Start the Installer

To 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:
java -Xmxamountm -Xincgc -jar webMethodsInstaller7.jar
Start the Installer and Specify a Different System Temp Directory

To 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:
java -Xmx512m -Xincgc -Djava.io.tmpdir=/different_directory

-jar webMethodsInstaller7.jar
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.

After You Start the Installer

welcome panel.
Note: If the progress bar on the installer launcher (called Zipfusion) stops showing
progress, your anti-virus software might be interfering. Start the installer using the jar
file with the JVM -Xmx option set to at least 512 (see “Start the Installer” on page 53).
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 57. 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 62.

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

To 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
different directory to use as the temporary directory (see “Start the Installer and Specify a
Different Temporary Directory” on page 55).
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 Installer

Log 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
Start the Installer and Specify a Different Temporary Directory


-jar webMethodsInstaller7.jar -console

After You Start the Installer

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 62.

Use Advanced Options

When 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.
Note: You can ignore the JVM tab. It is not used in this release.
Create, Install from, or Edit an Installation Script

For information on installation scripts, see “Installation Scripts and Images” on page 48.
You can do the following from this panel:
To do this... Follow these steps...

Create script and Click Create script. In the Script file name field, enter the fully
install 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 Click Edit script. In the Script file name field, enter the fully
installing 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.

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

Create script from Click Install from script. In the adjacent Script file name field, type
existing script the fully qualified name of the file that contains the existing
without installing 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.
Create or Install from an Installation Image

For information on installation images, see “Installation Scripts and Images” on page 48.
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 Install

If 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 Targets

By 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 Products
If 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.
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.
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 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.

Windows only
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).

The installer lists the webMethods products for which you have purchased licenses and
that are supported on the target operating system.
Important! The installer does not distinguish among versions (Windows) or flavors
(UNIX) of an operating system. Make sure you install products only on supported
operating systems, as specified in the webMethods System Requirements.
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 Products

You 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 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.
Note: For images, you must choose required products yourself. For details, see “Inter-
product Dependencies” on page 49.
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 Selection

When 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.
Products” on page 67 for instructions on completing the panels. If you are not installing
any of these products, go to “Review and Install” on page 76.

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.
Products”, below, for instructions on completing the panels. If you are not installing any
of these products, go to “Review and Install” on page 76.

Configure Products
If 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.

Configure Trading Networks Server
database connection from

Trading Networks Server
to Trading Networks
database component

Configure Integration Server

start/shut down automatically when
start/shut down manually (Windows only) start/shut down system (Windows only)
optional, can be
supplied at startup
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.
You must decide where to store some of the data written by Integration Server. For
complete information, see “Integration Server Data Storage” on page 22.

Configure Optimize
if you have multiple network

interfaces, identify the one to
use; default is default
network interface for local
machine; do not use localhost
enabled if chosen on
product selection tree
start/shut down manually start/shut down automatically when

(Windows only) start/shut down system (Windows only)
Optimize 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.

Configure Infrastructure Data Collector
optional, can be
supplied at startup
Broker for Infrastructure

Data Collector to use to
communicate with
Optimize Analytic Engine

Configure Metadata Library

start/shut down manually (WIndows only) start/shut down system (Windows only)
database connection
from Metadata Library
to Metadata Reasoner,
Metadata Repository
database components
Important! If you specify the database connection, the Database user and Password are
required.

Configure webMethods Broker
if multiple Broker Monitors

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

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

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.)
Important! Software AG recommends creating separate sessions. You cannot later

change from a combined session to separate sessions or vice versa.

Select a preconfigured storage session for the Broker Server that can handle your
expected usage needs, as follows:
Broker Server
Files Created When to Use Startup Time
Small Configuration
32MB log file 512MB Ideal for running development Broker Fastest of all
storage file Servers or relatively few production configurations
integrations, low document volumes, and
no document logging
Medium Configuration
64MB log file Standard deployment size, fits more cases Up to twice as
4GB storage file than Small; larger maximum transaction long as for Small
size and twice the storage capacity of
Small
Large Configuration
128MB log file Suitable for production deployments with Two times longer
8GB storage file many integrations running at relatively than for Medium;
high document volumes, possibly using four times longer
document logging as well than for Small
*For complete information on Broker Server storage sessions, see the webMethods Broker Administrator’s Guide.)
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.

Configure My webMethods Server

start/shut down manually (WIndows only) 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
 Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
 Specify Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
 Specify User Name and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
 Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
 Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7 Using Console Mode for Advanced Product Installation
Overview
This 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.
Note: When you run the webMethods Installer on an AIX system, you might receive
Java messages during installation. You can ignore these messages.
webMethods7). You can change logging behavior; for instructions, see “Start the Installer
Using Advanced Options” on page 79.
Start the Installer

To 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
different directory to use as the temporary directory (see “Start the Installer and Specify a
Different Temporary Directory” on page 79).
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 Installer


java -Xmx512m -Xincgc -jar webMethodsInstaller7.jar -console
Start the Installer and Specify a Different Temporary Directory


-jar webMethodsInstaller7.jar -console
Start the Installer Using Advanced Options

You can add the parameters listed below in any order after -jar webMethodsInstaller7.jar.
Create, Install from, or Edit an Installation Script

For information on installation scripts, see “Installation Scripts and Images” on page 48.
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.
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.

Create or Install from an Installation Image

For information on installation images, see “Installation Scripts and Images” on page 48.
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, SOLAMD64

Solaris for Intel x86
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.
Use a Proxy Server to Install

If 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.

Parameter Variables
Use an HTTP proxy server to install
-proxyHost host Host name or fully qualified IP address for 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 for the
proxy server.
-socksProxyPort port Port used by the proxy server.
The default is the system on which you are
running the installer.
Change Logging Level and File, and Add Targets

By 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
-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 10

20MB file
-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.
-debugErr Writes logging information to standard error as well as
to file.
-debug number Shorthand way to specify -debugErr -debugLvl number.

Overwrite Products
If 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.
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.
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.
Parameter Variables
-overwriteInstall None.
Specify Release
Choose to install from the 7.1.x and higher release.
Specify User Name and Password

Provide the user name and password you use to log in to the webMethods Advantage
Web site.

Specify 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).

The installer lists the products for which you have purchased licenses and that are
supported on the target operating system.
Important! The installer does not distinguish among flavors of an operating system.
Make sure you install products only on supported operating systems, as specified in
the webMethods System Requirements.

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 Products

The 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.
Note: You might not see the selections until you page forward through 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 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.
Note: For images, you must choose required products yourself. For details, see “Inter-
product Dependencies” on page 49.

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 Selection

When 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 84 for instructions on
providing the information. If you are not installing any of these products, go to “Review
and Install” on page 88.
Note: To see the entire license agreement, you might have to increase the number of
lines that are visible in your console window.
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.
Read the license agreement and indicate whether you accept the terms.
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 88.
Configure Products
If you are installing any of the products listed below, the installer prompts for
configuration information.
 Configure Trading Networks Server
 Configure Integration Server
 Configure Optimize

 Configure the Infrastructure Data Collector

 Configure Metadata Library
 Configure webMethods Broker
 Configure My webMethods Server
Some products require you to supply database connection information; sample URL
formats are shown below.
RDBMS Sample URL Format

Oracle jdbc:wm:oracle://server:{1521|port};serviceName=service
[;option=value]...
Oracle jdbc:wm:oracle://server:{1521|port};serviceName=service
configured for ;AlternateServers=(server:{1521|port};…)
;ConnectionRetry=value; ConnectionDelay=value
RAC
;LoadBalancing=value [;option=value]...
SQL Server jdbc:wm:sqlserver://server:{1433|port}

;databaseName=database [;option=value]...
DB2 for Linux, jdbc:wm:db2://server:{50000|port};databaseName=database

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

[;option=value]...
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 is the name of the default schema that is used to qualify unqualified
database objects in dynamically prepared SQL statements.
Configure Trading Networks Server

Define 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.
Configure Integration Server

1 You can provide the Integration Server license key now, or you can provide it after
you start Integration Server.
2 You must decide where to store some of the data written by Integration Server. For
complete information, see “Integration Server Data Storage” on page 22.
Note: If you choose the external RDBMS but do not provide the connection
information at this time, Integration Server will start after installation, but some
features will not work.

Configure Optimize
1 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 Collector

1 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.

1 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.
Configure webMethods Broker

1 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.
Important! Software AG recommends creating separate sessions. You cannot

later change from a combined session to separate sessions or vice versa.
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.
7 Select a preconfigured storage session for the Broker Server that is adequate for your
expected usage needs.
Broker Server
Files Created When to Use Startup Time
Small Configuration
32MB log file 512MB Ideal for running development Broker Fastest of all
storage file Servers or relatively few production configurations
integrations, low document volumes,
and no document logging
Medium Configuration
64MB log file Standard deployment size, fits more Up to twice as
4GB storage file cases than Small; larger maximum long as for Small
transaction size and twice the storage
capacity of Small
Large Configuration
128MB log file Suitable for production deployments Two times longer
8GB storage file with many integrations running at than for Medium;
relatively high document volumes, four times longer
possibly using document logging as than for Small
well
*For complete information on Broker Server storage sessions, see the webMethods Broker
Administrator’s Guide.
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.
Configure My webMethods Server

1 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 Install

Review 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

 Database Users and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
 Database Administrator Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
 Character Set and Sort Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
 Page and Block Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
 Set Database Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
 Download the Database Scripts and Database Component Configurator . . . . . . . . . . . . . . . . . . 94
 Change Environment Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
 Default Storage Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
 Database Component Descriptions and Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . 96

webMethods Products and Databases

webMethods 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.
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 Users and Storage

You 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.

Database Administrator Account

You 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 Order

webMethods 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.
Important! You must set character set and sort order before creating webMethods
storage.
Oracle
webMethods 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:
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 Server
webMethods 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:

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.
You can check the database configuration using the sp_helpdb database stored procedure.
DB2
webMethods 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 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:
RDBMS Use...
DB2 for Linux, Unix, GET DATABASE CONFIGURATION command
Windows
DB2 for iSeries DSPFD command to check the database file description
Page and Block Size

Use the page and block sizes specified below for each type of RDBMS.
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
Set Database Options
Oracle
For webMethods products to function properly, you must set the
NLS_LENGTH_SEMANTICS initialization parameter to BYTE.
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.
SQL Server
The 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.

Download the Database Scripts and Database Component

Configurator
The 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:
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
Database Component Any machine on the same network as your
Configurator database server
2 Start the webMethods Installer.

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

Change Environment Settings

The 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.
Determines whether the Database Component

Setting Configurator... Default
-DtermOutOn Writes execution information to the true
console.
-DspoolOn Logs execution information. true
-DlogLevel Sets the log level to INFO (high-level INFO
information) or DEBUG (more detailed
information, including internal
processing and SQL calls).
-Dlog.dir This setting specifies the full path to the webMethods_directory\
directory in which to store the log files. common\db\logs
Make sure you have permission to write
to this directory.
Default Storage Convention

By default, all webMethods database components follow this storage convention:
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, WEBMDATA WEBMINDX WEBMBLOB
Windows tablespaces
DB2 for iSeries Default Default Default
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.

Database Component Descriptions and Installation

Requirements
Each section below provides brief descriptions of database components, followed by
installation requirements.
Note: For detailed information on concepts mentioned in the sections below, see the
relevant product documentation.
Cross Reference, Document History, IS Internal, and IS Core Audit

Log Database Components
For information on Integration Server data storage, see “Integration Server Data Storage”
on page 22.
Process Audit Log Database Component

Process 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 Component

Process 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 Component

You can archive data from the IS Core Audit Log and Process Audit Log database
components (called the “source” database components in this section). To store the
archived data, you create three target database components - the Archive database
component, a target IS Core Audit Log database component, and a target Process Audit
Log database component.
The requirements for the three target database components are as follows:
 You must create the target database components in the same type of RDBMS as the
source database components.
 For DB2, you must create the target database components on the same database
server as, but in a different database from, the source database components.
 For Oracle or SQL Server, you can do either of the following:
 Create the target database components on the same database server as the source
database components. In this case, you must create the target database
components in a different schema (Oracle) or database (SQL Server) than the
source database components.
 Create the target database components on a different database server than the
source database components, and then create a DBlink name for the Archive
database component to use to link to each source database component. If the two
source database components are on the same database server, the Archive
database component can use the same DBLink to connect to both source database
components. For instructions on specifying the DBlink name, see the webMethods
Monitor User’s Guide.
Metadata Reasoner and Metadata Repository Database Components

Metadata 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 Component

My 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

Components
Trading 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 Components

Optimize 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 Components

Monitor 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 Components

The table below lists infrastructure database components that are automatically created
when you create product-related database components.
Database Component Description

Component Tracks the database components that are created or dropped.
Tracker
DataPurge Provides a common method for purging data from the Analysis
and Process Tracker database components.
Database Provides core routines for data purge functionality.
Management
Distributed Coordinates access to resources across a distributed collection of
Locking 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 Provides a common method for configuration, logging, and
Management error handling for any database component.
The Storage database component creates default webMethods storage structures, such as
tablespaces and user credentials, for all database components.


9 Creating and Dropping Database Components
 Use the Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

 Use the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
 Use Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Use the Graphical User Interface

This 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.
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

Storage
You 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 116).
Important! When you create database components in DB2 using the Database
Component Configurator, the configurator creates the schema name in all uppercase
letters. Since DB2 is case sensitive for schema names, you must use all uppercase
letters for the schema names when you type them in URLs for JDBC connection pools,
or you will experience problems.

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:
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.

Option Action
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.
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.
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
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.
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.
For Oracle, if you 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).

For DB2, if you are going to create database components in a schema other than
the default schema for the specified database user, you must specify these
connection options in the URL, where AlternateID is the name of the default
schema used to qualify unqualified database objects in dynamically prepared
SQL statements:
c In the User ID and Password fields, do the following:

 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, and the
password for that user.
 If you are not going to create a database user and storage, specify an existing
database user and password.
 If you are performing the checkEncoding action, specify an existing database
user that has create session and create table privileges, and that database
user’s 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 Components

Before dropping, shut down all webMethods products that are connected to the database
component and back up the database component.
Configurator.
2 In the Action list, click the action to perform, as follows:
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.
displayed.
c Specify the database user and password to use to connect to the RDBMS in the
User ID and Password fields.
directory.

Drop the Storage and Revoke Database User Permissions

If 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 116).
Configurator.
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.
displayed.
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.
directory.

Use the Command Line

This 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 116).
Important! When you create database components in DB2 using the Database
Component Configurator, the configurator creates the schema name in all uppercase
letters. Since DB2 is case sensitive for schema names, you must use all uppercase
letters for the schema names when you type them in URLs for JDBC connection pools,
or you will experience problems.
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 116).
Database Component Configurator Command

You 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| RDBMS on which to perform action.
sqlserver|db2luw|db2i}
Value DBMS
oracle Oracle
sqlserver SQL Server
db2luw DB2 for Linux, UNIX, Windows
db2i DB2 for iSeries

Parameter Entry
{-c|--component} Database component version for which to perform action.
db_component
{-v|--version} version For db_component, you can specify the database component
code or name.
Code Name
ALL All database components

ANL Analysis
ARC Archive
CTR ComponentTracker
XRF CrossReference
DTP DataPurge
DBM DatabaseManagement
DSL DistributedLocking
IDR DocumentHistory
ISC ISCoreAudit
ISI ISInternal
MTR MetadataReasoner
MTD MetadataRepository
MWS MywebMethodsServer
OPM OperationManagement
PRA ProcessAudit
PRE ProcessEngine
PTR ProcessTracker
PRP Reporting
PST Staging
STR Storage
TNS TradingNetworks
TNA TradingNetworksArchive
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”).

Parameter Entry
{-pr|--product} product Product release for whose database components to perform
{-v|--version} release action.
For product, you can specify the product code or name.

Code or Product Maps to These Database Components
IS or IS Core Audit Log, IS Internal, Process

Integration Audit Log, Document History, Process
Server Engine, Staging, Reporting, and Cross
Reference
ML or Metadata Metadata Repository and Metadata
Library Reasoner
MWS or My My webMethods Server
webMethods
Server
OPTI or Analysis, Process Tracker, and Process
Optimize Audit Log
TN or Trading Trading Networks
Networks
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).

Parameter Entry
SQL Server jdbc:wm:sqlserver://server:{1433|port}
;databaseName=database[;option=value]...
DB2 for jdbc:wm:db2://server:{50000|port}

Linux, UNIX, ;databaseName=database[;option=value]...
Windows
DB2 for jdbc:wm:db2://server:{446|port}
iSeries ;locationName=location[;option=value]...
Important! When working with database components on

UNIX systems, you must enclose the URL in double
quotes.
Important! For DB2, if you are going to create 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"
AlternateID is the name of the default schema used to

qualify unqualified database objects in dynamically
prepared SQL statements.
{-u|--user} db_user If you are going to create a database user and storage in
{-p|--password} Oracle or SQL Server, specify the database user and
password
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.
If you are performing the checkEncoding action, specify an
existing database user that has create session and create
table privileges, and that database user’s password.
[{-au|--admin_user} If you are going to create a database user and storage,
db_admin_user specify the database user or operating system user and
{-ap|--admin_password}
password that has the necessary database administrator
password]
credentials.

Parameter Entry
Additional Parameters
[-r|--runCatalog] Runs the catalog action at the end of every execution.
[-t|--tablespacedir] If you are going to create 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 going to create 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.
[-pp|--printProducts] Prints webMethods products the configurator supports.
[-pe] Prints command line examples.
{-e|--export} Exports values for all required parameters except the
{-dir|--configdir} password parameters to an .xml file.
directory
{-file|--configfile}
file
{-i|--import} Imports values for all parameters from an .xml file.
{-dir|--configdir}
directory Note: Password parameters are not saved, so you must
{-file|--configfile} specify them on the command.
file

Examples
Important! On UNIX systems, you must enclose the RDBMS URL in double quotes.
Create a Database User and Storage

This command creates the two webMethods tablespaces and the database user for Oracle:
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
This command creates the webMethods database and database user for SQL Server:
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
This command creates the webMethods bufferpool and tablespaces, and grants
permissions for DB2:
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
Drop the Storage and Revoke Database User Permissions

If 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 116).
This command drops the two webMethods tablespaces for Oracle:
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
This command drops the webMethods database for SQL Server:
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

This command drops the webMethods bufferpool and tablespaces, and revokes
permissions for DB2:
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
Create Database Components

This command creates Process Audit Log v30 in Oracle:
dbConfigurator.bat -a create -d oracle -c processaudit -v 30

-l jdbc:wm:oracle://DBserver:1521;serviceName=myservicename -u webmuser
-p w3bmpass
This command recreates (drops and then creates) the latest versions of all database
components in SQL Server:
dbConfigurator.bat -a recreate -d sqlserver -c all -v latest

-l jdbc:wm:sqlserver://DBserver:1433;databaseName=webmdb -u webmuser
-p w3bmpass
This command displays the database components that currently exist in DB2 for Linux,
UNIX, Windows:
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:
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

You cannot drop the Component Tracker database component using the configurator;
you must use a script. For instructions, see “Use Database Scripts” on page 116.
This command drops Process Audit Log v30 from Oracle:
dbConfigurator -a drop -d oracle -c processaudit -v 30

-l jdbc:wm:oracle://myserver:1521;serviceName=myservicename -u webmuser
-p w3bmpass

This command drops the latest versions of all database components from SQL Server:
dbConfigurator.bat -a drop -d sqlserver -c core -v latest

-l jdbc:wm:sqlserver://myserver:1433;databaseName=webmdb -u webmuser
-p w3bmpass
The command drops the latest version of the Analysis database component from DB2 for
Linux, UNIX, Windows:
dbConfigurator.bat -a drop -d db2luw -c analysis -v latest

-l jdbc:wm:db2://DBserver:50000;databaseName=webmdb -u webmuser -p w3bmpass
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 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 Scripts

This 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 108.
Create a Database User and Storage

To list the scripts for creating a database user and storage, run this command:
dbConfigurator.{bat|sh} -a print -d {oracle|sqlserver|db2luw|db2i}

-c storage -v latest

Drop Storage and Revoke Database User Permissions

If 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:

-c storage -v latest
Create Database Components

Create 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:

-c db_component -v db_component_version
To list the scripts for creating the database components for a certain webMethods
product, run this command:

-pr product -v product_release

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

-c db_component -v db_component_version
To list the scripts for dropping the database components for a certain webMethods
product, run this command:

-pr product -v product_release


10 Completing the Installation
 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

 Configure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
 Complete the webMethods Broker Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
 Complete the Integration Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
 Complete the Metadata Library Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
 Complete the Monitor Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
 Complete the Optimize Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
 Complete the Trading Networks Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
 Connect Products to Each Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
 Connect Products to Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
 Installed JDKs and Product JDK Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
 Complete the Installation for Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Post-Installation Checklist
The 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.
Product Task Page

webMethods Broker Make sure the Broker Server is running and the 121
default Broker exists
On HP-UX systems, adjust per-process thread and 121
kernel limits
On UNIX systems, configure Broker Monitor to start 121
automatically when you start the system
Integration Server On UNIX, IBM i5, and Mac systems, if you are using a 122
Sun JDK, increase PermGen space
On UNIX, IBM i5, and Mac systems, increase file 123
descriptors
On IBM i5 Systems, prevent memory problems 124
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 126
Java 5 32-bit IBM JDK 1.5
Monitor On UNIX systems, if you are not using SVG, set up 127
graphical display
Optimize Configure Optimize (see the webMethods Central
Configuration and Deployment Guide)
Most products Connect products to each other 129
Most products Connect products to webMethods database 136
components
Configure Logging
You can log various types of data for webMethods products. For detailed information
and instructions on setting up logging, see the webMethods Logging Guide.

Complete the webMethods Broker Installation
Make Sure the Broker Server is Running and the Default Broker
Exists
After 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:
broker_status [Broker #1@]Broker Server_host[:Broker Server_port]
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 Systems
If 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 Systems

By 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 aw_broker71 to the appropriate UNIX
startup directory.
3 Replace the “aw” in aw_broker71 with “Snumber,” where number is the run, or
priority, level (for example, S45broker71). 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, S45broker71_1,
S45broker71_2, and so on).

Set Locale on UNIX Systems

If 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 Systems

On 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:
chdev -l sys0 -a fullcore=true
 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 Systems

If you are using a Sun JDK with Integration Server, you must increase the permanent
generation (PermGen) space from the default of 64MB to at least 128MB. By default, the
webMethods Installer installs a Sun JDK for Integration Server 7.1.x 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.
Note: If you receive java.lang.OutOfMemoryError: PermGen space exceptions when

running Integration Server, set the PermGen space higher than 128MB.
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}

Increase File Descriptors and Change Permissions on UNIX, IBM i5,

and Mac Systems
On 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.
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.
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 Server

The tasks below require you to start Integration Server.
System Action
Windows On the Start menu, go to ProgramswebMethods7ServersIntegration
application Server 7.1.
Windows Go to the Services window and start the service webMethods Integration
service Server 7.1.
All other Go to the Integration Server_directory/bin directory and run the server.sh
systems script.
Open Integration Server Administrator in either of these ways:

 On the Windows Start menu, go to ProgramswebMethods7Integration Server
Administrator 7.1.
 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.

Prevent Memory Problems on IBM i5 Systems

If 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
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.
c Locate the JAVA_MEMSET parameter and set it as follows:

JAVA_MEMSET="-ms${JAVA_MIN_MEM}"
d Save and close the file.

Streamline Integration Server

By 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, Services that support business processes and tasks.
WmDesigner,
WmOptimize,
WmTaskClient
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.

Package Contents
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.
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 123).
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.
Important! Never disable the WmRoot or WmPublic package.
Drop Redundant Database Component

If 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 136 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

If 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 Systems

If 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 142.

Complete the Monitor Installation
Set Up Graphical Display on UNIX Systems

Monitor 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}
Note: If the JAVA_MEMSET line already includes the -server option, add the
-Djava.awt.headless option after the -server option.
Complete the Optimize Installation
Configure Optimize
You must configure Optimize using its Central Configurator. For instructions, see the
webMethods Central Configuration and Deployment Guide.
Drop Redundant Database Component

If 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 136 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 Trading Networks Installation
Prevent Memory Problems on AS/400

If Integration Server and Trading Networks Server are installed on an AS/400 system,
prevent memory problems when you try to connect from Trading Networks Console by
increasing the Integration Server heap space, as follows:
1 Shut down Integration Server.
2 Go to the Integration Server_directory\bin directory and open the server.sh file in a text
editor.
3 Locate the JAVA_MAX_MEM parameter and set it as follows:
JAVA_MAX_MEM=512M

Connect Products to Each Other

This section explains how to do the following:
 Connect Process Engine to Task Engine
 Connect Monitor to My webMethods Server
 Connect Optimize Analytic Engine to My webMethods Server
 Connect Process Engine to Optimize Analytic Engine
 Connect Integration Server to webMethods Broker Default Broker
 Connect Trading Networks Server to My webMethods Server
 Connect Integration Server to the Metadata Library
 Connect Designer to Other Products (for example, Metadata Library)
 Connect Deployer to Source and Target webMethods Products
Note: If you installed all products at the same time, and did not change any port
settings or default passwords after installation, many of these connections are set up
automatically.
Start Integration Server and My webMethods Server

To create the connections, you need Integration Server and My webMethods Server.
Start Integration Server and open Integration Server Administrator (see “Increase File
Descriptors and Change Permissions on UNIX, IBM i5, and Mac Systems” on page 123).
Start My webMethods Server as follows:
System Action
Windows On the Start menu, go to ProgramswebMethods7ServersMy
application webMethods Server 7.1.
Windows Go to the Services window and start the service webMethods My
service webMethods Server 7.1.
All other Go to the My webMethods Server_directory/bin directory and run this
systems command:
mws -s default start
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.
Important! After you finish connecting My webMethods Server to the other

webMethods products, you will have to restart it before you can start using it.
Connect Process Engine to Task Engine

The Process Engine must connect to the Task Engine so the Task Engine can provide
results of process steps that required human intervention to running processes.
Note: If you install multiple Process Engines in a Process Engine cluster, all Process
Engines in the cluster share a Broker, the same database component, or both, so the
Task Engine need only connect to one Process Engine to connect to all.
If you are going to cluster Task Engines, see the My webMethods Server High
Availability Documentation Supplement for connection instructions.
Identify the Process Engines to the Task

Engine... Identify the Task Engine to the Process Engines...
1 On the My webMethods Server 1 In the Integration Server Administrator
that hosts the Task Engine, go to for an Integration Server that hosts a
the AdministrationMy Process Engine in your Process Engine
webMethodsSystem Settings page. cluster, go to the PackagesManagement
2 In the Integration Server (Process page and click for the WmTaskClient
Engine host) area, identify an package.
Integration Server that hosts a 2 In the Task Server URL field, type the URL
Process Engine in your Process of the My webMethods Server that hosts
Engine cluster. The default port the Task Engine (for example,
for Integration Server is 5555. http://myserver:8585).
3 If My webMethods Server should 3 In the Task Server Username and Task Server
use SSL to communicate with the Password fields, accept the default values
Integration Server, select the Use sysadmin and manage.
SSL check box.
4 Click Save.
4 Click Save.
5 Reload the WmTaskClient package by
returning to the PackagesManagement
page and clicking in the WmTaskClient
row.

Connect Monitor to My webMethods Server

Monitor must connect to the My webMethods Server that hosts the Monitor user
interface so My webMethods can display Monitor data.
Note: If you are going to cluster My webMethods Servers, see the My webMethods
Server High Availability Documentation Supplement for connection instructions.
Identify Monitor to My webMethods Server... Identify My webMethods Server to Monitor...

1 On the My webMethods Server that 1 In Integration Server Administrator
hosts the Monitor user interface, go to for the Integration Server that hosts
the AdministrationMy webMethods Monitor, go to the
System Settings page. PackagesManagement page and click
2 In the Server Settings area, under for the WmMonitor package.
Integration Server (Monitor) Host, identify 2 In the MWS Password field, type the
an Integration Server that hosts password for Monitor to use to
Monitor, as follows: connect to the My webMethods Server
a If a blank row is not available, that hosts the Monitor user interface.
click Add to add one. The default is manage.
b In the Name field, supply a unique 3 If the My webMethods Server is not

name for the Integration Server. on the same machine as the
Integration Server, edit the MWS Host
c Provide the host and port for the and MWS Port fields to identify the My
Integration Server. The default webMethods Server host machine and
port for Integration Server is 5555. port.
d If My webMethods Server should 4 If you need to edit any other fields,
use SSL to communicate with the see the webMethods Monitor User’s
Integration Server, select the Use Guide.
SSL check box.
5 Click Submit.
3 If you want to identify other
Integration Servers that host Monitor, 6 Reload the WmMonitor package by
repeat the previous step as necessary, returning to the
and choose the Integration Server to PackagesManagement page and
serve as the default for users. Users clicking in the WmMonitor row.
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.

Connect Optimize Analytic Engine to My webMethods Server

The Optimize Analytic Engine must connect to the My webMethods Server that hosts the
Optimize user interfaces so My webMethods can display Optimize data.
Note: If you install multiple Analytic Engines, all will share the same database
components, so My webMethods Server need only connect to one to connect to all.
Identify an Analytic Engine to My webMethods Identify My webMethods Server to the Analytic

Server... Engines...
1 On the My webMethods Server that If you configured Optimize using the
hosts the Optimize user interfaces, go Central Configurator, you already
to the AdministrationMy webMethods identified the My webMethods Server
System Settings page. that hosts the Optimize user interfaces to
your Analytic Engines. If not, do so using
2 In the Server Settings area, under
the instructions in the webMethods Central
Analytic Engine Host, identify an
Configuration and Deployment Guide.
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.

Connect Process Engine to Optimize Analytic Engine

If processes are enabled for analysis, the Process Engine must connect to the Optimize
Analytic Engine so My webMethods can display process metrics.
By default, the URL provided to the Process Engines for this Broker is
broker://localhost:6849/Broker#1/analysis. If the 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.
Note: If you install multiple Process Engines in a Process Engine cluster, all Process
Engines in the cluster share the Broker.
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.
Important! Do not change the broker:// or /analysis parts of the URL.
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 Default Broker

1 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.
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.

Field Setting
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.
3 Click Save Changes, then restart Integration Server.
Connect Trading Networks Server to My webMethods Server

Trading Networks Server must connect 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 Integration Server to the Metadata Library

1 In Integration Server Administrator, go to the SolutionsAsset Publisher page.
2 Click Configuration, then click Edit Configuration and complete the fields below.
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 fully qualified 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.
3 Click Save Changes.
Connect Designer to Other Products

For instructions on connecting Designer to products other than Metadata Library, see the
Designer online help.
Connect Designer to the Metadata Library

1 Start Designer. On the Start menu, go to ProgramswebMethods7ToolsDesigner 7.1.
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.
Field Setting
Host Name or fully qualified 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.

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 Products

Configure 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.
Connect Products to Database Components

This 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.
For instructions on defining the database connections for Designer, see the Designer
online help.
Database Connections for Integration Server and Trading Networks

Server
You 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 Internal, IS
Core Audit Log, Process Audit Log, and Process Engine 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, and Archive database
components, you must point those functions at the appropriate connection pools as well.
Note: If you chose the embedded database during Integration Server installation, the
installer created a connection pool called Embedded Database Pool and pointed the IS
Internal and Cross Reference functions at that pool. Do not point any other functions
at that pool.
Note: If you chose the embedded database, Integration Server writes the IS Core Audit
Log to flat files. If you want Integration Server to write the IS Core Audit Log to an
external RDBMS instead, create the IS Core Audit Log and Process Audit Log
database components and point the corresponding functions at the appropriate
connection pools.
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 Pool

1 Start Integration Server and open Integration Server Administrator (see “Increase File
Descriptors and Change Permissions on UNIX, IBM i5, and Mac Systems” on
page 123).
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 for the pool.
Description
Associated Database driver to use.
Driver Alias

Field Entry
Database URL for the database server. Below are sample formats.
URL
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 …]
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"
AlternateID is the name of the default schema that is used to qualify

unqualified database objects in dynamically prepared SQL
statements.
User Id Database user for Integration Server to use to communicate with the
database.
Password Password for the database user.

Field Entry
Minimum Minimum number of connections the pool must keep open at all
connections 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 Maximum number of connections the pools can have open at one
connections 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.
3 Click Save Settings.

Point a Function at a Connection Pool

1 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 Usage

The table below lists the JDKs that are installed by the webMethods Installer on each
operating system that the webMethods product suite supports. The indicated products
use the installed JDK by default.
64 Bit 32 Bit
Run-time Products Windows Solaris Linux HP-UX AIX Windows Linux
Integration Server,
Trading Networks
64-bit
Server,
Sun
My webMethods 32-bit Sun 64-bit 64-bit 64-bit
1.5_15
Server, 1.5_15 Sun HP IBM 32-bit Sun
Optimize with 64-bit 1.5_ 1.5_ 1.5 1.5_15
Metadata Library, extension* 15 12 SR7**
32-bit
webMethods
Sun
Broker Java and
1.5_15
JMS APIs
*By default, this JDK runs in 32-bit mode. You can switch to 64-bit mode. For instructions, see “Configure
Run-Time Products to Use 64-Bit Mode on Solaris and HP-UX Systems” on page 141.
**Metadata Library on an AIX system requires the Java 5 32-bit IBM JDK 1.5. You must download and install
the JDK yourself.

Windows
Development Tools 64 Bit 32 Bit
Blaze Advisor, Designer
32-bit Sun 1.5_15
Developer, Trading Networks Console 64-bit Sun 1.5_15
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.
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 142.
Configure Run-Time Products to Use 64-Bit Mode on Solaris and

HP-UX Systems
On 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 1 Go to the {Integration Server| Infrastructure Data
Server (and Collector}_directory/bin directory and open the server.sh file in a
packages) and text editor.
Optimize
2 Locate the line #JAVA_D64=”-d64” and uncomment it, as
Infrastructure
follows:
Data Collector
JAVA_D64=”-d64”

Run-time Product Steps

Optimize 1 Go to the Optimize_directory/
Analytic Engine, {analysis|prediction|dataCollector}/bin directory and open
Prediction the startup{Analytic|Prediction|DataCollector}Engine.sh file
Engine, and Web in a text editor.
Service Data
2 Locate the line GLUE_OPTS="$GLUE_OPTS -Xss256k" and
Collector
add -d64, as follows:
GLUE_OPTS="$GLUE_OPTS –d64 -Xss256k"

My webMethods 1 Go to the My webMethods Server_directory/bin directory and
Server open the setenv.sh file in a text editor.
2 Locate the line {rem|#} JAVA_D64=-d64 and uncomment, as
follows:
JAVA_D64=-d64
Redirect Products to Use a Non-Default JRE or JDK

By 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.
Note: Software AG tests webMethods products only with the JDKs installed by the
webMethods Installer.
Run-time Products
Product Steps to Redirect to a Non-Default JRE or JDK

webMethods Require JDK 1.5.
Broker Java and
In the steps below, command is any command other than
JMS APIs
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 Require JRE 1.5. If you are using Integration Server with
Server (and Developer, Integration Server requires JDK 1.5.
packages),
Go to the {Integration Server|Infrastructure Data
Optimize
Collector}_directory\bin directory and open the server.bat or
Infrastructure
server.sh file in a text editor. Edit the JAVA_DIR parameter to
Data Collector
point to the JRE (or, for Integration Server, 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.


My webMethods Requires JDK 1.5.
Server
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 Require JDK 1.5.
Analytic Engine,
1 Log on to the host machine for the component.
Prediction
Engine, and Web 2 Go to the Optimize directory\component\bin directory and open
Service Data the kenobiEnv.bat or kenobiEnv.sh file in a text editor.
Collector
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.

Development Products

Blaze Advisor Requires JRE 1.5. You cannot redirect it from the default.
Designer, Require JRE 1.5.
Developer (and
Go to the {Designer|Developer}_directory\bin directory and open
plug-ins)
the {designer|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 Requires JRE 1.5.
Networks
Go to the Trading Networks Console_directory\bin directory and
Console
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.
Complete the Installation for Other Products

Some 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.


11 Uninstalling Products
 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
 Uninstall on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
 Uninstall on a UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
 Complete the Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Overview
Uninstall 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:
System Mode
Windows wizard
UNIX or Mac wizard or console mode
IBM i5 console mode
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
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 60 or “Start the Installer
Using Advanced Options” on page 79.
Uninstall on a Windows System

To 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.
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.
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.
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

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.
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:
xhost +remote_host
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:
export DISPLAY=uninstaller:0.0
3 Shut down all webMethods products and all other applications that are running on
the machine that contains the webMethods products you are uninstalling.
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.
4 Go to the webMethods_directory/bin directory and enter the appropriate command, as

follows:
Uninstall Mode Command

Wizard uninstall
Console mode uninstall -console
The uninstaller starts; it looks almost identical to the installer.

5 Choose the products to uninstall.
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 Uninstallation

For 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 Systems

On 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 Snumberbroker71 (for example, S45broker71). 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,
S45broker71_1, S45broker71_2, and so on). You can delete these scripts from the UNIX
startup directories.
Complete the Deployer Uninstallation

Uninstall 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
Component Default Port Protocol/Port Type

webMethods Broker
Broker Server 6849 (SSL not TCP
enabled)
6848 (SSL enabled)
6847 (SSL
authenticated)
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 24547 Proprietary binary
clustered Integration Servers protocol over TCP
Diagnostics 9999 HTTP
Metadata Library 8090 HTTP/HTTPS
Java debugger (available when My 5000 HTTP
webMethods Server is stared with -d
option)
AJP13 - Jetty listens to external Web 8009 AJP13
server, if using one (not enabled by
default)
Jetty HTTP Web server and 8585 HTTP
webMethods product user interfaces
Jetty HTTPS Web server (not enabled by 8443 HTTPS
default)
Communication with Central 15002 HTTP
Configuration

A Default Ports
Component Default Port Protocol/Port Type

Optimize
Analytic Engine
Communication with Central 15000 HTTP/HTTPS
Configuration
Broker client JMS API 6849 TCP/IP
My webMethods Server 8585 HTTP
Internal Web service registry 12503 HTTP
Infrastructure Data Collector 5555 HTTP
Prediction Engine
Configuration
Web Service Data Collector
Configuration

Web Methods Installation Guide 7 1 2 and 7 2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Web Methods Installation Guide 7 1 2 and 7 2

Uploaded by

Copyright:

Available Formats

Title Page

Version 7.1.2 and 7.2

Document ID: WEBM-IG-712_72-20090501

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2. Software and Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3. International Operating Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4. Using the Wizard for Simple Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

webMethods Installation Guide Version 7.1.2 and 7.2 3

Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5. Preparing for Advanced Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6. Using the Wizard for Advanced Product Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4 webMethods Installation Guide Version 7.1.2 and 7.2

7. Using Console Mode for Advanced Product Installation . . . . . . . . . . . . . . . . . . . . . . . . 77

8. Preparing for Database Component Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

webMethods Installation Guide Version 7.1.2 and 7.2 5

My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

9. Creating and Dropping Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

10. Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

6 webMethods Installation Guide Version 7.1.2 and 7.2

Complete the Optimize Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

11. Uninstalling Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

A. Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

webMethods Installation Guide Version 7.1.2 and 7.2 7

8 webMethods Installation Guide Version 7.1.2 and 7.2

webMethods Installation Guide Version 7.1.2 and 7.2 9

webMethods Central Documentation Directory

10 webMethods Installation Guide Version 7.1.2 and 7.2

webMethods Advantage Bookshelf

Software AG Developer Community

webMethods Installation Guide Version 7.1.2 and 7.2 11

12 webMethods Installation Guide Version 7.1.2 and 7.2

webMethods Installation Guide Version 7.1.2 and 7.2 13

14 webMethods Installation Guide Version 7.1.2 and 7.2

Below are additional options.

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

webMethods Installation Guide Version 7.1.2 and 7.2 15

Below are additional options.

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

16 webMethods Installation Guide Version 7.1.2 and 7.2

webMethods Installation Guide Version 7.1.2 and 7.2 17

Portlet and Web Application Development

Designer My webMethods Server database

Product Required Database Components

Blaze Advisor Integration Server

Central Configurator interface

18 webMethods Installation Guide Version 7.1.2 and 7.2

webMethods Installation Guide Version 7.1.2 and 7.2 19

Infrastructure Data Collector

Optimize and Central

20 webMethods Installation Guide Version 7.1.2 and 7.2

webMethods Installation Guide Version 7.1.2 and 7.2 21

Integration Server Data Storage

22 webMethods Installation Guide Version 7.1.2 and 7.2

webMethods Installation Guide Version 7.1.2 and 7.2 23

Integration Development Database Components

24 webMethods Installation Guide Version 7.1.2 and 7.2

Product Database Components Optional Database Components

webMethods Installation Guide Version 7.1.2 and 7.2 25

26 webMethods Installation Guide Version 7.1.2 and 7.2

 Operating Systems, JDKs, Browsers, RDBMSs, and Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

webMethods Installation Guide Version 7.1.2 and 7.2 27

Operating Systems, JDKs, Browsers, RDBMSs, and Drivers

Standard Product Hardware Support and Requirements

28 webMethods Installation Guide Version 7.1.2 and 7.2