web methods installation guide 6 5 and 6 5 1

webMethodsInstallation Guide

VERSION 6.5 AND 6.5.1

webMethods, Inc.South Tower3877 Fairfax Ridge RoadFairfax, VA 22030USA703.460.2500http://www.webmethods.com

webMethods Access, webMethods Administrator, webMethods Broker, webMethods Dashboard, webMethods Developer, webMethods Fabric, webMethods Glue, webMethods Installer, webMethods Integration Server, webMethods Mainframe, webMethods Manager, webMethods Modeler, webMethods Monitor, webMethods Optimize, webMethods Portal, webMethods Servicenet, webMethods Trading Networks, and webMethods Workflow are trademarks of webMethods, Inc. webMethods and the webMethods logo are registered trademarks of webMethods, Inc.

Acrobat and Adobe are registered trademarks, and Reader is a trademark of Adobe Systems Incorporated. Amdocs is a registered trademark, and ClarifyCRM is a trademark of Amdocs. Ariba is a registered trademark of Ariba, Inc. BEA, BEA WebLogic Server, Jolt, and Tuxedo are registered trademarks, and BEA WebLogic Platform is a trademark of BEA Systems, Inc. Action Request System, BMC Software, PATROL, and Remedy are registered trademarks of BMC Software, Inc. BroadVision is a registered trademark of BroadVision, Inc. ChemeStandards and CIDX are trademarks of Chemical Industry Data Exchange. Unicenter is a registered trademark of Computer Associates International, Inc. PopChart is a registered trademark of CORDA Technologies, Inc. Kenan and Arbor are registered trademarks of CSG Systems, Inc. Data Connection and SNAP‐IX are registered trademarks of Data Connection Corporation. DataDirect, DataDirect Connect, and SequeLink are registered trademarks of DataDirect Technologies. D&B and D‐U‐N‐S are registered trademarks of Dun & Bradstreet Corporation. Entrust is a registered trademark of Entrust, Inc. papiNet is a registered trademark of the European Union and the United States. Financial Information eXchange, F.I.X, and F.I.X Protocol are trademarks of FIX Protocol Ltd. UCCnet and eBusinessReady are registered trademarks, and 1SYNC and Transora are trademarks of GS1 US. Hewlett‐Packard, HP, HP‐UX, OpenView, PA‐RISC, and SNAplus2 are trademarks of Hewlett‐Packard Company. i2 is a registered trademark of i2 Technologies, Inc. AIX, AS/400, CICS, DB2, Domino, IBM, Informix, Infoprint, Lotus, Lotus Notes, MQSeries, OS/390, OS/400, RACF, RS/6000, SQL/400, S/390, System/390, VTAM, z/OS, and WebSphere are registered trademarks; and Communications System for Windows NT, DB2 Universal Database, IMS, MVS, and SQL/DS are trademarks of IBM Corporation. InnoDB is a trademark of Innobase Oy. Itanium is a registered trademark of Intel Corporation. JBoss is a registered trademark, and JBoss Group is a trademark of Jboss, Inc. Linux is a registered trademark of Linus Torvalds. W3C is a registered trademark, and X Window System is a trademark of the Massachusetts Institute of Technology. MetaSolv is a registered trademark of Metasolv Software, Inc. ActiveX, Microsoft, Outlook, Visual Basic, Windows, and Windows NT are registered trademarks; and Windows Server is a trademark of Microsoft Corporation. Six Sigma is a registered trademark of Motorola, Inc. Firefox is a registered trademark, and Mozilla is a trademark of the Mozilla Foundation. MySQL is a registered trademark of MySQL AB. nCipher is a trademark of nCipher Corporation Ltd. Teradata is a registered trademark of NCR International, Inc. Netscape is a registered trademark of Netscape Communications Corporation. SUSE is a registered trademark of Novell, Inc. ServletExec is a registered trademark, and New Atlanta is a trademark of New Atlanta Communications, LLC. CORBA is a registered trademark of Object Management Group, Inc. JD Edwards, OneWorld, Oracle, PeopleSoft, Siebel, and Vantive are registered trademarks, and PeopleSoft Pure Internet Architecture and WorldSoftware are trademarks of Oracle Corporation. Infranet and Portal are trademarks of Portal Software, Inc. Red Hat is a registered trademark of Red Hat, Inc. PIP and RosettaNet are trademarks of RosettaNet, a non‐profit organization. SAP and R/3 are registered trademarks of SAP AG. SWIFT and SWIFTNet are registered trademarks of Society for Worldwide Interbank Financial Telecommunication SCRL. SPARC and SPARCStation are registered trademarks of SPARC International, Inc. SSA is a registered trademark, and Baan and SSA Global are trademarks of SSA Global Technologies, Inc. EJB, Enterprise JavaBeans, Java, JavaServer, JDBC, JSP, J2EE, Solaris, Sun, and Sun Microsystems are registered trademarks; and Java Naming and Directory Interface, SOAP with Attachments API for Java, JavaServer Pages, and SunSoft are trademarks of Sun Microsystems, Inc. Sybase is a registered trademark of Sybase, Inc. VERITAS is a registered trademark, and VERITAS Cluster Server is a trademark of Symantec Corporation. UNIX is a registered trademark of The Open Group. Unicode is a trademark of Unicode, Inc. VeriSign is a registered trademark of Verisign, Inc.

All other marks are the property of their respective owners.

Copyright © 2005‐2006 by webMethods, Inc. All rights reserved, including the right of reproduction in whole or in part in any form.

Document ID: WEBM-IG-65-20060811

Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Part I. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 1. Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Access or Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22EDI Module and EDIINT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23webMethods Mainframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Manager and Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Development Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Production Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Servicenet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Trading Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Location of Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Example Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 2. Software and Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . 37Product Software Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Supported Operating Systems and Required JREs/JDKs and Browsers . . . . . . . . . . . . . . . . . . 38SNA Communications Server for webMethods Mainframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Servlet Engine and Limitations for Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Product Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Standard Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

webMethods Installation Guide Version 6.5 and 6.5.1 3

C o n t e n t s

Database Component Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Supported RDBMSs and Database Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Hardware Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44RDBMS Page and Block Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44RDBMS Character Set and Sort Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Use of SYS or SYSTEM User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 3. Support for International Operating Environments . . . . . . . . . . . . . . . . . . . . . . 49Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Character Encodings and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Part II. Simple Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 4. Simple Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Part III. Advanced Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 5. Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Prepare for Installation on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Prepare the Machine on Which to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Prepare to Install the Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Prepare to Install Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Prepare for Installation on a UNIX, Linux, OS/400, or Mac OS X System . . . . . . . . . . . . . . . . . . . . . 67Prepare for Install on a Remote Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Prepare the Machine on Which to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Prepare to Install webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Prepare to Install the Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Prepare to Install Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Log In as as Root or Non-Root User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

4 webMethods Installation Guide Version 6.5 and 6.5.1

Use a Proxy Server, Installation Script or Image, Custom Server, or 64-Bit JDK . . . . . . . . . . . . . . . . 70Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Installation Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Download webMethods Products from Your Own Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Install a 64-bit JDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Combinations of Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 6. Advanced Installation Using the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Start the Installer on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Use Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Create, Install from, or Edit an Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Create or Install from an Installation Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Use Proxy Server or Your Own Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Install a 64-Bit JDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

How to Use the Installer Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Finding Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Complete Product Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configure webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Configure Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Configure Manager, Optimize, or Both . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Configure Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Configure Servicenet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Configure Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Configure Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Overwrite Using the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103


C o n t e n t s

Chapter 7. Advanced Installation Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Install in Console Silent Mode on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Install Using Console Mode on a UNIX, Linux, OS/400, or Mac OS X System . . . . . . . . . . . . . . . . . . 107

Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Overwrite Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Part IV. Database Component Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Chapter 8. Installing the Database Components in Oracle . . . . . . . . . . . . . . . . . . . . . . . . . 129Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking

Store, Reporting, Staging, and Trading Networks Database Components . . . . . . . . . . . . . . . . . . . 130Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Set the Database Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Create the Tablespaces in Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Install the My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Create the Tablespace and Database User and Install the Database Component . . . . . . . . . . . 139Install the Database Component Using an Existing Tablespace and Database User . . . . . . . . . 140

Reinstall the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141


Chapter 9. Installing the Database Components in SQL Server . . . . . . . . . . . . . . . . . . . . 143Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository,

Process Tracking Store, Reporting, Staging, and Trading Networks Database Components . . . . 144Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Set the Database Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Install the My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Create the Database and Database User and Install the Database Component . . . . . . . . . . . . 150Install the Database Component Using an Existing Database and Database User . . . . . . . . . . 151

Reinstall the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Chapter 10. Installing the Database Components in DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . 153Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository,


Install the Reporting and Staging Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Set the Database Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Install the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Set the Database Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160


C o n t e n t s

Chapter 11. Installing the Database Components in Sybase . . . . . . . . . . . . . . . . . . . . . . . . 163Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository,


Install the Archive, Process Audit Log, Reporting, and Staging Database Components . . . . . . . . . . 166Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Set the Database Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Chapter 12. Identifying Databases for Use by Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Identify the Databases that Contain the Cross-Reference, Document History, IS Core Audit Log,

Process Audit Log, Reporting, and Staging Database Components . . . . . . . . . . . . . . . . . . . . . . . . 170Define a Connection Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Link a Function to a Connection Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Configure Integration Server to Write Cross-Reference, IS Core Audit Log, and

Process Audit Log Data to a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Identify the Database for the Process Tracking Store Database Component . . . . . . . . . . . . . . . . . . . 175Identify the Database for the Modeler Repository Database Component . . . . . . . . . . . . . . . . . . . . . . 177

Part V. Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Chapter 13. Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Configure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Complete the Access, My webMethods Server, or Portal Installation . . . . . . . . . . . . . . . . . . . . . . . . . 183

Configure the Server and Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Install the Portlet Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Complete the webMethods Broker Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Make Sure the Broker Server is Running and the Default Broker Exists . . . . . . . . . . . . . . . . . . 189Adjust Per-Process Thread Limit and Set Per-Process and Kernel Limit on HP-UX Systems . . 190Set Locale on UNIX or Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Enable Full Core Dumps on AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Complete the Deployer Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Apply Fixes for Modeler 6.1.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Install JCE Unlimited Strength Jurisdiction Policy Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191


Complete the Integration Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Direct Integration Server to Compiler to Use for Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Configure Integration Server to Use a 64-Bit JVM on Solaris and HP-UX Systems . . . . . . . . . . 192Install JCE Unlimited Strength Jurisdiction Policy Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Increase File Descriptors on UNIX, Linux, OS/400, and Mac OS X Systems . . . . . . . . . . . . . . . 193Change Permissions on UNIX, Linux, OS/400, and Mac OS X Systems . . . . . . . . . . . . . . . . . . 193Prevent Memory Problems on OS/400 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Streamline Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Complete the Installation for Manager, Optimize, or Both . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Create the Manager/Optimize User and Enable Automatic Start and Shut Down on UNIX

or Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Complete the Modeler Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Make Sure Modeler Design Package and PRT are Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Give Users Proper Permissions on Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Define Logical Servers and Map to Integration Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Complete the Monitor Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Set Up Authentication to Run Monitor Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Install the SVG Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Complete the Servicenet Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Set Up the Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Configure Registry Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Change the Default Registry Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Configure Servicenet Components to Communicate with My webMethods Server . . . . . . . . . . 211

Complete the Workflow Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Set Up the Workflow Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Set Up Secondary Workflow Servers to Access Encryption Passwords . . . . . . . . . . . . . . . . . . . 213Set Up Workflow Servers for Automatic Startup on Solaris, HP-UX, AIX, and Linux Systems . . 213Set Up Workflow Servers for Automatic or Manual Startup on Windows Machines . . . . . . . . . . 213Enable a Workflow Server on a Red Hat Linux System to Use an SSL-Enabled Broker . . . . . . 214Configure Workflow Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Configure Workflow to Use SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Connect Products to Each Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Connect My webMethods Server to Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Connect Integration Server to the Default Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Redirect Products to Use a Non-Default JRE or JDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Complete the Installation for Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234


C o n t e n t s

Part VI. Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Chapter 14. Uninstalling Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Uninstall on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Uninstall on a UNIX, Linux, OS/400, or Mac OS X System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Complete the Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Complete the Deployer Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Complete the webMethods Mainframe Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Complete the Modeler Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Chapter 15. Dropping Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Drop Database Components from Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Drop the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, and Trading Networks Database Component . . . . . . . . . . . . . . . . . 244

Drop the Analysis, Archive, Process Tracker, and Servicenet Database Components . . . . . . . 244Drop the My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Drop Database Components from SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Drop the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository,

Process Tracking Store, and Trading Networks Database Components . . . . . . . . . . . . . . . . 246Drop the Manager Server and Process Audit Log Database Components . . . . . . . . . . . . . . . . . 246Drop the Analysis, Archive, Process Tracker, and Servicenet Database Component . . . . . . . . 247Drop the My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Drop Database Components from DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Drop the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository,

Process Tracking Store, and Trading Networks Database Components . . . . . . . . . . . . . . . . 248Drop the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker

Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Drop the Database Components from Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Drop the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, and Trading Networks Database Components . . . . . . . . . . . . . . . . 250

Drop the Archive and Process Audit Log Database Components . . . . . . . . . . . . . . . . . . . . . . . . 250

Appendix A. Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

Appendix B. Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Monitor Service pub.monitor.archive:setOperationParameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264


Appendix C. Create the Broker Server Configuration Manually . . . . . . . . . . . . . . . . . . . . . 267Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Create the Broker Server Data Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Create the Data Directory on UNIX or Linux Systems as Non-Root User . . . . . . . . . . . . . . . . . . 268Create the Data Directory on a UNIX or Linux Systems as Root User . . . . . . . . . . . . . . . . . . . . 270Create the Data Directory on Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

Set Up Broker Monitor on UNIX or Linux Systems (Non-Root User) . . . . . . . . . . . . . . . . . . . . . . . . . 270Run as Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270Run as Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Create the Broker Server on Any System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Create Separate Storage Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Create a Combined Storage Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Create the Default Broker on Any System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Enable the Broker Server to Log Events to the UNIX or Linux System Log . . . . . . . . . . . . . . . . . . . . 279Adjust Per-Process and Kernel Limits on HP-UX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Set Locale on UNIX or Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Enable Full Core Dumps on AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281


C o n t e n t s


About This Guide

About This Guide

This guide is for users who are installing or uninstalling these webMethods products:

If you must perform certain configuration tasks before you start a webMethods product, this guide explains those configuration tasks. The documentation for each webMethods product explains how to start the product and how to perform configuration tasks after the product is started.

Product Version

webMethods Access 6.5.1

webMethods Administrator 6.5

Note: webMethods Administrator has been deprecated. It will no longer be available after this release.

webMethods Broker 6.5

webMethods Deployer 6.5

webMethods Developer 6.5

webMethods EDI Module and webMethods EDIINT Module 6.5

webMethods Integration Server 6.5

webMethods Mainframe 6.5

webMethods Manager 6.5.1 SP1

webMethods Modeler 6.5.1

webMethods Monitor 6.5.1 SP1

My webMethods Server 6.5.1

webMethods Optimize 6.5.1 SP1

webMethods Portal 6.5.1

webMethods Servicenet 6.5.1

webMethods Trading Networks 6.5

webMethods Workflow 6.5.1


For system requirements, JVM considerations, and instructions on installing and uninstalling webMethods products that are not listed above, see the documentation for those products.

Document Convent ions

Important! Information in this guide might have been updated since you last downloaded it. Go to the webMethods Advantage Web site at http://advantage.webmethods.com for the latest version of the guide.

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

Note: Typically, to install webMethods products, you download the webMethods Installer and the files for each product from the webMethods Advantage Web site. The Web site, at http://advantage.webmethods.com, is a secure Web site accessed through the Internet. If you are unable to download software, webMethods Customer Operations can provide the webMethods products you have licensed on a CD or through a private FTP site. Contact webMethods Customer Operations at [email protected].

Convention Description

Bold Identifies elements on a screen.

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

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

Typewriter font

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

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

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

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


http://advantage.webmethods.com


Additional Information

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

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

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

Additional Documentation. All webMethods documentation is available on the webMethods Bookshelf.



http://advantage.webmethods.com/cgi-bin/advantage/main.jsp?w=0&s=3232716887&targChanId=-536883032&all=1

http://advantage.webmethods.com/cgi-bin/advantage/main.jsp?w=0&s=3232716999&targChanId=-536883238



P A R T I
Requirements
Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Software and Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Support for International Operating Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49


C H A P T E R 1
Planning Your Instal lat ion
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Access or Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

EDI Module and EDIINT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

webMethods Mainframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Manager and Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Servicenet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Trading Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Location of Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Example Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36


C H A P T E R 1 P l a n n i n g Yo u r I n s t a l l a t i o n

OverviewThis chapter explains where to install webMethods products. The chapter also explains how to install webMethods database components. A database component is a grouping of database objects deployed as one or more database SQL scripts. Some database components are used by more than one product. For full descriptions of the data that the products write to each database component, see Appendix B, “Database Components”.

Some webMethods products depend on having other webMethods products installed on the same machine. The tables in the sections below list those products under Products Required on Same Machine as product. Most webMethods products require other webMethods products, database components, and lower‐level items to be installed on one or more machines in the network in order to operate fully. The tables below list those products as product Requirements for Full Operation.

webMethods products sometimes require additional lower‐level items to communicate with other webMethods products, and can use other lower‐level items to perform optional tasks. The tables below list those items under If you want to install.... If not otherwise stated in the table, install the items on the same machine as the product.

For help determining the best installation of webMethods products for your organization, consult webMethods Professional Services.

Access or PortalInstall Access or Portal on My webMethods Server. Install My webMethods Server database component.

If your system administrator is going to create clustered Access or Portal servers, install webMethods Broker on a machine to which all the clustered servers have network access, and install the JMS Client API on each machine that hosts one of the clustered servers.

If you want to develop portlets for use in Access or Portal, install the Portlet Developer, which is an Eclipse plug‐in. For instructions, see the webMethods Portal Design Guide.

Products Required on Same Machine as Access or Portal Access or Portal Requirements for Full Operation

My webMethods Server 6.5.1 When clustering, webMethods Broker 6.5 SP1, Broker Client Java API 6.5 SP1, and JMS Provider 6.5 SP1

Portlet Developer 6.5

My webMethods Server database component

Access or Portal

My webMethods Server My webMethods Server


Administrator

AdministratorInstall Administrator and Integration Server on a machine on the same network as the other webMethods products.

webMethods BrokerInstall webMethods Broker on a machine on the same network as other webMethods products. Install Integration Server, Broker Administrator, and JMS Administrator on another machine on the network.

When you install webMethods Broker, you actually install a Broker Server and a default Broker. The Broker Server manages the flow of documents and

communication among Brokers, Broker clients, JMS clients, and various applications. Brokers are the software to which Broker clients and JMS clients connect.

If you want to... Install this item...

Develop portlets SDK

Manage ADAM users and groups ADAM

Manage LDAP users and groups LDAP Browser

Monitor clustered Portal servers Remote Portal Log Viewer

Work with Web services clients and portlets

TCP Tunnel Monitor

Integration Server

Administrator

Note: Administrator has been deprecated. It will no longer be available after this release.

webMethods Broker

Integration Server

Logging Utility

Broker AdministratorJMS Administrator

Monitor

My webMethods Server

Monitor interface


IS Core Audit Log



You can log documents for Broker and JMS clients. To do so, you must install the following:

Install the Logging Utility on an Integration Server in the same network as the clients and the Broker to which the clients connect and install the IS Core Audit Log database component. The Logging Utility gets the client documents from the Brokers and passes them to Integration Server, which writes the documents to the IS Core Audit Log database component.

Install Integration Server and the Monitor run time on another machine on the network, install My webMethods Server and the Monitor user interface on another machine, and install the My webMethods Server database component. The Monitor run time reads from the IS Core Audit Log database component and sends the data to the Monitor user interface to display.

Products Required on Same Machine as webMethods Broker

webMethods Broker Requirements for Full Operation

None Integration Server 6.5, Broker Administra‐tor 6.5, JMS Administrator 6.5, Logging Utility 6.5, Monitor run time 6.5.1

My webMethods Server 6.5.1, Monitor user interface 6.5.1

IS Core Audit Log, My webMethods Server database components


Configure or retrieve information about local or remote Brokers and JMS adminis‐tered objects

Command Line Tools

Develop and run custom C messaging applications that interact with your Broker

Broker Client C API*

Develop and run custom Java messaging applications that interact with your Broker

Broker Client Java API*

*Install on the machines on which the custom clients will be developed and run.


Deployer

DeployerDeployer is a tool you use to deploy items that reside on source webMethods servers to target webMethods servers. For example, you might want to deploy items you have developed on servers in a development environment to servers in a test or production environment. Source and target servers can include Brokers, Integration Servers, Modeler Design servers (Integration Servers equipped with the Modeler Design Package), Monitor servers (Integration Servers equipped with Monitor), Portal servers, and Workflow Servers.

If no firewall separates the source and target environments, install Deployer and Integration Server on a machine that can access all source and target servers. If a firewall separates the environments, install Deployer and Integration Server on a machine in the source environment that can access all source servers and in the target environment on a machine that can access all target servers.

Develop and run custom JMS messaging applications that interact with your Bro‐ker

JMS Client API*

Run sample messaging applications with your Broker using APIs for different pro‐gramming languages

Samples*


*Install on the machines on which the custom clients will be developed and run.

Products Required on Same Machine as Deployer Deployer Requirements for Full Operation

Integration Server 6.x Deployer can deploy from and to:

Broker Servers 6.x through 6.5

Integration Server 6.x through 6.5

Modeler 6.0.1 through 6.2

Portal 6.1.5 through 6.5

Trading Networks Server 6.x through 6.5

Workflow Server 6.1.5

Integration Server Deployer



DeveloperIf Integration Server and Developer are the only webMethods products you are going to install, you can install the two products on the same machine. If you are also going to install other webMethods products such as Trading Networks, install

Integration Server and Developer on different machines on the same network.

EDI Module and EDI INT ModuleInstall the EDI Module, the EDIINT Module, Integration Server, and Trading Networks Server on one machine. Install Developer and Trading Networks Console on another machine on the same network.

Products Required on Same Machine as Developer Developer Requirements for Full Operation

None Integration Server 6.1 or 6.5


Develop C/C++ services or applications that need to interact with Integration Server using C/C++ rather than Java

Create clients with C/C++ code generation and rebuild the Integration Server shared libraries that support C/C++ clients and services so you can compile the clients using JDK 1.4.x

C/C++ SDK

Generate services from an existing .NET assembly

Plug‐in for Microsoft .NET

Browse services in Servicenet Servicenet Client API

Developer

Products Required on Same Machine as EDI Module EDI Module Requirements for Full Operation

Integration Server 6.5

Trading Networks Server 6.5

Developer 6.5

Trading Networks Console 6.5

EDI Module andEDIINT Module

Integration ServerDeveloper

Trading Networks

Server

Trading Networks Console


Integration Server

Integrat ion ServerIf Integration Server and Developer are the only webMethods products you are going to install, you can install the two products on the same machine. If you are also going to install other webMethods products such as Trading Networks, install

Integration Server and Developer on different machines on the same network.

If you are going to create publish‐subscribe solutions that span multiple Integration Servers, install webMethods Broker on a separate machine to serve as the communication link for the Integration Servers.

If you are logging documents, using Monitor, or storing process data in the Process Audit Log database component, install the IS Core Audit Log database component. If your triggers use Document History option for exactly once processing, install the Document History database component.

Integration Server can also use these database components:

Cross‐Referencing database component (information required to synchronize updates among various webMethods products and their database components; optional because data is written to flat file by default)

IS Core Audit Log database component (optional because error, guaranteed delivery, service, and session data is written to flat file by default, but required in some cases, such as when you use the Process Audit Log database component; see “Location of Database Components” on page 34 for complete information)

Repository database component (recommended when clustering Integration Servers)

Products Required on Same Machine as EDIINT Module EDIINT Module Requirements for Full Operation

Integration Server 6.5

Trading Networks Server 6.5

Developer 6.5

Trading Networks Console 6.5

If sending EDI documents to Trading Net‐works Server for processing, EDI Module 6.5

Integration Server IS Core Audit Log,Document History



Products Required on Same Machine as Integration Server

Integration Server Requirements for Full Operation

None webMethods Broker 6.5

Developer 6.5

IS Core Audit Log, Document History database components


Allow portlets running inside My web‐Methods Server to use My webMethods Server users to call Integration Server services.

Common Authorization Package

Develop C/C++ services or applications that need to interact with Integration Server using C/C++ rather than Java

Create clients with C/C++ code generation and rebuild the Integration Server shared libraries that support C/C++ clients and services so you can compile the clients using a JDK 1.2.2 or 1.3 compiler

C/C++ SDK

Use extended character set encoding support for Integration Server, adapters, and services.

Extended Character Set Encoding Support

Access the .NET environment from Integra‐tion Server

Microsoft Package

Store Integration Server keys and certificates securely

PKI Support


webMethods Mainframe

webMethods MainframeInstall webMethods Mainframe, webMethods Integration Server‐webMethods Mainframe Package (Mainframe Package), and Integration Server on one machine. If webMethods Mainframe is communicating with a mainframe over an SNA network, the machine must be the one that hosts the SNA communications server. Install the webMethods Mainframe Developer Plug‐in (Mainframe Plug‐in) and Developer on another machine on the same network.

Store and track scheduled jobs, session con‐text, and jobs tracked by guaranteed delivery for clustered Integration Servers

Repository Server

Note: You can but do not have to install this item on an Integration Server host machine.

Use for prototyping, design, or temporary database access

Important! For enterprise, mission‐critical applications, use the webMethods JDBC Adapter. For more information about when to use the WmDB package and when to use the JDBC Adapter, see the WmDB User’s Guide. The WmDB package does not support Sybase 12.5.3 databases.

WmDB


Products Required on Same Machine as webMethods Mainframe

webMethods Mainframe Requirements for Full Operation

None Developer 6.5, Mainframe Plug‐in 6.5

Integration Server 6.5, Mainframe Package 6.5

Developer


Mainframe Package

Mainframe Plug-inIntegration Server



Manager and OptimizeInstall the controller on a machine on the same network as the other webMethods products. If you install both Manager and Optimize, create a single controller that offers full functionality for both products by installing the

controller for each product on the same machine. Because the controller makes intensive use of its host machine, webMethods recommends that you dedicate an entire machine to running it. The controller host machine must have access to the data handler host machine and to all satellite host machines.

Install the data handler on a machine on the same network as the other webMethods products. The data handler is identical for Manager and Optimize; if you install both products, you can install the data handler from either product. The data handler host machine must have access to the controller host machine and to all satellite host machines.

Install satellites on enough machines to handle the load of gathering data from your environment. Typically, to reduce the burden on your network, you install satellites on or near each machine that hosts a process or application you want Manager or Optimize to monitor. If you want to monitor processes and applications on a remote host machine to which you have no physical access (for example, a machine in another country), you can also install satellites on the controller host machine. The satellites are identical for Manager and Optimize; if you install both products, you can install the satellites from either product.

Install the Manager and Optimize user interfaces on My webMethods Server.

Install the Analysis, My webMethods Server, Process Audit Log, and Process Tracker database components.


Create and modify webMethods Mainframe host connection pools and transactions

Mainframe Plug‐in

Note: Install on the Developer host machine.

Enable communication between web‐Methods Mainframe and Integration Server or Developer

Mainframe Package

Note: Install on the Integration Server/webMethods Mainframe host machine.

Manager server


Manager/ Optimize interface


Analysis, Process Audit Log,

Process TrackerManager/Optimize

controller/data handler

Manager Server


Manager and Optimize

In a production environment, webMethods recommends that you install the Manager server on a dedicated machine on which no other webMethods products are running. If necessary, however, the Manager server can share a machine with other products. Install the Manager Server database component.

Products Required on Same Machine as Manager or Optimize

Manager or Optimize Requirements for Full Operation

None My webMethods Server 6.5.1, Manager or Optimize user interface 6.5.1

Analysis, My webMethods Server, Process Audit Log, Process Tracker database compo‐nents

Important! The Manager server is bundled with its own Integration Server. The Integration Server is devoted entirely to use by the Manager server. Do not install any other packages on the Integration Server.

Products Required on Same Machine as Manager Server Manager Server Requirements for Full Operation

None Manager Server database component

Manager Server can manage:

Broker Servers 5.0.1 through 6.5

Integration Servers 4.6 through 6.5

webMethods Mainframe 6.5

Trading Networks Server 4.6 to 6.5

Workflow Server 6.1.5 through 6.5.1



Modeler

Development EnvironmentYou can install Modeler by itself on a machine and create process models. When you want to share the process models with other users, connect the Modeler machine to your network and install the Modeler Design Package, the Process Run Time (PRT), and Integration Server on another machine on the network. If your process models include steps that will call Integration Server flow services or Workflow processes, install Developer and the Workflow client on the same machine and in the same webMethods installation as Modeler.

The Modeler Design Package includes the Modeler Repository, a storage area in which Modeler saves process model information and the files needed to create and generate process models. By default, the Modeler Repository writes to a flat file. Flat file storage is sufficient for most installations. If your Modeler usage is extremely high, however, and you have sufficient resources to handle the overhead of maintaining a database, you can configure the Modeler Repository to write to the Modeler Repository database component instead.

Products Required on Same Machine as Modeler Modeler Requirements for Full Operation

None Developer 6.5

Integration Server 6.5, Modeler Design Package 6.5.1, Process Run Time 6.5.1

Workflow client 6.5.1


Browse services in Servicenet Servicenet Client API

Integration Server

PRT

Modeler

Developer

Workflow client

Modeler Design Package


Modeler

Production EnvironmentInstall the PRT on the Integration Server that will run processes designed in Modeler. Install Integration Server, the Monitor run time, and Administrator on a machine on the same network as the other webMethods products. Install the Monitor user interface on My

webMethods Server. Install the My webMethods Server and Process Audit Log database components.

If you are going to distribute process steps across multiple Integration Servers, install the PRT on each of those Integration Servers and install webMethods Broker on a separate machine to serve as the communication link for the PRTs.

If you want to persist process execution data (written to RAM by default), install the Process Tracking Store database component.

Products Required on Same Machine as Modeler Modeler Requirements for Full Operation

None webMethods Broker 6.5

Integration Server 6.5, Administrator 6.5, Monitor run time 6.5.1, Process Run Time 6.5.1

My webMethods Server 6.5.1, Monitor user interface 6.5.1

My webMethods Server, Process Audit Log database components

Integration Server

Monitor PRTAdministrator

Process Tracking Store

Process Audit Log


Monitor interface




MonitorInstall the Monitor run time on an Integration Server. In a production environment, dedicate the Integration Server to running Monitor. Install the Monitor user interface on My webMethods Server. Install the My webMethods Server database component.

Monitor reads from the IS Core Audit Log and Process Audit Log database components and offers functionality for archiving data stored in these database components. If you want to archive this data, install the Archive, Reporting, and Staging database components.

My webMethods ServerInstall My webMethods Server on a machine to which all webMethods products have network access and that users can access using a browser. Install the My webMethods Server database

component.

Products Required on Same Machine as Monitor Monitor Requirements for Full Operation

Integration Server 6.5 My webMethods Server 6.5.1, Monitor user interface 6.5.1

IS Core Audit Log, My webMethods Server, Process Audit Log database components

Monitor

Integration Server


Monitor interface


Products Required on Same Machine as My webMethods Server

My webMethods Server Requirements for Full Operation

None Common user interface 6.5.1, user interfaces for installed 6.5.x products

My webMethods Server My webMethods

Server


Servicenet

ServicenetInstall the controller, including Servicenet Analytics, on a machine on the same network as other webMethods products. Because the controller makes intensive use of its host machine, webMethods recommends that you dedicate an entire machine to running it. Install the registry on a machine on another machine on the same network. Install the data handler on the same machine as the registry or, to improve performance or distribute resource consumption, on another machine on the same network.

Install the Servicenet user interface on My webMethods Server. Install the Analysis, My webMethods Server, Process Audit Log, Process Tracker, and Servicenet database components.

If you want Servicenet to register and manage Web services hosted in a Integration Server, BEA WebLogic, Glue, or Microsoft .NET server container, install the corresponding plug‐in or publisher on the container host machine. If you want Servicenet to register and manage Web services hosted in other types of containers, install an intermediary on any machine other than the Servicenet registry host machine that has access to the container.

Any machine hosting the controller, the data handler, a plug‐in, a publisher, or an intermediary must have access to the Servicenet registry host machine and vice versa. By default, Servicenet components are configured to discover the registry using a subnet locator that sends out a UPD ping. If you want Servicenet components to use the default subnet locators, install them in the same network segment as the registry, to support UPD multicasting. (You can configure Servicenet components located outside the registry’s network segment to use static locators that contain the registry’s URL.)


Servicenet interface


registry, controller, and data handler

Analysis, Process Audit Log, Process Tracker, Servicenet

Note: The controller and data handler for Servicenet 6.5.1 is identical to the controller and data handler for Optimize 6.5.1 SP2. You can use the controller and data handler from either product for both products. However, to use Servicenet, you must install Servicenet Analytics on the controller.

Products Required on Same Machine as Servicenet Servicenet Requirements for Full Operation

None My webMethods Server 6.5.2, Servicenet user interface 6.5.1

Analysis, My webMethods Server, Process Audit Log, Process Tracker, Servicenet data‐base components



Trading NetworksInstall Integration Server, Trading Networks Server, and the Trading Networks Web Manager on one machine. Install Developer and Trading Networks Console on another machine on the same network. Install the Trading Networks

database component.


Register and manage Web services hosted in a WebLogic container

BEA WebLogic Plug‐in

