8-2 installing webmethods products

8/10/2019 8-2 Installing WebMethods Products

http://slidepdf.com/reader/full/8-2-installing-webmethods-products 1/154

Page

Installing webMethods Products

Version 8.2

June 2013



yright

This document applies to webMethods Product Suite Version 8.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 © 2010-2013 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America, and/or

their licensors.

The name Software AG, webMethods and all Software AG product names are either trademarks or registered trademarks of Software AGand/or Software AG USA, Inc. and/or its Subsidiaries and/or their licensors. Other company and product names mentioned herein may betrademarks of their respective owners.

Detailed information on trademarks and patents owned by Software AG and/or its subsidiaries is located athttp://documentation.softwareag.com/legal/.

Use of this software is subject to adherence to Software AG's licensing conditions and terms. These terms are part of the productdocumentation, located at http://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s).

This software may include portions of third-party products. For third-party copyright notices and license terms, please refer to “LicenseTexts, Copyright Notices and Disclaimers of Third-Party Products”. This document is part of the product documentation, located athttp://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s).

Document ID: WEBM-INST-82SP2-20130618

http://documentation.softwareag.com/legal/








Installing webMethods Products Version 8.2 3

Table of Contents

About this Gu ide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Deprecation of webMethods Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Documentation Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Online Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Legal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1. Software and Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Operating System Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Special Considerations for Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Special Considerations for webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

RDBMS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Browser Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

JDK Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Additional Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Available Disk Space in System Temp or Temporary Directory . . . . . . . . . . . . . . . . . . 18

Product Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2. Installi ng and Uninstalling CentraSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Operating System, Browser, and JDK Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Shut Down SoftwareAG Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Prepare Your Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Install CentraSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Start the Installer, Provide General Information, and Choose CentraSite . . . . . . . . . . 23

Supply Product Configuration Information in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . 23

System Management Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Sudo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Integrated Authentication Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

CentraSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Supply Product Configuration Information in Console Mode . . . . . . . . . . . . . . . . . . . . 28

System Management Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Sudo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28


CentraSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Uninstall CentraSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29



4 Installing webMethods Products Version 8.2

3. Installi ng and Uninstalling ApplinX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Typical Development Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32


Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Shut Down SoftwareAG Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33


Install ApplinX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Start the Installer, Provide General Information, and Choose ApplinX . . . . . . . . . . . . . 35

Supply Product Configuration Information in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . 35

ApplinX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35


ApplinX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Uninstall ApplinX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4. Installi ng and Unins talling EntireX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Typical Development Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40


Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Shut Down SoftwareAG Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41


Install EntireX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Choose Bit Mode on Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Provide General Information and Choose EntireX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Supply Product Configuration Information in GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . 45


Sudo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

EntireX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48




Sudo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

EntireX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51


Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Set Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Register Daemons and Set File Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Uninstall EntireX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5. Installing and Uninstalling All Other webMethods Products . . . . . . . . . . . . . . . . . . . . . 55

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Typical Development Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56




Application Integration Development Typical Installation . . . . . . . . . . . . . . . . . . . . . . . 56

Local Service Development Typical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Composite Applications Development Typical Installation . . . . . . . . . . . . . . . . . . . . . . 58

Process Design Typical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Monitoring and Reporting Typical Development Installation . . . . . . . . . . . . . . . . . . . . 59Complex Event Processing Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Service-Oriented Architecture Typical Development Installation . . . . . . . . . . . . . . . . . 60

Deployment Typical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Shut Down SoftwareAG Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61


Prepare to Install webMethods Broker on a UNIX System . . . . . . . . . . . . . . . . . . . . . . 63

Prepare to Install Integration Server on UNIX, IBM i5/OS, and Mac Systems . . . . . . . 64

Prepare to Install Mobile Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Prepare to Install Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Prepare to Install Report Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Database Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Install Using the Installer GUI Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Start the Installer, Provide General Information, and Choose the Products to Install . 66

Supply Product Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Sudo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

ActiveTransfer Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Content Service Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Event Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

OneData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Optimize Application Monitoring Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Optimize Infrastructure Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Report Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Rules Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Install Using the Installer Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Start the Installer, Provide General Information, and Choose the Products to Install . 86

Sudo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Supply Product Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

ActiveTransfer Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Content Service Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Event Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

OneData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90




Optimize Application Monitoring Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Optimize Infrastructure Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Report Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Rules Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Create Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Register Daemons and Set File Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Complete the webMethods Broker Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Make Sure Broker Server is Running and the Default Broker Exists . . . . . . . . . . . 92

Enable Full Core Dumps on AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Complete the Communicate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Complete the Content Service Platform Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Complete the Local Service Development Installation . . . . . . . . . . . . . . . . . . . . . . . . . 93

Complete the Integration Server Installation on UNIX, IBM i5/OS, and Mac Systems . 93

Complete the MashZone Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Complete the Mobile Designer Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Complete the My webMethods Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Connect Products to Each Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Start Integration Server and My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Start Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Start My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Connect Designer to Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Connect Event Publishers and Consumers to the Event Type Store . . . . . . . . . . . . . . 96

Connect Process Engines to Task Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Connect Process Engine to Optimize Analytic Engine . . . . . . . . . . . . . . . . . . . . . . . . . 97

Connect Integration Server to the Default Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Connect Products to Their User Interfaces in My webMethods . . . . . . . . . . . . . . . . . . 99

Connect ActiveTransfer Servers to My webMethods Server . . . . . . . . . . . . . . . . . 99

Connect Integration Servers to My webMethods Server . . . . . . . . . . . . . . . . . . . . 99

Connect Monitor to My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Connect Optimize Analytic Engines to My webMethods Server . . . . . . . . . . . . . . 100

Connect Report Server to My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . 101

Connect Rules Engines to My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . 101

Connect Trading Networks Server to My webMethods Server . . . . . . . . . . . . . . . 102

Connect Products to CentraSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Connect Integration Server to CentraSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Connect Mediator to CentraSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

6. Creating and Dropping Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

webMethods Products and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Data Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Integration Server Data Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Embedded Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108




External RDBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Product Database Component Descriptions and Installation Requirements . . . . . . . . 110

ActiveTransfer Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Archive Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Blaze Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111BusinessRules Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Integration Server ISCoreAudit, ISInternal, Cross Reference, Distributed Locking,

DocumentHistory, and DistributedLocking Database Components . . . . . . . . . . 111

MediatorEvents Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Monitor Staging and Reporting Database Components . . . . . . . . . . . . . . . . . . . . 112

MywebMethodsServer Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

OneDataMetadata, OneDataWorkArea, OneDataReleaseArea Database Components

113

Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Analysis Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113ProcessTracker Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

CentralConfiguration Database Component . . . . . . . . . . . . . . . . . . . . . . . . . 114

Process Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

ProcessAudit Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

ProcessEngine Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Report Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

SuiteReporting Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

SuiteReporting-Common Database Component . . . . . . . . . . . . . . . . . . . . . . 115

TradingNetworks and TradingNetworksArchive Database Components . . . . . . . 115

Infrastructure Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Preparing for Database Component Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Database Users and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Database Administrator Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Character Set and Sort Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Page and Block Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Set Database Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Default Storage Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Download the Database Component Configurator and Database Scripts . . . . . . . . . . . . . . 120

Use the Database Component Configurator Graphical User Interface . . . . . . . . . . . . . . . . 121

Create Database Components, Database User, and Storage . . . . . . . . . . . . . . . . . . . 122

Start the Database Component Configurator GUI . . . . . . . . . . . . . . . . . . . . . . . . . 122

Choose the Action to Perform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Specify the Connection to the RDBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Create Database Components, Database User, and Storage . . . . . . . . . . . . . . . 125




About this Guide

This guide provides product-specific preparation, installation, and uninstallationinstructions for installing and uninstalling the latest 8.2 releases of webMethods productsuite products.

Note: For instructions on installing products not covered in this guide, see the productdocumentation.

This guide is intended for use with Using the Software AG Installer. That guide explainshow to prepare your machine to use the Software AG Installer, and how to use theSoftware AG Installer and Software AG Uninstaller to install and uninstall yourproducts.

Important! If you want to upgrade products, you must use the instructions in theappropriate product upgrade guide. The instructions in this installation guide do notcover upgrades, so following the instructions in this guide for upgrades would haveunpredictable results.

Deprecation of webMethods Developer

webMethods Developer is deprecated and does not support all the features ofwebMethods Integration Server 8.2. Software AG recommends the use of Software AG

Designer for service development.

Document Conventions

Convention Description

Bold Identifies elements on a screen.

Narrowfont Identifies storage locations for services on webMethods IntegrationServer, 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 toyour own situation or environment. Identifies new terms the firsttime they occur in the text.

Monospace font Identifies text you must type or messages displayed by the system.



About this Guide


Documentation Installation

You can download the product documentation using the Software AG Installer.Depending on the release of the webMethods product suite, the location of thedownloaded documentation will be as shown in the table below.

Online Information

You can find additional information about Software AG products at the locations listed below.

{ } Indicates a set of choices from which you must choose one. Typeonly the information inside the curly braces. Do not type the { }symbols.

| Separates two mutually exclusive choices in a syntax line. Type oneof these choices. Do not type the | symbol.

[ ] Indicates one or more options. Type only the information inside thesquare brackets. Do not type the [ ] symbols.

... Indicates that you can type multiple options of the same type. Typeonly the information. Do not type the ellipsis (...).

For webMethods... The documentation is downloaded to...

8.x and 9.x A central directory named _documentation in the maininstallation directory (Software AG by default).

7.x A central directory named _documentation in the maininstallation directory (webMethods by default).

6.x The installation directory of each product.

If you want to... Go to...

Access the latest version of productdocumentation.

Software AG Documentation website

http://documentation.softwareag.com

Convention Description

http://documentation.softwareag.com/





About this Guide

Find information about product releases andtools that you can use to resolve problems.

See the Knowledge Center to:

Read technical articles and papers.

Download fixes and service packs.

Learn about critical alerts.

See the Products area to:

Download products.

Download certified samples.

Get information about product

availability.

Access older versions of productdocumentation.

Submit feature/enhancement requests.

Empower Product Support website

https://empower.softwareag.com

Access additional articles, demos, andtutorials.

Obtain technical information, usefulresources, and online discussion forums,moderated by Software AG professionals,to help you do more with Software AG

technology.

Use the online discussion forums toexchange best practices and chat withother experts.

Expand your knowledge about productdocumentation, code samples, articles,online seminars, and tutorials.

Link to external websites that discussopen standards and many webtechnology topics.

See how other customers are streamliningtheir operations with technology fromSoftware AG.

Software AG Developer Community for

webMethods

http://communities.softwareag.com/

If you want to... Go to...

https://empower.softwareag.com/KnowledgeCenter/default.asp

https://empower.softwareag.com/Products/default.asp

https://empower.softwareag.com/



https://empower.softwareag.com/

https://empower.softwareag.com/Products/default.asp




About this Guide


Legal

This document applies to webMethods Product Suite Version 8.2 and to all subsequentreleases.

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

Copyright © 2010-2013 Software AG, Darmstadt, Germany and/or Software AG USA,Inc., Reston, VA, United States of America, and/or their licensors.

The name Software AG, webMethods and all Software AG product names are eithertrademarks or registered trademarks of Software AG and/or Software AG USA, Inc.and/or its Subsidiaries and/or their licensors. Other company and product namesmentioned herein may be trademarks of their respective owners.

Detailed information on trademarks and patents owned by Software AG and/or itssubsidiaries is located at http://documentation.softwareag.com/legal/.

Use of this software is subject to adherence to Software AG's licensing conditions andterms. These terms are part of the product documentation, located athttp://documentation.softwareag.com/legal/ and/or in the root installation directory ofthe licensed product(s).

This software may include portions of third-party products. For third-party copyrightnotices and license terms, please refer to “License Texts, Copyright Notices andDisclaimers of Third-Party Products”. This document is part of the productdocumentation, located at http://documentation.softwareag.com/legal/ and/or in the rootinstallation directory of the licensed product(s).

DocumentID: WEBM-INST-82SP2-20130618










1 Software and Hardware Support and Requirements

Operating System Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

RDBMS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Browser Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

JDK Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Product Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18





Operating System Support

For information on operating systems that are supported by your webMethods products,see the webMethods System Requirements.

Special Considerations for Integration Server

Integration Server supports Web applications and JavaServer Pages (JSPs) onWindows and Solaris systems.

Integration Server supports C/C++ and Visual Basic code generation on OS/JVM bitmode 32/32 and 64/32 platforms only.

Integration Servers on IBM i5/OS or Mac systems cannot connect to webMethodsBrokers using SSL.

Integration Servers on IBM i5/OS systems do not support C/C++ code generation.

Special Considerations for webMethods Broker

On Windows and Linux systems, Software AG offers dedicated 64-bit and 32-bitversions of Broker Server. The 64-bit Broker Server is supported on 64-bit systems.The 32-bit Broker Server is supported on 32-bit systems.

On Solaris, HP-UX, and AIX systems, Broker Server is a 64-bit binary application.Before you install Broker Server on one of these systems, you must configure theoperating system kernel to run in 64-bit mode.

On Solaris, HP-UX, and AIX systems, if you install the webMethods Broker C API,Software AG installs both a 64-bit and a 32-bit version. The 64-bit C API is installed inthe Software AG_directory/Broker/lib directory. The 32-bit API (LP32 Object Code) isinstalled in the Software AG_directory/Broker/lib32 directory.

RDBMS Support

For information on RDBMSs that are supported by your webMethods products, see thewebMethods System Requirements. For information on supported database drivers, see“webMethods Products and Databases” on page 106.

Browser Support

webMethods products require an Internet browser. For information on supported browsers, see the webMethods System Requirements.





JDK Support

On IBM i5/OS and Mac systems, you must install a JDK to run the installer anduninstaller yourself, as instructed later in this guide. The installer configures the products

to use this JDK, so the JDK must be one that is supported by your products.

On IBM i5/OS and Mac systems, the installer does not install a JDK when you install yourproducts. Instead, you install an appropriate JDK to run the installer (see Using theSoftware AG Installer), and the installer automatically configures most webMethodsproducts you install to use that JDK.

Note: If the installer does not configure a product to use the installed JDK, instructionslater in this guide explain how to do so manually.

The installed JDKs contain Java Cryptography Extension (JCE) Limited Strength Jurisdiction Policy Files 6.0. If you want your products to be able to run in FIPS mode, or

use algorithms such as 256-bit AES, your JVM must use JCE Unlimited Strength Jurisdiction Policy Files 6.0. Download those files from the appropriate Web site below tothe jre/lib/security directory that you use to run Integration Server and install the filesusing the instructions in the vendor documentation.

Hardware Requirements

The table below lists the minimum and recommended hardware requirements for mostwebMethods products. Recommended amounts are shown in parentheses.

Products that are installed as packages on Integration Server (such as Mediator) have nohardware requirements above the host Integration Server.

For hardware requirements for ApplinX, EntireX, and CentraSite, see the chapters forthose products in this guide.

Important! The hardware requirements below are for products only. They do not include

500MB of hard drive space for Software AG infrastructure shared libraries required bymost products and installed once per installation directory. They do not includerequirements for supporting software such as RDBMSs. You must determine the overallhardware requirements for each of your machines based on the overall requirements ofyour operating system and software.

JDK Web Site

Oracle andHP

http://www.oracle.com/technetwork/java/javase/downloads/index.html

IBM http://www.ibm.com/developerworks/java/jdk/security/index.html



http://www.ibm.com/developerworks/java/jdk/security/index.html

http://www.ibm.com/developerworks/java/jdk/security/index.html







Product Hard Drive Space RAM CPUs

ActiveTransfer Server 100MB (200MB) 512MB 1

Blaze Advisor 200MB 1GB (2GB) 1

webMethods Broker 750MB (1.2GB) 512MB (2GB) 1

Content Service Platform 250MB 512MB 1

Communicate

Server 100MB 2GB 1

Aculab Telephony Hardware Drivers 500MB

Database Component Configurator 60MB

Deployer 20MB

Designer with all Software AG plug-ins 1.6GB 1.5GB (2GB) 1 (2)

Developer 100MB (200MB) 128MB (256MB) 1

Event Server 300MB (450MB) 256MB (512MB) 1

Integration Server 200MB (350MB) 256MB (512MB) 1

MashZone client and server 300MB 512MB (2GB) 1

Mobile Designer 1GB 1GB 1

My webMethods Server 300MB 1GB (2GB) 1

OneData

Server 512MB 2GB (4GB) 1 (2)

MDR Modules 50MB

Customer MDM Template 20MB

Optimize

Analytic Engine 100MB 2GB* 1

Prediction Engine 100MB 2GB* 1

Application Monitoring Data Collector 500MB 2GB 1

Infrastructure Data Collector 300MB 2GB* 1

Web Service Data Collector 100MB 256MB 1

Report Server 2.5GB 2GB

Trading Networks

Console 25MB 128MB (256MB)

Server 50MB 1

*4GB on 64-bit systems. 1GB in development environments.





Addi tional Hardware Requirements

This section describes additional requirements you must consider when determiningactual hardware requirements for the indicated products.

Product Additional Requirements

ActiveTransferServer

ActiveTransfer Server needs additional hard drive space if you usethe hard drive as your virtual file system. The space requireddepends on the total size of documents ActiveTransfer Server needsto store, upload, and download. ActiveTransfer Server might needadditional hard drive space for log files.

webMethodsBroker

webMethods Broker might need additional hard drive space if yourdocuments are large, or if your clients use many guaranteeddocuments.

CommunicateServer

Communicate Server needs additional hard drive space for log files.The recommended amount is at least 5GB. More hard drive spacemight be needed if you use debug level or higher logging.

Deployer Deployer needs additional hard drive space for the deploymentprojects you create. When allocating space, allow for the number ofprojects to increase over time.

MobileDesigner

You will need additional hard drive space to accommodate the SDKsfor the mobile devices for which you want to develop applications.

OneData OneData needs additional hard drive space for temp, import, andexport files in the Software AG_directory\OneData\config directory.

Optimizeengines

Each engine needs 1GB virtual swap space and a disk subsystemwith 10GB available free space. In a production environment, thedisk 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 needs additionalhard drive space for log files. The recommended amount is 100MB;each engine needs 7MB of space for each log file.

Optimize WebService DataCollector

Each Web Service Data Collector needs 128MB of virtual swap space.In a production environment, each Web Service Data Collector needsadditional hard drive space for log files. The recommended amountis 75MB; each Web Service Data Collector needs 5MB of hard drive

space for each log file. More hard drive space might be needed if youuse debug level or higher logging.

TradingNetworks

To use large document handling, Trading Networks Server needsadditional hard disk drive space on which to temporarily savedocuments (instead of storing them in memory). For detailedinformation, see Managing B2B Integrations: webMethods TradingNetworks User’s Guide.





Available Disk Space in System Temp or Temporary Di rectory

The installer needs 100MB of available disk space in its system temp (Windows) ortemporary (UNIX) directory. If you are installing from an installation image, you need

enough additional disk space to accommodate the image; for example, if the image is200MB, the directory must have at least 300MB of available disk space. For the productslisted below, the directory must have the additional disk space.

Product LicensesYou must provide license files to install and, later, to start some webMethods products.Software AG sends these license files with your installation message. When you providethe license files during installation, the installer validates that:

The license file is the correct one for the product.

The license file has not been changed.

The license file has not expired.

The product is licensed on the operating system on which you are installing.

You will only be able to install a product if its license file passes these checks. Theproducts will repeat these checks at startup.

Product Available Disk Space

You are installing Designer Eclipse Additional 200MB

You are installing EntireX Additional 800MB

You are installing Report Server Additional 4GB




2 Installing and Uninstalling CentraSite

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Operating System, Browser, and JDK Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20


Shut Down SoftwareAG Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Prepare Your Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Install CentraSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Uninstall CentraSite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29





Shut Down Software AG Products

Shut down all non-Software AG applications that are running on the machine on whichyou are going to install.

Important! If you do not shut down these applications, product files might becomecorrupted.

If you are installing new Software AG products into an existing Software AG productinstallation directory, shut down existing products in that directory that are running. Fora UNIX system, use the instructions in the product documentation. For a Windowssystem, use the instructions below.

Note: If you do not shut down these products, the installer will not be able to update keyfiles that are locked by the operating system.

Prepare Your Machine

Software AG strongly recommends that you create installation images of yourwebMethods products and store them on your internal network. Create an image foreach operating system on which you plan to install that is covered by your licenseagreement. Storing images enables you to ensure consistency across installations overtime; the installer provides only the latest product releases, while installation images

If a product is

runni ng as ... You can typical ly shut down f rom the...

Application Windows Start menu. Products are listed as Software AG > Stop

Servers > product .

For EntireX, also shut down the non-default Broker, RPC Servers,and customer applications that use EntireX shared libraries usinginstructions in the product documentation.

Exit Designer using the File menu.

Service Windows Services window. Services are listed as Software AG product release.

For CentraSite, stopping the CentraSite Apache service stops theApplication Server Tier. Stop the Registry Repository service usinginstructions in the product documentation after stopping allApplication Server Tiers.

For webMethods Broker, stopping the Broker Monitor service alsostops Broker Servers.





contain the product releases you download into them. In addition, installing fromimages helps you reduce WAN traffic and improve installation speeds. Forinstructions on creating an installation image, see Using the Software AG Installer.

If the vendor for your operating system recommends installing the latest service

packs, patch-bundles, and fixes, Software AG encourages you to follow thatrecommendation. If you experience problems with installed service packs, patch- bundles, or fixes, report those problems directly to the vendor.

If you are going to install on a UNIX NFS file system, the Basic Authentication featurewill only work if you mount the NFS file system with the suid option, which allowsset-user-identifier or set-group-identifier bits to take effect.

If you are going to install on a UNIX system:

a Make sure your system is using the DES, MD5 or Blowfish algorithm to encryptthe password of the user that you are going to use to install.

b Make sure you have set sufficient user limits for the shell you use to start theinstallation and the product daemons. For example, the daemons for theCentraSite database and infrastructure will run out of memory if they are startedfrom the shell with a low user limit for data. If your system policy allows it,Software AG recommends setting the value for coredump, data, file, memory, andthreads to unlimited, and the value of nofiles to 8192. For more information aboutsetting and displaying the ulimits, read the man page or ask your systemadministrator.

c Set the shmmax parameter to the memory (RAM) that is physically available onyour machine. Otherwise you might have problems during CentraSite startup.

If you are going to install on a Linux system, the library libcrypt.so must be present to

support the webMethods security infrastructure, or the login using OS usernames/authentication will not work. If you do not see the libcrypt.so file in the/usr/lib64 directory for Linux x86_64, or /usr/lib for Linux x86, install the rpmpackage glibc-devel.

If you are going to install on a Linux x86_64 system, install the rpm package compat-libstdc++ from your operating system distribution using the vendor instructions.

If you are going to install on a SUSE Linux Enterprise Server 11 SP1 system, and youhave configured the system to use the Blowfish algorithm to encrypt user passwords,download and install patch 18 Aug 2011 - glibc 4944 from Novell Support. This patchfixes an operating system bug relating to user authentication. For detailedinformation, see Novell’s SUSE Security Announcement: SUSE-SA:2011:035.





Install CentraSite

Start the Installer, Provide General Information, and Choose

CentraSite

Follow the instructions in the guide Using the Software AG Installer to start the installer inGUI or console mode, and to provide general information such as proxy server, release toinstall, and installation directory. That guide also provides information about how to usethe product and language pack selection trees.

On the product selection tree, choose the CentraSite components to install. You can installthe CentraSite Registry Repository and Application Server Tier in the same directory onthe same machine or on separate machines. If you install the components on separatemachines, or in the same directory on the same machine but at different times, you mustinstall the Registry Repository first, and it must be running when you install theApplication Server Tier.

Note: You cannot install multiple instances of the CentraSite 8.2 Application Server Tier orRegistry Repository on the same machine.

After the selection trees, the installer asks for product configuration information. Go to“Supply Product Configuration Information in GUI Mode” on page 23 or “SupplyProduct Configuration Information in Console Mode” on page 28 as appropriate for theinstaller mode you are using.

Supply Product Configuration Information in GUI ModeSystem Management Hub

This product is managed by System Management Hub, so the installer displays the panel below.





The actions you can take depend on the contents of your machine.

In this case... You can...

No instances of SystemManagement Hub exist on themachine

Customize port values, calculate port values froma specified base port, or use the legacy portvalues that were used by System Management

Hub in earlier releases.An earlier release of SystemManagement Hub exists on themachine

Customize port values or calculate port valuesfrom a specified base port.

One or more instances of SystemManagement Hub exist on themachine

Calculate port values from a specified base port.





Sudo

When you install on a UNIX system, the panel below might appear.

Note: If you are creating an installation script or if you are installing using an installationscript, you will not be able to use sudo in the installer because the installer does not storethe sudo password, for security reasons. After you install from the installation script, youcan run the script named in the panel, as explained later in this chapter.

Integrated Authentication Framework

If you selected Integrated Authentication Framework for installation, you will see thepanel below.





Field Entry

Administ rat ion

port

Specify the administration port to use to start up and shut down theIntegrated Authentication Framework from System ManagementHub. If you install multiple instances of the Integrated AuthenticationFramework on the same machine, the port for each instance must beunique.

SSL

communication

port

Specify the SSL port to use for communication between the IntegratedAuthentication Framework and other products. If you install multipleinstances of the Integrated Authentication Framework on the samemachine, the port for each instance must be unique.





CentraSite

Go to “Complete the Installation” on page 29.

Field Entry

Ac tiveSOA license file

portsIf you licensed CentraSite ActiveSOA, specify the full path to thelicense file.

Appl ication ServerTier ports

Defaults are for the bundled Apache HTTP server and Tomcat.See Appendix B, “Default Ports” for information about ports.

Remote Registry

Repository fieldsRequired when installing the Application Server Tier if theRegistry Repository is on separate machine. Do not use"localhost." See Appendix B, “Default Ports” for informationabout ports.





Supply Product Configuration Information in Console Mode

System Management Hub

This product is managed by System Management Hub, so the installer prompts forSystem Management Hub port values. The actions you can take depend on the contentsof your machine.

Sudo

The installer might ask whether to use sudo, in which case it will register daemons andset file permissions for this product, or to not use sudo, in which case you might have tomanually perform these tasks after installation as explained later in this chapter.



If you selected Integrated Authentication Framework for installation, you will beprompted for the information below.

1 Specify the administration port to use to start up and shut down the IntegratedAuthentication Framework from System Management Hub. If you install multipleinstances of the Integrated Authentication Framework on the same machine, the portfor each instance must be unique

2 Specify the SSL port to use for communication between the Integrated AuthenticationFramework and other products. If you install multiple instances of the IntegratedAuthentication Framework on the same machine, the port for each instance must beunique.



Customize port values, calculate port values froma specified base port, or use the legacy portvalues that were used by System ManagementHub in earlier releases.

An earlier release of SystemManagement Hub exists on the

machine








CentraSite

1 If you licensed CentraSite ActiveSOA, specify the full path to the license file.

2 If you are installing the Registry Repository, you can specify the application and

administration ports to use. See Appendix B, “Default Ports” for information aboutports.

3 If you are installing the Application Server Tier, provide the following:

Ports to use for the HTTP and Web applications servers; defaults shown are forthe bundled Apache HTTP and Tomcat servers.

If the Registry Repository is installed on a different machine, identify the RegistryRepository host and port. Do not use "localhost."

Complete the Installation

If you installed CentraSite on a UNIX system and did not use sudo, the installer was notable to register daemons and set file permissions for the CentraSite Registry RepositoryExtension, Tomcat Server, or System Management Hub.

You can perform these tasks now by running the scriptSoftware AG_directory/bin/afterInstallAsRoot.sh as the root user. If you do not want to runthis script, your CentraSite installation will have these limitations:

You will not be able to use the Operating System authentication method.

You will have to manually start the CentraSite Registry Repository Extension, TomcatServer, and System Management Hub each time you start your system.

Uninstall CentraSite

Important! If you are going to uninstall CentraSite, and the CentraSite Registry Repositoryis on a different machine than the Application Server Tier, uninstall the ApplicationServer Tier first, and then uninstall the Registry Repository.

1 If products in the directory from which you are going to uninstall are running, shutdown those products. For a UNIX system, use the instructions in the productdocumentation. For a Windows system, use the instructions below.

Note: If you do not shut down these products, the uninstaller will not be able toremove key files that are locked by the operating system.





2 If you are uninstalling all products in the installation directory, and you want to keepfiles you have stored in the Software AG_directory/install directory, move the files to anon-Software AG directory. The uninstaller will delete all files from theSoftware AG_directory/install directory except the logs and the installer-maintainedhistory.txt file.

3 If you are going to uninstall CentraSite from a UNIX system, and you used sudo toregister daemons and set file permissions during or after installation, you will alsohave to use sudo to unregister daemons and remove file permission. You can have theuninstaller take this action in the next step, or you can take this action now byrunning the script Software AG_directory/bin/beforeUninstallAsRoot.sh as the rootuser.

Note: If you are uninstalling using an uninstallation script, you will not be able to usesudo in the uninstaller because the uninstaller does not store the sudo password, forsecurity reasons.

4 Run the Software AG Uninstaller as instructed in Using the Software AG Installer. Ifyou choose to uninstall both CentraSite and EntireX, also choose to uninstall SystemManagement Hub.

5 After uninstallation is complete, Software AG recommends rebooting your system.

6 The Software AG Uninstaller does not delete files that were created after you installedyour products (for example, user-created or configuration files), nor does it delete thedirectory structure that contains the files. If you are going to reinstall into the samedirectory, delete the product directories after uninstallation is complete or, if youwant to save the files, move them.

If a product is

runni ng as ... You can typi cally shut down f rom the...

Application Windows Start menu. Products are listed as Start > Programs >

Software AG > Stop Servers > product .For EntireX, also shut down the non-default Broker, RPCServers, and customer applications that use EntireX sharedlibraries using instructions in the product documentation.



For webMethods Broker, stopping the Broker Monitor servicealso stops Broker Servers.




3 Installing and Uninstalling ApplinX

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Typical Development Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32





Install ApplinX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Uninstall ApplinX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37





Overview

This chapter provides product-specific preparation, installation, and uninstallationinstructions. These instructions are intended for use with Using the Software AG Installer.

That guide explains how to prepare your machine to use the Software AG Installer, andhow to use the Software AG Installer to install and uninstall your products. It describesthe various methods you can use to install and uninstall, such as using the installerwizard, the installer console mode, an installation script, or an installation image. It liststhe JDK to use to run the installer, and explains installation and uninstallation logging.

Important! Do not install products from webMethods product suite 8.2 into a directory thatcontains products from any other release.

Typical Development Installation

ApplinX Server, Administration, JSP and .NET Frameworks, and Visual Studio Add-in

Designer Eclipse with ApplinX, SOA Governance CentraSite, andWeb Services Stackplug-ins

Note: In a collaborative development environment, CentraSite Registry Repository would be installed on a shared machine and accessed by development users.

Operating System, Browser, and JDK Support For information on operating system and browser support for ApplinX, see thewebMethods System Requirements. For information on JDK support, see “JDK Support” onpage 15.


The table below lists the minimum and recommended hardware requirements forApplinX. Recommended amounts are shown in parentheses.

Important! The hardware requirements below are for ApplinX only. They do not include500MB of hard drive space for Software AG infrastructure shared libraries required bymost products and installed once per installation directory. You must determine theoverall hardware requirements for each of your machines based on the overallrequirements of your operating system and software.





For additional hardware requirements, see the ApplinX documentation.






Appl inX Component Hard Drive Space RAM CPUs

Server 100MB 80MB+300KB per user 2 (4)

Administration 75MB 40MB

JSP Framework 50MB 2GB

C#.NET Framework 55MB 2GB

VB.NET Framework 30MB 2GB

Visual Studio Add-In 1MB 2GB

If a product is



Servers > product .








Software AG strongly recommends that you create installation images of yourwebMethods products and store them on your internal network. Create an image foreach operating system on which you plan to install that is covered by your licenseagreement. Storing images enables you to ensure consistency across installations overtime; the installer provides only the latest product releases, while installation imagescontain the product releases you download into them. In addition, installing fromimages helps you reduce WAN traffic and improve installation speeds. Forinstructions on creating an installation image, see Using the Software AG Installer.

If the vendor for your operating system recommends installing the latest servicepacks, patch-bundles, and fixes, Software AG encourages you to follow thatrecommendation. If you experience problems with installed service packs, patch-

bundles, or fixes, report those problems directly to the vendor. If you are going to install on a Windows system, and you want to develop .NET

ApplinX Web applications in Visual Basic or C#, install Microsoft Visual Studio 2005,or install Microsoft Visual Studio 2008 or 2010 and the Microsoft Visual J# .NET 2.0Redistributable Package. Microsoft Visual Studio does not have to be running whenyou install ApplinX.

Important! If you do not install Microsoft Visual Studio, you will not be able to installthe ApplinX Visual Studio Add-in component, and the ApplinX .NET Frameworkcomponent will have limited functionality; you will not be able to develop compositeWeb applications.

If you are going to install on a UNIX system, make sure you have set sufficient userlimits for the shell you use to start the installation and the product daemons. Forexample, the daemons for the Tomcat Server will run out of memory if they arestarted from the shell with a low user limit for data. If your system policy allows it,Software AG recommends setting the value for coredump, data, file, memory, and




If a product is

runn ing as ... You can typi call y shut down fr om the...





threads to unlimited, and the value of nofiles to 8192. For more information aboutsetting and displaying the ulimits, read the man page or ask your systemadministrator.

If you are going to install on a Linux x86_64 system, install the rpm package compat-

libstdc++ from your operating system distribution using the vendor instructions.

Install Appl inX

Start the Installer, Provide General Information, and Choose ApplinX

Follow the instructions in the guide Using the Software AG Installer to start the installer inGUI or console mode, and to provide general information such as proxy server, release toinstall, and installation directory. That guide also provides information about the product

and language pack selection trees.On the product selection tree, choose the ApplinX components to install.

After the selection trees, the installer asks for product configuration information. Go to“Supply Product Configuration Information in GUI Mode” on page 35 or to “SupplyProduct Configuration Information in Console Mode” on page 37 as appropriate for theinstaller mode you are using.

Supply Product Configuration Information in GUI Mode

Appl inX

If you are installing the ApplinX Server, the installer displays the panel below.






Field Entry

License file Specify the full path to the ApplinX license file.

component ports If you install multiple ApplinX Server instances on the samemachine, use unique ports for each instance. See Appendix B,“Default Ports” for information about ports.

Migrate data Use for pre-8.1 release upgrades only; see the ApplinX upgradedocumentation.






Appl inX

If you are installing the ApplinX Server, do the following:1 Specify the full path to your ApplinX license file.

2 You can specify the ports to use for ApplinX Server. If you install multiple instances ofApplinX Server on the same machine, specify unique ports for each instance. Forinformation about ApplinX ports, see Appendix B, “Default Ports”.

Important! Use the migration prompt for pre-8.1 release upgrades only; see the ApplinXupgrade documentation.

Complete the InstallationAfter the installer finishes, if you installed on a UNIX system, source the Software AGenvironment file apxenv to set the environment variable APPLINX_ROOT, or set thevariable permanently by copying the setting from the apxenv file into your profile. Theapxenv file is located in the Software AG_directory/ApplinX installation directory.

Uninstall ApplinX

1 If products in the directory from which you are going to uninstall are running, shutdown those products. For a UNIX system, use the instructions in the product

documentation. For a Windows system, use the instructions below.


If a product is

runn ing as ... You can typi cally shut down f rom the...


Software AG > Stop Servers > product .

For EntireX, also shut down the non-default Broker, RPC

Servers, and customer applications that use EntireX sharedlibraries using instructions in the product documentation.







4 Installing and Uninstalling EntireX

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Typical Development Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40





Install EntireX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Uninstall EntireX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53





Overview




Typical Development Installation

EntireX Core Files, Broker, Administration, and Web Services Runtime

Designer Eclipse with EntireX and SOA Governance CentraSite plug-ins

Note: In a collaborative development environment, CentraSite Registry Repository would be installed on a shared machine and accessed by development users.

Operating System, Browser, and JDK Support

For information on operating system and browser support for EntireX, see thewebMethods System Requirements. For information on JDK support, see “JDK Support” onpage 15.


The table below lists the minimum and recommended hardware requirements forEntireX. Recommended amounts are shown in parentheses.

Important! The hardware requirements below are for EntireX only. They do not include500MB of hard drive space for Software AG infrastructure shared libraries required by

most products and installed once per installation directory. You must determine theoverall hardware requirements for each of your machines based on the overallrequirements of your operating system and software.

EntireX Component

Hard Drive Space

Windows

Hard Drive

Space UNIX RAM CPUs

Core Files 220MB 280MB 2GB 1





The installer needs 100MB of available disk space in its system temp (Windows) ortemporary (UNIX) directory. If you are installing from an installation image, you needenough additional disk space to accommodate the image; for example, if the image is

200MB, the directory must have at least 300MB of available disk space. For EntireX, thedirectory must have an additional 800MB of available disk space.






Administration* 140MB 170MB 1GB 1

Broker 20MB 30MBWeb Services Runtime** 140MB 150MB 1GB 1

*Includes 120MB hard drive space, 1GB RAM, and 1 CPU for the required andautomatically installed System Management Hub.

**Includes 120MB hard drive space, 1GB RAM, and 1 CPU for the required andautomatically installed Web Services Stack.

If a product is


Application Windows Start menu. Products are listed as Software AG > StopServers > product .



EntireX Component

Hard Drive Space

Windows

Hard Drive

Space UNIX RAM CPUs