Note: Install on the WebLogic host machine.

Register and manage Web services hosted in Glue

Glue Plug‐in

Note: Install on the Glue host machine.

Register and manage Web services hosted in any Web service container

Intermediary

Note: Install on any machine that can access the container host machine except the registry host machine.

Register Web services hosted in Microsoft .NET server

Microsoft .NET Publisher

Note: Install on the .NET server host machine.

Register and manage Web services hosted in Integration Server

Servicenet Package

Note: Install on the Integration Server host machine.

Products Required on Same Machine as Trading Networks Console

Trading Networks Console Requirements for Full Operation

Developer 6.5 Trading Networks database component

Integration ServerDeveloperTrading

Networks Server


Trading Networks


Workflow

Workf lowInstall Workflow Server and the Workflow client on separate machines on the same network as the other webMethods products. Install the Workflow database component.

If you are also installing Modeler and want to create process models that call Workflow processes, you must install the Workflow client on the same machine and in the same webMethods installation as Modeler. Otherwise, Workflow Server and the Workflow client can but do not have to share a machine with any other webMethods product. Install webMethods Broker on its own machine, and install Integration Server and Broker Administrator on another machine.

Workflow processes are Broker clients. You can log documents that processes publish or subscribe to on Brokers, and you can log process audit data through Broker. To do so, install the Logging Utility on the Integration Server equipped with Broker Administrator, install another Integration Server and the Monitor run time on another machine on the network, and install My webMethods Server and the Monitor user interface on another machine on the network. Install the My webMethods Server and Process Audit Log

Products Required on Same Machine as Trading Networks Server

Trading Networks Server Requirements for Full Operation

Integration Server 6.5 Trading Networks database component


Store Trading Networks keys and certificates securely

PKI Support

Enable the Manager server to manage Trading Networks Server

OMI Support

Workflow Server

Workflow client

webMethods Broker


Workflow interface

Process Audit Log

Workflow

Integration ServerLogging Utility

Broker Administrator


Workflow Servlet



database components. The Logging Utility acts as a logging agent between Integration Server and the Broker; the utility takes the client data from the Broker and provides it to Integration Server, and Integration Server writes the data to the Process Audit Log database component.

If you want to manage the worklists created by running processes from My webMethods, install the Workflow My Inbox on My webMethods Server. If you want to manage Workflow tasks from My webMethods, install the Workflow Task List Management interface on My webMethods Server. In either case, install the My webMethods Server database component.

Locat ion of Database ComponentsThe database environment for webMethods Fabric 6.5 provides for a more scalable and flexible architecture by allowing different database components to live on different databases servers and by dividing database objects across different storage tablespaces. Place resource‐intensive database components on different database servers. Place your database servers on high‐speed network segments and bring the database network as close as possible to the webMethods products.

If you are installing database components in Oracle, install each database component in its own schema. If you install multiple database components in the same schema, you will not be able to reinstall some database components without dropping all database components in the same schema.

Keep log files separate from data files to help improve performance and reduce disk contention.

Products Required on Same Machine as Workflow Client Workflow Client Requirements for Full Operation

None None

Products Required on Same Machine as Workflow Server Workflow Server Requirements for Full Operation

None webMethods Broker 6.5 SP1

Integration Server 6.5, Broker Administrator 6.5, Logging Utility 6.5, Monitor run time 6.5.1, Workflow Servlet 6.5.1

My webMethods Server 6.5.1; Monitor, My Inbox, and Task List Management user inter‐faces 6.5.1

My webMethods Server, Process Audit Log, Workflow database component


Location of Database Components

Follow the guidelines below when installing database components. Database components whose location is not mentioned can be installed in any location.

The IS Core Audit Log contains error, guaranteed delivery, service, and session data, and you can log documents to it. By default, Integration Server writes the error, guaranteed delivery, service, and session data to flat files. However, webMethods highly recommends that you install the IS Core Audit Log database component and configure Integration Server to use it. Doing so improves performance; when you use flat files, only one logging thread at a time can write data to each file, whereas when you use a database, multiple logging threads can write data to the database simultaneously. Also, when you store data in flat files, you must delete the files manually when you no longer need them, whereas when you store data in a database, you can use facilities in your database to control the length of time the data is retained. Typically, you would only use flat file storage if you lack the resources to purchase, install, and manage a database.

You must install the IS Core Audit Log database component and configure Integration Server to use it if any of the following are true:

You want to log documents

You want to use Monitor

You are using the Process Audit Log database component; the Process Audit Log must always be stored in a database, and you cannot store one log in a database and one in flat files

For best performance, webMethods recommends that you install the IS Core Audit Log and the Process Audit Log database components on separate database servers.

You must install the Analysis, Process Audit Log, and Process Tracker database components in separate databases or schemas. You can use one or more database servers. You can install the database server on the machine that hosts the Manager/Optimize controller but, for best performance, install the database server on a separate machine.

You can install the Process Tracking Store and the Process Audit Log in separate databases or schemas if you apply WmPRT_6‐5‐1_Fix1 to your PRTs (see the installation instructions in the fix’s readme). If you do not apply the fix, you must install the database components in the same database or schema.

If you want to archive data from the IS Core Audit Log database component, the Process Audit Log database component, or both, you must install the source and Archive database components in the same type of RDBMS. If you are using Oracle, SQL Server, or Sybase, you can install the Archive database component in a different database server than the source database components. If you are using DB2, you must install the Archive database component in the same database as the source database components.

The Reporting and Staging database components can be in the same database. However, the services that populate the Reporting database component consume



large amounts of CPU. For best performance, install the Reporting or Staging database components on a database server that will not adversely affect the Process Audit Log or the Process Tracking Store database components.

Example Instal lat ionA simple physical deployment of all webMethods products discussed in this chapter might look like this:

Modeler

webMethods Broker

Developer

Workflow Server

Workflow client

Mainframe Plug-in

Trading Networks

ServerMainframe Package

Monitor

Integration Server


Broker Administrator

Logging Utility

Manager/Optimize/Servicenet controller/data handler

Manager server

Administrator

PRT

JMS AdministratorEDI/EDIINT Modules


Manager Server


Process Audit Log

Servicenet registry Servicenet

Workflow

Trading Networks

Analysis,Process Tracker

IS Core Audit Log,Document History

Workflow Servlet


Monitor interfaceWorkflow interfaces

Access or Portal


Manager/Optimize interfaceServicenet interface


C H A P T E R 2
Software and Hardware Support and Requirements
Product Software Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Product Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Database Component Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44


C H A P T E R 2 S o f t w a r e a n d H a r d w a r e S u p p o r t a n d R e q u i r e m e n t s

Product Software Support and Requirements

Supported Operating Systems and Required JREs/JDKs and BrowsersFor the lists of supported operating systems and the lists of required JREs/JDKs and browsers, see webMethods System Requirements.

SNA Communications Server for webMethods MainframeIf webMethods Mainframe is installed on a Microsoft Windows NT or 2000 system and is communicating with a mainframe over an SNA network, webMethods Mainframe requires one of the SNA communications servers listed in the table below.

If webMethods Mainframe is installed on a Sun Solaris 8 or 9 system and is communicating with a mainframe over an SNA network, webMethods Mainframe requires the SNA communications server listed in the table below.

If webMethods Mainframe is installed on a Hewlett‐Packard HP‐UX 11i system and is communicating with a mainframe over an SNA network, webMethods Mainframe requires the SNA communications server listed in the table below.

SNA Communications Servers Version

Microsoft Host Integration Server 2000 5.0

IBM Communications Server for Windows NT 6.x or later

SNA Communications Server Version

Data Connection Limited SNAP‐IX 7

SNA Communications Server Version

Hewlett‐Packard SNAplus2 6.1


Product Hardware Support and Requirements

Servlet Engine and Limitations for WorkflowTo display HTML‐based tasks, Workflow Server requires one of the servlet engines listed in the table below.

The Workflow Servlet can use HTTPS to communicate with a Web browser. You can enable HTTPS directly in the servlet engine, or you can host the servlet environment in a traditional Web server farm. Typically, a Web server will support HTTPS and redirect URLs to servlet instances behind a firewall.

Workflow does not support the use of a firewall between Workflow Server and its clients (that is, Workflow client tools, the Workflow Java Client API, and the Workflow Servlet). Remote method invocation (RMI) uses a transient TCP/IP port between 1 and 65535, so opening the few ports defined by the Workflow configuration is typically not sufficient.

Product Hardware Support and RequirementsThis section first lists the standard hardware requirements for webMethods products. The section then describes special requirements you must consider when determining actual hardware requirements for certain products.

Standard RequirementsThe table below lists the minimum hardware requirements for each webMethods product. When webMethods recommends a larger amount of hard drive space, RAM, or virtual/swap memory than is required, the recommended amount is shown in parentheses.

Servlet Engine Version

Integration Server’s internal Tomcat servlet engine 6.5

Apache Tomcat 5.0

BEA WebLogic 7.x or 8.x

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



ProductHard Drive Space (MB) RAM (MB)

Vir-tual/Swap (MB) CPUs

Access 50 Nothing beyond My webMethods Server.

Administrator Nothing beyond Integration Server.

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

Deployer 20 Nothing beyond Integration Server

Developer 100 (200) 128 (256) 1

EDI Module and EDIINT Module

Nothing beyond Integration Server

Integration Server 250 (350) 256 (512) 1

webMethods Mainframe 10 128 (256) 1

Manager

Controller† 500 1000 (2000) 1000 1

Data handler 500 1000 (2000) 1000 1

Satellite† 4 100 100 1

Server 300 2000 (4000) 1000 1

Modeler 40 64

Modeler Repository 100 100

Monitor Nothing beyond Integration Server.

My webMethods Server 300 512 (1000) 1

Optimize

Controller† 500 1000 (2000) 1000 1

Data handler 500 1000 (2000) 1000 1

Satellite† 4 100 100 1

Portal 50 Nothing beyond My webMethods Server.

Servicenet

Controller 500 1000 (2000) 1000 1

Data handler 500 1000 (2000) 1000 1*More hard drive space might be required if your documents are large, or if your clients use many guaranteed documents.

†Production environment. For disk subsystem requirements in a production environment, and all hardware requirements in a development environment, see “Manager and Optimize” on page 41.



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

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

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


Additional Hardware Information for the Controller

In a production environment, the controller has these disk subsystem requirements:

Redundant array of independent disks (RAID 5)

UltraWide SCSI

10 to 15k RPM drives

Intermediary 82 256 1

Registry 100 512 30 1

Trading Networks

Console 25 128 (256)

Server 50 1

Workflow

Client 50 64 or 256 1

Server 210 1000 1

ProductHard Drive Space (MB) RAM (MB)

Vir-tual/Swap (MB) CPUs

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

†Production environment. For disk subsystem requirements in a production environment, and all hardware requirements in a development environment, see “Manager and Optimize” on page 41.



The controller requires additional hard drive space for log files. The recommended amount is 100 MB. The controller requires 7 MB of hard drive space for each log file.

In a development environment, the controller has these hardware requirements:

Additional Hardware Information for Satellites

In a production environment, each satellite requires additional hard drive space for log files. The recommended amount is 75 MB. The satellite requires 5 MB of hard drive space for each log file.

Additional Hardware Information for the Server

Each Manager server supports up to 5000 objects, but, for optimal performance, webMethods recommends that each Manager server manage no more than 3500 objects. To manage an environment with 3500 objects or less, a Manager server requires at least 2 GB of RAM. To manage an environment with 10,000 objects, you need at least two Manager servers; webMethods recommends using three. Each Manager server should run on a separate machine that satisfies the hardware requirements.

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

1 Go to the Manager server_directory/bin directory and open the server.bat or server.sh file, as appropriate, in a text editor.

2 Increase the Manager server’s heap space. Locate the JAVA_MAX_MEM parameter and set it as follows:JAVA_MAX_MEM=1536M

3 Save and close the file.

4 Increase the physical memory available for the Manager server to 4 GB.

For more information about scaling Manager servers to manage a larger number of objects, see the webMethods Manager Server Administrator’s Guide.

Hard Drive Space (MB) RAM (MB)

Virtual/Swap (MB) CPUs Disk Subsystem

100 1000 1000 Intel Pentium III processor 400 MHz or higher

10 GB available free space



ServicenetIn a production environment, the controller has these disk subsystem requirements:

Redundant array of independent disks (RAID 5)

UltraWide SCSI

10 to 15k RPM drives

The controller requires additional hard drive space for log files. The recommended amount is 100 MB. The controller requires 7 MB of hard drive space for each log file.

In a development environment, the controller has these hardware requirements:

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

WorkflowThe amount of RAM needed to run Workflow client depends on whether you are running Workflow Designer. If you are, Workflow client needs 256MB of RAM. If you are not running Workflow Designer, Workflow client needs only 64MB of RAM.

Workflow Server requires hard drive space for log files, for project data, and for versions of projects you generate and deploy. The amount of space you allocate should allow for all of these items to increase over time.

Hard Drive Space (MB) RAM (MB)

Virtual/Swap (MB) CPUs Disk Subsystem

100 1000 1000 Intel Pentium III processor 400 MHz or higher

10 GB available free space



Database Component Requirements

Supported RDBMSs and Database DriversFor the list of supported RDBMSs, and database drivers, see webMethods System Requirements.

Hardware RecommendationsProvide as much RAM as possible to database servers. Make sure the database servers use the fastest disk drives available; RAID level 10 is the fastest RAID level that supports redundancy.

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

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

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

OraclewebMethods’ Oracle database schemas use character data types. For character data types, Oracle supports the UTF8 and AL32UTF8 Unicode encodings. While UTF8 is CESU‐8‐compliant and supports the Unicode 3.0 UTF‐8 Universal character set, AL32UTF8 conforms to the Unicode 3.1 or higher UTF‐8 Universal character set. For nchar data types,

RDBMS Required Page and Block Size Default

Oracle 8k page/block size 8k

SQL Server 8k page/block size 8k

DB2 8k page size 4k

Sybase 8k page size 2k



Oracle supports the AL32UTF8 and AL16UTF16 Unicode encodings. The supported Unicode version for AL32UTF8 depends on the Oracle database version. webMethods’ Oracle database schemas do not have linguistic indexes. webMethods recommends the following character sets and sort order:

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

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

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

SybasewebMethods’ Sybase database schemas use character data types. Sybase provides UTF‐8 support for character data types and UTF‐16 support for Unichar data types. webMethods recommends these character sets and sort order:

For... webMethods 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, you will not be able to install some database components in SQL Server.


Character set UTF‐8

Unichar Character Set UTF‐16

Sort order bin_utf8 for UTF‐8 char, utf8bin for unichar



You can check database configuration by using the sp_helpsort stored procedure.

DB2 UDBwebMethods’ DB2 UDB database schemas use character data types. DB2 UDB supports UTF‐8 for character data types and UTF‐16 for graphic data types. webMethods recommends these character sets and sort order:

You can check database configuration by using the GET DATABASE CONFIGURATION command.

Use of SYS or SYSTEM User AccountTo install some webMethods database components in Oracle, you must use the SYS or SYSTEM user account. However, webMethods products do not connect to Oracle using that account; they use the database users you create for the database components.

Some database components are installed with advanced database operations such as data purge and data archive. These operations were built to be highly scalable, and are therefore dependent on advanced Oracle capabilities. For example, the dbms_job package is used as the scheduling mechanism for operations, and the dbms_alert package is used as the alerting mechanism for operations. Since permission to use these advanced Oracle capabilities can only be granted by the SYSDBA role, the SYS password is required to install those database components.

The database users you create require the permissions identified in the ora_cmn_c_ddl_user.sql file in the webMethods_directory\common\db\ scripts\oracle\code\common\create directory. Of those persmissions, the SYS permissions used to run operations are:GRANT EXECUTE ON SYS.DBMS_ALERT TO "USER";GRANT EXECUTE ON SYS.DBMS_JOB TO "USER";


Character set CCSID 1208 (UTF‐8)

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.

Note: The webMethods products that use these database components can function without these operations. The operations are meant simply to assist with such tasks as data management.



The right to execute DBMS_JOB does not allow a user to touch any jobs except their own. Jobs are created in the context of the user, not as SYS or SYSTEM.


C H A P T E R 3
Support for Internat ional Operat ing Environments
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Character Encodings and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51


C H A P T E R 3 S u p p o r t f o r I n t e r n a t i o n a l O p e r a t i n g E n v i r o n m e n t s

OverviewwebMethods products are designed for use anywhere in the world and enable you to exchange data with systems and users who speak languages other than your own. For specific information on the testing, configuration, capabilities, and limitations of any webMethods product, see the product’s readme.

Character Encodings and Configurat ionwebMethods products use the Universal Character Set (ISO/IEC 10646‐2, or Unicode) as the character set for all internal operations. Unicode currently encodes approximately 95,000 of the characters used to write the worldʹs languages. At minimum, the products support the requirements of Unicode 3.0. webMethods HTML content, including administration tools, uses the Unicode UTF‐8 encoding.

Language PacksThe webMethods Installer always installs the U.S. English files necessary to run webMethods products. However, for many products, you can also install language packs that provide translated user interfaces, messages, help, and documentation. For a list of language packs that are available for each webMethods product, see webMethods System Requirements.

Install language packs in these types of situations:

Your operating system is configured to run using a language (locale) other than U.S. English and you want to run your tools (for example, Developer or Modeler) in the language your operating system is using.

You have users, customers, or trading partners who do not speak U.S. English and you want your servers (for example, Integration Server, webMethods Broker, Trading Networks Server, or Workflow Server) to support those people in the languages their operating systems are using. You do not have to change the system settings or locale for your servers; the client sends its language and locale preference to the server, and the server loads the messages in the appropriate language for the client.

You are writing programs using a C or Java API and you want to provide localized messages for users in other languages.

Most products support multiple languages. Products are always installed with U.S. English messages and resources. You can install as many language packs as you want for any product. For products that support multiple languages, your client setup (browser language preference, the default locale in which the product is started, or the locale selected in your user profile) will determine which language you see. For products that support only a single language at a time, the locale and configuration of your operating environment will determine which language pack is displayed. If you operate a product


Browsers

in a locale for which language packs are not available or installed, you will see U.S. English.

BrowsersFor browsers, the HTML interfaces for webMethods products detect the language setting for your browser and try to supply messages and data in that language. When you install a product that is or includes an HTML interface, you can also install different language materials for the interface in the form of webMethods language packs.

webMethods HTML content, including administration tools, uses the Unicode UTF‐8 encoding. Some browsers, such as older 4.X version browsers displaying Asian languages, might require you to configure fonts to support the display of non‐English data or information correctly. In addition, if you have installed webMethods language packs on your webMethods products, you can indicate which of the installed languages to display in your browser. For Internet Explorer, click Tools Internet Options, then click Languages and add the language you want to use to the top of the list. For Firefox, click Tools Options General, then click Languages and add the language you want to use to the top of the list.

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


http://java.sun.com/j2se/1.4.2/docs/guide/intl/fontprop.html

C H A P T E R 3 S u p p o r t f o r I n t e r n a t i o n a l O p e r a t i n g E n v i r o n m e n t s


P A R T II
Simple Instal lat ion
Simple Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55


C H A P T E R 4
Simple Instal lat ion
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

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

Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62


C H A P T E R 4 S i m p l e I n s t a l l a t i o n

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

If errors or warnings occur during the installation, the installer writes the errors and warnings to a file named WmInstallLog.txt and stores the file in the main installation directory (by default, webMethods6).

If you want to install using any other options than those covered in this chapter, or if you need complete information on any topic mentioned here, see “Advanced Installation Using the Wizard” on page 73 or “Advanced Installation Using Console Mode” on page 105.

Before You Begin1 Prepare your machine as follows:

a Make sure the machine has about 50MB of available disk space in its system temp directory (Windows) or temporary directory (UNIX, Linux, OS/400, or Mac OS X) and about 80MB of available virtual memory.

b If you are installing on UNIX, Linux, OS/400, or Mac OS X, install a JRE or JDK 1.4.2.

If you are installing on an OS/400 system, you also need a JRE or JDK 1.4.2 to run webMethods products. You can install the same JRE or JDK to run the webMethods Installer and the products. The installer will automatically configure the products you install to use the JRE or JDK you use to run the installer.

c Download the webMethods Installer. To do so, go to the webMethods Advantage Web site at http://advantage.webmethods.com and log in. Click Product Downloads, then download the installer for Windows or UNIX, as appropriate.

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

e Shut down all webMethods products.

2 If you are going to install the Manager server or Trading Networks Server, ask your database administrator to set up a database user, password, and permissions for each

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



Start the Installer

product’s database component. Each database user must be able to select, insert, update, and delete rows from the tables in its database component.

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

administrator privileges.

If you are installing on a UNIX, Linux, OS/400, or Mac OS X system, log in as the non‐root user unless you are going to install webMethods Broker. If you are going to install webMethods Broker, log in as the root user so you can have the installer automatically create the Broker Server configuration.

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

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

Click Next.

System Action

Windows Double‐click the webMethodsInstaller651.exe file

Other Run the command java -jar webMethodsInstaller651.jar



Specify Release, User Name, and Password

Provide the requested information and then click Next.


Specify the Installation Directory

Specify the Instal lat ion Directory


In the root directory you specify, the installer will automatically install each product in a subdirectory named after the product.

Windows only

Important! Do not install webMethods Broker in the same directory as a pre‐webMethods 6 version of webMethods Broker or in the same directory as any other webMethods Broker product.

If you are installing Workflow and are going to use Integration Server’s Tomcat package as your Workflow servlet engine, you cannot install Integration Server into a directory whose path contains spaces because of a problem relating to 1.4.x JDKs. For example, you cannot install Integration Server in the directory Program Files\webMethods6.



Select Products to Instal l

Choose the webMethods products to install. The installer automatically selects the minimum recommended set of items for each product; however, you might need to select additional items that are listed under other products to install all functionality you need (see Chapter 1, “Planning Your Installation”). The table below indicates the location of certain items in the installer product tree.

Click Next. Read the license agreement. If you accept the terms, select the check box and click Next. If language packs are available for products you are installing or have already installed, the installer displays the language packs panel; click Next.

This item... Listed under...

Broker Administrator, JMS Administrator, Logging Utility, Mainframe Package, Modeler Design Package, Process Runtime, and Workflow Servlet

Integration Server

Product user interfaces (for example, Monitor user interface) My webMethods User Interfaces

Extended Character Set Encoding Support and Servicenet Client API

Common Files

JMS Provider 6.5 SP1 and Broker Client Java API 6.5 SP1 Broker and JMS

Mainframe Plug‐in Developer


Configure Products

If you are installing any of the products listed below, the installer displays panels that request configuration information. If you are not installing any of these products, go to “Review and Install” on page 62.

webMethods Broker

Integration Server

Manager or Optimize

Manager server

Servicenet

Trading Networks Server

Workflow

Configure ProductsAfter you complete each configuration panel, click Next.

webMethods Broker

Provide the license key, select the check box, and then click Next.

provided by webMethods



For instructions on completing the panels for the other products listed above, go to “Configure Products” on page 87. If you are installing Workflow, ignore the instructions for installing a secondary Workflow Server.

Review and Instal l

Review the list of products and items you have selected for install. If the list is correct, click Next. If the list is not correct, click Back until you return to the installer product tree and correct the choices.

The installer installs the products and related items, then displays the Installation Complete panel. Click Close.

Complete the Instal lat ionIf you shut down your anti‐virus software before starting the installer, restart the software.

Go to Chapter 13, “Completing the Installation”.


P A R T III
Advanced Instal lat ion
Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Advanced Installation Using the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Advanced Installation Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181


C H A P T E R 5
Preparing for Instal lat ion
Prepare for Installation on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Prepare for Installation on a UNIX, Linux, OS/400, or Mac OS X System . . . . . . . . . . . . . . 67

Use a Proxy Server, Installation Script or Image, Custom Server, or 64-Bit JDK . . . . . . . . . 70


C H A P T E R 5 P r e p a r i n g f o r I n s t a l l a t i o n

Prepare for Instal lat ion on a Windows System

Prepare the Machine on Which to Install1 Make sure the machine has enough disk space and virtual memory to run the

webMethods installer; that is, about 50MB of available disk space in the system temp directory and about 80MB of available virtual memory. If you are going to install from an image, make sure the machine has enough additional available disk space to accommodate the image. For example, if the image is 200MB, the machine must have at least 250MB of available disk space in its system temp directory.

2 Download the webMethods Installer. To do so, go to the webMethods Advantage Web site at http://advantage.webmethods.com and log in. Click Product Downloads, then download the installer for Windows.

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

4 Shut down all webMethods products.

Prepare to Install the Manager ServerIf you are going to install the Manager server, ask your database administrator to set up a database user, password, and permissions for the Manager server database component. The database user must be able to select, insert, update, and delete rows from the tables in the database component.

Prepare to Install Trading Networks ServerIf you are going to install Trading Networks Server, ask your database administrator to set up a database user, password, and permissions for the Trading Networks database component. The database user must be able to select, insert, update, and delete rows from the tables in the database component.

Note: If you cannot download software, webMethods Customer Operations can pro‐vide the webMethods products you have licensed on a CD or through a private FTP site. Contact webMethods Customer Operations at [email protected].



Prepare for Installation on a UNIX, Linux, OS/400, or Mac OS X System

Prepare for Instal lat ion on a UNIX, Linux, OS/400, or Mac OS X System

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

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

2 Log on to the remote machine.

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

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

1 Install JRE or JDK 1.4.2.

If you are installing on an OS/400 system, you also need a JRE or JDK 1.4.2 to run webMethods products. You can install the same JRE or JDK to run the webMethods Installer and the products. The installer will automatically configure the products you install to use the JRE or JDK you use to run the installer.

2 Make sure the machine has enough disk space and virtual memory to run the installer; that is, about 50MB of available disk space in the temporary directory and about 80MB of available virtual memory. If you are going to install from an image, make sure the machine has enough additional available disk space to accommodate the image. For example, if the image is 200MB, the machine must have at least 250MB of available disk space in its temporary directory.

3 Download the webMethods Installer. To do so, go to the webMethods Advantage Web site at http://advantage.webmethods.com and log in. Click Product Downloads, then download the installer for UNIX.

Note: If you cannot download software, webMethods Customer Operations can provide the webMethods products you have licensed on a CD or through a private FTP site. Contact webMethods Customer Operations at [email protected].




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

5 Shut down all webMethods products.

Prepare to Install webMethods Broker

Install on Solaris, HPUX, or AIXThe Broker Server you can install on a Solaris, HPUX, or AIX operating system is a 64‐bit binary application. If you are going to install Broker Server on any of these operating systems, you must configure the operating system kernel to run in 64‐bit mode. webMethods does not support the 64‐bit Broker Server on an operating system kernel configured to run in 32‐bit mode.

NFS-Mounted PartitionIf you are going to configure Broker Server to create data files on an NFS‐mounted partition, mount the partition using the command below. The options on the command help protect data integrity.mount -o hard,nointr,proto=tcp host:/path /mount_point

For example, if the partition you want to mount is on a machine named netappca, the data directory on the partition is wmbroker_data, and you want to mount the partition on the local file system at /var/opt/wmbroker_data. The command would be as follows:mount -o hard,nointr,proto=tcp netappca:/wmbroker_data /var/opt/wmbroker_data

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

Option Description

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

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

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


Prepare for Installation on a UNIX, Linux, OS/400, or Mac OS X System

Prepare to Install the Manager ServerIf you are going to install the Manager server, ask your database administrator to set up a database user, password, and permissions for the Manager server database component. The database user must be able to select, insert, update, and delete rows from the tables in the database component.

Prepare to Install Trading Networks ServerAsk your database administrator to set up a database user, password, and permissions for the Trading Networks database component. The database user must be able to select, insert, update, and delete rows from the tables in the database component.

Log In as as Root or Non-Root UserLog in as as the root user or as a non‐root user.

If you are going to install webMethods Broker, you can use the webMethods Installer to do the following automatically if you install as the root user:

Install Broker Monitor as a daemon that starts and shuts down automatically (and starts and shuts down your Broker Server automatically) when your system starts and shuts down.

Create the Broker Server, its data directory, and a default Broker.

Create separate storage sessions for configuration (metadata) and run‐time data for the Broker Server and place the sessions in a root directory (by default, /opt/webMethods6).

Create entries in the UNIX or Linux system log configuration file that enable the Broker Server to log Broker Server events to the system log.

However, the Broker Monitor and Broker Server will run as the root user.

If you install webMethods Broker as a non‐root user, you must perform several manual tasks after installation, as follows:

Set up Broker Monitor to run as a daemon or as an application that you start and shut down manually.

Create the Broker Server and its data directory, the default Broker, storage sessions, and system log entries.

You will be able to specify a different storage size than is offered by the installer and to create separate or a combined storage session for configuration and run‐time data. If you want to install as a non‐root user, create a userid that can be used by anyone who will



perform webMethods Broker configuration tasks (such as creating Brokers) and log in under that userid.

Use a Proxy Server, Instal lat ion Script or Image, Custom Server, or 64-Bit JDK

The webMethods Installer offers advanced options you can use to install. The options are described below.

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

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

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

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

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

Installation ImageIf you need to create installations on machines that cannot go outside your corporate firewall to the webMethods Advantage Web site, you can install from an installation image. From an image, you can create as many different installations as you need.

To create an image, you choose all webMethods products you want to install on various machines. The installer downloads the products into the image. You do not specify any installation options (for example, installation directory).

Note: For security reasons, webMethods recommends installing as a non‐root user.



Use a Proxy Server, Installation Script or Image, Custom Server, or 64-Bit JDK

When you install from the image on a particular machine, you choose the products to install from those that were downloaded into the image, and you specify the installation options you want to use for that machine.

Download webMethods Products from Your Own ServerYou can create your own server from which to download webMethods products. You can then choose to use that server when you run the installer.

Install a 64-bit JDKWhen you install a webMethods product on any supported system other than AS/400, the installer installs a 32‐bit JDK 1.4.2 that is appropriate for that system. The products use this JDK by default in most cases. If you are installing on a 64‐bit Solaris SPARC, HP‐UX, or AIX operating system, you can choose to have the installer install a 64‐bit JDK 1.4.2 instead.

Combinations of Advanced OptionsYou can use the advanced options in combination, as follows:

Use a proxy server and create or edit a script

Use a proxy server and create or edit an image

Create a script of installing from an image

Use a proxy server and create or edit a script of installing from an image

You can use your own server and install a 64‐bit JDK with any other option or combination of options.


C H A P T E R 6
Advanced Instal lat ion Using the Wizard
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Use Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

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

Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83


Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Overwrite Using the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103


C H A P T E R 6 A d v a n c e d I n s t a l l a t i o n U s i n g t h e W i z a r d

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

Install from the webMethods installer

Create an installation script or image

Install from an installation script or image

You can use the wizard to install locally or remotely. If you are going to install on a remote Windows system using the wizard or using an installation script that uses the wizard, you must run the installer using remote access software such as pcAnywhere.

To support the wizard, UNIX and Linux systems must have an X‐Windows environment.


Start the Instal ler

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

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

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

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

c Restart Windows.

Note: When you run the webMethods Installer on an OS/400 system, the installer experi‐ences display problems. While these display problems will not adversely affect the instal‐lation process, webMethods strongly recommends that you minimize the problems by running the installer from an OS/400 client for Windows rather than from a telnet client.

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


Start the Installer

2 The method you use to start the installer depends on whether you are installing on the local machine or on a remote machine.

To install on... Follow these steps...

Local machine

1 Open Windows Explorer and go to the directory that contains the installer.

2 Double‐click the webMethodsInstaller651.exe file.

Remote machine

1 Use remote access software such as pcAnywhere to access the remote machine.

2 Open a command window on the remote machine and go to the directory that contains the installer.

3 Enter this command:wMinstaller651.exe -Dsun.java2d.noddraw=true

You must include the noddraw option because of a Java incompatibility with Direct Draw.