Software AG strongly recommends that you create installation images of yourwebMethods products and store them on your internal network. Create an image foreach operating system on which you plan to install that is covered by your licenseagreement. Storing images enables you to ensure consistency across installations overtime; the installer provides only the latest product releases, while installation imagescontain the product releases you download into them. In addition, installing fromimages helps you reduce WAN traffic and improve installation speeds. Forinstructions on creating an installation image, see Using the Software AG Installer.

If the vendor for your operating system recommends installing the latest servicepacks, patch-bundles, and fixes, Software AG encourages you to follow thatrecommendation. If you experience problems with installed service packs, patch-

bundles, or fixes, report those problems directly to the vendor. If you are going to install on a UNIX system, make sure you have set sufficient user

limits for the shell you use to start the installation and the product daemons. Forexample, the daemons for System Management Hub will run out of memory if theyare started from the shell with a low user limit for data. If your system policy allowsit, Software AG recommends setting the value for coredump, data, file, memory, andthreads to unlimited, and the value of nofiles to 8192. For more information aboutsetting and displaying the ulimits, read the man page or ask your systemadministrator.

If you are going to install the Administration component on a UNIX NFS file system,the Basic Authentication feature will only work if you mount the NFS file system with

the suid option, which allows set-user-identifier or set-group-identifier bits to takeeffect.

If you are going to install on a Linux system, the library libcrypt.so must be present tosupport the webMethods security infrastructure, or the login using OS usernames/authentication will not work. If you do not see the libcrypt.so file in the/usr/lib64 directory for Linux x86_64, or /usr/lib for Linux x86, install the rpmpackage glibc-devel.




If a product is







If you are going to install on a SUSE Linux Enterprise Server 11 SP1 system, and youhave configured the system to use the Blowfish algorithm to encrypt user passwords,

download and install patch 18 Aug 2011 - glibc 4944 from Novell Support. This patchfixes an operating system bug relating to user authentication. For detailedinformation, see Novell’s SUSE Security Announcement: SUSE-SA:2011:035.

Install EntireX

Start the Installer

Follow the instructions in the guide Using the Software AG Installer to start the installer in

GUI or console mode.

Choose Bit Mode on Windows System

By default, the installer installs the 32-bit version of EntireX on 32-bit systems and the 64- bit version on 64-bit systems. On Windows systems, you can choose to have the installerinstall the 32-bit version on a 64-bit system instead.

Important! If you do so, you can install only products listed on the tab below and theirsupporting components in this run of the installer. If you want to install any otherproduct, you must do so in a separate run of the installer. You cannot mix 32-bit and 64- bit versions of products in the same installation directory. After you choose a bit mode toinstall, you cannot later return to the tab and choose the other bit mode; if you want tochange bit modes, you must exit the installer and start again.

On the Welcome panel, click the JVM and Bit Mode tab.





Choose the bit mode to use and click OK.

Provide General Information and Choose EntireX

Follow the instructions in the guide Using the Software AG Installer to provide generalinformation such as proxy server, release to install, and installation directory. That guidealso provides information about the product and language pack selection trees.

On the product selection tree, select the EntireX components to install. If you selectEntireX, the installer automatically selects the Administration component, which in turnselects System Management Hub. The Administration component enables you toadminister the EntireXBroker, Broker Agent, Location Transparency, and AuthorizationRule, and to use the System Management Hub to administer the EntireX RPC server. Ifyou need only a lightweight EntireX installation (for example, for use with NaturalONE),you might not need the Administration component. Without this component, you willonly be able to start and stop the default EntireXBroker. For complete information onfunctionality provided by the Administration component, see "System ManagementHub" in the EntireX product documentation.





After the selection trees, the installer asks for product configuration information. Go to“Supply Product Configuration Information in GUI Mode” on page 45 or to “SupplyProduct Configuration Information in Console Mode” on page 51 as appropriate for theinstaller mode you are using.

Supply Product Configuration Information in GUI Mode


This product is managed by System Management Hub, so the installer displays the panel below.

The actions you can take depend on the contents of your machine.





Sudo



No instances of SystemManagement Hub exist on the

machine

Customize port values, calculate port values froma specified base port, or use the legacy port

values that were used by System ManagementHub in earlier releases.

An earlier release of SystemManagement Hub exists on themachine








EntireX

Field Entry

License file Specify the full path to the EntireX license file.

Note: If you are also installing NaturalONE, EntireX uses theNaturalONE license file.

Default Entir eX Broker

TCP/IP and SSL ports

When you install EntireX Broker, TCP/IP and SSL ports for theBroker. If you install multiple EntireX instances on the samemachine, use unique ports for each default Broker instance. SeeAppendix B, “Default Ports” for information about ports.






If you selected Integrated Authentication Framework for installation, you will see thepanel below.

Default EntireX Broker

Autostart

When you install EntireX Broker, tells the installer whether tostart the default Broker after installation and to turn on theAutostart option so the Broker will start automatically wheneveryou start your system.

System Management

Hub EntireX

administrator

When you install the EntireX Administration component,administrator name to use to connect to the SystemManagement Hub.

If you are installing on a Windows system and you want theadministrator to be a user from the Active Directory, you mustalso specify the domain. For instructions, see the EntireXdocumentation.

Administ rat ion TCP/IP

and SSL ports

When you install theEntireX Administration component, TCP/IPand SSL ports to use for administration.

Field Entry






Field Entry

Administ rat ion

port

Specify the administration port to use to start up and shut down theIntegrated Authentication Framework from System ManagementHub. If you install multiple instances of the Integrated AuthenticationFramework on the same machine, the port for each instance must beunique.

SSL

communication

port

Specify the SSL port to use for communication between the IntegratedAuthentication Framework and other products. If you install multipleinstances of the Integrated Authentication Framework on the samemachine, the port for each instance must be unique.







This product is managed by System Management Hub, so the installer prompts forSystem Management Hub port values. The actions you can take depend on the contentsof your machine.

Sudo



EntireX

1 If you are also installing NaturalONE, EntireX uses the NaturalONE license file. Ifyou are not also installing NaturalONE, specify the full path to your EntireX licensefile.

2 When you install EntireX Broker, do the following:

a Specify the EntireX Broker port. If you install multiple EntireX instances on thesame machine, use unique ports for each default Broker instance. See Appendix B,“Default Ports” for information about ports.

b Indicate whether the installer should start the default Broker after installationand turn on the Autostart option so the Broker will start automatically wheneveryou start your system.



Customize port values, calculate port values froma specified base port, or use the legacy portvalues that were used by System ManagementHub in earlier releases.

An earlier release of SystemManagement Hub exists on the

machine








c Specify the administration ports.

3 When you install EntireX Administration, specify the administrator name to use toconnect to the System Management Hub, and specify the administration ports.


If you selected Integrated Authentication Framework for installation, you will beprompted for the information below.

1 Specify the administration port to use to start up and shut down the IntegratedAuthentication Framework from System Management Hub. If you install multipleinstances of the Integrated Authentication Framework on the same machine, the portfor each instance must be unique

2 Specify the SSL port to use for communication between the Integrated AuthenticationFramework and other products. If you install multiple instances of the IntegratedAuthentication Framework on the same machine, the port for each instance must be

unique.


Set Envi ronment Variables

On UNIX systems, you must set the EXXDIR environment variable to theSoftware AG_directory/EntireX directory, and set the PATH and LD_LIBRARY_PATHenvironment variables to include that directory.

To do so, source the EntireX environment script exxenv.csh or exxenv, depending on the

shell you are using. The script is located in the Software AG_directory/EntireX/INSTALLdirectory.

Source the Software AG environment script sagenv.new using the .$SAG/sagenv shellcommand. The script is located in the installation directory that contains the sharedcomponents. By default, that directory is /opt/softwareag.

Register Daemons and Set File Permissions

If you installed EntireX on a UNIX system and did not use sudo, do the following:

1 Register daemons and set file permissions by running the scriptSoftware AG_directory/bin/afterInstallAsRoot.sh as the root user.

2 Restart the EntireX Broker Admin Service. To do so, run the command/etc/init.d/sagnetbsrv restart , where n matches the number in the sagnetbsrvscript in the Software AG_directory/EntireX/bin directory.





3 During installation, you might have told the installer to enable autostart so theEntireX Broker would start automatically whenever you start your system. However,since you did not use sudo to install, the installer could not actually enable autostart.If you want to enable autostart, see the section on setting the local EntireX Brokerautostart in the System Management Hub documentation for instructions.

Uninstall EntireX




3 If you are going to uninstall this product from a UNIX system, and you do not wantto use sudo to uninstall, you must unregister daemons and remove file permissions by running the script Software AG_directory/bin/beforeUninstallAsRoot.sh as the rootuser.

Note: If you are uninstalling using an uninstallation script, you will not be able to usesudo in the uninstaller because the uninstaller does not store the sudo password, forsecurity reasons.

If a product is




For EntireX, also shut down the non-default Broker, RPCServers, and customer applications that use EntireX sharedlibraries using instructions in the product documentation.


Service Windows Services window. Services are listed as Software AG

product release.





5 Installing and Uninstalling All Other webMethods

Products

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Typical Development Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56



Database Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Install Using the Installer GUI Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Install Using the Installer Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Create Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Connect Products to Each Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103



5 Installing and Uninstalling All Other webMethods Products


Overview




Typical Development Installations

This section discusses typical development installations that enable you to perform acertain task, as follows:

Application integration development

local service development

Composite applications development

Process design

Monitoring and reporting

processing development Deployment

The sections below list the webMethods products that make up each of these typicaldevelopment installations. The products and components are listed as they appear on theSoftware AG Installer. For detailed information on how the products in each typicaldevelopment installation work together, see Understanding the webMethods Product Suite.

The sections below also list the webMethods database components you must or can installfor each typical development installation. A database component is a grouping ofdatabase objects that can be used by one or more webMethods products.

To create production environments, work with your administrators, Software AG Global

Consulting Services, GEAR methodology, and best practices documentation.

Appl icat ion Integration Development Typical Installation

Designer Eclipse with Service Development and SOA Governance CentraSite plug-ins.

Integration Server with Trading Networks Server and Monitor





Broker

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

Database Component ConfiguratorBelow are additional options.

Below are the database components you must or can include for an integrationdevelopment installation. For descriptions and instructions, see Chapter 6, “Creating andDropping Database Components”.

ISCoreAudit

ISInternal

CrossReference

DocumentHistory

DistributedLocking

MywebMethodsServer

TradingNetworks

Local Service Development Typical Installation

Designer Eclipse with Business Process Development, Process Simulation, andCentraSite Integration plug-ins; Composite Applications UI Development, CentraSiteIntegration, My webMethods Server Support, My webMethods Server Legacy PortletDevelopment, and Task Development plug-ins; Service Development plug-in; andSOA Governance CentraSite plug-in

Designer Workstation Local Service Development plug-in

Integration Server with Monitor, Process Engine, and Task Client Support

My webMethods Server with Task Engine, and My webMethods user interfaces forIntegration Server and Monitor

Database Component Configurator

If you want to store Integration Server keys and certificates securely, also install theIntegration Server PKI Support package.

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

Store Integration Server and Trading Networkskeys and certificates securely

Integration Server PKI Supportpackage

Maintain Designer elements in Microsoft VisualSourceSafe, IBM Rational ClearCase, orCollabNet Inc. Subversion

Integration Server VSS, ClearCase,or Subversion Support





Below are the database components you must or can include for an integrationdevelopment installation. For descriptions and instructions, see Chapter 6, “Creating andDropping Database Components”.

ISCoreAudit

ISInternal

CrossReference

DocumentHistory

DistributedLocking

MywebMethodsServer

Composite Appl ications Development Typical Installation

Designer Eclipse with Composite Applications Development and My webMethodsServer Support plug-ins, and SOA Governance CentraSite plug-ins

My webMethods Server


Note: In a collaborative development environment, you would install CentraSite RegistryRepository on a machine that is accessible to all development users.

You must include the MywebMethodsServer database component in a compositeapplication development installation. For descriptions and instructions, see Chapter 6,“Creating and Dropping Database Components”.

If you want your composite applications to call services available through other products,add these products:

Designer Service Development and SOA Governance CentraSiteplug-ins

Blaze Advisor

Integration Server with Blaze Rule Service Support and Monitor

My webMethods user interface for Blaze, Integration Server, and Monitor

Also add these database components:

ISCoreAudit

ISInternal

DistributedLocking

Blaze





Process Design Typical Installation

Designer Eclipse with Business Process Development, Process Simulation, andCentraSite Integration plug-ins; Business Rules Development and CentraSite

Integration plug-ins; Composite Applications Task Development plug-in; ServiceDevelopment plug-in, and SOA Governance CentraSite plug-in

Blaze Advisor

Integration Server with Rules Engine, Blaze Rule Service Support, Communicate,Monitor, Process Engine, Task Client Support, and Optimize Support

My webMethods Server with Task Engine, and My webMethods user interfaces forBlaze, Business Rules, Integration Server, and Monitor


Note: In a collaborative development environment, you would install CentraSite Registry

Repository on a machine that is accessible to all development users.

Below are additional options.

Below are the database components you must or can include for a process designinstallation. For descriptions and instructions, see Chapter 6, “Creating and DroppingDatabase Components”.

ISCoreAudit

ISInternal

DistributedLocking

Blaze

BusinessRules

MywebMethodsServer

ProcessEngine

ProcessAudit

Monitoring and Reporting Typical Development Installation

Optimize Analytic Engine and Prediction Engine

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

Store Integration Server keys and certificatessecurely

Integration Server PKI Supportpackage

Maintain Designer elements in Microsoft VisualSourceSafe, IBM Rational ClearCase, orCollabNet Inc. Subversion

Integration Server VSS, ClearCase,or Subversion Support





Broker

Integration Server with Monitor and Optimize Support

To collect data about Software AG products, Infrastructure Data Collector

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

Report Server with Monitor, Optimize, and Optimize for B2B packages

My webMethods Server, and My webMethods user interfaces forOptimize (all),Central Configuration, webMethods Broker, Monitor, and Reports


Below are the database components you must or can include for a monitoring andreporting installation. For descriptions and instructions, see Chapter 6, “Creating andDropping Database Components”.

Analysis

CentralConfiguration

MywebMethodsServer Locking

ProcessTracker

ProcessAudit

Reporting

Staging

SuiteReporting

SuiteReporting-Common

Complex Event Processing Development

Designer Eclipse with Business Events Event Type Development and ContinuousQuery Development plug-ins

Broker

My webMethods Server with My webMethods user interface for Broker

Event Server

Event Type Store MashZone

Service-Oriented Architecture Typical Development Installation

CentraSite Registry Repository and Application Server Tier

Integration Server with Mediator





Below are the database components you must or can include for an SOA Governanceinstallation. For descriptions and instructions, see Chapter 6, “Creating and DroppingDatabase Components”.

ISCoreAudit

ISInternal

CrossReference

DistributeLocking

MediatorEvents

Deployment Typical Installation

Deployer for run-time deployment.

Deployer and Asset Build Environment for repository-based deployment.Deployer 8.2 is the product you use to deploy webMethods assets from one environmentto another. For example, you might want to deploy assets you have developed on serversin a development environment (that is, source servers) to servers in a test or productionenvironment (that is, target servers).

In run-time deployment, you connect to webMethods source servers and deploy assetsthat reside on the source servers to target Software AG servers. Deployer is a package youinstall on an Integration Server. If no firewall separates your source and targetenvironments, install Deployer and its host Integration Server on a machine that canaccess all source and target servers. If a firewall separates the environments, installDeployer 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 alltarget servers. You can deploy assets from any release of webMethods Broker, Designer,Integration Server, My webMethods Server, Optimize, and Trading Networks to targetservers of the same release.

In repository-based deployment, you do not have to connect to the source servers.Instead, you build assets from source servers on a repository, then connect to therepository and deploy the assets to target Software AG servers. Install the Asset BuildEnvironment on development machines as necessary. In repository-based deployment,you can deploy assets from any release of webMethods Broker, Designer, IntegrationServer, My webMethods Server, Optimize, Trading Networks, Event Server, and BusinessRules to target servers of the same release.








If you are installing new Software AG products into an existing Software AG product

installation directory, shut down existing products in that directory that are running. Fora UNIX system, use the instructions in the product documentation. For a Windowssystem, use the instructions below.



Software AG strongly recommends that you create installation images of yourwebMethods products and store them on your internal network. Create an image foreach operating system on which you plan to install that is covered by your licenseagreement. Storing images enables you to ensure consistency across installations over

time; the installer provides only the latest product releases, while installation imagescontain the product releases you download into them. In addition, installing fromimages helps you reduce WAN traffic and improve installation speeds. Forinstructions on creating an installation image, see Using the Software AG Installer.

If the vendor for your operating system recommends installing the latest servicepacks, patch-bundles, and fixes, Software AG encourages you to follow thatrecommendation. If you experience problems with installed service packs, patch- bundles, or fixes, report those problems directly to the vendor.

If a product is



Servers > product .For EntireX, also shut down the non-default Broker, RPC Servers,and customer applications that use EntireX shared libraries usinginstructions in the product documentation.



For CentraSite, stopping the CentraSite Apache service stops theApplication Server Tier. Stop the Registry Repository service usinginstructions in the product documentation after stopping all

Application Server Tiers.






If you are going to install on an HP-UX 11i v3 system, set the variableUSE_J2D_FONTCONFIG to no. In a Bourne or Bash shell, run the command export

USE_J2D_FONTCONFIG=no.

Prepare to Install webMethods Broker on a UNIX System

Information about webMethods Broker installations is stored in the webMethodsBroker installations.txt file in the /var/opt/webmethods directory. Make sure the userthat you are going to use to install has write permission to that directory.

Broker Monitor and Broker Server require certain minimum system and user limitson UNIX systems. Ask your system administrator to set the following values for eachprocess:

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, configure theoperating system kernel to run in 64-bit mode. You cannot run the 64-bit BrokerServer on an operating system kernel that is configured to run in 32-bit mode.

If you are going to install on a Linux system:

The library libcrypt.so must be present to support the webMethods security

infrastructure, or the login using OS user names/authentication will not work. Ifyou do not see the libcrypt.so file in the /usr/lib64 directory for Linux x86_64, orthe /usr/lib directory for Linux x86, install the rpm package glibc-devel.

Install the rpm package ksh (kornshell) from your operating system distributionusing the vendor instructions.


If you are going to configure Broker Server to create data files on an NFS-mountedpartition, mount the partition using the command below. The options on thecommand help protect data integrity.

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

Limit Value

Maximum threads 512

Maximum open files 8192

Core dump size unlimited

Option Description

hard By default, if the NFS server does not respond to requests from theBroker Server, the Broker Server tries a few times and then fails. Thehard option forces the Broker Server to keep retrying until the NFSserver responds. The Broker Server hangs during this period.





Suppose the partition you want to mount is on a machine named netappca, the datadirectory on the partition is wmbroker_data, and you want to mount the partition onthe 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

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

If you are going to install Broker Server on an NFS file system, the BasicAuthentication feature will only work if you mount the NFS file system with the suidoption, which allows set-user-identifier or set-group-identifier bits to take effect.

Prepare to Install Integration Server on UNIX, IBM i5/OS, and Mac

Systems

Integration Server's ability to handle traffic is constrained by the number of filedescriptors available to the Integration Server process. On most systems, 64 filedescriptors are available to each process by default. If you are going to install Integration

Server on a UNIX, IBM i5/OS, or Mac system, Software AG recommends that you askyour system administrator to increase the number of file descriptors available to theIntegration Server process to at least 1024.

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

Prepare to Install Mobile Designer If you are going to install Mobile Designer on a Windows system, install Apache ANT 1.7or higher using the instructions in the vendor documentation.

If you are going to install Mobile Designer on a Mac system, install Mac OS X SnowLeopard or Lion using the instructions in the vendor documentation.

Install an integrated development environment (IDE). Software AG recommends usingthe Eclipse provided with Software AG Designer on the Software AG Installer.

nointr Prevents users from shutting down the Broker Server while it waitsfor the NFS server to respond.

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

Option Description





Prepare to Install Optimize

If you are going to install the Optimize Analytic Engine on a UNIX system, make sureyou have set sufficient user limits for the shell you use to start the installation and the

product daemons. For example, the daemons for the Optimize infrastructure will run outof memory if they are started from the shell with a low user limit for data. If your systempolicy allows it, Software AG recommends setting the value for coredump, data, file,memory, and threads to at least 32768, and the value of nofiles to 8192. For moreinformation about setting and displaying the ulimits, read the man page or ask yoursystem administrator.

Prepare to Install Report Server

If you are going to install Report Server, apply all operating system patches listedhere for your operating system: https://www-304.ibm.com/support/docview.wss?uid=swg27019997

If you are going to install Report Server on a UNIX or IBM i5/OS system, do thefollowing:

Add the current working directory (that is, .) to your PATH environment variable(for example, PATH=.:/usr/bin).

On a 64-bit system, add the Software AG_directory/cognos/c10/bin64 directory tothe library path environment variable, as follows:

Database Connection Information

Some products require you to supply database connection information duringinstallation. Sample URL formats for that driver are shown in the product panels. Keep inthe mind the following:

Many products use the DataDirect Connect JDBC 4.2 driver. For information about

options supported by this driver, see DataDirect Connect for JDBC User's Guide andReference 4.2 in the Software AG_directory/_documentation directory or on the SoftwareAG Documentation Web site.

If you are using the installer GUI mode, for ease of use, the database connectionvalues you enter on one panel are reflected on the next as you go forward through theinstaller the first time.

System Library Path Environment Variable

Solaris or Linux LD_LIBRARY_PATH

AIX LIBPATH

HP-UX SHLIB_PATH

https://www-304.ibm.com/support/docview.wss?uid=swg27019997












Use the DataDirect Connect connection option MaxPooledStatements=35 on alldatabase URLs except those for Trading Networks. This connection option improvesperformance by caching prepared statements. (Trading Networks caches its preparedstatements using its own pooling mechanism).

If the database user and password do not yet exist, specify the database user andpassword you will create after installation. You can use one database user formultiple database components, or you can use a different database user for eachdatabase component.

For DB2, if the product will connect to a schema other than the default schema for thespecified database user, you must specify these connection options in the databaseURL, where AlternateID is the name of the default schema that is used to qualifyunqualified database objects in dynamically prepared SQL statements:

;AlternateId=schema;”InitializationString=(SET CURRENT

PATH=current_path,schema)”;MaxPooledStatements=35

Install Using the Installer GUI Mode

Start the Installer, Prov ide General Information, and Choose the

Products to Install

Follow the instructions in the guide Using the Software AG Installer to start the installerand provide general information such as proxy server, release to install, and installationdirectory. That guide also provides information about the product and language packselection trees.

On the product selection tree, choose the products to install.

After the selection trees, the installer displays panels that ask for product configurationinformation. The sections below describe these panels. The panels are listed in productalphabetical order.

Supply Product Configuration Information

Sudo






Acti veTransfer Server

Field Entry

Run as

Server o r

Gateway

You can install ActiveTransfer Server to run as a server or as a reverseproxy server (Gateway).

License file If you chose to run ActiveTransfer Server as a server, specify the full pathto the license file that permits that functionality. If you chose to runActiveTransfer Server as a Gateway, specify the full path to the licensefile that permits that functionality.





webMethods Broker

When you install webMethods Broker, you install the following:

A default Broker. Brokers execute client messaging requests.

Database

Connection

If you are running ActiveTransfer Server as a server, specify theconnection ActiveTransfer Server is to use to connect to theActiveTransfer database component. If you do not do so, ActiveTransferServer will not start after installation.

Field Entry





A Broker Server. Broker Servers host Brokers; they receive client requests, send themto a Broker, and return responses to clients. They also manage memory and diskresources for the Brokers they host.

A Broker Monitor. Broker Monitors continually check the state of Broker Servers and

automatically restarts them if they stop running.

Field Entry

Broker Monitor

Port

If you install multiple Broker Monitor instances on the samemachine, use a unique port for each instance.

Create a Broker

Server

Configuration

Every Broker Server has it own data directory, which holds theBrokerServer's configuration file and log files, and storage session, whichstores metadata and run-time data.

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 combinedstorage session for configuration and run-time data. If you do notneed to back up configuration data without shutting down yourBroker Server, using a combined session might save you a smallamount of disk space. If you choose to not create the Broker Serverconfiguration at this time, you must create it after installation iscomplete, using instructions in Administering webMethods Broker.

You would create the Broker Server configuration at this time (that is,using the installer) if you want to use a storage size that is offered onthe panel and you want to create separate storage sessions forconfiguration (metadata) and run-time data. Using separate storage

sessions minimizes the risk of corruption that goes with a combinedstorage location and enables you to back up configuration datawithout having to shut down your Broker Server. (For informationabout the webMethods Broker online configuration data backup tool,see Administering webMethods Broker.)

Software AG recommends creating separate sessions. You cannotlater change from a combined session to separate sessions or viceversa.

To create the Broker Server configuration, select the check box andcomplete the fields below.

Field Entry

License file Specify the full path.

Broker Server

port

Broker Server uses this port for non-SSL and the previous two portsfor SSL. If you install multiple Broker Server instances on the samemachine, use unique ports for each instance.





When determining the appropriate size for the log file, the factors to balance are BrokerServer 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 (thatis, one larger-sized single document or a batch of documents). If necessary, you canremove 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 capacitymerely prevents the Broker Server from running out of room. After installation, if theamount of storage allocated turns out to be insufficient, you can add storage files andincrease their size. You cannot remove storage files or decrease their size. AdministeringwebMethods Broker provides complete information on Broker Server storage sessions andinstructions on working with log files and storage files.

Data dir ectory Full path to the directory for Broker Server data. If you installmultiple Broker Server instances on the same machine, use adifferent data directory for each instance.

Storage size Select a pre-configured storage session for the Broker Server that canhandle your expected usage needs.

Small (32MB log file, 512MB storage file). Ideal for runningdevelopment Broker Servers or small number of productionintegrations, low document volumes, and no document logging.Fastest Broker Server startup time.

Medium (64MB log file, 4GB storage file). Standard deploymentsize, fits more cases than Small; larger maximum transaction sizeand twice the storage capacity of Small. Broker Server startuptime two times longer than Small.

Large (128MB log file, 8GB storage file). Suitable for productiondeployments with many integrations running at high documentvolumes, possibly using document logging as well. Broker Serverstartup time two times longer than Medium , four times longer thanSmall.

Field Entry





Content Service Platform

Field Entry

Port Content Service Platform will use the port specified in this field and thesubsequent nine ports. If you install multiple Content Service Platforminstances on the same machine, use a unique set of ports for each

instance.Database

Connection

Content Service Platform uses a database to store document metadata,configuration data, and document-specific security settings. You mustspecify the connection Content Service Platform is to use to connect to itsdatabase. If you do not do so, Content Service Platform will not startafter installation.





Event Server

Field Entry


Port You can specify a port to use to remotely administer Event Server. If youinstall multiple Event Server instances on the same machine, use a

unique port for each instance.





Integration Server





Field Entry

License file If you are installing a production Integration Server, specify the full pathto the Integration Server production license file.

If you are installing Integration Server as part of Designer Workstation,specify the full path to the Integration Server development license file.

If you are installing Mediator and have not licensed Integration Server,specify the full path to the Mediator license file.

Important! The Mediator license does not allow full Integration Serverfunctionality. Do not install other products on this Integration Serverlater or those products might not work properly.

Port If you install multiple Integration Server instances on the same machine,use a unique port for each instance.

Install as If you are installing on a Windows system and will be using a versioncontrol system with Developer, you must install Integration Server as anapplication rather than a service.

Database

Connection

Available when you select External RDMBS. You must decide where tostore data written by Integration Server. For complete information, see“Data Storage” on page 107. You must specify the connection IntegrationServer is to use to connect to its database components or IntegrationServer will use its embedded database instead.





Field Entry

Database

Connection

If you are installing My webMethods Server for the sole purpose ofrunning the Messaging user interface in My webMethods, you can

configure My webMethods Server to use an embedded database insteadof an external RDBMS. To do so, leave the database connection fields onthe panel blank. After installation is complete, see AdministeringwebMethods Broker for instructions on configuring the embeddeddatabase.

If you are installing My webMethods Server for any other purpose, youmust use an external RDBMS. You must specify the connection MywebMethods Server is to use to connect to the MywebMethodsServerdatabase component. If you do not do so, My webMethods Server will notstart after installation.





OneData

Field Entry


Port If you install multiple OneData instances on the same machine, use aunique port for each instance.

Repository

ID

OneData provides a repository in which to store your master data.Provide an ID for the repository (for example, DevRepo). The ID will beused internally in OneData

Repository

name

Provide a name for the repository (for example, OneData DevelopmentRepository). The name will appear in the OneData user interface.





Database

Connection

You must specify the connection OneData is to use to connect to theOneData database components. If you do not do so, OneData will notstart after installation.