If the command shown above does not work, you can download the wMinstaller651.jar file to the remote machine (go to the webMethods Advantage Web site at http://advantage.webmethods.com, log in, click Product Downloads, and download the webMethods Installer for UNIX, install Java JRE 1.4.2, and enter this command:java -Dsun.java2d.noddraw=true-jar wMinstaller651.jar

Note: By default, the webMethods Installer launches with the JVM options ‐Xincgc and ‐Xmx256m. The ‐Xincgc option enables incremental garbage collection. The ‐Xmx option allows Java to use more memory than it uses by default, in case you are installing many products or are creating an installation image. If you are creating an installation image for a platform that is different from the one on which you are running the installer (for example, you are going to create an image for a Solaris platform and you are running the installer on a Windows platform), the installer needs still more memory.

If you want to allow Java to use more than 256MB of memory, open a command window, go to the directory that contains the webMethods Installer, and start the installer using a command that specifies the amount of memory to allow. For example, enter this command:

webMethodsInstaller651.exe -Xmx512m -Xincgc





4 If you want to use a proxy server to install, create or run an installation script or image, download webMethods products from your own server, or install a 64‐bit JDK, click Advanced Options and go to “Use Advanced Options” on page 79.

If you want to install webMethods products without using any advanced options, click Next and go to “Specify Release, User Name, and Password” on page 82.

Start the Installer on a UNIX, Linux, OS/400, or Mac OS X System1 If you are going to install in a locale other than U.S. English, or if you are going to

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

2 Navigate to the directory that contains the webMethods Installer and start the installer by entering this command:java -jar webMethodsInstaller65.jar -console

Shell Commands

sh LANG=locale; export LANG

csh setenv LANG locale


Start the Installer

If you are going to install many components or create an installation image, the installer might need more memory than Java provides by default. If you are going to create an installation image for a platform that is different from the one on which you are running the installer (for example, you are going to create an image for an HP‐UX platform and you are running the installer on a Solaris platform), the installer uses still more memory. On the command, specify parameters that allow Java to use more memory and enable incremental garbage collection as the first two parameters. For example, enter this command:

If you are installing on an AIX, OS/400, HP‐UX, or Linux platform and Java’s just‐in‐time (JIT) compiler is enabled, the compiler might interfere with the installer’s operation. You can start the installer with options that cause the installer to ignore the compiler, as follows:

System Command

AIX and OS/400

Either of the following:java -Djava.compiler=NONE -jar webMethodsInstaller65.jar

java -Djava.compiler= -jar webMethodsInstaller65.jar

HP‐UX java -Djava.compiler=NONE -jar webMethodsInstaller65.jar

Linux java -Djava.compiler=NONE -jar webMethodsInstaller65.jar

*The command varies slightly based on the version of the JRE you have installed.

java -Xmx512m -Xincgc -jar webMethodsInstaller65.jar

allocates more memory

enables incremental garbage collection




3 If you want to create or run an installation script or image, use a proxy server to install or download webMethods products from your own server, or install a 64‐bit JDK, click Advanced Options and go to “Use Advanced Options”, below.

If you want to install webMethods products without using any advanced options, click Next and go to “Specify Release, User Name, and Password” on page 82.


Use Advanced Options

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

Create, Install from, or Edit an Installation Script

The Create Script option both creates the script and installs the products. There are two other options for creating scripts:

To create a script without installing, click Edit script. In the Script file name box, enter the fully qualified name of the file in which to save the script. If the file does not exist, the installer will create it. You can specify any name you want for the file, and you do not have to specify an extension.

To create a script from an existing script without installing, click Install from script. In the Script file name box, type the fully qualified name of the file that contains the existing script to use as a template.

Click Create script. In the Script file name box, enter the fully qualified name of the file in which to save the new script. If the file does not exist, the installer will create it. You can specify any name you want for the file, and you do not have to specify an extension.

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

fully qualified name of file that contains script from which to installNote: If errors occur while script is running, installation fails.

fully qualified name of file that contains script to edit



Create or Install from an Installation Image

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

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

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


Use Advanced Options

Use Proxy Server or Your Own Server

Install a 64-Bit JDK

host name or fully qualified IP address

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

host name or fully qualified IP address



Specify Release, User Name, and Password



Specify the Installation Directory

Specify the Instal lat ion Directory


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


Windows only





Select Products to Instal l

Choose the webMethods products and related items to install.

How to Use the Installer TreeThe installer lists the products using a tree structure. The highest level shows product names and releases and the lower levels show the items that make up or are related to the product.

If you select the check box next to a product, the installer automatically selects the minimum recommended set of items for the product. It also selects other products or items that the product depends on having on the same machine (if those products or items are not already present). If you de‐select a product or item on which a product depends, the installer de‐selects the dependent product. For example, if you select Trading Networks Server, the installer selects Integration Server, because Trading Networks Server depends on Integration Server. If you de‐select Integration Server, the installer de‐selects Trading Networks Server.

Some products require other products and items but not necessarily on the same machine. For example, in a production environment, webMethods recommends you install My webMethods Server and user interfaces on a dedicated machine, not on on the same machines with the products to which the user interfaces belong. You must select these


Select Products to Install

products and items yourself, when you are installing on the proper machine. You must also choose optional items yourself.

Finding ItemsThe table below indicates the location of certain items in the installer product tree.

Complete Product SelectionWhen you are done, click Next. Read the license agreement. If you accept the terms, select the check box and click Next. If language packs are available for products you are installing or have already installed, the installer displays the language packs panel; go to “Select Language Packs”, below. Otherwise, go to “Configure Products” on page 87.

Note: If you have already installed an item in the specified root directory, the item name is followed by the text (Installed) and the item name and its check box are grayed out.

This item... Listed under...

Broker Administrator, JMS Administrator, Logging Utility, Mainframe Package, Modeler Design Package, Process Runtime, Servicenet Package, and Workflow Servlet

Integration Server



Common Files





Select Language Packs

Select the language packs to install.

webMethods Mainframe allows you to install multiple language packs. However, if you install the language pack that matches the host machine’s locale, webMethods Mainframe automatically loads that language pack, and only that language is available to users. If you do not install the language pack that matches the host machine’s locale, webMethods Mainframe uses the default, U.S. English. If you want to use the language of another installed language pack, you must modify the locale in which webMethods Mainframe is started.

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

Click Next. If you are installing any of the products listed below, the installer displays panels that request configuration information. If you are not installing any of these products, go to “Review and Install” on page 102.

Configure webMethods Broker

Configure Integration Server

Configure Manager, Optimize, or Both

Configure Manager Server

Configure Servicenet


Configure Products

Configure Trading Networks Server

Configure Workflow

Configure ProductsAfter you complete each configuration panel, click Next.


Broker Server ConfigurationYou would create the Broker Server at this time (that is, using the installer) if you want to specify one of the storage sizes that are offered by the installer and you want to create separate storage sessions for configuration (metadata) and run‐time data. Using separate storage sessions minimizes the risk of corruption that might occur with a combined storage location. In addition, you can use the webMethods Broker 6.5 online configuration data backup tool to back up configuration data without having to shut down your Broker Server. (For more information about the tool, see the webMethods Broker Administrator’s

Important! If you are installing webMethods Broker on a UNIX or Linux system as a non‐root user, you will not see the webMethods Broker panel discussed below. After installation, go to Appendix C, “Create the Broker Server Configuration Manually” for instructions on supplying webMethods Broker configuration information.

provided by webMethods

port for Broker Server; if multiple Broker Servers on one machine, use different port for each

fully qualified path to directory for Broker Server data

see below

see below



Guide.) If you choose to create the Broker Server at this time, continue to “Storage Size”, below.

You would not create the Broker Server at this time (that is, using the installer) if you want to specify a different storage size than is offered by the installer or if you want to create a combined storage session for configuration and run‐time data. If you do not need to use the online configuration data backup tool, using a combined session might save you a small amount of disk space. If you choose to not create the Broker Server at this time, you must use a webMethods Broker command to create the Broker Server after installation is complete (see Appendix C, “Create the Broker Server Configuration Manually”).

Storage SizeSelect a preconfigured storage session for the Broker Server that is adequate for your expected usage needs, as follows:

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

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

Files Created When to UseBroker Server Startup Time

Small Configuration

32MB log file and 512MB storage file

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

Fastest of all configurations.

Medium Configuration

64MB log file and 1GB storage file

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

Up to twice as long as for Small.

Large Configuration


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

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

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


Configure Products

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

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


start/shut down manually; typical for development environment

start/shut down automatically when start/shut down system; typical for production environment

provided by webMethods; optional, can supply at startup



Configure Manager, Optimize, or BothThis section explains how to configure Manager and Optimize. If you are installing Manager only, the product name used in the configuration panel titles is webMethods Manager. If you are installing Optimize only or both Manager and Optimize, the product name used is webMethods Optimize.

Configure the Controller

JMX port for data handler and satellites to use to communicate with controller

name of controller host machine or, if necessary, IP address

port My webMethods Server uses to communicate with controller; default port for My webMethods Server is 8080

port for data handler to use to communicate with controller name of data handler host machine

or, if necessary, IP address

name of My webMethods Server host machine or, if necessary, IP address

HTTP port for controller

Important! Do not use localhost to identify the host machines.


Configure Products

Configure the Data Handler or Satellite


JMX port for data handler and satellites to use to communicate with controller

Important! Do not use localhost to identify the controller host machine.



Configure the Database Connections

Manager or Optimize creates a JDBC connection pool for each database component. If you later need to modify the connection pools, see the webMethods Database Guide for instructions.

Important! You must configure the database connections during installation or Manager and Optimize will not be fully functional after installation.

If you already have a Process Audit Log database component that you are using to store Modeler or Workflow process data, provide connection parameters that point to the exist‐ing database.

driver for controller or data handler to use to communicate with database

name of database to contain database objects; if SQL Server, must be unique

name of database host machine or, if necessary, IP address

database user and password for controller and data handler to use to log into database component; must be unique

port for controller or data handler to use to communicate with database


Configure Products


Provide the License Key

start/shut down manually; typical for development environment

start/shut down automatically when start/shut down system; typical for production environment

provided by webMethods; optional, can supply at startup




The Database URL box provides a typical format for the selected driver, as follows:

Accept the defaults for the other fields. If you later need to change your JDBC connection pool configuration, see “Identify the Databases that Contain the Cross‐Reference, Document History, IS Core Audit Log, Process Audit Log, Reporting, and Staging Database Components” on page 170. The instructions in that section are for creating pools, but the instructions for modifying pools are very similar.

Important! You must define the JDBC connection pool for the Manager server during installation, or the Manager server will not work after installation.

RDBMS URLDefault Port

Oracle jdbc:wm:oracle://host_or_IPaddress:port;SID=database_name 1521

SQL Server

jdbc:wm:sqlserver://host_or_IPaddress:port;databaseName=database_name;SelectMethod=cursor

1433

driver to use to com-municate with database

database user and password for Manager server to use to log in to database

see below


Configure Products


Configure the Controller, Data Handler, or Both

JMX port for data handler to use to communicate with controller


port My webMethods Server uses to communicate with controller; default port for My webMethods Server is 8080

port for data handler to use to communicate with controller name of data handler host machine

or, if necessary, IP address

name of My webMethods Server host machine or, if necessary, IP address

HTTP port for controller

Important! Do not use localhost to identify the host machines.




Servicenet creates a JDBC connection pool for each database component. If you later need to modify the connection pools, see the webMethods Database Guide for instructions.

Important! You must configure the database connections during installation or Servicenet will not be fully functional after installation.


port for Servicenet clients to use to communicate with Servicenet registry (displays on Servicenet database component panel only)

driver for controller or data handler to use to communicate with database

name of database to contain database objects; if SQL Server, must be unique

name of database host machine or, if necessary, IP address

database user and password for controller and data handler to use to log into database component; must be unique

port for controller or data handler to use to communicate with database

Important! All Servicenet components are pre‐configured to use the default Subnet port. If you distribute Servicenet components over multiple machines, changing the Subnet port from the default will require you to perform manual configuration tasks after installation. However, if you intend to set up more than one Servicenet environment, you must use a different subnet port for each environment to prevent conflicts.


Configure Products


The Database URL box provides a typical format for the selected driver, as follows:

Important! You must define the JDBC connection pool for Trading Networks Server during installation, or Trading Networks Server will not start after installation.


Oracle jdbc:wm:oracle://host_or_IPaddress:port;SID=database_name 1521

Oracle config‐ured for RAC

jdbc:wm:oracle://main_OracleRAC_server_host:main_OracleRAC_server_port;ServiceName=Oracle_service_name;AlternateServers=(alternate_OracleRAC_server1_host:alternate_OracleRAC_server1_port, alternate_OracleRAC_server2_host:alternate_OracleRAC_server2_port,...alternate_OracleRAC_servern_host:alternate_OracleRAC_servern_port)

1521

SQL Server

jdbc:wm:sqlserver://host_or_IPaddress:port;databaseName=database_name;SelectMethod=cursor

1433

Sybase jdbc:wm:sybase://host_or_IPaddress:port;databaseName=database_name;SelectMethod=cursor

5000

driver to use to com-municate with database

database user and password for Trading Networks Serverr to use to log in to database

see below




DB2 UDB

jdbc:wm:db2://host_or_IPaddress:port;databaseName=database_name;PackageName=package_name

50000

DB2 UDB for AS/400

jdbc:wm:db2://host_or_IPaddress:port;LocationName=location_to_access;PackageName=package_name;AlternateId=schema_to_use;CollectionId=package_collection

Note: AlternateId must match the schema in which you created the Trading Networks database tables.

446



Configure Products

Configure Workflow

Configure Workflow Client

The central Workflow Server defaults for connection and RMI registry ports depend on the system on which the central Workflow Server is installed. For Windows, the defaults are 6000 and 6001, respectively. For any other system, the defaults are 5000 and 5001, respectively.

If you later need to change this part of the Workflow client configuration, see the webMethods Workflow User’s Guide for instructions.

Configure Workflow ServerThe values you provide on the webMethods Workflow Server panel depend on whether you want the Workflow Server you are installing to be the central Workflow Server or a secondary Workflow Server that will help the central Workflow Server handle the workload.

If you later need to change this part of the Workflow Server configuration, you can do so using the Workflow Configurator. See “Complete the Workflow Installation” on page 213 for instructions.

port used by central Workflow Server to communicate with Workflow clients

port used by central Workflow Server for RMI

DNS host name or network name of central Workflow Server host machine



Install as Central Workflow Server

On Windows systems, change the Connection port and the RMI registry port to 6000 and 6001, respectively. Ports 5000 and 5001 are reserved by Windows.

port for central Workflow Server to use to communicate with Workflow clients

port for central Workflow Server to use for RMI

DNS host name or network name of machine on which installing central Workflow Server

Important! If you install multiple central Workflow Servers on the same machine, the Workflow Servers must use different connection and RMI registry ports.


Configure Products

Install as Secondary Workflow Server

On Windows systems, change the Connection port and the RMI registry port to 6000 and 6001, respectively. Ports 5000 and 5001 are reserved by Windows.

port central Workflow Server uses to communicate with Workflow clients

port central Workflow Server uses for RMI

DNS host name or network name of machine that hosts central Workflow Server



Review and Instal l

Review the list of products and items you have selected for install. If the list is correct, click Next. If the list is not correct, click Back until you return to the installer product tree and correct the choices.

The installer installs the products and related items, then displays the installation complete panel. Click Close.

Complete the Instal lat ionIf you shut down your anti‐virus software before starting the installer, restart the software.



Overwrite Using the Wizard

Overwri te Using the WizardIf one or more of your webMethods product installations has been corrupted, or if you accidentally deleted some files from a product directory, you can overwrite the products using the webMethods Installer.

1 Shut down the webMethods products you are going to overwrite.

2 If you want to save files you have created or customized, copy them to a different directory.

3 If you want to overwrite from an installation script or image, create the script or image.

4 Start the installer. On the installer Welcome page, click Advanced Options. The installer displays the Advanced Options dialog box.

5 Click the Reinstall tab and select the Replace corrupt installation by overwriting all files, including user data check box.

6 If you want to use a proxy server, click the Servers tab, select the Use proxy server check box, and provide the required information.

7 If you are overwriting from a script, click the Script tab, select the User installation script check box, and then click Create script. In the Script file name box, type the fully qualified name of the file that contains the script to use to overwrite.

If you are overwriting from an image, click the Images tab, select the Use installation image check box, and then click Install from image. In the Image file name box, type the fully qualified name of the file that contains the image to use to overwrite.

8 If you are not using an installation script to overwrite, choose the products to overwrite.

9 Move any user‐created or customized files you copied earlier back to the appropriate location in the new installation.

Important! Only overwrite products in the most extreme cases. Overwriting not only overwrites the product installations, it overwrites all related files you have created or customized.

If the installation you are overwriting includes program files that are not included in the new version, those files remain (unused) in the installation.

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


C H A P T E R 7
Advanced Instal lat ion Using Console Mode
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Install in Console Silent Mode on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Install Using Console Mode on a UNIX, Linux, OS/400, or Mac OS X System . . . . . . . . . . 107

Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

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

Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110


Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Overwrite Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124


C H A P T E R 7 A d v a n c e d I n s t a l l a t i o n U s i n g C o n s o l e M o d e

OverviewThis chapter explains how to do the following:

Install from an installation script on a Windows system using the webMethods Installer console silent mode. You can use console silent mode to install locally or remotely on a Windows system.

Install from the webMethods Installer, create an installation script or image, or install from an installation script or image on a UNIX, Linux, OS/400, or Mac OS X system using the webMethods Installer console mode. You can use console mode to install locally or remotely on a UNIX, Linux, and OS/400 system, or locally on a Mac OS X system.


Instal l in Console Si lent Mode on a Windows SystemTo install from an installation script, you must have already created the script. For instructions on creating a script, and for complete instructions on using the installer, see Chapter 6, “Advanced Installation Using the Wizard”.

To run the installer, you must have Windows system administrator privileges.

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

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

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

c Restart Windows.

2 Open a command window and go to the directory that contains the webMethods Installer. Start the installer by entering the command shown below, where script_file is the fully qualified name of the file containing the installation script from which to install:webMethodsInstaller651.exe -readScript script_file -console


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


Install Using Console Mode on a UNIX, Linux, OS/400, or Mac OS X System

The installer writes output to the command window as it runs the script.

3 If you shut down your anti‐virus software before starting the installer, restart the software.

4 Go to Chapter 13, “Completing the Installation”.

Instal l Using Console Mode on a UNIX, Linux, OS/400, or Mac OS X System

Start the Installer1 If you are going to install in a locale other than U.S. English, or if you are going to

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

2 Navigate to the directory that contains the webMethods Installer and start the installer by entering this command:java -jar webMethodsInstaller65.jar -console

If you are going to install many components or create an installation image, the installer might need more memory than Java provides by default. If you are going to create an installation image for a platform that is different from the one on which you are running the installer (for example, you are going to create an image for an HP‐UX platform and you are running the installer on a Solaris platform), the installer uses still more memory. On the command, specify parameters that allow Java to use more memory and enable incremental garbage collection as the first two parameters. For example, enter this command:

Shell Commands

sh LANG=locale; export LANG

csh setenv LANG locale

java -Xmx512m -Xincgc -jar webMethodsInstaller65.jar

allocates more memory

enables incremental garbage collection



If you are installing on an AIX, OS/400, HP‐UX, or Linux platform and Java’s just‐in‐time (JIT) compiler is enabled, the compiler might interfere with the installer’s operation. You can start the installer with options that cause the installer to ignore the compiler, as follows:

If you want to use a proxy server to install, create or run an installation script or image, download webMethods products from your own server, or install a 64‐bit JDK, add the parameters listed below in any order after -jar webMethodsInstaller651.jar.

System Command

AIX and OS/400

Either of the following:java -Djava.compiler=NONE -jar webMethodsInstaller65.jar

java -Djava.compiler= -jar webMethodsInstaller65.jar

HP‐UX java -Djava.compiler=NONE -jar webMethodsInstaller65.jar

Linux java -Djava.compiler=NONE -jar webMethodsInstaller65.jar

*The command varies slightly based on the version of the JRE you have installed.

Parameter Variables

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

proxy server.

-proxyPort port Port used by the proxy server.

-proxyUser user_name User name for the installer to use to log on to the proxy server.

-proxyPass password Password for -proxyUser user_name.

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

proxy server.

-socksProxyPort port Port used by the proxy server.

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

save the script.

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

save the script.



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

the existing script to use as a template.

-writeScript script_file Fully qualified name of the file in which to save the new script.

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

the script to edit.

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

the installation script from which to install.

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

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

save the installation image.

-imagePlatform platform Platform for which you are creating the image. You can create an image for any platform from any platform. Valid value are as follows:

Platform Value

Windows WNT

Solaris SOL

AIX AIX

HP‐UX PA‐RISC HP11

HP‐UX Itanium 2 HP11IT

Linux LNX

OS/400 AS400

Mac OSX

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

Parameter Variables



Specify Release, User Name, and PasswordWhen prompted, provide the following information:

If you did not specify your own server and the version of the webMethods products to install on the command you used to start the installer, choose the version of the platform to install. Then choose the webMethods Installer server from which you want to download the products.

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

Specify the Installation DirectoryWhen prompted, specify the root directory into which to install webMethods products.

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

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

the installation image from which to install.

Specify webMethods Installer server and release-URLBase URL If you have created your own server from

which to download webMethods products, URL for the server (for example, http://machine/cgi‐bin/script.cgi).

-serverVersion version Release of the products to install (6.5).

Install a 64-bit JDK-64BitJVM Lets you install a 64‐bit JDK on a 64‐bit Solaris,

HP‐UX, or AIX operating system.

Parameter Variables






Select Products to InstallWhen prompted, choose the webMethods products and related items, like documentation, to install.

How to Use the Installer TreeThe installer lists the products using a tree structure. The highest level shows product names and releases and the lower levels show the items that make up or are related to the product.

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

If you want to install the minimum recommended set of items for a product, enter the number shown next to the product heading (for example, enter the number for Integration Server). The installer shows an X next to each of the recommended items listed under the product. If you want to install only items you choose for a product, enter the number for each of those items (for example, enter the number for Program Files under Integration Server). You must enter each number on a separate line. The installer shows an X next to each item you select. When all items are selected for a product, the installer shows an X next to the product heading. If only certain items are selected for a product, the installer shows a pound sign (#) next to the product heading.

Finding ItemsThe table below indicates the location of certain items in the installer product tree.

Note: If you have already installed an item in the specified root directory, the installer shows an I next to the item.

This item... Is listed under...

Broker Administrator, JMS Administrator, Logging Utility, Mainframe Package, Modeler Design Package, Process Runt‐ime, Servicenet Package, and Workflow Servlet

Integration Server



Common Files



Complete Product SelectionWhen you are done, press ENTER twice. The installer displays the license agreement. Read the agreement and indicate whether you accept its terms.

If language packs are available for products you are installing or have already installed, the installer prompts you to choose packs to install; go to “Select Language Packs”, below. Otherwise, go to “Configure Products” on page 113.

Select Language PackswebMethods Mainframe allows you to install multiple language packs. However, if you install the language pack that matches the host machine’s locale, webMethods Mainframe automatically loads that language pack, and only that language is available to users. If you do not install the language pack that matches the host machine’s locale, webMethods Mainframe uses the default, U.S. English. If you want to use the language of another installed language pack, you must modify the locale in which webMethods Mainframe is started.

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

If you are installing any of the products listed below, the installer next prompts for configuration information. If you are not installing any of these products, go to “Review and Install” on page 124.



Configure Manager, Optimize, or Both




Configure Workflow



This item... Is listed under...

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



Configure Products


When prompted, provide the information below for webMethods Broker.

1 Enter the webMethods Broker license key provided by webMethods.

2 Indicate whether you want to create the Broker Server.

You would create the Broker Server at this time (that is, using the installer) if you want to specify one of the storage sizes that are offered by the installer and you want to create separate storage sessions for configuration (metadata) and run‐time data. Using separate storage sessions minimizes the risk of corruption that might occur with a combined storage location. In addition, you can use the webMethods Broker 6.5 online configuration data backup tool to back up configuration data without having to shut down your Broker Server. (For more information about the tool, see the webMethods Broker Administrator’s Guide.) If you choose to create the Broker Server at this time, continue to step 3.

You would not create the Broker Server at this time (that is, using the installer) if you want to specify a different storage size than is offered by the installer or if you want to create a combined storage session for configuration and run‐time data. If you do not need to use the online configuration data backup tool, using a combined session might save you a small amount of disk space. If you choose to not create the Broker Server at this time, you must use a webMethods Broker command to create the Broker Server after installation is complete (see Appendix C, “Create the Broker Server Configuration Manually”).

3 Identify the port on which to run the Broker Server. The default port is 6849.

4 Provide the fully qualified path to the data directory in which to store Broker Server data.

Important! If you are installing webMethods Broker on a UNIX or Linux system as a non‐root user, you will not see the prompts discussed below. After installation, go to Appendix C, “Create the Broker Server Configuration Manually” for instructions on supplying webMethods Broker configuration information.

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

Important! If you install multiple Broker Servers on the same machine, you must configure each Broker Server to run on a different port.



5 Select a preconfigured storage session for the Broker Server that is adequate for your expected usage needs, as follows:

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

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

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

Files Created When to UseBroker Server Startup Time

Small Configuration

32MB log file and 512MB storage file

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

Fastest of all configurations.

Medium Configuration


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

Up to twice as long as for Small.

Large Configuration


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

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

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



Configure Integration ServerWhen prompted, provide the Integration Server license key provided by webMethods.

If you are installing on a Windows system, indicate whether to install Integration Server as a Windows application or as a Windows service, based on the following:

Configure Manager, Optimize, or BothThis section explains how to configure Manager and Optimize. If you are installing Manager only, the product name used is webMethods Manager. If you are installing Optimize only or both Manager and Optimize, the product name used is webMethods Optimize.


If you are installing the controller, provide the information below when prompted.

If you want ... Install as...

To start and shut down Integration Server manually. Typically, you would install a development Integration Server as an application.

Application

Integration Server to start and shut down automatically when you start and shut down your system. Typically, you would install a production Integration Server as a service.

Service

Box or Prompt Description

Controller host Name of the controller host machine. If necessary, you can provide the host machine’s IP address.

Important! Do not use localhost to identify the host machine.

Controller port HTTP port for the controller.

Controller JMX port JMX port for the satellites and the data handler to use to communi‐cate with the controller.

My webMethods Server host

Name of the machine that hosts My webMethods Server. If neces‐sary, you can provide the host machine’s IP address.


My webMethods Server port

Port that My webMethods Server uses to communicate with the controller. The default port for My webMethods Server is 8080.



Configure the Data Handler or Satellite

If you are installing the data handler or satellite on a non‐controller host machine, provide the information below when prompted.


When prompted, provide the information below.

Data handler host Name of the data handler host machine. If necessary, you can pro‐vide the host machine’s IP address.


Data handler port Port for the data handler to use to communicate with the control‐ler.




Controller JMX port JMX port for the data handler or satellites to use to communicate with the controller.


Important! You must configure the database connections during installation or Manager and Optimize will not be fully functional after installation.



Database driver Driver for the controller or data handler to use to communicate with the database.

Database host Name of the database host machine. If necessary, you can provide the host machine’s IP address.

Database port Port for the controller or data handler to use to communicate with the database.



Optimize creates a JDBC connection pool for each database component. If you later need to modify the connection pools, see the webMethods Database Guide for instructions.


Provide the License Key

When prompted, provide the Manager server license key provided by webMethods.

If you are installing on a Windows system, indicate whether to install the Manager server as a Windows application or as a Windows service, based on the following:

Database name (SQL Server) or SID (Oracle)

Name of the database that you want to contain the database objects for the database component. If you are using a SQL Server data‐base, the database name must be unique.

Database user Database user for the controller and the data handler to use to log into the database component. The database user for each database component must be unique.

Database user password

Password for the database user.

If you want ... Install as...

To start and shut down the Manager server manually. Typically, you would install a development Manager server as an application.

Application

The Manager server to start and shut down automatically when you start and shut down your system. Typically, you would install a production Manager server as a service.

Service




Configure the Database Connection



Important! You must configure the database connection during installation or the Manager server will not work after installation.

Box or Prompt Entry

Database driver

Driver to use to communicate with the database.

Database URL URL for the database, as follows:

URLDefault Port

Oraclejdbc:wm:oracle://host_or_IPaddress:port;SID=database_name

1521

SQL Serverjdbc:wm:sqlserver://host_or_IPaddress:port;databaseName=database_name;SelectMethod=cursor

1433

Database user name

Database user for the Manager server to use to log in to the database.

Database password






If you are installing the controller, data handler, or both, provide the information below when prompted.






Controller port HTTP port for the controller.

Controller JMX port JMX port for the data handler and the satellites to use to communi‐cate with the controller.

My webMethods Server host

Name of the machine that hosts My webMethods Server. If neces‐sary, you can provide the host machine’s IP address.


My webMethods Server port

Port that My webMethods Server uses to communicate with the controller. The default port for My webMethods Server is 8080.

Data handler host Name of the data handler host machine. If necessary, you can pro‐vide the host machine’s IP address.


Data handler port Port for the data handler to use to communicate with the control‐ler.

Important! You must configure the database connections during installation or Servicenet will not be fully functional after installation.




Servicenet creates a JDBC connection pool for each database component. If you later need to modify the connection pools, see the webMethods Database Guide for instructions.


Database driver Driver for the controller or data handler to use to communicate with the database.

Database host Name of the database host machine. If necessary, you can provide the host machine’s IP address.

Database port Port for the controller or data handler to use to communicate with the database.

Database name (SQL Server) or SID (Oracle)

Name of the database that you want to contain the database objects for the database component. If you are using a SQL Server data‐base, the database name must be unique.

Database user Database user for the controller and the data handler to use to log into the database component. The database user for each database component must be unique.

Database user password


Subnet port Port for Servicenet clients to use to communicate with the Servicenet registry. Display on Servicenet database component panel only.

Important! All Servicenet components are pre‐configured to use the default Subnet port. If you distribute Servicenet components over multiple machines, changing the Subnet port from the default will require you to perform manual configuration tasks after installation. However, if you intend to set up more than one Servicenet environment, you must use a different subnet port for each environment to prevent conflicts.



Configure Trading Networks ServerWhen prompted, provide the information below.

Important! You must configure the database connection during installation or Trading Networks will not start after installation.

Box or Prompt Entry

Database driver

Driver to use to communicate with the database.

Database URL URL for the database, as follows:

URLDefault Port


1521

Oracle configured for RACjdbc:wm:oracle://main_OracleRAC_server_host:main_OracleRAC_server_port;ServiceName=Oracle_service_name;AlternateServers=(alternate_OracleRAC_server1_host:alternate_OracleRAC_server1_port, alternate_OracleRAC_server2_host:alternate_OracleRAC_server2_port,...alternate_OracleRAC_servern_host:alternate_OracleRAC_servern_port)

1521


1433

Sybasejdbc:wm:sybase://host_or_IPaddress:port;databaseName=database_name;SelectMethod=cursor

5000

DB2 UDBjdbc:wm:db2://host_or_IPaddress:port;databaseName=database_name;PackageName=package_name

50000




Configure Workflow

Configure Workflow Client

When prompted, provide the information below for Workflow client.

If you later need to change this part of the Workflow client configuration, see the webMethods Workflow User’s Guide for instructions.

DB2 UDB for AS/400jdbc:wm:db2://host_or_IPaddress:port;LocationName=location_to_access;PackageName=package_name;AlternateId=schema_to_use;CollectionId=package_collection

Note: AlternateId must match the schema in which you created the Trading Networks database tables.

446

Database user name

Database user for Trading Networks Server to use to log in to the database.

Database password


Box or Prompt Entry

Host name DNS host name or network name of the machine that hosts the central Workflow Server.

Connection port

Port the central Workflow Server uses to communicate with Workflow clients.

The central Workflow Server default for connection port depends on the system on which the central Workflow Server is installed. For Windows, the default is 6000. For any other system, the default is 5000.

RMI registry port

Port used by the central Workflow Server for RMI.

The central Workflow Server default for connection port depends on the system on which the central Workflow Server is installed. For Windows, the default is 6001. For any other system, the default is 5001.

Box or Prompt Entry



Configure Workflow Server

When prompted, provide the information below for Workflow Server. The values you provide depend on whether you want the Workflow Server you are installing to be the central Workflow Server or a secondary Workflow Server that will help handle the workload.

If you want the Workflow Server to be the central Workflow Server, provide the values as follows:

If you want the Workflow Server to be a secondary Workflow Server, provide the values as follows:

Box or Prompt Entry

Host name DNS host name or network name of the machine on which you are installing the central Workflow Server.

Connection port

Port for the central Workflow Server to use to communicate with Workflow clients.

On Windows systems, change the Connection port to 6000. Port 5000 is reserved by Windows.

RMI registry port

Port for the central Workflow Server to use for remote method invocation (RMI).

On Windows systems, change the RMI registry port to 6001. Port 5001 is reserved by Windows.

Important! If you install multiple central Workflow Servers on the same machine, the Workflow Servers must use different connection and RMI registry ports.

Box or Prompt Entry

Host name DNS host name or network name of the machine that hosts the central Workflow Server. The default is the installation machineʹs host name, so you must change the default name to the central Workflow Serverʹs host name.

Connection port

Port for the central Workflow Server to use to communicate with Workflow clients.

On Windows systems, change the Connection port to 6000. Port 5000 is reserved by Windows.

RMI registry port

Port for the central Workflow Server to use for RMI.

On Windows systems, change the RMI registry port to 6001. Port 5001 is reserved by Windows.



If you later need to change this part of the Workflow Server configuration, you can do so using the Workflow Configurator. See “Complete the Workflow Installation” on page 213 for instructions.

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

Complete the InstallationIf you shut down your anti‐virus software before starting the installer, restart the software.


Overwri te Using Console ModeIf one or more of your webMethods product installations has been corrupted, or if you accidentally deleted some files from a product directory, you can overwrite the products using the webMethods Installer.

1 Shut down the webMethods products you are going to overwrite.

2 If you want to save files you have created or customized, copy them to a different directory.

3 If you want to overwrite from an installation script or image, create the script or image.

4 Start the webMethods Installer but add this parameter to the start command:-overwriteInstall

If you want to use a proxy server, also specify the parameter for that option. If you are overwriting from an installation script or image, specify the parameter for that option as well. The options are described in “Start the Installer” on page 107.

Important! Only overwrite products in the most extreme cases. Overwriting not only overwrites the product installations, it overwrites all related files you have created or customized.

If the installation you are overwriting includes program files that are not included in the new version, those files remain (unused) in the installation.



Overwrite Using Console Mode

5 If you are not using an installation script to overwrite, choose the products to overwrite.

6 Move any user‐created or customized files you copied earlier back to the appropriate location in the new installation.


P A R T IV
Database Component Instal lat ion
Installing the Database Components in Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Installing the Database Components in SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Installing the Database Components in DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Installing the Database Components in Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Identifying Databases for Use by Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169


C H A P T E R 8
Instal l ing the Database Components in Oracle
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, Reporting, Staging, and Trading Networks Database Components . . 130

Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Install the My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . 138

Reinstall the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141


C H A P T E R 8 I n s t a l l i n g t h e D a t a b a s e C o m p o n e n t s i n O r a c l e

OverviewThis chapter explains how to install webMethods database components in Oracle. Database components are installed using different methods; the section headings indicate which database components are covered in each section.

Instructions for installing the Workflow database component automatically via the Workflow Configurator are provided in “Complete the Workflow Installation” on page 213. Instructions for installing the Integration Server Repository are provided in the webMethods Integration Server Clustering Guide.

Instal l the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, Report ing, Staging, and Trading Networks Database Components

Set Up Database UsersAsk your database administrator to set up a database user, password, and permissions for each database component. Each database user must be able to select, insert, update, and delete rows from the tables in its database component.

Download the Database ScriptsYou install the database components covered in this section using database scripts available through the webMethods Installer. Download the database scripts as follows:

1 Download the webMethods Installer from the webMethods Advantage Web site at http://advantage.webmethods.com to a machine equipped with an Oracle database client.

2 Start the installer. Specify the installation directory as the webMethods 6.5 installation directory (by default, webMethods6).

3 In the component selection list, go to Common Files and choose to download the latest version of Database Scripts.

Note: If you installed Trading Networks Server, you might already have asked your database administrator to set up a database user, password, and permissions for the Trading Networks database component before installation so you could enter the database user and password during installation.



Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components

Install the Database ComponentsInstall the database components by executing the scripts listed below from your database editor. The scripts are located in the webMethods_directory\common\db\scripts\create directory.

Go to Chapter 12, “Identifying Databases for Use by Products”.

Instal l the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components

Set Up Database UsersYou can create database users as part of the installation process described in this section or you can have your database administrator set them up.

If you want your database administrator to set up the database users, ask the database administrator to create one database user for each database component. Assign the database user the permissions listed in the ora_cmn_c_ddl_user.sql file in the webMethods_directory\common\db\ scripts\oracle\code\common\create directory. If the Oracle instance in which you want to install is configured to allow remote administrative login, the database administrator can create the database users from a remote machine. If the Oracle instance is not configured to allow remote administrative

Component Script

Cross‐Reference create_xref_6‐5_database.sql

Document History create_idr_6‐5_database.sql

IS Core Audit Log create_iscoreaudit_6‐5_database.sql

Modeler Repository create_RepoV3_6‐5_database.sql


create_prt_6‐5_database.sql

Reporting create_reporting_6‐5_database.sql, populate_reporting_6‐5_database.sql

Staging create_staging_6‐5_database.sql

Trading Networks create_TN_6‐5_database.sql, create_archive_TN_6‐5_database.sql



login, the database administrator must create the database users on the machine that hosts the Oracle instance.

Download the Database ScriptsYou install the database components covered in this section using database scripts and a program called the webMethods Database Installer that are available through the webMethods Installer. Download the scripts and webMethods Database Installer as follows:

1 Download the webMethods Installer from the webMethods Advantage Web site at http://advantage.webmethods.com to a machine equipped with an Oracle database client.


3 In the component selection list, go to Common Files and choose to install Database Scripts 6.5.1.7.

Set the Database Connection Properties1 On the Oracle database client machine, open a command window and go to the

webMethods_directory\common\db\scripts\Oracle directory.

2 Start the webMethods Database Installer by running the oracle.{bat|sh} program.

3 Choose View/modify database connection properties file and set these properties for each database component you are going to install:set database_component_DBHOST=database_hostset database_component_SID=database_SIDset database_component_DBPORT=database_portset database_component_USER=database_user


Note: If you installed Manager server, you might already have asked your database administrator to set up a database user, password, and permissions for the Manager server database component before installation so you could enter the database user and password during installation.




Create the Tablespaces in OracleIf you are installing in Oracle, create the tablespaces listed below for the database components. If you install multiple database components on the same database, they can use the same tablespaces.

If you have a high‐demand production environment, you should create the tablespaces manually so you can configure the tablespace setup for optimal I/O performance. For example, dedicating a disk controller and drive to data and a separate controller and drive to index might result in better performance than if you use the same controller for both. Below is a sample script for creating the WEBMDATA_LGA tablespace.REM ********** TABLESPACE FOR WEBMDATA_LGA **********CREATE TABLESPACE WEBMDATA_LGADATAFILE '%ORACLE_DATA_DIR1%\webmdata_lga_01.dbf' SIZE 1000MAUTOEXTEND ON NEXT 10 M MAXSIZE 10000 MEXTENT MANAGEMENT LOCAL UNIFORM SIZE 5M;

If you have a development or low‐demand environment, you can have the database installer create the tablespaces automatically using the quick setup option, but be aware that this configuration might not produce optimal performance. To create tablespaces automatically, do the following:

1 In the database installer, choose Install webMethods tablespaces, then choose the database component that will use those tablespaces (for example, Analysis 6.5.1).

2 Choose the Oracle version you are using. The installer supplies default directories for the data and index files; you can accept them or identify other directories to use.

3 When prompted, enter the SYS password for server database_host. The installer creates the tablespaces based on the database connection properties you set earlier.

Tablespace Description ApproximateExtent Size

WEBMDATA_LGA Large extents for large tables 5 MB

WEBMDATA_MDA Medium extents for medium tables 1 MB

WEBMDATA_SMA Small extents for small tables 128 KB

WEBMINDX_LGA Large extents for large indexes 5 MB

WEBMINDX_MDA Medium extents for medium indexes 1 MB

WEBMINDX_SMA Small extents for small indexes 128 KB



Install the Database ComponentsYou can install the database components automatically using the webMethods Database Installer or you can install them manually. The database installer creates the user and database objects for each database component.

Before You BeginIf you are going to install the Archive database component on a different database server than the Process Audit Log and IS Core Audit Log database components, create a DBlink name for the Archive database component to use to link to each database component from which you want to archive. If the Process Audit Log and IS Core Audit Log database components are on the same database server, the Archive database component can use the same DBLink to connect to both.

Install a Database Component Using the Database Installer1 Choose Install/reinstall a database component, then choose the database component to

install (for example, Analysis 6.5.1).

2 This step depends on whether your database administrator created the database users for the database components.

If the database administrator did not create the database users, choose Create new user database_user. When prompted, enter the password for SYS.

If your database administrator did create the database uesrs, choose Use existing user database_user.

3 The installer prompts for these properties:

Property Entry

PROCESSAUDIT_DBLINK If you want to archive from the Process Audit Log, and the Archive and Process Audit Log database components are on different database servers, enter the name of the DBlink you created in “Before You Begin” on page 134. If you do not want to archive from the Process Audit Log database component, or the database components are on the same database server, press Enter.

ISCOREAUDIT_DBLINK If you want to archive from the IS Core Audit Log, and the Archive and IS Core Audit Log database components are on different database servers, enter the name of the DBlink you created in “Before You Begin” on page 134. If you do not want to archive from the IS Core Audit Log database component, or the database components are on the same database server, press Enter.



Install a Database Component Manually1 Open a command window and go to the webMethods_directory\common\

db\scripts\oracle directory.

2 Set the environment variable DBCALL_INPUT_STRING by running the commands below.set DBCALL_INPUT_STRING=database_component_code database_user database_user_password large_data_tablespace medium_data_tablespace small_data_tablespace

set DBCALL_INPUT_STRING=%DBCALL_INPUT_STRING% large_index_tablespace medium_index_tablespace small_index_tablespace

set DBCALL_INPUT_STRING=%DBCALL_INPUT_STRING% mail_host email_recipient

PROCESS_SCHEMA If you want to archive from the Process Audit Log, enter the database user (Oracle) or database name (SQL Server) for the Process Audit Log database component. Otherwise, press Enter.

ISCORE_SCHEMA If you want to archive from the IS Core Audit Log, enter the database user (Oracle) or database name (SQL Server) for the IS Core Audit Log database component. Otherwise, press Enter.

Parameter Entry

database_component_code Code for the database component, as follows:

Database Component Code

Analysis ANL

Archive ARC

Manager server MNS

Process Audit Log PRA

Process Tracker PTR

Servicenet SNT

database_user Schema user name.

database_user_password Schema password.

Property Entry



For example, if you want to install the Process Tracker database component on a Windows system, you would run these commands:set DBCALL_INPUT_STRING=PTR PROCESSTRACKER PROCESSTRACKER WEBMDATA_LGA WEBMDATA_MDA

set DBCALL_INPUT_STRING=%DBCALL_INPUT_STRING% WEBMDATA_SMA WEBMINDX_LGA WEBMINDX_MDA WEBMINDX_SMA TEMP

set DBCALL_INPUT_STRING=%DBCALL_INPUT_STRING% mailhost.mycompany.com [email protected]

3 If the database administrator did not create the database user for this database component, create the database user by running this command:sqlplus sys@service_name as sysdba @code/common/create/ora_cmn_c_ddl_user.sql %DBCALL_INPUT_STRING%

4 Install shared database objects by running the commands below. These objects, which include functionality like metadata information and data purge, provide a foundation for use by all product database components in the schema.

sqlplus database_user@service_name @code/common/create_cmn_ora.sql %DBCALL_INPUT_STRING%

sqlplus database_user@service_name @code/operationmanagement/create_opm_ora.sql %DBCALL_INPUT_STRING%

sqlplus database_user@service_name @code/databasemanagement/create_dbm_ora.sql %DBCALL_INPUT_STRING%

sqlplus database_user@service_name @code/datamgmt_massive/create_dtp_ora.sql %DBCALL_INPUT_STRING%

large_data_tablespace medium_data_tablespace small_data_tablespace

Tablespace for large, medium, and small tables.

large_index_tablespace medium_index_tablespace small_index_tablespace

Tablespace for large, medium, and small indexes.

temp_tablespace Tablespace for temporary storage.

mail_host email_recipient

Mail host for operation notices and default e‐mail address to receive them.

Parameter Entry

Important! Perform this step only once per schema.



5 Install the database component by running this command:sqlplus database_user@service_name @code/create_database_component_6-5_ora.sql %DBCALL_INPUT_STRING%

Complete the Installation1 For security reasons, if you installed the Analysis, Archive, Manager server, Process

Audit Log, or Process Tracker database component, remove the database user password from the database connection properties file, as follows:

a If the webMethods Database Installer is not already started, start the installer on the Oracle database client machine by running the oracle.{bat|sh} program.

b Choose View/modify database connection properties file and remove the password from the property shown below:set database_component_USER_PWD=

c Save and close the file.

2 If you installed the Archive, Manager Server, or Process Audit Log database component, define a JDBC connection pool for Integration Server to use to communicate with the database component. For instructions, see “Identify the Databases that Contain the Cross‐Reference, Document History, IS Core Audit Log, Process Audit Log, Reporting, and Staging Database Components” on page 170.

3 If you installed the Archive database component, use the GRANT command to give the Archive database user permission to select and delete from the Process Audit Log database component, the IS Core Audit Log database component, or both, depending on the data you want to archive.

Note: Manager, Optimize, and Servicenet automatically create JDBC connection pools to use to communicate with the Analysis, Process Audit Log, and Process Tracker database components when you start the Manager/Optimize and Servicenet controllers. The information required to create the connection pools was supplied during product installation.

You might also have already defined a connection pool for Manager server during product installation.



Instal l the My webMethods Server Database ComponentYou can install the My webMethods Server database component manually using one of the commands described in this section. The command you use depends on whether you are running the command from a machine that hosts My webMethods Server, Access, or Portal, or none of those. If you want to run the command to install from a machine that does not host any of those products, the machine must be equipped with an Oracle database client.

You can install the My webMethods Server database component in either of two ways:

If you have administrator access to the database server in which you want to install the database component, you can use a command to create a tablespace and database user and install the database component in the new tablespace.

If you do not have administrator access, you can ask your database administrator to create an empty tablespace and a database user, and then use a command to install the database component in the tablespace. The database user must have CONNECT, RESOURCE, CREATE VIEW, and GLOBAL QUERY REWRITE permissions.

Before You Begin1 Set the NLS_LENGTH_SEMANTICS initialization parameter to BYTE.

2 Prepare to run a command to install the My webMethods Server database component by following the appropriate steps below.

Note: You can use the Portal Server Configurator to automatically install the My webMethods Server database component. For instructions, see “Complete the Access, My webMethods Server, or Portal Installation” on page 183.

To run the command from... Follow these steps...

My webMethods Server, Access, or Portal host machine

Open a command window and go to the My web‐Methods Server, Access, or Portal_directory\bin\db\ scripts\oracle directory.

Other machine 1 On the My webMethods Server, Access, or Portal host machine, go to the My webMethods Server, Access, or Portal_directory\bin\db\scripts directory.

2 Copy the oracle directory to the Oracle database client machine.


Install the My webMethods Server Database Component

Create the Tablespace and Database User and Install the Database ComponentTo create a tablespace and database user and install the My webMethods Server database component in the new tablespace, run this command:{dbcreate.{bat|sh} | dbcreate_sqlplus.{bat|sh}} database_server_host:database_server_port SIDadministrator_user administrator_passworddatabase_user database_password tablespace y

For example, the following command creates the mywebmserver tablespace in the mywebmserver_db Oracle instance on the oraserver database server, creates the mywebmserveruser database user, and installs the My webMethods Server database component in the mywebmserver tablespace:dbcreate.bat oraserver:1521 mywebmserver_db sys syspassword mywebmserveruser mywebmserverpassword mywebmserver y

Parameter Entry

{dbcreate.{bat|sh} | dbcreate_sqlplus.{bat|sh}}

If you are running the command from the My webMethods Server, Access, or Portal host machine, enter dbcre‐ate.{bat|sh}. If you are running the command from a machine that does not host My webMethods Server, Access, or Portal, enter dbcreate_sqlplus.{bat|sh).

database_server_host Name or IP address of the machine that hosts the Oracle database server. Do not use localhost to identify the host.

database_server_port Port the database server uses to communicate. The default port for Oracle is 1521.

SID SID for the Oracle instance on database_server_host in which to install the database component.

administrator_user Administrator user for the database server.

administrator_password

Administrator password for the database server.

database_user Database user for My webMethods Server, Access, or Por‐tal to use to communicate with the database server. The database user must be unique for the database server.

database_user_password


tablespace Name of the tablespace in which to install the database component.

y Tells the command to create a tablespace and database user and install the database component in the new tablespace.



Install the Database Component Using an Existing Tablespace and Database UserTo install the My webMethods Server database component in an existing tablespace using an existing database user, run this command:{dbcreate.{bat|sh} | dbcreate_sqlplus.{bat|sh}} database_server_host:database_server_port SIDadministrator_user administrator_password database_user database_password tablespace n

For example, the following command installs the My webMethods Server database component in the existing tablespace mywebmserver on the oraserver database server, using the existing database user mywebmserveruser:dbcreate.bat oraserver:1521 mywebmserver_db mywebmserveruser mywebmserverpassword mywebmserveruser mywebmserverpassword portal n

Parameter Entry

{dbcreate.{bat|sh} | dbcreate_sqlplus.{bat|sh}}

If you are running the command from the My webMethods Server, Access, or Portal host machine, enter dbcre‐ate.{bat|sh}. If you are running the command from a machine that does not host My webMethods Server, Access, or Portal, enter dbcreate_sqlplus.{bat|sh).

database_server_host Name or IP address of the machine that hosts the Oracle database server. Do not use localhost to identify the host.


SID SID for the Oracle instance on database_server_host in which to install the database component.

administrator_user Enter the same value you enter for database_user.


Enter the same value you enter for database_user_password.

database_user Database user for My webMethods Server, Access, or Por‐tal to use to communicate with the database.



tablespace Name of the tablespace in which to install the database component.

n Tells the command to install the database component in an existing tablespace using an existing database user.


Reinstall the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet Database Component

Reinstal l the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet Database Component

If you need to start over by clearing out all data from the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet database component, you can reinstall the database component using the webMethods Database Installer.

1 On the machine that hosts the database scripts and webMethods Database Installer, open a command window and go to the webMethods_directory\common\ db\scripts\oracle directory.

2 Start the webMethods Database Installer by running the oracle.{bat|sh} program.

3 Choose Install/reinstall a database component, then choose the database component to reinstall (for example, Process Tracker 6.5.1).

Important! Do not reinstall a database component if you have installed multiple database components in a single Oracle schema. Doing so would drop all database components from the schema.


C H A P T E R 9
Instal l ing the Database Components in SQL Server
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144


Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Install the My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . 149

Reinstall the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152


C H A P T E R 9 I n s t a l l i n g t h e D a t a b a s e C o m p o n e n t s i n S Q L S e r v e r

OverviewThis chapter explains how to install webMethods database components in SQL Server. Database components are installed using different methods; the section headings indicate which database components are covered in each section.





1 Download the webMethods Installer from the webMethods Advantage Web site at http://advantage.webmethods.com to a machine equipped with a SQL Server database client.









Instal l the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components

Set Up Database UsersYou can create databases and database users as part of the installation process described in this section or you can have your database administrator set them up.

If you want your database administrator to set up the databases and database users, ask the database administrator to create one database and database user for each database component. Assign the database user the permissions listed in the

Component Script




Important! You might see maximum key length warnings for the IDX_SESS_SVRID, IDX_ERR_SVRID, IDX_TXIN_SVRID, and IDX_TXOUT_SVRID indices. If your Integration Server IDs will not exceed 900 bytes (300 multi‐byte characters), you can ignore this warning. If your Integration Server IDs will exceed 900 bytes, remove the indices.









mss_cmn_c_ddl_grant.sql file in the webMethods_directory\common\db\scripts\mssql\ code\common\create directory.

Download the Database ScriptsYou install the database components covered in this section using database scripts and a program called the webMethods Database Installer that are available through the webMethods Installer. Download the scripts and webMethods Database Installer as follows:

1 Download the webMethods Installer from the webMethods Advantage Web site at http://advantage.webmethods.com to a machine equipped with Windows.



Set the Database Connection Properties1 On the Windows machine, open a command window and go to the

webMethods_directory\common\db\scripts\mssql directory.

2 Start the webMethods Database Installer by running the mssql.bat program.

3 Choose View/modify database connection properties file and set these properties for each database component you are going to install:set @database_component_DBHOST='database_host'set @database_component_DBNAME='database_name'set @database_component_DBUSER='database_user'set @database_component_DBUSER_PWD='database_user_password'


Note: If you installed Manager server, you might already have asked your database administrator to set up a database user, password, and permissions for the Manager server database component before installation so you could enter the database user and password during installation.




Install the Database ComponentsYou can install the database components automatically using the webMethods Database Installer or you can install them manually. The database installer creates the user and database objects for each database component.

Install a Database Component Using the Database Installer1 Choose Install/reinstall a database component, then choose the database component to

install (for example, Analysis 6.5.1).

2 When prompted, enter the system administrator (SA) password for server database_host. Choose Component objects do not exist - proceed with creation for new database.

Install a Database Component in SQL Server Manually1 Open a command window and go to the webMethods_directory\common\

db\scripts\mssql directory.

2 If the database administrator did not create the database and database user for this database component, create the database and database user by running the commands below. The database component codes are as follows:

code\osql -U sa -P sa_password -S database_server -n -b -i code\common\create\mss_cmn_c_ddl_db_and_user_database_component_code.sql

code\osql -U sa -P sa_password -S database_server -d database -n -b -i code\common\create\mss_cmn_c_ddl_grant_database_component_code

3 Install shared database objects by running the commands below. These objects, which include functionality like metadata information and data purge, provide a foundation for use by shared by all product database components in the database.

code\osql -U sa -P sa_password -S database_server -d database -n -b -i code\common\create_cmn_mss.sql

code\osql -U sa -P sa_password -S database_server -d database -n -b -i code\operation_mgmt\create_opm_mss.sql

Database Component Code Database Component Code

Analysis ANL Archive ARC

Manager server MNS Process Audit Log PRA

Process Tracker PTR Servicenet SNT

Important! Perform this step only once per database.



code\osql -U sa -P -P sa_password -S database_server -d database -n -b -i code\databasemanagement\create_dbm_mss.sql

code\osql -U sa -P -P sa_password -S database_server -d database -n -b -i code\datamanagement\create_dtp_mss.sql

4 Install the database component by running this command:code\osql -U sa -P sa_password -S database_server -d database -n -b -i code\create_database_component_6-5_mss.sql

For example, if you want to install the Process Tracker database component on a Windows system, you would run these commands, where the SA password is test and the database name is processtracker:code\osql -U sa -P test -S localhost -n -b -i code\common\create\mss_cmn_c_ddl_db_and_user_PTR.sql

code\osql -U sa -P test -S localhost -d processtracker -n -b -i code\common\create\mss_cmn_c_ddl_grant_PTR.sql

code\osql -U sa -P test -S localhost -d processtracker -n -b -i code\common\create_cmn_mss.sql

code\osql -U sa -P test -S localhost -d processtracker -n -b -i code\operation_mgmt\create_opm_mss.sql

code\osql -U sa -P test -S localhost -d processtracker -n -b -i code\databasemanagement\create_dbm_mss.sql

code\osql -U sa -P test -S localhost -d processtracker -n -b -i code\datamanagement\create_dtp_mss.sql

code\osql -U sa -P test -S localhost -d processtracker -n -b -i code\create_processtracker_6-5_mss.sql

Complete the Installation1 For security reasons, if you installed the Analysis, Archive, Manager server, Process

Audit Log, or Process Tracker database component, remove the database user password from the database connection properties file, as follows:

a If the webMethods Database Installer is not already started, start the installer on the Windows machine by running the mssql.bat program.

b Choose View/modify database connection properties file and remove the password from the property shown below:set @database_component_DBUSER_PWD=''





3 If you installed the Archive database component, do the following:

a Use the Monitor service pub.monitor.archive:setOperationParameters to link the Archive database component to the Process Audit Log database component, the IS Core Audit Log database component, or both, depending on the data you want to archive. For instructions on using the service, see “Monitor Service pub.monitor.archive:setOperationParameters” on page 264; set the PROCESSAUDIT_DBLINK, ISCOREAUDIT_DBLINK, PROCESS_SCHEMA, and ISCORE_SCHEMA parameters on the service.

b Use the GRANT command to give the Archive database user permission to select and delete from the Process Audit Log database component, the IS Core Audit Log database component, or both, depending on the data you want to archive.

Instal l the My webMethods Server Database ComponentYou can install the My webMethods Server database component manually using one of the commands described in this section. The command you use depends on whether you are running the command from a machine that hosts My webMethods Server, Access, or Portal, or none of those. If you want to run the command from a machine that does not host any of those products, the machine must be equipped with the OSQL utility.

You can install the My webMethods Server database component in either of two ways:

If you have administrator access to the database server in which you want to install the database component, you can use the command to create a database and database user and install the database component in the new database.



Note: You can use the Portal Server Configurator to automatically install the My webMethods Server database component. For instructions, see “Complete the Access, My webMethods Server, or Portal Installation” on page 183.



If you do not have administrator access, you can ask your database administrator to create an empty database and a database user, and then use the command to install the database component in the database. The database user must be granted the db_owner and public roles on the database in addition to standard database permissions.

Before You BeginFollow the appropriate steps below.

Create the Database and Database User and Install the Database ComponentTo create a database and database user and install the My webMethods Server database component in the new database, run this command:{dbcreate.bat | dbcreate_osql.bat}database_server_host:database_server_port database administrator_user administrator_user_password database_user database_user_password y


Portal host machine Open a command window and go to the My webMethods Server, Access, or Portal_directory\bin\db\ scripts\ mssql directory.


2 Copy the mssql directory to the machine equipped with the OSSQL utility.

Parameter Entry

{dbcreate.bat | dbcreate_osql.bat}

If you are running the command from the My webMethods Server, Access, or Portal host machine, enter dbcreate.bat. If you are running the command from a machine that does not host My webMethods Server, Access, or Portal, enter dbcreate_osql.bat.

database_server_host

Name or IP address of the machine that hosts the SQL Server database server. Do not use localhost to identify the host.

database_server_port

Port the database server uses to communicate. The default port for SQL Server is 1433.



For example, the following command creates the mywebmserverdb database on the sqlserver database server, creates the mywebmserveruser database user, and installs the My webMethods Server database component in the mywebmserverdb database:dbcreate.bat sqlserver:1433 mywebmserverdb sa password mywebmserveruser mywebmserverpassword y

Install the Database Component Using an Existing Database and Database UserTo install the My webMethods Server database component in an existing database using an existing database user, run this command:{dbcreate.bat | dbcreate_osql.bat}database_server_host:database_server_port databaseadministrator_user administrator_user_passworddatabase_user database_user_password n

database Name of the database in which to install the database compo‐nent.




database_user Database user for My webMethods Server, Access, or Portal to use to communicate with the database. The database user must be unique for the database server.



y Tells the command to create a database and database user and install the database component in the new database.

Parameter Entry

{dbcreate.bat | dbcreate_osql.bat}

If you are running the command from the My webMethods Server, Access, or Portal host machine, enter dbcreate.bat. If you are running the command from a machine that does not host My webMethods Server, Access, or Portal, enter dbcreate_osql.bat.

database_server_host

Name or IP address of the machine that hosts the SQL Server database server. Do not use localhost to identify the host.

database_server_port

Port the database server uses to communicate. The default port for SQL Server is 1433.

Parameter Entry



For example, the following command installs the My webMethods Server database component in the existing database mywebmserver on the sqlserver database server, using the existing database user mywebmserveruser:dbcreate.bat sqlserverhost:1421 mywebmserver mywebmserveruser mywebmserverpassword mywebmserveruser mywebmserverpassword n

Reinstal l the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet Database Component

If you need to start over by clearing out all data from the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet database component, and you installed the database component, you can reinstall the database component using the webMethods Database Installer.

1 On the machine that hosts the database scripts and webMethods Database Installer, open a command window and go to the webMethods_directory\common\ db\scripts\mssql directory.

2 Start the webMethods Database Installer by running the mssql.bat program.

3 Choose Install/reinstall a database component, then choose the database component to reinstall (for example, Process Tracker 6.5.1).

database Name of the database in which to install the database compo‐nent.

administrator_user Enter the same value you enter for database_user.


Enter the same value you enter for database_user_password.

database_user Database user for My webMethods Server, Access, or Portal to use to communicate with the database.



n Tells the command to install the database component in an existing database using an existing database user.

Parameter Entry


C H A P T E R 10
Instal l ing the Database Components in DB2
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154


Install the Reporting and Staging Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Install the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157


C H A P T E R 1 0 I n s t a l l i n g t h e D a t a b a s e C o m p o n e n t s i n D B 2

OverviewThis chapter explains how to install webMethods database components in DB2. Database components are installed using different methods; the section headings indicate which database components are covered in each section.





1 Download the webMethods Installer from the webMethods Advantage Web site at http://advantage.webmethods.com to a machine equipped with a DB2 database client.






Install the Reporting and Staging Database Components



Instal l the Report ing and Staging Database Components

Set Up Database UsersAsk your database administrator to set up the database user, password, and permissions for each database component. Each database user must be able to select, insert, update, and delete rows from the tables in its database component.

Download the Database ScriptsYou install the database components covered in this section using database scripts and a program called the webMethods Database Installer. Both are available through the webMethods Installer. Download the scripts and webMethods Database Installer as follows:.

1 Download the webMethods Installer from the webMethods Advantage Web site at http://advantage.webmethods.com to the machine that hosts the DB2 database server.


Component Script














Set the Database Connection Properties1 On the DB2 database server host machine, go to the webMethods_directory\common\

db\scripts\db2 directory and open the db2_env_properties.{bat|sh} file in a text editor.

2 Edit these connection properties for each database component you are going to install:set database_component_DB=database_nameset database_component_USR=database_userset database_component_PWD=database_user_password


Install the Database ComponentsGo to the webMethods_directory\common\db\scripts\create directory and install the database components as follows:

Complete the InstallationFor security reasons, remove the database user password from the db2_env_properties.{bat|sh} database connection properties file.

To install this database component... Execute this script...

Reporting create_reporting_6‐5_RDBMS.sql

Staging create_staging_6‐5_RDBMS.sql


Install the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components

Instal l the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components


Download the Database ScriptsYou install the database components covered in this section using database scripts and a program called the webMethods Database Installer. Both are available through the webMethods Installer. Download the scripts as follows:

1 Download the webMethods Installer from the webMethods Advantage Web site at http://advantage.webmethods.com to the DB2 database server host machine.



Set the Database Connection Properties1 On the DB2 database server host machine, go to the webMethods_directory\common\

db\scripts\db2 directory.

2 Start the webMethods Database Installer by running this command:

ibmDB2.{bat|sh}

3 Choose View/Modify database connection properties file and set these properties for each database component you are going to install: set database_component_INSTANCE=’database_instance’set database_component_DB={’local_alias’ | ’dbase_name’}set database_component_SCHEMA=’database_schema’set database_component_USER=’operating_system_user_name’set database_component_USER_PWD=’operating_system_password’





Install the Database ComponentsYou can install the database components automatically using the webMethods Database Installer or you can install them manually. The database installer creates the database objects for each database component.

Install a Database Component Using the Database InstallerChoose Install/reinstall a database component, then choose the database component to install (for example, Analysis 6.5.1).

Install a Database Component in Oracle ManuallyOpen a command window and go to the webMethods_directory\common\ db\scripts\db2 directory. Run the scripts in the order indicated below.

Database Compo-nent Script

Analysis code/analysis/create/db2_anl_c_ddl_tables_indexes.sql

code/operation_mgmt/create/DDL_op_mgmt.sql

code/operation_mgmt/create/DML_op_mgmt.sql

code/operation_mgmt/create/operation_mgmt_get_debug_fl.db2

code/operation_mgmt/create/ operation_mgmt_get_parameter.db2

code/operation_mgmt/create/ operation_mgmt_log_operation_event.db2

code/databasemanagement/cre‐ate/db_mgmt_modify_fk_constraints_table.db2


code/databasemanagement/cre‐ate/db_mgmt_modify_fk_constraint.db2


code/databasemanagement/cre‐ate/db_mgmt_modify_fk_constraints_all.db2

code/datamanagement/create/data_mgmt_purge_data.db2



ProcessTracker code/processtracker/create/db2_ptr_c_ddl_tables_indexes.sql

code/operation_mgmt/create/DDL_op_mgmt.sql

code/operation_mgmt/create/DML_op_mgmt.sql

code/operation_mgmt/create/operation_mgmt_get_debug_fl.db2

code/operation_mgmt/create/ operation_mgmt_get_parameter.db2

code/operation_mgmt/create/ operation_mgmt_log_operation_event.db2



code/databasemanagement/cre‐ate/db_mgmt_modify_fk_constraint.db2


code/databasemanagement/cre‐ate/db_mgmt_modify_fk_constraints_all.db2

code/datamanagement/create/data_mgmt_purge_data.db2

ProcessAudit code/processaudit/create/metadata_tables.sql

code/processaudit/create/runtime_tables.sql

code/processaudit/create/processrecent_table.sql

code/processaudit/create/processrecent_triggers.sql

code/processaudit/create/fieldalias_triggers.sql

ManagerServer code/managerserver/create/db2_mgr_c_ddl_tables_indexes.sql




Complete the Installation1 For security reasons, remove the database user password from the database

connection properties file, as follows:

a If the webMethods Database Installer is not already started, start it by running this command:ibmDB2.{bat|sh}

b Choose View/Modify database connection properties file and and remove the password from the property shown below: set database_component_USER_PWD=



3 If you installed the Archive database component, use the GRANT command to give the Archive database user permission to select and delete from the Process Audit Log

Archive code/processaudit/create/metadata_tables.sql

code/processaudit/create/runtime_tables.sql

code/processaudit/create/processrecent_table.sql

../create/create_iscoreaudit_6‐5_DB2.sql

code/archive/create/db2_opmgmt_c_ddl_tables_indexes.sql

code/archive/create/db2_arc_c_ddl_tables_indexes.sql

code/archive/create/db2_arc_c_dml_parameters.sql






database component, the IS Core Audit Log database component, or both, depending on the data you want to archive.


C H A P T E R 11
Instal l ing the Database Components in Sybase
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164


Install the Archive, Process Audit Log, Reporting, and Staging Database Components . . 166


C H A P T E R 11 I n s t a l l i n g t h e D a t a b a s e C o m p o n e n t s i n S y b a s e

OverviewThis chapter explains how to install webMethods database components in Sybase. Database components are installed using different methods; the section headings indicate which database components are covered in each section.





1 Download the webMethods Installer from the webMethods Advantage Web site at http://advantage.webmethods.com to a machine equipped with a Sybase database client.






Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, Reporting, Staging, and Trading Networks Database Components



Component Script












Instal l the Archive, Process Audi t Log, Report ing, and Staging Database Components


Download the Database ScriptsYou install the database components covered in this section using database scripts and a program called the webMethods Database Installer. Both are available through the webMethods Installer. Download the scripts and webMethods Database Installer as follows:

1 Download the webMethods Installer from the webMethods Advantage Web site at http://advantage.webmethods.com to a machine equipped with a Sybase database client.



Set the Database Connection Properties1 On the Sybase database client machine, go to the webMethods_directory\common\

db\scripts\sybase directory and open the sybase_env_properties.{bat|sh} file in a text editor.

2 Edit these connection properties for each database component you are going to install:set database_component_DB=database_nameset database_component_USR=database_userset database_component_PWD=database_user_password


Important! Database names are case sensitive. You must use the right casing for the database name in the connection properties or the installation will fail.



Install the Archive, Process Audit Log, Reporting, and Staging Database Components

Install the Database Components1 Install the database components as follows:

2 If you installed the Archive database component, and the Process Audit Log and IS Core Audit Log database components are in a different database from each other, create the IS Core Audit Log driver tables in the IS Core Audit Log database component by navigating to the webMethods_directory\common\db\scripts\sybase\ code\archive\create directory and executing the SQL script sybase_arc_c_ddl_tables_indexes.sql.

Complete the Installation1 For security reasons, remove the database user password from the

sybase_env_properties.{bat|sh} database connection properties file.

2 If you installed the Process Audit Log database component, define a JDBC connection pool for Integration Server to use to communicate with the database component. For instructions, see “Identify the Databases that Contain the Cross‐Reference, Document History, IS Core Audit Log, Process Audit Log, Reporting, and Staging Database Components” on page 170.

To install this database component... Do this...

Archive Go to the webMethods_directory\common\db\scripts\ sybase directory and run the create_archive_6.5.{bat|sh} program.

Process Audit Log Go to the webMethods_directory\common\db\scripts\ sybase directory and run the create_processaudit_6.5.{bat|sh} program.

Reporting Go to the webMethods_directory\common\db\scripts\ create directory and execute the create_reporting_6‐5_sybase.sql script.

Staging Go to the webMethods_directory\common\db\scripts\ create directory and execute the create_staging_6‐5_sybase.sql script.

Note: Manager and Optimize automatically create a JDBC connection pool to use to communicate with the Process Audit Log database component when you start the Manager and Optimize controller. The information required to create the connection pools was supplied during product installation.


C H A P T E R 12
Ident i fy ing Databases for Use by Products
Identify the Databases that Contain the Cross-Reference, Document History, IS Core Audit Log, Process Audit Log, Reporting, and Staging Database Components . . . . . . . . . . . . . . 170

Identify the Database for the Process Tracking Store Database Component . . . . . . . . . . . 175

Identify the Database for the Modeler Repository Database Component . . . . . . . . . . . . . . 177


CHAPTER12 Identifying Databases for Use by Products

Ident i fy the Databases that Contain the Cross-Reference, Document History, IS Core Audit Log, Process Audit Log, Report ing, and Staging Database Components

The Integration Server audit subsystem uses JDBC connection pools to communicate with the database components for its Cross‐Reference, Document History, IS Core Audit Log, and Process Audit Log functions. Monitor built‐in services use JDBC connection pools to communicate with the Reporting and Staging database components. Manager server and Trading Networks Server use JDBC connection pools to communicate with their database components.

A JDBC connection pool identifies a database in which to store data and specifies pool parameters, such as minimum and maximum connections. After you define a connection pool, you link the appropriate function to that connection pool. For example, you would define a connection pool that identifies the database that contains the Process Audit Log database component, then link the Process Audit Log function to that connection pool. Multiple functions can use the same connection pool. For example, if you installed the IS Core Audit Log and Document History database components in the same database, you could link both functions to the same connection pool. When multiple functions share a connection pool, Integration Server creates a separate instance of the connection pool for each database component at run time.

Below are guidelines for when you are using multiple Integration Servers.

If you want to use Monitor to view the IS Core Audit Log data of multiple Integration Servers, the Integration Servers must store their IS Core Audit Logs in a single IS Core Audit Log database component. If you want to use Monitor to view the Process Audit Log data of multiple Integration Servers, the Integration Servers must store their Process Audit Logs in a single Process Audit Log database component.

If you have a cluster of Integration Servers, all Integration Servers in the cluster must store their Document History data in a single Document History database component.

Note: You might have already defined and linked a connection pool for Manager server and Trading Networks Server during product installation.


Identify the Databases that Contain the Cross-Reference, Document History, IS Core Audit Log, Process Audit Log, Reporting, and Staging Database Components

Define a Connection Pool1 In Integration Server Administrator, go to the Settings JDBC Pools page.

2 Click Create a new Pool Alias Definition and complete the boxes that appear as follows:

Box Entry

Alias Name Alias for the connection pool. The alias can include only characters that are valid for a file name in your operating system.

Alias Description

Description for the connection pool.

Associated Driver Alias

Alias for the driver to use. The list contains predefined aliases for the JDBC driver that webMethods supplies with Integration Server for each type of supported database.

Database URL URL for the database that contains one or more database components, as follows:

URLDefault Port


1521


1521


1433


5000



DB2 UDBjdbc:wm:db2://host_or_IPaddress:port;databaseName=database_name;PackageName=package_name;

For the Archive, Reporting, and Staging database components:BatchPerformanceWorkaround=true

50000


For the Archive, Reporting, and Staging database components:BatchPerformanceWorkaround=true

Note: AlternateId must match the schema in which you created the logging database tables.

446

User Id Database user for Integration Server to use to communicate with the database.

Password Password for the database user.

Minimum connections

Minimum number of connections the connection pool must keep open at all times.

If you use this pool alias for more than one function, each connection pool instance keeps the specified number of connections open. For example, if you specify that you want at least 3 connections kept open, and the IS Core Audit Log and the Document History table both use this connection pool, the connection pool keeps a total of 6 connections open ‐ 3 for the IS Core Audit Log connection pool instance and 3 for the Document History table connection pool instance.

If your logging volume has sudden spikes, you can improve performance by making sure the connections needed to handle the increased volume open quickly. You can minimize connection startup time during spikes by setting this value higher, so that more connections remain open at all times.

Box Entry


Identify the Databases that Contain the Cross-Reference, Document History, IS Core Audit Log, Process Audit Log, Reporting, and Staging Database Components

3 Click Save Settings.

Maximum connections

Maximum number of connections the connection pool can have open at one time.

Calculate this value as part of the total possible number of connections that could be opened simultaneously by all functions and applications that write to the database. Make sure the total number does not exceed the database’s connection limit. If one of the applications opens more connections than the database allows, the database will reject subsequent requests for connections from any application.

Suppose the database’s connection limit is 40 connections. If the IS Core Audit Log and the Document History table both use this connection pool, you could safely specify 20 as the maximum number of connections for the connection pool. The IS Core Audit Log connection pool instance could use up to 20 connections and the Document History table connection pool instance could use up to 20 connections. (If you are using Monitor, Monitor would use connections from the IS Core Audit Log connection pool instance.)

However, if Trading Networks also writes to the database and has a connection pool that could open up to 5 connections, you could specify only 17 as the maximum number of connections for the current connection pool. The IS Core Audit Log connection pool instance could use up to 17 connections, the Document History table connection pool instance could use up to 17 connections, and the Trading Networks connection pool could use the remaining 5 connections.

You must coordinate the value for the temporary store property watt.server.auditMaxPool with this value. For instructions, see the webMethods Logging Guide.

Idle timeout Period of time, in milliseconds, the connection pool can keep an unused connection open. After the specified period of time, unused connections that are not needed to satisfy the Minimum connections value are closed.

If your logging volume has sudden spikes, you can improve performance by making sure the connections needed to handle the increased volume open quickly. You can minimize connection startup time during spikes by setting this value higher, so that more connections remain open at all times.

Box Entry



Link a Function to a Connection PoolEach function has a predefined functional alias. To link a function to a connection pool, you associate the appropriate functional alias with the pool alias. The functional aliases are as follows:

1 In Integration Server Administrator, go to the Settings > JDBC Pools page.

2 In the Functional Alias Definitions area, scroll right to locate the Edit Association column for a functional alias and click Edit in that column.

3 In the Associated Pool Alias list, click the pool alias to link to the functional alias.

4 Click Save Settings. Integration Server Administrator returns to the Settings > JDBC Pools page.

5 Initialize the connection pool. In the Functional Alias Definitions area, scroll right to locate the Restart Function column for the functional alias and click Restart in that column.

6 Make sure Integration Server can connect to the database. In the Functional Alias Definitions area, locate the Test column for the functional alias and test the connection by clicking .

7 If you have not yet configured Integration Server to write logging and cross‐reference data to a database, go to “Configure Integration Server to Write Cross‐Reference, IS Core Audit Log, and Process Audit Log Data to a Database”, below. Otherwise, restart Integration Server.

Function Functional Alias

Cross‐Reference Xref

Document History DocumentHistory

IS Core Audit Log ISCoreAudit

Manager server Manager

Process Audit Log ProcessAudit

Reporting Reporting

Staging Staging

Trading Networks Server TN


Identify the Database for the Process Tracking Store Database Component

Configure Integration Server to Write Cross-Reference, IS Core Audit Log, and Process Audit Log Data to a DatabaseBy default, Integration Server writes Cross‐Reference, IS Core Audit Log, and Process Audit Log data to flat files. You must configure Integration Server to write the data to databases instead.

1 In Integration Server Administrator, go to the Settings > Extended page and click Show and Hide Keys. Integration Server Administrator displays a list of Integration Server configuration properties you can change using Integration Server Administrator.

2 Select the check boxes next to the properties watt.server.auditStore and watt.server.xref.type.

3 Click Save Changes. Integration Server Administrator displays the selected properties in the Extended Settings box.

4 Click Edit Extended Settings. In the Extended Settings box, set the properties as follows:watt.server.auditStore=databasewatt.server.xref.type=jdbc

5 Click Save Changes.

6 Restart Integration Server.

Ident i fy the Database for the Process Tracking Store Database Component

For each PRT cluster that will run processes that will store data in the Process Tracking Store database component, you must configure the Process Tracking Store properties.

1 Start an Integration Server that hosts a PRT in the PRT cluster. Open the home page for the PRT on that Integration Server by entering http://Integration Server_host:Integration Server_port/WmPRT in a browser.

2 In the Central Process Tracking Store box, indicate whether the PRT should store process status and global data in a central or distributed Process Tracking Store while steps run. With a central store, all PRTs store the data in a single, central Process Tracking

Important! By default, the PRT writes process status data to RAM. To have the PRT write process status data to the Process Tracking Store instead, you set properties on individual process models. For detailed instructions, see the webMethods Process Run Time User’s Guide.

Note: If at any time you need to revert to the default settings for the PRT home page, click Default on that page.



Store database component. With a distributed store, each PRT stores the data to its own Process Tracking Store database component. Decide which to use as follows:

3 When you use a central store, all process completion data is stored in the central Process Tracking Store database component. When you use a distributed store, process completion data is distributed among multiple Process Tracking Store database components; you must therefore designate one PRT to track process completion data for all PRTs. Indicate in the Process Completion Tracking Server box whether you want this PRT to serve in that capacity.

4 Specify Process Tracking Store database settings, as follows:

5 Each PRT uses a JDBC connection pool to communicate with the Process Tracking Store database component. In the Associated Pool Alias list, click the alias for the JDBC connection pool this PRT should use.

Use this type of store...

Central When using a single PRT to run processes

When using a cluster of PRTs to run processes that do not span geographically dispersed servers, and the connections of the PRTs to the Process Tracking Store database component are very reliable

Distributed When using a cluster of PRTs to run processes that span geographically dispersed servers

When using a cluster of PRTs whose connections to Process Tracking Store database components are unreliable

In this box... Specify...

Database Connection Retries

Maximum number of times the PRT should try to connect to the Process Tracking Store database component. After the maximum is reached, the PRT throws exceptions. You will not be able to run any more processes until you restart the PRT.

Database Connection Retry Time Interval

Period of time, in seconds, the PRT should wait between connection retries.

Database Cleanup Interval

Frequency, in seconds, with which the PRT should remove data about completed processes from the Process Tracking Store database component.

Clean the database often enough to keep data from straining the database size limit, but not so often as to degrade performance. The default of 10 minutes should be optimal for most situations.


Identify the Database for the Modeler Repository Database Component

By default, the PRT uses the same pool alias that Integration Server uses to communicate with the Process Audit Log database component, but the Process Tracking Store and Process Audit Log database components might not be installed in the same database. You can choose a different pool alias. If you need to define a new pool alias, see “Define a Connection Pool” on page 171.

6 If you are done, click Submit, then reload the WmPRT package or restart the host Integration Server.

7 Repeat these steps for every PRT in the cluster. Configure the settings for each PRT in a way that will allow them to function as an interconnected unit. For example, if you want to use a central Process Tracking Store, set all PRTs in the cluster to use the central Process Tracking Store and the same JDBC connection pool alias. Similarly, if you want to use a distributed Process Tracking Store, set all PRTs in the cluster to use a distributed Process Tracking Store, set each PRT to use a different JDBC connection pool alias, and designate one and only one PRT to serve as the Process Completion Tracking Server.

Ident i fy the Database for the Modeler Repository Database Component

1 Open the Modeler Design Package home page by entering http://server_host:server_port/WmModeler in a browser, where server_host and server_port identify the Integration Server that hosts the Modeler Design Package.

2 Set the properties listed below.

Important! You might have installed the Process Tracking Store and the Process Audit Log in separate databases or schemas if you applied WmPRT_6‐5‐1_Fix1. If you did not apply the fix, you must have installed the database components in the same database or schema, and Integration Server and the PRTs must all use the same JDBC connection pool to access the Process Tracking Store and Process Audit Log database components.

Property Value

Server Host

Name of the machine that hosts the Modeler Repository. The Modeler Design Package includes the Modeler Repository, so identify the machine that hosts the Integration Server that hosts the Modeler Design Package.

Port Port used by the Modeler Repository. By default, the port is 7778.

Storage Method

Specify Database as the storage method.



URL URL for the database that contains the Modeler Repository database component, as follows:

URLDefault Port


1521


1433


50000

User Database user for the Modeler Repository to use to communicate with the database.

Password Password for the database user.

JDBC Driver

JDBC driver name for the database, as follows:

Database Driver Name

Oracle com.wm.dd.jdbc.oracle.OracleDriver

SQL Server com.wm.dd.jdbc.sqlserver.SQLServerDriver

DB2 UDB com.wm.dd.jdbc.db2.DB2Driver

Classpath Path to the JDBC driver for the database.

Log File Name

Relative path to the directory in which to store log files. The default is JDBCData.log.

Property Value


P A R T V
Complete the Instal lat ion
Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181


C H A P T E R 13
Complet ing the Instal lat ion
Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Configure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Complete the Access, My webMethods Server, or Portal Installation . . . . . . . . . . . . . . . . . 183

Complete the webMethods Broker Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Complete the Deployer Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Complete the Integration Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Complete the Installation for Manager, Optimize, or Both . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Complete the Modeler Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Complete the Monitor Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198f

Complete the Servicenet Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Complete the Workflow Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Connect Products to Each Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Redirect Products to Use a Non-Default JRE or JDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Complete the Installation for Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234


C H A P T E R 1 3 C o m p l e t i n g t h e I n s t a l l a t i o n

Post- Instal lat ion Checkl istThe checklist below identifies tasks you need to perform to make a basic installation of webMethods products operational. Subsequent sections in this chapter or book provide detailed instructions. Sections in this chapter also provide detailed instructions for other tasks you might want or need to perform.

Product Task Page

Access, My webMethods Server, Portal

Run the Portal Server Configurator 183

webMethods Broker

If created Broker Server using installer:

Make sure Broker Server is running and default Broker exists 189

Adjust per‐process thread and kernel limits on HP‐UX 190

If did not create Broker Server using installer, create Broker Server and perform other tasks using commands

267

Deployer If installed on pre‐6.5 Integration Server, or on 6.5 Integration Server and using non‐default JDK, install JCE Unlimited Strength Jurisdiction Policy Files

191

Configure communication with source and target webMethods products; see webMethods Deployer User’s Guide

Integration Server

Start Integration Server and open Integration Server Administrator

191

Identify compiler for Developer‐generated Java code 191

If installed 64‐bit JVM on 64‐bit Solaris or HP‐UX, configure Integration Server to use JVM

192

If using non‐default JDK, install JCE Unlimited Strength Jurisdiction Policy Files

192

Manager, Optimize

On UNIX or Linux, create Manager/Optimize user 196

Modeler Make sure installed Modeler Design Package and PRT on Integration Server

196

On UNIX or Linux, give users proper permissions 197

Define logical servers for process steps and map to Integration Servers or Workflow Servers

197

Monitor Set up authentication to run Monitor services 198

Install SVG plug‐in 198


Configure Logging

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

Complete the Access, My webMethods Server, or Portal Instal lat ion

Configure the Server and DatabaseAfter you install a product that requires and is installed with My webMethods Server, you must run the Portal Server Configurator to configure My webMethods Server. If you installed Access or Portal, you use the configurator to configure a default server; your portal administrator can later configure additional servers.

You can also use the configurator to install the My webMethods Server database component to which My webMethods Server, Access, and Portal write, or you can install the database component manually. If you want to install manually, you must do so before you run the configurator. For instructions on installing manually, see “Install the My webMethods Server Database Component” on page 138.

To use the configurator on a UNIX or Linux system, the system must have an X‐Windows environment.

Servicenet Perform tasks on checklist 199

Workflow Set up Workflow database component 213

If installed secondary Workflow Servers, configure to access encryption passwords

213

Run Workflow configurator 215

If Workflow will use SSL, configure as necessary 224

Most products

Configure communication between My webMethods Server and other webMethods products

229

Product Task Page

Note: Whether you install My webMethods Server, Access, or Portal, the name of the configurator is always Portal Server Configurator, and the labels on the configurator panels always use the name Portal.



Before You BeginIf you are going to install manually, use the instructions in the webMethods Database Guide. If you are going to install the My webMethods Server database component using the configurator, do the following:

If you are installing in Oracle, set the NLS_LENGTH_SEMANTICS initialization parameter to BYTE.

Make sure the database server is running so the configurator can connect to it. You can install the database component in either of two ways:

If you have administrator access to the database server in which you want to install the database component, you can use the configurator to create a tablespace (Oracle) or database (SQL Server) and database user and then install the database component in the new tablespace or database.

If you do not have administrator access, you can ask your database administrator to create an empty tablespace (Oracle) or database (SQL Server) and a database user, and then use the configurator to install the database component in the tablespace or database. The database user must have CONNECT, RESOURCE, CREATE VIEW, and GLOBAL QUERY REWRITE permissions.

Start the ConfiguratorRun the configurator on the machine on which you installed My webMethods Server, Access, or Portal. If you installed using the webMethods Installer wizard, the installer automatically starts the configurator when installation is complete. If you installed using the webMethods Installer console mode, you must start the configurator manually by entering this command:webMethods_directory/Portal/tools/configurator/run.{bat | sh}

If you are configuring My webMethods Server alone, the configurator displays the General tab. If you are configuring Access or Portal, the configurator displays the New Server Instance tab. This tab lets you create servers. Since you are configuring the default Access or Portal server, click Next. In New Portal Server Instance Name field, type a name for the default server or accept the default name (default). Click Next. The configurator displays the General tab.


Complete the Access, My webMethods Server, or Portal Installation

Set General Parameters1 Complete the General tab as follows:

2 Click Next. If you are configuring Access or Portal, the configurator displays the Components tab; see “Select Portal Components to Deploy”, below. If you are configuring My webMethods Server alone, the configurator displays a tab labeled MSSQL or Oracle, depending on the database server you identified in the Database server type list on the General tab; see “Install the My webMethods Server Database Component” on page 187.

Select Portal Components to Deploy1 On the Components tab, select the Access or Portal components you want the

configurator to deploy when it initializes the default server.

Box Entry

Database server type

Type of database server in which you are going to install the My webMethods Server database component.

Database Server Option

SQL Server mssql

Oracle oracle

Messaging provider type

If you are configuring Access or Portal, indicate whether the default server is to use JMS to communicate with other servers in a cluster. Accept the default entry none.

Note: If your portal administrator is going to create a cluster of Access or Portal servers, he will change this entry later.

Web server type

If you are configuring Access or Portal, type of Web server for the default server to use. Accept the default entry internal to use the Jetty Web server that comes with the server.

Note: If your portal administrator is going to create a cluster of Access or Portal servers, he will change this entry later.

Important! webMethods recommends that you accept the set of components that are selected by default. Because the absence of components can lead to loss of necessary functions, only an experienced portal administrator should try to configure a server with less than the default component set.



2 Click Next. The configurator displays a tab labeled MSSQL or Oracle, depending on the database server you identified in the Database server type list on the General tab.

Component Group Deploys portlets that...

Portal Services Provide a variety of services, including subscriptions and notifications, version control, and support for directory services.

Administration Components

Let you perform administrative tasks on Access or Portal services, such as portal analysis, configuration, and content management.

Default Components

Provide basic elements of the Access or Portal user interface and let you manage communication between portals and external resources, such as WebDAV or FTP servers.

Default Content Provide default webMethods content for portals.

Portal Development

Help you develop portlets. Includes the Portlet Developer you can install as a plug‐in to Eclipse.

Samples Provide samples and demonstrations of portal technology. All sample include full source code.

Extras Add capabilities to a portal page or enable the proper functioning of other portlets.

Mobile UI Support

Support the delivery of HTML pages to mobile devices.


Complete the Access, My webMethods Server, or Portal Installation

Install the My webMethods Server Database Component1 Complete the MSSQL or Oracle tab as follows:

Box or Area Setting

Initialize Portal Database

Indicates whether to:

Create a tablespace (Oracle) or database (SQL Server) and database user and then install the My webMethods Server database component in the tablespace or database (option 1)

Install the My webMethods Server database component in an existing tablespace or database using an existing database user (option 2)

Use the My webMethods Server database component you installed manually before running the configurator (option 3)

database_server Host/Port

In the box on the left, name or IP address of the machine that hosts the database server. Do not use localhost to identify the host.

In the box on the right, port the database server uses to communicate. The default port for Oracle is 1521 and for SQL Server is 1433.

Portal database User name

Database user for the server to use to communicate with the database. If you are creating the database user (as opposed to using an existing one), the database user must be unique for the database server.

Portal database User password


Oracle instance system identifier (SID) (Oracle)

SID for the Oracle instance on the database server host machine for the My webMethods Server database component.

database_server administrator name

If you are creating a tablespace (Oracle) or database (SQL Server), administrator user for the database server. If you are using an existing tablespace, enter the same value you enter for Portal database User name.

database_server administrator password

If you are are creating a tablespace (Oracle) or database (SQL Server), administrator password for the database server. If you are using an existing tablespace, enter the same value you enter for Portal database User password.



2 Click Next. The configurator takes the appropriate action, then displays the Portal tab.

Initialize the Server1 Complete the Portal tab as follows:

2 Click Next. The configurator initializes the server by running a script in a separate window. If you are configuring Access or Portal, the configurator displays the Summary tab.

Portal database name (SQL Server)

Name of the database for the My webMethods Server database component.

Portal Tablespace(s) name (Oracle)

Name of the tablespace for the My webMethods Server database component.

Box Entry

Jetty HTTP Listener Host/Port

In the box on the right, HTTP port number for the server. The default port is 8080.

Note: The host box on the left is not available because the Jetty Web server must be on the local host.

If an application with an HTTP listener is already using port 8080, you should change the Jetty HTTP Listener port number to avoid possible conflicts.

Portal RMI Listener Host/Port

In the box on the right, port number on the local computer where the RMI registry is maintained. The default port is 1097.

Note: The host box on the left is not available because the RMI listener must be on the local host.

Default log level

Level of detail you want the server to include in its log messages.

Box or Area Setting

Note: The script might take up to an hour to run.


Complete the webMethods Broker Installation

Finish Portal Server ConfigurationThe Summary tab displays a summary of the configuration entries you provided for the default server. To complete the configuration, do the following:

1 Click Finish. The configurator displays a completion window.

2 If the default server is on a Windows system, indicate whether you want to run it as a Windows application or as a Windows service, based on the following:

3 When asked whether you want to automatically open the server page in a browser window, click Yes. The configurator starts the server.

4 Exit the configurator by clicking the File menu, then clicking Exit.

Install the Portlet DeveloperIf you want to install the Portlet Developer, see the webMethods Portal Design Guide for instructions.

Complete the webMethods Broker Instal lat ion

Make Sure the Broker Server is Running and the Default Broker ExistsOn most systems, after installation, Broker Monitor automatically starts Broker Server, which begins running with a default Broker. Use the broker_status command to make sure the Broker Server is running and the default Broker exists, as follows:

If you want ... Configure as...

To start and shut down the default server manually. Typically, you would install a development server as an application.

Application. Click Start webMethods Portal Server.

The default Portal server to start and shut down automatically when you start and shut down your system. Typically, you would install a produc‐tion server as a service.

Service. Click Install webMethods Portal Server as a Windows Service. In a separate window, the configurator changes the server to a Windows service. Click Start webMethods Portal Windows Service.

Important! Complete this section if you configured the Broker Server using the installer as described in “Configure webMethods Broker” on page 113. Otherwise, see Appendix C, “Create the Broker Server Configuration Manually” for instructions on configuring the Broker Server.



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

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

The exception is on Windows 2003 systems that are running Terminal Services. If you installed webMethods Broker on such a system, Broker Monitor cannot start Broker Server until you give Broker Monitor the location of the shared Windows system directory that contains the Broker Monitor configuration file. (A Windows 2003 system running Terminal Services provides Broker Monitor with the location of the private Windows system directory.) Set the WMBROKERMONITOR_CONFIG environment variable to the webMethods Broker configuration directory (by default, webmethods) in the shared Windows system directory. For example, if the shared Windows system directory is C:\Windows, set the variable to C:\Windows\webmethods.

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

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

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

Run this command:chdev -l sys0 -a fullcore=true

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

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


Complete the Deployer Installation

Complete the Deployer Instal lat ion

Apply Fixes for Modeler 6.1.5If you are going to deploy from 6.1.5 Modeler Design servers (that is, Integration Servers equipped with Modeler Design Package 6.1.5), you might need to apply Modeler_6‐1‐5_Fix26.

If one or more of your Modeler Design servers are on HP‐UX or Linux systems, the fix solves problems with the way Modeler Design servers work on UNIX or Linux machines running in a ʺheadlessʺ environment.

If you want to deploy process models that include Workflow steps, the fix enables Deployer to deploy the Integration Server items that are associated with Workflow process steps.

Install JCE Unlimited Strength Jurisdiction Policy FilesIf you installed Deployer on a pre‐6.5 Integration Server, or if you installed Deployer on a 6.5 Integration Server and are using a JDK other than the JDK installed by the installer, your JVM must contain the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files for that JVM version. Deployer needs these files to run its command line scripts.

You can download the JCE files for a Sun or Hewlett‐Packard JDK from the Sun Web site at http://java.sun.com/j2se/1.4.2/download.html. You can download the JCE files for an IBM JDK from the IBM site at http://www.ibm.com/developerworks/java/jdk/security/index.html. Install the files using the instructions in the vendor documentation.

Complete the Integrat ion Server Instal lat ion

Direct Integration Server to Compiler to Use for DeveloperIf you want Integration Server to use a JDK other than the default JDK to compile Java services developed using Developer, put the JDK in your system path or, if you want to use the JDK for Integration Server only, follow the steps below.

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

2 Open Integration Server Administrator by entering this URL in an Internet browser:http://Integration Server_host:Integration Server_port

The default port for Integration Server is 5555.


http://java.sun.com/j2se/1.4.2/download.html


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

4 Go to the Settings Extended page and click Show and Hide Keys. Integration Server Administrator lists Integration Server configuration properties you can change using Integration Server Administrator.

5 Select the check box next to the watt.server.compile property and the watt.server.compile.unicode property, then click Save Changes. Integration Server Administrator displays the selected properties in the Extended Settings box.

6 Click Edit Extended Settings. In the Extended Settings box, set the properties as follows:

watt.server.compile=JDK_directory/bin/javac -classpath {0} -d {1}{2}

watt.server.compile.unicode=JDK_directory/bin/javac-encoding Unicode -classpath {0} -d {1}{2}

The location of the JDK 1.4.2 that is automatically installed by the installer is webMethods\jvm\win142.



Configure Integration Server to Use a 64-Bit JVM on Solaris and HP-UX SystemsIf you installed a 64‐bit JVM on a 64‐bit AIX system, Integration Server will use the JVM automatically. If you installed a 64‐bit JVM on a 64‐bit Solaris or HP‐UX system, you must configure Integration Server to use the JVM.

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

2 Uncomment the JAVA_D64 parameter.


Install JCE Unlimited Strength Jurisdiction Policy FilesIf you are using a JDK other than the JDK installed by the installer, your JVM must contain Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 1.4.2. Integration Server needs these files to be able to encrypt and decrypt SSL certificates.

You can download the JCE files for a Sun or Hewlett‐Packard JDK from the Sun Web site at http://java.sun.com/j2se/1.4.2/download.html. You can download the JCE files for an IBM JDK from the IBM site at http://www.ibm.com/developerworks/java/jdk/security/index.html. Install the files using the instructions in the vendor documentation.


http://java.sun.com/j2se/1.4.2/download.html

Complete the Integration Server Installation

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

Change Permissions on UNIX, Linux, OS/400, and Mac OS X SystemsIf you installed Integration Server on a UNIX, Linux, OS/400, or Mac OS X system and non‐root users will be running Integration Server, you might want to change the ownership of the installed files to allow a single non‐root user to run Integration Server (chown), change the file group to the group of users who will run Integration Server (chgrp), or change file permissions to allow all users to run Integration Server (chmod).

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

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

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

b Shut down Integration Server.

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

Save and close the file.

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



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

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

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

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

d Save and close the file.

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

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

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

Package Contents

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

WmAdminResource Services that Administrator uses to retrieve information about resources (for example, packages) installed on Integration Server.

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

WmOmiAgent Services that the Manager server uses to connect to and manage Integration Server and Trading Networks Server.

Services that are required by the WmART package.


Complete the Integration Server Installation

If you need more information on any of these packages, see the webMethods Integration Server Administrator’s Guide.

2 Start Integration Server.

3 The WmOmiAgent package is dependent on the WmOmiIs package. If you want to disable the WmOmiIS package but you want to use the WmOmiAgent package, you must first remove the dependency using the steps below or the WmOmiAgent package will not load.

a Start Developer, as follows:

b In the Navigation panel on the left side of the interface, right‐click the WmOmiIs package, then click Open.

c On the Settings tab, in the Package dependencies area, click the WmOmiAgent row.

d Click . Developer removes the WmOmiAgent package’s dependency on the WmOmiIs package.

4 In Integration Server Administrator, go to the Packages Management page.

5 Disable each package you do not need. To do so, locate the row for the package in the table, then click Yes in the Enabled column in that row. The Yes changes to No.

WmOmiIs Services that the Manager server uses to manage adapters installed on Integration Server.

Services that are required by the WmART package.

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

Package Contents

Important! If you are going to use the WmART package, you cannot disable the WmOmiAgent package or the WmOmiIs package.

System Action

Windows On the Start menu, go to Programs webMethods webMethods Developer.

Linux Go to the Developer_directory/bin directory and run the developer.sh script.

Important! Do not disable the WmRoot or WmPublic packages.



Complete the Instal lat ion for Manager, Opt imize, or Both

Create the Manager/Optimize User and Enable Automatic Start and Shut Down on UNIX or Linux Systems

Perform the steps below on the controller host machine, the data handler host machine, and each satellite host machine.

1 Log on to the host machine as the root user.

2 Create a group named “webm,” then create a user account named “webmbam” within the webm group. Grant the webmbam user ownership of all controller, data handler, or satellite‐related software by navigating to the Manager/Optimize installation directory and entering this command:chown -R webmbam:webm webmbam

3 Go to the directory listed below and deploy the run command (RC) scripts that enable automatic start and shut down of the specified item by running the indicated shell scripts.

Complete the Modeler Instal lat ion

Make Sure Modeler Design Package and PRT are InstalledIn a development environment, you can install Modeler by itself on a machine and create process models. When you want to share the process models with other users, however, you must connect the Modeler machine to your network so it can communicate with the Integration Server that is equipped with the Modeler Design Package and the PRT. To check whether an Integration Server has these packages, open Integration Server Administrator, go to the Packages Management page, and look for the WmModeler and WmPRT packages. If the package is disabled, enable it. To do so, locate the row for the package in the table, then click Yes in the Enabled column in that row. The Yes changes to No.

Important! Only perform the steps in this section once for Manager and Optimize. If you install Manager and later install Optimize (or vice versa), do not perform the steps again when you install the second product.

Item Optimize Directory Shell Script

Controller controller/bin controller_rc_deploy.sh

Data handler datahandler/bin datahandler_rc_deploy.sh

Satellites satellite/bin satellite_rc_deploy.sh


Complete the Modeler Installation

Give Users Proper Permissions on Linux SystemsIf you installed Modeler on a Linux system, give any user who is going to run Modeler these permissions:

If you are using Modeler with a Workflow client, also give the users these permissions:

If you installed the Modeler Repository on a UNIX or Linux system, give any user who is going to start the Modeler Repository these permissions:

Define Logical Servers and Map to Integration ServersProcess steps run on Integration Servers or Workflow Servers. When a Modeler user defines a process model, he must assign each process step to run on a particular Integration Server or Workflow Server. However, the user makes the assignment indirectly; he assigns each step to an alias that maps to an Integration Server or Workflow Server. These aliases are called logical servers. The use of logical servers means that you can redirect steps to run on different Integration Servers or Workflow Servers whenever necessary simply by changing logical server mappings, as opposed to modifying process model step assignments.

To map logical servers to Integration Servers or Workflow Servers, open Integration Server Administrator for the Integration Server that is equipped with Administrator. Go to the Logical Servers Add Logical Servers page. Define logical servers and map them to Integration Servers or Workflow Servers. Name the logical servers intuitively (for example, Accounting Server); you cannot change these names later. For complete instructions on defining logical servers, see the webMethods Modeler User’s Guide.

Directory or File Permissions

Modeler installation directory Write permission

Modeler_directory/bin/modeler.sh Execute permission


Modeler_directory/lib/setup.sh Read/write/execute permission


webMethods_directory/Servers/RepoV3 Write permission, to create a logs directory

webMethods_directory/Servers/ RepoV3/WmRepository

Read/write permission, to create a flat file for Modeler Repository to write to

webMethods_directory/Servers/RepoV3/runreposerver.sh

Execute permission



Complete the Monitor Instal lat ion

Set Up Authentication to Run Monitor ServicesWhen you install Monitor, the installer automatically installs the Common Authentication package on the Integration Server that hosts the Monitor services. This package makes it possible for My webMethods Server to authenticate My webMethods users who are trying to run Monitor services on Integration Server. Follow these steps:

1 Open Integration Server Administrator and go to the Packages Management page.

2 Click for the WmComauth package. Complete the page as follows:

Install the SVG Plug-InTo see all Monitor image functionality, your browser must be equipped with a scalable vector graphics (SVG) browser plug‐in. You can use this test to determine whether your Internet Explorer browser has an SVG plug‐in:

http://www.adobe.com/svg/viewer/install/svgtest.html

If an SVG plug‐in is not installed, webMethods recommends Adobe’s SVG plugin, which is supported on Windows, Linux, and Mac OS X systems. You can download the plugin from this page:

http://www.adobe.com/svg/viewer/install/main.html

Box Entry

Enabled Select the check box.

Authorization Directory Host

Machine that hosts My webMethods Server.

Authorization Directory Port

Port for My webMethods Server. The default port for My webMethods Server is 8080.

Authorization Server User name

User name for Integration Server to use to log onto My webMethods Server. You can use the default user name or create a user name in My webMethods to use. For instructions on creating user names, see My webMethods Server Administrator’s Guide.

Authorization Server Password

Password for the user name.

Monitor Access Group

Monitor group to which to assign the My webMethods users who are trying to run Monitor services on Integration Server. Click MonitorAdministrators.


http://www.adobe.com/svg/viewer/install/svgtest.html

http://www.adobe.com/svg/viewer/install/main.html

Complete the Servicenet Installation

After you install the plug‐in, set your My webMethods interface to display process model images in SVG format. For instructions, see the My webMethods Server Administrator’s Guide.

Monitor contains Java Swing and AWT components that require a graphical display utility to load. If you installed Monitor on a UNIX or Linux system and you are not using SVG, you must do either of the following:

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

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

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

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

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

Complete the Servicenet Instal lat ionServicenet consists of core components that are required for basic operation and agents that interact with different Web service containers.

Note: If your browser does not support SVG, you can display process model images in JPG format. For instructions, see the My webMethods Server Administrator’s Guide.

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

Core Components Agents

Registry Intermediary

Controller Servicenet Package (on Integration Server)

Data handler Glue Plug‐in

My webMethods Server WebLogic Plug‐in

Microsoft .NET Publisher



To complete the Servicenet installation, you must do the following:

Action Instructions

1 Configure My webMethods Server and install the My webMethods Server database component.

When you installed the Servicenet user interface, the installer automatically installed My webMethods Server. You must configure My webMethods Server and install the My webMethods Server database component. For instructions, see “Configure the Server and Database” on page 183.

2 Place license files on the Servicenet registry and intermediary host machines.

When you licensed Servicenet, webMethods provided you with a license file named webMethods‐license.xml. Place the webMethods‐license.xml file in the Servicenet_directory\conf directory on the Servicenet registry host machine and on every intermediary host machine.

3 If you installed one or more plug‐ins, deploy and configure them.

See “Set Up the Plug‐ins” on page 201.

4 In some cases, configure the Servicenet components so they can discover the Servicenet registry.

Note: You do not have to configure the data handler to discover the registry because it communicates with the registry through the controller rather than directly.

See “Configure Registry Discovery” on page 205.

5 If you want to change the port on which the registry listens for clients, configure the registry.

See “Change the Default Registry Port” on page 210.

6 If some cases, configure the registry, intermediaries, and plug‐ins to communicate with My webMethods Server.

See “Configure Servicenet Components to Communicate with My webMethods Server” on page 211.



Set Up the Plug-ins

Configure the Servicenet Package on Integration Server1 Go to the Integration Server_directory\packages\WmSnetPlugin\web\WEB‐INF

directory and open the web.xml file in a text editor.

2 Locate the <init-param> element with the value electric.http.url.

a Change localhost to the name of the Integration Server host machine.

b Change the port number to the primary listener port for Integration Server (by default, 5555). For example:


Deploy and Configure the Glue Plug-inThe Glue Plug‐in consists of the following:

My webMethods Server, Optimize, and Servicenet jar files installed by the webMethods Installer in the Servicenet_directory\misc\plugins\glue\lib directory on the Glue host.

The snet‐client‐config.xml file in the snet‐client.jar file in the Servicenet_directory\ misc\plugins\glue\lib directory.

The jar files listed below, which are located in your Glue installation

The method you use to deploy and configure the Glue Plug‐in depends on the way you start Glue.

<init-param> <param-name>electric.http.url</param-name> <param-value>http://intserver:5555/web/WmSnetPlugin/services</param-value> </init-param>

Functional Area Jar Files

XML xalan.jar

xercesImpl.jar

xml‐apis.jar

jaxen‐core.jar

jaxen‐dom.jar

saaj‐api.jar

jaxrpc‐api.jar

saxpath.jar

Security xmlsec.jar

wss4j.jar

opensaml.jar



Deploy and Configure the Plug-in When You Start Glue by Calling the HTTP.startup() Method

If you start Glue by calling the HTTP.startup() method, do the following:

1 Deploy the plug‐in by adding all the jar files installed with the plug‐in to the system classpath at the same level as the glue.jar file. Also add the snet‐client‐default‐config.xml file to the system classpath.

2 Configure your HTTP.startup services to work correctly with the plug‐in by adding a Fabric.join() statement to the server class of the services. For example:

Deloy and Configure the Plug-in When You Start Glue Using the runapp Command

If you start Glue using the runapp command, do the following:

1 Do one of the following:

Copy the jar files installed with the plug‐in to the Glue_directory\WEB‐INF\lib directory and copy the snet‐client.jar file to the Glue_directory\WEB‐INF directory.

Add the jar files installed with the plug‐in to the system classpath at the same level as the glue.jar file. Copy the snet‐client‐default config.xml file to the Glue_directory\WEB‐INF directory.

2 Before you start Glue, configure Glue to work with the plug‐in, as follows:

a Go to the Glue_directory\WEB‐INF directory and open the web.xml file in a text editor.

b Add an <init-param> element to the glue‐soap servlet. This element enables the plug‐in to provide its location to the Servicenet registry. The <init-param> element takes the name electric.http.url and the HTTP URL value to the context root of Glue. For example:

public class Publish1{ public static void main( String[] arguments ) throws Throwable { // join the grid Fabric.join();

// start a web server on port 8004, accept messages via /examples HTTP.startup( "http://localhost:8004/examples" );

<init-param> <param-name>electric.http.url</param-name> <param-value>http://localhost:8004/glue</param-value> </init-param>



3 Add the following listener to the <web‐app> element:


Deploy the WebLogic Plug-in

1 On the WebLogic host machine on which you installed the WebLogic Plug‐in, go to the Servicenet_directory\misc\plugins\weblogic directory and open the wlplugindeploy.properties file in a text editor. Edit the file as shown below.


3 Open a command window and go to the Servicenet_directory\misc\ plugins\weblogic directory.

4 Run the command ant usage. The descriptions for a rebuild command and a deployment commands appear in the window.

5 Update the snet‐wl‐plugin.war file with the properties you just set by running this command:

6 Deploy the plug‐in by running this command:

<listener> <listener-class>com.webmethods.fabric.integration.glue. FabricContextListener</listener-class> </listener>

Important! You deploy the WebLogic Plug‐in using an Apache Ant script. If you do not have a separate installation of Ant, you can use the Ant library packaged with WebLogic at bea-home/weblogic81/server/bin/ant.

Set this property... ...to this value

snet.plugin.jars.dir Absolute path to the Servicenet_directory/lib directory

bea.home WebLogic is installed directory

weblogic.domain Name of the domain to use for the plug‐in

weblogic.username WebLogic administrator user name

weblogic.password (required only if you start WebLogic in production mode)

WebLogic administrator password

ant rebuild.wlplugin

ant deploy.wlplugin



Deploy and Configure the Microsoft .NET Publisher1 Deploy the publisher as follows:

a On the Microsoft .NET server host machine on which you installed the Microsoft .NET Publisher, go to the Servicenet_directory\misc\plugins directory.

b Start the Microsoft .NET Publisher installation wizard by double‐clicking the ServicenetContainerManager.msi file.

c Click Next until you reach the Select Installation Address panel. In the Port box, set the value to the port the .NET server (IIS) uses.

d Click Next until you reach the Install Complete panel, and then click Close.

2 Configure the publisher for to discover the registry as follows:

a Open the .NET server (IIS) and select the new servicenet virtual directory. Under the virtual directory, open the web.config file.

b Go to the DISCOVERY section. The next step depends on whether you want to use subnet or WAN locators.

If you want to use subnet locators, under the subnet locator, set the <port> element to the port you want the Servicenet components to use for the ping. For example:

Note: In the wizard, the .NET server is called Internet Information Services (IIS), and its port is the IIS port.

<locator> <name>subnet</name> <constructor> <class>Webmethods.Fabric.Services.Registry.Locators.Subnet. SubnetLocator</class> <args> <port>9030</port> <maxWait>2000</maxWait> </args> </constructor></locator>



If you want to use WAN locators, comment out the entire subnet locator. Under the WAN locator, set the value of the <url> parameter to the URL of the registry. For example:

c Save and close the file, then restart all Servicenet components.

Configure Registry DiscoveryDepending on how you installed Servicenet, you might need to configure discovery of the registry for your Servicenet components. Servicenet components can use subnet locators, static locators, or WAN locators to locate the registry.

<locator> <name>wan</name> <constructor> <class>Webmethods.Fabric.Services.Registry.Locators.Wan. WANLocator</class> <args> <url>http://10.3.22.238:8088/snet/fabric/registry</url> </args> </constructor></locator>

Locator Description

Subnet When configured to use a subnet locator, a Servicenet component, at star‐tup, sends a User Datagram Protocol (UDP) ping on a specified port out to the subnet. The registry component or any other Servicenet component that has already started and connected to the Servicenet registry, can respond to the ping and provide the registry’s URL to the Servicenet com‐ponent that sent the ping. In this way the Servicenet components dynami‐cally discover and bind to the registry.

The subnet locator identifies the port on which to send the UDP ping. Any Servicenet component that resides within the same subnet as the registry can use a subnet locator.

Static Static locators contain the URL (host/port) of the registry. All Servicenet components except the Microsoft .NET Publisher can use a static locator to locate the registry.

WAN WAN locators contain the URL (host/port) of the registry. Only the Microsoft .NET Publisher can use a WAN locator to locate the registry.

Note: You configure the Microsoft .NET Publisher differently for registry discovery than the other Servicenet components. For instructions, see “Deploy and Configure the Microsoft .NET Publisher” on page 204.



Use the following table to determine what you need to do.

If you...And you want to use... You must...

Installed all Ser‐vicenet compo‐nents on one machine or dis‐tributed Ser‐vicenet over multiple machines

Subnet locators and the default Subnet locator discovery port 9030

Do nothing. All components are configured by default to use subnet locators on the default port.

Static locators and the default registry port 8088

Configure all components except the registry to use static locators rather than subnet loca‐tors. See “Configure Servicenet Component to Use Static Locators” on page 207.

Static locators and a non‐default registry port

Configure all components except the registry to use static locators and to use the non‐default port. See “Configure Servicenet Com‐ponent to Use Static Locators” on page 207.

Change the registry to use the non‐default port; see “Change the Default Registry Port” on page 210.

Installed all Ser‐vicenet compo‐nents on one machine

Subnet locators and a non‐default port you specified during installation

Configure all plug‐ins and intermediaries to use the new port. See “Configure Servicenet Components to Use Subnet Locators” on page 208.

Distributed Ser‐vicenet compo‐nents over multiple machines

Subnet locators and a non‐default port you specified during installation

Configure all components to use the non‐default port. See “Configure Servicenet Components to Use Subnet Locators” on page 208.



Configure Servicenet Component to Use Static Locators1 If My webMethods Server is one of the Servicenet components you need to configure,

shut it down as follows:

2 Open the snet‐client‐config.xml file for each Servicenet component whose static locator you want to configure. The file is in the locations below.

System Action

Windows a Open the Control Panel and double‐click the Administrative Tools icon.

b In the Administrative Tools window, double‐click the Services icon.

c In the Services window, double‐click the webMethods Portal Server service, then click Stop.

UNIX a Open a command window and go to the Portal/server/ default/bin directory.

b Run this command:shutdown.sh

Note: Some components have a snet‐client‐default‐config.xml file. If you edit this version of the file, save the edited version as snet‐client‐config.xml. When both versions of the file exist on a component, the component uses the snet‐client‐config.xml file.

Component Location of the configuration file

Controller Optimize_directory\controller\webapps\ROOT\WEB‐INF\snet‐client‐config.xml


Portal_directory\lib\snet‐client.jar (contains snet‐client‐default‐config.xml)

Intermediary webMethods_directory\Servicenet\conf\snet‐client‐config.xml

Glue Plug‐in See “Deploy and Configure the Glue Plug‐in” on page 201 to determine where the snet‐client‐default‐config.xml file is for the Glue Plug‐in.

WebLogic Plug‐in

weblogic_domain.dir/servicenet/snet‐client‐default‐config.xml

Integration Server Plug‐in

Integration Server_directory\packages\WmSnetPlu‐gin\web\WEB‐INF\snet‐client‐config.xml



3 Go to the <discovery> section and set the <useLocator> element to static. For example:

4 Go to the <locator> section and set the <url> element to the host and port for the registry. For example:

5 Save and close the file, then restart all Servicenet components.

Configure Servicenet Components to Use Subnet Locators1 If My webMethods Server is one of the Servicenet components you need to configure,

shut it down as follows:

<discovery><noPath>fabric://failover&monitor</noPath><useLocator>static</useLocator><useSignatures>true</useSignatures>

Important! Do not change the default locator on the registry to static. Components using static locators can connect to the registry even when the locator on the registry is set to subnet. However, if some Servicenet components use subnet locators, configuring the registry for static locators can prevent those components from connecting to the registry.

<locator> <name>static</name> <constructor> <class>com.webmethods.fabric.services.registry.locators .StaticLocator</class> <args> <url>http://registryhost:8088/snet</url> </args> </constructor></locator>

System Action

Windows a Open the Control Panel and double‐click the Administrative Tools icon.

b In the Administrative Tools window, double‐click the Services icon.

c In the Services window, double‐click the webMethods Portal Server service, then click Stop.

UNIX a Open a command window and go to the Portal/server/ default/bin directory.

b Run this command:shutdown.sh



2 Open the snet‐client‐config.xml file for each component you want to configure to use subnet locators. The file is in the locations indicated below.

3 Go to the <discovery> section and make sure the <useLocator> element is set to subnet. For example:

Note: Some components have a snet‐default‐client‐config.xml file. If you edit this file, save the edited version as snet‐client‐config.xml. When both versions of the file exist on a component, the component uses the snet‐client‐config.xml file.

Component Location of the configuration file

Registry Servicenet_directory\conf\snet‐client‐config.xml

Controller Optimize_directory\controller\webapps\ROOT\WEB‐INF\snet‐client‐config.xml

My web‐Methods Server

Portal_directory\lib\snet‐client.jar (contains snet‐client‐default‐config.xml)

Intermediary Servicenet_directory\conf\snet‐client‐config.xml

Glue Plug‐in See “Deploy and Configure the Glue Plug‐in” on page 201 to determine where the snet‐client‐default‐config.xml file is for the Glue Plug‐in

WebLogic Plug‐in

weblogic_domain.dir/servicenet/snet‐client‐config.xml

Servicenet Package

Integration Server_directory\packages\WmSnetPlugin\ web\WEB‐INF\snet‐client‐config.xml

<discovery><noPath>fabric://failover&monitor</noPath><useLocator>subnet</useLocator><useSignatures>true</useSignatures>



4 Go to the <locator> section and set the <port> element to the port you want the component to use for pinging. For example:

5 Save and close the file, then restart all Servicenet components.

Change the Default Registry PortBy default, the Servicenet registry listens for data from clients on port 8088. If you have other applications that use that port, change to another port as described below.

1 On the Servicenet registry host machine, go to the webMethods_directory\Servicenet\ conf directory and open the servicenet‐config.xml file in a text editor.

2 Go to the <servers> section and change the port number in the <url> element to the port you want the registry to use. For example:


4 If you have not yet updated Servicenet components that are using static locators for registry discovery to use the new registry port, see “Configure Servicenet Component to Use Static Locators” on page 207.

<locator> <name>subnet</name> <constructor> <class>com.webmethods.fabric.services.registry.locators. subnet.SubnetLocator</class> <args> <port>9035</port> <maxWait>10</maxWait> <pingCycle>5</pingCycle> </args> </constructor></locator>

Important! You must configure all Servicenet components to use the same port.

Important! Make this change before you start Servicenet for the first time. Servicenet loads system services into the registry, and these system services are tied to the registry port. If you change the port after starting Servicenet, you will have duplicate entries in your Servicenet database, and Servicenet might be unable to load some services. If you drop the Servicenet database to clean up the registry, you will lose your connections to intermediaries in your grid, including the default intermediary that resides with the registry.

<servers> <http> <url>http://localhost:8099/snet</url>



Configure Servicenet Components to Communicate with My webMethods ServerAll Servicenet components except the data handler communicate with My webMethods Server. The configuration file for each component contains the My webMethods Server host name and port number. Depending on how you installed Servicenet components, you might have to add or modify this information for one or more components. Use the following table to determine what to do.

If you... And you... You must...

Installed the regis‐try, controller, data handler, and My webMethods Server on one machine

Kept the default My webMethods Server port 8080

Add the My webMethods Server host name to the configuration files for plug‐ins and intermediaries installed on other machines.

Specified a non‐default port for My webMethods Server during installation

Add the My webMethods Server host name and non‐default port number to the configuration files for plug‐ins and intermediaries installed on other machines.

Add the non‐default port number to the configuration file for the registry.

Distributed Ser‐vicenet over multi‐ple machines, or are using a previ‐ously installed My webMethods Server

Kept the default My webMethods Server port 8080

Add the My webMethods Server host name to the configuration files for the registry, plug‐ins, and intermediaries.

Specified a non‐default port for My webMethods Server during installation

Add the My webMethods Server host name and non‐default port number to the configuration files for the registry, plug‐ins, and intermediaries.

Note: You do not have to modify the configuration files for the controller or data handler in any case because the installer automatically modifies those files to contain the correct My webMethods Server host name and port number.



To add the My webMethods Server host name and port number to the configuration files for Servicenet components, do the following:

1 Open the glue‐config.xml file for each component whose My webMethods Server host or port information you need to change. The file is in the locations indicated below.

2 Go to the <realm> section and set the <portalURL> parameter to the correct My webMethods Server host and port. For example:


Component File Location

Registry Servicenet_directory\conf directory

Intermediary Servicenet_directory\conf directory

Integration Server Plug‐in

Integration Server_directory\packages\WmSnetPlugin\web\WEB‐INF directory

Glue Plug‐in webapp_directory\WEB‐INF directory

WebLogic Plug‐in Within the snet‐wl‐plugin.war file

<realm> <constructor> <class>com.webmethods.fabric.security.realm. DirectoryServiceRealm</class> <args> <name>PortalRealm</name> <portalURL>http://mywebmethodshost:8080</portalURL> <user>WEBM_SYSUSER</user> <password>manage</password> </args> </constructor></realm>


Complete the Workflow Installation

Complete the Workf low Instal lat ion

Set Up the Workflow DatabaseCreate a separate tablespace for the Workflow database component in your database. Then create a database user and password for the Workflow Servers to use to log in to the database. The database user needs permission to create, alter, and drop tables in the Workflow Server tablespace.

Set Up Secondary Workflow Servers to Access Encryption PasswordsIf you installed secondary Workflow Servers in addition to the central Workflow Server, you must set up the secondary Workflow Servers to access encryption passwords maintained by the central Workflow Server.

Manually copy the po.properties file and the authentication.properties file from the central Workflow Server installation to corresponding directories in every secondary Workflow Server installation. The po.properties file is located in the Workflow Server installation directory and the authentication.properties file is located in the Workflow Server_directory\etc directory.

Set Up Workflow Servers for Automatic Startup on Solaris, HP-UX, AIX, and Linux SystemsIf you installed a Workflow Server on a Solaris, HP‐UX, AIX, or Linux system and you want the Workflow Server to start automatically when you start the system, go to the Workflow Server_directory/bin directory and run this command:./bootsc.sh

Set Up Workflow Servers for Automatic or Manual Startup on Windows MachinesBy default, Workflow Server is installed as a Windows service on Windows systems. However, if you installed multiple Workflow Servers on the same machine, only the last‐installed Workflow Server is a Windows service and starts automatically; the previously installed Workflow Servers are Windows applications that have to be started manually.

You can change the Workflow Servers that are Windows applications that have to be started manually to run as Windows services that start automatically by creating service entries for them in the Windows registry. You can also change a Workflow Server that is running as a Windows service to be a Windows application instead.



Change a Workflow Server from a Windows Application to Run as a Windows Service1 If the Workflow Server is running, shut it down.

2 If the Windows Services window is open, close it.

3 Open a command window, go to the Workflow Server_directory/bin directory, and type this command on a single line, without any return or line‐feed characters:WorkflowSvc.exe -i -Djava.class.path=Workflow Server_directory\bin\SrvcWorkflow.jar wrkdir=Workflow Server_directory servicename=service_name displayname=display_name

Use the same name for service_name (name of the service) and display_name (name under which the service is displayed in the Services window), and make the name unique on the current machine. You might want to name each Workflow Server based on a port it uses (for example, WorkflowServer_port_6001, WorkflowServer_port_6002, and so on). Use quotation marks to enclose any variable that includes spaces.

Change a Workflow Server that Runs as a Windows Service to a Windows Application1 If the Windows service for the Workflow Server is running, open the Windows

Services window, stop the service, and then close the window.

2 Open a command window, go to the Workflow Server_directory/bin directory, and type this command on one line:WorkflowSvc.exe -r servicename=service_name displayname=display_name

Use quotation marks to enclose any variable that include spaces.

Enable a Workflow Server on a Red Hat Linux System to Use an SSL-Enabled BrokerIf you want to use an SSL‐enabled Broker with a Workflow Server that is installed on a Red Hat Linux system, you must install a compatibility package from Red Hat, as follows:

1 Go to the Red Hat Web site and download the compat‐libstdc++‐7.3‐2.96.128.i386.rpm package.

2 If the package name contains brackets ([]), remove the brackets from the name.

3 Go to the directory to which you downloaded the package and run this command:rpm -i compat-libstdc++-7.3-2.96.128.i386.rpm



Configure Workflow ServersTo configure a Workflow Server, you run the Workflow Configurator. The Workflow Configurator guides you through the process of configuring a Workflow Server.

If you installed the Workflow Server on a Windows system or on a UNIX or Linux system that has an X‐Windows environment, you can use the graphical Workflow Configurator. The graphical configurator shows sets of questions on multiple panels and saves the configuration information you enter on each panel when you click Next. You can click Cancel on any panel to exit the configurator without supplying any more information. However, you must continue to the last panel to complete the configuration at some point before you can start the Workflow Server.

If you installed the Workflow Server on a UNIX or Linux system that does not have an X‐Windows environment, you can use the non‐graphical Workflow Configurator. The non‐graphical configurator prompts you to answer questions that appear in sets that correspond to the graphical configurator’s panels; current settings or defaults appear in brackets [ ] at the end of each question. The configurator saves the configuration information you enter for each question set when you type N after the last question in the set. If you want to display help information for the current question set, type H. If you want to re‐enter your answers to the current question set, type R. If you want to go back to the previous question set without saving your current answers, type B. If you want to clear a field, type two double quotation marks (““). You can type X at any point to exit the configurator without supplying any more information. However, you must respond to all the question sets to complete the configuration at some point before you can start the Workflow Server. Type all paths without quotation marks.

Start the Workflow ConfiguratorStart the Workflow Configurator as follows:

The Configurator displays the JDK Parameters panel.

System Action

Windows On the Start menu, go to Programs webMethods Tools Workflow Configurator.

UNIX or Linux

To start the graphical configurator, go to the Workflow Server_directory/bin directory and enter this command:./configure.sh

To start the non‐graphical configurator, go to the Workflow Server_directory/bin directory and enter this command:./configure.sh -nogui



Identify the JDK to Use1 By default, the Workflow Server uses the JDK that was installed by the installer; the

configurator shows the path to that JDK in the JDK Path box. If you want to redirect the Workflow Server to use a different JDK instead, provide the path to that JDK. For JDK requirements for Workflow Servers, see the webMethods System Requirements.

2 Click Next. The configurator displays the Central Host Parameters panel.

Identify the Central Workflow Server and the Type of Authentication to Use1 Check the specifications for the Workflow Server central host name and port and the

RMI registry port that you provided in the webMethods Installer (see “Configure Workflow Server” on page 123) and edit them if necessary. Make sure the ports specified are not in use by any other process; for example, on Windows XP Professional systems, port 5000 is reserved.

2 If you are configuring the central Workflow Server, click Master next to the central host name. If you are configuring a secondary Workflow Server, click Slave.

Click Next. If you clicked Master, the configurator displays the Authentication and Security Parameters panel; go to the next step, below. If you clicked Slave, the configurator displays the Configuration Complete panel; go to “Complete the Configuration” on page 223.

3 If you want to enable SSL for the Workflow Server so the Workflow Server can encrypt Workflow client login data, select the SSL Enabled check box in the SSL Parameters area and provide the following information:

If you do not want to enable SSL for the Workflow Server, clear the SSL Enabled check box.

Box Entry

Keystore File Fully qualified path to the SSL keystore file. The file must be in PKCS#12 format.

Keystore Password

Password for the keystore file.

Certificate File Fully qualified path to the X509 certificate file for Workflow clients.

You must also add the X509 certificate to the keystore file.

Note: You can only specify one certificate at a time.



4 In the Local or Site-central Authentication Parameters area, choose the type of authentication system to use.

Authenticate Workflow users using... Action

Workflow Server

Click Local to use Workflow Server’s local store of user accounts. If you have installed webMethods products that do not communicate with My webMethods Server, you might want to use this option rather than using My webMethods Server for authentication (see below).

Your own authentication system

1 Click Site-central.

2 In the URL for Authentication Service JAR Archive box, type the URL for the jar archive file for your authentication system.

3 Workflow clients use a caching mechanism to store frequently used data. In the Caching Method area, specify the caching mechanism to use. If your authentication system can notify the Workflow Server when values change, click Notification. If your authentication system cannot notify Workflow Server, click Timeout and, in the Cache Timeout box, specify how often Workflow Server should request an update.

Note: If you do not have an authentication system but want to set one up so you can use it with Workflow, contact webMethods Customer Care for instructions.



The Workflow Server will check its connection to the Workflow Authentication Server periodically to make sure client sessions are connected and to clean up sessions that did not end after the user logged out. The Session Keep Alive Settings area lets you customize this functionality. Complete the boxes as follows:


If you have installed other webMethods products that communicate with My webMethods Server, you might want to use this option for simplicity rather than using Workflow Server for authentication (see above). You will have to make sure My webMethods Server always runs when you run Workflow if you choose this option.

1 Go to My webMethods and add Workflow users. For instructions, see the My webMethods Server Administrator’s Guide.

2 In the Workflow configurator, click My webMethods.

3 In the Protocol list, click the protocol to use for authentication. If you want My webMethods Server to authenticate using a standard connection, click http. If you want My webMethods Server to authenticate using a secure connection, select https. Your selections in the SSL Parameters section do not affect your selection here.

4 In the Host, Port, User, and Password boxes, enter the values needed to connect to My webMethods Server. The host and port are the Jetty HTTP Listener Host/Port you specified in the Portal Server Configurator. The default user name and password are Administrator and manage.

5 Workflow clients use a caching mechanism to store frequently used data. In the Cache Timeout box, specify how often Workflow Server should request an update.

Box Entry

Keep Alive Interval (minutes)

Number of minutes to wait between pings of authentication session clients with registered listeners. The default is 60 minutes.

Authenticate Workflow users using... Action



6 Click Next. The configurator displays the Broker Parameters panel. If you enabled SSL for Workflow Server, the configurator places the SSL certificate file you identified in the Certificate File field in the Workflow Server_directory\lib\security directory. The Workflow client and secondary Workflow Servers automatically pull this file at login time and place a copy in their security directories.

Identify the Broker to Use1 Type the name of the Broker to which you want the Workflow Server to connect, the

name of the machine on which the Broker resides, and the port the Broker is using.

If the Broker is SSL‐enabled, select the Broker SSL Enabled check box and complete the boxes below.

Retries Number of times to retry pinging dead authentication session clients with registered listeners. The default is 3.

Inactivity Timeout (minutes)

Number of minutes after which the Workflow Server will automatically log out a dead authentication session client with registered listener if the session has not recovered. The default is 30.

Box Entry

Important! Make sure the Broker you identify on this panel is running. When you click Next, the configurator will try to validate the Broker parameters you have entered; if the Broker is not running you will not be able to continue. The name of the default Broker is Broker #1.

The configurator assumes the Broker is using the default port 6849. If the Broker is using a different port, you must specify it.

Box Entry

Broker SSL Certificate Pathname

Fully qualified path to the Broker’s SSL certificate file.

Broker SSL Password

Password for the certificate file.

Broker SSL Distinguished Name

If you want to enable both server‐side and client‐side authentication, click the distinguished name specified in the Broker’s certificate file. If you want to enable server‐side authentication only, accept the default NONE.

Enable Broker SSL Data Encryption

By default, an SSL‐enabled Broker will not encrypt Workflow data. If you want the Broker to encrypt Workflow data, select the check box.



2 Click Next. The configurator displays the SMTP Parameters panel.

Enable the Workflow Server to Send E-mail Notifications1 If you want to enable the Workflow Server to send e‐mail notifications, complete the

boxes below.

2 Click Next. The configurator displays the webMethods Monitor Database Parameters panel.

Configure the Workflow Server to Write to the Process Audit Log Database1 If you want to use Monitor to monitor Workflow processes, you must set up

Workflow Server to write process data to the Process Audit Log. Complete the boxes below.

Box Entry

SMTP Host Name

Name of the machine that hosts the mail server.

SMTP Port Number of the port the mail server uses.

SMTP User User name for the Workflow Server to use to log in to the mail server.

SMTP Password

Password for the SMTP user.

SMTP Disconnect Timeout (seconds)

If you want the Workflow Server to disconnect from the mail server after a certain period of time, select the check box and specify the number of seconds. If you do not want the Workflow Server to disconnect, clear the check box.

Administrator E-mail

E‐mail address for the user to whom the Workflow Server will send messages about problems.

Box Entry

Database Type Type of database you are using for the Process Audit Log.

JDBC Driver Class

Fully qualified name of the Java class for the JDBC driver that the Workflow Server will use to communicate with the database.



2 If you want to make sure you can connect to the specified database, click Test. The configurator indicates whether the connection was successful. If the connection was not successful, supply a different set of parameters and click Test again.

3 Click Next. The configurator displays the Database Configuration Parameters panel.

URL for Database Connection

URL for the database, as follows:

URLDefault Port


1521


1521


1433


5000


50000

Database User Name

Database user for the Workflow Server to use to log in to the database. User the database user you created in “Set Up the Workflow Database” on page 213.

Database Password


Box Entry



Configure the Workflow Server to Write to the Workflow Database1 Make sure you have completed the tasks in “Set Up the Workflow Database” on

page 213.

2 Configure the Workflow Server to write Workflow process models to its database by completing the boxes below. If necessary, ask your database administrator to grant you the permissions needed to complete some of the boxes on the panel.

Box Entry

Database Type Type of database you are using.

JDBC Driver Class

Fully qualified name of the class for the JDBC driver that the Workflow Server will use to communicate with the database.

URL for JDBC Driver(s)

URL of the jar file that contains the JDBC drivers that the Workflow Server will use to communicate with the database. The configurator copies the jar file you identify to the Workflow Server_directory\lib directory.

URL for Database Connection

URL for the database.

URLDefault Port


1521


1433


50000


Note: AlternateId must match the schema in which you created the Workflow database tables.

446



3 Click Next. The configurator creates and initializes the tables in the Workflow database, then displays the Broker, Database, and Password Initialization panel.

Synchronize the Workflow Server with Your Broker1 If you want to clear the Broker’s queues and drop your database tables (for example,

because data has been corrupted), select the Drop Database Tables check box.

2 If you chose Local or Site-central authentication on the Authentication and Security Parameters panel, in the Internal Password box, type the password for Workflow Server to use internally to encrypt and decrypt the data it stores in its database.

3 Click Next. If you did not choose to clear the Broker’s queues and drop your database tables, the configurator synchronizes the Workflow Server with your Broker and updates your Broker document types.

If you did choose to clear the Broker’s queues and drop your database tables, the configurator displays a warning that you are about to delete all existing database records and asks whether you want to continue. Click Yes, then click Next.

If the information you have entered is accurate for your system, the configurator displays a confirmation message telling you that database schemas have been created or updated. If the information you entered is not accurate, the configurator displays an error message. Click OK. The configurator displays the Configuration Complete panel.

Complete the Configuration1 Click Done. The configurator closes.

2 Go to the Workflow Server_directory\log directory and open the configurelogn.txt file to see if any errors occurred during configuration. If you find error messages, see the troubleshooting information for Workflow on the webMethods Advantage Web site at http://advantage.webmethods.com/cgi‐bin/advantage/targetedLogin.jsp.

Database User Name

Database user for the Workflow Server to use to log in to the database. User the database user you created in “Set Up the Workflow Database” on page 213.

Database Password


Box Entry




Configure Workflow to Use SSLIf you want Workflow to use SSL to communicate, you must complete some or all of the tasks below.

Configure Workflow Clients to Connect to an SSL-Enabled BrokerIf you want to use an SSL‐enabled Broker with Workflow, you must configure each Workflow client you installed to connect to the Broker.

1 Start the Workflow client as follows:

2 On the Options menu, click Broker Certificates.

3 If the Broker is SSL‐enabled, select the Broker SSL Enabled check box and complete the boxes below with the same information you entered in the Workflow Configurator when you set up the Workflow Server (see “Identify the Central Workflow Server and the Type of Authentication to Use” on page 216).

4 Repeat these steps for every Workflow client.

System Action

Windows On the Start menu, go to Programs webMethods webMethods Workflow.

Linux Go to the Workflow client_directory/bin directory and run the clientmgr.sh script.

Box Entry

Broker SSL Certificate Pathname

Fully qualified path to the Broker’s SSL certificate file.

Broker SSL Password

Password for the certificate file.

Broker SSL Distinguished Name

If you want to enable both server‐side and client‐side authentication, click the distinguished name specified in the Broker’s certificate file. If you want to enable server‐side authentication only, accept the default NONE.

Enable Broker SSL Data Encryption

By default, an SSL‐enabled Broker will not encrypt Workflow data. If you want the Broker to encrypt Workflow data, select the check box.



Set Up Access Control Lists for an SSL-Enabled BrokerWhen you use an SSL‐enabled Broker with Workflow, both SSL‐enabled and non‐SSL‐enabled Workflow Servers, Workflow clients, and Workflow API applications can connect to the Broker. If you want to require that Workflow applications connect to the Broker using SSL, you must set up access control lists (ACLs) and assign the following Workflow client groups to the ACLs:

WFClassrv

WFClassrvClients

DCS

workFlowClients

BusinessLog

WorkflowMonitor

ProcessServer

WFPortfolio

WFPortfolioClients

For instructions on setting up access control lists, see the webMethods Broker Administrator’s Guide.

Configure the Workflow Servlet to Connect to an SSL-Enabled Workflow Server and BrokerIf you want to use the Workflow Servlet with an SSL‐enabled Workflow Server and Broker, you must configure the servlet engine.

Configure Integration Server’s Internal Tomcat Servlet Engine

If you are using Integration Server as your servlet engine, you installed the Workflow Servlet package during installation. This package lets you use Integration Server’s internal Tomcat servlet engine. Make sure the Workflow Servlet package is enabled. To do so, open Integration Server Administrator, go to the Packages Management page, and look for the WmWFServlet package. If the package is disabled, locate the row for the package in the table, then click Yes in the Enabled column in that row. The Yes changes to No.

If Integration Server and Workflow Server are installed on the same machine, do the following:

1 Go to the Integration Server_directory\bin directory and open the server.bat or server.sh file in a text editor. Locate the %JAVA_RUN% line and add these parameters to it: -Dcom.wm.security.directory=%Workflow Server_directory%\security



-Dbroker.sslcertfile=%Workflow Server_directory%\security\certificate_file-Dbroker.sslpassword=certificate_file_password-Dbroker.sslencrypted=true_or_false

If you want to use client‐side authentication, also add this parameter:-Dbroker.ssldname=”CN=cn_info,O=organization,L=location,ST=state,C=country”



If Integration Server and Workflow Server are installed on different machines, do the following:

1 Go to the Integration Server_directory and create a directory named security.

2 Make a copy of the Workflow Server SSL certificate file you identified in the Workflow Configurator and place the copy in the Integration Server_directory\security directory.

3 Make a copy of the Broker SSL certificate file you identified in the configurator and place the copy in the Integration Server_directory\security directory.

4 Go to the Integration Server_directory\bin directory and open the server.bat or server.sh file in a text editor. Locate the %JAVA_RUN% line and add these parameters to it:-Dcom.wm.security.directory=%Integration Server_directory%\security-Dbroker.sslcertfile=%Integration Server_directory%\security\certificate_file-Dbroker.sslpassword=certificate_file_password-Dbroker.sslencrypted=true_or_false

If you want to use client‐side authentication, also add this parameter:-Dbroker.ssldname=”CN=cn_info,O=organization,L=location,ST=state,C=country”



Configure the Apache Tomcat Servlet Engine

1 Install the Workflow Servlet in Apache Tomcat, as follows:

a Shut down Tomcat.

b Go to the Workflow Server installation directory.

c Copy the Workflow.war file into the Tomcat_directory\webapps directory.

d If you are installing the Workflow Servlet over an earlier verserion, delete the Workflow directory in the Tomcat_directory\webapps directory.

2 Go to the %CATALINA_HOME% directory and create a directory named security.

3 Make a copy of the Workflow Server SSL certificate file you identified in the configurator and place the copy in the %CATALINA_HOME%\security directory.



4 Make a copy of the Broker SSL certificate file you identified in the Workflow Configurator and place the copy in the %CATALINA_HOME%\security directory.

5 Open the catalina.bat or catalina.sh file in a text editor.

6 Set the PATH variable to contain the path to the SSL native libraries. On Windows systems, the path is Tomcat_directory\webapps\Workflow\WEB‐INF\lib\Windows; you would set the PATH variable as follows:set PATH=%PATH%;%CATALINA_BASE%\webapps\Workflow\WEB-INF\lib\Windows

On other operating systems, locate the corresponding directory and set the path accordingly.

7 Locate the set CATALINA_OPTS=%CATALINA_OPTS% line and add these parameters to it:-Dcom.wm.security.directory=%CATALINA_HOME_directory%\security-Dbroker.sslcertfile=%CATALINA_BASE_directory%\security\certificate_file-Dbroker.sslpassword=certificate_file_password-Dbroker.sslencrypted=true_or_false

If you want to use client‐side authentication, also add this parameter:-Dbroker.ssldname= ”CN=cn_info,O=organization,L=location,ST=state,C=country”

8 To increase the debug level for the Workflow client, locate the set JAVA_OPTS= line and set it as follows:set JAVA_OPTS=-Dwm.zeus.log.trace=15 -Dwm.zeus.log.debug=15


10 Restart Tomcat.

Configure the BEA WebLogic Servlet Engine

1 Install the Workflow Servlet in BEA WebLogic. For instructions, see the BEA WebLogic documentation.

2 Shut down BEA WebLogic.

3 Go to the WebLogic installation directory and create a directory named security.

4 Make a copy of the Workflow Server SSL certificate file you identified in the configurator and place the copy in the WebLogic_directory\security directory.

5 Make a copy of the Broker SSL certificate file you identified in the configurator and place the copy in the WebLogic_directory\security directory.

6 Open the startWebLogic.cmd or startWebLogic.sh file in a text editor. Locate the set JAVA_OPTIONS= line and add these parameters to it:-Dcom.wm.security.directory=%WebLogic_directory%\security-Dbroker.sslcertfile=%WebLogic_directory%\security\certificate_file-Dbroker.sslpassword=certificate_file_password-Dbroker.sslencrypted=true_or_false



If you want to use client‐side authentication, also add this parameter:-Dbroker.ssldname= ”CN=cn_info,O=organization,L=location,ST=state,C=country”


7 Restart BEA WebLogic.

Configure Modeler to Connect to an SSL-Enabled Workflow ServerIf you want to use Workflow with Modeler, and your Workflow Server is SSL‐enabled, you must configure Modeler to connect to the SSL‐enabled Workflow Server.

1 Start Workflow Designer and connect to the Workflow Server.

2 Start Modeler.

3 Go to the Modeler_directory\lib directory and open the setup.bat or setup.sh file in a text editor.

4 Add this information to the SET SYSVAR= parameter:-Dcom.wm.security.directory=Workflow client_directory\lib\security

5 When Modeler starts, it searches for a Workflow client installation. If Modeler and the Workflow client are installed in the same root directory (for example, webMethods6), Modeler automatically sets the WF_HOME parameter in the the setup.bat or setup.sh file to identify the Workflow client installation. If Modeler and the Workflow client are not installed in the same root directory, you must identify the Workflow client on the WF_HOME parameter.

6 Save the setup.bat or setup.sh file.

7 Restart Modeler.


Connect Products to Each Other


Connect My webMethods Server to Other ProductsYou must connect My webMethods Server to other webMethods products so the products can display their data in My webMethods.

Identify Products to My webMethods Server1 Start My webMethods Server as follows:

2 Open My webMethods by entering this URL in an Internet browser:http://My webMethods Server_host:My webMethods Server_port

The host and port are the Jetty HTTP Listener Host/Port you specified in the Portal Server Configurator. webMethods recommends that you do not use localhost to identify the host.

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

4 Go to the webMethods Configuration System Configuration System Settings page and identify the webMethods products you have installed. The products are Integration Server, the webMethods Controller (the Manager/Optimize controller), (Workflow) Task List Management DCS, (Workflow) Task List Management Authentication, Inbox Servlet (the Workflow Servlet; URL is case sensitive), and the central Workflow Server.

You provided the host machines and ports for most of the products during installation (for a list of default ports, see “Default Ports” on page 254). For the Task List Management DCS and Task List Management Authentication, however, you must look up the host machine and port information in Workflow Administrator, as follows:

System Action

Windows Open the Services window, double‐click the webMethods Portal Server service, and then click Start.

UNIX or Linux

Go to the Portal_directory/server/default/bin directory and run the run.sh (start in same console window) or startup.sh (start in new con‐sole window) script.

Note: When you go to the System Settings page, you might see errors for products that are not running. You can ignore these errors. My webMethods Server will save your settings regardless of whether the products are started or not.



a Start the Workflow client as follows:

b Click the Administrator icon ( ). In the list of Workflow Servers and processes on the left, click the Authentication Server and the DCS, respectively, to view their host machine and port information on the Main tab.

Identify My webMethods Server to Products

System Action

Windows On the Start menu, go to Programs webMethods webMethods Workflow.

Linux Go to the Workflow client_directory/bin directory and run the clientmgr.sh script.

Product Action

Manager, Optimize

You identified My webMethods Server to Manager and Optimize when you installed the controller. However, if My webMethods Server is on a different host machine or uses a different port than you thought at that time, you must update that information in the appropriate controller configuration file. For instructions, see the webMethods Optimize and webMethods Manager Console Administrator’s Guide.

Manager server You must identify Manager server to the webMethods OMI explorer agent so My webMethods can display Manager server data. For instructions, see the webMethods Optimize and webMethods Manager Console Administrator’s Guide.

Monitor By default, the Monitor run time looks for the Monitor interface on My webMethods Server on the local host at port 8080. If My webMethods Server is on a different host machine or uses a different port, you must update that information in the Monitor run time configuration file, as follows:

1 Go to the Integration Server_directory/packages/ WmMonitor/config directory and open the monitor.cnf file in a text editor.

2 Change the myWebmethodsHost and myWebmethodsPort values as necessary.


Workflow If you chose to use My webMethods Server to authenticate Workflow users when you ran the Workflow Configurator, you identified My webMethods Server to Workflow Server at that time. No further configuration is required.



Connect Integration Server to the Default BrokerThis section explains how to connect Integration Server to the default Broker. For complete information on the entries below, and for information on configuring Integration Server to use SSL to connect to the Broker, see the webMethods Integration Server Administrator’s Guide.

1 Open Integration Server Administrator.

2 Go to Settings Broker and click Edit Broker Settings.

3 Click the Configured option button on the left side of the page and complete the boxes below.


Box Entry

Broker Host DNS host name or fully qualified IP address and port for the Broker Server.

Broker Name Name of the default Broker as defined on the Broker Server (that is, Broker #1).

Client Group Client group to which you want Integration Server to connect. Integration Server will create the client group when it connects to the Broker.

Client Prefix String that identifies Integration Server to the Broker. By default, Integration Server uses its license key for the prefix. For ease of use you can define your own, shorter, prefix name.



Redirect Products to Use a Non-Default JRE or JDKIf you installed a JRE or JDK for a product to use instead of the default JDK installed by the installer, follow the steps below to redirect the product.

Product Steps

webMethods Broker items (for example, Com‐mand Line tools)

In the steps below, command is any command other than server_config, awcert, awbroker, or awbrokermon.

webMethods Broker_directory\bin\command ‐DJAVA_HOME‐=JDK_path host:port

On a Windows system, the command might look like this:C:\Program Files\webMethods6\Broker\bin\broker_status -DJAVA_HOME-=C:\jdk1.4.2 localhost

On a UNIX or Linux system, the command might look like this:/opt/webMethods6/Broker/bin/broker_status -DJAVA_HOME=/opt/java1.4 localhost

Developer (and plug‐ins)

1 Go to the Developer_directory\bin directory and open the developer.bat or developer.sh file in a text editor.

2 Edit the JAVA_DIR parameter to point to the JRE installation directory, then save and close the file.

Integration Server (and pack‐ages)

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


Manager control‐ler, data handler, or satellite

1 Log on to the host machine for the controller, data handler, or satellite.

2 Go to the Optimize directory\item\bin directory and open the kenobiEnv.bat or kenobiEnv.sh file in a text editor.

3 Edit the JAVA_HOME parameter to point to the JDK or JRE installation directory, then save and close the file.

Manager server 1 Go to the Manager server_directory\bin directory and open the server.bat or server.sh file in a text editor.



Redirect Products to Use a Non-Default JRE or JDK

Modeler 1 Go to the Modeler_directory\bin directory and open the mod‐eler.bat or modeler.sh file in a text editor.

2 Edit the JAVAPATH parameter to point to the JRE installation directory, then save and close the file.

Note: When you launch Developer from Modeler, Developer runs in the same JVM as Modeler. If you decide to use a different JRE for Modeler, the JRE must be suitable for both Modeler and Devel‐oper.


1 Go to the Portal_directory\bin directory and open the set‐env.bat or setenv.sh file in a text editor.

2 Edit the JAVA_HOME parameter to point to the JRE installa‐tion directory, then save and close the file.

Optimize con‐troller, data han‐dler, or satellite

1 Log on to the host machine for the controller, data handler, or satellite.

2 Go to the Optimize directory\item\bin directory and open the kenobiEnv.bat or kenobiEnv.sh file in a text editor.

3 Edit the JAVA_HOME parameter to point to the JDK or JRE installation directory, then save and close the file.

Trading Net‐works Console

1 Go to the Trading Networks Console_directory\bin directory and open the console.bat or console.sh file in a text editor.

2 Edit the JAVA_ROOT parameter to point to the JRE installa‐tion directory, then save and close the file.

Note: When you launch Developer from Trading Networks Con‐sole, Developer runs in the same JVM as Trading Networks Con‐sole. If you decide to use a different JRE for Trading Networks Console, the JRE must be suitable for both Trading Networks Con‐sole and Developer.

Workflow client 1 Go to the Workflow client_directory\bin directory and open the console.bat or console.sh file in a text editor.

2 Edit the JAVA_ROOT parameter to point to the JDK installa‐tion directory, then save and close the file.

Product Steps



Complete the Instal lat ion for Other ProductsSome products not covered in this chapter have tasks you must complete that are beyond the scope of this guide. Make sure you check the product user’s guides for such tasks before starting the products.


P A R T VI
Uninstal lat ion
Uninstalling Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Dropping Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243


C H A P T E R 14
Uninstal l ing Products
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Uninstall on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Uninstall on a UNIX, Linux, OS/400, or Mac OS X System . . . . . . . . . . . . . . . . . . . . . . . . 239

Complete the Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240


C H A P T E R 1 4 U n i n s t a l l i n g P r o d u c t s

OverviewUninstall webMethods products using the webMethods Uninstaller. The webMethods Installer installed all files you need to run the uninstaller.

You can run the uninstaller using different modes, as follows:

To uninstall using the wizard on a UNIX or Linux system, your system must have an X‐Windows environment.

If errors or warnings occur during the uninstallation, the uninstaller writes the errors and warnings to a file named WmUninstallLog.txt and stores the file in the main installation directory (by default, webMethods6).

Uninstal l on a Windows SystemTo uninstall webMethods products on a Windows system, you must have Windows system administrator privileges.

1 Shut down all webMethods products and all other applications that are running on your machine.

2 Use the Windows Add/Remove Programs utility, available from the Control Panel, to start the uninstaller.

3 Select webMethods release installation_directory as the program to uninstall.

4 Choose the webMethods products to remove from your machine. For webMethods Broker, Integration Server, Developer, the uninstaller allows you to choose the parts of the product to remove. In addition, for webMethods Broker and Integration Server, the uninstaller asks whether it should delete program files that have been modified since you installed the product. For each product, choose to delete all the program files.

System Mode

Windows wizard

UNIX, Linux, or Mac OS X wizard or console mode

OS/400 console mode

Important! If you do not shut down all products and applications, the uninstaller will not be able to remove key files that are locked by the operating system.

Important! When you choose a product, the uninstaller asks whether it should also uninstall all products that depend on the product. Read the messages carefully to avoid uninstalling products accidentally.


Uninstall on a UNIX, Linux, OS/400, or Mac OS X System

Uninstal l on a UNIX, Linux, OS/400, or Mac OS X System

1 Log on as the same user that installed the webMethods products.

2 If the webMethods products you are uninstalling are located on a remote machine and you want to use a graphical uninstaller, follow these steps:

a Enable the display of the local machine using the command shown below, where remote_host is the remote machine from which to uninstall:xhost +remote_host

b Log on to the remote machine.

c Set the DISPLAY variable on the remote machine to point to the local machine. For example, if you are using a bash shell and are uninstalling from a local machine named uninstaller and want to set the DISPLAY to the default device, enter:export DISPLAY=uninstaller:0.0

3 Shut down all webMethods products and all other applications that are running on the machine that contains the webMethods products you are uninstalling.

4 Go to the webMethods_directory/bin directory and enter the appropriate command, as follows:

5 Choose the webMethods products to remove from the machine. For webMethods Broker, Integration Server, Developer, the uninstaller allows you to choose the parts of the product to remove. In addition, for webMethods Broker and Integration Server, the uninstaller asks whether it should delete program files that have been modified

Important! When you run the webMethods Uninstaller on an OS/400 system, the uninstaller experiences display problems. While these display problems will not adversely affect the uninstallation process, webMethods strongly recommends that you minimize the problems by running the uninstaller from an OS/400 client for Windows rather than from a telnet client.

Important! If you do not shut down all products and applications, the uninstaller will not be able to remove key files that are locked by the operating system.

Uninstall Mode Command

Wizard uninstall

Console mode uninstall -console



since you installed the product. For each product, choose to delete all the program files.

Complete the Uninstal lat ionFor most products, the uninstaller does not delete files created after you installed the product (for example, user‐created or configuration files), nor does it delete the directory structure that contains the files. If you do not want to save the files, delete the product installation directory.

Complete the Deployer UninstallationTo uninstall the Deployer communications component from source and target Integration Servers, follow these steps:

1 In the Integration Server Administrator for an Integration Server that hosts the resource package, go to the Packages Management page.

2 Delete the WmDeployerResource package.

To uninstall the Deployer communication component from source and target Portal servers, ask your Portal administrator to remove the portlet named Portal Deployer Plug‐in. The plug‐in ID is wm_deployerplugin‐pdp, and it is located in the Portal directory/SDK directory.

Complete the webMethods Mainframe UninstallationIf you installed Mainframe Adapter 4.6 and want to uninstall it, use the Windows Add/Remove Programs utility, available from the Control Panel.

If you install the webMethods Mainframe Developer Plug‐in, the uninstaller does not delete the webMethods Mainframe Developer Plug‐in log file, named Builder.log, from the Developer installation. If you do not want to save the file, go to the Developer installation directory (by default, webMethods6\Developer) and delete the Builder.log file.

Important! When you choose a product, the uninstaller asks whether it should also uninstall all products that depend on the product. Read the messages carefully to avoid uninstalling products accidentally.


Complete the Uninstallation

Complete the Modeler UninstallationIf you uninstalled Modeler, the uninstaller does not delete generated deployment files, exported XML files, or user preference files. If you do not want to save these files, delete them from the indicated directories:

If you uninstalled the Modeler Design Package, the uninstaller does not remove log files and, if the Modeler Repository writes to a flat file, the repository.db file. If you do not want to save the files, delete them from these directories:

Files Directory

Generated deployment (processname.xml)

webMethods_directory\Modeler\Deployment Info

Exported XML User‐specified

User preference (.wmModelerPrefs)

Documents and Settings\user directory (Windows system) or $HOME directory (Linux system)

Files Directory

Log webMethods_directory\Servers\RepoV3\logs

repository.db webMethods_directory\Servers\RepoV3\WmRepository


C H A P T E R 15
Dropping Database Components
Drop Database Components from Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

Drop Database Components from SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Drop Database Components from DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Drop the Database Components from Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250


C H A P T E R 1 5 D r o p p i n g D a t a b a s e C o m p o n e n t s

Drop Database Components from Oracle

Drop the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, and Trading Networks Database ComponentTo drop a database component, execute the script indicated below from your database editor. The scripts are located in the webMethods_directory\common\db\scripts\drop directory on the machine to which you downloaded the database scripts.

Drop the Analysis, Archive, Process Tracker, and Servicenet Database ComponentsDrop these database components by dropping the schema through the database administration utility provided by your database vendor.

Drop the My webMethods Server Database ComponentWhen you drop the My webMethods Server database component, the database user is deleted along with all user objects, such as tables, procedures, packages, and so forth.

You use different commands to drop the My webMethods Server database component depending on whether you are running the command from a machine that hosts My webMethods Server, Access, or Portal, or none of those products. If you want to drop the My webMethods Server database component from a machine that does not host any of those products, the machine must be equipped with an Oracle database client.

To drop the My webMethods Server database component, you must have database administrator privileges.

Component Script

Cross‐Reference drop_xref_6‐5.sql

Document History drop_idr_6‐5.sql

IS Core Audit Log drop_iscoreaudit_6‐5.sql

Modeler Repository drop_RepoV3_6‐5.sql

Process Tracking Store drop_prt_6‐5.sql

Reporting drop_reporting_6‐5.sql

Trading Networks drop_TN_6‐5.sql, drop_archive_TN_6‐5.sql

Staging drop_staging_6‐5.sql


Drop Database Components from Oracle

1 Follow the appropriate steps below.

2 Run this command:{dbdrop.{bat|sh} | dbdrop_sqlplus.{bat|sh}}database_server_host:database_server_port instanceadministrator_user administrator_password database_user


My webMethods Server or Access or Portal host machine

Open a command window and go to the My webMethods Server, Access, or Portal_directory\bin\db\ scripts\oracle directory.

Other machine If you have not yet copied the oracle directory to the machine equipped with an Oracle database client:

1 On the My webMethods Server, Access, or Portal host machine, go to the My webMethods Server, Access, or Portal_directory\bin\db\scripts directory.

2 Copy the oracle directory to the machine equipped with the Oracle database client.

Parameter Entry

{dbdrop.{bat|sh} | dbdrop_sqlplus.{bat|sh}}

If you are running the command from the My web‐Methods Server, Access, or Portal host machine, enter dbdrop.{bat|sh}. If you are running the command from a machine that does not host My webMethods Server, Access, or Portal, enter dbdrop_sqlplus.{bat|sh).

database_server_host Name or IP address of the machine that hosts the Ora‐cle database server. Do not use localhost to identify the host.

instance Name of the instance on database_server_host that con‐tains the My webMethods Server database component.


administrator_user

Administrator user for the database server.



database_user Database user My webMethods Server, Access, and Portal to use to communicate with the database server.



For example, the following command drops the My webMethods Server database component from the mywebmserver_db instance on the oraserver database server:dbdrop.bat oraserver:1521 mywebmserver_db sys syspassword mywebmserveruser

Drop Database Components from SQL Server

Drop the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, and Trading Networks Database ComponentsTo drop a database component, execute the script indicated below from your database editor. The scripts are located in the webMethods_directory\common\db\scripts\drop directory on the machine to which you downloaded the database scripts.

Drop the Manager Server and Process Audit Log Database ComponentsTo drop a database component, execute the script indicated below from your database editor. The script is in the webMethods_directory\scripts\mssql\code\component\drop directory on the machine to which you downloaded the database scripts.

Component Oracle, SQL Server, and DB2









Important! Before dropping the Manager server database component, shut down all Manager servers that are connected to the database component. Doing so will make sure Manager servers access the correct data after restart.


Drop Database Components from SQL Server

Drop the Analysis, Archive, Process Tracker, and Servicenet Database ComponentDrop these database components by dropping the database through the database administration utility provided by your database vendor.

Drop the My webMethods Server Database ComponentWhen you drop the My webMethods Server database component, the database user is deleted along with all user objects, such as tables, procedures, packages, and so forth.

You use different commands to drop the My webMethods Server database component depending on whether you are running the command from a machine that hosts My webMethods Server, Access, or Portal, or none of those products. If you want to drop the My webMethods Server database component from a machine that does not host any of those products, the machine must be equipped with the OSQL utility.

To drop the My webMethods Server database component, you must have database administrator privileges.

1 Follow the appropriate steps below.

2 Run this command:{dbdrop.bat | dbdrop_osql.bat}database_server_host:database_server_port databaseadministrator_user administrator_password database_user

Component Script

Manager server drop_ManagerServer_6‐5.sql

Process Audit Log metadata.sql, processrecent.sql, runtime.sql


Portal host machine

Open a command window and go to the My webMethods Server, Access, or Portal_directory\bin\db\scripts\ mssql directory.


2 Copy the mssql directory to the machine equipped with the OSSQL utility.



For example, the following command drops the My webMethods Server database component from the mywebmserver_db database on the sqlserver database server:dbdrop.bat sqlserver:1433 mywebmserverdb sa password mywebmserveruser

Drop Database Components from DB2


Parameter Entry

{dbdrop.bat | dbdrop_osql.bat}

If you are running the command from the My web‐Methods Server, Access, or Portal host machine, enter dbdrop.bat. If you are running the command from a machine that does not host My webMethods Server, Access, or Portal, enter dbdrop_osql.bat.

database_server_host Name or IP address of the machine that hosts the SQL Server database server. Do not use localhost to identify the host.

database Name of database on database_server_host containing the My webMethods Server database component.

database_server_port Port the database server uses to communicate. The default port for SQL Server is 1433.


administrator_password Administrator password for the database server.

database_user Database user My webMethods Server, Access, and Portal use to communicate with the database.

Component Scripts





Drop Database Components from DB2

Drop the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database ComponentsYou can drop these database components using the webMethods Database Installer or you can drop them manually.

Drop the Database Components Using the Database Installer1 On the DB2 database server host machine, go to the webMethods_directory\common\

db\scripts\db2 directory.

2 Start the webMethods Database Installer by running this command:ibmDB2.{bat | sh}

3 Choose Drop a Database Component, then choose the database component to drop.

Drop the Database Components ManuallyOpen a command window and go to the webMethods_directory\common\ db\scripts\db2 directory. Run the scripts in the order indicated below.







Analysis code/analysis/drop/db2_anl_d_ddl_tables_indexes.sql

ProcessTracker code/processtracker/drop/db2_ptr_d_ddl_tables_indexes.sql

ProcessAudit code/processaudit/drop/fieldalias_triggers.sql

code/processaudit/drop/processrecent_triggers.sql

code/processaudit/drop/metadata.sql

code/processaudit/drop/runtime.sql

code/processaudit/drop/processrecent.sql

ManagerServer code/managerserver/drop/db2_mgr_d_ddl_tables_indexes.sql

Component Scripts



Drop the Database Components from Sybase


Drop the Archive and Process Audit Log Database Components

Set the Database Connection Properties1 On the machine to which you downloaded the database scripts and the webMethods

Database Installer, go to the webMethods_directory\common\db\scripts\sybase directory and open the sybase_env_properties.{bat|sh} file in a text editor.

Archive code/processaudit/drop/metadata.sql

code/processaudit/drop/runtime.sql

code/processaudit/drop/processrecent.sql

../drop/drop_iscoreaudit_6‐5.sql

code/archive/drop/db2_opmgmt_c_ddl_tables_indexes.sql

code/archive/drop/db2_arc_c_ddl_tables_indexes.sql

code/archive/drop/drop_archive_procedures.sql


Component Scripts

Cross‐Reference drop_xref_6‐5_Sybase.sql

Document History drop_idr_6‐5_Sybase.sql

IS Core Audit Log drop_iscoreaudit_6‐5_Sybase.sql

Reporting drop_reporting_6‐5_Sybase.sql

Trading Networks drop_TN_6‐5_Sybase.sql, drop_archive_TN_6‐5_Sybase.sql

Staging drop_staging_6‐5_Sybase.sql


Drop the Database Components from Sybase

2 After you installed the database components, you removed the database user password from the database connection properties file for security reasons. To be able to drop the database components, you must re‐enter the password. Edit these connection properties for each database component you are going to drop:set database_component_DB=database_nameset database_component_USR=database_userset database_component_PWD=database_user_password


Drop the Database Components1 If you installed the IS Core Audit Log driver tables (because you installed the Archive

database component, and the IS Core Audit Log and the Process Audit Log database components are on separate database servers), drop the driver tables by navigating to the webMethods_directory\common\db\scripts\sybase\code\ archive\drop directory and executing the SQL script sybase_arc_c_ddl_tables_indexes.sql.

2 Go to the webMethods_directory\common\db\scripts\sybase directory and drop the database components as follows:

Important! Database names are case sensitive. You must use the right casing for the database name in the connection properties or the drop will fail.

To drop this database component... Run this program...

Archive drop_archive_6‐5.{bat | sh}

Process Audit Log drop_processaudit_6‐5.{bat | sh}


A P P E N D I X A
Default Ports
Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254


A P P E N D I X A D e f a u l t P o r t s

Default Ports

Component Default PortProtocol/Port Type

Access, My webMethods Server, and Portal

RMI registry ‐ communication among clustered Access or Portal servers

1097 RMI

Diagnostics 5000 HTTP

AJP13 ‐ Jetty listens to external Web server, if using one (not enabled by default)

8009 AJP13

Jetty HTTP Web server 8080 HTTP

Jetty HTTPS Web server (not enabled by default)

8443 HTTPS

webMethods Broker

Broker Server 6849 (SSL not enabled)6848 (SSL enabled)6847 (SSL authenticated)

TCP

Default Broker 6849 TCP

Broker Monitor 6850 TCP

Dashboard application server 8080 HTTP

Integration Server 5555 HTTP

Communication with remote repository 7777 Proprietary binary protocol over TCP

Communication among clustered Integration Servers

8897 Proprietary binary protocol over TCP

Diagnostics 9999 HTTP


Default Ports

JBoss Package

JNDI ‐ RMI clients call remote Java Object methods on Integration Server through sockets

1099 Client APIs

RMI ‐ EJB clients access the JNDI naming service in JBoss

4444 RMI

Hypersonic SQL database ‐ communication between JBoss and default Hypersonic SQL database

1701 JDBC over TCP

Jetty HTTP ‐ HTTP clients call Integration Server services and access JSPs in WARs that are deployed on Integration Server

8080 HTTP

webMethods Mainframe 8087 TCP/IP

Modeler Repository 7778 RMI


Controller

HTTP ‐ communication with other webMethods products

12503 HTTP

JMX ‐ listen for data from satellites and data handler

12501 HTTP

Data handler

HTTP ‐ communication with clients publishing to Web service DCAs

12603 HTTP

JMX ‐ listen for data from controller 12601 HTTP

Satellite

HTTP ‐ communication with clients publishing to Web service DCAs

12005 HTTP

JMX ‐ listen for data from controller 12001 HTTP




Servicenet

Controller

Diagnostics for JMX view of Manager and Optimize

12500 HTTP

Listen for data from data handler and satellites on intermediaries

12501 JMX over HTTP

Listen for data from clients 12503 HTTP

JVM diagnostic port (not enabled by default)

5005 TCP

Data handler

Communication with clients publishing to Web service DCAs

12603 HTTP

Listen for data from controller 12103 JMX over HTTP


5005 TCP

Registry

Listen for data from clients 8088 SOAP over HTTP

Listen for data from satellite 12030 JMX over HTTP


5007 TCP

Intermediary

Listen for requests from Web service clients

2112 SOAP over HTTP

Listen for data from satellite 12031 JMX over HTTP


5008 TCP

Subnet locator discovery port 9030 UDP proprietary



Default Ports

Workflow Server

Communication between Workflow Server and Workflow clients

6000 (Windows XP Professional)5000 (all other systems)

HTTP

RMI registry 6001 (Windows XP Professional5001 or 6001 if 5001 is in use (all other systems)

RMI



A P P E N D I X B
Database Components
Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Monitor Service pub.monitor.archive:setOperationParameters . . . . . . . . . . . . . . . . . . . . . . 264


A P P E N D I X B D a t a b a s e C o m p o n e n t s

Descript ionsThe webMethods database components are described below.

Database Compo-nent Description

Analysis The following write data to this database component:

The Manager and Optimize data handler writes process and monitoring data it receives from satellites

The Manager and Optimize controller evaluates the data and writes rule and fingerprint evaluations

Servicenet writes monitoring, rule, SLA, and action data

My webMethods displays the data.

Archive Monitor can archive data that was originally stored in the IS Core Audit Log and Process Audit Log database components to this database component. Monitor can archive documents and data for 4.x activations, processes, and services. Monitor can also archive server data, which includes Integration Server server, session, and guaranteed delivery log entries, and error log entries that are not associated with logged processes, services, 4.x activations, or doc‐uments (for example, errors that occur during startup or during the run of unlogged processes, services, activations, and docu‐ments).

Cross‐Referencing Integration Server can write cross‐reference keys and process integrity status information required to synchronize updates among various webMethods products and their database compo‐nents to this database component. By default, Integration Server writes this information to flat files.

Document His‐tory

Integration Server writes the history of documents that are pro‐cessed by triggers configured for exactly‐once processing to this database component.


Descriptions

IS Core Audit Log Integration Server can write the following to this database compo‐nent:

Error, guaranteed delivery, service, and session data (by default, Integration Server writes this information to flat files)

Documents that are in doubt, have failed, and or have exhausted trigger retries

Documents logged by Brokers for all JMS clients and all Bro‐ker clients except Workflow processes; the Logging Utility takes the documents from the Brokers and passes it to Integra‐tion Server

Integration Server Administrator and Monitor display different parts of this data.

Integration Server repository

Integration Servers in a cluster can write their state to this data‐base component so transactions can be continued on other Inte‐gration Servers in the cluster if the original Integration Server fails. Clustered Integration Servers use the repository to keep track of scheduled jobs, session context, and jobs tracked by guar‐anteed delivery. Integration Servers also store information needed by the Brokers to which they connect.

Manager server Manager server writes objects, notifications, and configurations to this database component. The data is displayed in the Manager server interface.

Manager server stores metadata about its management model and instances of objects within the management model in this data‐base component. If you have to restart Manager server, the man‐agement model can be recreated with the correct state.

Modeler Reposi‐tory

The Modeler Design Package includes the Modeler Repository, a storage area in which Modeler saves process model information and the files needed to create and generate process models. By default, the Modeler Repository writes to a flat file. Flat file storage is sufficient for most installations. If your Modeler usage is extremely high, however, and you have sufficient resources to handle the overhead of maintaining a database, you can configure the Modeler Repository to write to this database component instead.





My webMethods Server, Access, and Portal write data about deployment, configuration, security, portal pages, and the My webMethods Server run time to this database component. My webMethods Server uses this data to manage the My web‐Methods, Access, and Portal user interfaces.

Process Audit Log Integration Server can write the following to this database compo‐nent:

Modeler process data; the data is passed to Integration Server by the PRT

Documents and process data logged by Brokers for client Workflow processes; the Logging Utility takes the documents and data from the Brokers and passes it to Integration Server

Monitor displays this data. Optimize obtains process model defi‐nitions from this database component so it can analyze capabili‐ties such as transition duration.

Servicenet requires but does not use this database component. Servicenet requires this database component because its controller is based on Optimize, and Optimize requires this database com‐ponent.

Process Tracker The Manager and Optimize data handler writes business, system, and process data it receives from satellites to this database compo‐nent.

Servicenet requires but does not use this database component. Servicenet requires this database component because its controller is based on Optimize, and Optimize requires this database com‐ponent.


The PRT can write process execution data to this database compo‐nent. By default, the PRT writes to RAM.

Reporting Monitor built‐in services can write process status data extracted from the Process Audit Log database component and aggregated into daily statistics to this database component. Monitor displays this data.

Note: Reporting is available only on data collected after January 1, 2003. Also, the reports are only available in English. They are not localized and are not available in the JA language pack.



Descriptions

Servicenet Servicenet writes UDDI‐based catalog data that identifies the Web services that are under Servicenet management to this database component. The services can then be monitored and managed through the Servicenet interface.

Servicenet writes the following to this database component:

UDDI‐based catalog data that identifies the Web services that are under Servicenet management

Servicenet intermediary data

Logging data generated by Servicenet events

My webMethods displays the services, the intermediary data, and the logging data.

Staging Monitor built‐in services use this database component to accumu‐late the process status data extracted from the Process Audit Log database component so the data can be manipulated and then loaded into the Reporting database component.

Trading Networks Trading Networks Server writes its metadata (partner profiles, trading partner agreements, document types, processing rules, and partner profile groups) and run‐time data (documents; docu‐ment content parts, attributes, and delivery information; and log entries about document processing steps) to this database compo‐nent. Trading Networks Console displays the data.

Workflow Workflow Server writes critical process and task run‐time state data and monitoring data to this database component.




Monitor Service pub.monitor.archive:setOperat ionParametersSets parameters in the OPERATION_PARAMETER table of the Archive database component if you are using Oracle, SQL Server, or DB2. The names of the parameters in the table below exactly match the column names in the table.

Input Parameters

PROCESSAUDIT_DBLINK

String For SQL Server, if you want to archive from the Process Audit Log and the Archive and Process Audit Log database components are on different database servers, enter the Linked Server name to use to link the database components. If you do not want to archive from the Process Audit Log database component, or the database components are on the same database server, enter null.

ISCOREAUDIT_DBLINK

String For SQL Server, if you want to archive from the IS Core Audit Log, and the Archive and IS Core Audit Log database components are on different database servers, enter the Linked Server name to use to link the database components. If you do not want to archive from the IS Core Log database component, or the database components are on the same database server, enter null.

PROCESS_SCHEMA String If you want to archive from the Process Audit Log database component, enter the following for the Process Audit Log database component:

RDBMS Entry

Oracle Database user

SQL Server Database name

DB2 Schema name

If you do not want to archive from the Process Audit Log database component, enter null.

ISCORE_SCHEMA String If you want to archive from the IS Core Audit Log database component, enter the following for the IS Core Audit Log database component:

RDBMS Entry

Oracle Database user

SQL Server Database name


Monitor Service pub.monitor.archive:setOperationParameters

Output Parameters

DB2 Schema name

If you do not want to archive from the IS Core Audit Log database component, enter null.

message String Message that indicates that the parameters have been set.


A P P E N D I X C
Create the Broker Server Configurat ion Manual ly
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Create the Broker Server Data Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Set Up Broker Monitor on UNIX or Linux Systems (Non-Root User) . . . . . . . . . . . . . . . . . 270

Create the Broker Server on Any System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Create the Default Broker on Any System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Enable the Broker Server to Log Events to the UNIX or Linux System Log . . . . . . . . . . . . 279

Adjust Per-Process and Kernel Limits on HP-UX Systems . . . . . . . . . . . . . . . . . . . . . . . . . 280

Set Locale on UNIX or Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

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


A P P E N D I X C C r e a t e t h e B r o k e r S e r v e r C o n f i g u r a t i o n M a n u a l l y

OverviewYou must complete the instructions in this appendix if you did not use the webMethods Installer to create the Broker Server configuration. You did not use the installer to create the Broker Server configuration in these cases:

You installed webMethods Broker on a UNIX or Linux system as a non‐root user. In this case you must complete all tasks in this chapter.

You installed on a UNIX or Linux system as root user or you installed on a Windows system, but you wanted to specify a different storage size than is available through the installer or you wanted to create a combined storage session for configuration and run‐time data. In this case you must complete all tasks in this chapter except “Set Up Broker Monitor on UNIX or Linux Systems (Non‐Root User)” on page 270.

Create the Broker Server Data Directory

Create the Data Directory on UNIX or Linux Systems as Non-Root User1 Log in as the same non‐root user that you logged in as to install webMethods Broker.

2 Create the directory in which you want Broker Server to store data (that is, the Broker Server data directory).

3 Go to the webMethods Broker directory (by default, webMethods6/Broker) and open the S45broker65 file in a text editor.

a Set the DEFAULT_ACTIVE_CONFIG parameter as follows:DEFAULT_ACTIVE_CONFIG=fully_qualified_path_to_Broker_Monitor_configuration_directory

Important! You must have installed webMethods Broker using the webMethods Installer for the instructions in this appendix to work. You should never install webMethods Broker by copying the product files from one directory to another.

Note: When the installer is used to create the Broker Server configuration, the default data directory is /var/opt/webmethods/awbrokers65/default. If you want to create that directory to be the Broker Server data directory, ask your system administrator for full read and write permissions to the /var/opt directory.

Do not use the /tmp directory as the Broker Server data directory. Make sure the Broker Server data directory does not contain a file named awbroker.cfg; such a file indicates that the directory is in use by another Broker Server


Create the Broker Server Data Directory

For example:DEFAULT_ACTIVE_CONFIG=/var/opt/webmethods

b Set the DEFAULT_ACTIVE_HOME parameter as follows:DEFAULT_ACTIVE_HOME=webMethods Broker_directory

For example:DEFAULT_ACTIVE_HOME=/opt/webMethods6/Broker


4 Export the values you just set to your current environment.

a Export the DEFAULT_ACTIVE_CONFIG parameter to ACTIVE_CONFIG as follows:

b Export the DEFAULT_ACTIVE_HOME parameter to ACTIVE_HOME as follows:

System Command and Example

csh setenv ACTIVE_CONFIG fully_qualified_path_to_Broker_Monitor_configuration_directory

Example: setenv ACTIVE_CONFIG /var/opt/webmethods

ksh/bash export ACTIVE_CONFIG=fully_qualified_path_to_Broker_Monitor_configuration_directory

Example: export ACTIVE_CONFIG /var/opt/webmethods

System Command and Example

csh setenv ACTIVE_HOME webMethods Broker_directory

Example: setenv ACTIVE_HOME /opt/webMethods6/Broker

ksh/bash export ACTIVE_HOME=webMethods Broker_directory

Example: export ACTIVE_HOME /opt/webMethods6/Broker



Create the Data Directory on a UNIX or Linux Systems as Root UserLog in as the root user and create the directory in which you want Broker Server to store data (that is, the Broker Server data directory).

Create the Data Directory on Windows SystemTo complete this step, you must have Windows system administrator privileges.

Create the directory in which you want Broker Server to store data (that is, the Broker Server data directory).

Set Up Broker Monitor on UNIX or Linux Systems (Non-Root User)

If you installed webMethods Broker as a non‐root user, you must set up Broker Monitor to run as either a daemon that starts and shuts down automatically when your system starts and shuts down, or an application that you start and shut down manually. The Broker Monitor controls the Broker Server; when the Broker Monitor starts or shuts down, it starts or shuts down the Broker Server.

Run as Daemon1 Log in under the non‐root user ID you used to install webMethods Broker.

2 If you configured Broker Server to create data files on an NFS‐mounted partition, go to the webMethods Broker directory and open the S45broker65 file in a text editor. The S45broker65 file is the script that starts and stops Broker Monitor.

Note: When the installer is used to create the Broker Server configuration, the default data directory is /var/opt/webmethods/awbrokers65/default.

Do not use the /tmp directory as the Broker Server data directory. Make sure the Broker Server data directory does not contain a file named awbroker.cfg; such a file indicates that the directory is in use by another Broker Server.

Note: When the installer is used to create the Broker Server configuration, the default data directory is C:\Program Files\webMethods6\ Broker\data\awbrokers65\default.

Do not use the temp directory as the Broker Server data directory. Make sure the Broker Server data directory does not contain a file named awbroker.cfg; such a file indicates that the directory is in use by another Broker Server.


Set Up Broker Monitor on UNIX or Linux Systems (Non-Root User)

Locate this line:${NOHUP_CMD} ${ACTIVE_HOME}/bin/awbrokermon > /dev/null 2>&1 &

Add this line after ${NOHUP_CMD}:su non_root_user -c

For non_root_user, specify the non‐root user you used to install webMethods Broker. For example:${NOHUP_CMD} su qa -c ${ACTIVE_HOME}/bin/awbrokermon > /dev/null 2>&1 &


3 Create the directory you want to use as the Broker Monitor configuration directory.

4 Go to the Broker Monitor configuration directory. Create the configuration file awbrokermon.cfg by entering this command on a single line:$ webMethods Broker_directory/bin/awbrokermon-config webMethods Broker_directory/ -user non_root_user -group non_root_user_group

For non_root_user and non_root_user_group, specify the non‐root user and non‐root user group you used to install webMethods Broker. For example:$ /opt/webMethods6/Broker/bin/awbrokermon -config /opt/webMethods6/Broker -user qa group Eng

5 Ask your system administrator to do the following:

a Copy the S45broker65 file you just modified to the /rc3.d directory. This directory is located as follows:

b Go to the rc3.d directory and run this command to start Broker Monitor:./S45broker65 start

Broker Monitor will launch as root at first, but then will switch to running under the user ID and group ID that you supplied in the awbrokermon.cfg file.

Note: When the installer is used to create the Broker Monitor configuration directory, the default is /var/opt/webmethods. If you want to create that directory to be the Broker Monitor configuration directory, ask your system administrator for full read and write permissions to the /var/opt directory.

System Directory

AIX /var/opt/webmethods

Hewlett‐Packard /sbin/rc3.d

Solaris and Linux Red Hat /etc/rc3.d

SUSE Linux etc/rc.d/rc3.d



6 Make sure Broker Monitor is running by entering this command:ps –ef | grep aw

Run as Application1 Log in under the non‐root user ID you used to install webMethods Broker.

2 Create the directory you want to use as the Broker Monitor configuration directory.

3 Go to the Broker Monitor configuration directory. Create the configuration file awbrokermon.cfg by entering this command on a single line:$ webMethods Broker_directory/bin/awbrokermon -config webMethods Broker_directory/ -user non_root_user -group non_root_user_group

For non_root_user and non_root_user_group, specify the non‐root user and non‐root user group you used to install webMethods Broker. For example:$ /opt/webMethods6/Broker/bin/awbrokermon -config /opt/webMethods6/Broker -user qa -group Eng

4 Run this command to start Broker Monitor:$ webMethods Broker_directory/S45broker65 start

For example:

/opt/webMethods6/Broker/S45broker65 start

5 Make sure Broker Monitor is running by entering this command:ps –ef | grep aw

Create the Broker Server on Any SystemThe command you run to create the Broker Server also creates the Broker Server configuration file awbroker.cfg and the data files that will be used by individual Brokers running on the Broker Server. The command places the awbroker.cfg file and the data files in the Broker Server data directory.

The command also lets you create either separate storage sessions for the configuration (metadata) and run‐time data or a combined storage session for both types of data.

Using separate storage sessions minimizes the risk of corruption that might occur with a combined storage location. In addition, you can use the webMethods Broker

Note: When the installer is used to create the Broker Monitor configuration directory, the default is /var/opt/webmethods. If you want to create that directory to be the Broker Monitor configuration directory, ask your system administrator for full read and write permissions to the /var/opt directory.


Create the Broker Server on Any System

6.5 online configuration data backup tool to back up configuration data without having to shut down your Broker Server. For more information about the tool, see the webMethods Broker Administrator’s Guide.

A combined storage session is the type of storage that was used in webMethods Broker 6.1 and earlier. If you do not need to use the online configuration data backup tool, using a combined session might save you a small amount of disk space.

Create Separate Storage SessionsRun the command below to create the Broker Server, its accompanying files, and separate storage sessions for configuration and run‐time data. You must type the entire command on a single line.server_config create data_directory -k license_key [-d description] [-p port] [-nostart] [-S] [-session_config qs [-qs_log_file file_name file_size]

[-qs_storage_file file_name file_size [reserved_size]][-session_data qs [-qs_log_file file_name file_size]

[-qs_storage_file file_name file_size [reserved_size]]

Important! You cannot later change from separate sessions to the combined session or vice versa. webMethods recommends creating separate sessions.

Argument Description

data_directory Fully qualified path to the Broker Server data directory. If the path includes spaces, enclose it in double quotation marks. The default Broker Server data directory for UNIX or Linux is /var/opt/webmethods/awbrokers65/default. For Windows, it is C:\Program Files\webMethods6\ Broker\data\awbroker65\default.

-k license_key Broker Server run‐time license key.

[-d description] One‐line description for the Broker Server. If the string includes spaces, enclose it in double quotation marks. The description will appear in the Broker Administrator main window.

[-p port] The default port for Broker Servers is 6849. If another Bro‐ker Server is using that port, you must use this argument to identify the port the Broker Server you are creating is to use.

[-nostart] By default, the command starts the Broker Server automat‐ically after it creates it. If you want to start the Broker Server manually later instead, use this argument to pre‐vent the command from starting the Broker Server.



[-S] By default, the command writes error messages to stderr and information messages to stdout. If you want to write error messages to stdout and suppress information mes‐sages instead, use this argument.

[-session_config qs] Creates the configuration storage session. By default, the command creates two files in the default Broker Server data directory:

Log file named BrokerConfig.qs.log with a maximum size of 32M

Storage file named BrokerConfig.qs.stor with a maximum size of 512M and an initial (reserved) size of 64M

The default Broker Server data directory for UNIX or Linux is /var/opt/webmethods/awbrokers65/default. For Windows, it is C:\Program Files\webMethods6\Broker\ data\awbroker65\default.

[-session_data qs] Creates the run‐time storage session. By default, the command creates two files in the default Broker Server data directory:

Log file named BrokerData.qs.log with a maximum size of 32M

Storage file named BrokerData.qs.stor with a maximum size of 512M and an initial (reserved) size of 64M


[-qs_log_file file_name file_size]

[-qs_storage_filefile_name file_size [reserved_size]]

If you want to use a different name for the log or storage file, or if the Broker Server data directory is not in the default location, use the file_name parameter to specify the fully qualified path to the file. You can also use the parameter to create additional storage files for either type of session.

If you want to specify a different maximum size for the log or storage file, use the file_size parameter. Follow the size with K (kilobytes), M (megabytes), or G (gigabytes). For information on setting the maximum size of these files, see “Configure webMethods Broker” on page 113.




UNIX or LinuxAn example of this command for UNIX or Linux is as follows:server_config create /var/opt/webmethods/awbrokers65/default-k license_key -p 8800 -session_data qs-qs_log_file /var/opt/webmethods/awbrokers65/default/BrokerData.qs.log 256M-qs_storage_file /var/opt/webmethods/awbrokers65/default/BrokerData.qs.stor 10G 1G-session_config qs -qs_log_file /var/opt/webmethods/awbrokers65/default/BrokerConfig.qs.log 32M 512M -qs_storage_file /var/opt/webmethods/awbrokers65/default/BrokerConfig.qs.stor 64M 32M

You will see the message, ʺSuccessfully created Broker Server in data_directory.”

Make sure the Broker Monitor and the Broker Server are running by entering this command:ps -ef | grep aw

WindowsAn example of this command for Windows is as follows:server_config create C:\Program Files\webMethods6\Broker\data\awbrokers65\default-k license_key -p 8800 -session_data qs-qs_log_file C:\Program Files\webMethods6\Broker\data\awbrokers65\default\ BrokerData.qs.log 256M-qs_storage_file C:\Program Files\webMethods6\Broker\data\awbrokers65\default\ BrokerData.qs.stor 10G 1G-session_config qs-qs_log_file C:\Program Files\webMethods6\Broker\data\awbrokers65\default\ BrokerConfig.qs.log 32M 512M -qs_storage_file C:\Program Files\webMethods6\Broker\data\awbrokers65\default\ BrokerConfig.qs.stor 64M 32M

If you want to specify a different initial size for the storage file, use the reserved_size parameter. Follow the size with K (kilobytes), M (megabytes), or G (gigabytes). The size must be at least 16M.

Anticipate a small delay in operation while the command initializes the files.

After installation, you can remove or replace log files, and you can increase or decrease their size. You can add storage files and increase their size, but you cannot remove storage files or decrease their size. The webMethods Broker Administrator’s Guide provides instructions.


Note: If you experience problems running this long command in your current shell, try running it in a bash shell.




Make sure the Broker Monitor and the Broker Server are running. Open the Services window. Locate the service webMethods Broker Server 6.5, port xxxx, and make sure its status is Started.

Create a Combined Storage SessionRun the command below to create the Broker Server, its accompanying files, and a combined storage session for configuration and run‐time data. You must type the entire command on a single line.server_config create data_directory -k license_key [-d description] [-p port] [-nostart] [-S] [-session_config qs [-qs_log_file file_name file_size]

[-qs_storage_file file_name file_size [reserved_size]]]-use_combined_storage


data_directory Fully qualified path to the Broker Server data directory. If the path includes spaces, enclose it in double quotation marks. The default Broker Server data directory for UNIX or Linux is /var/opt/webmethods/awbrokers65/default. For Windows, it is C:\Program Files\webMethods6\ Broker\data\awbroker65\default.

-k license_key Broker Server run‐time license key.

[-d description] One‐line description for the Broker Server. If the string includes spaces, enclose it in double quotation marks. The description will appear in the Broker Administrator main window.

[-p port] The default port is 6849. If another Broker Server is using that port, you must use this argument to identify the port the Broker Serveryou are creating is to use.

[-nostart] By default, the command starts the Broker Server automat‐ically after it creates it. If you want to start the Broker Server manually later instead, use this argument to pre‐vent the command from starting the Broker Server.

[-S] By default, the command writes error messages to stderr and information messages to stdout. If you want to write error messages to stdout and suppress information mes‐sages instead, use this argument.



[-session_config qs

[-qs_log_file file_name file_size]

[-qs_storage_filefile_name file_size [reserved_size]]]

By default, the command creates two files in the default Broker Server data directory:

Log file named Broker.qs.log with a maximum size of 32M

Storage file named Broker.qs.stor with a maximum size of 512M and an initial (reserved) size of 64 M


If you want to use a different name for the log or storage file, or if the Broker Server data directory is not in the default location, use the file_name parameter to specify the fully qualified path to the file. You can also use the parameter to create additional storage files for the session.

If you want to specify a different maximum size for the log file or the storage file, use the file_size parameter. Follow the size with K (kilobytes), M (megabytes), or G (gigabytes). For information on setting the maximum size of the log file and the storage file, see “Configure webMethods Broker” on page 113.

If you want to specify a different initial size for the storage file, use the reserved_size parameter to specify the size followed by K (kilobytes), M (megabytes), or G (gigabytes). The size must be at least 16M.

Anticipate a small delay in operation while the command initializes the files.

After installation, you can remove or replace log files, and you can increase or decrease their size. You can add storage files and increase their size, but you cannot remove storage files or decrease their size. The webMethods Broker Administrator’s Guide provides instructions.

-use_combined_storage Tells the command to create a combined storage session for configuration and run‐time data.




UNIX or LinuxAn example of this command for UNIX or Linux is as follows:server_config create /var/opt/webmethods/awbrokers65/default2 -k license_key-p 7700 -session_config qs-qs_log_file /var/opt/webmethods/awbrokers65/default/Broker.qs.log 256M-qs_storage_file /var/opt/webmethods/awbrokers65/default/Broker.qs.stor 10G 1G-use_combined_storage


Make sure the Broker Monitor and the Broker Server are running by entering this command:ps -ef | grep aw

WindowsAn example of this command for Windows is as follows:server_config create C:\Program Files\webMethods6\Broker\data\awbrokers65\default-k license_key -p 7700 -session_config qs-qs_log_file C:\Program Files\webMethods6\Broker\data\awbrokers65\default\ Broker.qs.log 256M-qs_storage_file C:\Program Files\webMethods6\Broker\data\awbrokers65\default\ Broker.qs.stor 10G 1G-use_combined_storage


Make sure the Broker Monitor and the Broker Server are running. Open the Services window. Locate the service webMethods Broker Server 6.5, port xxxx, and make sure its status is Started.

Note: If you experience problems running this long command in your current shell, try running it in a bash shell.


Create the Default Broker on Any System

Create the Default Broker on Any SystemRun this command:webMethods Broker_directory/bin/broker_createBroker[@Broker_Server[:port]] -default [-description text][-createterr territory] [-jointerr Broker[@Broker_Server[:port]]]

An example of this command is as follows:webmethods6/Broker/bin/broker_create "Broker #1"@hostname:7700 -default

Use Broker Administrator to make sure the default Broker (Broker #1) is running. For instructions, see the webMethods Broker Administrator’s Guide.

Enable the Broker Server to Log Events to the UNIX or Linux System Log

If you want the Broker Server to log Broker Server events to the UNIX or Linux system log, ask your system administrator to create the necessary entries in the UNIX or Linux system log configuration file. The system administrator must log on as root user and run these commands:$ echo "local5.alert /var/log/broker.alert" >> /etc/syslog.conf$ echo "local5.info /var/log/broker.info" >> /etc/syslog.conf


Broker[@Broker_Server [:port]

Broker specifies the name to give the Broker you are creating.

Broker_Server [:port] identifies the Broker Server on which the Broker is to run (that is, the Broker Server you just created). If the Broker Server is on the local host, you do not have to specify these arguments.

[description text] One‐line description of the Broker. If the string includes spaces, enclose it in double quotation marks. The description will appear in the Broker Administrator main window.

[-createterr territory]

Creates a new territory and makes the Broker you are creating the first member of that territory.

[-jointerr Broker[@Broker_Server[:port]]

Identifies an existing Broker and makes the Broker you are creating a member of the same territory of which the existing Broker is a member.



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

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

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

Run this command:chdev -l sys0 -a fullcore=true

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

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


Index

Numerics64-bit JDK, have installer install 81

AAccess

hardware requirements 40installation location 18

Administratorhardware requirements 40installation location 19

advanced optionsdescription of 70use to install 76, 78, 108valid combinations of 71

BBroker (webMethods Broker)

adjust per-process thread limit on HP-UX system 280adjust per-process thread limit on HP-UX systems 190configure Brokers and JMS 20data directory for Broker Server 87, 113develop custom C messaging applications 20develop custom Java messaging applications 20develop custom JMS messaging applications 21hardware requirements 40, 41installation location 19license key 87, 113make sure default Broker is running 189port for Broker Server 87, 113set per-process and kernel limit for open files on HP-UX

system 280set per-process and kernel limit for open files on HP-UX

systems 190use non-default JDK 232

Broker Administrator, installation location 19

Broker Serverconfigure storage session 88, 114data directory for 87, 113log file size 88, 114port for 87, 113

browsers, required 38

Ccommand line, use to install from an installation script on a

Windows system 106console mode

use to install 107use to uninstall 239

conventions used in this document 12corrupt installations, overwrite 103, 124Cross-Reference database component

set up JDBC connection pool 170

DData Connection Limited SNAP-IX 38database components

descriptions 260drop My webMethods Server using commands 244, 247install My webMethods Server using commands 138, 149install My webMethods Server using configurator 183install using SYS or SYSTEM user account 46install Workflow 213products that require them 260where to install them 34, 35

database drivers, supported 44database servers

bandwidth 34hardware 44

database URLsDB2 172Oracle 171SQL Server 171Sybase 171


I n d e x

database user 130, 132, 144, 146, 154, 155, 157, 164, 166database user permissions 130, 144, 154, 155, 157, 164, 166databases

character set and sort order 44encodings for international operating environments 50page and block size 44supported 44

DB2 URLs 172dependencies among webMethods products 18Deployer

hardware requirements 40, 41installation location 21

Developerbrowse services in Servicenet 22develop C/C++ services 22generate services from a .NET assembly 22hardware requirements 40installation location 22rebuild C/C++ shared libraries 22use non-default JDK 232

display problems on OS/400 systems 56, 74, 239Document History database component

set up JDBC connection pool 170documentation

additional 13conventions used 12feedback 13

EEDI Module

hardware requirements 40installation location 22

EDIINT Modulehardware requirements 40installation location 22

extended character set encoding support 24

Ffirewall, install on machines that cannot go outside of 70

Hhardware requirements for webMethods products 37Hewlett-Packard SNAplus2 38

IIBM Communications Server for NT 38install

display problems on OS/400 systems 56, 74, 239from an installation image 110from an installation script on a UNIX system 109from an installation script on a Windows system 106on a remote machine 67on a Windows system using a wizard 74on machines that cannot go outside firewall 70specify server to download from 110use a proxy server 81use a proxy server to 70, 108using console mode 107

installation imagecreate 80, 109description of 70extra memory required to create 75, 77, 107extra memory required to install from 66, 67install from 110

installation log file 56, 74, 106installation script

create 79, 108description of 70install from on a UNIX system 109install from on a Windows system 106

Integration Serveraccess .NET environment 24change access permissions for on UNIX and MAC OS X

systems 193cluster support 25configure to write to a database 175dedicate instance to running Monitor 30develop C/C++ services 24hardware requirements 40identify compiler to use with Developer 191identify JRE to use on OS/400 systems 193increase memory on OS/400 systems 193


install in development environment as a Windows application 89, 115, 189

install in production environment as a Windows service 89, 115, 189

installation location 23let portlets running in My webMethods Server use My

webMethods Server users to call services 24license key 89, 115rebuild C/C++ shared libraries 24store keys and certificates securely 24streamline 194support for extended character set encoding 24use non-default JDK 232WmDB package, use for backward compatibility 25

Integration Server Administrator, description of 23Integration Server-webMethods Mainframe Package, installation

location 25international operating environments, support for 49IS Core Audit Log database component

set up JDBC connection pool 170

JJDBC connection pools

change configuration of for Manager server 94, 118change configuration of for Trading Networks 98, 122set up 170specify for Manager server database component during

installation 94, 118specify for Trading Networks database component during

installation 97, 121JDKs, required 38JMS Administrator

installation location 19JREs, required 38

Llanguage packs 50log file

for installation 56, 74, 106for uninstallation 238

Logging Utilityinstallation location 20, 33

MMainframe (webMethods Mainframe)

create and modify host connection pools and transactions 26enable communication with Integration Server and Developer

26hardware requirements 40installation location 25SNA communications server requirements 38

Mainframe Administrator, description of 25Mainframe Package

installation location 25Mainframe Plug-in

installation location 25use to create and modify webMethods Mainframe host

connection pools and transactions 26Manager

hardware requirements 40, 41installation location 26use non-default JDK 232, 233

Manager serverchange JDBC pool configuration 94, 118install in development environment as a Windows application

93, 117install in production environment as a Windows service 93,

117license key 93, 117use non-default JDK 232

Microsoft Host Integration Server 2000 38Modeler

browse services in Servicenet 28give permissions for on UNIX system 197hardware requirements 40use non-default JDK 233

Modeler Repositoryhardware requirements 40

Modeler Repository database componentconfigure 177

Monitorgraphical display utility requirements 198hardware requirements 40installation location 30


I n d e x

My webMethods Serverhardware requirements 40use non-default JDK 233

My webMethods Server database componentdrop using commands 244, 247install using commands 138, 149install using configurator 183

Ooperating systems, supported 38Optimize

hardware requirements 40, 41Oracle URLs 171OS/400 systems

installer display problems 74uninstaller display problems 239

OS/400 systems, installer display problems 56overwrite corrupt installations 103, 124

PPortal

develop portlets 19hardware requirements 40installation location 18manage ADAM users and groups 19manage LDAP users and groups 19monitor clustered Portal servers 19work with Web services clients and portlets 19

Process Audit Log database componentset up JDBC connection pool 170

Process Tracking Store database componentconfigure 175

product dependencies 18program code conventions in this document 12proxy server, use to install 70, 81, 108

RRDBMS

character set and sort order 44page and block size 44supported 44

RDBMS URLsDB2 172Oracle 171SQL Server 171Sybase 171

reinstall corrupt installations 103, 124remote machine, install on 67remote machine, uninstall from 239replace corrupt installations 103, 124Reporting database component

set up JDBC connection pool 170required JREs/JDKs and browsers 38

Sscript, description of 70Servicenet

hardware requirements 40, 43installation location 31register and manage Web services hosted in any Web serivce

container 32register and manage Web services hosted in Glue 32register and manage Web services hosted in Integration

Server 32register and manage Web services hosted in WebLogic 32register Web services hosted in .NET server 32

servlet engines supported by Workflow 39SNA communications servers supported by webMethods

Mainframe 38software requirements for webMethods products 37SQL Server URL 171Staging database component

set up JDBC connection pool 170streamline Integration Server 194support for international operating environments 49supported operating systems 38supported RDBMSs and database drivers 44Sybase URL 171SYS or SYSTEM user account for database install 46


TTrading Networks

change JDBC pool configuration 98, 122enable Manager server to manage Trading Networks Server

33hardware requirements 41, 43store keys and certificates securely 33

Trading Networks Consoleinstallation location 32use non-default JDK 233

Trading Networks Server, installation location 32Trading Networks Web Manager

description of 32troubleshooting information 13typographical conventions in this document 12

Uuninstall

from a UNIX system using a wizard 239from a Windows system using a wizard 238on a remote machine 239using console mode 239

uninstallation log file 238uninstaller, uninstall mode choices 238URLs

DB2 172Oracle 171SQL Server 171Sybase 171

WwebMethods Installer

run as a wizard on a Windows system 74run in console mode 107server, specify 110

webMethods productshardware requirements 37software requirements 37

webMethods Uninstallerrun as a wizard on a UNIX system 239run as a wizard on a Windows system 238run in console mode 239uninstall mode choices 238

Windows application, install Integration Server as 189Windows service, install Integration Server as 189wizard

use to install on a Windows system 74use to uninstall from a UNIX system 239use to uninstall from a Windows system 238

WmInstallLog.txt file 56, 74, 106WmUninstallLog.txt file 238Workflow

does not support use of firewall 39hardware requirements 41, 43servlet engine requirements 39use Apache Tomcat as servlet engine 39use BEA WebLogic as servlet engine 39use with Modeler 33

Workflow clientinstallation location 33use non-default JDK 233

Workflow Configurator 215Workflow database component, install 213Workflow Server

configure to write to the Process Audit Log database 220configure to write workflow models to database 222connect to Broker 219drop database tables 223enable to send email notifications 220install central 100, 123install secondary 101, 123installation location 33provide authentication for 216set up for automatic startup on Solaris, HP-UX, and AIX

systems 213synchronize with Broker 223use Integration Server Tomcat as servlet engine 39


I n d e x