The URL you specify must include the option catalogOptions=1 so thatOneDatacan retrieve database metadata information for variousoperations (for example, jdbc:wm:oracle://localhost:1521;serviceName=XE;catalogOptions=1).

The prefix you specify will be added to each of the three schemaconnection names (that is, prefix_md, prefix_wa, and prefix_ra). Provide adifferent database user and password for each of the three schemas.

Field Entry





Optimize

Field Entry

Host or IP

address

If you have multiple network interfaces, identify the one to use; thedefault is the default network interface for local machine. Do not use"localhost."

component

port

Enabled if you chose them on the product selection tree.

Optimize provides a Central Configuration user interface that allows youto configure Optimize components from a central machine. Specify theport you want the interface to use to communicate with each Optimizecomponent you are installing. If you install multiple instances of acomponent on the same machine, the port for each instance must beunique.





Optimize Application Monitor ing Data Collector

Field Entry

Broker URL URL for the Broker to use to route KPI readings from data collectors toOptimize. Change localhost to the correct host, the port to the correctport, and Broker #1 to the correct Broker instance name.

Important! Do not change the /analysis part of the URL.

Port Data collector port to which products should send monitoring data.

Administ rat i

on port

Port to use to start and stop the data collector.





Optimize Infrastructure Data Collector

Field Entry

Configuration

port

Optimize provides a Central Configuration user interface that allowsyou to configure Optimize components from a central machine. Specifythe port you want the interface to use to communicate with theInfrastructure Data Collector. The port must be unique. If you installmultiple instances of the Infrastructure Data Collector on the samemachine, the port for each instance must be unique.





Report Server

Field Entry

Host or IP

address

If you have multiple network interfaces, identify the one to use; thedefault is the default network interface for local machine. Do not use"localhost."





Rules Engine

Database

Connection

The Report Server uses a Content Store. The Content Store is an externalRDBMS containing data that the Report Server needs to operate, such asglobal configuration data and report definitions. You must specify thedatabase connection between the Report Server and its Content Store. Ifyou do not do so, the Report Server will not start after installation.

The database connection fields vary slightly by RDBMS. If the service(Oracle) or database (SQL Server or DB2) does not yet exist, specify theservice or database you will create after installation. For moreinformation on the Content Store, see Generating webMethods Reports.

Field Entry





Trading Networks Server

Field Entry


Field Entry

Database

Connection

Specify the connection Trading Networks Server is to use to connect tothe TradingNetworks database component. If you do not do so, TradingNetworks Server will not start after installation.





Install Using the Installer Console Mode

Start the Installer, Prov ide General Information, and Choose the

Products to Install

Follow the instructions in the guide Using the Software AG Installer to start the installerand provide general information such as proxy server, release to install, and installationdirectory. That guide also provides information about the product and language packselection trees.

On the product selection tree, choose the products to install.

After the selection trees, the installer displays prompts that ask for product configurationinformation. The sections below describe these prompts. The panels are listed in productalphabetical order.

Sudo



Supply Product Configuration Information

Acti veTransfer Server

1 You can install ActiveTransfer Server to run as a server or as a reverse proxy server(Gateway).

2 If you chose to run ActiveTransfer Server as a server, specify the full path to thelicense file that permits that functionality. If you chose to run ActiveTransfer Server asa Gateway, specify the full path to the license file that permits that functionality.

3 If you are running ActiveTransfer Server as a server, specify the connectionActiveTransfer Server is to use to connect to the ActiveTransfer database component.If you do not do so, ActiveTransfer Server will not start after installation.





webMethods Broker

1 You can specify the port to use for Broker Monitor. If you install multiple BrokerMonitors on this machine, specify a different port for each.

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

3 Every Broker Server has it own data directory, which holds theBroker Server'sconfiguration file and log files, and storage session, which stores metadata and run-time data. Indicate whether you want to create the Broker Server.

You would not create the Broker Server configuration at this time (that is, usingthe installer) if you want to use a different storage size than is offered on the panelor if you want to create a combined storage session for configuration and run-timedata. If you do not need to back up configuration data without shutting downyour Broker Server, using a combined session might save you a small amount ofdisk space. If you choose to not create the Broker Server configuration at this time,

you must create it after installation is complete, using instructions in Administering webMethods Broker.

You would create the Broker Server at this time (that is, using the installer) if youwant to use a storage size that is offered on the panel and separate storagesessions for configuration (metadata) and run-time data. Using separate storagesessions minimizes the greater risk of corruption that goes with a combinedstorage location, and enables you to back up configuration data without having toshut down your Broker Server. (For information about the webMethods Brokeronline configuration data backup tool, see Administering webMethods Broker.) Ifyou choose to create the Broker Server at this time, follow the steps below.

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

1 Enter the full path to your webMethods Broker license file.

2 Identify the port on which to run the Broker Server; Broker Server uses thisport for non-SSL and the previous two ports for SSL. The default (non-SSL)port is 6849 (and, for SSL, 6848 and 6847). If you install multiple instances ofBroker Server on the same machine, specify unique ports for each instance.

3 Provide the full path to the data directory in which to store Broker Serverdata. If you install multiple instances of Broker Server on the same machine,specify a unique data directory for each instance.

4 Select a pre-configured storage session for the Broker Server that can handle yourexpected usage needs, as follows:

Small (32MB log file, 512MB storage file). Ideal for running development BrokerServers or small number of production integrations, low document volumes, andno document logging. Fastest Broker Server startup time.





Medium (64MB log file, 4GB storage file). Standard deployment size, fits morecases than Small; larger maximum transaction size and twice the storage capacityof Small. Broker Server startup time two times longer than Small.

Large (128MB log file, 8GB storage file). Suitable for production deployments with

many integrations running at high document volumes, possibly using documentlogging as well. Broker Server startup time two times longer than Medium , fourtimes longer than Small.

When determining the appropriate size for the log file, the factors to balance areBroker Server startup time and the desired maximum transaction size. Thesmaller the log file, the faster the startup; however, with a larger log file, you cansend larger messages (that is, one larger-sized single document or a batch ofdocuments). 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 thesize of the storage file; additional storage capacity merely prevents the BrokerServer 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 theirsize. You cannot remove storage files or decrease their size. AdministeringwebMethods Broker provides complete information on Broker Server storagesessions and instructions on working with log files and storage files.

Content Service Platform

1 You can specify the port to use for Content Service Platform. Content Service Platformwill use this port and the subsequent nine ports. If you install multiple ContentService Platform instances on the same machine, use a unique set of ports for eachinstance.

2 Content Service Platform uses a database to store document metadata, configurationdata, and document-specific security settings. You must specify the connectionContent Service Platform is to use to connect to its database. If you do not do so,Content Service Platform will not start after installation.

Event Server

1 Specify the full path to your Event Server license file.

2 You can specify a port to use to remotely administer Event Server. If you installmultiple instances of Event Server on the same machine, specify a unique port foreach instance.





Integration Server

1 If you are installing a production Integration Server, specify the full path to theIntegration Server production license file. If you are installing Integration Server aspart of , specify the full path to the Integration Server development license file. If youare installing Mediator and have not licensed Integration Server, specify the full pathto the Mediator license file.

2 You can specify the port to use for Integration Server. If you install multiple instancesof Integration Server on the same machine, specify unique ports for each instance.

3 You must decide where to store data written by Integration Server (see “DataStorage” on page 107).

Note: If you select the external RDBMS but do not provide the connection information,Integration Server will use the embedded database.


1 You can specify the port to use for My webMethods Server.

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

Note: If you are installing My webMethods Server for the sole purpose of running theMessaging user interface in My webMethods, you can configure My webMethodsServer to use an embedded database instead of an external RDBMS. To do so, do notspecify the database connection fields. After installation is complete, see

Administering webMethods Broker for instructions on configuring the embeddeddatabase. If you are installing My webMethods Server for any other purpose, youmust use an external RDBMS.

OneData

1 Specify the full path to your OneData license file.

2 You can specify the port to use for OneData. If you install multiple instances ofOneData on the same machine, specify unique ports for each instance.

3 OneData provides a repository in which to store your master data. Provide an ID for

the repository (for example, DevRepo). The ID will be used internally in OneData.

4 Provide a name for the repository (for example, OneData Development Repository).The name will appear in the OneData user interface.

5 You must specify the connection OneData is to use to connect to the OneDatadatabase components. If you do not do so, OneData will not start after installation.





The URL you specify must include the option catalogOptions=1 so that OneDatacanretrieve database metadata information for various operations (for example, jdbc:wm:oracle://localhost:1521;serviceName=XE;catalogOptions=1).

The prefix you specify will be added to each of the three schema connection names

(that is, prefix_md, prefix_wa, and prefix_ra). Provide a different database user andpassword for each of the three schemas.

Optimize

1 If you have multiple network interfaces, identify the one to use for the Optimizecomponents you are installing. Do not use "localhost."

2 Optimize offers a Central Configuration user interface that allows you to configureOptimize components from a single machine. Specify the port you want the interfaceto use to communicate with each Optimize component you are installing. Each portmust be unique. If you install multiple instances of a component on the same

machine, the port for each instance must be unique.

Optimize Application Monitoring Data Collector

1 Specify the URL for the Broker to use to route KPI readings from data collectors toOptimize. Change localhost to the correct host, the port to the correct port, andBroker #1 to the correct Broker instance name.

Important! Do not change the /analysis part of the URL.

2 You can specify the data collector port to which products should send monitoringdata.

3 You can specify the port to use to start and shut down the data collector.

Optimize Infrastructure Data Collector

1 You can specify the port to use for Infrastructure Data Collector.

2 Optimize provides a Central Configuration user interface that allows you toconfigure Optimize components from a central machine. Specify the port you wantthe interface to use to communicate with the Infrastructure Data Collector. The portmust be unique. If you install multiple instances of the Infrastructure Data Collectoron the same machine, the port for each instance must be unique.

Report Server

1 If you have multiple network interfaces, identify the one to use for the Report Server.Do not use "localhost."

2 You can specify the port to use for the Report Server.





3 The Report Server uses a Content Store. The Content Store is an external RDBMScontaining data, such as global configuration data and report definitions, that theReport Server needs to operate. You must specify the database connection betweenthe Report Server and the Content Store or the Report Server will not start afterinstallation.

The database connection fields vary slightly by RDBMS. If the service (Oracle) ordatabase (SQL Server or DB2) for which you are prompted does not yet exist, specifythe service or database you will create after installation. For more information on theContent Store, see Generating webMethods Reports.

Rules Engine

Specify the full path to your Rules Engine license file.

Trading Networks Server

Specify the database connection for Trading Networks Server to use to connect to theTrading Networks database component. If you do not do so, Trading Networks will notstart after installation.

Create Database Components

If you installed these webMethods products, you must create webMethods databasecomponents:

ActiveTransfer Server

Blaze Advisor Integration Server

Mediator

Monitor


OneData

Optimize

Process Engine

Report Server

Rules Engine

Trading Networks

For instructions, see Chapter 6, “Creating and Dropping Database Components”.






For some products, you must perform certain tasks before startup. This section explainsthose tasks. For instructions on starting products and performing post-startup

configuration and customization, see the product documentation.

Register Daemons and Set File Permissions

If you installed on a UNIX system and were prompted to use sudo, but you did not usesudo, the installer was not able to register daemons and set file permissions for theaffected products. Perform these tasks now by running the scriptSoftware AG_directory/bin/afterInstallAsRoot.sh as the root user.

Complete the webMethods Broker Installation

Make Sure Broker Server is Running and the Default Broker Exists

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

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

Enable Full Core Dumps on AIX Systems

On AIX systems, you must enable full core dumps. Using the AIX System ManagementInterface Tool (SMIT), run the command smitty chgsys and set Enable full CORE dump to

true.

Complete the Communicate Installation

1 Install Microsoft .NET Framework 3.5 and its latest service packs.

2 Install the Microsoft Visual C++ 2008 Redistributable Package. To do so, go to theSoftware AG_directory\CommunicateServer\Install\Microsoft\cpp_runtimedirectory and double-click the vcredist_x86_1.1.exe file.

3 If you installed the Aculab Telephony Hardware Drivers, do the following:

a Go to the Software AG_directory\CommunicateServer\Install\Aculab directory.b Execute the appropriate batch script for your operating system. For example, for

Windows Server 2003 32 bit, execute install_aculab2k3_x86. For Windows Server2008 32 bit, execute install_aculab2k8_x86.

c When prompted by the Windows driver signing dialog box, choose to installanyway.

d Reboot your machine.





Complete the Content Service Platform Installation

1 Create the database user and password you want to use to create the Content ServicePlatform database tables. The database user must have create table and create indices

privileges.2 Set up the Content Service Platform server. Open a command window, go to the

Software AG_directory/CSP/server directory, and run this command:

cspconfigurator.{bat|sh} -Dsetup.env.db.user=database_user

-Dsetup.env.db.password=password

Note: Do not run this command more than once.

3 The Content Service Platform offers a client you can install if you want to insert dataand search for content types in the Content Service Platform repository. The clientruns on Windows systems, but you can use it to connect to the Content Service

Platform on any operating system. Go to the Software AG_directory\CSP\winclientdirectory and locate the Software AG webMethods CSP Client Setup 8.2.exe file. If thefile is on a Windows system, double-click the .exe. If the file is on a non-Windowssystem, copy the file to a Windows system and then double-click the .exe. The clientinstaller wizard opens; follow the instructions to install the client.

Note: The .exe file name might contain additional numbers.

Complete the Local Service Development Installation

Apply IS_8.2_SP2_Core_Fix3 (or the latest fix that replaces this fix) to Integration Server

using the instructions in the fix readme. Fixes and their readmes are available from theSoftware AG Knowledge Center.

Complete the Integration Server Installation on UNIX, IBM i5/OS, and

Mac Systems

If non-root users will be running Integration Server, you might want to change theownership 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).

Complete the MashZone Installation

When you installedMashZone, you installed both the client and the server. Follow theinstructions below to start MashZone.







1 After the Software AG Installer finishes, the ARIS MashZone screen displays. ClickStart ARIS MashZone. The MashZone client starts and displays in an Internet browser.

2 If the MashZone server is not already running, start it now. To do so, on the WindowsStart menu, go to Programs > ARIS MashZone > ARIS MashZone.

3 In theMashZone client, go to the Administration panel.

4 Click the Server tab, enter your license key, and make sure the other settings, such asthe proxy server settings, are correct.

5 Click the webMethods Broker tab and configure the connection from MashZone towebMethods Broker.

Complete the Mobile Designer Installation

If you installed on a Windows system, go to the Software AG_directory\MobileDesignerdirectory and double-click the MobileDesignerInstaller exe file.

If you installed on a Mac system, go to the Software AG_directory/MobileDesignerdirectory, unzip the webMethods.MobileDesigner.pkg.zip file, and double-click thewebMethods.MobileDesigner.pkg file.

Follow the instructions to install Mobile Designer. You will be asked for your license keyand other installation options such as JDK location.

Complete the My webMethods Server Installation

If you installed My webMethods Server on a UNIX system and want My webMethodsServer to start automatically each time you start your system, run the My webMethodsServer service registration script, as follows:

Software AG_directory/MWS/bin su ./mws.sh -s server_instance installservice

mws.user=My webMethods Server_user_account [platform={suse|redhat}]

For more information on My webMethods Server startup, including optional parameters,see the section on running My webMethods Server from the command line in Administering My webMethods Server 8.2.

Connect Products to Each Other

Note: If you installed all products at the same time, and did not change any port settingsor default passwords after installation, many of these inter-product connections areconfigured automatically.

Start Integration Server and My webMethods Server

To create the connections, you need Integration Server and My webMethods Server.





Start Integration Server

Start Integration Server as follows:

Open Integration Server Administrator as follows:

Note: Integration Server can take several minutes to start. Integration ServerAdministrator will not display in your browser until Integration Server is running.

Start My webMethods Server

Start My webMethods Server as follows:

My webMethods Server takes about five minutes to initialize the first time, then shutsdown and restarts automatically. Open My webMethods as follows:

System Action

Windowsapplication

On the Start menu, go to Programs > Software AG> Start Servers > Start

Integration Server 8.2.

All othersystems

Go to the Software AG_directory/IntegrationServer/bin directory andrun the startup.sh script.

Running as... Action

Windowsapplication

On the Start menu, go to Programs > Software AG> Administ ration >

Integration Server Administrator 8.2.

Anything Enter the URL http://Integration Server_host:Integration

Server_port in an Internet browser. The default port for IntegrationServer is 5555. Log in under the default user name and password,Administrator and manage.

System Action

Windowsapplication

On the Start menu, go to Programs > Software AG> Start Servers > Start My

webMethods Server 8.2.

All othersystems

Go to the Software AG_directory/MWS/server/server_instance/bindirectory and run the command mws -s default start.


Windowsapplication

On the Start menu, go to Programs > Software AG> Administ ration > My

webMethods 8.2.





Important! After you finish connecting My webMethods Server to the other products, youwill have to restart it before you can start using it.

Connect Designer to Other Products

For instructions on connecting Designer to other products, see the Designer online help.

Connect Event Publishers and Consumers to the Event Type StoreFor instructions on connecting the Event Server and other event publisher or consumerproducts to the shared Event Type Store in a production environment, see the productdocumentation.

Connect Process Engines to Task Engine

The Process Engine must connect to the Task Engine so the Task Engine can provideresults of process steps that required human intervention to running processes.

Note: If you install multiple Process Engines in a Process Engine cluster, all ProcessEngines in the cluster share a Broker (from webMethods Broker), the same databasecomponent, or both, so the Task Engine need only connect to one Process Engine toconnect to all.

Note: If you are going to cluster Task Engines, see Administering My webMethods Server forconnection instructions.

1 Identify the Process Engines to the Task Engine as follows:

a On the My webMethods Server that hosts the Task Engine, go to the Navigate >

Appl ications > Administration > My webMethods > System Set tings > Task Engine page.b In the Integration Server (Process Engine) Host row, identify the host machine for an

Integration Server that hosts a Process Engine in your Process Engine cluster. Thedefault port for Integration Server is 5555, but the port might have been changedduring or after installation.

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

Anything Enter the URL http://My webMethods Server_host:My webMethods

Server_port in an Internet browser. The default port for MywebMethods Server is 8585. Log in under the default user name andpassword Administrator and manage.






2 Return to the Packages > Management page and do the following:

a Click for the WmOptimize package.

b In the Broker URL field, change localhost to the correct host, the port to the correct

port, and Broker #1 to the correct Broker name.

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

c If you need to edit any of the other fields, see Administering webMethods Optimize.

d Click Submit.

Connect Integration Server to the Default Broker

1 In Integration Server Administrator, go to the Settings > Messaging > Broker Settings

page and click Edit Broker Settings.

2 Complete the fields as shown below.

Field Entry

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

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

Client Group Broker Server client group to which Integration Server shouldconnect. If the specified client group does not exist, Integration

Server creates it when it connects to the Broker.Client Prefix String that identifies Integration Server to the Broker. You can define

your own, shorter, prefix. If the Integration Server is part of acluster, all Integration Servers in the cluster must use the same clientprefix.

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

Note: If this Integration Server belongs to a cluster, make sure it usesthe same client prefix as the rest of the cluster.

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





3 Click Save Changes , then restart Integration Server.

Connect Products to Their User Interfaces in My webMethods

ActiveTransfer Server, Integration Server, Monitor, the Optimize Analytic Engine, theReport Server, the Rules Engine, and Trading Networks Server must connect to the MywebMethods Server that hosts their user interfaces so My webMethods can display eachproduct's data. This section explains how to connect these products to My webMethods

Server.

Note: If you are going to cluster My webMethods Servers, see Administering MywebMethods Server for connection instructions.

Connect ActiveTransfer Servers to My webMethods Server

1 On the My webMethods Server that hosts the ActiveTransfer Server user interface, goto the Appl ications > Administr ation > Integration > M y webMethods > System Set tings >

ActiveTransfer Servers page.

2 In the Ac ti veTransfer Server Sett ings area, click Add Act iveTransfer Server Instance.

3 In the Ac ti veTransfer Server Ins tance Name field, provide a name for the ActiveTransferServer to use in the user interface.

4 Identify the Integration Server that hosts ActiveTransfer Server. The default port forIntegration Server is 5555, but the port might have been changed during or afterinstallation.

5 If My webMethods Server should use SSL to communicate with the ActiveTransferServer, select the Use Secure Connection check box.

Connect Integration Servers to My webMethods Server

If you want to administer Integration Servers from My webMethods Server, you mustmake the ESB Adminis tration option available from the My webMethods Administ rat ion menu. Perform the steps below for each My webMethods Server instance.

1 Go to the Software AG_directory/MWS/bin directory, open a command windows, andrun this command

MWS -s server_instance update

Password Password to use to access the SSL certificate inIntegration Server's keystore file.

Encryption Whether to encrypt the connection betweenIntegration Server and the Broker.

Field Entry





2 Go to the Software AG_directory/MWS/server/server_instance/deploy directory andmake sure the ESBAdministration.war file exists and its timestamp is the time ofinstallation.

Connect Monitor to My webMethods Server 1 Identify Monitor to My webMethods Server as follows:

a On the My webMethods Server that hosts the Monitor user interface, go to theNavigate > Applications > Administr ation > My webMethods > System Settings > Server page.

b In the Integration Server (Monitor) Host row, identify the host machine for anIntegration Server that hosts Monitor. The default port for Integration Server is5555, but the port might have been changed during or after installation.

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

d If you want to check whether the Integration Server is currently running, clickCheck Server Status.

e Click Save.

2 Identify My webMethods Server to Monitor as follows:

a In the Integration Server Administrator for the Integration Server that hosts

Monitor, go to the Packages > Management page and click for the WmMonitorpackage.

b If the My webMethods Server is not on the same machine as the IntegrationServer, edit the MWS Host and MWS Port fields to identify the My webMethods

Server host machine and port.

c In the MWS Username and Password fields, type the user name and password forMonitor to use to connect to the My webMethods Server that hosts the Monitoruser interface. The password default is manage.

d If you need to edit any other fields, see Monitoring BPM, Services, and Documentswith BAM: webMethods Monitor User’s Guide.

e Click Submit.

f Reload the WmMonitor package by returning to the Packages > Management page

and clicking in the WmMonitor row.

Connect Optimize Analytic Engines to My webMethods Server

Note: If you install multiple Analytic Engines, all will share the same databasecomponents, so My webMethods Server need only connect to one to connect to all.





1 Identify an Analytic Engine to My webMethods Server as follows:

a On the My webMethods Server that hosts the Optimize user interface, go to theNavigate > Applications > Administ ration > My webMethods > System Settings > Server page.

b In the Analytic Engine Host row, identify the host machine for an Analytic Engine.The default port for Analytic Engines is 12503.

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

d Click Save.

2 If you configured Optimize using the Central Configuration user interface in MywebMethods, you already identified the My webMethods Server that hosts theOptimize user interfaces to your Analytic Engines. If not, do so using the instructionsin Configuring BAM.

Connect Report Server to My webMethods Server

1 On the My webMethods Server that hosts the Reporting user interface, go to theNavigate > Applications > Administr ation > System-Wide > Report Configuration page.

2 In the Report Server Host and Port fields, identify the host machine for the ReportServer. The default port for Report Server is 9300, but the port might have beenchanged during or after installation.

3 In the Web Server Hos t and Port fields, identify the Web server you installed for usewith the Report Server.

Connect Rules Engines to My webMethods Server

Note: If you install multiple Rules Engines, all will share the same database component, soMy webMethods Server need only connect to one to connect to all.

1 On the My webMethods Server that hosts the Reporting user interface, go to theNavigate > Applications > Administr ation > My webMethods > System Settings > webMethods

Business Rules Settings page.

2 Click Add In tegrat ion Server .

3 In the row that appears, provide a name for an Integration Server that hosts a Rules

Engine and identify theIntegration Server’s host machine. The default port forIntegration Server is 5555. Also provide the user name and password for MywebMethods Server to use to log on to the Integration Server.





Connect Trading Networks Server to My webMethods Server

1 On the My webMethods Server that hosts the Trading Networks user interface, go tothe Appl ications > Adminis tration > Integration > B2B Sett ings > Configure Propert ies page.

2 In the TN Server area, identify the Integration Server that hosts Trading NetworksServer.

Connect Products to CentraSite

Connect Integration Server to CentraSite

1 In Integration Server Administrator, go to the Settings > Metadata page and click Edit

Configuration.

2 In the CentraSite Configu ration area, complete the fields as shown below.

3 Click Save Changes.

4 Return to the Settings > Metadata page and click Test Connection.

Connect Mediator to CentraSite

1 Identify Mediator to CentraSite as a target. For instructions, see the policy-enforcement targets and run-time events section of the CentraSite documentation.

2 Identify CentraSite to Mediator as follows:

a In Integration Server Administrator, go to Solutions > Mediator .

b In Mediator, go to the Administ rat ion > CentraSite Communicat ion page and click Editc Complete the fields as shown below.

Field Entry

IS Identifier Name or IP address of the local machine. Integration Serverincludes this name with the published metadata. By default,Integration Server populates this field with the IP address, butyou can enter an alias instead. The alias can include only alpha-numeric characters.

Centrasite URL URL for the CentraSite Registry Repository.

User Name andPassword

User name and password for Integration Server to use to publishassets to CentraSite.

For th is parameter... Spec ify...

Protocol Protocol to use for communication betweenCentraSiteand Mediator.

Host Name Name or IP address of the CentraSite host machine.





d Click Save.

Uninstall



Target Name Target name defined in CentraSite for Mediator.

UDDI Port CentraSite UDDI access port.

User Name andPassword

User name and password for Mediator to use to accessCentraSite.

If you are using the Operating System auth mechanism,use the format CentraSite_host\user_name for user name.

Report Performance

Data

Whether Mediator should collect performance data andreport it to CentraSite. If you select this check box, youmust also complete the Publish Interval field.

Publish Interval

(minutes)

How often, in minutes, Mediator should reportperformance data. Valid values are 1 through 60.

If a product is




For EntireX, also shut down the non-default Broker, RPCServers, and customer applications that use EntireX sharedlibraries using instructions in the product documentation.




For th is parameter... Spec ify...






3 If you are uninstalling from an HP-UX 11i v3 system, set the variableUSE_J2D_FONTCONFIG to no. In a Bourne or Bash shell, run the command export

USE_J2D_FONTCONFIG=no.

4 If you are going to uninstall Integration Server, retract all assets you have publishedto CentraSite. For instructions, see the webMethods BPM and CAF CentraSite MetadataHelp.

5 Uninstall the products using the Software AG Uninstaller. For instructions, see Usingthe Software AG Installer.

6 If you uninstalled Mobile Designer, you can remove the environment variable

MOBILE_DESIGNER from your system.7 After uninstallation, if you uninstalled webMethods Broker, and your Broker Monitor

was configured to run as a daemon, you can delete the Broker Monitor startup scriptfrom your UNIX startup directories. If you had configured a single Broker Monitor torun as a daemon, the startup script is named Snumber broker82 (for example,S45broker82). If you had configured multiple Broker Monitors to run as daemons, thenames of the startup scripts have an additional character at the end to make themunique (for example, S45broker82_1, S45broker82_2, and so on).


9 The Software AG Uninstaller does not delete files that were created after you installed

your products (for example, user-created or configuration files), nor does it delete thedirectory structure that contains the files. If you are going to reinstall into the samedirectory, delete the product directories after uninstallation is complete or, if youwant to save the files, move them.




6 Creating and Dropping Database Components

webMethods Products and Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Data Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Preparing for Database Component Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

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

Use the Database Component Configurator Graphical User Interface . . . . . . . . . . . . . . . . . . . . 121

Use the Database Component Configurator Command Line Interface . . . . . . . . . . . . . . . . . . . . 129

Use the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Connect Products to Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141





webMethods Products and Databases

If you installed these webMethods products, you must create webMethods databasecomponents:

ActiveTransfer Server

Blaze Advisor

Integration Server

Mediator

Monitor


OneData

Optimize Process Engine

Report Server

Rules Engine

Trading Networks

A database component is a grouping of database objects that can be used by one or moreproducts. For example, Integration Servers write process status data to the Process AuditLog database component; My webMethods Server reads the data from the Process AuditLog database component and passes it to My webMethods to display. Each databasecomponent is named for the type of data that is written to it; for example, the databasecomponent for IS Core Audit Log data is called the ISCoreAudit database component.

The products listed above use Java Database Connectivity (JDBC) to interact with theirdatabases; specifically, to query and update data in database components. Unlessotherwise noted, the products use the DataDirect Connect JDBC 4.2 driver. The productscome with the client component of this driver; it is a Type 5 JDBC native-protocol driverthat does not have a server component. The products use the driver to convert JDBCrequests from Java programs directly into the vendor-specific database protocol that eachtype of RDBMS can understand. The products execute DDL commands at install timeand sometimes design time for each RDBMS with which they interact. For informationabout the driver, see DataDirect Connect for JDBC User's Guide and Reference 4.2 in theSoftware AG_directory/_documentation directory or on the Software AG Documentation

Web site.

To enable products to interact with a database component, you provide databaseconnection parameters, usually during product installation, and the Software AGInstaller uses the parameters to configure JDBC connection pools. After productinstallation and database component creation is complete, you set up the products to usethe appropriate connection pools.









For the list of RDBMSs supported by webMethods products, see the webMethods SystemRequirements.

Note: If you want your products to exchange data with databases other than webMethodsdatabases, you can use the webMethods JDBC Adapter. For more information, see thewebMethods JDBC Adapter documentation.

Data Storage

Integration Server Data Storage

Integration Server can persist these types of data:

Type of Data Content Integration Server wr itesthis data when...

IS Internal Scheduled tasks, client certificate mappings,run-time data for pub.storage services, auditlog of guaranteed delivery transactions, andtrigger* joins.

You are using thefeatures listed in theContents column

IS CoreAudit Log

Error, guaranteed delivery, service,security, and session audit data.

Logging is enabled (seethe webMethods AuditLogging Guide)

Documents that are in doubt, have failed,or have exhausted trigger* retries.

You are using triggers

CrossReference

Cross-referencing data* for publish-and-subscribe solutions.

You are using publish-and-subscribesolutions

DocumentHistory*

Document history data for exactly-onceprocessing* in publish-and-subscribesolutions. Integration Server uses the data todetect and reject duplicate documents.

You are using exactly-once processing

DistributedLocking

Information that coordinates access toresources across distributed servers andprocesses. Resources can be locked to prevent

one server from accessing a resource as it is being updated by another, or to prevent oneserver from updating a resource as it is beingaccessed by another.

Executing services inthe pub.storage folder.

*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 IntegrationServer to write data to an embedded database or an external RDBMS. The sections belowexplain when you would choose each option.

Embedded DatabaseThe 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 the runtime for adapters, or Deployer).

Do not have an external RDBMS.

Are not installing in a production environment that has high transaction volumes orlarge datasets.

If you choose the embedded database, Integration Server will write IS Internal and CrossReference data to that database, and will write IS Core Audit Log data to files. For

information about the files, see the webMethods Audit Logging Guide.

Important! Integration Server uses Derby, a file-based database, as its embedded database.If one of database file gets corrupted, the entire database might become unusable.Software AG therefore recommends backing up the Integration Server_directory\db folderperiodically so you will be able to return to the last known good state if necessary.

Document History data can only be written to an external RDBMS. You are using exactly-once processing in publish-and-subscribe solutions, you must create theDocumentHistory database component and configure Integration Server appropriately.

If you later choose to write IS Internal, Cross Reference, or IS Core Audit Log data to an

external RDBMS instead of the embedded database, you will need to install the necessarydatabase components. You will then need to reconfigure where Integration Server writesIS Internal and Cross Reference data as described in Administering webMethods IntegrationServer , and IS Core Audit Log data as described in “Connect Products to DatabaseComponents” on page 141. You must write IS Core Audit Log data to an external RDBMSwhen the IS Core Audit Log includes the following types of data:

If you are using triggers. When you use triggers, Integration Server needs to writeproblem documents to the IS Core Audit Log. Documents can only be written to anexternal RDBMS; they cannot be written to files.

If you want services to log their input pipelines, or post user-defined progressmessages (for example, to indicate whether certain pieces of code ran successfully).

Input pipelines and user-defined messages can only be written to an externalRDBMS; they cannot be written to files.

You are using Mediator, and have configured the log invocation policy action inCentraSite to include the request or response SOAP envelopes with loggedtransaction events. The MediatorEvents database component to which Mediatorwrites is in the same schema (Oracle) or database (DB2 or SQL Server) as theISCoreAudit database component.





If you are using Monitor. Monitor can only read from an RDBMS.

External RDBMS

You must use an external RDBMS if you are going to:

Cluster Integration Servers.

Write Document History data (that is, use exactly-once processing in publish-and-subscribe solutions).

Write Process Audit Log and Process Engine data (that is, run business processes).

Use triggers; Integration Server can only write problem documents to an externalRDBMS.

Have services log their input pipelines, or post user-defined progress messages (forexample, to indicate whether certain segments of code ran successfully).

Use Monitor. You are using Mediator, and have configured the log invocation policy action in

CentraSite to include the request or response SOAP envelopes with loggedtransaction events. The MediatorEvents database component to which Mediatorwrites is in the same schema (Oracle) or database (DB2 or SQL Server) as theISCoreAudit database component.

Install in a production environment with high transaction volumes or large datasets.

When you use an external RDBMS, you must create the ISCoreAudit, ISInternal, andDistributedLocking database components in your external RDBMS. You must create theISInternal and DistributedLocking database components in the same schema (Oracle) or

database (DB2 or SQL Server). You will also create other database components as needed.For example, if you are using publish-and-subscribe solutions and exactly-onceprocessing, you will need the CrossReference and DocumentHistory databasecomponents; if you are running business processes, you will need the ProcessAudit andProcessEngine database components. For complete information about the databasecomponents you will need to create, see “Product Database Component Descriptions andInstallation Requirements” on page 110.

When you choose the external RDBMS in the installer, the installer asks you to supply thedatabase connection. From this information, the installer creates a JDBC connection pooland configures Integration Server to write IS Internal, IS Core Audit Log, CrossReference, Distributed Locking, Document History, Process Audit Log, and Process

Engine data to the external RDBMS using that pool.

Note: This auto-configuration of Integration Server is for ease of use only. You need notcreate all the corresponding database components; only create those you will actuallyuse. Also, in a production environment, you might want to create additional JDBCconnection pools and reconfigure Integration Server to write different types of data usingdifferent pools. “Connect Products to Database Components” on page 141 providesinstructions.





If you are clustering Integration Servers, create one of each of the following databasecomponents for the cluster to share: ISCoreAudit, ISInternal and DistributedLocking inthe same schema (Oracle) or database (DB2 or SQL Server), CrossReference, andDocumentHistory.

If you are not clustering Integration Servers, create an ISInternal database componentand a Distributed Locking database component in the same schema (Oracle) or database(DB2 or SQL Server) for all Integration Servers to share. Also create the ISCoreAudit,CrossReference, and DocumentHistory database components; you can create a singleinstance of each of those database components for all Integration Servers to share, or youcan create a separate instance of each of those database components for each IntegrationServer.

Product Database Component Descriptions and Installation

Requirements

This section briefly describes each database component and its installation requirements.

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

Acti veTransfer Database Component

If you installed ActiveTransfer Server, you must create the ActiveTransfer databasecomponent.

ActiveTransfer Server writes listener (port), server, user configuration, and other

metadata to this database component. ActiveTransfer Server also writes run-time data,such as file transfer transaction information and audit data. MashZone displays the datafrom this database component in dashboards.

If you are clustering ActiveTransfer Servers, create a single ActiveTransfer databasecomponent for the cluster to share. If you are not clustering, create a separateActiveTransfer database component for each ActiveTransfer Server.

Arch ive Database Component

If you want to archive data from the ISCoreAudit and ProcessAudit databasecomponents (called the "source" database components in this section), create the Archivedatabase component.

The Archive database component includes a copy of the ISCoreAudit and ProcessAuditdatabase components. You must create the Archive database component in the same typeof RDBMS as the source database components. Depending on the RDBMS, you can do thefollowing:





For Oracle, DB2, or SQL Server, you can create the Archive database component onthe same database server as the source database components. In this case, you mustcreate the Archive database component in a different schema (Oracle or DB2) ordatabase (SQL Server) than the source database components.

For Oracle or SQL Server, you can create the Archive database component on adifferent database server than the source database components, and then create aDBlink name for the Archive database component to use to link to each sourcedatabase component. If the two source database components are on the samedatabase server, the Archive database component can use the same DBLink toconnect to both source database components. For instructions on specifying theDBlink name, see Monitoring BPM, Services, and Documents with BAM: webMethods Monitor User’s Guide.

Blaze Database Component

If you want to use the Blaze user interface in My webMethods to edit rules created in

Blaze Advisor, create the Blaze database component.

Blaze Advisor writes metadata, project information, and rulesets for Blaze rules to thisdatabase component. The Blaze user interface connects to this database component toretrieve Blaze rules and to store Blaze rules after users modify them.

BusinessRules Database Component

If you installed the Rules Engine, you must create the BusinessRules databasecomponent. You must create the database component in the same schema (Oracle) ordatabase (SQL Server and DB2) as the ProcessAudit database component.

As each Rules Engine instance starts, it registers itself in this database component andstores information about deployed projects and the state of business rules instances.When you modify a business rule, the hot deployment functionality in the Business Rulesuser interface in My webMethods enables you to deploy changes to all of the instancesregistered in this database component.

If you install multiple Rules Engine instances, create a single BusinessRules databasecomponent for the instances to share.

Designer

See “Monitor Staging and Reporting Database Components” on page 112.

Integration Server ISCoreAudit, ISInternal, Cross Reference, Dist ribu tedLocking, DocumentHistory, and DistributedLocking Database Components

See “Integration Server Data Storage” on page 107.





MediatorEvents Database Component

If you installed Mediator, you must create the MediatorEvents database component. Youmust create the database component in the same schema (Oracle) or database (SQLServer and DB2) as the ISCoreAudit database component.

Mediator writes transaction events about certain SOA policies to the MediatorEventsdatabase component.

Monitor Staging and Reporting Database Components

If you want to simulate business processes in Designer using historical data, create theReporting database component. Tables for simulation data are automatically created aspart of the Reporting database component.

If you want to generate Monitor reports, create the Staging and Reporting databasecomponents. Monitor extracts business process audit and execution data from the

ProcessAudit database component and aggregates it using the Staging and Reportingdatabase components. The Report Server generates the Monitor reports about businessprocess execution metrics from the aggregated data in the Reporting databasecomponent. The Reporting user interface in My webMethods displays the reports.

You can create the Reporting and Staging database components in the same schema(Oracle) or database (DB2 or SQL Server). However, the Monitor services that aggregateand load data consume large amounts of the CPU. For best performance, install theReporting and Staging database components on a database server that will not adverselyaffect the ProcessAudit or ProcessEngine database components.

The ProcessAudit, Staging, and Reporting database components have a 1-to-1-to-1relationship. This means that you cannot gather data from multiple ProcessAudit

database components into a single Reporting database component. The Report Server cangenerate Monitor reports from only one Reporting database component at a time.

MywebMethodsServer Database Component

If you installed My webMethods Server, you must create the MywebMethodsServerdatabase component.

The following write to this database component:

My webMethods Server writes data about deployment, configuration, security, portalpages, and run-time operations. It uses this data to manage the My webMethods userinterfaces (that is, the user interfaces in My webMethods for webMethods Broker,

Monitor, Optimize, Optimize for B2B, Reporting, and Trading Networks) and tosupport central user management in Integration Server and Optimize.

The Task Engine writes task status, task distribution, and business data. The TaskEngine user interface in My webMethods displays the data.

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





OneDataMetadata, OneDataWorkArea, OneDataReleaseArea Database

Components

If you installed OneData, you must create the OneDataMetadata, OneDataWorkArea,

and OneDataReleaseArea database components. OneData writes internal configuration data to the OneDataMetadata database

component.

OneData users create data objects and work-in-progress data values in theOneDataWorkArea database component.

The OneDataReleaseArea database component contains the same data objects as theOneDataWorkArea database component, and approved data values. Data values aredeployed from the OneDataReleaseArea database component.

You must create each OneData database component in a separate Oracle schema, with adifferent Oracle database user. You must create the OneDataMetadata database

component first, then the OneDataWorkArea database component, then theOneDataReleaseArea database component.

Optimize

Analysis Database Component

If you installed Optimize, you must create the Analysis database component.

Optimize Analytic Engines write computed analytics and process and monitoring datareceived from Infrastructure Data Collectors and Web Service Data Collectors to theAnalysis database component. Optimize Prediction Engines evaluate the data and

generate prediction events. The Optimize user interface in My webMethods displays thedata.

The Report Server generates Optimize reports about key performance indicators (KPIs)from the data in the Analysis database component. The Reporting user interface in MywebMethods displays the data.

Create a single Analysis database component for all Optimize Analytic Engines to share.If you are going to use root cause analysis for business processes, install the Analysis andProcessTracker database components in the same schema (Oracle) or database (DB2 orSQL Server).

ProcessTracker Database Component

If you installed Optimize, you must create the ProcessTracker database component.

Optimize Analytic Engines write business and process status data received fromprocesses that are not orchestrated by the Process Engine to the ProcessTracker databasecomponent. The Optimize user interface in My webMethods displays the data.





Create a single ProcessTracker database component for all Optimize Analytic Engines toshare. If you are going to use root cause analysis for business processes, install theProcessTracker and Analysis database components in the same schema (Oracle) ordatabase (DB2 or SQL Server).

CentralConfiguration Database Component

The CentralConfiguration database component is automatically created when you createthe MywebMethodsServer database component. The CentralConfiguration databasecomponent stores the Optimize configuration information you enter in the CentralConfiguration interface in My webMethods.

Note: The CentralConfiguration database component is not automatically dropped whenyou drop the MywebMethodsServer database component. If you want to drop theCentralConfiguration database component, you must do so manually.

Process Engine

ProcessAudi t Database Component

If you installed the Process Engine, you must create the ProcessAudit databasecomponent.

The following write to this database component:

Process Engines write process audit data for business processes they orchestrate.

Task Engines write task audit data.

Third-party products can write process execution data.

Optimize Analytic Engines read process data from this database component so they cananalyze capabilities such as transition duration and write data about analysis-enabledprocesses. The Optimize user interface in My webMethods displays the data.

If you are distributing business process steps, you cluster the Process Engines thatorchestrate the steps. Create a single ProcessAudit database component for the cluster toshare. Integration Servers that host these Process Engines and also the Blaze Rule ServiceSupport package register themselves in the shared ProcessAudit database component.When users modify rules in the Blaze user interface in My webMethods, the interfaceredeploys the modified rules to the registered Integration Servers.

If you are not distributing business process steps, and therefore not clustering Process

Engines, you can create either a separate ProcessAudit database component for eachProcess Engine or a single shared ProcessAudit database component.

Create a single ProcessAudit database components for all Task Engines to share.

If you are using Process Engines, Task Engines, Optimize Analytic Engines, or somecombination of these, create a single ProcessAudit database component for all to share.





ProcessEngine Database Component

If you installed the Process Engine, you must create the ProcessEngine databasecomponent.

Process Engines write process execution data for processes they orchestrate to thisdatabase component.

If you are distributing business process steps, you cluster the Process Engines thatorchestrate the steps. Create a single ProcessEngine database component for the cluster toshare. If you are not clustering, create a separate ProcessEngine database component foreach Process Engine.

Report Server

SuiteReporting Database Component

If you installed Report Server, the SuiteReporting database component is automatically

created when you create the MywebMethodsServer database component. TheSuiteReporting component stores the configuration information you enter in theReporting interface in My webMethods.

Note: The SuiteReporting database component is not automatically dropped when youdrop the MywebMethodsServer database component. If you want to drop theSuiteReporting database component, you must do so manually.

SuiteReporting-Common Database Component

If you installed Report Server, and are using Trading Networks and Optimize reports,

you must create this database component in the TradingNetworks and Analysis databasecomponents, respectively. This database component stores the database objects for thereports.

Note: Monitor reports do not require this database component.

TradingNetworks and TradingNetworksArchive Database Components

If you installed Trading Networks Server, you must create the TradingNetworks databasecomponent. If you want to archive your Trading Networks data, also create theTradingNetworksArchive database component. You must create the

TradingNetworksArchive database component in the same schema (Oracle) or database(SQL Server and DB2) as the source TradingNetworks database component.

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 theTradingNetworks database component. Trading Networks Server also logs entries aboutdocument processing steps. Trading Networks Console and the Trading Networks user





interface in My webMethods display the data. Trading Networks archiving functionalitycan archive data from the TradingNetworks database component to theTradingNetworksArchive database component.

The Report Server generates Trading Networks reports about B2B transactions and

trading partners from the data in the TradingNetworks and TradingNetworksArchivedatabase components. The Report Server generates Optimize for B2B reports aboutTrading Networks document types and attributes that are monitored by Optimize forB2B from the data in the TradingNetworks database component. The reports display inthe reporting user interface in My webMethods.

If you are clustering Trading Networks Servers, create a single TradingNetworksdatabase component for the cluster to share. If you are not clustering, create a separateTradingNetworks database component for each Trading Networks Server.

Infrastructure Database Components

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

The table below lists infrastructure database components that are automatically createdwhen you create product-related database components.

Preparing for Database Component Creation

Database Users and Storage

You can create one database user for multiple database components, or you can create adifferent database user for each database component. You can create all databasecomponent objects in the same storage or you can create the objects for each databasecomponent in its own storage. Later sections in this chapter explain how to createdatabase users and storage.

The database user must have the permissions listed in the file below.

Database Component Description

ComponentTracker Tracks the database components that are created ordropped.

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

DatabaseManagement Provides core routines for data purge functionality.

OperationManagement Provides a common method for configuration, logging, anderror handling for any database component.





Database Administrator Account

You need DBA access only if you want to use the Database Component Configurator tocreate the necessary database users and storage objects.

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

Character Set and Sort Order

webMethods products are globalized and support Unicode. Software AG stronglyrecommends choosing a Unicode encoding for your database and the most appropriate

sort order for your environment. A database character set determines which languages adatabase can represent. Database sort order determines collation and comparison behavior.

The sections below list the most appropriate Unicode character encoding and sort orderfor each RDBMS that webMethods products support. If you want to use a differentcharacter set or sort order than recommended below, consult your databaseadministrator and your RDBMS vendor's documentation so you can carefully choose adatabase character set that supports the languages your data is in.

If you use the Database Component Configurator to create your database components,you can check whether the selected RDBMS is configured for the Unicode character set. Ifthe 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 storage.

RDBMS Path to File

Oracle Software AG_directory\common\db\scripts\oracle\storage\25\create\ora_str_c_ddl_user.sql

Note: webMethods scripts require ALTER SESSION permission at thetime of creating database tables. You can revoke this permission after thetables have been created.

SQL Server Software AG_directory\common\db\scripts\mssql\storage\30\create\mss_str_c_ddl_user.sql

DB2 Software AG_directory\common\db\scripts\db2\storage\30\create\db2_str_c_ddl_user.sql





Oracle

Database schemas for Oracle use character data types. For character data types, Oraclesupports the UTF8 and AL32UTF8 Unicode encodings. While UTF8 is CESU-8 compliantand supports the Unicode 3.0 UTF-8 Universal character set, AL32UTF8 conforms to theUnicode 3.1 or higher UTF-8 Universal character set. For nchar data types, Oraclesupports the AL32UTF8 and AL16UTF16 Unicode encodings. The supported Unicodeversion for AL32UTF8 depends on the Oracle database version. Oracle database schemasfor webMethods products do not have linguistic indexes. Software AG recommendsthese character sets and sort order:

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

SQL Server

Database schemas for SQL Server use nchar data types. SQL Server provides support forUTF-16 through its nchar data types. Since nchar data types are always in UTF-16, you donot have to perform any special database configuration and can choose the mostappropriate code page for your environment as a database character set. Software AGrecommends these character sets and sort order:

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

DB2

Database schemas for DB2 use character data types. DB2 supports UTF-8 for characterdata types and UTF-16 for graphic data types. Software AG recommends these charactersets and sort order:

For... Software AG recommends...

Character set AL32UTF8

Nchar character set AL16UTF16

Sort order Binary


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, youwill not be able to create some database components in SQLServer.





You can check the database configuration by using the following:

Page and Block Size

Use the page and block sizes specified below for each type of RDBMS.

Set Database Options

Oracle

For webMethods products to function properly, you must set theNLS_LENGTH_SEMANTICS initialization parameter to BYTE.


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 onlyavailable for DB2 for Linux, Unix, Windows (LUW). ForDB2 for iSeries, sort order is always binary order when thedatabase character set is UTF-8.

RDBMS Use...

DB2 for LUW GET DATABASE CONFIGURATION command

DB2 for iSeries DSPFD command to check the database file description

RDBMS Required Page and Block Size Default

Oracle 8k page/block size 8k

SQL Server 8k page/block size 8k

DB2 32k page size 4k





Important! webMethods products use BYTE rather than CHAR semantics because BYTE isthe default configuration of Oracle database and is used by most Oracle users. If you tryto use webMethods products with CHAR semantics, unexpected results might occur. Forexample, 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 functionproperly:

ALTER DATABASE database_name SET ALLOW_SNAPSHOT_ISOLATION ON;

ALTER DATABASE database_name SET READ_COMMITTED_SNAPSHOT ON;

In addition, enable Named Pipes and TCP/IP protocols using the SQL ServerConfiguration Manager.

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

Default Storage Convention

By default, all database components follow this storage convention:

You can use a different storage convention when you create database components. Forinstructions, see “Modify Storage Convention” on page 139.

Download the Database Component Configurator and

Database Scripts

The Database Component Configurator and database scripts are available through theSoftware AG Installer. For complete instructions on using the installer, see Using theSoftware AG Installer.

RDBMS Data Storage Unit Index Storage Unit BLOB Storage Unit

Oracle tablespaces WEBMDATA WEBMINDX WEBMDATA

SQL Server filegroups Primary Primary Primary

DB2 for LUWtablespaces

WEBMDATA WEBMINDX WEBMBLOB

DB2 for iSeries Default Default Default





1 Download the Software AG Installer as instructed by your installation email fromSoftware AG to the appropriate machine, as follows:

2 Start the installer.

3 In the product selection list, select Database Configuration > Database Scripts or Database

Component Configurator , as desired.

4 The Database Component Configurator has the default environment settings shown

below. If necessary, you can change them as described below.

a Go to the Software AG_directory\common\db\bin directory.

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

c Save and close the file.

Use the Database Component Configurator Graphical UserInterface

This section explains how to use the Database Component Configurator graphical userinterface (GUI) to create or drop a database user and storage, and to create or dropdatabase components. Each run of the configurator operates on a single schema.

If you are going to create database

components... Download the Software AG Installer to...

Automatically, using the DatabaseComponent Configurator

Any machine on the same network as yourdatabase server

Manually, using database scripts A machine equipped with the database clientfor your type of RDBMS

Setting Determines whether the configurator... Default

-DtermOutOn Writes execution information to theconsole.

true

-DspoolOn Logs execution information. true

-DlogLevel Sets the log level to INFO (high-level

information) or DEBUG (moredetailed information, includinginternal processing and SQL calls).

INFO

-Dlog.dir This setting specifies the full path tothe directory in which to store thelog files. Make sure you havepermission to write to this directory.

Software AG_directory\common\db\logs





You can use the Database Component Configurator GUI on all operating systems that aresupported by webMethods products. UNIX systems must have an X Windowsenvironment.

The configurator writes execution information to the Results tab and to a log file named

dcc_ yyyymmddHHMMss in the Software AG_directory\common\db\logs directory.

Create Database Components, Database User, and Storage

For Oracle, SQL Server, and DB2 for LUW, when you create database components usingthe configurator, you can also create the database user and storage. For DB2 for iSeries,you must create the database user and storage using scripts (see “Use the DatabaseScripts” on page 139).

Important! When you create database components in DB2 using the Database ComponentConfigurator, 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 schemanames when you type them in URLs for JDBC connection pools, or you will experienceproblems.

Start the Database Component Conf igurator GUI

Start the Database Component Configurator GUI as follows:

System Action

Windows On the Start menu, go to Programs > Software AG> Tools > Database

Component Configurator .

UNIX Go to Software AG_directory and run the command dbConfigurator.sh.





Initially, some of the fields on the Inputs tab show values you entered for the same fields inthe Software AG Installer during product installation. You can change these values andspecify other field values.

Choose the Action to Perform

In the Ac tion Type list, click the action to perform, as follows:

Option Action

create Creates the database components you select in the Database

component list, and lets you create a database user and storage.





Specify the Connect ion to the RDBMS

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

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

2 In the URL field, provide the URL for the RDBMS. Sample URL formats for theDataDirect Connect JDBC 4.2 driver are displayed. Below is additional information

for completing this field. 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 (forexample, ;sysLoginRole=sysdba).

For DB2, if you are going to create database components in a schema other thanthe default schema for the specified database user, you must specify theseconnection options in the URL, where AlternateID is the name of the defaultschema used to qualify unqualified database objects in dynamically preparedSQL statements:


PATH=current_path,schema)”

Important! If you are creating Optimize database components (that is, Analysis andProcessTracker), you must specify schema using all uppercase letters. In addition,you must specify the options CreateDefaultPackage=true,ReplacePackage=true ,and DynamicSections=3000. These settings will affect all database components inthe same schema or database.

For information about options supported by the DataDirect Connect JDBC 4.2driver used by webMethods products, see DataDirect Connect for JDBC User'sGuide and Reference 4.2 in the Software AG_directory/_documentation directory oron the Software AG Documentation Web site.

recreate Drops and then re-creates the database components you select in theDatabase component list.

catalog Displays existing database components on the Results tab.checkEncoding Checks whether your RDBMS is Unicode-enabled and displays the

answer on the Results tab.

Option Action







3 In the User ID and Password fields, your entries depend on the task you are going toperform, as follows:

Create Database Components, Database User, and Storage

If you selected create in the Ac tion Type list, do the following:

1 In the Database Component list, select the database components to create. You can useany of the options below.

Click one database component to create.

If you are going to create the SuiteReporting-Common database component, itrequires the following:

8GB of hard drive space for Oracle and DB2 and 18GB for SQL Server. It willtake about 10 minutes (Oracle and DB2) and 1 hour (SQL Server) to create thedatabase component.

For DB2, the configuration parameters below must be set as follows:

LOGFILSZ=8192LOGPRIMARY=20

LOGSECOND=10

APPLHEAPSZ=60000

If you are... Specify...

Creating a database user and storagein Oracle or SQL Server

The database user and password to create.

Note: For SQL Server, the user will becreated and a default schema named dbowill be assigned to that user.

Important! For Oracle, do not use theSYSTEM user to create the databasecomponents in the SYSTEM schema.

Creating a database user and storage

in DB2 for LUW

The OS user to which to grant permissions,

and the password for that user.

Creating database components orperforming the catalog action

An existing database user and password.

Performing the checkEncoding action An existing database user that has createsession and create table privileges, and thatdatabase user's password.





In addition, the log must be at least 500MB.

Click Al l - COMPONENT to create all database components. The Al l - COMPONENT option includes the SuiteReporting-Common database component; see theprevious bullet for requirements.

Click product - PRODUCT to create the database components for that product, orclick Al l - PRODUCT to create the database components for all the PRODUCT options.You can see the list of database components for a PRODUCT option by selecting thePRODUCT option, clicking print in the Ac tion Type list, clicking Execute, and thenclicking the Results tab.

2 Select from the Version list as follows:

3 If you want to also create the database user and storage, follow the steps below.

a Select the Create Tablespaces check box.

Note: This check box is labeled Create Database and Database User for SQL Server,and Create Tablespaces and Grant Permiss ions to OS User for DB2.

Note: For DB2 on Linux systems, tablespaces are created for each DB2 database. Ifyou are creating webMethods database components in more than one DB2database, either the tablespace directory or the tablespace names must be uniquefor each DB2 database.

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

c The next field and your entry depend on your RDBMS.

If you selected... Click...

A databasecomponent or Al l -

COMPONENT

Latest. The configurator will create the latest version of thedatabase component or of all database components,

respectively.product - PRODUCT or Al l - PRODUCT

8.2.

RDBMS Field and Entry

Oracle or DB2for LUW

In the Tablespace Directo ry field, identify the directory inwhich to create the tablespaces. For Oracle, use this field onlyif the DB_CREATE_FILE_DEST parameter is not set for yourOracle instance.

SQL Server In the Database field, specify the database to create.





4 For Oracle or DB2 for LUW, you can select the Use Custom Tablespace Names check boxand specify custom tablespace names in the fields.

For Oracle, the custom tablespace names will replace the defaults WEBMDATAand WEBMINDX.

For DB2 for LUW, the custom tablespace names will replace the defaultsWEBMDATA, WEBMINDX, and WEBMBLOB. You can also specify a customname to use for the buffer pool for webMethods products (WEBMBUFF bydefault).

Note: webMethods products support all tablespace configurations deployed byusers.

Execute the Specified Act ion

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

2 Click Execute. The execution information is displayed on the Results tab and is writtento the log file dcc_ yyyymmddHHMMss in the Software AG_directory\common\db\logsdirectory.

Drop Database Components

1 Shut down all products that are connected to the database components you want todrop, and back up the database components.

2 Start the Database Component Configurator GUI as follows:

3 In the Ac tion list, click the action to perform, as follows:

System Action



UNIX Go to Software AG_directory and run the commanddbConfigurator.sh.

Value Action

drop Drops the database components you select in the Database component list.

catalog Lists existing database components on the Results tab.





4 In the Connection area, specify the connection for the configurator to use to connect tothe RDBMS, as follows:

5 In the Database Component list, select the database components to drop.

6 Select from the Version list as follows:

7 Click Execute. The execution information is displayed on the Results tab and is writtento the log file dcc_ yyyymmddHHMMss in the Software AG_directory\common\db\logsdirectory.

Drop the Storage and Revoke Database User Permissions

If you have dropped all database components in a schema, you can drop the storage andrevoke the database user permissions.

You can use the Database Component Configurator to drop the storage for Oracle, SQLServer, and DB2 for LUW. For DB2 for iSeries, you must drop the database user andstorage using a script (see “Use the Database Scripts” on page 139).

1 Start the Database Component Configurator GUI as follows:

2 In the Ac tion list, click drop.

3 In the Database component list, click Al l - COMPONENT.

Field Do this...

RDBMS Click the RDBMS from which to drop the database components.

URL Type the URL for the RDBMS. Sample URL formats for theDataDirect Connect JDBC 4.2 driver are displayed.

User ID andPassword

Specify the database user and password to use to connect to theRDBMS.

If you selected... Click this in the Version list...

A database component or Al l -

COMPONENT

Latest.

A product 8.2.

System Action



UNIX Go to Software AG_directory and run the commanddbConfigurator.sh.





Important! When you create database components in DB2 using the Database ComponentConfigurator, the configurator creates the schema name in all uppercase letters. SinceDB2 is case sensitive for schema names, you must use all uppercase letters for the schemanames when you type them in URLs for JDBC connection pools, or you will experience

problems.

Before dropping any database component, shut down all products that are connected tothe database component.

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

Database Component Configurator Command

You can perform an action on one database component or on all database components, oron the database components for one product, using the command below. You run thecommand from the Software AG_directory\common\db\bin directory.

dbConfigurator.{bat|sh} {-a|--action} action

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

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

{-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]

[{-tsdata|--tablespacefordata} data_tspace_name][{-tsindex|--tablespaceforindex} index_tspace_name]

[{-tsblob|--tablespaceforblob} BLOB_tspace_name]

[{-b|--bufferpool} buffer_pool_name]

[-t|--tablespacedir directory]

[-n|--dbname database_name]

[-h|--help]

[-ab|--about]

[-pa|--printActions] [-pd|--printDatabase] [-pc|--printComponents]

[-pp|--printProducts] [-pe]

[{-e|--export|-i|--import} {-dir|--configdir} directory

{-file|--configfile} file_name]

Parameter Entry

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

Value Action

catalog Displays existing database components.

create Creates db_component or the databasecomponents for product.





drop Drops db_component or the databasecomponents for product.

recreate Drops db_component or the databasecomponents for product , then createsdb_component or the databasecomponents for product.

checkEncoding Checks whether your RDBMS isUnicode-enabled and displays theanswer.

{-d|--dbms} {oracle|

sqlserver|db2luw|db2i}RDBMS on which to perform action.

Value DBMS

oracle Oraclesqlserver SQL Server

db2luw DB2 for LUW

db2i DB2 for iSeries

{-c|--component}

db_component

{-v|--version} version

Database component version for which to perform action.

For db_component , you can specify the database componentcode or name. You can see the list of database componentcodes and names by specifying -c all with the print action.

Important! The SuiteReporting-Common database component,which is also included in the ALL option, requires thefollowing:

8GB of hard drive space for Oracle and DB2 and 18GBfor SQL Server. It will take about 10 minutes (Oracleand DB2) and 1 hour (SQL Server) to create thedatabase component.

For DB2, the configuration parameters below must beset as follows:

LOGFILSZ=8192

LOGPRIMARY=20

LOGSECOND=10

APPLHEAPSZ=60000

For DB2, the log must be at least 500MB.

Parameter Entry





For version , you can specify this value:

Value Description

latest If you specified one database componentfor db_component , perform action for thelatest version of db_component.

If you specified ALL for db_component ,you must specify latest fordb_component_version. The configuratorwill create the latest version of eachdatabase component.

{-pr|--product}

product

{-v|--version}

release

Product release for whose database components to performaction.

For product , you can specify the product code or name, orALL. You can see the list of database components for aproduct by specifying this parameter with the print action.

For release , you can specify the values below.

Value Description

latest Perform action on the databasecomponents for the latest release ofproduct.

release Release of the product for whose

database components to perform action.The configurator will create the correctversions of the database components forthe specified release.

{-l|--url} RDBMS_URL URL for the RDBMS. For information about optionssupported by the DataDirect Connect JDBC 4.2 driver used by webMethods products, see DataDirect Connect for JDBCUser's Guide and Reference 4.2 in theSoftware AG_directory/_documentation directory or on theSoftware AG Documentation Web site.

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

RDBMS Sample Format for DataDirect Connect Driver

Oracle jdbc:wm:oracle://server:{1521|port}

;serviceName=service[;option=value].

..

Parameter Entry







Important! For Oracle, If are going to create storage and theData Purge database component, you must specify the

sysLoginRole connection option on the URL (for example,;sysLoginRole=sysdba).

SQL Server jdbc:wm:sqlserver://server:{1433|por

t}

;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

]...

For DB2, if you are going to create database components ina schema other than the default schema for the specifieddatabase user, you must specify these connection options inthe URL:

;AlternateId=schema;”InitializationString=(SET

CURRENT PATH=current_path,schema)”

AlternateID is the name of the default schema used toqualify unqualified database objects in dynamicallyprepared SQL statements.

If you are creating Optimize database components (that is,Analysis and ProcessTracker), you must specify schema using all uppercase letters. In addition, you must specifythe options CreateDefaultPackage=true,ReplacePackage=true , and DynamicSections=3000. Thesesettings will affect all database components in the sameschema or database.

{-u|--user} db_user

{-p|--password}

password

Your entry here depends on the action you are performing.

If you are... Specify...

Parameter Entry





Creating adatabase userand storage inOracle or SQLServer

The database user and password tocreate.

Note: For SQL Server, the user will becreated and a default schema named dbowill be assigned to that user.

Important! For Oracle, do not use theSYSTEM user to create the databasecomponents in the SYSTEM schema.

Creating adatabase userand storage inDB2 for LUW

The OS user to which to grantpermissions.

Performing thecheckEncodingaction

An existing database user that has createsession and create table privileges, andthat database user's password.

Performing anyother action

An existing database user and password.

[{-au|--admin_user}

db_admin_user

{-ap|--admin_password}

password]

If you are going to create a database user and storage, ordrop storage and revoke the database user permissions,specify the database user or operating system user andpassword that has the necessary database administrator

credentials.

Addi tional Parameters

[-r|--runCatalog] Runs the catalog action at the end of every execution.

Parameter Entry





[{-tsdata|

--tablespacefordata}

data_tspace_name]

[{-tsindex|--tablespaceforindex}

index_tspace_name]

[{-tsblob|--

tablespaceforblob}

BLOB_tspace_name]

[{-b|--bufferpool}

buffer_pool_name]

If you are going to create database components in Oracleand DB2 for LUW, you can specify custom tablespacenames.

For Oracle, the custom tablespace names will replacethe defaults WEBMDATA and WEBMINDX.

For DB2 for LUW, the custom tablespace names willreplace the defaults WEBMDATA, WEBMINDX, andWEBMBLOB. You can also specify a custom name touse for the webMethods buffer pool (WEBMBUFF bydefault).

Note: webMethods products support all tablespaceconfigurations deployed by users.

If you are going to drop storage and revoke the databaseuser permissions for Oracle or DB2 for LUW, and youspecified custom tablespace names, provide those names.

[-t|--tablespacedir

directory]If you are going to create a database user and storage, andwant to create a tablespace directory for DB2 for LUW orOracle, provide the full path to the directory. For Oracle,use this parameter only if the DB_CREATE_FILE_DESTparameter is not set for your Oracle instance.

Note: For DB2 on Linux systems, tablespaces are created for

each DB2 database. If you are creating webMethodsdatabase components in more than one DB2 database,either the tablespace directory or the tablespace namesmust be unique for each DB2 database.

If you are going to drop storage and revoke the databaseuser permissions or DB2 for LUW or Oracle, identify thedirectory that contains the tablespaces to drop.

[-n|--dbname

database_name]If you are going to create a database user and storage inSQL Server, name of the target database.

If you are going to drop storage and revoke the database

user permissions in SQL Server, identify the database thatcontains the storage.

[-h|--help] Lists command line interface help.

[-ab|--about] Lists information about the Database ComponentConfigurator.

[-pa|--printActions] Lists the actions you can perform, like create or drop.

Parameter Entry





Examples

Important! On UNIX systems, you must enclose the RDBMS URL in your commands indouble quotes.

Create the Database User and Storage

This command creates the database user and the two tablespaces (default names) forOracle:

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 database user and the two tablespaces (custom names) forOracle:

dbConfigurator.bat -a create -d oracle -c storage -v latest


-ap adminpass -u webmuser -p w3bmpass -t tablespace_dir -tsdata MYDATA

-tsindex MYINDEX

This command creates the 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 buffer pool and tablespaces (default names), and grantspermissions for DB2:

[-pd|--printDatabase] Lists RDBMS the configurator supports.

[-pc|--

printComponents]Lists database components the configurator supports.

[-pp|--printProducts] Lists products the configurator supports.

[-pe] Lists command line interface examples.

{-e|--export}

{-dir|--configdir}

directory

{-file|--configfile}

file_name

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

{-i|--import}

{-dir|--configdir}

directory

{-file|--configfile}

file_name

Imports values for all parameters from an .xml file.

Note: Password parameters are not saved, so you must

specify them on the command.

Parameter Entry





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

This command creates the buffer pool and tablespaces (custom names), and grants

permissions for DB2:dbConfigurator.bat -a create -d db2luw -c storage -v latest


-ap admin_password -t tablespace_dir -tsdata MYDATA -tsindex MYINDEX

-tsblob MYBLOB -b MYBUFF

Drop the Storage and Revoke Database User Permissions

If you drop all database components in a schema, you can drop the storage and revokethe database user permissions.

You can use the configurator to drop the storage for Oracle, SQL Server, and DB2 forLUW. For DB2 for iSeries, you must drop the database user and storage using a script (see

“Use the Database Scripts” on page 139).

This command drops the two tablespaces (default names) for Oracle:

dbConfigurator.bat -a drop -d oracle -c storage -v latest


-ap adminpass -u webmuser -p w3bmpass -t tablespace_dir

This command drops the two tablespaces (custom names) for Oracle:

dbConfigurator.bat -a drop -d oracle -c storage -v latest


-ap adminpass -u webmuser -p w3bmpass -t tablespace_dir -tsdata MYDATA

-tsindex MYINDEX

This command drops the 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 buffer pool and tablespaces (default names), and revokespermissions for DB2:

dbConfigurator.bat -a drop -d db2luw -c storage -v latest


-ap admin_password -t tablespace_dir

This command drops the buffer pool and tablespaces (custom names), and revokespermissions 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 -tsdata MYDATA -tsindex MYINDEX

-tsblob MYBLOB -b MYBUFF


This command creates the latest version of ProcessAudit in Oracle:





dbConfigurator.bat -a create -d oracle -c processaudit -v latest

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

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 inALTSCHEMA 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=current_path,ALTSCHEMA\" -u webmuser -p w3bmpass


Before dropping, shut down all products that are connected to the database componentand back up the database component.

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

This command drops the latest ProcessAudit database component from Oracle:

dbConfigurator -a drop -d oracle -c processaudit -v latest

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

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 DB2when 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=current_path,ALTSCHEMA)” -u webmuser

-p w3bmpass





Use the Database Scripts

This section explains how to use database scripts provided by Software AG to createstorage, create a database user and grant database user permissions, drop storage and

revoke database user permissions, and create or drop database components.

Modify Storage Convention

By default, all database components follow this storage convention:

If you want to use a different storage convention when you create database components,do the following:

1 Go to the Software AG_directory\common\db\scripts directory.

2 Copy the creation scripts for your RDBMS to another directory.

3 Modify the values listed in the table above in the creation scripts.

Note: Commercial and public domain utilities provide search and replace

functionality across subdirectories. webMethods products support all tablespaceconfigurations deployed by users.

Run the Database Scripts

You run the database scripts from your database client. By default, the scripts are storedin the Software AG_directory\common\db\scripts directory. If you modified the storageconventions, the creation scripts are stored in the directory to which you copied them.

To determine which scripts to run, go to the Software AG_directory\common\ db\bindirectory 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 thecommands below, see “Use the Database Component Configurator Graphical UserInterface” on page 121 or “Database Component Configurator Command” on page 130.

Create a Database User and Storage

To list the scripts for creating a database user and storage, run this command:

RDBMS Data Storage Unit Index Storage Unit BLOB Storage Unit

Oracle tablespaces WEBMDATA WEBMINDX WEBMDATA

SQL Server filegroups Primary Primary Primary

DB2 for LUW tablespaces WEBMDATA WEBMINDX WEBMBLOB

DB2 for iSeries Default Default Default





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 databaseuser and storage.

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

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

latest


Create the proper versions of the database components for your product (see “Typical

Development Installations” on page 56).

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

dbConfigurator.{bat|sh} -a print -d {oracle|sqlserver|db2luw|db2i}

-c db_component -v db_component_version

To list the scripts for creating the database components for a certain product, run thiscommand:

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

-v product_release


Before dropping, shut down all products that are connected to the database componentand back up the database component.

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

dbConfigurator.{bat|sh} -a print -d {oracle|sqlserver|db2luw|db2i}

-c db_component -v db_component_version

To list the scripts for dropping the database components for a certain product, run thiscommand:

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





Connect Products to Database Components

This section explains how to define the following database connections, if you did notdefine them during installation, or if you want to modify the database connections you

set during installation:

From Integration Server or products it hosts to the ActiveTransfer, Archive,BusinessRules, CrossReference, DocumentHistory, ISInternal, ISCoreAudit,MediatorEvents, ProcessAudit, ProcessEngine, Reporting and Staging, andTradingNetworks and TradingNetworksArchive database components, and to theSimulation tables in the Reporting database component.

From Integration Server to the central users feature in My webMethods Server. Thisfeature allows My webMethods Server users to access Integration Server, enablesIntegration Server to delegate user management to My webMethods Server, andenables My webMethods Server's user interfaces to call Integration Server services.

For instructions on defining the database connections for other products, see thefollowing:

Important! If you used the Database Component Configurator to install databasecomponents, and you installed the Integration Server database components and theOptimize database components in two different schemas, you will have two instances ofthe Process Audit Log database component. Configure Integration Server and Optimizeto point to the same instance using the instructions below for Integration Server andinConfiguring BAM for Optimize. You can then drop the other, redundant instance.

Database Connections for Integration Server and Hosted Products

You use Integration Server Administrator to connect Integration Server to databasecomponents, as follows:

Product See

Designer Designer online help

My webMethodsServer

Administering My webMethods Server

Note: You were prompted to define this database connectionduring My webMethods Server installation.

OneData

Optimize Configuring BAM

Report Server Generating webMethods Reports

Task Engine Working with BPM Tasks: webMethods Task Engine User’s Guide





You define JDBC database connection pools in Integration Server Administrator thatIntegration Server uses to connect to database components. Each pool specifies theconnection to a database server that hosts database components.

Integration Server Administrator provides functions that correspond to most database

components (for example, IS Core Audit Log function that corresponds to theISCoreAudit database component, a Cross Reference function that corresponds to theCrossReference database component, and so on). You direct each function to write toits database components by pointing the function at the appropriate connection pool.

During Integration Server installation, if you chose an external RDBMS for theIntegration Server database components and supplied the database connectionparameters, the installer automatically did the following:

Configured Integration Server to write to the external RDBMS.

Created a default connection pool from the Integration Server database connectionparameters you supplied.

Pointed the Cross Reference, Distributed Locking, Document History, IS Internal, ISCore Audit Log, Process Audit Log, and Process Engine functions at that pool.

Note: If you created the MediatorEvents database component, you created it in thesame schema or database as the IS Core Audit Log. Integration Server thereforewrites to the MediatorEvents database component using the IS Core Audit Logfunction. Similarly, if you created the BusinessRules database component, you createdit in the same schema or database as the Process Audit Log. Integration Servertherefore writes to the BusinessRules database component using the Process AuditLog function. There is no separate function for the MediatorEvents or BusinessRulesdatabase component.

You can edit the default connection pool using the instructions in this section, or you cancreate separate pools and redirect individual functions to use them. At run time,Integration Server creates a separate instance of the appropriate connection pool for eachdatabase component.

You also use Integration Server Administrator to connect other products to databasecomponents, as follows:

During Trading Networks Server installation, you supplied the database connectionparameters for the TradingNetworks database component. The installer created aconnection pool from those parameters and pointed the Trading Networks function atthat pool. You can edit the connection using Integration Server Administrator and the

instructions below.

During ActiveTransfer Server installation, you supplied the database connectionparameters for the ActiveTransfer database component. The installer created aconnection pool from those parameters and pointed the ActiveTransfer function atthat pool. You can edit the connection using Integration Server Administrator and theinstructions below.





Integration Server can authenticate clients using internally-defined user and groupinformation, or it can use the My webMethods Server central user managementfeature. To use the latter, and to use the single sign on feature for My webMethodsServer, Integration Server must have a connection pool that points to the MywebMethods Server database component, and the CentralUsers function inIntegration Server must point at that connection pool.

If you installed My webMethods Server in the same directory as Integration Server,the installer created a connection pool from the My webMethods Server databaseparameters you supplied and pointed the CentralUsers function at that pool. If youinstalled My webMethods Server in a different directory from Integration Server, youmust create the connection pool and point the CentralUsers function at that poolusing Integration Server Administrator and the instructions below.

If you created the Archive and Reporting and Staging database components, youmust point those functions at connection pools. If you want to simulate businessprocesses in Designer using historical data, you must point the Simulation function at

the connection pool for the Reporting database component.

Define an Integration Server Connection Pool

1 Start Integration Server and open Integration Server Administrator.

2 Go to the Settings > JDBC Pools page.

3 On the Settings > JDBC Pools page, click Create a new Pool Alias Definition and completethe fields as follows:

Field Entry

Al ias Name Name for the connection pool. The name can include anycharacters that are valid for a file name in your operating system.

Al ias

Description

Description for the pool.

Associated

Driver Alias

Database driver to use.





Database URL URL for the database server. Sample URL formats for theDataDirect Connect JDBC 4.2 driver are displayed.

Important! Use the DataDirect Connect connection optionMaxPooledStatements=35 on all database URLs except those forTrading Networks. This connection option improves performance by caching prepared statements. (Trading Networks caches itsprepared statements using its own pooling mechanism).

Important! For DB2, if Integration Server will connect to a schemaother than the default schema for the specified database user, youmust specify these connection options in the URL:


PATH=current_path,schema)”;MaxPooledStatements=35

AlternateID is the name of the default schema that is used toqualify unqualified database objects in dynamically prepared SQLstatements.

User Id Database user for Integration Server to use to communicate withthe database.

Password Password for the database user.

Minimum

connections

Minimum number of connections the pool must keep open at alltimes.

If you use this pool alias for more than one function, each poolinstance keeps the specified number of connections open. Forexample, if you specify keeping at least 3 connections open, andthe IS Core Audit Log and the Document History databasecomponents both use this pool, the pool keeps a total of 6connections open - 3 for the IS Core Audit Log pool instance and 3for the Document History pool instance.

If your logging volume has sudden spikes, you can improveperformance by making sure the connections needed to handle theincreased volume open quickly. You can minimize connectionstartup time during spikes by setting this value higher, so that

more connections remain open at all times.

Field Entry





8 Restart Integration Server.

Drop Redundant Database Component

If you used the Database Component Configurator to install database components, andyou installed the Integration Server database components and the Optimize databasecomponents in two different schemas, you will have two instances of the Process AuditLog database component. Configure Integration Server and Optimize to point to thesame instance using the instructions above for Integration Server and in Configuring BAM for Optimize. You can then drop the other, redundant instance.




A International Operating Environments

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Extended Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Configure Browsers and JDK Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Configure the Proper Locale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149





Overview

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

The products use the Universal Character Set (ISO/IEC 10646-2, or Unicode) as thecharacter set for all internal operations. At minimum, the products support therequirements of Unicode 3.0. HTML content, including administration tools, usesUnicode UTF-8 encoding.

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

Language Packs

Language packs are available for webMethods Broker on all supported operatingsystems. Language packs are available for other Software AG products on all supportedoperating systems except IBM i5/OS and Mac OS X.

The Software AG Installer always installs the U.S. English files necessary to run yourproducts. However, for many products, you can also install language packs that providetranslated user interfaces, messages, help, and documentation.

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

U.S. English.

Eclipse Language Packs

Designer is based on the Eclipse platform and its projects. Software AG’s language packsdo not include language packs for plug-ins provided by Eclipse projects. If you needlanguage packs for those plug-ins, follow these steps:

1 Start Designer.

2 Go to Help > Software Updates , click the Avai lab le So ftware tab, and then click Add Si te.

3 In the Location field, type http://download.eclipse.org/technology/babel/update-

site/R0.8.0/helios and click OK.

4 Click Refresh , select the language pack for the language you need, and click Install.Confirm the language pack to install and click Next.

5 Read the license agreement. If you accept the terms, select the check box and clickFinish.

6 Restart Eclipse.





Extended Character Set

The Software AG 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 usecustom character encodings such as EBCDIC and OEM character encodings withIntegration Server, adapters, and services.

Configure Browsers and JDK Font

Some HTML interfaces for Software AG products detect the language setting for your browser. If you have installed language packs on your products, those interfaces try tosupply the user interface, messages, and data in that language. You can indicate which ofthe installed languages to display in your browser as follows:

Your Java run-time environment might require modification to display non-ASCII data. Ifyou see hollow boxes or black squares where you would expect to see non-ASCIIcharacters, you might need to modify your JDK's font configuration file to provide anappropriate 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 particularlanguage. For information on modifying font configuration file, see J2SE 6.0 at the Oracle Java SE Documentation Web site.

Configure the Proper Locale

If you are going to install or run your products in a locale other than U.S. English, followthe instructions below.

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

Browser Action

Firefox 3.x Go to Tools > Options > Content , click Choose , and add the languageyou want to use to the top of the list.

Internet Explorer7.x and 8.x

Go to Tools > Internet Options , click Languages , and add the languageyou want to use to the top of the list.

http://download.oracle.com/javase/6/docs/technotes/guides/intl/fontconfig.html








System Action

Windows Set the Windows system locale to the proper locale, as follows:

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

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

3 Restart Windows.

UNIX Set your shell to the proper locale by setting the LANG environmentvariable. Run the appropriate command below:

In an sh shell: LANG=locale; export LANG

In a csh shell: setenv LANG locale




B Default Ports

Product Description

Default

Port Protocol

ActiveTransfer Default port for handling server and userlogs in the ActiveTransfer user interface.

2080 HTTP

ApplinXServer

Ports for communication with Designer,ApplinX Java and .NET frameworks- based objects, and ApplinX Java and .NETprocedure clients for SOA.

2323

23443*

TCP

Secured TCP

HTTP server port for communicationwith clients

2380 HTTP

Internal Administration port 2305 TCP

Internal AJP port 2309 AJP/1.3

webMethodsBroker

Broker Server ports 6849,6848†,6847‡

TCP

Default Broker port 6849 TCP

Broker Monitor port 6850 TCP

CentraSiteRegistryRepository

Applications port 53301 TCPAdministration port 53303 TCP

RMI Registry port 53313 Standard RMI

Remote Authenticator port forauthenticating remote users via SSX

53314 RMI over SSL

Remote Repository Manager port foraccessing repository data via SSX

53315 RMI over SSL

CentraSite HTTP server port (Apache) 53305 HTTP

Application

Server Tier

Web applications port (Tomcat) 53307

53308

HTTP

HTTPS

Communicate Communicate Server ports forcommunication with the Communicatepackage on Integration Server

5020

5021

TCP

Secured TCP

Internal proxy port 5022 TCP



B Default Ports


ContentServicePlatform

Port for transporting service requests andresponses between the Content ServicePlatform and its clients (Designer, ProcessEngine, and Task Engine)

9010 TCP

Port for uploading files to the ContentService Platform from Task Engine, andfor downloading files from ContentService Platform to Task Engine

9011 TCP

Port for returning dynamic reports orvirtual objects to clients

9015

9016

HTTPS

HTTP

Port for managing and monitoring JMX

server

9019 TCP

EntireX Default Broker port

Note: If these default values are notavailable, EntireX uses other values.

1971 TCP

Default Broker SSL port 1958 TCP

Broker agent administration port 3000 TCP

Broker administration service port 57707,57708**

TCP

Event Server Primary port 7867 TCPIntegratedAuthenticationFramework

Port for start up and shut down fromSystem Management Hub

11971 TCP

Data port for communication with otherproducts

11953 SSL

IntegrationServer

Primary port 5555 HTTP

Diagnostics port 9999 HTTP

Data port for communication amongclustered Integration Servers usingCoherence

24547 TCP

MashZone Tomcat communication port 16360 HTTP

Tomcat shutdown port 16366 TCP

Product Description

Default

Port Protocol




B Default Ports

MywebMethodsServer

Java debugger port (available when MywebMethods Server is started with -doption)

5000 TCP

Jetty HTTP Web server port (forcommunication between products andtheir user interfaces on My webMethodsServer, and for users and clients to callWeb services)

8585 HTTP

Communication with CentralConfiguration

15002 HTTP

OneData Applications port 9090

9091

HTTP

HTTPSPorts for communicating with the RMIserver

9092-9094

RMI

Data port for communication amongclustered OneData servers usingCoherence

9095 UDP

Optimize Central Configuration 16000-16025

HTTP

AnalyticEngine

Central Configuration port 15000 HTTP/HTTPS

Internal Web service registry port 12503 HTTP

Data port for communication amongclustered Analytic Engines

30999 TCP

PredictionEngine



ApplicationMonitoringData Collector

Data collector port to which productsshould send monitoring data.

57900 TCP

Port to use to start and stop the datacollector. 57901 TCP

Web ServiceData Collector



InfrastructureData Collector


Product Description

Default

Port Protocol



B Default Ports

Primary port 6666 HTTP

Report Server Primary port 9300 HTTPSystemManagementHub

Communication with CentraSite Controland all other user interface plug-ins toSystem Management Hub

10010 HTTP

CSLayer ports 10016

10012,10015

SNMP

TCP

EventLayer ports 10017

10014

SNMP

TCP

MiLayer port 10010

10018

10013

10019

10013

HTTP

HTTPS

SNMP

SNMP over TCP

TCP

Tomcat Server Shutdown port.

Product Description

Default

Port Protocol