Web Methods Installation Guide 6 5 and 6 5 1

webMethods
Installation Guide
VERSION 6.5 AND 6.5.1
webMethods, Inc. South Tower 3877 Fairfax Ridge Road Fairfax, VA 22030 USA 703.460.2500 http://www.webmethods.com
webMethodsAccess,webMethodsAdministrator,webMethodsBroker,webMethodsDashboard,webMethodsDeveloper,webMethodsFabric,webMethods Glue,webMethodsInstaller,webMethodsIntegrationServer,webMethodsMainframe,webMethodsManager,webMethodsModeler,webMethodsMonitor, webMethodsOptimize,webMethodsPortal,webMethodsServicenet,webMethodsTradingNetworks,andwebMethodsWorkflowaretrademarksof webMethods,Inc.webMethodsandthewebMethodslogoareregisteredtrademarksofwebMethods,Inc. AcrobatandAdobeareregisteredtrademarks,andReaderisatrademarkofAdobeSystemsIncorporated.Amdocsisaregisteredtrademark,andClarifyCRM isatrademarkofAmdocs.AribaisaregisteredtrademarkofAriba,Inc.BEA,BEAWebLogicServer,Jolt,andTuxedoareregisteredtrademarks,andBEA WebLogicPlatformisatrademarkofBEASystems,Inc.ActionRequestSystem,BMCSoftware,PATROL,andRemedyareregisteredtrademarksofBMC Software,Inc.BroadVisionisaregisteredtrademarkofBroadVision,Inc.ChemeStandardsandCIDXaretrademarksofChemicalIndustryDataExchange. UnicenterisaregisteredtrademarkofComputerAssociatesInternational,Inc.PopChartisaregisteredtrademarkofCORDATechnologies,Inc.Kenanand ArborareregisteredtrademarksofCSGSystems,Inc.DataConnectionandSNAPIXareregisteredtrademarksofDataConnectionCorporation.DataDirect, DataDirectConnect,andSequeLinkareregisteredtrademarksofDataDirectTechnologies.D&BandDUNSareregisteredtrademarksofDun&Bradstreet Corporation.EntrustisaregisteredtrademarkofEntrust,Inc.papiNetisaregisteredtrademarkoftheEuropeanUnionandtheUnitedStates.Financial InformationeXchange,F.I.X,andF.I.XProtocolaretrademarksofFIXProtocolLtd.UCCnetandeBusinessReadyareregisteredtrademarks,and1SYNCand TransoraaretrademarksofGS1US.HewlettPackard,HP,HPUX,OpenView,PARISC,andSNAplus2aretrademarksofHewlettPackardCompany.i2isa registeredtrademarkofi2Technologies,Inc.AIX,AS/400,CICS,DB2,Domino,IBM,Informix,Infoprint,Lotus,LotusNotes,MQSeries,OS/390,OS/400, RACF,RS/6000,SQL/400,S/390,System/390,VTAM,z/OS,andWebSphereareregisteredtrademarks;andCommunicationsSystemforWindowsNT,DB2 UniversalDatabase,IMS,MVS,andSQL/DSaretrademarksofIBMCorporation.InnoDBisatrademarkofInnobaseOy.Itaniumisaregisteredtrademarkof IntelCorporation.JBossisaregisteredtrademark,andJBossGroupisatrademarkofJboss,Inc.LinuxisaregisteredtrademarkofLinusTorvalds.W3Cisa registeredtrademark,andXWindowSystemisatrademarkoftheMassachusettsInstituteofTechnology.MetaSolvisaregisteredtrademarkofMetasolv Software,Inc.ActiveX,Microsoft,Outlook,VisualBasic,Windows,andWindowsNTareregisteredtrademarks;andWindowsServerisatrademarkof MicrosoftCorporation.SixSigmaisaregisteredtrademarkofMotorola,Inc.Firefoxisaregisteredtrademark,andMozillaisatrademarkoftheMozilla Foundation.MySQLisaregisteredtrademarkofMySQLAB.nCipherisatrademarkofnCipherCorporationLtd.TeradataisaregisteredtrademarkofNCR International,Inc.NetscapeisaregisteredtrademarkofNetscapeCommunicationsCorporation.SUSEisaregisteredtrademarkofNovell,Inc.ServletExecis aregisteredtrademark,andNewAtlantaisatrademarkofNewAtlantaCommunications,LLC.CORBAisaregisteredtrademarkofObjectManagement Group,Inc.JDEdwards,OneWorld,Oracle,PeopleSoft,Siebel,andVantiveareregisteredtrademarks,andPeopleSoftPureInternetArchitectureand WorldSoftwarearetrademarksofOracleCorporation.InfranetandPortalaretrademarksofPortalSoftware,Inc.RedHatisaregisteredtrademarkofRed Hat,Inc.PIPandRosettaNetaretrademarksofRosettaNet,anonprofitorganization.SAPandR/3areregisteredtrademarksofSAPAG.SWIFTand SWIFTNetareregisteredtrademarksofSocietyforWorldwideInterbankFinancialTelecommunicationSCRL.SPARCandSPARCStationareregistered trademarksofSPARCInternational,Inc.SSAisaregisteredtrademark,andBaanandSSAGlobalaretrademarksofSSAGlobalTechnologies,Inc.EJB, EnterpriseJavaBeans,Java,JavaServer,JDBC,JSP,J2EE,Solaris,Sun,andSunMicrosystemsareregisteredtrademarks;andJavaNamingandDirectory Interface,SOAPwithAttachmentsAPIforJava,JavaServerPages,andSunSoftaretrademarksofSunMicrosystems,Inc.Sybaseisaregisteredtrademarkof Sybase,Inc.VERITASisaregisteredtrademark,andVERITASClusterServerisatrademarkofSymantecCorporation.UNIXisaregisteredtrademarkofThe OpenGroup.UnicodeisatrademarkofUnicode,Inc.VeriSignisaregisteredtrademarkofVerisign,Inc. Allothermarksarethepropertyoftheirrespectiveowners. Copyright20052006bywebMethods,Inc.Allrightsreserved,includingtherightofreproductioninwholeorinpartinanyform.
Document ID: WEBM-IG-65-20060811
Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Part I.
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1. Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access or Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDI Module and EDIINT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . webMethods Mainframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manager and Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Development Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Production Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Servicenet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trading Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location of Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15 17
18 18 19 19 21 22 22 23 25 26 28 28 29 30 30 31 32 33 34 36
Chapter 2. Software and Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . .

Product Software Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Operating Systems and Required JREs/JDKs and Browsers . . . . . . . . . . . . . . . . . . SNA Communications Server for webMethods Mainframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Servlet Engine and Limitations for Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
38 38 38 39 39 39 41
webMethods Installation Guide Version 6.5 and 6.5.1
Contents
Database Component Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported RDBMSs and Database Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RDBMS Page and Block Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RDBMS Character Set and Sort Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use of SYS or SYSTEM User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44 44 44 44 44 46
Chapter 3. Support for International Operating Environments . . . . . . . . . . . . . . . . . . . . . . 49

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Character Encodings and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 50 50 51
Part II. Simple Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Chapter 4. Simple Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 56 57 58 59 60 61 61 62 62
Part III. Advanced Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Chapter 5. Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Prepare for Installation on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare the Machine on Which to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare to Install the Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare to Install Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare for Installation on a UNIX, Linux, OS/400, or Mac OS X System . . . . . . . . . . . . . . . . . . . . . Prepare for Install on a Remote Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare the Machine on Which to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare to Install webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare to Install the Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare to Install Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log In as as Root or Non-Root User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 66 66 66 67 67 67 68 69 69 69
Use a Proxy Server, Installation Script or Image, Custom Server, or 64-Bit JDK . . . . . . . . . . . . . . . . Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download webMethods Products from Your Own Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install a 64-bit JDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combinations of Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
70 70 70 70 71 71 71
Chapter 6. Advanced Installation Using the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start the Installer on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use Advanced Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create, Install from, or Edit an Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create or Install from an Installation Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use Proxy Server or Your Own Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install a 64-Bit JDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Use the Installer Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete Product Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure webMethods Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Manager, Optimize, or Both . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Manager Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Servicenet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Trading Networks Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overwrite Using the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
74 74 74 79 79 80 81 81 82 83 84 84 85 85 86 87 87 89 90 93 95 97 99 102 102 103
Contents
Chapter 7. Advanced Installation Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install in Console Silent Mode on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install Using Console Mode on a UNIX, Linux, OS/400, or Mac OS X System . . . . . . . . . . . . . . . . . . Start the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specify Release, User Name, and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specify the Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overwrite Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 106 107 107 110 110 111 112 113 124 124 124
Part IV. Database Component Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Chapter 8. Installing the Database Components in Oracle . . . . . . . . . . . . . . . . . . . . . . . . . 129
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 Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Set the Database Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Create the Tablespaces in Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Install the My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Create the Tablespace and Database User and Install the Database Component . . . . . . . . . . . 139 Install 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 . . . . . . . . . . . . . . . . . . . . 143

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, Reporting, Staging, and Trading Networks Database Components . . . . Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set the Database Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create the Database and Database User and Install the Database Component . . . . . . . . . . . . Install the Database Component Using an Existing Database and Database User . . . . . . . . . . Reinstall the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 144 144 144 145 145 145 146 146 147 148 149 150 150 151 152
Chapter 10. Installing the Database Components in DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, Reporting, Staging, and Trading Networks Database Components . . . . Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Reporting and Staging Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set the Database Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set the Database Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 154 154 154 155 155 155 155 156 156 156 157 157 157 157 158 160
Contents
Chapter 11. Installing the Database Components in Sybase . . . . . . . . . . . . . . . . . . . . . . . . 163

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, Reporting, Staging, and Trading Networks Database Components . . . . Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Archive, Process Audit Log, Reporting, and Staging Database Components . . . . . . . . . . Set Up Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Download the Database Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set the Database Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 164 164 164 165 166 166 166 166 167 167
Chapter 12. Identifying Databases for Use by Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

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 Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Link a Function to a Connection Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Integration Server to Write Cross-Reference, IS Core Audit Log, and Process Audit Log Data to a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identify the Database for the Process Tracking Store Database Component . . . . . . . . . . . . . . . . . . . Identify the Database for the Modeler Repository Database Component . . . . . . . . . . . . . . . . . . . . . . 170 171 174 175 175 177
Part V. Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Chapter 13. Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Access, My webMethods Server, or Portal Installation . . . . . . . . . . . . . . . . . . . . . . . . . Configure the Server and Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the Portlet Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the webMethods Broker Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Make Sure the Broker Server is Running and the Default Broker Exists . . . . . . . . . . . . . . . . . . Adjust Per-Process Thread Limit and Set Per-Process and Kernel Limit on HP-UX Systems . . Set Locale on UNIX or Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Full Core Dumps on AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Deployer Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Apply Fixes for Modeler 6.1.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install JCE Unlimited Strength Jurisdiction Policy Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 183 183 183 189 189 189 190 190 190 191 191 191
Complete the Integration Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Direct Integration Server to Compiler to Use for Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Integration Server to Use a 64-Bit JVM on Solaris and HP-UX Systems . . . . . . . . . . Install JCE Unlimited Strength Jurisdiction Policy Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Increase File Descriptors on UNIX, Linux, OS/400, and Mac OS X Systems . . . . . . . . . . . . . . . Change Permissions on UNIX, Linux, OS/400, and Mac OS X Systems . . . . . . . . . . . . . . . . . . Prevent Memory Problems on OS/400 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Streamline Integration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Installation for Manager, Optimize, or Both . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create the Manager/Optimize User and Enable Automatic Start and Shut Down on UNIX or Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Modeler Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Make Sure Modeler Design Package and PRT are Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . Give Users Proper Permissions on Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define Logical Servers and Map to Integration Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Monitor Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up Authentication to Run Monitor Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install the SVG Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Servicenet Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up the Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Registry Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Change the Default Registry Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Servicenet Components to Communicate with My webMethods Server . . . . . . . . . . Complete the Workflow Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up the Workflow Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up Secondary Workflow Servers to Access Encryption Passwords . . . . . . . . . . . . . . . . . . . Set Up Workflow Servers for Automatic Startup on Solaris, HP-UX, AIX, and Linux Systems . . Set Up Workflow Servers for Automatic or Manual Startup on Windows Machines . . . . . . . . . . Enable a Workflow Server on a Red Hat Linux System to Use an SSL-Enabled Broker . . . . . . Configure Workflow Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Workflow to Use SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connect Products to Each Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connect My webMethods Server to Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connect Integration Server to the Default Broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redirect Products to Use a Non-Default JRE or JDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Installation for Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
191 191 192 192 193 193 193 194 196 196 196 196 197 197 198 198 198 199 201 205 210 211 213 213 213 213 213 214 215 224 229 229 231 232 234
Contents
Part VI. Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Chapter 14. Uninstalling Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstall on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uninstall on a UNIX, Linux, OS/400, or Mac OS X System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Deployer Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the webMethods Mainframe Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Modeler Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 238 239 240 240 240 241
Chapter 15. Dropping Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Drop Database Components from Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drop the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, and Trading Networks Database Component . . . . . . . . . . . . . . . . . Drop the Analysis, Archive, Process Tracker, and Servicenet Database Components . . . . . . . Drop the My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 Components . . . . . . . . . . . . . . . . Drop the Manager Server and Process Audit Log Database Components . . . . . . . . . . . . . . . . . Drop the Analysis, Archive, Process Tracker, and Servicenet Database Component . . . . . . . . Drop the My webMethods Server Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drop Database Components from DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drop the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, and Trading Networks Database Components . . . . . . . . . . . . . . . . Drop the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drop the Database Components from Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drop the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, and Trading Networks Database Components . . . . . . . . . . . . . . . . Drop the Archive and Process Audit Log Database Components . . . . . . . . . . . . . . . . . . . . . . . . 244 244 244 244 246 246 246 247 247 248 248 249 250 250 250
Appendix A. Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Appendix B. Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Monitor Service pub.monitor.archive:setOperationParameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
10
Appendix C. Create the Broker Server Configuration Manually . . . . . . . . . . . . . . . . . . . . . 267

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create the Broker Server Data Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create the Data Directory on UNIX or Linux Systems as Non-Root User . . . . . . . . . . . . . . . . . . Create the Data Directory on a UNIX or Linux Systems as Root User . . . . . . . . . . . . . . . . . . . . Create the Data Directory on Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up Broker Monitor on UNIX or Linux Systems (Non-Root User) . . . . . . . . . . . . . . . . . . . . . . . . . Run as Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Run as Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create the Broker Server on Any System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create Separate Storage Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a Combined Storage Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create the Default Broker on Any System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable the Broker Server to Log Events to the UNIX or Linux System Log . . . . . . . . . . . . . . . . . . . . Adjust Per-Process and Kernel Limits on HP-UX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Locale on UNIX or Linux Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Full Core Dumps on AIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 268 268 270 270 270 270 272 272 273 276 279 279 280 280 280
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
11
Contents
12
About This Guide
About This Guide

ThisguideisforuserswhoareinstallingoruninstallingthesewebMethodsproducts: Product webMethodsAccess webMethodsAdministrator Version 6.5.1 6.5
Note: webMethodsAdministratorhasbeendeprecated.Itwillnolongerbeavailable afterthisrelease. webMethodsBroker webMethodsDeployer webMethodsDeveloper webMethodsEDIModuleandwebMethodsEDIINTModule webMethodsIntegrationServer webMethodsMainframe webMethodsManager webMethodsModeler webMethodsMonitor MywebMethodsServer webMethodsOptimize webMethodsPortal webMethodsServicenet webMethodsTradingNetworks webMethodsWorkflow 6.5 6.5 6.5 6.5 6.5 6.5 6.5.1SP1 6.5.1 6.5.1SP1 6.5.1 6.5.1SP1 6.5.1 6.5.1 6.5 6.5.1
IfyoumustperformcertainconfigurationtasksbeforeyoustartawebMethodsproduct, thisguideexplainsthoseconfigurationtasks.ThedocumentationforeachwebMethods productexplainshowtostarttheproductandhowtoperformconfigurationtasksafter theproductisstarted.
11
Important! Informationinthisguidemighthavebeenupdatedsinceyoulastdownloaded it.GotothewebMethodsAdvantageWebsiteathttp://advantage.webmethods.comfor thelatestversionoftheguide. Ifyouwanttoupgradetheseproducts,youmustusetheinstructionsintheappropriate upgradeprocedure.Theinstructionsinthisinstallationguidedonotcoverupgrades,so followingtheinstructionsinthisguideforupgradeswouldhaveunpredictableresults. Forsystemrequirements,JVMconsiderations,andinstructionsoninstallingand uninstallingwebMethodsproductsthatarenotlistedabove,seethedocumentationfor thoseproducts. Note: Typically,toinstallwebMethodsproducts,youdownloadthewebMethodsInstaller andthefilesforeachproductfromthewebMethodsAdvantageWebsite.TheWebsite,at http://advantage.webmethods.com,isasecureWebsiteaccessedthroughtheInternet.If youareunabletodownloadsoftware,webMethodsCustomerOperationscanprovidethe webMethodsproductsyouhavelicensedonaCDorthroughaprivateFTPsite.Contact webMethodsCustomerOperationsatcustops@webmethods.com.
Document Conventions
Convention Bold Italic Description Identifieselementsonascreen. Identifiesvariableinformationthatyoumustsupplyorchangebased onyourspecificsituationorenvironment.Identifiestermsthefirst timetheyaredefinedintext.Alsoidentifiesserviceinputandoutput variables. IdentifiesstoragelocationsforservicesonthewebMethods IntegrationServerusingtheconventionfolder.subfolder:service. Identifiescharactersandvaluesthatyoumusttypeexactlyor messagesthatthesystemdisplaysontheconsole. Identifieskeyboardkeys.Keysthatyoumustpresssimultaneouslyare joinedwiththe+symbol. Directorypathsusethe\directorydelimiterunlessthesubjectis UNIXspecific. Optionalkeywordsorvaluesareenclosedin[].Donottypethe[] symbolsinyourowncode.
Narrow font
Typewriter font
UPPERCASE \ []
12
Additional Information
Additional Information
ThewebMethodsAdvantageWebsiteathttp://advantage.webmethods.comprovidesyou withimportantsourcesofinformationaboutwebMethodsproducts: Troubleshooting Information.webMethodsprovidestroubleshootinginformationfor manywebMethodsproductsinthewebMethodsKnowledgeBase. Documentation Feedback.ToprovidedocumentationfeedbacktowebMethods,gotothe DocumentationFeedbackFormonthewebMethodsBookshelf. Additional Documentation.AllwebMethodsdocumentationisavailableonthe webMethodsBookshelf.
13
14
PART
Requirements
Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Software and Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Support for International Operating Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
15
16
CHAPTER
Planning Your Installation

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
17
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
Overview
ThischapterexplainswheretoinstallwebMethodsproducts.Thechapteralsoexplains howtoinstallwebMethodsdatabasecomponents.Adatabasecomponentisagroupingof databaseobjectsdeployedasoneormoredatabaseSQLscripts.Somedatabase componentsareusedbymorethanoneproduct.Forfulldescriptionsofthedatathatthe productswritetoeachdatabasecomponent,seeAppendix B,DatabaseComponents. SomewebMethodsproductsdependonhavingotherwebMethodsproductsinstalledon thesamemachine.ThetablesinthesectionsbelowlistthoseproductsunderProducts Required on Same Machine as product. MostwebMethodsproductsrequireother webMethodsproducts,databasecomponents,andlowerlevelitemstobeinstalledonone ormoremachinesinthenetworkinordertooperatefully.Thetablesbelowlistthose productsasproduct Requirements for Full Operation. webMethodsproductssometimesrequireadditionallowerlevelitemstocommunicate withotherwebMethodsproducts,andcanuseotherlowerlevelitemstoperformoptional tasks.ThetablesbelowlistthoseitemsunderIf you want to install....Ifnototherwisestated inthetable,installtheitemsonthesamemachineastheproduct. ForhelpdeterminingthebestinstallationofwebMethodsproductsforyourorganization, consultwebMethodsProfessionalServices.
Access or Portal
InstallAccessorPortalonMywebMethodsServer. InstallMywebMethodsServerdatabase component.
Access or Portal My webMethods Server My webMethods Server
Ifyoursystemadministratorisgoingtocreate clusteredAccessorPortalservers,install webMethodsBrokeronamachinetowhichalltheclusteredservershavenetworkaccess, andinstalltheJMSClientAPIoneachmachinethathostsoneoftheclusteredservers. IfyouwanttodevelopportletsforuseinAccessorPortal,installthePortletDeveloper, whichisanEclipseplugin.Forinstructions,seethewebMethodsPortalDesignGuide. Products Required on Same Machine as Access or Portal MywebMethodsServer6.5.1
Access or Portal Requirements for Full Operation Whenclustering,webMethodsBroker6.5SP1, BrokerClientJavaAPI6.5SP1,andJMS Provider6.5SP1 PortletDeveloper6.5 MywebMethodsServerdatabasecomponent
18
Administrator
If you want to... Developportlets ManageADAMusersandgroups ManageLDAPusersandgroups MonitorclusteredPortalservers WorkwithWebservicesclientsand portlets
Install this item... SDK ADAM LDAPBrowser RemotePortalLogViewer TCPTunnelMonitor
Administrator
InstallAdministratorandIntegrationServeronamachineon thesamenetworkastheotherwebMethodsproducts.
Integration Server Administrator
Note: Administratorhasbeendeprecated.Itwillnolongerbeavailableafterthisrelease.
webMethods Broker
webMethods Broker
Broker Administrator JMS Administrator Logging Utility Monitor Monitor interface My webMethods Server Integration Server
InstallwebMethodsBroker onamachineonthesame networkasother webMethodsproducts. InstallIntegrationServer, BrokerAdministrator,and JMSAdministratoron anothermachineonthe network.
Whenyouinstall webMethodsBroker,you actuallyinstallaBroker Serverandadefault My webMethods Broker.TheBrokerServer Server managestheflowof documentsand communicationamongBrokers,Brokerclients,JMSclients,andvariousapplications. BrokersarethesoftwaretowhichBrokerclientsandJMSclientsconnect.
IS Core Audit Log
19
YoucanlogdocumentsforBrokerandJMSclients.Todoso,youmustinstallthe following: InstalltheLoggingUtilityonanIntegrationServerinthesamenetworkastheclients andtheBrokertowhichtheclientsconnectandinstalltheISCoreAuditLogdatabase component.TheLoggingUtilitygetstheclientdocumentsfromtheBrokersand passesthemtoIntegrationServer,whichwritesthedocumentstotheISCoreAudit Logdatabasecomponent. InstallIntegrationServerandtheMonitorruntimeonanothermachineonthe network,installMywebMethodsServerandtheMonitoruserinterfaceonanother machine,andinstalltheMywebMethodsServerdatabasecomponent.TheMonitor runtimereadsfromtheISCoreAuditLogdatabasecomponentandsendsthedatato theMonitoruserinterfacetodisplay. Products Required on Same Machine as webMethods Broker None webMethods Broker Requirements for Full Operation IntegrationServer6.5,BrokerAdministra tor6.5,JMSAdministrator6.5,Logging Utility6.5,Monitorruntime6.5.1 MywebMethodsServer6.5.1,Monitor userinterface6.5.1 ISCoreAuditLog,MywebMethods Serverdatabasecomponents If you want to... Configureorretrieveinformationabout localorremoteBrokersandJMSadminis teredobjects DevelopandruncustomCmessaging applicationsthatinteractwithyour Broker DevelopandruncustomJavamessaging applicationsthatinteractwithyour Broker Install this item... CommandLineTools
BrokerClientCAPI*
BrokerClientJavaAPI*
*Install on the machines on which the custom clients will be developed and run.
20
Deployer
If you want to... DevelopandruncustomJMSmessaging applicationsthatinteractwithyourBro ker Runsamplemessagingapplicationswith yourBrokerusingAPIsfordifferentpro gramminglanguages
Install this item... JMSClientAPI*
Samples*
*Install on the machines on which the custom clients will be developed and run.
Deployer
Deployerisatoolyouusetodeployitemsthatresideon sourcewebMethodsserverstotargetwebMethodsservers. Integration Server Deployer Forexample,youmightwanttodeployitemsyouhave developedonserversinadevelopmentenvironmentto serversinatestorproductionenvironment.Sourceand targetserverscanincludeBrokers,IntegrationServers,ModelerDesignservers (IntegrationServersequippedwiththeModelerDesignPackage),Monitorservers (IntegrationServersequippedwithMonitor),Portalservers,andWorkflowServers. Ifnofirewallseparatesthesourceandtargetenvironments,installDeployerand IntegrationServeronamachinethatcanaccessallsourceandtargetservers.Ifafirewall separatestheenvironments,installDeployerandIntegrationServeronamachineinthe sourceenvironmentthatcanaccessallsourceserversandinthetargetenvironmentona machinethatcanaccessalltargetservers. Products Required on Same Machine as Deployer IntegrationServer6.x
Deployer Requirements for Full Operation Deployercandeployfromandto: BrokerServers6.xthrough6.5 IntegrationServer6.xthrough6.5 Modeler6.0.1through6.2 Portal6.1.5through6.5 TradingNetworksServer6.xthrough 6.5 WorkflowServer6.1.5
21
Developer
IfIntegrationServerandDeveloperaretheonlywebMethods productsyouaregoingtoinstall,youcaninstallthetwoproducts Developer onthesamemachine.Ifyouarealsogoingtoinstallother webMethodsproductssuchasTradingNetworks,install IntegrationServerandDeveloperondifferentmachinesonthesamenetwork. Products Required on Same Machine as Developer None If you want to... DevelopC/C++servicesorapplicationsthat needtointeractwithIntegrationServerusing C/C++ratherthanJava CreateclientswithC/C++codegenerationand rebuildtheIntegrationServersharedlibraries thatsupportC/C++clientsandservicessoyou cancompiletheclientsusingJDK1.4.x Generateservicesfromanexisting.NET assembly BrowseservicesinServicenet PluginforMicrosoft.NET ServicenetClientAPI Developer Requirements for Full Operation IntegrationServer6.1or6.5 Install this item... C/C++SDK
EDI Module and EDIINT Module

InstalltheEDIModule,the EDIINTModule,Integration Server,andTrading NetworksServeronone machine.InstallDeveloper andTradingNetworks Consoleonanothermachine onthesamenetwork.
Trading Networks Console Integration Server EDI Module and EDIINT Module Trading Networks Server
Developer
Products Required on Same Machine as EDI Module IntegrationServer6.5 TradingNetworksServer6.5
EDI Module Requirements for Full Operation Developer6.5 TradingNetworksConsole6.5
22
Integration Server
Products Required on Same Machine as EDIINT Module IntegrationServer6.5 TradingNetworksServer6.5
EDIINT Module Requirements for Full Operation Developer6.5 TradingNetworksConsole6.5 IfsendingEDIdocumentstoTradingNet worksServerforprocessing,EDIModule6.5
Integration Server
IfIntegrationServerandDeveloperaretheonly IS Core Audit Log, webMethodsproductsyouaregoingtoinstall,you Integration Server Document History caninstallthetwoproductsonthesamemachine. IfyouarealsogoingtoinstallotherwebMethods productssuchasTradingNetworks,install IntegrationServerandDeveloperondifferentmachinesonthesamenetwork. IfyouaregoingtocreatepublishsubscribesolutionsthatspanmultipleIntegration Servers,installwebMethodsBrokeronaseparatemachinetoserveasthecommunication linkfortheIntegrationServers. Ifyouareloggingdocuments,usingMonitor,orstoringprocessdataintheProcessAudit Logdatabasecomponent,installtheISCoreAuditLogdatabasecomponent.Ifyour triggersuseDocumentHistoryoptionforexactlyonceprocessing,installtheDocument Historydatabasecomponent. IntegrationServercanalsousethesedatabasecomponents: CrossReferencingdatabasecomponent(informationrequiredtosynchronizeupdates amongvariouswebMethodsproductsandtheirdatabasecomponents;optional becausedataiswrittentoflatfilebydefault) ISCoreAuditLogdatabasecomponent(optionalbecauseerror,guaranteeddelivery, service,andsessiondataiswrittentoflatfilebydefault,butrequiredinsomecases, suchaswhenyouusetheProcessAuditLogdatabasecomponent;seeLocationof DatabaseComponentsonpage 34forcompleteinformation) Repositorydatabasecomponent(recommendedwhenclusteringIntegrationServers)
23
Products Required on Same Machine as Integration Server None
Integration Server Requirements for Full Operation webMethodsBroker6.5 Developer6.5 ISCoreAuditLog,DocumentHistory databasecomponents
If you want to... AllowportletsrunninginsideMyweb MethodsServertouseMywebMethods ServeruserstocallIntegrationServerservices. DevelopC/C++servicesorapplicationsthat needtointeractwithIntegrationServerusing C/C++ratherthanJava CreateclientswithC/C++codegenerationand rebuildtheIntegrationServersharedlibraries thatsupportC/C++clientsandservicessoyou cancompiletheclientsusingaJDK1.2.2or1.3 compiler Useextendedcharactersetencodingsupport forIntegrationServer,adapters,andservices. Accessthe.NETenvironmentfromIntegra tionServer StoreIntegrationServerkeysandcertificates securely
Install this item... CommonAuthorizationPackage
C/C++SDK
ExtendedCharacterSetEncoding Support MicrosoftPackage PKISupport
24
webMethods Mainframe
If you want to... Storeandtrackscheduledjobs,sessioncon text,andjobstrackedbyguaranteeddelivery forclusteredIntegrationServers
Install this item... RepositoryServer Note: Youcanbutdonothaveto installthisitemonanIntegration Serverhostmachine. WmDB
Useforprototyping,design,ortemporary databaseaccess Important! Forenterprise,missioncritical applications,usethewebMethodsJDBC Adapter.Formoreinformationaboutwhento usetheWmDBpackageandwhentousethe JDBCAdapter,seetheWmDBUsersGuide. TheWmDBpackagedoesnotsupportSybase 12.5.3databases.
webMethods Mainframe
InstallwebMethods Mainframe,webMethods webMethods Mainframe IntegrationServer webMethodsMainframe Mainframe Package(Mainframe Plug-in Mainframe Integration Server Developer Package),andIntegration Package Serverononemachine.If webMethodsMainframeis communicatingwithamainframeoveranSNAnetwork,themachinemustbetheone thathoststheSNAcommunicationsserver.InstallthewebMethodsMainframeDeveloper Plugin(MainframePlugin)andDeveloperonanothermachineonthesamenetwork. Products Required on Same Machine as webMethods Mainframe None webMethods Mainframe Requirements for Full Operation Developer6.5,MainframePlugin6.5 IntegrationServer6.5,MainframePackage6.5
25
If you want to... CreateandmodifywebMethods Mainframehostconnectionpoolsand transactions Enablecommunicationbetweenweb MethodsMainframeandIntegration ServerorDeveloper
Install this item... MainframePlugin Note: InstallontheDeveloperhostmachine. MainframePackage Note: InstallontheIntegration Server/webMethodsMainframehostmachine.
Manager and Optimize

Installthecontrollerona machineonthesame Manager/ Optimize interface networkastheother webMethodsproducts.If My webMethods Server youinstallbothManager andOptimize,createa singlecontrollerthatoffers Manager Server Manager server My webMethods fullfunctionalityforboth Server productsbyinstallingthe controllerforeachproductonthesamemachine.Becausethecontrollermakesintensive useofitshostmachine,webMethodsrecommendsthatyoudedicateanentiremachineto runningit.Thecontrollerhostmachinemusthaveaccesstothedatahandlerhostmachine andtoallsatellitehostmachines.
Analysis, Process Audit Log, Process Tracker Manager/Optimize controller/data handler
InstallthedatahandleronamachineonthesamenetworkastheotherwebMethods products.ThedatahandlerisidenticalforManagerandOptimize;ifyouinstallboth products,youcaninstallthedatahandlerfromeitherproduct.Thedatahandlerhost machinemusthaveaccesstothecontrollerhostmachineandtoallsatellitehostmachines. Installsatellitesonenoughmachinestohandletheloadofgatheringdatafromyour environment.Typically,toreducetheburdenonyournetwork,youinstallsatellitesonor neareachmachinethathostsaprocessorapplicationyouwantManagerorOptimizeto monitor.Ifyouwanttomonitorprocessesandapplicationsonaremotehostmachineto whichyouhavenophysicalaccess(forexample,amachineinanothercountry),youcan alsoinstallsatellitesonthecontrollerhostmachine.Thesatellitesareidenticalfor ManagerandOptimize;ifyouinstallbothproducts,youcaninstallthesatellitesfrom eitherproduct. InstalltheManagerandOptimizeuserinterfacesonMywebMethodsServer. InstalltheAnalysis,MywebMethodsServer,ProcessAuditLog,andProcessTracker databasecomponents.
26
Products Required on Same Machine as Manager or Optimize None
Manager or Optimize Requirements for Full Operation MywebMethodsServer6.5.1,Manageror Optimizeuserinterface6.5.1 Analysis,MywebMethodsServer,Process AuditLog,ProcessTrackerdatabasecompo nents
Inaproductionenvironment,webMethodsrecommendsthatyouinstalltheManager serveronadedicatedmachineonwhichnootherwebMethodsproductsarerunning.If necessary,however,theManagerservercanshareamachinewithotherproducts.Install theManagerServerdatabasecomponent. Important! TheManagerserverisbundledwithitsownIntegrationServer.TheIntegration ServerisdevotedentirelytousebytheManagerserver.Donotinstallanyotherpackages ontheIntegrationServer. Products Required on Same Machine as Manager Server None
Manager Server Requirements for Full Operation ManagerServerdatabasecomponent ManagerServercanmanage: BrokerServers5.0.1through6.5 IntegrationServers4.6through6.5 webMethodsMainframe6.5 TradingNetworksServer4.6to6.5 WorkflowServer6.1.5through6.5.1
27
Modeler
Development Environment
YoucaninstallModelerbyitselfona machineandcreateprocessmodels. Workflow client Whenyouwanttosharetheprocess modelswithotherusers,connectthe Modelermachinetoyournetworkand Modeler installtheModelerDesignPackage, theProcessRunTime(PRT),and Integration Server IntegrationServeronanothermachine Developer onthenetwork.Ifyourprocessmodels PRT Modeler Design includestepsthatwillcallIntegration Package ServerflowservicesorWorkflow processes,installDeveloperandtheWorkflowclientonthesamemachineandinthe samewebMethodsinstallationasModeler. TheModelerDesignPackageincludestheModelerRepository,astorageareainwhich Modelersavesprocessmodelinformationandthefilesneededtocreateandgenerate processmodels.Bydefault,theModelerRepositorywritestoaflatfile.Flatfilestorageis sufficientformostinstallations.IfyourModelerusageisextremelyhigh,however,and youhavesufficientresourcestohandletheoverheadofmaintainingadatabase,youcan configuretheModelerRepositorytowritetotheModelerRepositorydatabasecomponent instead. Products Required on Same Machine as Modeler None
Modeler Requirements for Full Operation Developer6.5 IntegrationServer6.5,ModelerDesign Package6.5.1,ProcessRunTime6.5.1 Workflowclient6.5.1
If you want to... BrowseservicesinServicenet
Install this item... ServicenetClientAPI
28
Modeler
Production Environment
InstallthePRTontheIntegration Serverthatwillrunprocesses Monitor interface Integration Server designedinModeler.Install IntegrationServer,theMonitor My webMethods Server Monitor Admin PRT runtime,andAdministratoron istrator amachineonthesamenetwork Process Audit astheotherwebMethods My webMethods Process Log Server Tracking Store products.InstalltheMonitor userinterfaceonMy webMethodsServer.InstalltheMywebMethodsServerandProcessAuditLogdatabase components. IfyouaregoingtodistributeprocessstepsacrossmultipleIntegrationServers,installthe PRToneachofthoseIntegrationServersandinstallwebMethodsBrokeronaseparate machinetoserveasthecommunicationlinkforthePRTs. Ifyouwanttopersistprocessexecutiondata(writtentoRAMbydefault),installthe ProcessTrackingStoredatabasecomponent. Products Required on Same Machine as Modeler None
Modeler Requirements for Full Operation webMethodsBroker6.5 IntegrationServer6.5,Administrator6.5, Monitorruntime6.5.1,ProcessRunTime 6.5.1 MywebMethodsServer6.5.1,Monitoruser interface6.5.1 MywebMethodsServer,ProcessAuditLog databasecomponents
29
Monitor
InstalltheMonitorruntimeonan IntegrationServer.Inaproduction environment,dedicatetheIntegration ServertorunningMonitor.Installthe MonitoruserinterfaceonMy webMethodsServer.InstalltheMy webMethodsServerdatabase component.
Integration Server Monitor interface My webMethods Server Monitor
MonitorreadsfromtheISCoreAudit My webMethods LogandProcessAuditLogdatabase Server componentsandoffersfunctionalityfor archivingdatastoredinthesedatabase components.Ifyouwanttoarchivethisdata,installtheArchive,Reporting,andStaging databasecomponents. Products Required on Same Machine as Monitor IntegrationServer6.5
Monitor Requirements for Full Operation MywebMethodsServer6.5.1,Monitoruser interface6.5.1 ISCoreAuditLog,MywebMethodsServer, ProcessAuditLogdatabasecomponents
My webMethods Server
My webMethods Server My webMethods Server
InstallMywebMethodsServeronamachineto whichallwebMethodsproductshavenetwork accessandthatuserscanaccessusingabrowser. InstalltheMywebMethodsServerdatabase
component. Products Required on Same Machine as My webMethods Server None My webMethods Server Requirements for Full Operation Commonuserinterface6.5.1,userinterfaces forinstalled6.5.xproducts
30
Servicenet
Servicenet
Installthecontroller,including ServicenetAnalytics,onamachineon registry, controller, Servicenet interface thesamenetworkasotherwebMethods and data handler products.Becausethecontrollermakes My webMethods Server intensiveuseofitshostmachine, webMethodsrecommendsthatyou Analysis, Process Audit Log, Process dedicateanentiremachinetorunningit. Tracker, Servicenet Installtheregistryonamachineon My webMethods Server anothermachineonthesamenetwork. Installthedatahandleronthesame machineastheregistryor,toimproveperformanceordistributeresourceconsumption, onanothermachineonthesamenetwork. Note: ThecontrolleranddatahandlerforServicenet6.5.1isidenticaltothecontrollerand datahandlerforOptimize6.5.1SP2.Youcanusethecontrolleranddatahandlerfrom eitherproductforbothproducts.However,touseServicenet,youmustinstallServicenet Analyticsonthecontroller. InstalltheServicenetuserinterfaceonMywebMethodsServer.InstalltheAnalysis,My webMethodsServer,ProcessAuditLog,ProcessTracker,andServicenetdatabase components. IfyouwantServicenettoregisterandmanageWebserviceshostedinaIntegrationServer, BEAWebLogic,Glue,orMicrosoft.NETservercontainer,installthecorrespondingplug inorpublisheronthecontainerhostmachine.IfyouwantServicenettoregisterand manageWebserviceshostedinothertypesofcontainers,installanintermediaryonany machineotherthantheServicenetregistryhostmachinethathasaccesstothecontainer. Anymachinehostingthecontroller,thedatahandler,aplugin,apublisher,oran intermediarymusthaveaccesstotheServicenetregistryhostmachineandviceversa.By default,Servicenetcomponentsareconfiguredtodiscovertheregistryusingasubnet locatorthatsendsoutaUPDping.IfyouwantServicenetcomponentstousethedefault subnetlocators,installtheminthesamenetworksegmentastheregistry,tosupportUPD multicasting.(YoucanconfigureServicenetcomponentslocatedoutsidetheregistrys networksegmenttousestaticlocatorsthatcontaintheregistrysURL.) Products Required on Same Machine as Servicenet None
Servicenet Requirements for Full Operation MywebMethodsServer6.5.2,Servicenetuser interface6.5.1 Analysis,MywebMethodsServer,Process AuditLog,ProcessTracker,Servicenetdata basecomponents
31
If you want to... RegisterandmanageWebservices hostedinaWebLogiccontainer
Install this item... BEAWebLogicPlugin Note: InstallontheWebLogichostmachine.
RegisterandmanageWebservices hostedinGlue
GluePlugin Note: InstallontheGluehostmachine.
RegisterandmanageWebservices hostedinanyWebservicecontainer
Intermediary Note: Installonanymachinethatcanaccess thecontainerhostmachineexcepttheregistry hostmachine.
RegisterWebserviceshostedin Microsoft.NETserver
Microsoft.NETPublisher Note: Installonthe.NETserverhostmachine.
RegisterandmanageWebservices hostedinIntegrationServer
ServicenetPackage Note: InstallontheIntegrationServerhost machine.
Trading Networks
Trading Networks Trading Networks Console Trading Networks Server
Developer
Integration Server
InstallIntegrationServer, TradingNetworksServer,and theTradingNetworksWeb Managerononemachine.Install DeveloperandTrading NetworksConsoleonanother machineonthesamenetwork. InstalltheTradingNetworks
databasecomponent. Products Required on Same Machine as Trading Networks Console Developer6.5 Trading Networks Console Requirements for Full Operation TradingNetworksdatabasecomponent
32
Workflow
Products Required on Same Machine as Trading Networks Server IntegrationServer6.5 If you want to... StoreTradingNetworkskeysand certificatessecurely EnabletheManagerservertomanage TradingNetworksServer
Trading Networks Server Requirements for Full Operation TradingNetworksdatabasecomponent Install this item... PKISupport OMISupport
Workflow
Install Workflow Serverandthe Workflow clienton separate machineson thesame networkasthe other webMethods products. Installthe Workflow database component.
Workflow client Workflow Workflow Server Workflow interface My webMethods Server webMethods Broker My webMethods Server Broker Administrator Integration Server Logging Utility Workflow Servlet Process Audit Log
Ifyouarealso installingModelerandwanttocreateprocessmodelsthatcallWorkflowprocesses,you mustinstalltheWorkflowclientonthesamemachineandinthesamewebMethods installationasModeler.Otherwise,WorkflowServerandtheWorkflowclientcanbutdo nothavetoshareamachinewithanyotherwebMethodsproduct.InstallwebMethods Brokeronitsownmachine,andinstallIntegrationServerandBrokerAdministratoron anothermachine. WorkflowprocessesareBrokerclients.Youcanlogdocumentsthatprocessespublishor subscribetoonBrokers,andyoucanlogprocessauditdatathroughBroker.Todoso, installtheLoggingUtilityontheIntegrationServerequippedwithBrokerAdministrator, installanotherIntegrationServerandtheMonitorruntimeonanothermachineonthe network,andinstallMywebMethodsServerandtheMonitoruserinterfaceonanother machineonthenetwork.InstalltheMywebMethodsServerandProcessAuditLog
33
databasecomponents.TheLoggingUtilityactsasaloggingagentbetweenIntegration ServerandtheBroker;theutilitytakestheclientdatafromtheBrokerandprovidesitto IntegrationServer,andIntegrationServerwritesthedatatotheProcessAuditLog databasecomponent. IfyouwanttomanagetheworklistscreatedbyrunningprocessesfromMywebMethods, installtheWorkflowMyInboxonMywebMethodsServer.Ifyouwanttomanage WorkflowtasksfromMywebMethods,installtheWorkflowTaskListManagement interfaceonMywebMethodsServer.Ineithercase,installtheMywebMethodsServer databasecomponent. Products Required on Same Machine as Workflow Client None Products Required on Same Machine as Workflow Server None
Workflow Client Requirements for Full Operation None
Workflow Server Requirements for Full Operation webMethodsBroker6.5SP1 IntegrationServer6.5,BrokerAdministrator 6.5,LoggingUtility6.5,Monitorruntime 6.5.1,WorkflowServlet6.5.1 MywebMethodsServer6.5.1;Monitor,My Inbox,andTaskListManagementuserinter faces6.5.1 MywebMethodsServer,ProcessAuditLog, Workflowdatabasecomponent
Location of Database Components

ThedatabaseenvironmentforwebMethodsFabric6.5providesforamorescalableand flexiblearchitecturebyallowingdifferentdatabasecomponentstoliveondifferent databasesserversandbydividingdatabaseobjectsacrossdifferentstoragetablespaces. Placeresourceintensivedatabasecomponentsondifferentdatabaseservers.Placeyour databaseserversonhighspeednetworksegmentsandbringthedatabasenetworkas closeaspossibletothewebMethodsproducts. IfyouareinstallingdatabasecomponentsinOracle,installeachdatabasecomponentin itsownschema.Ifyouinstallmultipledatabasecomponentsinthesameschema,youwill notbeabletoreinstallsomedatabasecomponentswithoutdroppingalldatabase componentsinthesameschema. Keeplogfilesseparatefromdatafilestohelpimproveperformanceandreducedisk contention.
34
Location of Database Components
Followtheguidelinesbelowwheninstallingdatabasecomponents.Databasecomponents whoselocationisnotmentionedcanbeinstalledinanylocation. TheISCoreAuditLogcontainserror,guaranteeddelivery,service,andsessiondata, andyoucanlogdocumentstoit.Bydefault,IntegrationServerwritestheerror, guaranteeddelivery,service,andsessiondatatoflatfiles.However,webMethods highlyrecommendsthatyouinstalltheISCoreAuditLogdatabasecomponentand configureIntegrationServertouseit.Doingsoimprovesperformance;whenyouuse flatfiles,onlyoneloggingthreadatatimecanwritedatatoeachfile,whereaswhen youuseadatabase,multipleloggingthreadscanwritedatatothedatabase simultaneously.Also,whenyoustoredatainflatfiles,youmustdeletethefiles manuallywhenyounolongerneedthem,whereaswhenyoustoredatainadatabase, youcanusefacilitiesinyourdatabasetocontrolthelengthoftimethedatais retained.Typically,youwouldonlyuseflatfilestorageifyoulacktheresourcesto purchase,install,andmanageadatabase. YoumustinstalltheISCoreAuditLogdatabasecomponentandconfigureIntegration Servertouseitifanyofthefollowingaretrue: Youwanttologdocuments YouwanttouseMonitor YouareusingtheProcessAuditLogdatabasecomponent;theProcessAuditLog mustalwaysbestoredinadatabase,andyoucannotstoreoneloginadatabase andoneinflatfiles Forbestperformance,webMethodsrecommendsthatyouinstalltheISCoreAudit LogandtheProcessAuditLogdatabasecomponentsonseparatedatabaseservers. YoumustinstalltheAnalysis,ProcessAuditLog,andProcessTrackerdatabase componentsinseparatedatabasesorschemas.Youcanuseoneormoredatabase servers.Youcaninstallthedatabaseserveronthemachinethathoststhe Manager/Optimizecontrollerbut,forbestperformance,installthedatabaseserveron aseparatemachine. YoucaninstalltheProcessTrackingStoreandtheProcessAuditLoginseparate databasesorschemasifyouapplyWmPRT_651_Fix1toyourPRTs(seethe installationinstructionsinthefixsreadme).Ifyoudonotapplythefix,youmust installthedatabasecomponentsinthesamedatabaseorschema. IfyouwanttoarchivedatafromtheISCoreAuditLogdatabasecomponent,the ProcessAuditLogdatabasecomponent,orboth,youmustinstallthesourceand ArchivedatabasecomponentsinthesametypeofRDBMS.IfyouareusingOracle, SQLServer,orSybase,youcaninstalltheArchivedatabasecomponentinadifferent databaseserverthanthesourcedatabasecomponents.IfyouareusingDB2,youmust installtheArchivedatabasecomponentinthesamedatabaseasthesourcedatabase components. TheReportingandStagingdatabasecomponentscanbeinthesamedatabase. However,theservicesthatpopulatetheReportingdatabasecomponentconsume
35
largeamountsofCPU.Forbestperformance,installtheReportingorStaging databasecomponentsonadatabaseserverthatwillnotadverselyaffecttheProcess AuditLogortheProcessTrackingStoredatabasecomponents.
Example Installation
AsimplephysicaldeploymentofallwebMethodsproductsdiscussedinthischapter mightlooklikethis:
Workflow Workflow Server
webMethods Broker
Workflow client
Trading Networks webMethods Mainframe Broker Administrator JMS Administrator Logging Utility Workflow Servlet Monitor Admin PRT istrator IS Core Audit Log, Document History Process Tracking Store Process Audit Log Integration Server Trading Networks Server Mainframe Package EDI/EDIINT Modules
Modeler
Trading Networks Console Mainframe Plug-in
Developer
Workflow interfaces Monitor interface Servicenet interface Manager/Optimize interface Access or Portal My webMethods Server
Servicenet registry
Servicenet
Manager/Optimize/Servicenet controller/data handler
Analysis, Process Tracker
My webMethods Server
Manager server
Manager Server
36
CHAPTER
Software and Hardware Support and Requirements

Product Software Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Product Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Database Component Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
37
CHAPTER 2 Software and Hardware Support and Requirements
Product Software Support and Requirements

Supported Operating Systems and Required JREs/JDKs and Browsers
ForthelistsofsupportedoperatingsystemsandthelistsofrequiredJREs/JDKsand browsers,seewebMethodsSystemRequirements.
SNA Communications Server for webMethods Mainframe

IfwebMethodsMainframeisinstalledonaMicrosoftWindowsNTor2000systemandis communicatingwithamainframeoveranSNAnetwork,webMethodsMainframe requiresoneoftheSNAcommunicationsserverslistedinthetablebelow. SNA Communications Servers MicrosoftHostIntegrationServer2000 IBMCommunicationsServerforWindowsNT Version 5.0 6.xorlater
IfwebMethodsMainframeisinstalledonaSunSolaris8or9systemandis communicatingwithamainframeoveranSNAnetwork,webMethodsMainframe requirestheSNAcommunicationsserverlistedinthetablebelow. SNA Communications Server DataConnectionLimitedSNAPIX Version 7
IfwebMethodsMainframeisinstalledonaHewlettPackardHPUX11isystemandis communicatingwithamainframeoveranSNAnetwork,webMethodsMainframe requirestheSNAcommunicationsserverlistedinthetablebelow. SNA Communications Server HewlettPackardSNAplus2 Version 6.1
38
Product Hardware Support and Requirements
Servlet Engine and Limitations for Workflow

TodisplayHTMLbasedtasks,WorkflowServerrequiresoneoftheservletengineslisted inthetablebelow. Servlet Engine IntegrationServersinternalTomcatservletengine ApacheTomcat BEAWebLogic Version 6.5 5.0 7.xor8.x
TheWorkflowServletcanuseHTTPStocommunicatewithaWebbrowser.Youcan enableHTTPSdirectlyintheservletengine,oryoucanhosttheservletenvironmentina traditionalWebserverfarm.Typically,aWebserverwillsupportHTTPSandredirect URLstoservletinstancesbehindafirewall. WorkflowdoesnotsupporttheuseofafirewallbetweenWorkflowServeranditsclients (thatis,Workflowclienttools,theWorkflowJavaClientAPI,andtheWorkflowServlet). Remotemethodinvocation(RMI)usesatransientTCP/IPportbetween1and65535,so openingthefewportsdefinedbytheWorkflowconfigurationistypicallynotsufficient.

ThissectionfirstliststhestandardhardwarerequirementsforwebMethodsproducts.The sectionthendescribesspecialrequirementsyoumustconsiderwhendeterminingactual hardwarerequirementsforcertainproducts.
Standard Requirements
ThetablebelowliststheminimumhardwarerequirementsforeachwebMethodsproduct. WhenwebMethodsrecommendsalargeramountofharddrivespace,RAM,or virtual/swapmemorythanisrequired,therecommendedamountisshownin parentheses. Important! ThehardwarerequirementsbelowareforwebMethodsproductsonly.Theydo notincluderequirementsforsupportingsoftwaresuchasdatabases.Youmustdetermine theoverallhardwarerequirementsforeachofyourmachinesbasedonyouroverall requirementsofyouroperatingsystemandsoftware.
39
Product Access Administrator webMethodsBroker Deployer Developer EDIModuleandEDIINT Module IntegrationServer webMethodsMainframe Manager Controller Datahandler Satellite Server Modeler ModelerRepository Monitor MywebMethodsServer Optimize Controller Datahandler Satellite Portal Servicenet Controller Datahandler
Hard Drive Space (MB) 50
RAM (MB)
Virtual/Swap (MB)
CPUs
NothingbeyondMywebMethodsServer.
NothingbeyondIntegrationServer. 750(1250)* 20 100(200) 512(2000) 1
NothingbeyondIntegrationServer 128(256) 1
NothingbeyondIntegrationServer 250(350) 10 256(512) 128(256) 1 1
500 500 4 300 40 100
1000(2000) 1000(2000) 100 2000(4000) 64
1000 1000 100 1000
1 1 1 1
100
NothingbeyondIntegrationServer. 300 512(1000) 1
500 500 4 50
1000(2000) 1000(2000) 100
1000 1000 100
1 1 1
NothingbeyondMywebMethodsServer.
500 500
1000(2000) 1000(2000)
1000 1000
1 1
*Moreharddrivespacemightberequiredifyourdocumentsarelarge,orifyourclientsusemanyguaranteed documents. Productionenvironment.Fordisksubsystemrequirementsinaproductionenvironment,andallhardware requirementsinadevelopmentenvironment,seeManagerandOptimizeonpage 41.
40
Product Intermediary Registry TradingNetworks Console Server Workflow Client Server
Hard Drive Space (MB) 82 100
RAM (MB) 256 512
Virtual/Swap (MB)
CPUs 1
30
25 50
128(256) 1
50 210
64or256 1000
1 1
*Moreharddrivespacemightberequiredifyourdocumentsarelarge,orifyourclientsusemanyguaranteed documents.
Productionenvironment.Fordisksubsystemrequirementsinaproductionenvironment,andallhardware requirementsinadevelopmentenvironment,seeManagerandOptimizeonpage 41.
Special Considerations
Thissectiondescribesspecialrequirementsyoumustconsiderwhendeterminingactual hardwarerequirementsfortheindicatedproducts.
webMethods Broker
OnaWindowssystem,youcanonlyinstallwebMethodsBrokeronalocalharddrive.You cannotinstallwebMethodsBrokeronanetworkmounteddrive.
Deployer
Deployerrequiresadditionalharddrivespaceforthedeploymentprojectsyoucreate. Whenallocatingspace,allowforthenumberofprojectstoincreaseovertime.

Additional Hardware Information for the Controller Inaproductionenvironment,thecontrollerhasthesedisksubsystemrequirements: Redundantarrayofindependentdisks(RAID5) UltraWideSCSI 10to15kRPMdrives
41
Thecontrollerrequiresadditionalharddrivespaceforlogfiles.Therecommended amountis100MB.Thecontrollerrequires7MBofharddrivespaceforeachlogfile. Inadevelopmentenvironment,thecontrollerhasthesehardwarerequirements: Hard Drive Space (MB) 100 Virtual/ Swap (MB) 1000
RAM (MB) 1000
CPUs IntelPentiumIII processor400MHz orhigher
Disk Subsystem 10GBavailablefree space
Additional Hardware Information for Satellites Inaproductionenvironment,eachsatelliterequiresadditionalharddrivespaceforlog files.Therecommendedamountis75MB.Thesatelliterequires5MBofharddrivespace foreachlogfile. Additional Hardware Information for the Server EachManagerserversupportsupto5000objects,but,foroptimalperformance, webMethodsrecommendsthateachManagerservermanagenomorethan3500objects. Tomanageanenvironmentwith3500objectsorless,aManagerserverrequiresatleast2 GBofRAM.Tomanageanenvironmentwith10,000objects,youneedatleasttwo Managerservers;webMethodsrecommendsusingthree.EachManagerservershouldrun onaseparatemachinethatsatisfiesthehardwarerequirements. ThedefaultheapspacefortheManagerserveris512MB.Whenmanaginglarger environments,Managerserverneedsgreaterheapspaceandphysicalmemorytofunction optimally.IfyouplanforManagerservertomanageclosetothe5,000objectlimit,dothe following: 1 2 GototheManagerserver_directory/bindirectoryandopentheserver.batorserver.sh file,asappropriate,inatexteditor. IncreasetheManagerserversheapspace.LocatetheJAVA_MAX_MEMparameter andsetitasfollows:
JAVA_MAX_MEM=1536M
3 4
Saveandclosethefile. IncreasethephysicalmemoryavailablefortheManagerserverto4GB.
FormoreinformationaboutscalingManagerserverstomanagealargernumberof objects,seethewebMethodsManagerServerAdministratorsGuide.
42
Servicenet
Inaproductionenvironment,thecontrollerhasthesedisksubsystemrequirements: Redundantarrayofindependentdisks(RAID5) UltraWideSCSI 10to15kRPMdrives Thecontrollerrequiresadditionalharddrivespaceforlogfiles.Therecommended amountis100MB.Thecontrollerrequires7MBofharddrivespaceforeachlogfile. Inadevelopmentenvironment,thecontrollerhasthesehardwarerequirements: Hard Drive Space (MB) 100 Virtual/ Swap (MB) 1000
RAM (MB) 1000
CPUs IntelPentiumIII processor400MHz orhigher
Disk Subsystem 10GBavailablefree space
Trading Networks
TheharddrivespacelistedinStandardRequirementsonpage 39identifiesonlythe amountofspaceTradingNetworksServerrequiresfornormalprocessing.Itdoesnot accountforthespacerequiredtotemporarilysavelargedocumentsduringprocessing.To uselargedocumenthandling,youmustdefineharddiskdrivespaceonwhichTrading NetworksServercantemporarilysavedocuments(ratherthanstoretheminmemory). Theamountofspaceyouneedtotemporarilysavedocumentsvariesbasedonthenumber ofdocumentsyouprocessconcurrentlyandthesizeofthedocumentsyouprocess.For example,ifyourtypicalconcurrentdocumentloadis10,youwouldneedharddiskdrive spacethatis10to15timesthecombinedsizeofthedocumentsbeingprocessed concurrently.Formoreinformation,seethewebMethodsTradingNetworksUsersGuide.
Workflow
TheamountofRAMneededtorunWorkflowclientdependsonwhetheryouarerunning WorkflowDesigner.Ifyouare,Workflowclientneeds256MBofRAM.Ifyouarenot runningWorkflowDesigner,Workflowclientneedsonly64MBofRAM. WorkflowServerrequiresharddrivespaceforlogfiles,forprojectdata,andforversions ofprojectsyougenerateanddeploy.Theamountofspaceyouallocateshouldallowforall oftheseitemstoincreaseovertime.
43
Database Component Requirements

Supported RDBMSs and Database Drivers
ForthelistofsupportedRDBMSs,anddatabasedrivers,seewebMethodsSystem Requirements.
Hardware Recommendations
ProvideasmuchRAMaspossibletodatabaseservers.Makesurethedatabaseserversuse thefastestdiskdrivesavailable;RAIDlevel10isthefastestRAIDlevelthatsupports redundancy.
RDBMS Page and Block Size

UsethepageandblocksizesspecifiedbelowforeachtypeofRDBMS. RDBMS Oracle SQLServer DB2 Sybase Required Page and Block Size 8kpage/blocksize 8kpage/blocksize 8kpagesize 8kpagesize Default 8k 8k 4k 2k
RDBMS Character Set and Sort Order

webMethodsproductsareglobalizedandsupportUnicode.webMethodsstrongly recommendschoosingaUnicodeencodingforyourdatabaseandthemostappropriate sortorderforyourenvironment.Adatabasecharactersetdetermineswhichlanguagesa databasecanrepresent.Databasesortorderdeterminescollationandcomparison behavior. ThesectionsbelowlistthemostappropriateUnicodecharacterencodingandsortorder foreachRDBMSthatwebMethodssupports.Ifyouwanttouseadifferentcharactersetor sortorderthanrecommendedbelow,consultyourdatabaseadministratorandyour RDBMSvendorsdocumentationsoyoucancarefullychooseadatabasecharactersetthat supportsthelanguagesyourdataisin.
Oracle
webMethodsOracledatabaseschemasusecharacterdatatypes.Forcharacterdatatypes, OraclesupportstheUTF8andAL32UTF8Unicodeencodings.WhileUTF8isCESU8 compliantandsupportstheUnicode3.0UTF8Universalcharacterset,AL32UTF8 conformstotheUnicode3.1orhigherUTF8Universalcharacterset.Fornchardatatypes,
44
OraclesupportstheAL32UTF8andAL16UTF16Unicodeencodings.Thesupported UnicodeversionforAL32UTF8dependsontheOracledatabaseversion.webMethods Oracledatabaseschemasdonothavelinguisticindexes.webMethodsrecommendsthe followingcharactersetsandsortorder: For... Characterset Ncharcharacterset Sortorder webMethods recommends... AL32UTF8 AL16UTF16 Binary
Youcancheckdatabaseconfigurationandsessionsettingsbyviewingthe SYS.NLS_DATABASE_PARAMETERSorV$NLS_PARAMETERSparameter.
SQL Server
webMethodsSQLServerdatabaseschemasusenchardatatypes.SQLServerprovides supportforUTF16throughitsnchardatatypes.Sincenchardatatypesarealwaysin UTF16,youdonothavetoperformanyspecialdatabaseconfigurationandcanchoose themostappropriatecodepageforyourenvironmentasadatabasecharacterset. webMethodsrecommendsthesecharactersetsandsortorder: For... Characterset Ncharcharacterset Sortorder webMethods recommends... Theappropriateencodingforthelanguagesyourdataisin. UTF16 Anycaseinsensitivecollationtype. Important! Ifyoudonotchooseacaseinsensitivesortorder, youwillnotbeabletoinstallsomedatabasecomponentsin SQLServer.
Youcancheckdatabaseconfigurationusingthesp_helpdbdatabasestoredprocedure.
Sybase
webMethodsSybasedatabaseschemasusecharacterdatatypes.SybaseprovidesUTF8 supportforcharacterdatatypesandUTF16supportforUnichardatatypes.webMethods recommendsthesecharactersetsandsortorder: For... Characterset UnicharCharacterSet Sortorder webMethods recommends... UTF8 UTF16 bin_utf8forUTF8char,utf8binforunichar
45
Youcancheckdatabaseconfigurationbyusingthesp_helpsortstoredprocedure.
DB2 UDB
webMethodsDB2UDBdatabaseschemasusecharacterdatatypes.DB2UDBsupports UTF8forcharacterdatatypesandUTF16forgraphicdatatypes.webMethods recommendsthesecharactersetsandsortorder: For... Characterset GraphicCharacterSet Sortorder webMethods recommends... CCSID1208(UTF8) UTF16 IDENTITY_16BIT Note: Thissortorderensuresthesamesortingresultfor bothcharacterandgraphicdatatypes.
YoucancheckdatabaseconfigurationbyusingtheGETDATABASECONFIGURATION command.
Use of SYS or SYSTEM User Account

ToinstallsomewebMethodsdatabasecomponentsinOracle,youmustusetheSYSor SYSTEMuseraccount.However,webMethodsproductsdonotconnecttoOracleusing thataccount;theyusethedatabaseusersyoucreateforthedatabasecomponents. Somedatabasecomponentsareinstalledwithadvanceddatabaseoperationssuchasdata purgeanddataarchive.Theseoperationswerebuilttobehighlyscalable,andare thereforedependentonadvancedOraclecapabilities.Forexample,thedbms_jobpackage isusedastheschedulingmechanismforoperations,andthedbms_alertpackageisused asthealertingmechanismforoperations.SincepermissiontousetheseadvancedOracle capabilitiescanonlybegrantedbytheSYSDBArole,theSYSpasswordisrequiredto installthosedatabasecomponents. Note: ThewebMethodsproductsthatusethesedatabasecomponentscanfunctionwithout theseoperations.Theoperationsaremeantsimplytoassistwithsuchtasksasdata management. Thedatabaseusersyoucreaterequirethepermissionsidentifiedinthe ora_cmn_c_ddl_user.sqlfileinthewebMethods_directory\common\db\ scripts\oracle\code\common\createdirectory.Ofthosepersmissions,theSYS permissionsusedtorunoperationsare:
GRANT EXECUTE ON SYS.DBMS_ALERT TO "USER"; GRANT EXECUTE ON SYS.DBMS_JOB TO "USER";
46
TherighttoexecuteDBMS_JOBdoesnotallowausertotouchanyjobsexcepttheirown. Jobsarecreatedinthecontextoftheuser,notasSYSorSYSTEM.
47
48
CHAPTER
Support for International Operating Environments

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Character Encodings and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
49
CHAPTER 3 Support for International Operating Environments
Overview
webMethodsproductsaredesignedforuseanywhereintheworldandenableyouto exchangedatawithsystemsanduserswhospeaklanguagesotherthanyourown.For specificinformationonthetesting,configuration,capabilities,andlimitationsofany webMethodsproduct,seetheproductsreadme.
Character Encodings and Configuration

webMethodsproductsusetheUniversalCharacterSet(ISO/IEC106462,orUnicode)as thecharactersetforallinternaloperations.Unicodecurrentlyencodesapproximately 95,000ofthecharactersusedtowritetheworldslanguages.Atminimum,theproducts supporttherequirementsofUnicode3.0.webMethodsHTMLcontent,including administrationtools,usestheUnicodeUTF8encoding.
Language Packs
ThewebMethodsInstalleralwaysinstallstheU.S.Englishfilesnecessarytorun webMethodsproducts.However,formanyproducts,youcanalsoinstalllanguagepacks thatprovidetranslateduserinterfaces,messages,help,anddocumentation.Foralistof languagepacksthatareavailableforeachwebMethodsproduct,seewebMethodsSystem Requirements. Installlanguagepacksinthesetypesofsituations: Youroperatingsystemisconfiguredtorunusingalanguage(locale)otherthanU.S. Englishandyouwanttorunyourtools(forexample,DeveloperorModeler)inthe languageyouroperatingsystemisusing. Youhaveusers,customers,ortradingpartnerswhodonotspeakU.S.Englishand youwantyourservers(forexample,IntegrationServer,webMethodsBroker,Trading NetworksServer,orWorkflowServer)tosupportthosepeopleinthelanguagestheir operatingsystemsareusing.Youdonothavetochangethesystemsettingsorlocale foryourservers;theclientsendsitslanguageandlocalepreferencetotheserver,and theserverloadsthemessagesintheappropriatelanguagefortheclient. YouarewritingprogramsusingaCorJavaAPIandyouwanttoprovidelocalized messagesforusersinotherlanguages. Mostproductssupportmultiplelanguages.ProductsarealwaysinstalledwithU.S. Englishmessagesandresources.Youcaninstallasmanylanguagepacksasyouwantfor anyproduct.Forproductsthatsupportmultiplelanguages,yourclientsetup(browser languagepreference,thedefaultlocaleinwhichtheproductisstarted,orthelocale selectedinyouruserprofile)willdeterminewhichlanguageyousee.Forproductsthat supportonlyasinglelanguageatatime,thelocaleandconfigurationofyouroperating environmentwilldeterminewhichlanguagepackisdisplayed.Ifyouoperateaproduct
50
Browsers
inalocaleforwhichlanguagepacksarenotavailableorinstalled,youwillseeU.S. English.
Browsers
Forbrowsers,theHTMLinterfacesforwebMethodsproductsdetectthelanguagesetting foryourbrowserandtrytosupplymessagesanddatainthatlanguage.Whenyouinstall aproductthatisorincludesanHTMLinterface,youcanalsoinstalldifferentlanguage materialsfortheinterfaceintheformofwebMethodslanguagepacks. webMethodsHTMLcontent,includingadministrationtools,usestheUnicodeUTF8 encoding.Somebrowsers,suchasolder4.XversionbrowsersdisplayingAsianlanguages, mightrequireyoutoconfigurefontstosupportthedisplayofnonEnglishdataor informationcorrectly.Inaddition,ifyouhaveinstalledwebMethodslanguagepackson yourwebMethodsproducts,youcanindicatewhichoftheinstalledlanguagestodisplay inyourbrowser.ForInternetExplorer,clickTools Internet Options,thenclickLanguages andaddthelanguageyouwanttousetothetopofthelist.ForFirefox,click Tools Options General,thenclickLanguagesandaddthelanguageyouwanttousetothe topofthelist. YourJavaruntimeenvironmentmightalsorequiremodificationtodisplaynonASCII data.IfyouseehollowboxesorblacksquareswhereyouwouldexpecttoseenonASCII characters,youmightneedtomodifyyourJREsfont.propertiesfiletoprovidean appropriatefontfordisplayingthesecharacters.Forexample,youmightinstallafull Unicodefont,suchasArialUnicodeMSorCode2000,oryoucaninstallafontfora particularlanguage.Forinformationonmodifyingyourfont.propertiesfile,goto http://java.sun.com/j2se/1.4.2/docs/guide/intl/fontprop.html.
51
CHAPTER 3 Support for International Operating Environments
52
PART
II
Simple Installation
Simple Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
53
54
CHAPTER
Simple Installation
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
55
CHAPTER 4 Simple Installation
Overview
ThischapterexplainshowtoinstalllocallyusingthewebMethodsInstallerwizardonany supportedsysteminaU.S.Englishlocale.Tosupportthewizard,UNIXandLinux systemsmusthaveanXWindowsenvironment. Note: WhenyourunthewebMethodsInstalleronanOS/400system,theinstaller experiencesdisplayproblems.Whilethesedisplayproblemswillnotadverselyaffectthe installationprocess,webMethodsstronglyrecommendsthatyouminimizetheproblems byrunningtheinstallerfromanOS/400clientforWindowsratherthanfromatelnet client. Iferrorsorwarningsoccurduringtheinstallation,theinstallerwritestheerrorsand warningstoafilenamedWmInstallLog.txtandstoresthefileinthemaininstallation directory(bydefault,webMethods6). Ifyouwanttoinstallusinganyotheroptionsthanthosecoveredinthischapter,orifyou needcompleteinformationonanytopicmentionedhere,seeAdvancedInstallation UsingtheWizardonpage 73orAdvancedInstallationUsingConsoleModeon page 105.
Before You Begin

1 Prepareyourmachineasfollows: a Makesurethemachinehasabout50MBofavailablediskspaceinitssystemtemp directory(Windows)ortemporarydirectory(UNIX,Linux,OS/400,orMacOSX) andabout80MBofavailablevirtualmemory. IfyouareinstallingonUNIX,Linux,OS/400,orMacOSX,installaJREorJDK 1.4.2. IfyouareinstallingonanOS/400system,youalsoneedaJREorJDK1.4.2torun webMethodsproducts.YoucaninstallthesameJREorJDKtorunthe webMethodsInstallerandtheproducts.Theinstallerwillautomaticallyconfigure theproductsyouinstalltousetheJREorJDKyouusetoruntheinstaller. c DownloadthewebMethodsInstaller.Todoso,gotothewebMethodsAdvantage Websiteathttp://advantage.webmethods.comandlogin.ClickProduct Downloads, thendownloadtheinstallerforWindowsorUNIX,asappropriate. Ifthemachineisrunningantivirussoftware,thesoftwarewillscanallthefiles theinstallerdownloads.Thisactivitycantakealongtime.Ifyoudonotwantthe softwaretoscanthefiles,shutdowntheantivirussoftware. ShutdownallwebMethodsproducts.
e 2
IfyouaregoingtoinstalltheManagerserverorTradingNetworksServer,askyour databaseadministratortosetupadatabaseuser,password,andpermissionsforeach
56
Start the Installer
productsdatabasecomponent.Eachdatabaseusermustbeabletoselect,insert, update,anddeleterowsfromthetablesinitsdatabasecomponent.
Start the Installer

1 IfyouareinstallingonaWindowssystem,youmusthaveWindowssystem administratorprivileges. IfyouareinstallingonaUNIX,Linux,OS/400,orMacOSXsystem,loginasthenon rootuserunlessyouaregoingtoinstallwebMethodsBroker.Ifyouaregoingto installwebMethodsBroker,loginastherootusersoyoucanhavetheinstaller automaticallycreatetheBrokerServerconfiguration. 2 GotothedirectorythatcontainsthewebMethodsInstallerandstarttheinstalleras follows: System Windows Other Action DoubleclickthewebMethodsInstaller651.exefile Runthecommandjava -jar webMethodsInstaller651.jar
TheinstallertakesseveralsecondstounzipandlaunchitsJVM,thendisplaysthe welcomepanel.
ClickNext.
57
Specify Release, User Name, and Password
ProvidetherequestedinformationandthenclickNext.
58
Specify the Installation Directory
Windows only
ProvidetherequestedinformationandthenclickNext. Important! DonotinstallwebMethodsBrokerinthesamedirectoryasaprewebMethods6 versionofwebMethodsBrokerorinthesamedirectoryasanyotherwebMethodsBroker product. IfyouareinstallingWorkflowandaregoingtouseIntegrationServersTomcatpackageas yourWorkflowservletengine,youcannotinstallIntegrationServerintoadirectory whosepathcontainsspacesbecauseofaproblemrelatingto1.4.xJDKs.Forexample,you cannotinstallIntegrationServerinthedirectoryProgramFiles\webMethods6. Intherootdirectoryyouspecify,theinstallerwillautomaticallyinstalleachproductina subdirectorynamedaftertheproduct.
59
Select Products to Install
ChoosethewebMethodsproductstoinstall.Theinstallerautomaticallyselectsthe minimumrecommendedsetofitemsforeachproduct;however,youmightneedtoselect additionalitemsthatarelistedunderotherproductstoinstallallfunctionalityyouneed (seeChapter 1,PlanningYourInstallation).Thetablebelowindicatesthelocationof certainitemsintheinstallerproducttree. This item... BrokerAdministrator,JMSAdministrator,LoggingUtility, MainframePackage,ModelerDesignPackage,Process Runtime,andWorkflowServlet Productuserinterfaces(forexample,Monitoruserinterface) ExtendedCharacterSetEncodingSupportandServicenet ClientAPI JMSProvider6.5SP1andBrokerClientJavaAPI6.5SP1 MainframePlugin Listed under... IntegrationServer
MywebMethods UserInterfaces CommonFiles BrokerandJMS Developer
ClickNext.Readthelicenseagreement.Ifyouaccepttheterms,selectthecheckboxand clickNext.Iflanguagepacksareavailableforproductsyouareinstallingorhavealready installed,theinstallerdisplaysthelanguagepackspanel;clickNext.
60
Configure Products
Ifyouareinstallinganyoftheproductslistedbelow,theinstallerdisplayspanelsthat requestconfigurationinformation.Ifyouarenotinstallinganyoftheseproducts,goto ReviewandInstallonpage 62. webMethodsBroker IntegrationServer ManagerorOptimize Managerserver Servicenet TradingNetworksServer Workflow
Configure Products
Afteryoucompleteeachconfigurationpanel,clickNext.
webMethods Broker
provided by webMethods
Providethelicensekey,selectthecheckbox,andthenclickNext.
61
Forinstructionsoncompletingthepanelsfortheotherproductslistedabove,goto ConfigureProductsonpage 87.IfyouareinstallingWorkflow,ignoretheinstructions forinstallingasecondaryWorkflowServer.
Review and Install
Reviewthelistofproductsanditemsyouhaveselectedforinstall.Ifthelistiscorrect, clickNext.Ifthelistisnotcorrect,clickBackuntilyoureturntotheinstallerproducttree andcorrectthechoices. Theinstallerinstallstheproductsandrelateditems,thendisplaystheInstallation Complete panel.ClickClose.
Complete the Installation

Ifyoushutdownyourantivirussoftwarebeforestartingtheinstaller,restartthe software. GotoChapter 13,CompletingtheInstallation.
62
PART
III
Advanced Installation
Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Advanced Installation Using the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Advanced Installation Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
63
64
CHAPTER
Preparing for Installation

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
65
CHAPTER 5 Preparing for Installation
Prepare for Installation on a Windows System

Prepare the Machine on Which to Install
1 Makesurethemachinehasenoughdiskspaceandvirtualmemorytorunthe webMethodsinstaller;thatis,about50MBofavailablediskspaceinthesystemtemp directoryandabout80MBofavailablevirtualmemory.Ifyouaregoingtoinstallfrom animage,makesurethemachinehasenoughadditionalavailablediskspaceto accommodatetheimage.Forexample,iftheimageis200MB,themachinemusthave atleast250MBofavailablediskspaceinitssystemtempdirectory. DownloadthewebMethodsInstaller.Todoso,gotothewebMethodsAdvantageWeb siteathttp://advantage.webmethods.comandlogin.ClickProduct Downloads,then downloadtheinstallerforWindows. Note: Ifyoucannotdownloadsoftware,webMethodsCustomerOperationscanpro videthewebMethodsproductsyouhavelicensedonaCDorthroughaprivateFTP site.ContactwebMethodsCustomerOperationsatcustops@webmethods.com. 3 Ifthemachineisrunningantivirussoftware,thesoftwarewillscanallthefilesthe installerdownloads.Thisactivitycantakealongtime.Ifyoudonotwantthe softwaretoscanthefiles,shutdowntheantivirussoftware. ShutdownallwebMethodsproducts.
Prepare to Install the Manager Server

IfyouaregoingtoinstalltheManagerserver,askyourdatabaseadministratortosetupa databaseuser,password,andpermissionsfortheManagerserverdatabasecomponent. Thedatabaseusermustbeabletoselect,insert,update,anddeleterowsfromthetablesin thedatabasecomponent.
Prepare to Install Trading Networks Server

IfyouaregoingtoinstallTradingNetworksServer,askyourdatabaseadministratortoset upadatabaseuser,password,andpermissionsfortheTradingNetworksdatabase component.Thedatabaseusermustbeabletoselect,insert,update,anddeleterowsfrom thetablesinthedatabasecomponent.
66
Prepare for Installation on a UNIX, Linux, OS/400, or Mac OS X System

Prepare for Install on a Remote Machine
IfyouaregoingtoinstallwebMethodsproductsonaremotemachineandyouwantto installusingthewebMethodsinstallerwizardorusinganinstallationscriptthatusesthe wizard,followthesesteps: 1 Enablethedisplayofthelocalmachineusingthecommandshownbelow,where remote_hostistheremotemachineonwhichyouaregoingtoinstall:
xhost +remote_host
2 3
Logontotheremotemachine. SettheDISPLAYvariableontheremotemachinetopointtothelocalmachine.For example,ifyouareusingabashshellandareinstallingfromalocalmachinenamed installerandwanttosettheDISPLAYtothedefaultdevice,enter:

export DISPLAY=installer:0.0
Prepare the Machine on Which to Install

Preparethemachineonwhichyouaregoingtoinstallasfollows: 1 InstallJREorJDK1.4.2. IfyouareinstallingonanOS/400system,youalsoneedaJREorJDK1.4.2torun webMethodsproducts.YoucaninstallthesameJREorJDKtorunthewebMethods Installerandtheproducts.Theinstallerwillautomaticallyconfiguretheproductsyou installtousetheJREorJDKyouusetoruntheinstaller. 2 Makesurethemachinehasenoughdiskspaceandvirtualmemorytorunthe installer;thatis,about50MBofavailablediskspaceinthetemporarydirectoryand about80MBofavailablevirtualmemory.Ifyouaregoingtoinstallfromanimage, makesurethemachinehasenoughadditionalavailablediskspacetoaccommodate theimage.Forexample,iftheimageis200MB,themachinemusthaveatleast250MB ofavailablediskspaceinitstemporarydirectory. DownloadthewebMethodsInstaller.Todoso,gotothewebMethodsAdvantageWeb siteathttp://advantage.webmethods.comandlogin.ClickProduct Downloads,then downloadtheinstallerforUNIX. Note: Ifyoucannotdownloadsoftware,webMethodsCustomerOperationscan providethewebMethodsproductsyouhavelicensedonaCDorthroughaprivate FTPsite.ContactwebMethodsCustomerOperationsatcustops@webmethods.com.
67
Ifthemachineisrunningantivirussoftware,thesoftwarewillscanallthefilesthe installerdownloads.Thisactivitycantakealongtime.Ifyoudonotwantthe softwaretoscanthefiles,shutdowntheantivirussoftware. ShutdownallwebMethodsproducts.
Prepare to Install webMethods Broker

Install on Solaris, HPUX, or AIX
TheBrokerServeryoucaninstallonaSolaris,HPUX,orAIXoperatingsystemisa64bit binaryapplication.IfyouaregoingtoinstallBrokerServeronanyoftheseoperating systems,youmustconfiguretheoperatingsystemkerneltorunin64bitmode. webMethodsdoesnotsupportthe64bitBrokerServeronanoperatingsystemkernel configuredtorunin32bitmode.
NFS-Mounted Partition
IfyouaregoingtoconfigureBrokerServertocreatedatafilesonanNFSmounted partition,mountthepartitionusingthecommandbelow.Theoptionsonthecommand helpprotectdataintegrity.
mount -o hard,nointr,proto=tcp host:/path /mount_point
Forexample,ifthepartitionyouwanttomountisonamachinenamednetappca,thedata directoryonthepartitioniswmbroker_data,andyouwanttomountthepartitiononthe localfilesystemat/var/opt/wmbroker_data.Thecommandwouldbeasfollows:

mount -o hard,nointr,proto=tcp netappca:/wmbroker_data /var/opt/wmbroker_data
Option
hard
Description Bydefault,iftheNFSserverdoesnotrespondtorequestsfromthe BrokerServer,theBrokerServertriesafewtimesandthenfails.The hardoptionforcestheBrokerServertokeepretryinguntiltheNFS serverresponds.TheBrokerServerhangsduringthisperiod. PreventsusersfromkillingtheBrokerServerwhileitishungwaiting fortheNFSservertorespond. Bydefault,theNFSmountedpartitionusestheuserdatagramproto col(UDP)protocoltocommunicatewiththeBrokerServer.The proto=tcpoptionforcesthepartitiontousetransmissioncontrolpro tocol(TCP)instead.TCPismorereliablethanUDP.
nointr
proto=tcp
Forinformationonotherwaystoprotectdataintegrity,seeyourNFSserver documentation.
68
Prepare to Install the Manager Server

IfyouaregoingtoinstalltheManagerserver,askyourdatabaseadministratortosetupa databaseuser,password,andpermissionsfortheManagerserverdatabasecomponent. Thedatabaseusermustbeabletoselect,insert,update,anddeleterowsfromthetablesin thedatabasecomponent.
Prepare to Install Trading Networks Server

Askyourdatabaseadministratortosetupadatabaseuser,password,andpermissionsfor theTradingNetworksdatabasecomponent.Thedatabaseusermustbeabletoselect, insert,update,anddeleterowsfromthetablesinthedatabasecomponent.
Log In as as Root or Non-Root User

Loginasastherootuserorasanonrootuser. IfyouaregoingtoinstallwebMethodsBroker,youcanusethewebMethodsInstallerto dothefollowingautomaticallyifyouinstallastherootuser: InstallBrokerMonitorasadaemonthatstartsandshutsdownautomatically(and startsandshutsdownyourBrokerServerautomatically)whenyoursystemstartsand shutsdown. CreatetheBrokerServer,itsdatadirectory,andadefaultBroker. Createseparatestoragesessionsforconfiguration(metadata)andruntimedatafor theBrokerServerandplacethesessionsinarootdirectory(bydefault, /opt/webMethods6). CreateentriesintheUNIXorLinuxsystemlogconfigurationfilethatenablethe BrokerServertologBrokerServereventstothesystemlog. However,theBrokerMonitorandBrokerServerwillrunastherootuser. IfyouinstallwebMethodsBrokerasanonrootuser,youmustperformseveralmanual tasksafterinstallation,asfollows: SetupBrokerMonitortorunasadaemonorasanapplicationthatyoustartandshut downmanually. CreatetheBrokerServeranditsdatadirectory,thedefaultBroker,storagesessions, andsystemlogentries. Youwillbeabletospecifyadifferentstoragesizethanisofferedbytheinstallerandto createseparateoracombinedstoragesessionforconfigurationandruntimedata.Ifyou wanttoinstallasanonrootuser,createauseridthatcanbeusedbyanyonewhowill
69
performwebMethodsBrokerconfigurationtasks(suchascreatingBrokers)andlogin underthatuserid. Note: Forsecurityreasons,webMethodsrecommendsinstallingasanonrootuser.
Use a Proxy Server, Installation Script or Image, Custom Server, or 64-Bit JDK
ThewebMethodsInstalleroffersadvancedoptionsyoucanusetoinstall.Theoptionsare describedbelow.
Proxy Server
IfyourcompanyconnectstotheInternetthroughanHTTPorSocksproxyserver,you mustusethatproxyservertoinstall.Yournetworkadministratorcanprovideinformation onyourcompanysproxyservers.
Installation Script
Ifyouneedtocreateidenticalinstallationsonmultiplemachines,youcancreateascriptof theinstallationononemachine,thenrunthescripttocreatethesameinstallationoneach oftheothermachines. Tocreateascript,youselectthewebMethodsproductstoinstallandspecifyall installationoptions(forexample,installationdirectory).Youcanchoosetoactuallycreate thedesiredinstallationonthecurrentmachine,oryoucancreatethescriptwithout creatingtheinstallation. Whenyourunthescript,itautomaticallydownloadsandinstallsthewebMethods productsyouselectedandusestheinstallationoptionsyouspecified. Ifyoulaterfindthatascriptrequiresachange,youcaneditthescript.Youcanalsocreate ascriptbyeditinganexistingscriptandsavingitunderanewname.
Installation Image
Ifyouneedtocreateinstallationsonmachinesthatcannotgooutsideyourcorporate firewalltothewebMethodsAdvantageWebsite,youcaninstallfromaninstallation image.Fromanimage,youcancreateasmanydifferentinstallationsasyouneed. Tocreateanimage,youchooseallwebMethodsproductsyouwanttoinstallonvarious machines.Theinstallerdownloadstheproductsintotheimage.Youdonotspecifyany installationoptions(forexample,installationdirectory).
70
Use a Proxy Server, Installation Script or Image, Custom Server, or 64-Bit JDK
Whenyouinstallfromtheimageonaparticularmachine,youchoosetheproductsto installfromthosethatweredownloadedintotheimage,andyouspecifytheinstallation optionsyouwanttouseforthatmachine.
Download webMethods Products from Your Own Server

YoucancreateyourownserverfromwhichtodownloadwebMethodsproducts.Youcan thenchoosetousethatserverwhenyouruntheinstaller.
Install a 64-bit JDK

WhenyouinstallawebMethodsproductonanysupportedsystemotherthanAS/400,the installerinstallsa32bitJDK1.4.2thatisappropriateforthatsystem.Theproductsuse thisJDKbydefaultinmostcases.Ifyouareinstallingona64bitSolarisSPARC,HPUX, orAIXoperatingsystem,youcanchoosetohavetheinstallerinstalla64bitJDK1.4.2 instead.
Combinations of Advanced Options

Youcanusetheadvancedoptionsincombination,asfollows: Useaproxyserverandcreateoreditascript Useaproxyserverandcreateoreditanimage Createascriptofinstallingfromanimage Useaproxyserverandcreateoreditascriptofinstallingfromanimage Youcanuseyourownserverandinstalla64bitJDKwithanyotheroptionor combinationofoptions.
71
72
CHAPTER
Advanced Installation 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 Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Overwrite Using the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
73
CHAPTER 6 Advanced Installation Using the Wizard
Overview
ThischapterexplainshowtodothefollowingonanysystemusingthewebMethods Installerwizard: InstallfromthewebMethodsinstaller Createaninstallationscriptorimage Installfromaninstallationscriptorimage Youcanusethewizardtoinstalllocallyorremotely.Ifyouaregoingtoinstallonaremote Windowssystemusingthewizardorusinganinstallationscriptthatusesthewizard,you mustruntheinstallerusingremoteaccesssoftwaresuchaspcAnywhere. Tosupportthewizard,UNIXandLinuxsystemsmusthaveanXWindowsenvironment. Note: WhenyourunthewebMethodsInstalleronanOS/400system,theinstallerexperi encesdisplayproblems.Whilethesedisplayproblemswillnotadverselyaffecttheinstal lationprocess,webMethodsstronglyrecommendsthatyouminimizetheproblemsby runningtheinstallerfromanOS/400clientforWindowsratherthanfromatelnetclient. Iferrorsorwarningsoccurduringtheinstallation,theinstallerwritestheerrorsand warningstoafilenamedWmInstallLog.txtandstoresthefileinthemaininstallation directory(bydefault,webMethods6).
Start the Installer

Start the Installer on a Windows System
ToruntheinstalleronaWindowssystem,youmusthaveWindowssystemadministrator privileges. 1 IfyouaregoingtoinstallinalocaleotherthanU.S.English,orifyouaregoingto installwebMethodsBrokerandrunitinalocaleotherthanU.S.English,setthe Windowssystemlocaletotheproperlocale. Note: TheinstructionsbelowareforWindowsXP.InstructionsforotherWindows systemsvaryslightly. a b c OntheStartmenu,gotoControl Panel Regional and Language Options.
ClicktheAdvanced tab.IntheLanguage for non-Unicode programsarea,clickthe languagetouse,andthenclickOK. RestartWindows.
74
Start the Installer
Themethodyouusetostarttheinstallerdependsonwhetheryouareinstallingonthe localmachineoronaremotemachine. To install on... Local machine Follow these steps... 1 2 Remote machine 1 2 3 OpenWindowsExplorerandgotothedirectorythatcontainsthe installer. DoubleclickthewebMethodsInstaller651.exefile. UseremoteaccesssoftwaresuchaspcAnywheretoaccessthe remotemachine. Openacommandwindowontheremotemachineandgotothe directorythatcontainstheinstaller. Enterthiscommand:
wMinstaller651.exe -Dsun.java2d.noddraw=true
YoumustincludethenoddrawoptionbecauseofaJava incompatibilitywithDirectDraw. Ifthecommandshownabovedoesnotwork,youcandownload thewMinstaller651.jarfiletotheremotemachine(gotothe webMethodsAdvantageWebsiteat http://advantage.webmethods.com,login,clickProduct Downloads, anddownloadthewebMethodsInstallerforUNIX,installJavaJRE 1.4.2,andenterthiscommand:

java -Dsun.java2d.noddraw=true -jar wMinstaller651.jar
Note: Bydefault,thewebMethodsInstallerlauncheswiththeJVMoptionsXincgcand Xmx256m.TheXincgcoptionenablesincrementalgarbagecollection.TheXmx optionallowsJavatousemorememorythanitusesbydefault,incaseyouare installingmanyproductsorarecreatinganinstallationimage.Ifyouarecreatingan installationimageforaplatformthatisdifferentfromtheoneonwhichyouare runningtheinstaller(forexample,youaregoingtocreateanimageforaSolaris platformandyouarerunningtheinstalleronaWindowsplatform),theinstaller needsstillmorememory. IfyouwanttoallowJavatousemorethan256MBofmemory,openacommand window,gotothedirectorythatcontainsthewebMethodsInstaller,andstartthe installerusingacommandthatspecifiestheamountofmemorytoallow.For example,enterthiscommand:
webMethodsInstaller651.exe -Xmx512m -Xincgc
75
Ifyouwanttouseaproxyservertoinstall,createorrunaninstallationscriptor image,downloadwebMethodsproductsfromyourownserver,orinstalla64bitJDK, clickAdvanced OptionsandgotoUseAdvancedOptionsonpage 79. IfyouwanttoinstallwebMethodsproductswithoutusinganyadvancedoptions, clickNextandgotoSpecifyRelease,UserName,andPasswordonpage 82.
Start the Installer on a UNIX, Linux, OS/400, or Mac OS X System

1 IfyouaregoingtoinstallinalocaleotherthanU.S.English,orifyouaregoingto installwebMethodsBrokerandrunitinalocaleotherthanU.S.English,setyourshell totheproperlocalebysettingtheLANGenvironmentvariableasfollows: Shell sh csh 2 Commands
LANG=locale; export LANG setenv LANG locale
NavigatetothedirectorythatcontainsthewebMethodsInstallerandstartthe installerbyenteringthiscommand:
java -jar webMethodsInstaller65.jar -console
76
Start the Installer
Ifyouaregoingtoinstallmanycomponentsorcreateaninstallationimage,the installermightneedmorememorythanJavaprovidesbydefault.Ifyouaregoingto createaninstallationimageforaplatformthatisdifferentfromtheoneonwhichyou arerunningtheinstaller(forexample,youaregoingtocreateanimageforanHPUX platformandyouarerunningtheinstalleronaSolarisplatform),theinstalleruses stillmorememory.Onthecommand,specifyparametersthatallowJavatousemore memoryandenableincrementalgarbagecollectionasthefirsttwoparameters.For example,enterthiscommand:

allocates more memory
java -Xmx512m -Xincgc -jar webMethodsInstaller65.jar

enables incremental garbage collection
IfyouareinstallingonanAIX,OS/400,HPUX,orLinuxplatformandJavasjustin time(JIT)compilerisenabled,thecompilermightinterferewiththeinstallers operation.Youcanstarttheinstallerwithoptionsthatcausetheinstallertoignorethe compiler,asfollows: System AIXand OS/400 Command Eitherofthefollowing:

java -Djava.compiler=NONE -jar webMethodsInstaller65.jar java -Djava.compiler= -jar webMethodsInstaller65.jar
HPUX Linux
java -Djava.compiler=NONE -jar webMethodsInstaller65.jar java -Djava.compiler=NONE -jar webMethodsInstaller65.jar
*ThecommandvariesslightlybasedontheversionoftheJREyouhaveinstalled.
77
Ifyouwanttocreateorrunaninstallationscriptorimage,useaproxyservertoinstall ordownloadwebMethodsproductsfromyourownserver,orinstalla64bitJDK, clickAdvanced OptionsandgotoUseAdvancedOptions,below. IfyouwanttoinstallwebMethodsproductswithoutusinganyadvancedoptions, clickNextandgotoSpecifyRelease,UserName,andPasswordonpage 82.
78
Use Advanced Options

Whenareyoudonesettingadvancedoptions,clickOK.Theinstallerclosesthedialogbox andreturnstothewelcomepanel,whereyoucanclickNexttocontinue.
Create, Install from, or Edit an Installation Script
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 install Note: If errors occur while script is running, installation fails. fully qualified name of file that contains script to edit
TheCreate Scriptoptionbothcreatesthescriptandinstallstheproducts.Therearetwo otheroptionsforcreatingscripts: Tocreateascriptwithoutinstalling,clickEdit script.IntheScript file namebox,enterthe fullyqualifiednameofthefileinwhichtosavethescript.Ifthefiledoesnotexist,the installerwillcreateit.Youcanspecifyanynameyouwantforthefile,andyoudonot havetospecifyanextension. Tocreateascriptfromanexistingscriptwithoutinstalling,clickInstall from script.In theScript file namebox,typethefullyqualifiednameofthefilethatcontainsthe existingscripttouseasatemplate. ClickCreate script.IntheScript file namebox,enterthefullyqualifiednameofthefilein whichtosavethenewscript.Ifthefiledoesnotexist,theinstallerwillcreateit.Youcan specifyanynameyouwantforthefile,andyoudonothavetospecifyanextension.
79
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
80
Use Proxy Server or Your Own Server
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
Install a 64-Bit JDK
81
ProvidetherequestedinformationandthenclickNext.
82
Windows only
ProvidetherequestedinformationandthenclickNext. IfyouareinstallingonaUNIXorLinuxsystemasanonrootuserandareinstalling webMethodsBroker,theuseridunderwhichyouareloggedinmusthavefullreadand writepermissionstotherootdirectoryyouspecify(forexample,yourhomedirectory). Important! DonotinstallwebMethodsBrokerinthesamedirectoryasaprewebMethods6 versionofwebMethodsBrokerorinthesamedirectoryasanyotherwebMethodsBroker product. IfyouareinstallingWorkflowandaregoingtouseIntegrationServersTomcatpackageas yourWorkflowservletengine,youcannotinstallIntegrationServerintoadirectory whosepathcontainsspacesbecauseofaproblemrelatingto1.4.xJDKs.Forexample,you cannotinstallIntegrationServerinthedirectoryProgramFiles\webMethods6. Intherootdirectoryyouspecify,theinstallerwillautomaticallyinstalleachproductina subdirectorynamedaftertheproduct.
83
ChoosethewebMethodsproductsandrelateditemstoinstall.
How to Use the Installer Tree

Theinstallerliststheproductsusingatreestructure.Thehighestlevelshowsproduct namesandreleasesandthelowerlevelsshowtheitemsthatmakeuporarerelatedtothe product. Ifyouselectthecheckboxnexttoaproduct,theinstallerautomaticallyselectsthe minimumrecommendedsetofitemsfortheproduct.Italsoselectsotherproductsor itemsthattheproductdependsonhavingonthesamemachine(ifthoseproductsoritems arenotalreadypresent).Ifyoudeselectaproductoritemonwhichaproductdepends, theinstallerdeselectsthedependentproduct.Forexample,ifyouselectTrading NetworksServer,theinstallerselectsIntegrationServer,becauseTradingNetworks ServerdependsonIntegrationServer.IfyoudeselectIntegrationServer,theinstallerde selectsTradingNetworksServer. Someproductsrequireotherproductsanditemsbutnotnecessarilyonthesamemachine. Forexample,inaproductionenvironment,webMethodsrecommendsyouinstallMy webMethodsServeranduserinterfacesonadedicatedmachine,notononthesame machineswiththeproductstowhichtheuserinterfacesbelong.Youmustselectthese
84
productsanditemsyourself,whenyouareinstallingonthepropermachine.Youmust alsochooseoptionalitemsyourself. Note: Ifyouhavealreadyinstalledaniteminthespecifiedrootdirectory,theitemnameis followedbythetext(Installed)andtheitemnameanditscheckboxaregrayedout.
Finding Items
Thetablebelowindicatesthelocationofcertainitemsintheinstallerproducttree. This item... BrokerAdministrator,JMSAdministrator,LoggingUtility, MainframePackage,ModelerDesignPackage,Process Runtime,ServicenetPackage,andWorkflowServlet Productuserinterfaces(forexample,Monitoruserinterface) ExtendedCharacterSetEncodingSupportandServicenet ClientAPI JMSProvider6.5SP1andBrokerClientJavaAPI6.5SP1 MainframePlugin Listed under... IntegrationServer
MywebMethods UserInterfaces CommonFiles BrokerandJMS Developer
Complete Product Selection

Whenyouaredone,clickNext.Readthelicenseagreement.Ifyouaccepttheterms,select thecheckboxandclickNext.Iflanguagepacksareavailableforproductsyouare installingorhavealreadyinstalled,theinstallerdisplaysthelanguagepackspanel;goto SelectLanguagePacks,below.Otherwise,gotoConfigureProductsonpage 87.
85
Select Language Packs
Selectthelanguagepackstoinstall. webMethodsMainframeallowsyoutoinstallmultiplelanguagepacks.However,ifyou installthelanguagepackthatmatchesthehostmachineslocale,webMethodsMainframe automaticallyloadsthatlanguagepack,andonlythatlanguageisavailabletousers.If youdonotinstallthelanguagepackthatmatchesthehostmachineslocale,webMethods Mainframeusesthedefault,U.S.English.Ifyouwanttousethelanguageofanother installedlanguagepack,youmustmodifythelocaleinwhichwebMethodsMainframeis started. Allotherproductssupportmultiplelanguages;youcaninstallasmanylanguagepacksas youwant,andallofthelanguagesinstalled(includingthedefault,U.S.English)willbe availabletousers. ClickNext.Ifyouareinstallinganyoftheproductslistedbelow,theinstallerdisplays panelsthatrequestconfigurationinformation.Ifyouarenotinstallinganyofthese products,gotoReviewandInstallonpage 102. ConfigurewebMethodsBroker ConfigureIntegrationServer ConfigureManager,Optimize,orBoth ConfigureManagerServer ConfigureServicenet
86
Configure Products
ConfigureTradingNetworksServer ConfigureWorkflow
Configure Products
Afteryoucompleteeachconfigurationpanel,clickNext.
Configure webMethods Broker

Important! IfyouareinstallingwebMethodsBrokeronaUNIXorLinuxsystemasanon rootuser,youwillnotseethewebMethods Brokerpaneldiscussedbelow.Afterinstallation, gotoAppendix C,CreatetheBrokerServerConfigurationManuallyforinstructionson supplyingwebMethodsBrokerconfigurationinformation.
provided by webMethods
see below 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
Broker Server Configuration

YouwouldcreatetheBrokerServeratthistime(thatis,usingtheinstaller)ifyouwantto specifyoneofthestoragesizesthatareofferedbytheinstallerandyouwanttocreate separatestoragesessionsforconfiguration(metadata)andruntimedata.Usingseparate storagesessionsminimizestheriskofcorruptionthatmightoccurwithacombined storagelocation.Inaddition,youcanusethewebMethodsBroker6.5onlineconfiguration databackuptooltobackupconfigurationdatawithouthavingtoshutdownyourBroker Server.(Formoreinformationaboutthetool,seethewebMethodsBrokerAdministrators
87
Guide.)IfyouchoosetocreatetheBrokerServeratthistime,continuetoStorage Size, below. YouwouldnotcreatetheBrokerServeratthistime(thatis,usingtheinstaller)ifyouwant tospecifyadifferentstoragesizethanisofferedbytheinstallerorifyouwanttocreatea combinedstoragesessionforconfigurationandruntimedata.Ifyoudonotneedtouse theonlineconfigurationdatabackuptool,usingacombinedsessionmightsaveyoua smallamountofdiskspace.IfyouchoosetonotcreatetheBrokerServeratthistime,you mustuseawebMethodsBrokercommandtocreatetheBrokerServerafterinstallationis complete(seeAppendix C,CreatetheBrokerServerConfigurationManually). Important! Youcannotlaterchangefromseparatesessionstoacombinedsessionorvice versa.webMethodsrecommendscreatingseparatesessions.
Storage Size
SelectapreconfiguredstoragesessionfortheBrokerServerthatisadequateforyour expectedusageneeds,asfollows: Files Created Small Configuration 32MBlogfileand 512MBstoragefile IdealforrunningdevelopmentBroker Serversorrelativelyfewproduction integrations,lowdocumentvolumes,and nodocumentlogging. Fastestofall configurations. When to Use Broker Server Startup Time
Medium Configuration 64MBlogfileand 1GBstoragefile Standarddeploymentsize,fitsmorecases thanSmall.Largermaximumtransaction sizeandtwicethestoragecapacityof Small. Uptotwiceas longasforSmall.
Large Configuration 128MBlogfileand 2GBstoragefile Suitableforproductiondeploymentswith manyintegrationsrunningatrelatively highdocumentvolumes,possiblyusing documentloggingaswell. Twotimeslonger thanforMedium; fourtimeslonger thanforSmall.
*For complete information on Broker Server storage sessions, see the webMethods Broker Administrators Guide.)
Whendeterminingtheappropriatesizeforthelogfile,thefactorstobalanceareBroker Serverstartuptimeandthedesiredmaximumtransactionsize.Thesmallerthelogfile, thefasterthestartup;however,withalargerlogfile,youcansendlargermessages(that is,onelargersizedsingledocumentorabatchofdocuments).Ifnecessary,youcan removeorreplacelogfilesafterinstallation,andyoucanincreaseordecreasetheirsize.
88
Configure Products
Startuptimedoesnotdependonthesizeofthestoragefile;additionalstoragecapacity merelypreventstheBrokerServerfromrunningoutofroom.Afterinstallation,ifthe amountofstorageallocatedturnsouttobeinsufficient,youcanaddstoragefilesand increasetheirsize.Youcannotremovestoragefilesordecreasetheirsize. ThewebMethodsBrokerAdministratorsGuideprovidesinstructionsonworkingwithlog filesandstoragefiles.
Configure Integration Server
provided by webMethods; optional, can supply at startup start/shut down manually; typical for development environment start/shut down automatically when start/shut down system; typical for production environment
89
Configure Manager, Optimize, or Both

ThissectionexplainshowtoconfigureManagerandOptimize.Ifyouareinstalling Manageronly,theproductnameusedintheconfigurationpaneltitlesiswebMethods Manager. IfyouareinstallingOptimizeonlyorbothManagerandOptimize,theproduct nameusediswebMethods Optimize.
Configure the Controller

port My webMethods Server uses to communicate with controller; default port for My webMethods Server is 8080 name of My webMethods Server host machine or, if necessary, IP address
name of controller host machine or, if necessary, IP address HTTP port for controller JMX port for data handler and satellites to use to communicate with controller
port for data handler to use to communicate with controller
name of data handler host machine or, if necessary, IP address
Important! Donotuselocalhosttoidentifythehostmachines.
90
Configure Products
Configure the Data Handler or Satellite
name of controller host machine or, if necessary, IP address JMX port for data handler and satellites to use to communicate with controller
Important! Donotuselocalhosttoidentifythecontrollerhostmachine.
91
Configure the Database Connections

Important! YoumustconfigurethedatabaseconnectionsduringinstallationorManager andOptimizewillnotbefullyfunctionalafterinstallation. IfyoualreadyhaveaProcessAuditLogdatabasecomponentthatyouareusingtostore ModelerorWorkflowprocessdata,provideconnectionparametersthatpointtotheexist ingdatabase.
driver for controller or data handler to use to communicate with database name of database host machine or, if necessary, IP address port for controller or data handler to use to communicate with database name of database to contain database objects; if SQL Server, must be unique
database user and password for controller and data handler to use to log into database component; must be unique
ManagerorOptimizecreatesaJDBCconnectionpoolforeachdatabasecomponent.Ifyou laterneedtomodifytheconnectionpools,seethewebMethodsDatabaseGuidefor instructions.
92
Configure Products
Configure Manager Server

Provide the License Key
provided by webMethods; optional, can supply at startup start/shut down manually; typical for development environment start/shut down automatically when start/shut down system; typical for production environment
93

Important! YoumustdefinetheJDBCconnectionpoolfortheManagerserverduring installation,ortheManagerserverwillnotworkafterinstallation.
driver to use to communicate with database see below database user and password for Manager server to use to log in to database
TheDatabase URLboxprovidesatypicalformatfortheselecteddriver,asfollows: RDBMS Oracle SQL Server URL

jdbc:wm:oracle://host_or_IPaddress:port;SID=database_name
Default Port 1521 1433
jdbc:wm:sqlserver://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
Acceptthedefaultsfortheotherfields.IfyoulaterneedtochangeyourJDBCconnection poolconfiguration,seeIdentifytheDatabasesthatContaintheCrossReference, DocumentHistory,ISCoreAuditLog,ProcessAuditLog,Reporting,andStaging DatabaseComponentsonpage 170.Theinstructionsinthatsectionareforcreating pools,buttheinstructionsformodifyingpoolsareverysimilar.
94
Configure Products
Configure Servicenet
Configure the Controller, Data Handler, or Both
port My webMethods Server uses to communicate with controller; default port for My webMethods Server is 8080 name of My webMethods Server host machine or, if necessary, IP address
name of controller host machine or, if necessary, IP address HTTP port for controller JMX port for data handler to use to communicate with controller
port for data handler to use to communicate with controller
name of data handler host machine or, if necessary, IP address
Important! Donotuselocalhosttoidentifythehostmachines.
95

Important! YoumustconfigurethedatabaseconnectionsduringinstallationorServicenet willnotbefullyfunctionalafterinstallation. IfyoualreadyhaveaProcessAuditLogdatabasecomponentthatyouareusingtostore ModelerorWorkflowprocessdata,provideconnectionparametersthatpointtotheexist ingdatabase.
driver for controller or data handler to use to communicate with database name of database host machine or, if necessary, IP address port for controller or data handler to use to communicate with database name of database to contain database objects; if SQL Server, must be unique
database user and password for controller and data handler to use to log into database component; must be unique
port for Servicenet clients to use to communicate with Servicenet registry (displays on Servicenet database component panel only)
Important! AllServicenetcomponentsarepreconfiguredtousethedefaultSubnet port.If youdistributeServicenetcomponentsovermultiplemachines,changingtheSubnet port fromthedefaultwillrequireyoutoperformmanualconfigurationtasksafterinstallation. However,ifyouintendtosetupmorethanoneServicenetenvironment,youmustusea differentsubnetportforeachenvironmenttopreventconflicts. ServicenetcreatesaJDBCconnectionpoolforeachdatabasecomponent.Ifyoulaterneed tomodifytheconnectionpools,seethewebMethodsDatabaseGuideforinstructions.
96
Configure Products
Configure Trading Networks Server

Important! YoumustdefinetheJDBCconnectionpoolforTradingNetworksServerduring installation,orTradingNetworksServerwillnotstartafterinstallation.
driver to use to communicate with database see below database user and password for Trading Networks Serverr to use to log in to database
TheDatabase URLboxprovidesatypicalformatfortheselecteddriver,asfollows: RDBMS Oracle Oracle config ured for RAC URL
jdbc:wm:oracle://host_or_IPaddress:port;SID=database_name
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) jdbc:wm:sqlserver://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor jdbc:wm:sybase://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
SQL Server Sybase
1433 5000
97
RDBMS DB2 UDB DB2 UDB for AS/400
URL
jdbc:wm:db2://host_or_IPaddress:port; databaseName=database_name;PackageName=package_name jdbc:wm:db2://host_or_IPaddress:port; LocationName=location_to_access; PackageName=package_name; AlternateId=schema_to_use; CollectionId=package_collection
Note: AlternateIdmustmatchtheschemainwhichyoucreated theTradingNetworksdatabasetables.
98
Configure Products
Configure Workflow
Configure Workflow Client
DNS host name or network name of central Workflow Server host machine
port used by central Workflow Server to communicate with Workflow clients port used by central Workflow Server for RMI
ThecentralWorkflowServerdefaultsforconnectionandRMIregistryportsdependon thesystemonwhichthecentralWorkflowServerisinstalled.ForWindows,thedefaults are6000and6001,respectively.Foranyothersystem,thedefaultsare5000and5001, respectively. IfyoulaterneedtochangethispartoftheWorkflowclientconfiguration,seethe webMethodsWorkflowUsersGuideforinstructions.
Configure Workflow Server

ThevaluesyouprovideonthewebMethods Workflow Serverpaneldependonwhetheryou wanttheWorkflowServeryouareinstallingtobethecentralWorkflowServerora secondaryWorkflowServerthatwillhelpthecentralWorkflowServerhandlethe workload. IfyoulaterneedtochangethispartoftheWorkflowServerconfiguration,youcandoso usingtheWorkflowConfigurator.SeeCompletetheWorkflowInstallationonpage 213 forinstructions.
99
Install as Central Workflow Server
DNS host name or network name of machine on which installing central Workflow Server port for central Workflow Server to use to communicate with Workflow clients port for central Workflow Server to use for RMI
OnWindowssystems,changetheConnection port andtheRMI registry port to6000and6001, respectively.Ports5000and5001arereservedbyWindows. Important! IfyouinstallmultiplecentralWorkflowServersonthesamemachine,the WorkflowServersmustusedifferentconnectionandRMIregistryports.
100
Configure Products
Install as Secondary Workflow Server
DNS host name or network name of machine that hosts central Workflow Server port central Workflow Server uses to communicate with Workflow clients port central Workflow Server uses for RMI
OnWindowssystems,changetheConnection port andtheRMI registry port to6000and6001, respectively.Ports5000and5001arereservedbyWindows.
101
Review and Install
Reviewthelistofproductsanditemsyouhaveselectedforinstall.Ifthelistiscorrect, clickNext.Ifthelistisnotcorrect,clickBackuntilyoureturntotheinstallerproducttree andcorrectthechoices. Theinstallerinstallstheproductsandrelateditems,thendisplaystheinstallation completepanel.ClickClose.

102
Overwrite Using the Wizard
Overwrite Using the Wizard

IfoneormoreofyourwebMethodsproductinstallationshasbeencorrupted,orifyou accidentallydeletedsomefilesfromaproductdirectory,youcanoverwritetheproducts usingthewebMethodsInstaller. Important! Onlyoverwriteproductsinthemostextremecases.Overwritingnotonly overwritestheproductinstallations,itoverwritesallrelatedfilesyouhavecreatedor customized. Iftheinstallationyouareoverwritingincludesprogramfilesthatarenotincludedinthe newversion,thosefilesremain(unused)intheinstallation. 1 2 3 4 5 6 7 ShutdownthewebMethodsproductsyouaregoingtooverwrite. Ifyouwanttosavefilesyouhavecreatedorcustomized,copythemtoadifferent directory. Ifyouwanttooverwritefromaninstallationscriptorimage,createthescriptor image. Starttheinstaller.OntheinstallerWelcomepage,clickAdvanced Options.Theinstaller displaystheAdvanced Optionsdialogbox. ClicktheReinstalltabandselecttheReplace corrupt installation by overwriting all files, including user datacheckbox. Ifyouwanttouseaproxyserver,clicktheServerstab,selecttheUse proxy servercheck box,andprovidetherequiredinformation. Ifyouareoverwritingfromascript,clicktheScripttab,selecttheUser installation script checkbox,andthenclickCreate script.IntheScript file namebox,typethefully qualifiednameofthefilethatcontainsthescripttousetooverwrite. Important! Iferrorsoccurwhileaninstallationscriptisrunning,theinstallationfails. Ifyouareoverwritingfromanimage,clicktheImagestab,selecttheUse installation imagecheckbox,andthenclickInstall from image.IntheImage file namebox,typethe fullyqualifiednameofthefilethatcontainstheimagetousetooverwrite. 8 9 Ifyouarenotusinganinstallationscripttooverwrite,choosetheproductsto overwrite. Moveanyusercreatedorcustomizedfilesyoucopiedearlierbacktotheappropriate locationinthenewinstallation.
103
104
CHAPTER
Advanced Installation 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 Products to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Select Language Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Configure Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 Review and Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Complete the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Overwrite Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
105
CHAPTER 7 Advanced Installation Using Console Mode
Overview
Thischapterexplainshowtodothefollowing: InstallfromaninstallationscriptonaWindowssystemusingthewebMethods Installerconsolesilentmode.Youcanuseconsolesilentmodetoinstalllocallyor remotelyonaWindowssystem. InstallfromthewebMethodsInstaller,createaninstallationscriptorimage,orinstall fromaninstallationscriptorimageonaUNIX,Linux,OS/400,orMacOSXsystem usingthewebMethodsInstallerconsolemode.Youcanuseconsolemodetoinstall locallyorremotelyonaUNIX,Linux,andOS/400system,orlocallyonaMacOSX system. Iferrorsorwarningsoccurduringtheinstallation,theinstallerwritestheerrorsand warningstoafilenamedWmInstallLog.txtandstoresthefileinthemaininstallation directory(bydefault,webMethods6).
Install in Console Silent Mode on a Windows System

Toinstallfromaninstallationscript,youmusthavealreadycreatedthescript.For instructionsoncreatingascript,andforcompleteinstructionsonusingtheinstaller,see Chapter 6,AdvancedInstallationUsingtheWizard. Important! Iferrorsoccurwhileaninstallationscriptisrunning,theinstallationfails. Toruntheinstaller,youmusthaveWindowssystemadministratorprivileges. 1 IfyouaregoingtoinstallinalocaleotherthanU.S.English,orifyouaregoingto installwebMethodsBrokerandrunitinalocaleotherthanU.S.English,setthe Windowssystemlocaletotheproperlocale. Note: TheinstructionsbelowareforWindowsXP.InstructionsforotherWindows systemsvaryslightly. a b c 2 OntheStartmenu,gotoSettings Control Panel Regional and Language Options.
ClicktheAdvanced tab.IntheLanguage for non-Unicode programsarea,clickthe languagetouse,andthenclickOK. RestartWindows.
OpenacommandwindowandgotothedirectorythatcontainsthewebMethods Installer.Starttheinstallerbyenteringthecommandshownbelow,wherescript_fileis thefullyqualifiednameofthefilecontainingtheinstallationscriptfromwhichto install:

webMethodsInstaller651.exe -readScript script_file -console
106
Install Using Console Mode on a UNIX, Linux, OS/400, or Mac OS X System
Theinstallerwritesoutputtothecommandwindowasitrunsthescript. 3 4 Ifyoushutdownyourantivirussoftwarebeforestartingtheinstaller,restartthe software. GotoChapter 13,CompletingtheInstallation.

Start the Installer
1 IfyouaregoingtoinstallinalocaleotherthanU.S.English,orifyouaregoingto installwebMethodsBrokerandrunitinalocaleotherthanU.S.English,setyourshell totheproperlocalebysettingtheLANGenvironmentvariableasfollows: Shell sh csh 2 Commands
LANG=locale; export LANG setenv LANG locale
NavigatetothedirectorythatcontainsthewebMethodsInstallerandstartthe installerbyenteringthiscommand:
java -jar webMethodsInstaller65.jar -console
Ifyouaregoingtoinstallmanycomponentsorcreateaninstallationimage,the installermightneedmorememorythanJavaprovidesbydefault.Ifyouaregoingto createaninstallationimageforaplatformthatisdifferentfromtheoneonwhichyou arerunningtheinstaller(forexample,youaregoingtocreateanimageforanHPUX platformandyouarerunningtheinstalleronaSolarisplatform),theinstalleruses stillmorememory.Onthecommand,specifyparametersthatallowJavatousemore memoryandenableincrementalgarbagecollectionasthefirsttwoparameters.For example,enterthiscommand:

allocates more memory
java -Xmx512m -Xincgc -jar webMethodsInstaller65.jar

enables incremental garbage collection
107
IfyouareinstallingonanAIX,OS/400,HPUX,orLinuxplatformandJavasjustin time(JIT)compilerisenabled,thecompilermightinterferewiththeinstallers operation.Youcanstarttheinstallerwithoptionsthatcausetheinstallertoignorethe compiler,asfollows: System AIXand OS/400 Command Eitherofthefollowing:

java -Djava.compiler=NONE -jar webMethodsInstaller65.jar java -Djava.compiler= -jar webMethodsInstaller65.jar
HPUX Linux
java -Djava.compiler=NONE -jar webMethodsInstaller65.jar java -Djava.compiler=NONE -jar webMethodsInstaller65.jar
*ThecommandvariesslightlybasedontheversionoftheJREyouhaveinstalled.
Ifyouwanttouseaproxyservertoinstall,createorrunaninstallationscriptorimage, downloadwebMethodsproductsfromyourownserver,orinstalla64bitJDK,addthe parameterslistedbelowinanyorderafter-jar webMethodsInstaller651.jar. Parameter Use an HTTP proxy server to install
-proxyHost host
Variables
HostnameorfullyqualifiedIPaddressofthe proxyserver. Portusedbytheproxyserver. Usernamefortheinstallertousetologonto theproxyserver. Passwordfor-proxyUser user_name.
-proxyPort port -proxyUser user_name
-proxyPass password
Use a Socks proxy server to install

-socksProxyHost host
HostnameorfullyqualifiedIPaddressofthe proxyserver. Portusedbytheproxyserver.
-socksProxyPort port
Create a script and install

-writeScript script_file
Fullyqualifiednameofthefileinwhichto savethescript.
Create a script without installing

-editScript script_file
Fullyqualifiednameofthefileinwhichto savethescript.
108
Parameter
Variables
Create a script from an existing script without installing

-readScript script_file
Fullyqualifiednameofthefilethatcontains theexistingscripttouseasatemplate. Fullyqualifiednameofthefileinwhichto savethenewscript.
-writeScript script_file
Edit a script
-editScript script_file
Fullyqualifiednameofthefilethatcontains thescripttoedit.
Install from a script

-readScript script_file
Fullyqualifiednameofthefilethatcontains theinstallationscriptfromwhichtoinstall. Important! Ifanyerrorsoccurwhilean installationscriptisrunning,theinstallation fails.
Create an image
-writeImage image_file
Fullyqualifiednameofthefileinwhichto savetheinstallationimage. Platformforwhichyouarecreatingtheimage. Youcancreateanimageforanyplatformfrom anyplatform.Validvalueareasfollows: Platform Windows Solaris AIX HPUXPARISC HPUXItanium2 Linux OS/400 Mac Value
WNT SOL AIX HP11 HP11IT LNX AS400 OSX
-imagePlatform platform
Thedefaultistheplatformonwhichyouare runningtheinstaller.
109
Parameter Install from a image

-readImage image_file
Variables
Fullyqualifiednameofthefilethatcontains theinstallationimagefromwhichtoinstall.
Specify webMethods Installer server and release

-URLBase URL
Ifyouhavecreatedyourownserverfrom whichtodownloadwebMethodsproducts, URLfortheserver(forexample, http://machine/cgibin/script.cgi). Releaseoftheproductstoinstall(6.5).
-serverVersion version
Install a 64-bit JDK

-64BitJVM
Letsyouinstalla64bitJDKona64bitSolaris, HPUX,orAIXoperatingsystem.

Whenprompted,providethefollowinginformation: IfyoudidnotspecifyyourownserverandtheversionofthewebMethodsproductsto installonthecommandyouusedtostarttheinstaller,choosetheversionofthe platformtoinstall.ThenchoosethewebMethodsInstallerserverfromwhichyou wanttodownloadtheproducts. ProvidetheusernameandpasswordyouusetologintothewebMethodsAdvantage Website.

Whenprompted,specifytherootdirectoryintowhichtoinstallwebMethodsproducts. IfyouareinstallingasanonrootuserandareinstallingwebMethodsBroker,theuserid underwhichyouareloggedinmusthavefullreadandwritepermissionstotheroot directoryyouspecify(forexample,yourhomedirectory). Important! DonotinstallwebMethodsBrokerinthesamedirectoryasaprewebMethods6 versionofwebMethodsBrokerorinthesamedirectoryasanyotherwebMethodsBroker product. IfyouareinstallingWorkflowandaregoingtouseIntegrationServersTomcatpackageas yourWorkflowservletengine,youcannotinstallIntegrationServerintoadirectory whosepathcontainsspacesbecauseofaproblemrelatingto1.4.xJDKs.Forexample,you cannotinstallIntegrationServerinthedirectoryProgramFiles\webMethods6.
110
Intherootdirectoryyouspecify,theinstallerwillautomaticallyinstalleachproductina subdirectorynamedaftertheproduct.

Whenprompted,choosethewebMethodsproductsandrelateditems,like documentation,toinstall.
How to Use the Installer Tree

Theinstallerliststheproductsusingatreestructure.Thehighestlevelshowsproduct namesandreleasesandthelowerlevelsshowtheitemsthatmakeuporarerelatedtothe product. Theinstallercandisplayonlyalimitednumberofproductsatatime.Topageforward throughthelist,enteraplussign(+).Topagebackwardthroughthelist,enteraminus sign().Tosearchforaspecificproductoritem,enterS,thenenterthenameofthe productoritem.EnterSagaintofindthenextoccurrenceoftheproductoritem. Ifyouwanttoinstalltheminimumrecommendedsetofitemsforaproduct,enterthe numbershownnexttotheproductheading(forexample,enterthenumberforIntegration Server).TheinstallershowsanXnexttoeachoftherecommendeditemslistedunderthe product.Ifyouwanttoinstallonlyitemsyouchooseforaproduct,enterthenumberfor eachofthoseitems(forexample,enterthenumberforProgram FilesunderIntegration Server).Youmustentereachnumberonaseparateline.TheinstallershowsanXnextto eachitemyouselect.Whenallitemsareselectedforaproduct,theinstallershowsanX nexttotheproductheading.Ifonlycertainitemsareselectedforaproduct,theinstaller showsapoundsign(#)nexttotheproductheading. Note: Ifyouhavealreadyinstalledaniteminthespecifiedrootdirectory,theinstaller showsanInexttotheitem.
Finding Items
Thetablebelowindicatesthelocationofcertainitemsintheinstallerproducttree. This item... BrokerAdministrator,JMSAdministrator,LoggingUtility, MainframePackage,ModelerDesignPackage,ProcessRunt ime,ServicenetPackage,andWorkflowServlet Productuserinterfaces(forexample,Monitoruserinterface) ExtendedCharacterSetEncodingSupportandServicenet ClientAPI Is listed under... IntegrationServer
MywebMethods UserInterfaces CommonFiles
111
This item... JMSProvider6.5SP1andBrokerClientJavaAPI6.5SP1 MainframePlugin
Is listed under... BrokerandJMS Developer
Complete Product Selection

Whenyouaredone,pressENTERtwice.Theinstallerdisplaysthelicenseagreement. Readtheagreementandindicatewhetheryouacceptitsterms. Note: Toseetheentirelicenseagreement,youmighthavetoincreasethenumberoflines thatarevisibleinyourconsolewindow. Iflanguagepacksareavailableforproductsyouareinstallingorhavealreadyinstalled, theinstallerpromptsyoutochoosepackstoinstall;gotoSelectLanguagePacks,below. Otherwise,gotoConfigureProductsonpage 113.
Select Language Packs

webMethodsMainframeallowsyoutoinstallmultiplelanguagepacks.However,ifyou installthelanguagepackthatmatchesthehostmachineslocale,webMethodsMainframe automaticallyloadsthatlanguagepack,andonlythatlanguageisavailabletousers.If youdonotinstallthelanguagepackthatmatchesthehostmachineslocale,webMethods Mainframeusesthedefault,U.S.English.Ifyouwanttousethelanguageofanother installedlanguagepack,youmustmodifythelocaleinwhichwebMethodsMainframeis started. Allotherproductssupportmultiplelanguages;youcaninstallasmanylanguagepacksas youwant,andallofthelanguagesinstalled(includingthedefault,U.S.English)willbe availabletousers. Ifyouareinstallinganyoftheproductslistedbelow,theinstallernextpromptsfor configurationinformation.Ifyouarenotinstallinganyoftheseproducts,gotoReview andInstallonpage 124. ConfigurewebMethodsBroker ConfigureIntegrationServer ConfigureManager,Optimize,orBoth ConfigureManagerServer ConfigureServicenet ConfigureTradingNetworksServer ConfigureWorkflow
112
Configure Products
Configure webMethods Broker
Important! IfyouareinstallingwebMethodsBrokeronaUNIXorLinuxsystemasanon rootuser,youwillnotseethepromptsdiscussedbelow.Afterinstallation,goto Appendix C,CreatetheBrokerServerConfigurationManuallyforinstructionson supplyingwebMethodsBrokerconfigurationinformation. Whenprompted,providetheinformationbelowforwebMethodsBroker. 1 2 EnterthewebMethodsBrokerlicensekeyprovidedbywebMethods. IndicatewhetheryouwanttocreatetheBrokerServer. YouwouldcreatetheBrokerServeratthistime(thatis,usingtheinstaller)ifyouwant tospecifyoneofthestoragesizesthatareofferedbytheinstallerandyouwantto createseparatestoragesessionsforconfiguration(metadata)andruntimedata. Usingseparatestoragesessionsminimizestheriskofcorruptionthatmightoccur withacombinedstoragelocation.Inaddition,youcanusethewebMethodsBroker 6.5onlineconfigurationdatabackuptooltobackupconfigurationdatawithout havingtoshutdownyourBrokerServer.(Formoreinformationaboutthetool,seethe webMethodsBrokerAdministratorsGuide.)IfyouchoosetocreatetheBrokerServerat thistime,continuetostep 3. YouwouldnotcreatetheBrokerServeratthistime(thatis,usingtheinstaller)ifyou wanttospecifyadifferentstoragesizethanisofferedbytheinstallerorifyouwantto createacombinedstoragesessionforconfigurationandruntimedata.Ifyoudonot needtousetheonlineconfigurationdatabackuptool,usingacombinedsession mightsaveyouasmallamountofdiskspace.IfyouchoosetonotcreatetheBroker Serveratthistime,youmustuseawebMethodsBrokercommandtocreatetheBroker Serverafterinstallationiscomplete(seeAppendix C,CreatetheBrokerServer ConfigurationManually). Important! Youcannotlaterchangefromseparatesessionstoacombinedsessionor viceversa.webMethodsrecommendscreatingseparatesessions. 3 IdentifytheportonwhichtoruntheBrokerServer.Thedefaultportis6849. Important! IfyouinstallmultipleBrokerServersonthesamemachine,youmust configureeachBrokerServertorunonadifferentport. 4 ProvidethefullyqualifiedpathtothedatadirectoryinwhichtostoreBrokerServer data.
113
SelectapreconfiguredstoragesessionfortheBrokerServerthatisadequateforyour expectedusageneeds,asfollows: Files Created Small Configuration 32MBlogfileand 512MBstoragefile IdealforrunningdevelopmentBroker Serversorrelativelyfewproduction integrations,lowdocumentvolumes, andnodocumentlogging. Fastestofall configurations. When to Use Broker Server Startup Time
Medium Configuration 64MBlogfileand 1GBstoragefile Standarddeploymentsize,fitsmore casesthanSmall.Largermaximum transactionsizeandtwicethestorage capacityofSmall. Uptotwiceas longasforSmall.
Large Configuration 128MBlogfileand 2GBstoragefile Suitableforproductiondeployments withmanyintegrationsrunningat relativelyhighdocumentvolumes, possiblyusingdocumentloggingas well. Twotimeslonger thanforMedium; fourtimeslonger thanforSmall.
*For complete information on Broker Server storage sessions, see the webMethods Broker Administrators Guide.)
Whendeterminingtheappropriatesizeforthelogfile,thefactorstobalanceare BrokerServerstartuptimeandthedesiredmaximumtransactionsize.Thesmallerthe logfile,thefasterthestartup;however,withalargerlogfile,youcansendlarger messages(thatis,onelargersizedsingledocumentorabatchofdocuments).If necessary,youcanremoveorreplacelogfilesafterinstallation,andyoucanincrease ordecreasetheirsize. Startuptimedoesnotdependonthesizeofthestoragefile;additionalstorage capacitymerelypreventstheBrokerServerfromrunningoutofroom.After installation,iftheamountofstorageallocatedturnsouttobeinsufficient,youcanadd storagefilesandincreasetheirsize.Youcannotremovestoragefilesordecreasetheir size. ThewebMethodsBrokerAdministratorsGuideprovidesinstructionsonworkingwith logfilesandstoragefiles.
114
Configure Integration Server

Whenprompted,providetheIntegrationServerlicensekeyprovidedbywebMethods. IfyouareinstallingonaWindowssystem,indicatewhethertoinstallIntegrationServer asaWindowsapplicationorasaWindowsservice,basedonthefollowing: If you want ... TostartandshutdownIntegrationServermanually.Typically,you wouldinstalladevelopmentIntegrationServerasanapplication. IntegrationServertostartandshutdownautomaticallywhenyou startandshutdownyoursystem.Typically,youwouldinstalla productionIntegrationServerasaservice. Install as... Application Service
Configure Manager, Optimize, or Both

ThissectionexplainshowtoconfigureManagerandOptimize.Ifyouareinstalling Manageronly,theproductnameusediswebMethodsManager. Ifyouareinstalling OptimizeonlyorbothManagerandOptimize,theproductnameusediswebMethods Optimize. Configure the Controller Ifyouareinstallingthecontroller,providetheinformationbelowwhenprompted. Box or Prompt Controller host Description Nameofthecontrollerhostmachine.Ifnecessary,youcanprovide thehostmachinesIPaddress. Important! Donotuselocalhosttoidentifythehostmachine. Controller port Controller JMX port My webMethods Server host HTTPportforthecontroller. JMXportforthesatellitesandthedatahandlertousetocommuni catewiththecontroller. NameofthemachinethathostsMywebMethodsServer.Ifneces sary,youcanprovidethehostmachinesIPaddress. Important! Donotuselocalhosttoidentifythehostmachine. My webMethods Server port PortthatMywebMethodsServerusestocommunicatewiththe controller.ThedefaultportforMywebMethodsServeris8080.
115
Box or Prompt Data handler host
Description Nameofthedatahandlerhostmachine.Ifnecessary,youcanpro videthehostmachinesIPaddress. Important! Donotuselocalhosttoidentifythehostmachine.
Data handler port
Portforthedatahandlertousetocommunicatewiththecontrol ler.
Configure the Data Handler or Satellite Ifyouareinstallingthedatahandlerorsatelliteonanoncontrollerhostmachine,provide theinformationbelowwhenprompted. Box or Prompt Controller host Description Nameofthecontrollerhostmachine.Ifnecessary,youcanprovide thehostmachinesIPaddress. Important! Donotuselocalhosttoidentifythehostmachine. Controller JMX port JMXportforthedatahandlerorsatellitestousetocommunicate withthecontroller.
Configure the Database Connections Whenprompted,providetheinformationbelow. Important! YoumustconfigurethedatabaseconnectionsduringinstallationorManager andOptimizewillnotbefullyfunctionalafterinstallation. IfyoualreadyhaveaProcessAuditLogdatabasecomponentthatyouareusingtostore ModelerorWorkflowprocessdata,provideconnectionparametersthatpointtotheexist ingdatabase. Box or Prompt Database driver Database host Database port Description Driverforthecontrollerordatahandlertousetocommunicate withthedatabase. Nameofthedatabasehostmachine.Ifnecessary,youcanprovide thehostmachinesIPaddress. Portforthecontrollerordatahandlertousetocommunicatewith thedatabase.
116
Box or Prompt Database name (SQLServer)or SID(Oracle) Database user
Description Nameofthedatabasethatyouwanttocontainthedatabaseobjects forthedatabasecomponent.IfyouareusingaSQLServerdata base,thedatabasenamemustbeunique. Databaseuserforthecontrollerandthedatahandlertousetolog intothedatabasecomponent.Thedatabaseuserforeachdatabase componentmustbeunique. Passwordforthedatabaseuser.
Database user password
OptimizecreatesaJDBCconnectionpoolforeachdatabasecomponent.Ifyoulaterneed tomodifytheconnectionpools,seethewebMethodsDatabaseGuideforinstructions.
Configure Manager Server

Provide the License Key Whenprompted,providetheManagerserverlicensekeyprovidedbywebMethods. IfyouareinstallingonaWindowssystem,indicatewhethertoinstalltheManagerserver asaWindowsapplicationorasaWindowsservice,basedonthefollowing: If you want ... TostartandshutdowntheManagerservermanually.Typically,you wouldinstalladevelopmentManagerserverasanapplication. TheManagerservertostartandshutdownautomaticallywhenyou startandshutdownyoursystem.Typically,youwouldinstalla productionManagerserverasaservice. Install as... Application Service
117
Configure the Database Connection Whenprompted,providetheinformationbelow. Important! YoumustconfigurethedatabaseconnectionduringinstallationortheManager serverwillnotworkafterinstallation. Box or Prompt Database driver Database URL Entry Drivertousetocommunicatewiththedatabase. URLforthedatabase,asfollows: URL Oracle
jdbc:wm:oracle://host_or_IPaddress:port; SID=database_name
Default Port
1521
SQL Server
1433
Database user name Database password
DatabaseuserfortheManagerservertousetologintothedatabase. Passwordforthedatabaseuser.
118
Configure Servicenet
Configure the Controller Ifyouareinstallingthecontroller,datahandler,orboth,providetheinformationbelow whenprompted. Box or Prompt Controller host Description Nameofthecontrollerhostmachine.Ifnecessary,youcanprovide thehostmachinesIPaddress. Important! Donotuselocalhosttoidentifythehostmachine. Controller port Controller JMX port My webMethods Server host HTTPportforthecontroller. JMXportforthedatahandlerandthesatellitestousetocommuni catewiththecontroller. NameofthemachinethathostsMywebMethodsServer.Ifneces sary,youcanprovidethehostmachinesIPaddress. Important! Donotuselocalhosttoidentifythehostmachine. My webMethods Server port Data handler host PortthatMywebMethodsServerusestocommunicatewiththe controller.ThedefaultportforMywebMethodsServeris8080. Nameofthedatahandlerhostmachine.Ifnecessary,youcanpro videthehostmachinesIPaddress. Important! Donotuselocalhosttoidentifythehostmachine. Data handler port Portforthedatahandlertousetocommunicatewiththecontrol ler.
Configure the Database Connections Whenprompted,providetheinformationbelow. Important! YoumustconfigurethedatabaseconnectionsduringinstallationorServicenet willnotbefullyfunctionalafterinstallation. IfyoualreadyhaveaProcessAuditLogdatabasecomponentthatyouareusingtostore ModelerorWorkflowprocessdata,provideconnectionparametersthatpointtotheexist ingdatabase.
119
Box or Prompt Database driver Database host Database port Database name (SQLServer)or SID(Oracle) Database user
Description Driverforthecontrollerordatahandlertousetocommunicate withthedatabase. Nameofthedatabasehostmachine.Ifnecessary,youcanprovide thehostmachinesIPaddress. Portforthecontrollerordatahandlertousetocommunicatewith thedatabase. Nameofthedatabasethatyouwanttocontainthedatabaseobjects forthedatabasecomponent.IfyouareusingaSQLServerdata base,thedatabasenamemustbeunique. Databaseuserforthecontrollerandthedatahandlertousetolog intothedatabasecomponent.Thedatabaseuserforeachdatabase componentmustbeunique. Passwordforthedatabaseuser. PortforServicenetclientstousetocommunicatewiththe Servicenetregistry.DisplayonServicenetdatabasecomponent panelonly.
Database user password Subnet port
Important! AllServicenetcomponentsarepreconfiguredtousethedefaultSubnet port.If youdistributeServicenetcomponentsovermultiplemachines,changingtheSubnet port fromthedefaultwillrequireyoutoperformmanualconfigurationtasksafterinstallation. However,ifyouintendtosetupmorethanoneServicenetenvironment,youmustusea differentsubnetportforeachenvironmenttopreventconflicts. ServicenetcreatesaJDBCconnectionpoolforeachdatabasecomponent.Ifyoulaterneed tomodifytheconnectionpools,seethewebMethodsDatabaseGuideforinstructions.
120
Configure Trading Networks Server

Whenprompted,providetheinformationbelow. Important! YoumustconfigurethedatabaseconnectionduringinstallationorTrading Networkswillnotstartafterinstallation. Box or Prompt Database driver Database URL Entry Drivertousetocommunicatewiththedatabase. URLforthedatabase,asfollows: URL Oracle
Default Port
1521
Oracle configured for RAC

jdbc:wm:oracle://main_OracleRAC_server_host: main_OracleRAC_server_port; ServiceName=Oracle_service_name; AlternateServers=(alternate_OracleRAC_server1_ho st: alternate_OracleRAC_server1_port, alternate_OracleRAC_server2_host: alternate_OracleRAC_server2_port,... alternate_OracleRAC_servern_host: alternate_OracleRAC_servern_port)
1521
SQL Server
1433
Sybase
jdbc:wm:sybase://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
5000
DB2 UDB
jdbc:wm:db2://host_or_IPaddress:port; databaseName=database_name; PackageName=package_name
50000
121
Box or Prompt
Entry 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
446
Note: AlternateIdmustmatchtheschemainwhichyou createdtheTradingNetworksdatabasetables. Database user name Database password DatabaseuserforTradingNetworksServertousetologintothe database. Passwordforthedatabaseuser.
Configure Workflow
Configure Workflow Client Whenprompted,providetheinformationbelowforWorkflowclient. Box or Prompt Host name Connection port Entry DNShostnameornetworknameofthemachinethathoststhecentral WorkflowServer. PortthecentralWorkflowServerusestocommunicatewithWorkflow clients. ThecentralWorkflowServerdefaultforconnectionportdependson thesystemonwhichthecentralWorkflowServerisinstalled.For Windows,thedefaultis6000.Foranyothersystem,thedefaultis5000. RMI registry port PortusedbythecentralWorkflowServerforRMI. ThecentralWorkflowServerdefaultforconnectionportdependson thesystemonwhichthecentralWorkflowServerisinstalled.For Windows,thedefaultis6001.Foranyothersystem,thedefaultis5001.
IfyoulaterneedtochangethispartoftheWorkflowclientconfiguration,seethe webMethodsWorkflowUsersGuideforinstructions.
122
Configure Workflow Server Whenprompted,providetheinformationbelowforWorkflowServer.Thevaluesyou providedependonwhetheryouwanttheWorkflowServeryouareinstallingtobethe centralWorkflowServerorasecondaryWorkflowServerthatwillhelphandlethe workload. IfyouwanttheWorkflowServertobethecentralWorkflowServer,providethevaluesas follows: Box or Prompt Host name Connection port Entry DNShostnameornetworknameofthemachineonwhichyouare installingthecentralWorkflowServer. PortforthecentralWorkflowServertousetocommunicatewith Workflowclients. OnWindowssystems,changetheConnection port to6000.Port5000is reservedbyWindows. RMI registry port PortforthecentralWorkflowServertouseforremotemethod invocation(RMI). OnWindowssystems,changetheRMI registry port to6001.Port5001is reservedbyWindows. Important! IfyouinstallmultiplecentralWorkflowServersonthesamemachine,the WorkflowServersmustusedifferentconnectionandRMIregistryports. IfyouwanttheWorkflowServertobeasecondaryWorkflowServer,providethevalues asfollows: Box or Prompt Host name Entry DNShostnameornetworknameofthemachinethathoststhecentral WorkflowServer.Thedefaultistheinstallationmachineshostname, soyoumustchangethedefaultnametothecentralWorkflowServers hostname. PortforthecentralWorkflowServertousetocommunicatewith Workflowclients. OnWindowssystems,changetheConnection port to6000.Port5000is reservedbyWindows. RMI registry port PortforthecentralWorkflowServertouseforRMI. OnWindowssystems,changetheRMI registry port to6001.Port5001is reservedbyWindows.
Connection port
123
IfyoulaterneedtochangethispartoftheWorkflowServerconfiguration,youcandoso usingtheWorkflowConfigurator.SeeCompletetheWorkflowInstallationonpage 213 forinstructions.
Review and Install

Reviewthelistofproductsyouhavechosentoinstall.Ifthelistiscorrect,pressENTER. Theinstallerinstallstheproductsandrelateditems.

Overwrite Using Console Mode

IfoneormoreofyourwebMethodsproductinstallationshasbeencorrupted,orifyou accidentallydeletedsomefilesfromaproductdirectory,youcanoverwritetheproducts usingthewebMethodsInstaller. Important! Onlyoverwriteproductsinthemostextremecases.Overwritingnotonly overwritestheproductinstallations,itoverwritesallrelatedfilesyouhavecreatedor customized. Iftheinstallationyouareoverwritingincludesprogramfilesthatarenotincludedinthe newversion,thosefilesremain(unused)intheinstallation. 1 2 3 4 ShutdownthewebMethodsproductsyouaregoingtooverwrite. Ifyouwanttosavefilesyouhavecreatedorcustomized,copythemtoadifferent directory. Ifyouwanttooverwritefromaninstallationscriptorimage,createthescriptor image. StartthewebMethodsInstallerbutaddthisparametertothestartcommand:
-overwriteInstall
Ifyouwanttouseaproxyserver,alsospecifytheparameterforthatoption.Ifyouare overwritingfromaninstallationscriptorimage,specifytheparameterforthatoption aswell.TheoptionsaredescribedinStarttheInstalleronpage 107. Important! Iferrorsoccurwhileaninstallationscriptisrunning,theinstallationfails.
124
Overwrite Using Console Mode
5 6
Ifyouarenotusinganinstallationscripttooverwrite,choosetheproductsto overwrite. Moveanyusercreatedorcustomizedfilesyoucopiedearlierbacktotheappropriate locationinthenewinstallation.
125
126
PART
IV
Database Component Installation

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
127
128
CHAPTER
Installing 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
129
CHAPTER 8 Installing the Database Components in Oracle
Overview
ThischapterexplainshowtoinstallwebMethodsdatabasecomponentsinOracle. Databasecomponentsareinstalledusingdifferentmethods;thesectionheadingsindicate whichdatabasecomponentsarecoveredineachsection. InstructionsforinstallingtheWorkflowdatabasecomponentautomaticallyviathe WorkflowConfiguratorareprovidedinCompletetheWorkflowInstallationon page 213.InstructionsforinstallingtheIntegrationServerRepositoryareprovidedinthe webMethodsIntegrationServerClusteringGuide.
Install the Cross-Reference, Docu ment History, IS Core Audit Log, Modeler Repository, Process Tracking Store, Reporting, Staging, and Trading Networks Database Components
Set Up Database Users
Askyourdatabaseadministratortosetupadatabaseuser,password,andpermissionsfor eachdatabasecomponent.Eachdatabaseusermustbeabletoselect,insert,update,and deleterowsfromthetablesinitsdatabasecomponent. Note: IfyouinstalledTradingNetworksServer,youmightalreadyhaveaskedyour databaseadministratortosetupadatabaseuser,password,andpermissionsforthe TradingNetworksdatabasecomponentbeforeinstallationsoyoucouldenterthe databaseuserandpasswordduringinstallation.
Download the Database Scripts

Youinstallthedatabasecomponentscoveredinthissectionusingdatabasescripts availablethroughthewebMethodsInstaller.Downloadthedatabasescriptsasfollows: 1 DownloadthewebMethodsInstallerfromthewebMethodsAdvantageWebsiteat http://advantage.webmethods.comtoamachineequippedwithanOracledatabase client. Starttheinstaller.SpecifytheinstallationdirectoryasthewebMethods6.5installation directory(bydefault,webMethods6). Inthecomponentselectionlist,gotoCommon Filesandchoosetodownloadthelatest versionofDatabase Scripts.
2 3
130
Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components
Install the Database Components

Installthedatabasecomponentsbyexecutingthescriptslistedbelowfromyourdatabase editor.ThescriptsarelocatedinthewebMethods_directory\common\db\scripts\create directory. Component CrossReference DocumentHistory ISCoreAuditLog ModelerRepository ProcessTracking Store Reporting Staging TradingNetworks Script create_xref_65_database.sql create_idr_65_database.sql create_iscoreaudit_65_database.sql create_RepoV3_65_database.sql create_prt_65_database.sql create_reporting_65_database.sql,populate_reporting_ 65_database.sql create_staging_65_database.sql create_TN_65_database.sql,create_archive_TN_65_database.sql
GotoChapter 12,IdentifyingDatabasesforUsebyProducts.
Youcancreatedatabaseusersaspartoftheinstallationprocessdescribedinthissection oryoucanhaveyourdatabaseadministratorsetthemup. Ifyouwantyourdatabaseadministratortosetupthedatabaseusers,askthedatabase administratortocreateonedatabaseuserforeachdatabasecomponent.Assignthe databaseuserthepermissionslistedintheora_cmn_c_ddl_user.sqlfileinthe webMethods_directory\common\db\scripts\oracle\code\common\createdirectory.If theOracleinstanceinwhichyouwanttoinstallisconfiguredtoallowremote administrativelogin,thedatabaseadministratorcancreatethedatabaseusersfroma remotemachine.IftheOracleinstanceisnotconfiguredtoallowremoteadministrative
131
login,thedatabaseadministratormustcreatethedatabaseusersonthemachinethathosts theOracleinstance. Note: IfyouinstalledManagerserver,youmightalreadyhaveaskedyourdatabase administratortosetupadatabaseuser,password,andpermissionsfortheManager serverdatabasecomponentbeforeinstallationsoyoucouldenterthedatabaseuserand passwordduringinstallation.

Youinstallthedatabasecomponentscoveredinthissectionusingdatabasescriptsanda programcalledthewebMethodsDatabaseInstallerthatareavailablethroughthe webMethodsInstaller.DownloadthescriptsandwebMethodsDatabaseInstalleras follows: 1 DownloadthewebMethodsInstallerfromthewebMethodsAdvantageWebsiteat http://advantage.webmethods.comtoamachineequippedwithanOracledatabase client. Starttheinstaller.SpecifytheinstallationdirectoryasthewebMethods6.5installation directory(bydefault,webMethods6). Inthecomponentselectionlist,gotoCommon FilesandchoosetoinstallDatabase Scripts 6.5.1.7.
2 3
Set the Database Connection Properties

1 2 3 OntheOracledatabaseclientmachine,openacommandwindowandgotothe webMethods_directory\common\db\scripts\Oracledirectory. StartthewebMethodsDatabaseInstallerbyrunningtheoracle.{bat|sh}program. ChooseView/modify database connection properties fileandsetthesepropertiesforeach databasecomponentyouaregoingtoinstall:
set set set set database_component_DBHOST=database_host database_component_SID=database_SID database_component_DBPORT=database_port database_component_USER=database_user
Saveandclosethefile.
132
Create the Tablespaces in Oracle

IfyouareinstallinginOracle,createthetablespaceslistedbelowforthedatabase components.Ifyouinstallmultipledatabasecomponentsonthesamedatabase,theycan usethesametablespaces. Tablespace WEBMDATA_LGA WEBMDATA_MDA WEBMDATA_SMA WEBMINDX_LGA WEBMINDX_MDA WEBMINDX_SMA Description Largeextentsforlargetables Mediumextentsformediumtables Smallextentsforsmalltables Largeextentsforlargeindexes Mediumextentsformediumindexes Smallextentsforsmallindexes Approximate Extent Size 5MB 1MB 128KB 5MB 1MB 128KB
Ifyouhaveahighdemandproductionenvironment,youshouldcreatethetablespaces manuallysoyoucanconfigurethetablespacesetupforoptimalI/Operformance.For example,dedicatingadiskcontrolleranddrivetodataandaseparatecontrolleranddrive toindexmightresultinbetterperformancethanifyouusethesamecontrollerforboth. BelowisasamplescriptforcreatingtheWEBMDATA_LGAtablespace.

REM ********** TABLESPACE FOR WEBMDATA_LGA ********** CREATE TABLESPACE WEBMDATA_LGA DATAFILE '%ORACLE_DATA_DIR1%\webmdata_lga_01.dbf' SIZE 1000M AUTOEXTEND ON NEXT 10 M MAXSIZE 10000 M EXTENT MANAGEMENT LOCAL UNIFORM SIZE 5M;
Ifyouhaveadevelopmentorlowdemandenvironment,youcanhavethedatabase installercreatethetablespacesautomaticallyusingthequicksetupoption,butbeaware thatthisconfigurationmightnotproduceoptimalperformance.Tocreatetablespaces automatically,dothefollowing: 1 2 3 Inthedatabaseinstaller,chooseInstall webMethods tablespaces,thenchoosethe databasecomponentthatwillusethosetablespaces(forexample,Analysis 6.5.1). ChoosetheOracleversionyouareusing.Theinstallersuppliesdefaultdirectoriesfor thedataandindexfiles;youcanacceptthemoridentifyotherdirectoriestouse. Whenprompted,entertheSYSpasswordforserverdatabase_host.Theinstallercreates thetablespacesbasedonthedatabaseconnectionpropertiesyousetearlier.
133

YoucaninstallthedatabasecomponentsautomaticallyusingthewebMethodsDatabase Installeroryoucaninstallthemmanually.Thedatabaseinstallercreatestheuserand databaseobjectsforeachdatabasecomponent.
Before You Begin

IfyouaregoingtoinstalltheArchivedatabasecomponentonadifferentdatabaseserver thantheProcessAuditLogandISCoreAuditLogdatabasecomponents,createaDBlink namefortheArchivedatabasecomponenttousetolinktoeachdatabasecomponentfrom whichyouwanttoarchive.IftheProcessAuditLogandISCoreAuditLogdatabase componentsareonthesamedatabaseserver,theArchivedatabasecomponentcanusethe sameDBLinktoconnecttoboth.
Install a Database Component Using the Database Installer

1 2 ChooseInstall/reinstall a database component,thenchoosethedatabasecomponentto install(forexample,Analysis 6.5.1). Thisstepdependsonwhetheryourdatabaseadministratorcreatedthedatabaseusers forthedatabasecomponents. Ifthedatabaseadministratordidnotcreatethedatabaseusers,chooseCreate new user database_user.Whenprompted,enterthepasswordforSYS. Ifyourdatabaseadministratordidcreatethedatabaseuesrs,chooseUse existing user database_user. 3 Theinstallerpromptsfortheseproperties: Property PROCESSAUDIT_DBLINK Entry IfyouwanttoarchivefromtheProcessAuditLog, andtheArchiveandProcessAuditLogdatabase componentsareondifferentdatabaseservers,enter thenameoftheDBlinkyoucreatedinBeforeYou Beginonpage 134.Ifyoudonotwanttoarchivefrom theProcessAuditLogdatabasecomponent,orthe databasecomponentsareonthesamedatabaseserver, pressEnter. IfyouwanttoarchivefromtheISCoreAuditLog,and theArchiveandISCoreAuditLogdatabase componentsareondifferentdatabaseservers,enter thenameoftheDBlinkyoucreatedinBeforeYou Beginonpage 134.Ifyoudonotwanttoarchivefrom theISCoreAuditLogdatabasecomponent,orthe databasecomponentsareonthesamedatabaseserver, pressEnter.
ISCOREAUDIT_DBLINK
134
Property PROCESS_SCHEMA
Entry IfyouwanttoarchivefromtheProcessAuditLog, enterthedatabaseuser(Oracle)ordatabasename (SQLServer)fortheProcessAuditLogdatabase component.Otherwise,pressEnter. IfyouwanttoarchivefromtheISCoreAuditLog, enterthedatabaseuser(Oracle)ordatabasename (SQLServer)fortheISCoreAuditLogdatabase component.Otherwise,pressEnter.
ISCORE_SCHEMA
Install a Database Component Manually

1 2 OpenacommandwindowandgotothewebMethods_directory\common\ db\scripts\oracledirectory. SettheenvironmentvariableDBCALL_INPUT_STRINGbyrunningthecommands 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
Parameter
database_component_code
Entry Codeforthedatabasecomponent,asfollows: Database Component Analysis Archive Managerserver ProcessAuditLog ProcessTracker Servicenet Code ANL ARC MNS PRA PTR SNT
database_user database_user_password
Schemausername. Schemapassword.
135
Parameter
large_data_tablespace medium_data_tablespace small_data_tablespace large_index_tablespace medium_index_tablespace small_index_tablespace temp_tablespace mail_host email_recipient
Entry Tablespaceforlarge,medium,andsmalltables.
Tablespaceforlarge,medium,andsmallindexes.
Tablespacefortemporarystorage. Mailhostforoperationnoticesanddefaultemail addresstoreceivethem.
Forexample,ifyouwanttoinstalltheProcessTrackerdatabasecomponentona Windowssystem,youwouldrunthesecommands:
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 myemail@mycompany.com
Ifthedatabaseadministratordidnotcreatethedatabaseuserforthisdatabase component,createthedatabaseuserbyrunningthiscommand:
sqlplus sys@service_name as sysdba @code/common/create/ora_cmn_c_ddl_user.sql %DBCALL_INPUT_STRING%
Installshareddatabaseobjectsbyrunningthecommandsbelow.Theseobjects,which includefunctionalitylikemetadatainformationanddatapurge,provideafoundation forusebyallproductdatabasecomponentsintheschema. Important! Performthissteponlyonceperschema.

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%
136
Installthedatabasecomponentbyrunningthiscommand:
sqlplus database_user@service_name @code/create_database_component_ 6-5_ora.sql %DBCALL_INPUT_STRING%

1 Forsecurityreasons,ifyouinstalledtheAnalysis,Archive,Managerserver,Process AuditLog,orProcessTrackerdatabasecomponent,removethedatabaseuser passwordfromthedatabaseconnectionpropertiesfile,asfollows: a b IfthewebMethodsDatabaseInstallerisnotalreadystarted,starttheinstalleron theOracledatabaseclientmachinebyrunningtheoracle.{bat|sh}program. ChooseView/modify database connection properties fileandremovethepassword fromthepropertyshownbelow:
set database_component_USER_PWD=
c 2
IfyouinstalledtheArchive,ManagerServer,orProcessAuditLogdatabase component,defineaJDBCconnectionpoolforIntegrationServertouseto communicatewiththedatabasecomponent.Forinstructions,seeIdentifythe DatabasesthatContaintheCrossReference,DocumentHistory,ISCoreAuditLog, ProcessAuditLog,Reporting,andStagingDatabaseComponentsonpage 170. Note: Manager,Optimize,andServicenetautomaticallycreateJDBCconnectionpools tousetocommunicatewiththeAnalysis,ProcessAuditLog,andProcessTracker databasecomponentswhenyoustarttheManager/OptimizeandServicenet controllers.Theinformationrequiredtocreatetheconnectionpoolswassupplied duringproductinstallation. YoumightalsohavealreadydefinedaconnectionpoolforManagerserverduring productinstallation.
IfyouinstalledtheArchivedatabasecomponent,usetheGRANTcommandtogive theArchivedatabaseuserpermissiontoselectanddeletefromtheProcessAuditLog databasecomponent,theISCoreAuditLogdatabasecomponent,orboth,depending onthedatayouwanttoarchive.
137
Install the My webMethods Server Database Component

YoucaninstalltheMywebMethodsServerdatabasecomponentmanuallyusingoneof thecommandsdescribedinthissection.Thecommandyouusedependsonwhetheryou arerunningthecommandfromamachinethathostsMywebMethodsServer,Access,or Portal,ornoneofthose.Ifyouwanttorunthecommandtoinstallfromamachinethat doesnothostanyofthoseproducts,themachinemustbeequippedwithanOracle databaseclient. Note: YoucanusethePortalServerConfiguratortoautomaticallyinstalltheMy webMethodsServerdatabasecomponent.Forinstructions,seeCompletetheAccess,My webMethodsServer,orPortalInstallationonpage 183. YoucaninstalltheMywebMethodsServerdatabasecomponentineitheroftwoways: Ifyouhaveadministratoraccesstothedatabaseserverinwhichyouwanttoinstall thedatabasecomponent,youcanuseacommandtocreateatablespaceanddatabase userandinstallthedatabasecomponentinthenewtablespace. Ifyoudonothaveadministratoraccess,youcanaskyourdatabaseadministratorto createanemptytablespaceandadatabaseuser,andthenuseacommandtoinstall thedatabasecomponentinthetablespace.ThedatabaseusermusthaveCONNECT, RESOURCE,CREATEVIEW,andGLOBALQUERYREWRITEpermissions.
Before You Begin

1 2 SettheNLS_LENGTH_SEMANTICSinitializationparametertoBYTE. PreparetorunacommandtoinstalltheMywebMethodsServerdatabasecomponent byfollowingtheappropriatestepsbelow. To run the command from... MywebMethodsServer, Access,orPortalhost machine Othermachine Follow these steps... OpenacommandwindowandgototheMyweb MethodsServer,Access,orPortal_directory\bin\db\ scripts\oracledirectory. 1 OntheMywebMethodsServer,Access,orPortal hostmachine,gototheMywebMethodsServer, Access,orPortal_directory\bin\db\scriptsdirectory. CopytheoracledirectorytotheOracledatabase clientmachine.
138
Create the Tablespace and Database User and Install the Database Component
TocreateatablespaceanddatabaseuserandinstalltheMywebMethodsServerdatabase componentinthenewtablespace,runthiscommand:
{dbcreate.{bat|sh} | dbcreate_sqlplus.{bat|sh}} database_server_host:database_server_port SID administrator_user administrator_password database_user database_password tablespace y
Parameter
{dbcreate.{bat|sh} | dbcreate_sqlplus. {bat|sh}}
Entry IfyouarerunningthecommandfromtheMywebMethods Server,Access,orPortalhostmachine,enterdbcre ate.{bat|sh}.Ifyouarerunningthecommandfroma machinethatdoesnothostMywebMethodsServer, Access,orPortal,enterdbcreate_sqlplus.{bat|sh). NameorIPaddressofthemachinethathoststheOracle databaseserver.Donotuselocalhosttoidentifythehost. Portthedatabaseserverusestocommunicate.Thedefault portforOracleis1521. SIDfortheOracleinstanceondatabase_server_hostinwhich toinstallthedatabasecomponent. Administratoruserforthedatabaseserver. Administratorpasswordforthedatabaseserver. DatabaseuserforMywebMethodsServer,Access,orPor taltousetocommunicatewiththedatabaseserver.The databaseusermustbeuniqueforthedatabaseserver. Passwordforthedatabaseuser. Nameofthetablespaceinwhichtoinstallthedatabase component. Tellsthecommandtocreateatablespaceanddatabaseuser andinstallthedatabasecomponentinthenewtablespace.
database_server_host
database_server_port
SID
administrator_user administrator_ password database_user
database_user_ password tablespace
Forexample,thefollowingcommandcreatesthemywebmserver tablespaceinthe mywebmserver_dbOracleinstanceontheoraserverdatabaseserver,createsthe mywebmserveruserdatabaseuser,andinstallstheMywebMethodsServerdatabase componentinthemywebmserver tablespace:

dbcreate.bat oraserver:1521 mywebmserver_db sys syspassword mywebmserveruser mywebmserverpassword mywebmserver y
139
Install the Database Component Using an Existing Tablespace and Database User
ToinstalltheMywebMethodsServerdatabasecomponentinanexistingtablespaceusing anexistingdatabaseuser,runthiscommand:
{dbcreate.{bat|sh} | dbcreate_sqlplus.{bat|sh}} database_server_host:database_server_port SID administrator_user administrator_password database_user database_password tablespace n
Parameter
{dbcreate.{bat|sh} | dbcreate_sqlplus. {bat|sh}}
Entry IfyouarerunningthecommandfromtheMywebMethods Server,Access,orPortalhostmachine,enterdbcre ate.{bat|sh}.Ifyouarerunningthecommandfroma machinethatdoesnothostMywebMethodsServer, Access,orPortal,enterdbcreate_sqlplus.{bat|sh). NameorIPaddressofthemachinethathoststheOracle databaseserver.Donotuselocalhosttoidentifythehost. Portthedatabaseserverusestocommunicate.Thedefault portforOracleis1521. SIDfortheOracleinstanceondatabase_server_hostinwhich toinstallthedatabasecomponent. Enterthesamevalueyouenterfordatabase_user. Enterthesamevalueyouenterfor database_user_password. DatabaseuserforMywebMethodsServer,Access,orPor taltousetocommunicatewiththedatabase. Passwordforthedatabaseuser. Nameofthetablespaceinwhichtoinstallthedatabase component. Tellsthecommandtoinstallthedatabasecomponentinan existingtablespaceusinganexistingdatabaseuser.
SID
database_user_ password tablespace
Forexample,thefollowingcommandinstallstheMywebMethodsServerdatabase componentintheexistingtablespacemywebmserverontheoraserverdatabaseserver, usingtheexistingdatabaseusermywebmserveruser:

dbcreate.bat oraserver:1521 mywebmserver_db mywebmserveruser mywebmserverpassword mywebmserveruser mywebmserverpassword portal n
140
Reinstall the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet Database Component
IfyouneedtostartoverbyclearingoutalldatafromtheAnalysis,Archive,ProcessAudit Log,ProcessTracker,orServicenetdatabasecomponent,youcanreinstallthedatabase componentusingthewebMethodsDatabaseInstaller. Important! Donotreinstalladatabasecomponentifyouhaveinstalledmultipledatabase componentsinasingleOracleschema.Doingsowoulddropalldatabasecomponents fromtheschema. 1 OnthemachinethathoststhedatabasescriptsandwebMethodsDatabaseInstaller, openacommandwindowandgotothewebMethods_directory\common\ db\scripts\oracledirectory. StartthewebMethodsDatabaseInstallerbyrunningtheoracle.{bat|sh}program. ChooseInstall/reinstall a database component,thenchoosethedatabasecomponentto reinstall(forexample,Process Tracker 6.5.1).
2 3
141
142
CHAPTER
Installing the Database Components in SQL Server

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, Reporting, Staging, and Trading Networks Database Components . . 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
143
CHAPTER 9 Installing the Database Components in SQL Server
Overview
ThischapterexplainshowtoinstallwebMethodsdatabasecomponentsinSQLServer. Databasecomponentsareinstalledusingdifferentmethods;thesectionheadingsindicate whichdatabasecomponentsarecoveredineachsection. InstructionsforinstallingtheWorkflowdatabasecomponentautomaticallyviathe WorkflowConfiguratorareprovidedinCompletetheWorkflowInstallationon page 213.InstructionsforinstallingtheIntegrationServerRepositoryareprovidedinthe webMethodsIntegrationServerClusteringGuide.

Youinstallthedatabasecomponentscoveredinthissectionusingdatabasescripts availablethroughthewebMethodsInstaller.Downloadthedatabasescriptsasfollows: 1 DownloadthewebMethodsInstallerfromthewebMethodsAdvantageWebsiteat http://advantage.webmethods.comtoamachineequippedwithaSQLServer databaseclient. Starttheinstaller.SpecifytheinstallationdirectoryasthewebMethods6.5installation directory(bydefault,webMethods6). Inthecomponentselectionlist,gotoCommon Filesandchoosetodownloadthelatest versionofDatabase Scripts.
2 3
144

Installthedatabasecomponentsbyexecutingthescriptslistedbelowfromyourdatabase editor.ThescriptsarelocatedinthewebMethods_directory\common\db\scripts\create directory. Component CrossReference DocumentHistory ISCoreAuditLog Script create_xref_65_database.sql create_idr_65_database.sql create_iscoreaudit_65_database.sql Important! Youmightseemaximumkeylengthwarningsforthe IDX_SESS_SVRID,IDX_ERR_SVRID,IDX_TXIN_SVRID,and IDX_TXOUT_SVRIDindices.IfyourIntegrationServerIDswill notexceed900bytes(300multibytecharacters),youcanignore thiswarning.IfyourIntegrationServerIDswillexceed900 bytes,removetheindices. ModelerRepository ProcessTracking Store Reporting Staging TradingNetworks create_RepoV3_65_database.sql create_prt_65_database.sql create_reporting_65_database.sql,populate_reporting_ 65_database.sql create_staging_65_database.sql create_TN_65_database.sql,create_archive_TN_65_database.sql
Youcancreatedatabasesanddatabaseusersaspartoftheinstallationprocessdescribed inthissectionoryoucanhaveyourdatabaseadministratorsetthemup. Ifyouwantyourdatabaseadministratortosetupthedatabasesanddatabaseusers,ask thedatabaseadministratortocreateonedatabaseanddatabaseuserforeachdatabase component.Assignthedatabaseuserthepermissionslistedinthe
145
mss_cmn_c_ddl_grant.sqlfileinthewebMethods_directory\common\db\scripts\mssql\ code\common\createdirectory. Note: IfyouinstalledManagerserver,youmightalreadyhaveaskedyourdatabase administratortosetupadatabaseuser,password,andpermissionsfortheManager serverdatabasecomponentbeforeinstallationsoyoucouldenterthedatabaseuserand passwordduringinstallation.

Youinstallthedatabasecomponentscoveredinthissectionusingdatabasescriptsanda programcalledthewebMethodsDatabaseInstallerthatareavailablethroughthe webMethodsInstaller.DownloadthescriptsandwebMethodsDatabaseInstalleras follows: 1 2 3 DownloadthewebMethodsInstallerfromthewebMethodsAdvantageWebsiteat http://advantage.webmethods.comtoamachineequippedwithWindows. Starttheinstaller.SpecifytheinstallationdirectoryasthewebMethods6.5installation directory(bydefault,webMethods6). Inthecomponentselectionlist,gotoCommon FilesandchoosetoinstallDatabase Scripts 6.5.1.7.

1 2 3 OntheWindowsmachine,openacommandwindowandgotothe webMethods_directory\common\db\scripts\mssqldirectory. StartthewebMethodsDatabaseInstallerbyrunningthemssql.batprogram. ChooseView/modify database connection properties fileandsetthesepropertiesforeach databasecomponentyouaregoingtoinstall:
set set set set @database_component_DBHOST='database_host' @database_component_DBNAME='database_name' @database_component_DBUSER='database_user' @database_component_DBUSER_PWD='database_user_password'
146

YoucaninstallthedatabasecomponentsautomaticallyusingthewebMethodsDatabase Installeroryoucaninstallthemmanually.Thedatabaseinstallercreatestheuserand databaseobjectsforeachdatabasecomponent.

1 2 ChooseInstall/reinstall a database component,thenchoosethedatabasecomponentto install(forexample,Analysis 6.5.1). Whenprompted,enterthesystemadministrator(SA)passwordforserver database_host.ChooseComponent objects do not exist - proceed with creation for new database.
Install a Database Component in SQL Server Manually

1 2 OpenacommandwindowandgotothewebMethods_directory\common\ db\scripts\mssqldirectory. Ifthedatabaseadministratordidnotcreatethedatabaseanddatabaseuserforthis databasecomponent,createthedatabaseanddatabaseuserbyrunningthe commandsbelow.Thedatabasecomponentcodesareasfollows: Database Component Analysis Managerserver ProcessTracker Code ANL MNS PTR Database Component Archive ProcessAuditLog Servicenet Code ARC PRA SNT
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.s ql 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
Installshareddatabaseobjectsbyrunningthecommandsbelow.Theseobjects,which includefunctionalitylikemetadatainformationanddatapurge,provideafoundation forusebysharedbyallproductdatabasecomponentsinthedatabase. Important! Performthissteponlyonceperdatabase.

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
147
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
Installthedatabasecomponentbyrunningthiscommand:
code\osql -U sa -P sa_password -S database_server -d database -n -b -i code\create_database_component_6-5_mss.sql
Forexample,ifyouwanttoinstalltheProcessTrackerdatabasecomponentonaWindows system,youwouldrunthesecommands,wheretheSApasswordistestandthedatabase nameisprocesstracker:

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

1 Forsecurityreasons,ifyouinstalledtheAnalysis,Archive,Managerserver,Process AuditLog,orProcessTrackerdatabasecomponent,removethedatabaseuser passwordfromthedatabaseconnectionpropertiesfile,asfollows: a b IfthewebMethodsDatabaseInstallerisnotalreadystarted,starttheinstalleron theWindowsmachinebyrunningthemssql.batprogram. ChooseView/modify database connection properties fileandremovethepassword fromthepropertyshownbelow:
set @database_component_DBUSER_PWD=''
148
IfyouinstalledtheArchivedatabasecomponent,dothefollowing: a UsetheMonitorservicepub.monitor.archive:setOperationParametersto linktheArchivedatabasecomponenttotheProcessAuditLogdatabase component,theISCoreAuditLogdatabasecomponent,orboth,dependingon thedatayouwanttoarchive.Forinstructionsonusingtheservice,seeMonitor Servicepub.monitor.archive:setOperationParametersonpage 264;setthe PROCESSAUDIT_DBLINK,ISCOREAUDIT_DBLINK,PROCESS_SCHEMA,and ISCORE_SCHEMAparametersontheservice. UsetheGRANTcommandtogivetheArchivedatabaseuserpermissiontoselect anddeletefromtheProcessAuditLogdatabasecomponent,theISCoreAudit Logdatabasecomponent,orboth,dependingonthedatayouwanttoarchive.

YoucaninstalltheMywebMethodsServerdatabasecomponentmanuallyusingoneof thecommandsdescribedinthissection.Thecommandyouusedependsonwhetheryou arerunningthecommandfromamachinethathostsMywebMethodsServer,Access,or Portal,ornoneofthose.Ifyouwanttorunthecommandfromamachinethatdoesnot hostanyofthoseproducts,themachinemustbeequippedwiththeOSQLutility. Note: YoucanusethePortalServerConfiguratortoautomaticallyinstalltheMy webMethodsServerdatabasecomponent.Forinstructions,seeCompletetheAccess,My webMethodsServer,orPortalInstallationonpage 183. YoucaninstalltheMywebMethodsServerdatabasecomponentineitheroftwoways: Ifyouhaveadministratoraccesstothedatabaseserverinwhichyouwanttoinstall thedatabasecomponent,youcanusethecommandtocreateadatabaseanddatabase userandinstallthedatabasecomponentinthenewdatabase.
149
Ifyoudonothaveadministratoraccess,youcanaskyourdatabaseadministratorto createanemptydatabaseandadatabaseuser,andthenusethecommandtoinstall thedatabasecomponentinthedatabase.Thedatabaseusermustbegrantedthe db_ownerandpublicrolesonthedatabaseinadditiontostandarddatabase permissions.
Before You Begin

Followtheappropriatestepsbelow. To run the command from... Portalhostmachine Follow these steps... OpenacommandwindowandgototheMywebMethods Server,Access,orPortal_directory\bin\db\scripts\mssql directory. 1 OntheMywebMethodsServer,Access,orPortalhost machine,gototheMywebMethodsServer,Access,or Portal_directory\bin\db\scriptsdirectory. Copythemssqldirectorytothemachineequipped withtheOSSQLutility.
Othermachine
Create the Database and Database User and Install the Database Component
TocreateadatabaseanddatabaseuserandinstalltheMywebMethodsServerdatabase componentinthenewdatabase,runthiscommand:
{dbcreate.bat | dbcreate_osql.bat} database_server_host:database_server_port database administrator_user administrator_user_password database_user database_user_password y
Parameter
{dbcreate.bat | dbcreate_osql.bat}
Entry IfyouarerunningthecommandfromtheMywebMethods Server,Access,orPortalhostmachine,enterdbcreate.bat.If youarerunningthecommandfromamachinethatdoesnot hostMywebMethodsServer,Access,orPortal,enter dbcreate_osql.bat. NameorIPaddressofthemachinethathoststheSQLServer databaseserver.Donotuselocalhosttoidentifythehost. Portthedatabaseserverusestocommunicate.Thedefault portforSQLServeris1433.
database_server_ host database_server_ port
150
Parameter
database
Entry Nameofthedatabaseinwhichtoinstallthedatabasecompo nent. Administratoruserforthedatabaseserver. Administratorpasswordforthedatabaseserver. DatabaseuserforMywebMethodsServer,Access,orPortal tousetocommunicatewiththedatabase.Thedatabaseuser mustbeuniqueforthedatabaseserver. Passwordforthedatabaseuser. Tellsthecommandtocreateadatabaseanddatabaseuserand installthedatabasecomponentinthenewdatabase.
database_user_ password y
Forexample,thefollowingcommandcreatesthemywebmserverdbdatabaseonthe sqlserverdatabaseserver,createsthemywebmserveruserdatabaseuser,andinstallsthe MywebMethodsServerdatabasecomponentinthemywebmserverdbdatabase:

dbcreate.bat sqlserver:1433 mywebmserverdb sa password mywebmserveruser mywebmserverpassword y
Install the Database Component Using an Existing Database and Database User
ToinstalltheMywebMethodsServerdatabasecomponentinanexistingdatabaseusing anexistingdatabaseuser,runthiscommand:
{dbcreate.bat | dbcreate_osql.bat} database_server_host:database_server_port database administrator_user administrator_user_password database_user database_user_password n
Parameter
{dbcreate.bat | dbcreate_osql.bat}
Entry IfyouarerunningthecommandfromtheMywebMethods Server,Access,orPortalhostmachine,enterdbcreate.bat.If youarerunningthecommandfromamachinethatdoesnot hostMywebMethodsServer,Access,orPortal,enter dbcreate_osql.bat. NameorIPaddressofthemachinethathoststheSQLServer databaseserver.Donotuselocalhosttoidentifythehost. Portthedatabaseserverusestocommunicate.Thedefaultport forSQLServeris1433.
database_server_ host database_server_ port
151
Parameter
database
Entry Nameofthedatabaseinwhichtoinstallthedatabasecompo nent. Enterthesamevalueyouenterfordatabase_user. Enterthesamevalueyouenterfordatabase_user_password. DatabaseuserforMywebMethodsServer,Access,orPortalto usetocommunicatewiththedatabase. Passwordforthedatabaseuser. Tellsthecommandtoinstallthedatabasecomponentinan existingdatabaseusinganexistingdatabaseuser.
database_user_ password n
Forexample,thefollowingcommandinstallstheMywebMethodsServerdatabase componentintheexistingdatabasemywebmserveronthesqlserverdatabaseserver, usingtheexistingdatabaseusermywebmserveruser:

dbcreate.bat sqlserverhost:1421 mywebmserver mywebmserveruser mywebmserverpassword mywebmserveruser mywebmserverpassword n
IfyouneedtostartoverbyclearingoutalldatafromtheAnalysis,Archive,ProcessAudit Log,ProcessTracker,orServicenetdatabasecomponent,andyouinstalledthedatabase component,youcanreinstallthedatabasecomponentusingthewebMethodsDatabase Installer. 1 OnthemachinethathoststhedatabasescriptsandwebMethodsDatabaseInstaller, openacommandwindowandgotothewebMethods_directory\common\ db\scripts\mssqldirectory. StartthewebMethodsDatabaseInstallerbyrunningthemssql.batprogram. ChooseInstall/reinstall a database component,thenchoosethedatabasecomponentto reinstall(forexample,Process Tracker 6.5.1).
2 3
152
CHAPTER
10
Installing the Database Components in DB2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, Reporting, Staging, and Trading Networks Database Components . . 154 Install the Reporting and Staging Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Install the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
153
CHAPTER 10 Installing the Database Components in DB2
Overview
ThischapterexplainshowtoinstallwebMethodsdatabasecomponentsinDB2.Database componentsareinstalledusingdifferentmethods;thesectionheadingsindicatewhich databasecomponentsarecoveredineachsection. InstructionsforinstallingtheWorkflowdatabasecomponentautomaticallyviathe WorkflowConfiguratorareprovidedinCompletetheWorkflowInstallationon page 213.InstructionsforinstallingtheIntegrationServerRepositoryareprovidedinthe webMethodsIntegrationServerClusteringGuide.

Youinstallthedatabasecomponentscoveredinthissectionusingdatabasescripts availablethroughthewebMethodsInstaller.Downloadthedatabasescriptsasfollows: 1 2 3 DownloadthewebMethodsInstallerfromthewebMethodsAdvantageWebsiteat http://advantage.webmethods.comtoamachineequippedwithaDB2databaseclient. Starttheinstaller.SpecifytheinstallationdirectoryasthewebMethods6.5installation directory(bydefault,webMethods6). Inthecomponentselectionlist,gotoCommon Filesandchoosetodownloadthelatest versionofDatabase Scripts.
154
Install the Reporting and Staging Database Components

Install the Reporting and Staging Database Components

Askyourdatabaseadministratortosetupthedatabaseuser,password,andpermissions foreachdatabasecomponent.Eachdatabaseusermustbeabletoselect,insert,update, anddeleterowsfromthetablesinitsdatabasecomponent.

Youinstallthedatabasecomponentscoveredinthissectionusingdatabasescriptsanda programcalledthewebMethodsDatabaseInstaller.Bothareavailablethroughthe webMethodsInstaller.DownloadthescriptsandwebMethodsDatabaseInstalleras follows:. 1 2 DownloadthewebMethodsInstallerfromthewebMethodsAdvantageWebsiteat http://advantage.webmethods.comtothemachinethathoststheDB2databaseserver. Starttheinstaller.SpecifytheinstallationdirectoryasthewebMethods6.5installation directory(bydefault,webMethods6).
155
Inthecomponentselectionlist,gotoCommon FilesandchoosetoinstallDatabase Scripts 6.5.1.7.

1 OntheDB2databaseserverhostmachine,gotothewebMethods_directory\common\ db\scripts\db2directoryandopenthedb2_env_properties.{bat|sh}fileinatext editor. Edittheseconnectionpropertiesforeachdatabasecomponentyouaregoingtoinstall:
set database_component_DB=database_name set database_component_USR=database_user set database_component_PWD=database_user_password

GotothewebMethods_directory\common\db\scripts\createdirectoryandinstallthe databasecomponentsasfollows: To install this database component... Reporting Staging Execute this script... create_reporting_65_RDBMS.sql create_staging_65_RDBMS.sql

Forsecurityreasons,removethedatabaseuserpasswordfromthe db2_env_properties.{bat|sh}databaseconnectionpropertiesfile.
156
Install the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components

Youinstallthedatabasecomponentscoveredinthissectionusingdatabasescriptsanda programcalledthewebMethodsDatabaseInstaller.Bothareavailablethroughthe webMethodsInstaller.Downloadthescriptsasfollows: 1 2 3 DownloadthewebMethodsInstallerfromthewebMethodsAdvantageWebsiteat http://advantage.webmethods.comtotheDB2databaseserverhostmachine. Starttheinstaller.SpecifytheinstallationdirectoryasthewebMethods6.5installation directory(bydefault,webMethods6). Inthecomponentselectionlist,gotoCommon FilesandchoosetoinstallDatabase Scripts 6.5.1.7.

1 2 3 OntheDB2databaseserverhostmachine,gotothewebMethods_directory\common\ db\scripts\db2directory. StartthewebMethodsDatabaseInstallerbyrunningthiscommand: ibmDB2.{bat|sh} ChooseView/Modify database connection properties fileandsetthesepropertiesforeach databasecomponentyouaregoingtoinstall:
set set set set set database_component_INSTANCE=database_instance database_component_DB={local_alias | dbase_name} database_component_SCHEMA=database_schema database_component_USER=operating_system_user_name database_component_USER_PWD=operating_system_password
157

YoucaninstallthedatabasecomponentsautomaticallyusingthewebMethodsDatabase Installeroryoucaninstallthemmanually.Thedatabaseinstallercreatesthedatabase objectsforeachdatabasecomponent.

ChooseInstall/reinstall a database component,thenchoosethedatabasecomponenttoinstall (forexample,Analysis 6.5.1).
Install a Database Component in Oracle Manually

OpenacommandwindowandgotothewebMethods_directory\common\db\scripts\db2 directory.Runthescriptsintheorderindicatedbelow. Database Component Analysis Script 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_constraints_table.db2 code/databasemanagement/cre ate/db_mgmt_modify_fk_constraint.db2 code/databasemanagement/cre ate/db_mgmt_modify_fk_constraints_table.db2 code/databasemanagement/cre ate/db_mgmt_modify_fk_constraints_all.db2 code/datamanagement/create/data_mgmt_purge_data.db2
158
Database Component ProcessTracker
Script 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_constraints_table.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_table.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
159
Database Component Archive
Script code/processaudit/create/metadata_tables.sql code/processaudit/create/runtime_tables.sql code/processaudit/create/processrecent_table.sql ../create/create_iscoreaudit_65_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

1 Forsecurityreasons,removethedatabaseuserpasswordfromthedatabase connectionpropertiesfile,asfollows: a IfthewebMethodsDatabaseInstallerisnotalreadystarted,startitbyrunning thiscommand:
ibmDB2.{bat|sh}
ChooseView/Modify database connection properties fileandandremovethepassword fromthepropertyshownbelow:

set database_component_USER_PWD=
c 2
IfyouinstalledtheArchivedatabasecomponent,usetheGRANTcommandtogive theArchivedatabaseuserpermissiontoselectanddeletefromtheProcessAuditLog
160
databasecomponent,theISCoreAuditLogdatabasecomponent,orboth,depending onthedatayouwanttoarchive.
161
162
CHAPTER
11
Installing the Database Components in Sybase

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, Reporting, Staging, and Trading Networks Database Components . . 164 Install the Archive, Process Audit Log, Reporting, and Staging Database Components . . 166
163
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
Overview
ThischapterexplainshowtoinstallwebMethodsdatabasecomponentsinSybase. Databasecomponentsareinstalledusingdifferentmethods;thesectionheadingsindicate whichdatabasecomponentsarecoveredineachsection. InstructionsforinstallingtheWorkflowdatabasecomponentautomaticallyviathe WorkflowConfiguratorareprovidedinCompletetheWorkflowInstallationon page 213.InstructionsforinstallingtheIntegrationServerRepositoryareprovidedinthe webMethodsIntegrationServerClusteringGuide.

Youinstallthedatabasecomponentscoveredinthissectionusingdatabasescripts availablethroughthewebMethodsInstaller.Downloadthedatabasescriptsasfollows: 1 DownloadthewebMethodsInstallerfromthewebMethodsAdvantageWebsiteat http://advantage.webmethods.comtoamachineequippedwithaSybasedatabase client. Starttheinstaller.SpecifytheinstallationdirectoryasthewebMethods6.5installation directory(bydefault,webMethods6). Inthecomponentselectionlist,gotoCommon Filesandchoosetodownloadthelatest versionofDatabase Scripts.
2 3
164
Install the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, Reporting, Staging, and Trading Networks Database Components

165
Install the Archive, Process Audit Log, Reporting, and Staging Database Components

Youinstallthedatabasecomponentscoveredinthissectionusingdatabasescriptsanda programcalledthewebMethodsDatabaseInstaller.Bothareavailablethroughthe webMethodsInstaller.DownloadthescriptsandwebMethodsDatabaseInstalleras follows: 1 DownloadthewebMethodsInstallerfromthewebMethodsAdvantageWebsiteat http://advantage.webmethods.comtoamachineequippedwithaSybasedatabase client. Starttheinstaller.SpecifytheinstallationdirectoryasthewebMethods6.5installation directory(bydefault,webMethods6). Inthecomponentselectionlist,gotoCommon FilesandchoosetoinstallDatabase Scripts 6.5.1.7.
2 3

1 OntheSybasedatabaseclientmachine,gotothewebMethods_directory\common\ db\scripts\sybasedirectoryandopenthesybase_env_properties.{bat|sh}fileina texteditor. Edittheseconnectionpropertiesforeachdatabasecomponentyouaregoingtoinstall:
Important! Databasenamesarecasesensitive.Youmustusetherightcasingforthe databasenameintheconnectionpropertiesortheinstallationwillfail. 3 Saveandclosethefile.
166
Install the Archive, Process Audit Log, Reporting, and Staging Database Components

1 Installthedatabasecomponentsasfollows: To install this database component... Archive Do this... GotothewebMethods_directory\common\db\scripts\ sybasedirectoryandrunthecreate_archive_6.5.{bat|sh} program. GotothewebMethods_directory\common\db\scripts\ sybasedirectoryandrunthe create_processaudit_6.5.{bat|sh}program. GotothewebMethods_directory\common\db\scripts\ createdirectoryandexecutethecreate_reporting_6 5_sybase.sqlscript. GotothewebMethods_directory\common\db\scripts\ createdirectoryandexecutethecreate_staging_6 5_sybase.sqlscript.
ProcessAuditLog
Reporting
Staging
IfyouinstalledtheArchivedatabasecomponent,andtheProcessAuditLogandIS CoreAuditLogdatabasecomponentsareinadifferentdatabasefromeachother, createtheISCoreAuditLogdrivertablesintheISCoreAuditLogdatabase componentbynavigatingtothewebMethods_directory\common\db\scripts\sybase\ code\archive\createdirectoryandexecutingtheSQLscript sybase_arc_c_ddl_tables_indexes.sql.

1 2 Forsecurityreasons,removethedatabaseuserpasswordfromthe sybase_env_properties.{bat|sh}databaseconnectionpropertiesfile. IfyouinstalledtheProcessAuditLogdatabasecomponent,defineaJDBCconnection poolforIntegrationServertousetocommunicatewiththedatabasecomponent.For instructions,seeIdentifytheDatabasesthatContaintheCrossReference,Document History,ISCoreAuditLog,ProcessAuditLog,Reporting,andStagingDatabase Componentsonpage 170. Note: ManagerandOptimizeautomaticallycreateaJDBCconnectionpooltouseto communicatewiththeProcessAuditLogdatabasecomponentwhenyoustartthe ManagerandOptimizecontroller.Theinformationrequiredtocreatetheconnection poolswassuppliedduringproductinstallation.
167
168
CHAPTER
12
Identifying 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
169
CHAPTER12 Identifying 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
TheIntegrationServerauditsubsystemusesJDBCconnectionpoolstocommunicatewith thedatabasecomponentsforitsCrossReference,DocumentHistory,ISCoreAuditLog, andProcessAuditLogfunctions.MonitorbuiltinservicesuseJDBCconnectionpoolsto communicatewiththeReportingandStagingdatabasecomponents.Managerserverand TradingNetworksServeruseJDBCconnectionpoolstocommunicatewiththeirdatabase components. AJDBCconnectionpoolidentifiesadatabaseinwhichtostoredataandspecifiespool parameters,suchasminimumandmaximumconnections.Afteryoudefineaconnection pool,youlinktheappropriatefunctiontothatconnectionpool.Forexample,youwould defineaconnectionpoolthatidentifiesthedatabasethatcontainstheProcessAuditLog databasecomponent,thenlinktheProcessAuditLogfunctiontothatconnectionpool. Multiplefunctionscanusethesameconnectionpool.Forexample,ifyouinstalledtheIS CoreAuditLogandDocumentHistorydatabasecomponentsinthesamedatabase,you couldlinkbothfunctionstothesameconnectionpool.Whenmultiplefunctionssharea connectionpool,IntegrationServercreatesaseparateinstanceoftheconnectionpoolfor eachdatabasecomponentatruntime. Note: YoumighthavealreadydefinedandlinkedaconnectionpoolforManagerserver andTradingNetworksServerduringproductinstallation. BelowareguidelinesforwhenyouareusingmultipleIntegrationServers. IfyouwanttouseMonitortoviewtheISCoreAuditLogdataofmultipleIntegration Servers,theIntegrationServersmuststoretheirISCoreAuditLogsinasingleISCore AuditLogdatabasecomponent.IfyouwanttouseMonitortoviewtheProcessAudit LogdataofmultipleIntegrationServers,theIntegrationServersmuststoretheir ProcessAuditLogsinasingleProcessAuditLogdatabasecomponent. IfyouhaveaclusterofIntegrationServers,allIntegrationServersintheclustermust storetheirDocumentHistorydatainasingleDocumentHistorydatabasecomponent.
170
Define a Connection Pool

1 2 InIntegrationServerAdministrator,gototheSettings JDBC Poolspage. ClickCreate a new Pool Alias Definitionandcompletetheboxesthatappearasfollows: Box Alias Name Alias Description Associated Driver Alias Database URL Entry Aliasfortheconnectionpool.Thealiascanincludeonlycharacters thatarevalidforafilenameinyouroperatingsystem. Descriptionfortheconnectionpool. Aliasforthedrivertouse.Thelistcontainspredefinedaliasesfor theJDBCdriverthatwebMethodssupplieswithIntegrationServer foreachtypeofsupporteddatabase. URLforthedatabasethatcontainsoneormoredatabase components,asfollows: URL Oracle
Default Port
1521

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
1433
Sybase
5000
171
Box
Entry DB2 UDB

jdbc:wm:db2://host_or_IPaddress:port; databaseName=database_name; PackageName=package_name;
50000
FortheArchive,Reporting,andStagingdatabase components:
BatchPerformanceWorkaround=true
DB2 UDB for AS/400

446
FortheArchive,Reporting,andStagingdatabase components:
BatchPerformanceWorkaround=true
Note: AlternateIdmustmatchtheschemainwhich youcreatedtheloggingdatabasetables. User Id Password Minimum connections DatabaseuserforIntegrationServertousetocommunicatewith thedatabase. Passwordforthedatabaseuser. Minimumnumberofconnectionstheconnectionpoolmustkeep openatalltimes. Ifyouusethispoolaliasformorethanonefunction,each connectionpoolinstancekeepsthespecifiednumberof connectionsopen.Forexample,ifyouspecifythatyouwantat least3connectionskeptopen,andtheISCoreAuditLogandthe DocumentHistorytablebothusethisconnectionpool,the connectionpoolkeepsatotalof6connectionsopen3fortheIS CoreAuditLogconnectionpoolinstanceand3fortheDocument Historytableconnectionpoolinstance. Ifyourloggingvolumehassuddenspikes,youcanimprove performancebymakingsuretheconnectionsneededtohandlethe increasedvolumeopenquickly.Youcanminimizeconnection startuptimeduringspikesbysettingthisvaluehigher,sothat moreconnectionsremainopenatalltimes.
172
Box Maximum connections
Entry Maximumnumberofconnectionstheconnectionpoolcanhave openatonetime. Calculatethisvalueaspartofthetotalpossiblenumberof connectionsthatcouldbeopenedsimultaneouslybyallfunctions andapplicationsthatwritetothedatabase.Makesurethetotal numberdoesnotexceedthedatabasesconnectionlimit.Ifoneof theapplicationsopensmoreconnectionsthanthedatabaseallows, thedatabasewillrejectsubsequentrequestsforconnectionsfrom anyapplication. Supposethedatabasesconnectionlimitis40connections.IftheIS CoreAuditLogandtheDocumentHistorytablebothusethis connectionpool,youcouldsafelyspecify20asthemaximum numberofconnectionsfortheconnectionpool.TheISCoreAudit Logconnectionpoolinstancecoulduseupto20connectionsand theDocumentHistorytableconnectionpoolinstancecoulduseup to20connections.(IfyouareusingMonitor,Monitorwoulduse connectionsfromtheISCoreAuditLogconnectionpoolinstance.) However,ifTradingNetworksalsowritestothedatabaseandhas aconnectionpoolthatcouldopenupto5connections,youcould specifyonly17asthemaximumnumberofconnectionsforthe currentconnectionpool.TheISCoreAuditLogconnectionpool instancecoulduseupto17connections,theDocumentHistory tableconnectionpoolinstancecoulduseupto17connections,and theTradingNetworksconnectionpoolcouldusetheremaining5 connections. Youmustcoordinatethevalueforthetemporarystoreproperty watt.server.auditMaxPoolwiththisvalue.Forinstructions,seethe webMethodsLoggingGuide.
Idle timeout
Periodoftime,inmilliseconds,theconnectionpoolcankeepan unusedconnectionopen.Afterthespecifiedperiodoftime, unusedconnectionsthatarenotneededtosatisfytheMinimum connectionsvalueareclosed. Ifyourloggingvolumehassuddenspikes,youcanimprove performancebymakingsuretheconnectionsneededtohandlethe increasedvolumeopenquickly.Youcanminimizeconnection startuptimeduringspikesbysettingthisvaluehigher,sothat moreconnectionsremainopenatalltimes.
ClickSave Settings.
173
Link a Function to a Connection Pool

Eachfunctionhasapredefinedfunctionalalias.Tolinkafunctiontoaconnectionpool,you associatetheappropriatefunctionalaliaswiththepoolalias.Thefunctionalaliasesareas follows: Function CrossReference DocumentHistory ISCoreAuditLog Managerserver ProcessAuditLog Reporting Staging TradingNetworksServer 1 2 3 4 5 Functional Alias Xref DocumentHistory ISCoreAudit Manager ProcessAudit Reporting Staging TN
InIntegrationServerAdministrator,gototheSettings>JDBC Poolspage. IntheFunctional Alias Definitionsarea,scrollrighttolocatetheEdit Associationcolumn forafunctionalaliasandclickEditinthatcolumn. IntheAssociated Pool Aliaslist,clickthepoolaliastolinktothefunctionalalias. ClickSave Settings.IntegrationServerAdministratorreturnstotheSettings>JDBC Poolspage. Initializetheconnectionpool.IntheFunctional Alias Definitionsarea,scrollrightto locatetheRestart FunctioncolumnforthefunctionalaliasandclickRestartinthat column. MakesureIntegrationServercanconnecttothedatabase.IntheFunctional Alias Definitionsarea,locatetheTestcolumnforthefunctionalaliasandtesttheconnection byclicking . IfyouhavenotyetconfiguredIntegrationServertowriteloggingandcrossreference datatoadatabase,gotoConfigureIntegrationServertoWriteCrossReference,IS CoreAuditLog,andProcessAuditLogDatatoaDatabase,below.Otherwise,restart IntegrationServer.
174
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 Database
Bydefault,IntegrationServerwritesCrossReference,ISCoreAuditLog,andProcess AuditLogdatatoflatfiles.YoumustconfigureIntegrationServertowritethedatato databasesinstead. 1 InIntegrationServerAdministrator,gototheSettings>ExtendedpageandclickShow and Hide Keys.IntegrationServerAdministratordisplaysalistofIntegrationServer configurationpropertiesyoucanchangeusingIntegrationServerAdministrator. Selectthecheckboxesnexttothepropertieswatt.server.auditStoreand watt.server.xref.type. ClickSave Changes.IntegrationServerAdministratordisplaystheselectedproperties intheExtended Settingsbox. ClickEdit Extended Settings.IntheExtended Settingsbox,setthepropertiesasfollows:
watt.server.auditStore=database watt.server.xref.type=jdbc
2 3 4
5 6
ClickSave Changes. RestartIntegrationServer.
Identify the Database for the Process Tracking Store Database Component
Important! Bydefault,thePRTwritesprocessstatusdatatoRAM.TohavethePRTwrite processstatusdatatotheProcessTrackingStoreinstead,yousetpropertiesonindividual processmodels.Fordetailedinstructions,seethewebMethodsProcessRunTimeUsers Guide. ForeachPRTclusterthatwillrunprocessesthatwillstoredataintheProcessTracking Storedatabasecomponent,youmustconfiguretheProcessTrackingStoreproperties. 1 StartanIntegrationServerthathostsaPRTinthePRTcluster.Openthehomepage forthePRTonthatIntegrationServerbyenteringhttp://Integration Server_host:IntegrationServer_port/WmPRTinabrowser. Note: IfatanytimeyouneedtoreverttothedefaultsettingsforthePRThomepage, clickDefaultonthatpage. 2 IntheCentral Process Tracking Storebox,indicatewhetherthePRTshouldstoreprocess statusandglobaldatainacentralordistributedProcessTrackingStorewhilesteps run.Withacentralstore,allPRTsstorethedatainasingle,centralProcessTracking
175
Storedatabasecomponent.Withadistributedstore,eachPRTstoresthedatatoits ownProcessTrackingStoredatabasecomponent.Decidewhichtouseasfollows: Use this type of store... Central WhenusingasinglePRTtorunprocesses WhenusingaclusterofPRTstorunprocessesthatdonotspan geographicallydispersedservers,andtheconnectionsofthe PRTstotheProcessTrackingStoredatabasecomponentare veryreliable Distributed WhenusingaclusterofPRTstorunprocessesthatspan geographicallydispersedservers WhenusingaclusterofPRTswhoseconnectionstoProcess TrackingStoredatabasecomponentsareunreliable 3 Whenyouuseacentralstore,allprocesscompletiondataisstoredinthecentral ProcessTrackingStoredatabasecomponent.Whenyouuseadistributedstore, processcompletiondataisdistributedamongmultipleProcessTrackingStore databasecomponents;youmustthereforedesignateonePRTtotrackprocess completiondataforallPRTs.IndicateintheProcess Completion Tracking Serverbox whetheryouwantthisPRTtoserveinthatcapacity. SpecifyProcessTrackingStoredatabasesettings,asfollows: In this box... Database Connection Retries Specify... MaximumnumberoftimesthePRTshouldtrytoconnectto theProcessTrackingStoredatabasecomponent.Afterthe maximumisreached,thePRTthrowsexceptions.Youwillnot beabletorunanymoreprocessesuntilyourestartthePRT. Periodoftime,inseconds,thePRTshouldwaitbetween connectionretries. Frequency,inseconds,withwhichthePRTshouldremove dataaboutcompletedprocessesfromtheProcessTracking Storedatabasecomponent. Cleanthedatabaseoftenenoughtokeepdatafromstraining thedatabasesizelimit,butnotsooftenastodegrade performance.Thedefaultof10minutesshouldbeoptimalfor mostsituations. 5 EachPRTusesaJDBCconnectionpooltocommunicatewiththeProcessTracking Storedatabasecomponent.IntheAssociated Pool Alias list,clickthealiasfortheJDBC connectionpoolthisPRTshoulduse.
Database Connection Retry Time Interval Database Cleanup Interval
176
Identify the Database for the Modeler Repository Database Component
Bydefault,thePRTusesthesamepoolaliasthatIntegrationServerusesto communicatewiththeProcessAuditLogdatabasecomponent,buttheProcess TrackingStoreandProcessAuditLogdatabasecomponentsmightnotbeinstalledin thesamedatabase.Youcanchooseadifferentpoolalias.Ifyouneedtodefineanew poolalias,seeDefineaConnectionPoolonpage 171. Important! YoumighthaveinstalledtheProcessTrackingStoreandtheProcessAudit LoginseparatedatabasesorschemasifyouappliedWmPRT_651_Fix1.Ifyoudid notapplythefix,youmusthaveinstalledthedatabasecomponentsinthesame databaseorschema,andIntegrationServerandthePRTsmustallusethesameJDBC connectionpooltoaccesstheProcessTrackingStoreandProcessAuditLogdatabase components. 6 7 Ifyouaredone,clickSubmit,thenreloadtheWmPRTpackageorrestartthehost IntegrationServer. RepeatthesestepsforeveryPRTinthecluster.ConfigurethesettingsforeachPRTin awaythatwillallowthemtofunctionasaninterconnectedunit.Forexample,ifyou wanttouseacentralProcessTrackingStore,setallPRTsintheclustertousethe centralProcessTrackingStoreandthesameJDBCconnectionpoolalias.Similarly,if youwanttouseadistributedProcessTrackingStore,setallPRTsintheclustertouse adistributedProcessTrackingStore,seteachPRTtouseadifferentJDBCconnection poolalias,anddesignateoneandonlyonePRTtoserveastheProcessCompletion TrackingServer.
Identify the Database for the Modeler Repository Database Component

1 OpentheModelerDesignPackagehomepagebyentering http://server_host:server_port/WmModelerinabrowser,whereserver_hostand server_portidentifytheIntegrationServerthathoststheModelerDesignPackage. Setthepropertieslistedbelow. Property Server Host Value NameofthemachinethathoststheModelerRepository.TheModeler DesignPackageincludestheModelerRepository,soidentifythe machinethathoststheIntegrationServerthathoststheModeler DesignPackage. PortusedbytheModelerRepository.Bydefault,theportis7778. SpecifyDatabaseasthestoragemethod.
Port Storage Method
177
Property URL
Value URLforthedatabasethatcontainstheModelerRepositorydatabase component,asfollows: URL Oracle

Default Port
1521
SQL Server
1433
DB2 UDB
50000
User Password JDBC Driver
DatabaseuserfortheModelerRepositorytousetocommunicatewith thedatabase. Passwordforthedatabaseuser. JDBCdrivernameforthedatabase,asfollows: Database Oracle SQLServer DB2UDB Driver Name
com.wm.dd.jdbc.oracle.OracleDriver com.wm.dd.jdbc.sqlserver.SQLServerDri ver com.wm.dd.jdbc.db2.DB2Driver
Classpath Log File Name
PathtotheJDBCdriverforthedatabase. Relativepathtothedirectoryinwhichtostorelogfiles.Thedefaultis JDBCData.log.
178
PART

Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
179
180
CHAPTER
13
Completing the Installation

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
181
CHAPTER 13 Completing the Installation
Post-Installation Checklist
Thechecklistbelowidentifiestasksyouneedtoperformtomakeabasicinstallationof webMethodsproductsoperational.Subsequentsectionsinthischapterorbookprovide detailedinstructions.Sectionsinthischapteralsoprovidedetailedinstructionsforother tasksyoumightwantorneedtoperform. Product Access,My webMethods Server,Portal webMethods Broker Task RunthePortalServerConfigurator Page 183
IfcreatedBrokerServerusinginstaller: MakesureBrokerServerisrunninganddefaultBrokerexists AdjustperprocessthreadandkernellimitsonHPUX IfdidnotcreateBrokerServerusinginstaller,createBroker Serverandperformothertasksusingcommands 189 190 267 191
Deployer
Ifinstalledonpre6.5IntegrationServer,oron6.5Integration ServerandusingnondefaultJDK,installJCEUnlimited StrengthJurisdictionPolicyFiles Configurecommunicationwithsourceandtarget webMethodsproducts;seewebMethodsDeployerUsersGuide
Integration Server
StartIntegrationServerandopenIntegrationServer Administrator IdentifycompilerforDevelopergeneratedJavacode Ifinstalled64bitJVMon64bitSolarisorHPUX,configure IntegrationServertouseJVM IfusingnondefaultJDK,installJCEUnlimitedStrength JurisdictionPolicyFiles
191 191 192 192 196 196 197 197 198 198
Manager, Optimize Modeler
OnUNIXorLinux,createManager/Optimizeuser MakesureinstalledModelerDesignPackageandPRTon IntegrationServer OnUNIXorLinux,giveusersproperpermissions DefinelogicalserversforprocessstepsandmaptoIntegration ServersorWorkflowServers
Monitor
SetupauthenticationtorunMonitorservices InstallSVGplugin
182
Configure Logging
Product Servicenet Workflow
Task Performtasksonchecklist SetupWorkflowdatabasecomponent IfinstalledsecondaryWorkflowServers,configuretoaccess encryptionpasswords RunWorkflowconfigurator IfWorkflowwilluseSSL,configureasnecessary
Page 199 213 213 215 224 229
Most products
ConfigurecommunicationbetweenMywebMethodsServer andotherwebMethodsproducts
Configure Logging
YoucanlogvarioustypesofdataforwebMethodsproducts.Fordetailedinformationand instructionsonsettinguplogging,seethewebMethodsLoggingGuide.
Complete the Access, My webM ethods Server, or Portal Installation

Configure the Server and Database
AfteryouinstallaproductthatrequiresandisinstalledwithMywebMethodsServer,you mustrunthePortalServerConfiguratortoconfigureMywebMethodsServer.Ifyou installedAccessorPortal,youusetheconfiguratortoconfigureadefaultserver;your portaladministratorcanlaterconfigureadditionalservers. YoucanalsousetheconfiguratortoinstalltheMywebMethodsServerdatabase componenttowhichMywebMethodsServer,Access,andPortalwrite,oryoucaninstall thedatabasecomponentmanually.Ifyouwanttoinstallmanually,youmustdosobefore youruntheconfigurator.Forinstructionsoninstallingmanually,seeInstalltheMy webMethodsServerDatabaseComponentonpage 138. TousetheconfiguratoronaUNIXorLinuxsystem,thesystemmusthaveanXWindows environment. Note: WhetheryouinstallMywebMethodsServer,Access,orPortal,thenameofthe configuratorisalwaysPortalServerConfigurator,andthelabelsontheconfigurator panelsalwaysusethenamePortal.
183
Before You Begin

Ifyouaregoingtoinstallmanually,usetheinstructionsinthewebMethodsDatabaseGuide. IfyouaregoingtoinstalltheMywebMethodsServerdatabasecomponentusingthe configurator,dothefollowing: IfyouareinstallinginOracle,settheNLS_LENGTH_SEMANTICSinitialization parametertoBYTE. Makesurethedatabaseserverisrunningsotheconfiguratorcanconnecttoit.You caninstallthedatabasecomponentineitheroftwoways: Ifyouhaveadministratoraccesstothedatabaseserverinwhichyouwantto installthedatabasecomponent,youcanusetheconfiguratortocreatea tablespace(Oracle)ordatabase(SQLServer)anddatabaseuserandtheninstall thedatabasecomponentinthenewtablespaceordatabase. Ifyoudonothaveadministratoraccess,youcanaskyourdatabaseadministrator tocreateanemptytablespace(Oracle)ordatabase(SQLServer)andadatabase user,andthenusetheconfiguratortoinstallthedatabasecomponentinthe tablespaceordatabase.ThedatabaseusermusthaveCONNECT,RESOURCE, CREATEVIEW,andGLOBALQUERYREWRITEpermissions.
Start the Configurator

RuntheconfiguratoronthemachineonwhichyouinstalledMywebMethodsServer, Access,orPortal.IfyouinstalledusingthewebMethodsInstallerwizard,theinstaller automaticallystartstheconfiguratorwheninstallationiscomplete.Ifyouinstalledusing thewebMethodsInstallerconsolemode,youmuststarttheconfiguratormanuallyby enteringthiscommand:
webMethods_directory/Portal/tools/configurator/run.{bat | sh}
IfyouareconfiguringMywebMethodsServeralone,theconfiguratordisplaystheGeneral tab.IfyouareconfiguringAccessorPortal,theconfiguratordisplaystheNew Server Instancetab.Thistabletsyoucreateservers.SinceyouareconfiguringthedefaultAccess orPortalserver,clickNext.InNew Portal Server Instance Namefield,typeanameforthe defaultserveroracceptthedefaultname(default).ClickNext.Theconfiguratordisplays theGeneraltab.
184
Complete the Access, My webMethods Server, or Portal Installation
Set General Parameters

1 CompletetheGeneraltabasfollows: Box Database server type Entry TypeofdatabaseserverinwhichyouaregoingtoinstalltheMy webMethodsServerdatabasecomponent. Database Server SQLServer Oracle Messaging provider type Option mssql oracle
IfyouareconfiguringAccessorPortal,indicatewhetherthe defaultserveristouseJMStocommunicatewithotherserversina cluster.Acceptthedefaultentrynone. Note: Ifyourportaladministratorisgoingtocreateaclusterof AccessorPortalservers,hewillchangethisentrylater.
Web server type
IfyouareconfiguringAccessorPortal,typeofWebserverforthe defaultservertouse.Acceptthedefaultentryinternaltousethe JettyWebserverthatcomeswiththeserver. Note: Ifyourportaladministratorisgoingtocreateaclusterof AccessorPortalservers,hewillchangethisentrylater.
ClickNext.IfyouareconfiguringAccessorPortal,theconfiguratordisplaysthe Componentstab;seeSelectPortalComponentstoDeploy,below.Ifyouare configuringMywebMethodsServeralone,theconfiguratordisplaysatablabeled MSSQLorOracle,dependingonthedatabaseserveryouidentifiedintheDatabase server typelistontheGeneraltab;seeInstalltheMywebMethodsServerDatabase Componentonpage 187.
Select Portal Components to Deploy

1 OntheComponentstab,selecttheAccessorPortalcomponentsyouwantthe configuratortodeploywhenitinitializesthedefaultserver. Important! webMethodsrecommendsthatyouacceptthesetofcomponentsthatare selectedbydefault.Becausetheabsenceofcomponentscanleadtolossofnecessary functions,onlyanexperiencedportaladministratorshouldtrytoconfigureaserver withlessthanthedefaultcomponentset.
185
Component Group Portal Services Administration Components Default Components Default Content Portal Development Samples Extras Mobile UI Support 2
Deploys portlets that... Provideavarietyofservices,includingsubscriptionsand notifications,versioncontrol,andsupportfordirectoryservices. LetyouperformadministrativetasksonAccessorPortal services,suchasportalanalysis,configuration,andcontent management. ProvidebasicelementsoftheAccessorPortaluserinterfaceand letyoumanagecommunicationbetweenportalsandexternal resources,suchasWebDAVorFTPservers. ProvidedefaultwebMethodscontentforportals. Helpyoudevelopportlets.IncludesthePortletDeveloperyou caninstallasaplugintoEclipse. Providesamplesanddemonstrationsofportaltechnology.All sampleincludefullsourcecode. Addcapabilitiestoaportalpageorenabletheproper functioningofotherportlets. SupportthedeliveryofHTMLpagestomobiledevices.
ClickNext.TheconfiguratordisplaysatablabeledMSSQLorOracle,dependingonthe databaseserveryouidentifiedintheDatabase server typelistontheGeneraltab.
186
Complete the Access, My webMethods Server, or Portal Installation

1 CompletetheMSSQLorOracletabasfollows: Box or Area Initialize Portal Database Setting Indicateswhetherto: Createatablespace(Oracle)ordatabase(SQLServer)and databaseuserandtheninstalltheMywebMethodsServer databasecomponentinthetablespaceordatabase(option1) InstalltheMywebMethodsServerdatabasecomponentinan existingtablespaceordatabaseusinganexistingdatabase user(option2) UsetheMywebMethodsServerdatabasecomponentyou installedmanuallybeforerunningtheconfigurator(option 3) database_server Host/Port Intheboxontheleft,nameorIPaddressofthemachinethat hoststhedatabaseserver.Donotuselocalhosttoidentifythe host. Intheboxontheright,portthedatabaseserverusesto communicate.ThedefaultportforOracleis1521andforSQL Serveris1433. Portal database User name Databaseuserfortheservertousetocommunicatewiththe database.Ifyouarecreatingthedatabaseuser(asopposedto usinganexistingone),thedatabaseusermustbeuniqueforthe databaseserver. Passwordforthedatabaseuser. SIDfortheOracleinstanceonthedatabaseserverhostmachine fortheMywebMethodsServerdatabasecomponent. Ifyouarecreatingatablespace(Oracle)ordatabase(SQL Server),administratoruserforthedatabaseserver.Ifyouare usinganexistingtablespace,enterthesamevalueyouenterfor Portal database User name. Ifyouarearecreatingatablespace(Oracle)ordatabase(SQL Server),administratorpasswordforthedatabaseserver.Ifyou areusinganexistingtablespace,enterthesamevalueyouenter forPortal database User password.
Portal database User password Oracle instance system identifier (SID) (Oracle) database_server administrator name database_server administrator password
187
Box or Area Portal database name (SQL Server) Portal Tablespace(s) name (Oracle) 2
Setting NameofthedatabasefortheMywebMethodsServerdatabase component. NameofthetablespacefortheMywebMethodsServerdatabase component.
ClickNext.Theconfiguratortakestheappropriateaction,thendisplaysthePortaltab.
Initialize the Server

1 CompletethePortaltabasfollows: Box Jetty HTTP Listener Host/Port Entry Intheboxontheright,HTTPportnumberfortheserver.The defaultportis8080. Note: ThehostboxontheleftisnotavailablebecausetheJettyWeb servermustbeonthelocalhost. IfanapplicationwithanHTTPlistenerisalreadyusingport8080, youshouldchangetheJettyHTTPListenerportnumbertoavoid possibleconflicts. Portal RMI Listener Host/Port Intheboxontheright,portnumberonthelocalcomputerwhere theRMIregistryismaintained.Thedefaultportis1097. Note: ThehostboxontheleftisnotavailablebecausetheRMI listenermustbeonthelocalhost. Default log level 2 Levelofdetailyouwanttheservertoincludeinitslogmessages.
ClickNext.Theconfiguratorinitializestheserverbyrunningascriptinaseparate window.IfyouareconfiguringAccessorPortal,theconfiguratordisplaysthe Summarytab. Note: Thescriptmighttakeuptoanhourtorun.
188
Complete the webMethods Broker Installation
Finish Portal Server Configuration

TheSummarytabdisplaysasummaryoftheconfigurationentriesyouprovidedforthe defaultserver.Tocompletetheconfiguration,dothefollowing: 1 2 ClickFinish.Theconfiguratordisplaysacompletionwindow. IfthedefaultserverisonaWindowssystem,indicatewhetheryouwanttorunitasa WindowsapplicationorasaWindowsservice,basedonthefollowing: If you want ... Tostartandshutdownthedefault servermanually.Typically,youwould installadevelopmentserverasan application. ThedefaultPortalservertostartand shutdownautomaticallywhenyou startandshutdownyoursystem. Typically,youwouldinstallaproduc tionserverasaservice. 3 4 Configure as... Application.ClickStart webMethods Portal Server.
Service.ClickInstall webMethods Portal Server as a Windows Service.Inaseparate window,theconfiguratorchangesthe servertoaWindowsservice.ClickStart webMethods Portal Windows Service.
Whenaskedwhetheryouwanttoautomaticallyopentheserverpageinabrowser window,clickYes.Theconfiguratorstartstheserver. ExittheconfiguratorbyclickingtheFilemenu,thenclickingExit.
Install the Portlet Developer

IfyouwanttoinstallthePortletDeveloper,seethewebMethodsPortalDesignGuidefor instructions.
Complete the webMethods Broker Installation

Important! CompletethissectionifyouconfiguredtheBrokerServerusingtheinstalleras describedinConfigurewebMethodsBrokeronpage 113.Otherwise,seeAppendix C, CreatetheBrokerServerConfigurationManuallyforinstructionsonconfiguringthe BrokerServer.
Make Sure the Broker Server is Running and the Default Broker Exists
Onmostsystems,afterinstallation,BrokerMonitorautomaticallystartsBrokerServer, whichbeginsrunningwithadefaultBroker.Usethebroker_statuscommandtomake suretheBrokerServerisrunningandthedefaultBrokerexists,asfollows:
189
broker_status [Broker #1@]Broker Server_host[:Broker Server_port]
YoucanalsouseBrokerAdministratortomakesuretheBrokerServerisrunningandthe defaultBrokerexists(seethewebMethodsBrokerAdministratorsGuide). TheexceptionisonWindows2003systemsthatarerunningTerminalServices.Ifyou installedwebMethodsBrokeronsuchasystem,BrokerMonitorcannotstartBroker ServeruntilyougiveBrokerMonitorthelocationofthesharedWindowssystemdirectory thatcontainstheBrokerMonitorconfigurationfile.(AWindows2003systemrunning TerminalServicesprovidesBrokerMonitorwiththelocationoftheprivateWindows systemdirectory.)SettheWMBROKERMONITOR_CONFIGenvironmentvariabletothe webMethodsBrokerconfigurationdirectory(bydefault,webmethods)intheshared Windowssystemdirectory.Forexample,ifthesharedWindowssystemdirectoryis C:\Windows,setthevariabletoC:\Windows\webmethods.
Adjust Per-Process Thread Limit and Set Per-Process and Kernel Limit on HP-UX Systems
IfyouinstalledwebMethodsBrokeronanHPUXsystem,askyoursystemadministrator toadjusttheperprocessthreadlimitandsettheperprocessandkernellimitforthe maximumnumberofopenfiles.Forinstructions,seetheHPUXsystemmanual.
Set Locale on UNIX or Linux Systems

IfyouaregoingtorunwebMethodsBrokerinalocaleotherthanU.S.English,you probablysetyourshelltotheproperlocalebeforeinstallation.However,thissettingonly affectshowthewebMethodsInstallerstartsyourBrokerServerduringinstallation.When yourestarttheBrokerServer,theBrokerServerwillusethedefaultlocale,U.S.English.If youwanttosettheBrokerServertorunusingadifferentlocale,settheenvironment variablesLC_ALLandLANGtothatlocale.
Enable Full Core Dumps on AIX Systems

OnAIXsystems,bydefault,theabilitytoperformfullcoredumpsisnotenabled.Ifyou wanttoenablethisability,dooneofthefollowing: Runthiscommand:
chdev -l sys0 -a fullcore=true
UsetheAIXSystemManagementInterfaceTool(SMIT).Runthecommandsmitty
chgsysandsetthevalueofEnablefullCOREdumptotrue.
YoudonothavetoreboottheAIXsystemforthischangetotakeeffect.
190
Complete the Deployer Installation
Complete the Deployer Installation

Apply Fixes for Modeler 6.1.5
Ifyouaregoingtodeployfrom6.1.5ModelerDesignservers(thatis,IntegrationServers equippedwithModelerDesignPackage6.1.5),youmightneedtoapplyModeler_61 5_Fix26. IfoneormoreofyourModelerDesignserversareonHPUXorLinuxsystems,thefix solvesproblemswiththewayModelerDesignserversworkonUNIXorLinux machinesrunninginaheadlessenvironment. IfyouwanttodeployprocessmodelsthatincludeWorkflowsteps,thefixenables DeployertodeploytheIntegrationServeritemsthatareassociatedwithWorkflow processsteps.
Install JCE Unlimited Strength Jurisdiction Policy Files

IfyouinstalledDeployeronapre6.5IntegrationServer,orifyouinstalledDeployerona 6.5IntegrationServerandareusingaJDKotherthantheJDKinstalledbytheinstaller, yourJVMmustcontaintheJavaCryptographyExtension(JCE)UnlimitedStrength JurisdictionPolicyFilesforthatJVMversion.Deployerneedsthesefilestorunits commandlinescripts. YoucandownloadtheJCEfilesforaSunorHewlettPackardJDKfromtheSunWebsite athttp://java.sun.com/j2se/1.4.2/download.html.YoucandownloadtheJCEfilesforan IBMJDKfromtheIBMsiteat http://www.ibm.com/developerworks/java/jdk/security/index.html.Installthefilesusing theinstructionsinthevendordocumentation.
Complete the Integration Server Installation

Direct Integration Server to Compiler to Use for Developer
IfyouwantIntegrationServertouseaJDKotherthanthedefaultJDKtocompileJava servicesdevelopedusingDeveloper,puttheJDKinyoursystempathor,ifyouwantto usetheJDKforIntegrationServeronly,followthestepsbelow. 1 2 StartIntegrationServer.OntheStartmenu,goto Programs webMethods Servers webMethods Integration Server. OpenIntegrationServerAdministratorbyenteringthisURLinanInternetbrowser:
http://Integration Server_host:Integration Server_port
ThedefaultportforIntegrationServeris5555.
191
3 4
Loginunderthedefaultusernameandpassword,Administratorandmanage. GototheSettings ExtendedpageandclickShow and Hide Keys.IntegrationServer AdministratorlistsIntegrationServerconfigurationpropertiesyoucanchangeusing IntegrationServerAdministrator. Selectthecheckboxnexttothewatt.server.compilepropertyandthe watt.server.compile.unicodeproperty,thenclickSave Changes.IntegrationServer AdministratordisplaystheselectedpropertiesintheExtended Settingsbox. ClickEdit Extended Settings.IntheExtended Settingsbox,setthepropertiesasfollows:
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}
ThelocationoftheJDK1.4.2thatisautomaticallyinstalledbytheinstalleris webMethods\jvm\win142. 7 8 ClickSave Changes. RestartIntegrationServer.
Configure Integration Server to Use a 64-Bit JVM on Solaris and HP-UX Systems
Ifyouinstalleda64bitJVMona64bitAIXsystem,IntegrationServerwillusetheJVM automatically.Ifyouinstalleda64bitJVMona64bitSolarisorHPUXsystem,youmust configureIntegrationServertousetheJVM. 1 2 3 GototheIntegrationServer_directory/bindirectoryandopentheserver.shfileinatext editor. UncommenttheJAVA_D64parameter. Saveandclosethefile.
Install JCE Unlimited Strength Jurisdiction Policy Files

IfyouareusingaJDKotherthantheJDKinstalledbytheinstaller,yourJVMmustcontain JavaCryptographyExtension(JCE)UnlimitedStrengthJurisdictionPolicyFiles1.4.2. IntegrationServerneedsthesefilestobeabletoencryptanddecryptSSLcertificates. YoucandownloadtheJCEfilesforaSunorHewlettPackardJDKfromtheSunWebsite athttp://java.sun.com/j2se/1.4.2/download.html.YoucandownloadtheJCEfilesforan IBMJDKfromtheIBMsiteat http://www.ibm.com/developerworks/java/jdk/security/index.html.Installthefilesusing theinstructionsinthevendordocumentation.
192
Increase File Descriptors on UNIX, Linux, OS/400, and Mac OS X Systems

OnUNIX,Linux,OS/400,andMacOSXsystems,IntegrationServersabilitytohandle trafficisconstrainedbythenumberoffiledescriptorsavailabletotheIntegrationServer process.Onmostsystems,64filedescriptorsareavailabletoeachprocessbydefault. webMethodsrecommendsthatyouaskyoursystemadministratortoincreasethenumber offiledescriptorsavailabletotheIntegrationServerprocesstoatleast1024. Important! Youmighthavetoincreasethisnumberdependingonthenumberoffiles IntegrationServerneedstohaveopenatonetime.Itisdangeroustosettherlim_fd_max valuehigherthan1024becauseoflimitationswiththeselectfunction,soifIntegration Serverrequiresmorefiledescriptors,askthesystemadministratortosetthesetrlimit valuedirectly.
Change Permissions on UNIX, Linux, OS/400, and Mac OS X Systems

IfyouinstalledIntegrationServeronaUNIX,Linux,OS/400,orMacOSXsystemand nonrootuserswillberunningIntegrationServer,youmightwanttochangethe ownershipoftheinstalledfilestoallowasinglenonrootusertorunIntegrationServer (chown),changethefilegrouptothegroupofuserswhowillrunIntegrationServer (chgrp),orchangefilepermissionstoallowalluserstorunIntegrationServer(chmod).
Prevent Memory Problems on OS/400 Systems

IfyouinstalledIntegrationServeronanOS/400system,preventmemoryproblemsby followingthestepsbelow. 1 LimitthesizeoftheportqueueavailabletotheTCP/IPstack,asfollows: a b c IfyouhavenotyetstartedIntegrationServer6.1,startitnow.IntegrationServer createstheserver.cnffileswhenitstartsforthefirsttime. ShutdownIntegrationServer. GototheIntegrationServer_directory/configdirectoryandopentheserver.cnffile inatexteditor.Addthisline:
watt.server.portQueue=511
193
OnOS/400systems,theJAVA_MIN_MEMsettingactsasagarbagecollection threshold.PreventtheJVMthatIntegrationServerisusingfromrunningoutof memorybydoingthefollowing: a b GototheIntegrationServer_directory/bindirectoryandopentheserver.shfileina texteditor. LocatetheJAVA_MIN_MEMparameterandsetitasfollows:

JAVA_MIN_MEM=64M
Note: ThissettingisbasedonanOS/400systemthathostsanIntegrationServer andaDB2UDBforAS/400database.Theoptimalvalueforinitialheapsizemight behigherorlowerbasedonyoursystemsconfiguration. c d LocatetheJAVA_MEMSETparameterandsetitasfollows:

JAVA_MEMSET="-ms${JAVA_MIN_MEM}"
Streamline Integration Server

Bydefault,IntegrationServerisequippedwithseveralpackagesthatprovidedifferent typesoffunctionality.IfyouwanttostreamlineIntegrationServer(forexample,because youareusingitonlytorunadapters,orbecauseyouarerunningitasareverseinvoke proxyserver),youcandisablemanyofthesepackages. 1 Reviewthetablebelowanddeterminewhichpackagesyoucansafelydisable. Package WmART WmAdminResource Contents ServicesthatIntegrationServerusestorunadaptersthat areversion6.0orlater. ServicesthatAdministratorusestoretrieveinformation aboutresources(forexample,packages)installedon IntegrationServer. Servicesthatenableyoutoprocessflatfilesandusefile pollingports. ServicesthattheManagerserverusestoconnecttoand manageIntegrationServerandTradingNetworks Server. ServicesthatarerequiredbytheWmARTpackage.
WmFlatFile WmOmiAgent
194
Package WmOmiIs
Contents ServicesthattheManagerserverusestomanage adaptersinstalledonIntegrationServer. ServicesthatarerequiredbytheWmARTpackage.
WmWin32
ServicesyoucanusetocallmethodsonCOMobjects.Also containsWindowsspecificsamples,suchassampleVisual Basicservices.
Ifyouneedmoreinformationonanyofthesepackages,seethewebMethodsIntegration ServerAdministratorsGuide. 2 3 StartIntegrationServer. TheWmOmiAgentpackageisdependentontheWmOmiIspackage.Ifyouwantto disabletheWmOmiISpackagebutyouwanttousetheWmOmiAgentpackage,you mustfirstremovethedependencyusingthestepsbelowortheWmOmiAgent packagewillnotload. Important! IfyouaregoingtousetheWmARTpackage,youcannotdisablethe WmOmiAgentpackageortheWmOmiIspackage. a StartDeveloper,asfollows: System Windows Linux Action OntheStartmenu,gotoPrograms Developer. webMethods webMethods
GototheDeveloper_directory/bindirectoryandrunthe developer.shscript.
b c d 4 5
IntheNavigationpanelontheleftsideoftheinterface,rightclicktheWmOmiIs package,thenclickOpen. OntheSettingstab,inthePackage dependenciesarea,clicktheWmOmiAgentrow. Click .DeveloperremovestheWmOmiAgentpackagesdependencyonthe WmOmiIspackage. Managementpage.
InIntegrationServerAdministrator,gotothePackages
Disableeachpackageyoudonotneed.Todoso,locatetherowforthepackageinthe table,thenclickYesintheEnabledcolumninthatrow.TheYeschangestoNo. Important! DonotdisabletheWmRootorWmPublicpackages.
195
Complete the Installation for Manager, Optimize, or Both

Create the Manager/Optimize User and Enable Automatic Start and Shut Down on UNIX or Linux Systems
Important! OnlyperformthestepsinthissectiononceforManagerandOptimize.Ifyou installManagerandlaterinstallOptimize(orviceversa),donotperformthestepsagain whenyouinstallthesecondproduct. Performthestepsbelowonthecontrollerhostmachine,thedatahandlerhostmachine, andeachsatellitehostmachine. 1 2 Logontothehostmachineastherootuser. Createagroupnamedwebm,thencreateauseraccountnamedwebmbam withinthewebmgroup.Grantthewebmbamuserownershipofallcontroller,data handler,orsatelliterelatedsoftwarebynavigatingtotheManager/Optimize installationdirectoryandenteringthiscommand:
chown -R webmbam:webm webmbam
Gotothedirectorylistedbelowanddeploytheruncommand(RC)scriptsthatenable automaticstartandshutdownofthespecifieditembyrunningtheindicatedshell scripts. Item Controller Datahandler Satellites Optimize Directory controller/bin datahandler/bin satellite/bin Shell Script
controller_rc_deploy.sh datahandler_rc_deploy.sh satellite_rc_deploy.sh
Complete the Modeler Installation

Make Sure Modeler Design Package and PRT are Installed
Inadevelopmentenvironment,youcaninstallModelerbyitselfonamachineandcreate processmodels.Whenyouwanttosharetheprocessmodelswithotherusers,however, youmustconnecttheModelermachinetoyournetworksoitcancommunicatewiththe IntegrationServerthatisequippedwiththeModelerDesignPackageandthePRT.To checkwhetheranIntegrationServerhasthesepackages,openIntegrationServer Administrator,gotothePackages Managementpage,andlookfortheWmModelerand WmPRTpackages.Ifthepackageisdisabled,enableit.Todoso,locatetherowforthe packageinthetable,thenclickYesintheEnabledcolumninthatrow.TheYeschangesto No.
196
Complete the Modeler Installation
Give Users Proper Permissions on Linux Systems

IfyouinstalledModeleronaLinuxsystem,giveanyuserwhoisgoingtorunModeler thesepermissions: Directory or File Modelerinstallationdirectory Modeler_directory/bin/modeler.sh Permissions Writepermission Executepermission
IfyouareusingModelerwithaWorkflowclient,alsogivetheusersthesepermissions: Directory or File Modeler_directory/lib/setup.sh Permissions Read/write/executepermission
IfyouinstalledtheModelerRepositoryonaUNIXorLinuxsystem,giveanyuserwhois goingtostarttheModelerRepositorythesepermissions: Directory or File webMethods_directory/Servers/RepoV3 webMethods_directory/Servers/ RepoV3/WmRepository webMethods_directory/Servers/RepoV3/ runreposerver.sh Permissions Writepermission,tocreatealogs directory Read/writepermission,tocreateaflatfile forModelerRepositorytowriteto Executepermission
Define Logical Servers and Map to Integration Servers

ProcessstepsrunonIntegrationServersorWorkflowServers.WhenaModeleruser definesaprocessmodel,hemustassigneachprocesssteptorunonaparticular IntegrationServerorWorkflowServer.However,theusermakestheassignment indirectly;heassignseachsteptoanaliasthatmapstoanIntegrationServerorWorkflow Server.Thesealiasesarecalledlogicalservers.Theuseoflogicalserversmeansthatyou canredirectstepstorunondifferentIntegrationServersorWorkflowServerswhenever necessarysimplybychanginglogicalservermappings,asopposedtomodifyingprocess modelstepassignments. TomaplogicalserverstoIntegrationServersorWorkflowServers,openIntegration ServerAdministratorfortheIntegrationServerthatisequippedwithAdministrator.Go totheLogical Servers Add Logical Serverspage.Definelogicalserversandmapthemto IntegrationServersorWorkflowServers.Namethelogicalserversintuitively(for example,AccountingServer);youcannotchangethesenameslater.Forcomplete instructionsondefininglogicalservers,seethewebMethodsModelerUsersGuide.
197
Complete the Monitor Installation

Set Up Authentication to Run Monitor Services
WhenyouinstallMonitor,theinstallerautomaticallyinstallstheCommonAuthentication packageontheIntegrationServerthathoststheMonitorservices.Thispackagemakesit possibleforMywebMethodsServertoauthenticateMywebMethodsuserswhoaretrying torunMonitorservicesonIntegrationServer.Followthesesteps: 1 2 OpenIntegrationServerAdministratorandgotothePackages Click Box Enabled Authorization Directory Host Authorization Directory Port Authorization Server User name Managementpage.
fortheWmComauthpackage.Completethepageasfollows: Entry Selectthecheckbox. MachinethathostsMywebMethodsServer. PortforMywebMethodsServer.ThedefaultportforMy webMethodsServeris8080. UsernameforIntegrationServertousetologontoMy webMethodsServer.Youcanusethedefaultusernameor createausernameinMywebMethodstouse.Forinstructions oncreatingusernames,seeMywebMethodsServer AdministratorsGuide. Passwordfortheusername. MonitorgrouptowhichtoassigntheMywebMethodsusers whoaretryingtorunMonitorservicesonIntegrationServer. ClickMonitorAdministrators.
Authorization Server Password Monitor Access Group
Install the SVG Plug-In

ToseeallMonitorimagefunctionality,yourbrowsermustbeequippedwithascalable vectorgraphics(SVG)browserplugin.Youcanusethistesttodeterminewhetheryour InternetExplorerbrowserhasanSVGplugin: http://www.adobe.com/svg/viewer/install/svgtest.html IfanSVGpluginisnotinstalled,webMethodsrecommendsAdobesSVGplugin,which issupportedonWindows,Linux,andMacOSXsystems.Youcandownloadtheplugin fromthispage: http://www.adobe.com/svg/viewer/install/main.html
198
Complete the Servicenet Installation
Afteryouinstalltheplugin,setyourMywebMethodsinterfacetodisplayprocessmodel imagesinSVGformat.Forinstructions,seetheMywebMethodsServerAdministrators Guide. Note: IfyourbrowserdoesnotsupportSVG,youcandisplayprocessmodelimagesinJPG format.Forinstructions,seetheMywebMethodsServerAdministratorsGuide. MonitorcontainsJavaSwingandAWTcomponentsthatrequireagraphicaldisplay utilitytoload.IfyouinstalledMonitoronaUNIXorLinuxsystemandyouarenotusing SVG,youmustdoeitherofthefollowing: UseautilitysuchasanXServeroravirtualXServersuchasXvfb.TheUNIXor Linuxsystemmusthaveaccesstothegraphicaldisplayutility,andyoumustsetthe machinesDISPLAYsettingtoidentifythehostmachineonwhichtheutilityis running. ModifyIntegrationServersstartupfiletousetheDjava.awt.headlessoption,as follows: a b c GototheIntegrationServer_directory/bindirectoryandopentheserver.shfileina texteditor. Locatethisline:
JAVA_MEMSET="-ms${JAVA_MIN_MEM} -mx${JAVA_MAX_MEM}"
Addtheargumentshownbelowtotheline:
JAVA_MEMSET="-Djava.awt.headless=true -ms${JAVA_MIN_MEM} -mx${JAVA_MAX_MEM}
Note: IftheJAVA_MEMSETlinealreadyincludestheserveroption,addthe Djava.awt.headlessoptionaftertheserveroption.

Servicenetconsistsofcorecomponentsthatarerequiredforbasicoperationandagents thatinteractwithdifferentWebservicecontainers. Core Components Registry Controller Datahandler MywebMethodsServer Agents Intermediary ServicenetPackage(onIntegrationServer) GluePlugin WebLogicPlugin Microsoft.NETPublisher
199
TocompletetheServicenetinstallation,youmustdothefollowing: Action 1 ConfigureMywebMethods ServerandinstalltheMy webMethodsServerdatabase component. Instructions WhenyouinstalledtheServicenetuser interface,theinstallerautomaticallyinstalled MywebMethodsServer.Youmustconfigure MywebMethodsServerandinstalltheMy webMethodsServerdatabasecomponent.For instructions,seeConfiguretheServerand Databaseonpage 183. WhenyoulicensedServicenet,webMethods providedyouwithalicensefilenamed webMethodslicense.xml.Placethe webMethodslicense.xmlfileinthe Servicenet_directory\confdirectoryonthe Servicenetregistryhostmachineandonevery intermediaryhostmachine. SeeSetUpthePluginsonpage 201. SeeConfigureRegistryDiscoveryon page 205.
Placelicensefilesonthe Servicenetregistryand intermediaryhostmachines.
3 4
Ifyouinstalledoneormoreplug ins,deployandconfigurethem. Insomecases,configurethe Servicenetcomponentssothey candiscovertheServicenet registry.
Note: Youdonothavetoconfigurethe datahandlertodiscovertheregistry becauseitcommunicateswiththe registrythroughthecontrollerrather thandirectly. 5 Ifyouwanttochangetheporton whichtheregistrylistensfor clients,configuretheregistry. Ifsomecases,configurethe registry,intermediaries,and pluginstocommunicatewithMy webMethodsServer. SeeChangetheDefaultRegistryPorton page 210. SeeConfigureServicenetComponentsto CommunicatewithMywebMethodsServer onpage 211.
200
Set Up the Plug-ins

Configure the Servicenet Package on Integration Server
1 2 GototheIntegrationServer_directory\packages\WmSnetPlugin\web\WEBINF directoryandopentheweb.xmlfileinatexteditor. Locatethe<init-param>elementwiththevalueelectric.http.url. a b ChangelocalhosttothenameoftheIntegrationServerhostmachine. ChangetheportnumbertotheprimarylistenerportforIntegrationServer(by default,5555).Forexample:
<init-param> <param-name>electric.http.url</param-name> <param-value>http://intserver:5555/web/WmSnetPlugin/services</param-value> </init-param>
Deploy and Configure the Glue Plug-in

TheGluePluginconsistsofthefollowing: MywebMethodsServer,Optimize,andServicenetjarfilesinstalledbythe webMethodsInstallerintheServicenet_directory\misc\plugins\glue\libdirectoryon theGluehost. Thesnetclientconfig.xmlfileinthesnetclient.jarfileintheServicenet_directory\ misc\plugins\glue\libdirectory. Thejarfileslistedbelow,whicharelocatedinyourGlueinstallation Functional Area XML Jar Files xalan.jar xercesImpl.jar xmlapis.jar jaxencore.jar Security xmlsec.jar wss4j.jar opensaml.jar ThemethodyouusetodeployandconfiguretheGluePlugindependsonthewayyou startGlue. jaxendom.jar saajapi.jar jaxrpcapi.jar saxpath.jar
201
Deploy and Configure the Plug-in When You Start Glue by Calling the HTTP.startup() Method IfyoustartGluebycallingtheHTTP.startup()method,dothefollowing: 1 Deploythepluginbyaddingallthejarfilesinstalledwiththeplugintothesystem classpathatthesamelevelastheglue.jarfile.Alsoaddthesnetclientdefault config.xmlfiletothesystemclasspath. ConfigureyourHTTP.startupservicestoworkcorrectlywiththepluginbyaddinga Fabric.join()statementtotheserverclassoftheservices.Forexample:
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" );
Deloy and Configure the Plug-in When You Start Glue Using the runapp Command IfyoustartGlueusingtherunappcommand,dothefollowing: 1 Dooneofthefollowing: CopythejarfilesinstalledwiththeplugintotheGlue_directory\WEBINF\lib directoryandcopythesnetclient.jarfiletotheGlue_directory\WEBINFdirectory. Addthejarfilesinstalledwiththeplugintothesystemclasspathatthesame levelastheglue.jarfile.Copythesnetclientdefaultconfig.xmlfiletothe Glue_directory\WEBINFdirectory. 2 BeforeyoustartGlue,configureGluetoworkwiththeplugin,asfollows: a b GototheGlue_directory\WEBINFdirectoryandopentheweb.xmlfileinatext editor. Addan<init-param>elementtothegluesoapservlet.Thiselementenablesthe plugintoprovideitslocationtotheServicenetregistry.The<init-param> elementtakesthenameelectric.http.urlandtheHTTPURLvaluetothe contextrootofGlue.Forexample:
<init-param> <param-name>electric.http.url</param-name> <param-value>http://localhost:8004/glue</param-value> </init-param>
202
Addthefollowinglistenertothe<webapp>element:
<listener> <listener-class>com.webmethods.fabric.integration.glue. FabricContextListener</listener-class> </listener>
Deploy the WebLogic Plug-in

Important! YoudeploytheWebLogicPluginusinganApacheAntscript.Ifyoudonot haveaseparateinstallationofAnt,youcanusetheAntlibrarypackagedwithWebLogic atbea-home/weblogic81/server/bin/ant. 1 OntheWebLogichostmachineonwhichyouinstalledtheWebLogicPlugin,goto theServicenet_directory\misc\plugins\weblogicdirectoryandopenthe wlplugindeploy.propertiesfileinatexteditor.Editthefileasshownbelow. Set this property... snet.plugin.jars.dir bea.home weblogic.domain weblogic.username weblogic.password (requiredonlyifyou startWebLogicin productionmode) 2 3 4 5 Saveandclosethefile. OpenacommandwindowandgototheServicenet_directory\misc\plugins\weblogic directory. Runthecommandant usage.Thedescriptionsforarebuildcommandanda deploymentcommandsappearinthewindow. Updatethesnetwlplugin.warfilewiththepropertiesyoujustsetbyrunningthis command:
ant rebuild.wlplugin
...to this value AbsolutepathtotheServicenet_directory/libdirectory WebLogicisinstalleddirectory Nameofthedomaintousefortheplugin WebLogicadministratorusername WebLogicadministratorpassword
Deploythepluginbyrunningthiscommand:
ant deploy.wlplugin
203
Deploy and Configure the Microsoft .NET Publisher

1 Deploythepublisherasfollows: a b OntheMicrosoft.NETserverhostmachineonwhichyouinstalledtheMicrosoft .NETPublisher,gototheServicenet_directory\misc\pluginsdirectory. StarttheMicrosoft.NETPublisherinstallationwizardbydoubleclickingthe ServicenetContainerManager.msifile. Note: Inthewizard,the.NETserveriscalledInternetInformationServices(IIS), anditsportistheIISport. c d 2 ClickNextuntilyoureachtheSelect Installation Addresspanel.InthePortbox,set thevaluetotheportthe.NETserver(IIS)uses. ClickNextuntilyoureachtheInstall Completepanel,andthenclickClose.
Configurethepublisherfortodiscovertheregistryasfollows: a b Openthe.NETserver(IIS)andselectthenewservicenetvirtualdirectory.Under thevirtualdirectory,opentheweb.configfile. GototheDISCOVERYsection.Thenextstepdependsonwhetheryouwantto usesubnetorWANlocators. Ifyouwanttousesubnetlocators,underthesubnetlocator,setthe<port> elementtotheportyouwanttheServicenetcomponentstousefortheping. Forexample:

<locator> <name>subnet</name> <constructor> <class>Webmethods.Fabric.Services.Registry.Locators.Subnet. SubnetLocator</class> <args> <port>9030</port> <maxWait>2000</maxWait> </args> </constructor> </locator>
204
IfyouwanttouseWANlocators,commentouttheentiresubnetlocator. UndertheWANlocator,setthevalueofthe<url>parametertotheURLof theregistry.Forexample:

<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>
Saveandclosethefile,thenrestartallServicenetcomponents.
Configure Registry Discovery

DependingonhowyouinstalledServicenet,youmightneedtoconfigurediscoveryofthe registryforyourServicenetcomponents.Servicenetcomponentscanusesubnetlocators, staticlocators,orWANlocatorstolocatetheregistry. Locator Subnet Description Whenconfiguredtouseasubnetlocator,aServicenetcomponent,atstar tup,sendsaUserDatagramProtocol(UDP)pingonaspecifiedportoutto thesubnet.TheregistrycomponentoranyotherServicenetcomponent thathasalreadystartedandconnectedtotheServicenetregistry,can respondtothepingandprovidetheregistrysURLtotheServicenetcom ponentthatsenttheping.InthiswaytheServicenetcomponentsdynami callydiscoverandbindtotheregistry. ThesubnetlocatoridentifiestheportonwhichtosendtheUDPping.Any Servicenetcomponentthatresideswithinthesamesubnetastheregistry canuseasubnetlocator. Static StaticlocatorscontaintheURL(host/port)oftheregistry.AllServicenet componentsexcepttheMicrosoft.NETPublishercanuseastaticlocatorto locatetheregistry. WANlocatorscontaintheURL(host/port)oftheregistry.Onlythe Microsoft.NETPublishercanuseaWANlocatortolocatetheregistry.
WAN
Note: YouconfiguretheMicrosoft.NETPublisherdifferentlyforregistrydiscoverythan theotherServicenetcomponents.Forinstructions,seeDeployandConfigurethe Microsoft.NETPublisheronpage 204.
205
Usethefollowingtabletodeterminewhatyouneedtodo. If you... InstalledallSer vicenetcompo nentsonone machineordis tributedSer vicenetover multiple machines And you want to use... Subnetlocators andthedefault Subnetlocator discoveryport 9030 Staticlocators andthedefault registryport8088 Staticlocators andanon defaultregistry port You must... Donothing.Allcomponentsareconfigured bydefaulttousesubnetlocatorsonthe defaultport.
Configureallcomponentsexcepttheregistry tousestaticlocatorsratherthansubnetloca tors.SeeConfigureServicenetComponentto UseStaticLocatorsonpage 207. Configureallcomponentsexcepttheregistry tousestaticlocatorsandtousethenon defaultport.SeeConfigureServicenetCom ponenttoUseStaticLocatorsonpage 207. Changetheregistrytousethenondefault port;seeChangetheDefaultRegistryPort onpage 210.
InstalledallSer vicenetcompo nentsonone machine DistributedSer vicenetcompo nentsover multiple machines
Subnetlocators andanon defaultportyou specifiedduring installation Subnetlocators andanon defaultportyou specifiedduring installation
Configureallpluginsandintermediariesto usethenewport.SeeConfigureServicenet ComponentstoUseSubnetLocatorson page 208. Configureallcomponentstousethenon defaultport.SeeConfigureServicenet ComponentstoUseSubnetLocatorson page 208.
206
Configure Servicenet Component to Use Static Locators

1 IfMywebMethodsServerisoneoftheServicenetcomponentsyouneedtoconfigure, shutitdownasfollows: System Windows Action a b c UNIX a b OpentheControlPanelanddoubleclicktheAdministrative Tools icon. IntheAdministrative Toolswindow,doubleclicktheServicesicon. IntheServiceswindow,doubleclickthe webMethods Portal Server service,thenclickStop. OpenacommandwindowandgotothePortal/server/ default/bindirectory. Runthiscommand:
shutdown.sh
Openthesnetclientconfig.xmlfileforeachServicenetcomponentwhosestatic locatoryouwanttoconfigure.Thefileisinthelocationsbelow. Note: Somecomponentshaveasnetclientdefaultconfig.xmlfile.Ifyoueditthis versionofthefile,savetheeditedversionassnetclientconfig.xml.Whenboth versionsofthefileexistonacomponent,thecomponentusesthesnetclient config.xmlfile. Component Controller MywebMethods Server Intermediary GluePlugin Location of the configuration file Optimize_directory\controller\webapps\ROOT\WEB INF\snetclientconfig.xml Portal_directory\lib\snetclient.jar(containssnetclient defaultconfig.xml) webMethods_directory\Servicenet\conf\snetclientconfig.xml SeeDeployandConfiguretheGluePluginonpage 201to determinewherethesnetclientdefaultconfig.xmlfileisfor theGluePlugin. weblogic_domain.dir/servicenet/snetclientdefaultconfig.xml IntegrationServer_directory\packages\WmSnetPlu gin\web\WEBINF\snetclientconfig.xml
WebLogic Plugin Integration ServerPlugin
207
Gotothe<discovery>sectionandsetthe<useLocator>elementtostatic.For example:
<discovery> <noPath>fabric://failover&monitor</noPath> <useLocator>static</useLocator> <useSignatures>true</useSignatures>
Important! Donotchangethedefaultlocatorontheregistrytostatic.Components usingstaticlocatorscanconnecttotheregistryevenwhenthelocatorontheregistry issettosubnet.However,ifsomeServicenetcomponentsusesubnetlocators, configuringtheregistryforstaticlocatorscanpreventthosecomponentsfrom connectingtotheregistry. 4 Gotothe <locator>sectionandsetthe<url>elementtothehostandportforthe registry.Forexample:

<locator> <name>static</name> <constructor> <class>com.webmethods.fabric.services.registry.locators .StaticLocator</class> <args> <url>http://registryhost:8088/snet</url> </args> </constructor> </locator>
Saveandclosethefile,thenrestartallServicenetcomponents.
Configure Servicenet Components to Use Subnet Locators

1 IfMywebMethodsServerisoneoftheServicenetcomponentsyouneedtoconfigure, shutitdownasfollows: System Windows Action a b c UNIX a b OpentheControlPanelanddoubleclicktheAdministrative Tools icon. IntheAdministrative Toolswindow,doubleclicktheServicesicon. IntheServiceswindow,doubleclickthe webMethods Portal Server service,thenclickStop. OpenacommandwindowandgotothePortal/server/ default/bindirectory. Runthiscommand:
shutdown.sh
208
Openthesnetclientconfig.xmlfileforeachcomponentyouwanttoconfiguretouse subnetlocators.Thefileisinthelocationsindicatedbelow. Note: Somecomponentshaveasnetdefaultclientconfig.xmlfile.Ifyoueditthisfile, savetheeditedversionassnetclientconfig.xml.Whenbothversionsofthefileexist onacomponent,thecomponentusesthesnetclientconfig.xmlfile. Component Registry Controller Myweb Methods Server Intermediary GluePlugin Location of the configuration file Servicenet_directory\conf\snetclientconfig.xml Optimize_directory\controller\webapps\ROOT\WEBINF\ snetclientconfig.xml Portal_directory\lib\snetclient.jar(containssnetclientdefault config.xml) Servicenet_directory\conf\snetclientconfig.xml SeeDeployandConfiguretheGluePluginonpage 201to determinewherethesnetclientdefaultconfig.xmlfileisforthe GluePlugin weblogic_domain.dir/servicenet/snetclientconfig.xml IntegrationServer_directory\packages\WmSnetPlugin\web\ WEBINF\snetclientconfig.xml
WebLogic Plugin Servicenet Package 3
Gotothe<discovery>sectionandmakesurethe<useLocator>elementissetto subnet.Forexample:
<discovery> <noPath>fabric://failover&monitor</noPath> <useLocator>subnet</useLocator> <useSignatures>true</useSignatures>
209
Gotothe<locator>sectionandsetthe<port>elementtotheportyouwantthe componenttouseforpinging.Forexample:
<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! YoumustconfigureallServicenetcomponentstousethesameport. 5 Saveandclosethefile,thenrestartallServicenetcomponents.
Change the Default Registry Port

Bydefault,theServicenetregistrylistensfordatafromclientsonport8088.Ifyouhave otherapplicationsthatusethatport,changetoanotherportasdescribedbelow. Important! MakethischangebeforeyoustartServicenetforthefirsttime.Servicenetloads systemservicesintotheregistry,andthesesystemservicesaretiedtotheregistryport.If youchangetheportafterstartingServicenet,youwillhaveduplicateentriesinyour Servicenetdatabase,andServicenetmightbeunabletoloadsomeservices.Ifyoudropthe Servicenetdatabasetocleanuptheregistry,youwillloseyourconnectionsto intermediariesinyourgrid,includingthedefaultintermediarythatresideswiththe registry. 1 2 OntheServicenetregistryhostmachine,gotothewebMethods_directory\Servicenet\ confdirectoryandopentheservicenetconfig.xmlfileinatexteditor. Gotothe<servers>sectionandchangetheportnumberinthe<url>elementtothe portyouwanttheregistrytouse.Forexample:
<servers> <http> <url>http://localhost:8099/snet</url>
3 4
Saveandclosethefile. IfyouhavenotyetupdatedServicenetcomponentsthatareusingstaticlocatorsfor registrydiscoverytousethenewregistryport,seeConfigureServicenetComponent toUseStaticLocatorsonpage 207.
210
Configure Servicenet Components to Communicate with My webMethods Server

AllServicenetcomponentsexceptthedatahandlercommunicatewithMywebMethods Server.TheconfigurationfileforeachcomponentcontainstheMywebMethodsServer hostnameandportnumber.DependingonhowyouinstalledServicenetcomponents, youmighthavetoaddormodifythisinformationforoneormorecomponents.Usethe followingtabletodeterminewhattodo. If you... Installedtheregis try,controller,data handler,andMy webMethods Serveronone machine And you... Keptthedefault MywebMethods Serverport8080 Specifiedanon defaultportfor MywebMethods Serverduring installation You must... AddtheMywebMethodsServerhostname totheconfigurationfilesforpluginsand intermediariesinstalledonothermachines. AddtheMywebMethodsServerhostname andnondefaultportnumbertothe configurationfilesforpluginsand intermediariesinstalledonothermachines. Addthenondefaultportnumbertothe configurationfilefortheregistry. AddtheMywebMethodsServerhostname totheconfigurationfilesfortheregistry, plugins,andintermediaries. AddtheMywebMethodsServerhostname andnondefaultportnumbertothe configurationfilesfortheregistry,plugins, andintermediaries.
DistributedSer vicenetovermulti plemachines,or areusingaprevi ouslyinstalledMy webMethods Server
Keptthedefault MywebMethods Serverport8080 Specifiedanon defaultportfor MywebMethods Serverduring installation
Note: Youdonothavetomodifytheconfigurationfilesforthecontrollerordatahandlerin anycasebecausetheinstallerautomaticallymodifiesthosefilestocontainthecorrectMy webMethodsServerhostnameandportnumber.
211
ToaddtheMywebMethodsServerhostnameandportnumbertotheconfigurationfiles forServicenetcomponents,dothefollowing: 1 Opentheglueconfig.xmlfileforeachcomponentwhoseMywebMethodsServerhost orportinformationyouneedtochange.Thefileisinthelocationsindicatedbelow. Component Registry Intermediary IntegrationServer Plugin GluePlugin WebLogicPlugin 2 File Location Servicenet_directory\confdirectory Servicenet_directory\confdirectory IntegrationServer_directory\packages\ WmSnetPlugin\web\WEBINFdirectory webapp_directory\WEBINFdirectory Withinthesnetwlplugin.warfile
Gotothe<realm>sectionandsetthe<portalURL>parametertothecorrectMy webMethodsServerhostandport.Forexample:
<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>
212
Complete the Workflow Installation

Set Up the Workflow Database
CreateaseparatetablespacefortheWorkflowdatabasecomponentinyourdatabase. ThencreateadatabaseuserandpasswordfortheWorkflowServerstousetologintothe database.Thedatabaseuserneedspermissiontocreate,alter,anddroptablesinthe WorkflowServertablespace.
Set Up Secondary Workflow Servers to Access Encryption Passwords

IfyouinstalledsecondaryWorkflowServersinadditiontothecentralWorkflowServer, youmustsetupthesecondaryWorkflowServerstoaccessencryptionpasswords maintainedbythecentralWorkflowServer. Manuallycopythepo.propertiesfileandtheauthentication.propertiesfilefromthe centralWorkflowServerinstallationtocorrespondingdirectoriesineverysecondary WorkflowServerinstallation.Thepo.propertiesfileislocatedintheWorkflowServer installationdirectoryandtheauthentication.propertiesfileislocatedintheWorkflow Server_directory\etcdirectory.
Set Up Workflow Servers for Automatic Startup on Solaris, HP-UX, AIX, and Linux Systems
IfyouinstalledaWorkflowServeronaSolaris,HPUX,AIX,orLinuxsystemandyou wanttheWorkflowServertostartautomaticallywhenyoustartthesystem,gotothe WorkflowServer_directory/bindirectoryandrunthiscommand:
./bootsc.sh
Set Up Workflow Servers for Automatic or Manual Startup on Windows Machines

Bydefault,WorkflowServerisinstalledasaWindowsserviceonWindowssystems. However,ifyouinstalledmultipleWorkflowServersonthesamemachine,onlythelast installedWorkflowServerisaWindowsserviceandstartsautomatically;thepreviously installedWorkflowServersareWindowsapplicationsthathavetobestartedmanually. YoucanchangetheWorkflowServersthatareWindowsapplicationsthathavetobe startedmanuallytorunasWindowsservicesthatstartautomaticallybycreatingservice entriesforthemintheWindowsregistry.YoucanalsochangeaWorkflowServerthatis runningasaWindowsservicetobeaWindowsapplicationinstead.
213
Change a Workflow Server from a Windows Application to Run as a Windows Service

1 2 3 IftheWorkflowServerisrunning,shutitdown. IftheWindowsServiceswindowisopen,closeit. Openacommandwindow,gototheWorkflowServer_directory/bindirectory,andtype thiscommandonasingleline,withoutanyreturnorlinefeedcharacters:
WorkflowSvc.exe -i -Djava.class.path=Workflow Server_directory\bin\SrvcWorkflow.jar wrkdir=Workflow Server_directory servicename=service_name displayname=display_name
Usethesamenameforservice_name(nameoftheservice)anddisplay_name(name underwhichtheserviceisdisplayedintheServiceswindow),andmakethename uniqueonthecurrentmachine.YoumightwanttonameeachWorkflowServerbased onaportituses(forexample,WorkflowServer_port_6001, WorkflowServer_port_6002,andsoon).Usequotationmarkstoencloseanyvariable thatincludesspaces.
Change a Workflow Server that Runs as a Windows Service to a Windows Application

1 2 IftheWindowsservicefortheWorkflowServerisrunning,opentheWindows Serviceswindow,stoptheservice,andthenclosethewindow. Openacommandwindow,gototheWorkflowServer_directory/bindirectory,andtype thiscommandononeline:
WorkflowSvc.exe -r servicename=service_name displayname=display_name
Usequotationmarkstoencloseanyvariablethatincludespaces.
Enable a Workflow Server on a Red Hat Linux System to Use an SSL-Enabled Broker
IfyouwanttouseanSSLenabledBrokerwithaWorkflowServerthatisinstalledona RedHatLinuxsystem,youmustinstallacompatibilitypackagefromRedHat,asfollows: 1 2 3 GototheRedHatWebsiteanddownloadthecompatlibstdc++7.32.96.128.i386.rpm package. Ifthepackagenamecontainsbrackets([]),removethebracketsfromthename. Gotothedirectorytowhichyoudownloadedthepackageandrunthiscommand:
rpm -i compat-libstdc++-7.3-2.96.128.i386.rpm
214
Configure Workflow Servers

ToconfigureaWorkflowServer,youruntheWorkflowConfigurator.TheWorkflow ConfiguratorguidesyouthroughtheprocessofconfiguringaWorkflowServer. IfyouinstalledtheWorkflowServeronaWindowssystemoronaUNIXorLinuxsystem thathasanXWindowsenvironment,youcanusethegraphicalWorkflowConfigurator. Thegraphicalconfiguratorshowssetsofquestionsonmultiplepanelsandsavesthe configurationinformationyouenteroneachpanelwhenyouclickNext.Youcanclick Cancelonanypaneltoexittheconfiguratorwithoutsupplyinganymoreinformation. However,youmustcontinuetothelastpaneltocompletetheconfigurationatsomepoint beforeyoucanstarttheWorkflowServer. IfyouinstalledtheWorkflowServeronaUNIXorLinuxsystemthatdoesnothaveanX Windowsenvironment,youcanusethenongraphicalWorkflowConfigurator.Thenon graphicalconfiguratorpromptsyoutoanswerquestionsthatappearinsetsthat correspondtothegraphicalconfiguratorspanels;currentsettingsordefaultsappearin brackets[]attheendofeachquestion.Theconfiguratorsavestheconfiguration informationyouenterforeachquestionsetwhenyoutypeNafterthelastquestioninthe set.Ifyouwanttodisplayhelpinformationforthecurrentquestionset,typeH.Ifyou wanttoreenteryouranswerstothecurrentquestionset,typeR.Ifyouwanttogobackto thepreviousquestionsetwithoutsavingyourcurrentanswers,typeB.Ifyouwantto clearafield,typetwodoublequotationmarks().YoucantypeXatanypointtoexitthe configuratorwithoutsupplyinganymoreinformation.However,youmustrespondtoall thequestionsetstocompletetheconfigurationatsomepointbeforeyoucanstartthe WorkflowServer.Typeallpathswithoutquotationmarks.
Start the Workflow Configurator

StarttheWorkflowConfiguratorasfollows: System Windows UNIXor Linux Action OntheStartmenu,gotoPrograms Configurator. webMethods Tools Workflow
Tostartthegraphicalconfigurator,gototheWorkflowServer_directory/bin directoryandenterthiscommand:
./configure.sh
Tostartthenongraphicalconfigurator,gototheWorkflow Server_directory/bindirectoryandenterthiscommand:
./configure.sh -nogui
TheConfiguratordisplaystheJDK Parameterspanel.
215
Identify the JDK to Use

1 Bydefault,theWorkflowServerusestheJDKthatwasinstalledbytheinstaller;the configuratorshowsthepathtothatJDKintheJDK Pathbox.Ifyouwanttoredirectthe WorkflowServertouseadifferentJDKinstead,providethepathtothatJDK.ForJDK requirementsforWorkflowServers,seethewebMethodsSystemRequirements. ClickNext.TheconfiguratordisplaystheCentral Host Parameterspanel.
Identify the Central Workflow Server and the Type of Authentication to Use
1 CheckthespecificationsfortheWorkflowServercentralhostnameandportandthe RMIregistryportthatyouprovidedinthewebMethodsInstaller(seeConfigure WorkflowServeronpage 123)andeditthemifnecessary.Makesuretheports specifiedarenotinusebyanyotherprocess;forexample,onWindowsXP Professionalsystems,port5000isreserved. IfyouareconfiguringthecentralWorkflowServer,clickMasternexttothecentralhost name.IfyouareconfiguringasecondaryWorkflowServer,clickSlave. ClickNext.IfyouclickedMaster,theconfiguratordisplaystheAuthentication and Security Parameterspanel;gotothenextstep,below.IfyouclickedSlave,theconfigurator displaystheConfiguration Completepanel;gotoCompletetheConfigurationon page 223. 3 IfyouwanttoenableSSLfortheWorkflowServersotheWorkflowServercanencrypt Workflowclientlogindata,selecttheSSL EnabledcheckboxintheSSL Parametersarea andprovidethefollowinginformation: Box Keystore File Keystore Password Certificate File Entry FullyqualifiedpathtotheSSLkeystorefile.Thefilemustbein PKCS#12format. Passwordforthekeystorefile. FullyqualifiedpathtotheX509certificatefileforWorkflow clients. YoumustalsoaddtheX509certificatetothekeystorefile. Note: Youcanonlyspecifyonecertificateatatime.
IfyoudonotwanttoenableSSLfortheWorkflowServer,cleartheSSL Enabledcheck box.
216
IntheLocal or Site-central Authentication Parametersarea,choosethetypeof authenticationsystemtouse. Authenticate Workflow users using... Workflow Server
Action ClickLocaltouseWorkflowServerslocalstoreofuseraccounts. IfyouhaveinstalledwebMethodsproductsthatdonot communicatewithMywebMethodsServer,youmightwantto usethisoptionratherthanusingMywebMethodsServerfor authentication(seebelow). 1 2 3 ClickSite-central. IntheURL for Authentication Service JAR Archivebox,typethe URLforthejararchivefileforyourauthenticationsystem. Workflowclientsuseacachingmechanismtostore frequentlyuseddata.IntheCaching Methodarea,specifythe cachingmechanismtouse.Ifyourauthenticationsystemcan notifytheWorkflowServerwhenvalueschange,click Notification.Ifyourauthenticationsystemcannotnotify WorkflowServer,clickTimeoutand,intheCache Timeoutbox, specifyhowoftenWorkflowServershouldrequestan update.
Yourown authentication system
Note: Ifyoudonothaveanauthenticationsystembutwanttoset oneupsoyoucanuseitwithWorkflow,contactwebMethods CustomerCareforinstructions.
217
Authenticate Workflow users using... My webMethods Server
Action IfyouhaveinstalledotherwebMethodsproductsthat communicatewithMywebMethodsServer,youmightwantto usethisoptionforsimplicityratherthanusingWorkflowServer forauthentication(seeabove).YouwillhavetomakesureMy webMethodsServeralwaysrunswhenyourunWorkflowifyou choosethisoption. 1 GotoMywebMethodsandaddWorkflowusers.For instructions,seetheMywebMethodsServerAdministrators Guide. IntheWorkflowconfigurator,clickMy webMethods. IntheProtocollist,clicktheprotocoltouseforauthentication. IfyouwantMywebMethodsServertoauthenticateusinga standardconnection,clickhttp.IfyouwantMywebMethods Servertoauthenticateusingasecureconnection,selecthttps. YourselectionsintheSSL Parameters sectiondonotaffect yourselectionhere. IntheHost,Port,User,andPasswordboxes,enterthevalues neededtoconnecttoMywebMethodsServer.Thehostand portaretheJetty HTTP Listener Host/Portyouspecifiedinthe PortalServerConfigurator.Thedefaultusernameand passwordareAdministratorandmanage. Workflowclientsuseacachingmechanismtostore frequentlyuseddata.IntheCache Timeoutbox,specifyhow oftenWorkflowServershouldrequestanupdate.
2 3
TheWorkflowServerwillcheckitsconnectiontotheWorkflowAuthenticationServer periodicallytomakesureclientsessionsareconnectedandtocleanupsessionsthat didnotendaftertheuserloggedout.TheSession Keep Alive Settingsarealetsyou customizethisfunctionality.Completetheboxesasfollows: Box Keep Alive Interval (minutes) Entry Numberofminutestowaitbetweenpingsofauthentication sessionclientswithregisteredlisteners.Thedefaultis60minutes.
218
Box Retries Inactivity Timeout (minutes)
Entry Numberoftimestoretrypingingdeadauthenticationsession clientswithregisteredlisteners.Thedefaultis3. NumberofminutesafterwhichtheWorkflowServerwill automaticallylogoutadeadauthenticationsessionclientwith registeredlistenerifthesessionhasnotrecovered.Thedefaultis 30.
ClickNext.TheconfiguratordisplaystheBroker Parameterspanel.IfyouenabledSSL forWorkflowServer,theconfiguratorplacestheSSLcertificatefileyouidentifiedin theCertificate FilefieldintheWorkflowServer_directory\lib\securitydirectory.The WorkflowclientandsecondaryWorkflowServersautomaticallypullthisfileatlogin timeandplaceacopyintheirsecuritydirectories.
Identify the Broker to Use

1 TypethenameoftheBrokertowhichyouwanttheWorkflowServertoconnect,the nameofthemachineonwhichtheBrokerresides,andtheporttheBrokerisusing. Important! MakesuretheBrokeryouidentifyonthispanelisrunning.Whenyouclick Next,theconfiguratorwilltrytovalidatetheBrokerparametersyouhaveentered;if theBrokerisnotrunningyouwillnotbeabletocontinue.Thenameofthedefault BrokerisBroker#1. TheconfiguratorassumestheBrokerisusingthedefaultport6849.IftheBrokeris usingadifferentport,youmustspecifyit. IftheBrokerisSSLenabled,selecttheBroker SSL Enabledcheckboxandcompletethe boxesbelow. Box Broker SSL Certificate Pathname Broker SSL Password Broker SSL Distinguished Name Enable Broker SSL Data Encryption Entry FullyqualifiedpathtotheBrokersSSLcertificatefile.
Passwordforthecertificatefile. Ifyouwanttoenablebothserversideandclientside authentication,clickthedistinguishednamespecifiedinthe Brokerscertificatefile.Ifyouwanttoenableserverside authenticationonly,acceptthedefaultNONE. Bydefault,anSSLenabledBrokerwillnotencryptWorkflowdata. IfyouwanttheBrokertoencryptWorkflowdata,selectthecheck box.
219
ClickNext.TheconfiguratordisplaystheSMTP Parameterspanel.
Enable the Workflow Server to Send E-mail Notifications

1 IfyouwanttoenabletheWorkflowServertosendemailnotifications,completethe boxesbelow. Box SMTP Host Name SMTP Port SMTP User SMTP Password SMTP Disconnect Timeout (seconds) Administrator E-mail 2 Entry Nameofthemachinethathoststhemailserver. Numberoftheportthemailserveruses. UsernamefortheWorkflowServertousetologintothemail server. PasswordfortheSMTPuser. IfyouwanttheWorkflowServertodisconnectfromthemail serverafteracertainperiodoftime,selectthecheckboxand specifythenumberofseconds.IfyoudonotwanttheWorkflow Servertodisconnect,clearthecheckbox. EmailaddressfortheusertowhomtheWorkflowServerwill sendmessagesaboutproblems.
ClickNext.TheconfiguratordisplaysthewebMethods Monitor Database Parameterspanel.
Configure the Workflow Server to Write to the Process Audit Log Database
1 IfyouwanttouseMonitortomonitorWorkflowprocesses,youmustsetup WorkflowServertowriteprocessdatatotheProcessAuditLog.Completetheboxes below. Box Database Type JDBC Driver Class Entry TypeofdatabaseyouareusingfortheProcessAudit Log. FullyqualifiednameoftheJavaclassfortheJDBCdriver thattheWorkflowServerwillusetocommunicatewith thedatabase.
220
Box URL for Database Connection
Entry URLforthedatabase,asfollows: URL Oracle

Default Port
1521

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
1433
Sybase
5000
DB2 UDB
50000
Database User Name Database Password 2
DatabaseuserfortheWorkflowServertousetologinto thedatabase.UserthedatabaseuseryoucreatedinSet UptheWorkflowDatabaseonpage 213. Passwordforthedatabaseuser.
Ifyouwanttomakesureyoucanconnecttothespecifieddatabase,clickTest.The configuratorindicateswhethertheconnectionwassuccessful.Iftheconnectionwas notsuccessful,supplyadifferentsetofparametersandclickTestagain. ClickNext.TheconfiguratordisplaystheDatabase Configuration Parameterspanel.
221
Configure the Workflow Server to Write to the Workflow Database

1 2 MakesureyouhavecompletedthetasksinSetUptheWorkflowDatabaseon page 213. ConfiguretheWorkflowServertowriteWorkflowprocessmodelstoitsdatabaseby completingtheboxesbelow.Ifnecessary,askyourdatabaseadministratortogrant youthepermissionsneededtocompletesomeoftheboxesonthepanel. Box Database Type JDBC Driver Class URL for JDBC Driver(s) Entry Typeofdatabaseyouareusing. FullyqualifiednameoftheclassfortheJDBCdriverthatthe WorkflowServerwillusetocommunicatewiththedatabase. URLofthejarfilethatcontainstheJDBCdriversthattheWorkflow Serverwillusetocommunicatewiththedatabase.Theconfigurator copiesthejarfileyouidentifytotheWorkflowServer_directory\lib directory. URLforthedatabase. URL Oracle
URL for Database Connection
Default Port
1521
SQL Server
1433
DB2 UDB
50000
DB2 UDB for AS/400

446
Note: AlternateIdmustmatchtheschemainwhich youcreatedtheWorkflowdatabasetables.
222
Box Database User Name Database Password 3
Entry DatabaseuserfortheWorkflowServertousetologintothe database.UserthedatabaseuseryoucreatedinSetUpthe WorkflowDatabaseonpage 213. Passwordforthedatabaseuser.
ClickNext.TheconfiguratorcreatesandinitializesthetablesintheWorkflow database,thendisplaystheBroker, Database, and Password Initializationpanel.
Synchronize the Workflow Server with Your Broker

1 2 IfyouwanttocleartheBrokersqueuesanddropyourdatabasetables(forexample, becausedatahasbeencorrupted),selecttheDrop Database Tablescheckbox. IfyouchoseLocal or Site-centralauthenticationontheAuthentication and Security Parameterspanel,intheInternal Passwordbox,typethepasswordforWorkflowServer touseinternallytoencryptanddecryptthedataitstoresinitsdatabase. ClickNext.IfyoudidnotchoosetocleartheBrokersqueuesanddropyourdatabase tables,theconfiguratorsynchronizestheWorkflowServerwithyourBrokerand updatesyourBrokerdocumenttypes. IfyoudidchoosetocleartheBrokersqueuesanddropyourdatabasetables,the configuratordisplaysawarningthatyouareabouttodeleteallexistingdatabase recordsandaskswhetheryouwanttocontinue.ClickYes,thenclickNext. Iftheinformationyouhaveenteredisaccurateforyoursystem,theconfigurator displaysaconfirmationmessagetellingyouthatdatabaseschemashavebeencreated orupdated.Iftheinformationyouenteredisnotaccurate,theconfiguratordisplays anerrormessage.ClickOK.TheconfiguratordisplaystheConfiguration Completepanel.
Complete the Configuration

1 2 ClickDone.Theconfiguratorcloses. GototheWorkflowServer_directory\logdirectoryandopentheconfigurelogn.txtfile toseeifanyerrorsoccurredduringconfiguration.Ifyoufinderrormessages,seethe troubleshootinginformationforWorkflowonthewebMethodsAdvantageWebsiteat http://advantage.webmethods.com/cgibin/advantage/targetedLogin.jsp.
223
Configure Workflow to Use SSL

IfyouwantWorkflowtouseSSLtocommunicate,youmustcompletesomeorallofthe tasksbelow.
Configure Workflow Clients to Connect to an SSL-Enabled Broker

IfyouwanttouseanSSLenabledBrokerwithWorkflow,youmustconfigureeach WorkflowclientyouinstalledtoconnecttotheBroker. 1 StarttheWorkflowclientasfollows: System Windows Linux Action OntheStartmenu,gotoPrograms Workflow. webMethods webMethods
GototheWorkflowclient_directory/bindirectoryandrunthe clientmgr.shscript.
2 3
OntheOptionsmenu,clickBroker Certificates. IftheBrokerisSSLenabled,selecttheBroker SSL Enabledcheckboxandcompletethe boxesbelowwiththesameinformationyouenteredintheWorkflowConfigurator whenyousetuptheWorkflowServer(seeIdentifytheCentralWorkflowServerand theTypeofAuthenticationtoUseonpage 216). Box Broker SSL Certificate Pathname Broker SSL Password Broker SSL Distinguished Name Enable Broker SSL Data Encryption Entry FullyqualifiedpathtotheBrokersSSLcertificatefile.
Passwordforthecertificatefile. Ifyouwanttoenablebothserversideandclientside authentication,clickthedistinguishednamespecifiedinthe Brokerscertificatefile.Ifyouwanttoenableserverside authenticationonly,acceptthedefaultNONE. Bydefault,anSSLenabledBrokerwillnotencryptWorkflowdata. IfyouwanttheBrokertoencryptWorkflowdata,selectthecheck box.
RepeatthesestepsforeveryWorkflowclient.
224
Set Up Access Control Lists for an SSL-Enabled Broker

WhenyouuseanSSLenabledBrokerwithWorkflow,bothSSLenabledandnonSSL enabledWorkflowServers,Workflowclients,andWorkflowAPIapplicationscanconnect totheBroker.IfyouwanttorequirethatWorkflowapplicationsconnecttotheBroker usingSSL,youmustsetupaccesscontrollists(ACLs)andassignthefollowingWorkflow clientgroupstotheACLs: WFClassrv WFClassrvClients DCS workFlowClients BusinessLog WorkflowMonitor ProcessServer WFPortfolio WFPortfolioClients Forinstructionsonsettingupaccesscontrollists,seethewebMethodsBrokerAdministrators Guide.
Configure the Workflow Servlet to Connect to an SSL-Enabled Workflow Server and Broker
IfyouwanttousetheWorkflowServletwithanSSLenabledWorkflowServerand Broker,youmustconfiguretheservletengine. Configure Integration Servers Internal Tomcat Servlet Engine IfyouareusingIntegrationServerasyourservletengine,youinstalledtheWorkflow Servletpackageduringinstallation.ThispackageletsyouuseIntegrationServersinternal Tomcatservletengine.MakesuretheWorkflowServletpackageisenabled.Todoso,open IntegrationServerAdministrator,gotothePackages Managementpage,andlookforthe WmWFServletpackage.Ifthepackageisdisabled,locatetherowforthepackageinthe table,thenclickYesintheEnabledcolumninthatrow.TheYeschangestoNo. IfIntegrationServerandWorkflowServerareinstalledonthesamemachine,dothe following: 1 GototheIntegrationServer_directory\bindirectoryandopentheserver.bator server.shfileinatexteditor.Locatethe%JAVA_RUN%lineandaddtheseparametersto it:
-Dcom.wm.security.directory=%Workflow Server_directory%\security
225
-Dbroker.sslcertfile=%Workflow Server_directory%\security\certificate_file -Dbroker.sslpassword=certificate_file_password -Dbroker.sslencrypted=true_or_false
Ifyouwanttouseclientsideauthentication,alsoaddthisparameter:
-Dbroker.ssldname=CN=cn_info,O=organization,L=location,ST=state,C=country
Saveandclosethefile. 2 RestartIntegrationServer.
IfIntegrationServerandWorkflowServerareinstalledondifferentmachines,dothe following: 1 2 GototheIntegrationServer_directoryandcreateadirectorynamedsecurity. MakeacopyoftheWorkflowServerSSLcertificatefileyouidentifiedinthe WorkflowConfiguratorandplacethecopyintheIntegrationServer_directory\security directory. MakeacopyoftheBrokerSSLcertificatefileyouidentifiedintheconfiguratorand placethecopyintheIntegrationServer_directory\securitydirectory. GototheIntegrationServer_directory\bindirectoryandopentheserver.bator server.shfileinatexteditor.Locatethe%JAVA_RUN%lineandaddtheseparametersto 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
3 4
-Dbroker.ssldname=CN=cn_info,O=organization,L=location,ST=state,C=country
Saveandclosethefile. 5 RestartIntegrationServer.
Configure the Apache Tomcat Servlet Engine 1 InstalltheWorkflowServletinApacheTomcat,asfollows: a b c d 2 3 ShutdownTomcat. GototheWorkflowServerinstallationdirectory. CopytheWorkflow.warfileintotheTomcat_directory\webappsdirectory. IfyouareinstallingtheWorkflowServletoveranearlierverserion,deletethe WorkflowdirectoryintheTomcat_directory\webappsdirectory.
Gotothe%CATALINA_HOME%directoryandcreateadirectorynamedsecurity. MakeacopyoftheWorkflowServerSSLcertificatefileyouidentifiedinthe configuratorandplacethecopyinthe%CATALINA_HOME%\securitydirectory.
226
4 5 6
MakeacopyoftheBrokerSSLcertificatefileyouidentifiedintheWorkflow Configuratorandplacethecopyinthe%CATALINA_HOME%\securitydirectory. Openthecatalina.batorcatalina.shfileinatexteditor. SetthePATHvariabletocontainthepathtotheSSLnativelibraries.OnWindows systems,thepathisTomcat_directory\webapps\Workflow\WEBINF\lib\Windows; youwouldsetthePATHvariableasfollows:

set PATH=%PATH%;%CATALINA_BASE%\webapps\Workflow\WEB-INF\lib\Windows
Onotheroperatingsystems,locatethecorrespondingdirectoryandsetthepath accordingly. 7 Locatetheset CATALINA_OPTS=%CATALINA_OPTS%lineandaddtheseparametersto 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
-Dbroker.ssldname= CN=cn_info,O=organization,L=location,ST=state,C=country
ToincreasethedebuglevelfortheWorkflowclient,locatetheset JAVA_OPTS=line andsetitasfollows:

set JAVA_OPTS=-Dwm.zeus.log.trace=15 -Dwm.zeus.log.debug=15
10 RestartTomcat. Configure the BEA WebLogic Servlet Engine 1 2 3 4 5 6 InstalltheWorkflowServletinBEAWebLogic.Forinstructions,seetheBEA WebLogicdocumentation. ShutdownBEAWebLogic. GototheWebLogicinstallationdirectoryandcreateadirectorynamedsecurity. MakeacopyoftheWorkflowServerSSLcertificatefileyouidentifiedinthe configuratorandplacethecopyintheWebLogic_directory\securitydirectory. MakeacopyoftheBrokerSSLcertificatefileyouidentifiedintheconfiguratorand placethecopyintheWebLogic_directory\securitydirectory. OpenthestartWebLogic.cmdorstartWebLogic.shfileinatexteditor.Locatetheset
JAVA_OPTIONS=lineandaddtheseparameterstoit: -Dcom.wm.security.directory=%WebLogic_directory%\security -Dbroker.sslcertfile=%WebLogic_directory%\security\certificate_file -Dbroker.sslpassword=certificate_file_password -Dbroker.sslencrypted=true_or_false
227
-Dbroker.ssldname= CN=cn_info,O=organization,L=location,ST=state,C=country
Saveandclosethefile. 7 RestartBEAWebLogic.
Configure Modeler to Connect to an SSL-Enabled Workflow Server

IfyouwanttouseWorkflowwithModeler,andyourWorkflowServerisSSLenabled, youmustconfigureModelertoconnecttotheSSLenabledWorkflowServer. 1 2 3 4 5 StartWorkflowDesignerandconnecttotheWorkflowServer. StartModeler. GototheModeler_directory\libdirectoryandopenthesetup.batorsetup.shfileina texteditor. AddthisinformationtotheSET SYSVAR=parameter:
-Dcom.wm.security.directory=Workflow client_directory\lib\security
WhenModelerstarts,itsearchesforaWorkflowclientinstallation.IfModelerandthe Workflowclientareinstalledinthesamerootdirectory(forexample,webMethods6), ModelerautomaticallysetstheWF_HOMEparameterinthethesetup.batorsetup.sh filetoidentifytheWorkflowclientinstallation.IfModelerandtheWorkflowclientare notinstalledinthesamerootdirectory,youmustidentifytheWorkflowclientonthe WF_HOMEparameter. Savethesetup.batorsetup.shfile. RestartModeler.
6 7
228
Connect Products to Each Other

Connect My webMethods Server to Other Products
YoumustconnectMywebMethodsServertootherwebMethodsproductssotheproducts candisplaytheirdatainMywebMethods.
Identify Products to My webMethods Server

1 StartMywebMethodsServerasfollows: System Windows UNIXor Linux Action OpentheServiceswindow,doubleclickthewebMethodsPortalServer service,andthenclickStart. GotothePortal_directory/server/default/bindirectoryandrunthe run.sh(startinsameconsolewindow)orstartup.sh(startinnewcon solewindow)script.
OpenMywebMethodsbyenteringthisURLinanInternetbrowser:
http://My webMethods Server_host:My webMethods Server_port
ThehostandportaretheJetty HTTP Listener Host/PortyouspecifiedinthePortalServer Configurator.webMethodsrecommendsthatyoudonotuselocalhosttoidentify thehost. 3 4 Loginunderthedefaultusernameandpassword,Administratorandmanage. GotothewebMethods Configuration System Configuration System Settingspageand identifythewebMethodsproductsyouhaveinstalled.TheproductsareIntegration Server,thewebMethodsController(theManager/Optimizecontroller),(Workflow) TaskListManagementDCS,(Workflow)TaskListManagementAuthentication,Inbox Servlet(theWorkflowServlet;URLiscasesensitive),andthecentralWorkflow Server. Note: WhenyougototheSystem Settingspage,youmightseeerrorsforproductsthat arenotrunning.Youcanignoretheseerrors.MywebMethodsServerwillsaveyour settingsregardlessofwhethertheproductsarestartedornot. Youprovidedthehostmachinesandportsformostoftheproductsduring installation(foralistofdefaultports,seeDefaultPortsonpage 254).FortheTask ListManagementDCSandTaskListManagementAuthentication,however,youmust lookupthehostmachineandportinformationinWorkflowAdministrator,as follows:
229
StarttheWorkflowclientasfollows: System Windows Linux Action OntheStartmenu,gotoPrograms Workflow. webMethods webMethods
GototheWorkflowclient_directory/bindirectoryandrunthe clientmgr.shscript.
ClicktheAdministratoricon( ).InthelistofWorkflowServersandprocesses ontheleft,clicktheAuthenticationServerandtheDCS,respectively,toviewtheir hostmachineandportinformationontheMaintab.
Identify My webMethods Server to Products

Product Manager, Optimize Action YouidentifiedMywebMethodsServertoManagerandOptimize whenyouinstalledthecontroller.However,ifMywebMethods Serverisonadifferenthostmachineorusesadifferentportthan youthoughtatthattime,youmustupdatethatinformationinthe appropriatecontrollerconfigurationfile.Forinstructions,seethe webMethodsOptimizeandwebMethodsManagerConsole AdministratorsGuide. YoumustidentifyManagerservertothewebMethodsOMI exploreragentsoMywebMethodscandisplayManagerserver data.Forinstructions,seethewebMethodsOptimizeandwebMethods ManagerConsoleAdministratorsGuide. Bydefault,theMonitorruntimelooksfortheMonitorinterfaceon MywebMethodsServeronthelocalhostatport8080.IfMy webMethodsServerisonadifferenthostmachineorusesa differentport,youmustupdatethatinformationintheMonitor runtimeconfigurationfile,asfollows: 1 GototheIntegrationServer_directory/packages/ WmMonitor/configdirectoryandopenthemonitor.cnffileina texteditor. ChangethemyWebmethodsHostandmyWebmethodsPort valuesasnecessary. Saveandclosethefile.
Managerserver
Monitor
2 3 Workflow
IfyouchosetouseMywebMethodsServertoauthenticate WorkflowuserswhenyourantheWorkflowConfigurator,you identifiedMywebMethodsServertoWorkflowServeratthattime. Nofurtherconfigurationisrequired.
230
Connect Integration Server to the Default Broker

ThissectionexplainshowtoconnectIntegrationServertothedefaultBroker.For completeinformationontheentriesbelow,andforinformationonconfiguringIntegration ServertouseSSLtoconnecttotheBroker,seethewebMethodsIntegrationServer AdministratorsGuide. 1 2 3 OpenIntegrationServerAdministrator. GotoSettings BrokerandclickEdit Broker Settings.
ClicktheConfiguredoptionbuttonontheleftsideofthepageandcompletetheboxes below. Box Broker Host Broker Name Client Group Entry DNShostnameorfullyqualifiedIPaddressandportforthe BrokerServer. NameofthedefaultBrokerasdefinedontheBrokerServer (thatis,Broker#1). ClientgrouptowhichyouwantIntegrationServertoconnect. IntegrationServerwillcreatetheclientgroupwhenitconnects totheBroker. StringthatidentifiesIntegrationServertotheBroker.By default,IntegrationServerusesitslicensekeyfortheprefix. Foreaseofuseyoucandefineyourown,shorter,prefixname.
Client Prefix
ClickSave Changes.
231
Redirect Products to Use a Non-Default JRE or JDK

IfyouinstalledaJREorJDKforaproducttouseinsteadofthedefaultJDKinstalledby theinstaller,followthestepsbelowtoredirecttheproduct. Product webMethods Brokeritems(for example,Com mandLinetools) Steps Inthestepsbelow,commandisanycommandotherthan server_config,awcert,awbroker,orawbrokermon. webMethodsBroker_directory\bin\commandDJAVA_HOME =JDK_pathhost:port OnaWindowssystem,thecommandmightlooklikethis:
C:\Program Files\webMethods6\Broker\bin\broker_status -DJAVA_HOME-=C:\jdk1.4.2 localhost
OnaUNIXorLinuxsystem,thecommandmightlooklikethis:
/opt/webMethods6/Broker/bin/broker_status -DJAVA_HOME=/opt/java1.4 localhost
Developer(and plugins)
1 2
GototheDeveloper_directory\bindirectoryandopenthe developer.batordeveloper.shfileinatexteditor. EdittheJAVA_DIRparametertopointtotheJREinstallation directory,thensaveandclosethefile. GototheIntegrationServer_directory\bindirectoryandopen theserver.batorserver.shfileinatexteditor. EdittheJAVA_DIRparametertopointtotheJREinstallation directory,thensaveandclosethefile. Logontothehostmachineforthecontroller,datahandler,or satellite. GototheOptimizedirectory\item\bindirectoryandopenthe kenobiEnv.batorkenobiEnv.shfileinatexteditor. EdittheJAVA_HOMEparametertopointtotheJDKorJRE installationdirectory,thensaveandclosethefile. GototheManagerserver_directory\bindirectoryandopenthe server.batorserver.shfileinatexteditor. EdittheJAVA_DIRparametertopointtotheJREinstallation directory,thensaveandclosethefile.
Integration Server(andpack ages)
1 2 1 2 3
Managercontrol ler,datahandler, orsatellite
Managerserver
1 2
232
Redirect Products to Use a Non-Default JRE or JDK
Product Modeler
Steps 1 2 GototheModeler_directory\bindirectoryandopenthemod eler.batormodeler.shfileinatexteditor. EdittheJAVAPATHparametertopointtotheJREinstallation directory,thensaveandclosethefile.
Note: WhenyoulaunchDeveloperfromModeler,Developerruns inthesameJVMasModeler.IfyoudecidetouseadifferentJRE forModeler,theJREmustbesuitableforbothModelerandDevel oper. MywebMethods Server 1 2 Optimizecon troller,datahan dler,orsatellite 1 2 3 TradingNet worksConsole 1 2 GotothePortal_directory\bindirectoryandopentheset env.batorsetenv.shfileinatexteditor. EdittheJAVA_HOMEparametertopointtotheJREinstalla tiondirectory,thensaveandclosethefile. Logontothehostmachineforthecontroller,datahandler,or satellite. GototheOptimizedirectory\item\bindirectoryandopenthe kenobiEnv.batorkenobiEnv.shfileinatexteditor. EdittheJAVA_HOMEparametertopointtotheJDKorJRE installationdirectory,thensaveandclosethefile. GototheTradingNetworksConsole_directory\bindirectoryand opentheconsole.batorconsole.shfileinatexteditor. EdittheJAVA_ROOTparametertopointtotheJREinstalla tiondirectory,thensaveandclosethefile.
Note: WhenyoulaunchDeveloperfromTradingNetworksCon sole,DeveloperrunsinthesameJVMasTradingNetworksCon sole.IfyoudecidetouseadifferentJREforTradingNetworks Console,theJREmustbesuitableforbothTradingNetworksCon soleandDeveloper. Workflowclient 1 2 GototheWorkflowclient_directory\bindirectoryandopenthe console.batorconsole.shfileinatexteditor. EdittheJAVA_ROOTparametertopointtotheJDKinstalla tiondirectory,thensaveandclosethefile.
233
Complete the Installation for Other Products

Someproductsnotcoveredinthischapterhavetasksyoumustcompletethatarebeyond thescopeofthisguide.Makesureyouchecktheproductusersguidesforsuchtasks beforestartingtheproducts.
234
PART
VI
Uninstallation
Uninstalling Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Dropping Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
235
236
CHAPTER
14
Uninstalling 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
237
CHAPTER 14 Uninstalling Products
Overview
UninstallwebMethodsproductsusingthewebMethodsUninstaller.ThewebMethods Installerinstalledallfilesyouneedtoruntheuninstaller. Youcanruntheuninstallerusingdifferentmodes,asfollows: System Windows UNIX,Linux,orMacOSX OS/400 Mode wizard wizardorconsolemode consolemode
TouninstallusingthewizardonaUNIXorLinuxsystem,yoursystemmusthaveanX Windowsenvironment. Iferrorsorwarningsoccurduringtheuninstallation,theuninstallerwritestheerrorsand warningstoafilenamedWmUninstallLog.txtandstoresthefileinthemaininstallation directory(bydefault,webMethods6).
Uninstall on a Windows System

TouninstallwebMethodsproductsonaWindowssystem,youmusthaveWindows systemadministratorprivileges. 1 ShutdownallwebMethodsproductsandallotherapplicationsthatarerunningon yourmachine. Important! Ifyoudonotshutdownallproductsandapplications,theuninstallerwill notbeabletoremovekeyfilesthatarelockedbytheoperatingsystem. 2 3 4 UsetheWindowsAdd/RemoveProgramsutility,availablefromtheControlPanel,to starttheuninstaller. SelectwebMethods release installation_directoryastheprogramtouninstall. ChoosethewebMethodsproductstoremovefromyourmachine.ForwebMethods Broker,IntegrationServer,Developer,theuninstallerallowsyoutochoosetheparts oftheproducttoremove.Inaddition,forwebMethodsBrokerandIntegrationServer, theuninstalleraskswhetheritshoulddeleteprogramfilesthathavebeenmodified sinceyouinstalledtheproduct.Foreachproduct,choosetodeletealltheprogram files. Important! Whenyouchooseaproduct,theuninstalleraskswhetheritshouldalso uninstallallproductsthatdependontheproduct.Readthemessagescarefullyto avoiduninstallingproductsaccidentally.
238
Uninstall on a UNIX, Linux, OS/400, or Mac OS X System
Uninstall on a UNIX, Linux, OS/400, or Mac OS X System

Important! WhenyourunthewebMethodsUninstalleronanOS/400system,theuninstaller experiencesdisplayproblems.Whilethesedisplayproblemswillnotadverselyaffectthe uninstallationprocess,webMethodsstronglyrecommendsthatyouminimizethe problemsbyrunningtheuninstallerfromanOS/400clientforWindowsratherthanfrom atelnetclient. 1 2 LogonasthesameuserthatinstalledthewebMethodsproducts. IfthewebMethodsproductsyouareuninstallingarelocatedonaremotemachine andyouwanttouseagraphicaluninstaller,followthesesteps: a Enablethedisplayofthelocalmachineusingthecommandshownbelow,where remote_hostistheremotemachinefromwhichtouninstall:
xhost +remote_host
b c
Logontotheremotemachine. SettheDISPLAYvariableontheremotemachinetopointtothelocalmachine. Forexample,ifyouareusingabashshellandareuninstallingfromalocal machinenameduninstallerandwanttosettheDISPLAYtothedefaultdevice, enter:

export DISPLAY=uninstaller:0.0
ShutdownallwebMethodsproductsandallotherapplicationsthatarerunningon themachinethatcontainsthewebMethodsproductsyouareuninstalling. Important! Ifyoudonotshutdownallproductsandapplications,theuninstallerwill notbeabletoremovekeyfilesthatarelockedbytheoperatingsystem.
GotothewebMethods_directory/bindirectoryandentertheappropriatecommand,as follows: Uninstall Mode Wizard Consolemode Command

uninstall uninstall -console
ChoosethewebMethodsproductstoremovefromthemachine.ForwebMethods Broker,IntegrationServer,Developer,theuninstallerallowsyoutochoosetheparts oftheproducttoremove.Inaddition,forwebMethodsBrokerandIntegrationServer, theuninstalleraskswhetheritshoulddeleteprogramfilesthathavebeenmodified
239
sinceyouinstalledtheproduct.Foreachproduct,choosetodeletealltheprogram files. Important! Whenyouchooseaproduct,theuninstalleraskswhetheritshouldalso uninstallallproductsthatdependontheproduct.Readthemessagescarefullyto avoiduninstallingproductsaccidentally.
Complete the Uninstallation

Formostproducts,theuninstallerdoesnotdeletefilescreatedafteryouinstalledthe product(forexample,usercreatedorconfigurationfiles),nordoesitdeletethedirectory structurethatcontainsthefiles.Ifyoudonotwanttosavethefiles,deletetheproduct installationdirectory.
Complete the Deployer Uninstallation

TouninstalltheDeployercommunicationscomponentfromsourceandtargetIntegration Servers,followthesesteps: 1 2 IntheIntegrationServerAdministratorforanIntegrationServerthathoststhe resourcepackage,gotothePackages Managementpage. DeletetheWmDeployerResourcepackage.
TouninstalltheDeployercommunicationcomponentfromsourceandtargetPortal servers,askyourPortaladministratortoremovetheportletnamedPortalDeployerPlug in.ThepluginIDiswm_deployerpluginpdp,anditislocatedinthePortaldirectory/SDK directory.
Complete the webMethods Mainframe Uninstallation

IfyouinstalledMainframeAdapter4.6andwanttouninstallit,usetheWindows Add/RemoveProgramsutility,availablefromtheControlPanel. IfyouinstallthewebMethodsMainframeDeveloperPlugin,theuninstallerdoesnot deletethewebMethodsMainframeDeveloperPluginlogfile,namedBuilder.log,from theDeveloperinstallation.Ifyoudonotwanttosavethefile,gototheDeveloper installationdirectory(bydefault,webMethods6\Developer)anddeletetheBuilder.log file.
240
Complete the Uninstallation
Complete the Modeler Uninstallation

IfyouuninstalledModeler,theuninstallerdoesnotdeletegenerateddeploymentfiles, exportedXMLfiles,oruserpreferencefiles.Ifyoudonotwanttosavethesefiles,delete themfromtheindicateddirectories: Files Generateddeployment (processname.xml) ExportedXML Userpreference (.wmModelerPrefs) Directory webMethods_directory\Modeler\DeploymentInfo Userspecified DocumentsandSettings\userdirectory(Windowssystem) or$HOMEdirectory(Linuxsystem)
IfyouuninstalledtheModelerDesignPackage,theuninstallerdoesnotremovelogfiles and,iftheModelerRepositorywritestoaflatfile,therepository.dbfile.Ifyoudonot wanttosavethefiles,deletethemfromthesedirectories: Files Log repository.db Directory webMethods_directory\Servers\RepoV3\logs webMethods_directory\Servers\RepoV3\WmRepository
241
242
CHAPTER
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
243
CHAPTER 15 Dropping Database Components
Drop Database Components from Oracle

Drop the Cross-Reference, Document History, IS Core Audit Log, Modeler Repository, Process Tracking Store, and Trading Networks Database Component
Todropadatabasecomponent,executethescriptindicatedbelowfromyourdatabase editor.ThescriptsarelocatedinthewebMethods_directory\common\db\scripts\drop directoryonthemachinetowhichyoudownloadedthedatabasescripts. Component CrossReference DocumentHistory ISCoreAuditLog ModelerRepository ProcessTrackingStore Reporting TradingNetworks Staging Script drop_xref_65.sql drop_idr_65.sql drop_iscoreaudit_65.sql drop_RepoV3_65.sql drop_prt_65.sql drop_reporting_65.sql drop_TN_65.sql,drop_archive_TN_65.sql drop_staging_65.sql
Drop the Analysis, Archive, Process Tracker, and Servicenet Database Components
Dropthesedatabasecomponentsbydroppingtheschemathroughthedatabase administrationutilityprovidedbyyourdatabasevendor.
Drop the My webMethods Server Database Component

WhenyoudroptheMywebMethodsServerdatabasecomponent,thedatabaseuseris deletedalongwithalluserobjects,suchastables,procedures,packages,andsoforth. YouusedifferentcommandstodroptheMywebMethodsServerdatabasecomponent dependingonwhetheryouarerunningthecommandfromamachinethathostsMy webMethodsServer,Access,orPortal,ornoneofthoseproducts.Ifyouwanttodropthe MywebMethodsServerdatabasecomponentfromamachinethatdoesnothostanyof thoseproducts,themachinemustbeequippedwithanOracledatabaseclient. TodroptheMywebMethodsServerdatabasecomponent,youmusthavedatabase administratorprivileges.
244
Drop Database Components from Oracle
Followtheappropriatestepsbelow. To run the command from... MywebMethods ServerorAccessor Portalhostmachine Othermachine Follow these steps... OpenacommandwindowandgototheMywebMethods Server,Access,orPortal_directory\bin\db\scripts\oracle directory. Ifyouhavenotyetcopiedtheoracledirectorytothe machineequippedwithanOracledatabaseclient: 1 OntheMywebMethodsServer,Access,orPortalhost machine,gototheMywebMethodsServer,Access,or Portal_directory\bin\db\scriptsdirectory. Copytheoracledirectorytothemachineequipped withtheOracledatabaseclient.
Runthiscommand:
{dbdrop.{bat|sh} | dbdrop_sqlplus.{bat|sh}} database_server_host:database_server_port instance administrator_user administrator_password database_user
Parameter
{dbdrop.{bat|sh} | dbdrop_sqlplus. {bat|sh}}
Entry IfyouarerunningthecommandfromtheMyweb MethodsServer,Access,orPortalhostmachine,enter dbdrop.{bat|sh}.Ifyouarerunningthecommandfrom amachinethatdoesnothostMywebMethodsServer, Access,orPortal,enterdbdrop_sqlplus.{bat|sh). NameorIPaddressofthemachinethathoststheOra cledatabaseserver.Donotuselocalhosttoidentify thehost. Nameoftheinstanceondatabase_server_hostthatcon tainstheMywebMethodsServerdatabasecomponent. Portthedatabaseserverusestocommunicate.The defaultportforOracleis1521. Administratoruserforthedatabaseserver. Administratorpasswordforthedatabaseserver. DatabaseuserMywebMethodsServer,Access,and Portaltousetocommunicatewiththedatabaseserver.
instance
administrator_ user administrator_ password database_user
245
Forexample,thefollowingcommanddropstheMywebMethodsServerdatabase componentfromthemywebmserver_dbinstanceontheoraserverdatabaseserver:
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 Components
Todropadatabasecomponent,executethescriptindicatedbelowfromyourdatabase editor.ThescriptsarelocatedinthewebMethods_directory\common\db\scripts\drop directoryonthemachinetowhichyoudownloadedthedatabasescripts. Component CrossReference DocumentHistory ISCoreAuditLog ModelerRepository ProcessTrackingStore Reporting TradingNetworks Staging Oracle, SQL Server, and DB2 drop_xref_65.sql drop_idr_65.sql drop_iscoreaudit_65.sql drop_RepoV3_65.sql drop_prt_65.sql drop_reporting_65.sql drop_TN_65.sql,drop_archive_TN_65.sql drop_staging_65.sql
Drop the Manager Server and Process Audit Log Database Components
Todropadatabasecomponent,executethescriptindicatedbelowfromyourdatabase editor.ThescriptisinthewebMethods_directory\scripts\mssql\code\component\drop directoryonthemachinetowhichyoudownloadedthedatabasescripts. Important! BeforedroppingtheManagerserverdatabasecomponent,shutdownall Managerserversthatareconnectedtothedatabasecomponent.Doingsowillmakesure Managerserversaccessthecorrectdataafterrestart.
246
Drop Database Components from SQL Server
Component Managerserver ProcessAuditLog
Script drop_ManagerServer_65.sql metadata.sql,processrecent.sql,runtime.sql
Drop the Analysis, Archive, Process Tracker, and Servicenet Database Component
Dropthesedatabasecomponentsbydroppingthedatabasethroughthedatabase administrationutilityprovidedbyyourdatabasevendor.
Drop the My webMethods Server Database Component

WhenyoudroptheMywebMethodsServerdatabasecomponent,thedatabaseuseris deletedalongwithalluserobjects,suchastables,procedures,packages,andsoforth. YouusedifferentcommandstodroptheMywebMethodsServerdatabasecomponent dependingonwhetheryouarerunningthecommandfromamachinethathostsMy webMethodsServer,Access,orPortal,ornoneofthoseproducts.Ifyouwanttodropthe MywebMethodsServerdatabasecomponentfromamachinethatdoesnothostanyof thoseproducts,themachinemustbeequippedwiththeOSQLutility. TodroptheMywebMethodsServerdatabasecomponent,youmusthavedatabase administratorprivileges. 1 Followtheappropriatestepsbelow. To run the command from... Portalhost machine Othermachine Follow these steps... OpenacommandwindowandgototheMywebMethods Server,Access,orPortal_directory\bin\db\scripts\mssql directory. 1 OntheMywebMethodsServer,Access,orPortalhost machine,gototheMywebMethodsServer,Access,or Portal_directory\bin\db\scriptsdirectory. Copythemssqldirectorytothemachineequippedwith theOSSQLutility.
Runthiscommand:
{dbdrop.bat | dbdrop_osql.bat} database_server_host:database_server_port database administrator_user administrator_password database_user
247
Parameter
{dbdrop.bat | dbdrop_osql.bat}
Entry IfyouarerunningthecommandfromtheMyweb MethodsServer,Access,orPortalhostmachine, enterdbdrop.bat.Ifyouarerunningthecommand fromamachinethatdoesnothostMywebMethods Server,Access,orPortal,enterdbdrop_osql.bat. NameorIPaddressofthemachinethathoststhe SQLServerdatabaseserver.Donotuselocalhost toidentifythehost. Nameofdatabaseondatabase_server_hostcontaining theMywebMethodsServerdatabasecomponent. Portthedatabaseserverusestocommunicate.The defaultportforSQLServeris1433. Administratoruserforthedatabaseserver. Administratorpasswordforthedatabaseserver. DatabaseuserMywebMethodsServer,Access,and Portalusetocommunicatewiththedatabase.
database
administrator_user administrator_password database_user
Forexample,thefollowingcommanddropstheMywebMethodsServerdatabase componentfromthemywebmserver_dbdatabaseonthesqlserverdatabaseserver:
dbdrop.bat sqlserver:1433 mywebmserverdb sa password mywebmserveruser
Drop Database Components from DB2

Todropadatabasecomponent,executethescriptindicatedbelowfromyourdatabase editor.ThescriptsarelocatedinthewebMethods_directory\common\db\scripts\drop directoryonthemachinetowhichyoudownloadedthedatabasescripts. Component CrossReference DocumentHistory ISCoreAuditLog Scripts drop_xref_65.sql drop_idr_65.sql drop_iscoreaudit_65.sql
248
Drop Database Components from DB2
Component ModelerRepository ProcessTrackingStore Reporting TradingNetworks Staging
Scripts drop_RepoV3_65.sql drop_prt_65.sql drop_reporting_65.sql drop_TN_65.sql,drop_archive_TN_65.sql drop_staging_65.sql
Drop the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components
YoucandropthesedatabasecomponentsusingthewebMethodsDatabaseInstalleror youcandropthemmanually.
Drop the Database Components Using the Database Installer

1 2 3 OntheDB2databaseserverhostmachine,gotothewebMethods_directory\common\ db\scripts\db2directory. StartthewebMethodsDatabaseInstallerbyrunningthiscommand:
ibmDB2.{bat | sh}
ChooseDrop a Database Component,thenchoosethedatabasecomponenttodrop.
Drop the Database Components Manually

OpenacommandwindowandgotothewebMethods_directory\common\db\scripts\db2 directory.Runthescriptsintheorderindicatedbelow. Database Component Analysis ProcessTracker ProcessAudit Script code/analysis/drop/db2_anl_d_ddl_tables_indexes.sql code/processtracker/drop/db2_ptr_d_ddl_tables_indexes.sql 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
249
Database Component Archive
Script code/processaudit/drop/metadata.sql code/processaudit/drop/runtime.sql code/processaudit/drop/processrecent.sql ../drop/drop_iscoreaudit_65.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
Drop the Database Components from Sybase

Todropadatabasecomponent,executethescriptindicatedbelowfromyourdatabase editor.ThescriptsarelocatedinthewebMethods_directory\common\db\scripts\drop directoryonthemachinetowhichyoudownloadedthedatabasescripts. Component CrossReference DocumentHistory ISCoreAuditLog Reporting TradingNetworks Staging Scripts drop_xref_65_Sybase.sql drop_idr_65_Sybase.sql drop_iscoreaudit_65_Sybase.sql drop_reporting_65_Sybase.sql drop_TN_65_Sybase.sql,drop_archive_TN_65_Sybase.sql drop_staging_65_Sybase.sql
Drop the Archive and Process Audit Log Database Components

1 OnthemachinetowhichyoudownloadedthedatabasescriptsandthewebMethods DatabaseInstaller,gotothewebMethods_directory\common\db\scripts\sybase directoryandopenthesybase_env_properties.{bat|sh}fileinatexteditor.
250
Drop the Database Components from Sybase
Afteryouinstalledthedatabasecomponents,youremovedthedatabaseuser passwordfromthedatabaseconnectionpropertiesfileforsecurityreasons.Tobeable todropthedatabasecomponents,youmustreenterthepassword.Editthese connectionpropertiesforeachdatabasecomponentyouaregoingtodrop:

Important! Databasenamesarecasesensitive.Youmustusetherightcasingforthe databasenameintheconnectionpropertiesorthedropwillfail. 3 Saveandclosethefile.
Drop the Database Components

1 IfyouinstalledtheISCoreAuditLogdrivertables(becauseyouinstalledtheArchive databasecomponent,andtheISCoreAuditLogandtheProcessAuditLogdatabase componentsareonseparatedatabaseservers),dropthedrivertablesbynavigatingto thewebMethods_directory\common\db\scripts\sybase\code\archive\drop directoryandexecutingtheSQLscriptsybase_arc_c_ddl_tables_indexes.sql. GotothewebMethods_directory\common\db\scripts\sybasedirectoryanddropthe databasecomponentsasfollows: To drop this database component... Archive ProcessAuditLog Run this program... drop_archive_65.{bat|sh} drop_processaudit_65.{bat|sh}
251
252
APPENDIX
Default Ports
Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
253
APPENDIX A Default Ports
Default Ports
Component Access, My webMethods Server, and Portal RMIregistrycommunicationamong clusteredAccessorPortalservers Diagnostics AJP13JettylistenstoexternalWebserver, ifusingone(notenabledbydefault) JettyHTTPWebserver JettyHTTPSWebserver(notenabledby default) webMethods Broker BrokerServer 6849(SSLnotenabled) 6848(SSLenabled) 6847(SSLauthenticated) 6849 6850 8080 5555 7777 TCP 1097 5000 8009 8080 8443 RMI HTTP AJP13 HTTP HTTPS Default Port Protocol/Port Type
DefaultBroker BrokerMonitor Dashboard application server Integration Server Communicationwithremoterepository
TCP TCP HTTP HTTP Proprietary binary protocol overTCP Proprietary binary protocol overTCP HTTP
Communicationamongclustered IntegrationServers
8897
Diagnostics
9999
254
Default Ports
Component JBoss Package JNDIRMIclientscallremoteJavaObject methodsonIntegrationServerthrough sockets RMIEJBclientsaccesstheJNDInaming serviceinJBoss HypersonicSQLdatabase communicationbetweenJBossanddefault HypersonicSQLdatabase JettyHTTPHTTPclientscallIntegration ServerservicesandaccessJSPsinWARs thataredeployedonIntegrationServer webMethods Mainframe Modeler Repository Manager and Optimize Controller HTTPcommunicationwithother webMethodsproducts JMXlistenfordatafromsatellitesand datahandler Data handler HTTPcommunicationwithclients publishingtoWebserviceDCAs JMXlistenfordatafromcontroller Satellite HTTPcommunicationwithclients publishingtoWebserviceDCAs JMXlistenfordatafromcontroller
Default Port
Protocol/Port Type
1099
ClientAPIs
4444 1701
RMI JDBCover TCP HTTP
8080
8087 7778
TCP/IP RMI
12503 12501
HTTP HTTP
12603 12601
HTTP HTTP
12005 12001
HTTP HTTP
255
Component Servicenet Controller DiagnosticsforJMXviewofManager andOptimize Listenfordatafromdatahandlerand satellitesonintermediaries Listenfordatafromclients JVMdiagnosticport(notenabledby default) Data handler Communicationwithclientspublishing toWebserviceDCAs Listenfordatafromcontroller JVMdiagnosticport(notenabledby default) Registry Listenfordatafromclients Listenfordatafromsatellite JVMdiagnosticport(notenabledby default) Intermediary ListenforrequestsfromWebservice clients Listenfordatafromsatellite JVMdiagnosticport(notenabledby default) Subnet locator discovery port
Default Port
Protocol/Port Type
12500 12501 12503 5005
HTTP JMXover HTTP HTTP TCP
12603 12103 5005
HTTP JMXover HTTP TCP
8088 12030 5007
SOAPover HTTP JMXover HTTP TCP
2112 12031 5008 9030
SOAPover HTTP JMXover HTTP TCP UDP proprietary
256
Default Ports
Component Workflow Server CommunicationbetweenWorkflowServer andWorkflowclients RMIregistry
Default Port
Protocol/Port Type
6000(WindowsXP Professional) 5000(allothersystems) 6001(WindowsXP Professional 5001or6001if5001isin use(allothersystems)
HTTP
RMI
257
258
APPENDIX
Database Components
Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Monitor Service pub.monitor.archive:setOperationParameters . . . . . . . . . . . . . . . . . . . . . . 264
259
APPENDIX B Database Components
Descriptions
ThewebMethodsdatabasecomponentsaredescribedbelow. Database Component Analysis Description Thefollowingwritedatatothisdatabasecomponent: TheManagerandOptimizedatahandlerwritesprocessand monitoringdataitreceivesfromsatellites TheManagerandOptimizecontrollerevaluatesthedataand writesruleandfingerprintevaluations Servicenetwritesmonitoring,rule,SLA,andactiondata MywebMethodsdisplaysthedata. Archive MonitorcanarchivedatathatwasoriginallystoredintheISCore AuditLogandProcessAuditLogdatabasecomponentstothis databasecomponent.Monitorcanarchivedocumentsanddatafor 4.xactivations,processes,andservices.Monitorcanalsoarchive serverdata,whichincludesIntegrationServerserver,session,and guaranteeddeliverylogentries,anderrorlogentriesthatarenot associatedwithloggedprocesses,services,4.xactivations,ordoc uments(forexample,errorsthatoccurduringstartuporduring therunofunloggedprocesses,services,activations,anddocu ments). IntegrationServercanwritecrossreferencekeysandprocess integritystatusinformationrequiredtosynchronizeupdates amongvariouswebMethodsproductsandtheirdatabasecompo nentstothisdatabasecomponent.Bydefault,IntegrationServer writesthisinformationtoflatfiles. IntegrationServerwritesthehistoryofdocumentsthatarepro cessedbytriggersconfiguredforexactlyonceprocessingtothis databasecomponent.
CrossReferencing
DocumentHis tory
260
Descriptions
Database Component ISCoreAuditLog
Description IntegrationServercanwritethefollowingtothisdatabasecompo nent: Error,guaranteeddelivery,service,andsessiondata(by default,IntegrationServerwritesthisinformationtoflatfiles) Documentsthatareindoubt,havefailed,andorhave exhaustedtriggerretries DocumentsloggedbyBrokersforallJMSclientsandallBro kerclientsexceptWorkflowprocesses;theLoggingUtility takesthedocumentsfromtheBrokersandpassesittoIntegra tionServer IntegrationServerAdministratorandMonitordisplaydifferent partsofthisdata.
IntegrationServer repository
IntegrationServersinaclustercanwritetheirstatetothisdata basecomponentsotransactionscanbecontinuedonotherInte grationServersintheclusteriftheoriginalIntegrationServer fails.ClusteredIntegrationServersusetherepositorytokeep trackofscheduledjobs,sessioncontext,andjobstrackedbyguar anteeddelivery.IntegrationServersalsostoreinformationneeded bytheBrokerstowhichtheyconnect. Managerserverwritesobjects,notifications,andconfigurationsto thisdatabasecomponent.ThedataisdisplayedintheManager serverinterface. Managerserverstoresmetadataaboutitsmanagementmodeland instancesofobjectswithinthemanagementmodelinthisdata basecomponent.IfyouhavetorestartManagerserver,theman agementmodelcanberecreatedwiththecorrectstate.
Managerserver
ModelerReposi tory
TheModelerDesignPackageincludestheModelerRepository,a storageareainwhichModelersavesprocessmodelinformation andthefilesneededtocreateandgenerateprocessmodels.By default,theModelerRepositorywritestoaflatfile.Flatfile storageissufficientformostinstallations.IfyourModelerusageis extremelyhigh,however,andyouhavesufficientresourcesto handletheoverheadofmaintainingadatabase,youcanconfigure theModelerRepositorytowritetothisdatabasecomponent instead.
261
Database Component MywebMethods Server
Description MywebMethodsServer,Access,andPortalwritedataabout deployment,configuration,security,portalpages,andtheMy webMethodsServerruntimetothisdatabasecomponent.My webMethodsServerusesthisdatatomanagetheMyweb Methods,Access,andPortaluserinterfaces. IntegrationServercanwritethefollowingtothisdatabasecompo nent: Modelerprocessdata;thedataispassedtoIntegrationServer bythePRT DocumentsandprocessdataloggedbyBrokersforclient Workflowprocesses;theLoggingUtilitytakesthedocuments anddatafromtheBrokersandpassesittoIntegrationServer Monitordisplaysthisdata.Optimizeobtainsprocessmodeldefi nitionsfromthisdatabasecomponentsoitcananalyzecapabili tiessuchastransitionduration. Servicenetrequiresbutdoesnotusethisdatabasecomponent. Servicenetrequiresthisdatabasecomponentbecauseitscontroller isbasedonOptimize,andOptimizerequiresthisdatabasecom ponent.
ProcessAuditLog
ProcessTracker
TheManagerandOptimizedatahandlerwritesbusiness,system, andprocessdataitreceivesfromsatellitestothisdatabasecompo nent. Servicenetrequiresbutdoesnotusethisdatabasecomponent. Servicenetrequiresthisdatabasecomponentbecauseitscontroller isbasedonOptimize,andOptimizerequiresthisdatabasecom ponent.
ProcessTracking Store Reporting
ThePRTcanwriteprocessexecutiondatatothisdatabasecompo nent.Bydefault,thePRTwritestoRAM. Monitorbuiltinservicescanwriteprocessstatusdataextracted fromtheProcessAuditLogdatabasecomponentandaggregated intodailystatisticstothisdatabasecomponent.Monitordisplays thisdata. Note: ReportingisavailableonlyondatacollectedafterJanuary1, 2003.Also,thereportsareonlyavailableinEnglish.Theyarenot localizedandarenotavailableintheJAlanguagepack.
262
Descriptions
Database Component Servicenet
Description ServicenetwritesUDDIbasedcatalogdatathatidentifiestheWeb servicesthatareunderServicenetmanagementtothisdatabase component.Theservicescanthenbemonitoredandmanaged throughtheServicenetinterface. Servicenetwritesthefollowingtothisdatabasecomponent: UDDIbasedcatalogdatathatidentifiestheWebservicesthat areunderServicenetmanagement Servicenetintermediarydata LoggingdatageneratedbyServicenetevents MywebMethodsdisplaystheservices,theintermediarydata,and theloggingdata.
Staging
Monitorbuiltinservicesusethisdatabasecomponenttoaccumu latetheprocessstatusdataextractedfromtheProcessAuditLog databasecomponentsothedatacanbemanipulatedandthen loadedintotheReportingdatabasecomponent. TradingNetworksServerwritesitsmetadata(partnerprofiles, tradingpartneragreements,documenttypes,processingrules, andpartnerprofilegroups)andruntimedata(documents;docu mentcontentparts,attributes,anddeliveryinformation;andlog entriesaboutdocumentprocessingsteps)tothisdatabasecompo nent.TradingNetworksConsoledisplaysthedata. WorkflowServerwritescriticalprocessandtaskruntimestate dataandmonitoringdatatothisdatabasecomponent.
TradingNetworks
Workflow
263
Monitor Service pub.monitor.archive:setOperationParameters

SetsparametersintheOPERATION_PARAMETERtableoftheArchivedatabase componentifyouareusingOracle,SQLServer,orDB2.Thenamesoftheparametersin thetablebelowexactlymatchthecolumnnamesinthetable. Input Parameters PROCESSAUDIT _DBLINK StringForSQLServer,ifyouwanttoarchivefromtheProcess AuditLogandtheArchiveandProcessAuditLogdatabase componentsareondifferentdatabaseservers,entertheLinked Servernametousetolinkthedatabasecomponents.Ifyoudo notwanttoarchivefromtheProcessAuditLogdatabase component,orthedatabasecomponentsareonthesame databaseserver,enternull. StringForSQLServer,ifyouwanttoarchivefromtheISCore AuditLog,andtheArchiveandISCoreAuditLogdatabase componentsareondifferentdatabaseservers,entertheLinked Servernametousetolinkthedatabasecomponents.Ifyoudo notwanttoarchivefromtheISCoreLogdatabasecomponent, orthedatabasecomponentsareonthesamedatabaseserver, enternull. String IfyouwanttoarchivefromtheProcessAuditLog databasecomponent,enterthefollowingfortheProcessAudit Logdatabasecomponent: RDBMS Oracle SQLServer DB2 Entry Databaseuser Databasename Schemaname
ISCOREAUDIT _DBLINK
PROCESS_SCHEMA
IfyoudonotwanttoarchivefromtheProcessAuditLog databasecomponent,enternull. ISCORE_SCHEMA String IfyouwanttoarchivefromtheISCoreAuditLog databasecomponent,enterthefollowingfortheISCoreAudit Logdatabasecomponent: RDBMS Oracle SQLServer Entry Databaseuser Databasename
264
Monitor Service pub.monitor.archive:setOperationParameters
DB2
Schemaname
IfyoudonotwanttoarchivefromtheISCoreAuditLog databasecomponent,enternull. Output Parameters message String Messagethatindicatesthattheparametershavebeenset.
265
266
APPENDIX
Create the Broker Server Configuration Manually

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
267
APPENDIX C Create the Broker Server Configuration Manually
Overview
YoumustcompletetheinstructionsinthisappendixifyoudidnotusethewebMethods InstallertocreatetheBrokerServerconfiguration.Youdidnotusetheinstallertocreate theBrokerServerconfigurationinthesecases: YouinstalledwebMethodsBrokeronaUNIXorLinuxsystemasanonrootuser.In thiscaseyoumustcompletealltasksinthischapter. YouinstalledonaUNIXorLinuxsystemasrootuseroryouinstalledonaWindows system,butyouwantedtospecifyadifferentstoragesizethanisavailablethrough theinstalleroryouwantedtocreateacombinedstoragesessionforconfigurationand runtimedata.InthiscaseyoumustcompletealltasksinthischapterexceptSetUp BrokerMonitoronUNIXorLinuxSystems(NonRootUser)onpage 270. Important! YoumusthaveinstalledwebMethodsBrokerusingthewebMethodsInstaller fortheinstructionsinthisappendixtowork.YoushouldneverinstallwebMethods Brokerbycopyingtheproductfilesfromonedirectorytoanother.
Create the Broker Server Data Directory

Create the Data Directory on UNIX or Linux Systems as NonRoot User
1 2 LoginasthesamenonrootuserthatyouloggedinastoinstallwebMethodsBroker. CreatethedirectoryinwhichyouwantBrokerServertostoredata(thatis,theBroker Serverdatadirectory). Note: WhentheinstallerisusedtocreatetheBrokerServerconfiguration,thedefault datadirectoryis/var/opt/webmethods/awbrokers65/default.Ifyouwanttocreatethat directorytobetheBrokerServerdatadirectory,askyoursystemadministratorforfull readandwritepermissionstothe/var/optdirectory. Donotusethe/tmpdirectoryastheBrokerServerdatadirectory.Makesurethe BrokerServerdatadirectorydoesnotcontainafilenamedawbroker.cfg;suchafile indicatesthatthedirectoryisinusebyanotherBrokerServer 3 GotothewebMethodsBrokerdirectory(bydefault,webMethods6/Broker)andopen theS45broker65fileinatexteditor. a SettheDEFAULT_ACTIVE_CONFIGparameterasfollows:
DEFAULT_ACTIVE_CONFIG=fully_qualified_path_to_Broker_Monitor_ configuration_directory
268
Create the Broker Server Data Directory
Forexample:
DEFAULT_ACTIVE_CONFIG=/var/opt/webmethods
SettheDEFAULT_ACTIVE_HOMEparameterasfollows:
DEFAULT_ACTIVE_HOME=webMethods Broker_directory
Forexample:
DEFAULT_ACTIVE_HOME=/opt/webMethods6/Broker
c 4
Exportthevaluesyoujustsettoyourcurrentenvironment. a ExporttheDEFAULT_ACTIVE_CONFIGparametertoACTIVE_CONFIGas follows: System csh Command and Example

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 b ExporttheDEFAULT_ACTIVE_HOMEparametertoACTIVE_HOMEasfollows: System csh Command and Example

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
269
Create the Data Directory on a UNIX or Linux Systems as Root User

LoginastherootuserandcreatethedirectoryinwhichyouwantBrokerServertostore data(thatis,theBrokerServerdatadirectory). Note: WhentheinstallerisusedtocreatetheBrokerServerconfiguration,thedefaultdata directoryis/var/opt/webmethods/awbrokers65/default. Donotusethe/tmpdirectoryastheBrokerServerdatadirectory.MakesuretheBroker Serverdatadirectorydoesnotcontainafilenamedawbroker.cfg;suchafileindicatesthat thedirectoryisinusebyanotherBrokerServer.
Create the Data Directory on Windows System

Tocompletethisstep,youmusthaveWindowssystemadministratorprivileges. CreatethedirectoryinwhichyouwantBrokerServertostoredata(thatis,theBroker Serverdatadirectory). Note: WhentheinstallerisusedtocreatetheBrokerServerconfiguration,thedefaultdata directoryisC:\ProgramFiles\webMethods6\Broker\data\awbrokers65\default. DonotusethetempdirectoryastheBrokerServerdatadirectory.MakesuretheBroker Serverdatadirectorydoesnotcontainafilenamedawbroker.cfg;suchafileindicatesthat thedirectoryisinusebyanotherBrokerServer.
Set Up Broker Monitor on UNIX or Linux Systems (Non-Root User)

IfyouinstalledwebMethodsBrokerasanonrootuser,youmustsetupBrokerMonitorto runaseitheradaemonthatstartsandshutsdownautomaticallywhenyoursystemstarts andshutsdown,oranapplicationthatyoustartandshutdownmanually.TheBroker MonitorcontrolstheBrokerServer;whentheBrokerMonitorstartsorshutsdown,it startsorshutsdowntheBrokerServer.
Run as Daemon
1 2 LoginunderthenonrootuserIDyouusedtoinstallwebMethodsBroker. IfyouconfiguredBrokerServertocreatedatafilesonanNFSmountedpartition,go tothewebMethodsBrokerdirectoryandopentheS45broker65fileinatexteditor. TheS45broker65fileisthescriptthatstartsandstopsBrokerMonitor.
270
Set Up Broker Monitor on UNIX or Linux Systems (Non-Root User)
Locatethisline:
${NOHUP_CMD} ${ACTIVE_HOME}/bin/awbrokermon > /dev/null 2>&1 &
Addthislineafter${NOHUP_CMD}:
su non_root_user -c
Fornon_root_user,specifythenonrootuseryouusedtoinstallwebMethodsBroker. Forexample:
${NOHUP_CMD} su qa -c ${ACTIVE_HOME}/bin/awbrokermon > /dev/null 2>&1 &
Saveandclosethefile. 3 CreatethedirectoryyouwanttouseastheBrokerMonitorconfigurationdirectory. Note: WhentheinstallerisusedtocreatetheBrokerMonitorconfigurationdirectory, thedefaultis/var/opt/webmethods.Ifyouwanttocreatethatdirectorytobethe BrokerMonitorconfigurationdirectory,askyoursystemadministratorforfullread andwritepermissionstothe/var/optdirectory. 4 GototheBrokerMonitorconfigurationdirectory.Createtheconfigurationfile awbrokermon.cfgbyenteringthiscommandonasingleline:

$ webMethods Broker_directory/bin/awbrokermon -config webMethods Broker_directory/ -user non_root_user -group non_root_user_group
Fornon_root_userandnon_root_user_group,specifythenonrootuserandnonroot usergroupyouusedtoinstallwebMethodsBroker.Forexample:
$ /opt/webMethods6/Broker/bin/awbrokermon -config /opt/webMethods6/Broker -user qa group Eng
Askyoursystemadministratortodothefollowing: a CopytheS45broker65fileyoujustmodifiedtothe/rc3.ddirectory.Thisdirectory islocatedasfollows: System AIX HewlettPackard SolarisandLinuxRedHat SUSELinux b Directory /var/opt/webmethods /sbin/rc3.d /etc/rc3.d etc/rc.d/rc3.d
Gototherc3.ddirectoryandrunthiscommandtostartBrokerMonitor:
./S45broker65 start
BrokerMonitorwilllaunchasrootatfirst,butthenwillswitchtorunningunder theuserIDandgroupIDthatyousuppliedintheawbrokermon.cfgfile.
271
MakesureBrokerMonitorisrunningbyenteringthiscommand:
ps ef | grep aw
Run as Application
1 2 LoginunderthenonrootuserIDyouusedtoinstallwebMethodsBroker. CreatethedirectoryyouwanttouseastheBrokerMonitorconfigurationdirectory. Note: WhentheinstallerisusedtocreatetheBrokerMonitorconfigurationdirectory, thedefaultis/var/opt/webmethods.Ifyouwanttocreatethatdirectorytobethe BrokerMonitorconfigurationdirectory,askyoursystemadministratorforfullread andwritepermissionstothe/var/optdirectory. 3 GototheBrokerMonitorconfigurationdirectory.Createtheconfigurationfile awbrokermon.cfgbyenteringthiscommandonasingleline:
$ webMethods Broker_directory/bin/awbrokermon -config webMethods Broker_directory/ -user non_root_user -group non_root_user_group
Fornon_root_userandnon_root_user_group,specifythenonrootuserandnonroot usergroupyouusedtoinstallwebMethodsBroker.Forexample:
$ /opt/webMethods6/Broker/bin/awbrokermon -config /opt/webMethods6/Broker -user qa -group Eng
RunthiscommandtostartBrokerMonitor:
$ webMethods Broker_directory/S45broker65 start
Forexample: /opt/webMethods6/Broker/S45broker65start 5 MakesureBrokerMonitorisrunningbyenteringthiscommand:

ps ef | grep aw
Create the Broker Server on Any System

ThecommandyouruntocreatetheBrokerServeralsocreatestheBrokerServer configurationfileawbroker.cfgandthedatafilesthatwillbeusedbyindividualBrokers runningontheBrokerServer.Thecommandplacestheawbroker.cfgfileandthedatafiles intheBrokerServerdatadirectory. Thecommandalsoletsyoucreateeitherseparatestoragesessionsfortheconfiguration (metadata)andruntimedataoracombinedstoragesessionforbothtypesofdata. Usingseparatestoragesessionsminimizestheriskofcorruptionthatmightoccur withacombinedstoragelocation.Inaddition,youcanusethewebMethodsBroker
272
6.5onlineconfigurationdatabackuptooltobackupconfigurationdatawithout havingtoshutdownyourBrokerServer.Formoreinformationaboutthetool,seethe webMethodsBrokerAdministratorsGuide. AcombinedstoragesessionisthetypeofstoragethatwasusedinwebMethods Broker6.1andearlier.Ifyoudonotneedtousetheonlineconfigurationdatabackup tool,usingacombinedsessionmightsaveyouasmallamountofdiskspace. Important! Youcannotlaterchangefromseparatesessionstothecombinedsessionorvice versa.webMethodsrecommendscreatingseparatesessions.
Create Separate Storage Sessions

RunthecommandbelowtocreatetheBrokerServer,itsaccompanyingfiles,andseparate storagesessionsforconfigurationandruntimedata.Youmusttypetheentirecommand onasingleline.
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]]
Argument
data_directory
Description FullyqualifiedpathtotheBrokerServerdatadirectory.If thepathincludesspaces,encloseitindoublequotation marks.ThedefaultBrokerServerdatadirectoryforUNIX orLinuxis/var/opt/webmethods/awbrokers65/default. ForWindows,itisC:\ProgramFiles\webMethods6\ Broker\data\awbroker65\default. BrokerServerruntimelicensekey. OnelinedescriptionfortheBrokerServer.Ifthestring includesspaces,encloseitindoublequotationmarks.The descriptionwillappearintheBrokerAdministratormain window. ThedefaultportforBrokerServersis6849.IfanotherBro kerServerisusingthatport,youmustusethisargument toidentifytheporttheBrokerServeryouarecreatingisto use. Bydefault,thecommandstartstheBrokerServerautomat icallyafteritcreatesit.IfyouwanttostarttheBroker Servermanuallylaterinstead,usethisargumenttopre ventthecommandfromstartingtheBrokerServer.
-k license_key [-d description]
[-p port]
[-nostart]
273
Argument
[-S]
Description Bydefault,thecommandwriteserrormessagestostderr andinformationmessagestostdout.Ifyouwanttowrite errormessagestostdoutandsuppressinformationmes sagesinstead,usethisargument. Createstheconfigurationstoragesession.Bydefault,the commandcreatestwofilesinthedefaultBrokerServer datadirectory: LogfilenamedBrokerConfig.qs.logwithamaximum sizeof32M StoragefilenamedBrokerConfig.qs.storwitha maximumsizeof512Mandaninitial(reserved)sizeof 64M ThedefaultBrokerServerdatadirectoryforUNIXor Linuxis/var/opt/webmethods/awbrokers65/default.For Windows,itisC:\ProgramFiles\webMethods6\Broker\ data\awbroker65\default.
[-session_config qs]
[-session_data qs]
Createstheruntimestoragesession.Bydefault,the commandcreatestwofilesinthedefaultBrokerServer datadirectory: LogfilenamedBrokerData.qs.logwithamaximum sizeof32M StoragefilenamedBrokerData.qs.storwitha maximumsizeof512Mandaninitial(reserved)sizeof 64M ThedefaultBrokerServerdatadirectoryforUNIXor Linuxis/var/opt/webmethods/awbrokers65/default.For Windows,itisC:\ProgramFiles\webMethods6\Broker\ data\awbroker65\default.
[-qs_log_file file_name file_size] [-qs_storage_file file_name file_size [reserved_size]]
Ifyouwanttouseadifferentnameforthelogorstorage file,oriftheBrokerServerdatadirectoryisnotinthe defaultlocation,usethefile_nameparametertospecifythe fullyqualifiedpathtothefile.Youcanalsousethe parametertocreateadditionalstoragefilesforeithertype ofsession. Ifyouwanttospecifyadifferentmaximumsizeforthelog orstoragefile,usethefile_sizeparameter.Followthesize withK(kilobytes),M(megabytes),orG(gigabytes).For informationonsettingthemaximumsizeofthesefiles,see ConfigurewebMethodsBrokeronpage 113.
274
Argument
Description Ifyouwanttospecifyadifferentinitialsizeforthestorage file,usethereserved_sizeparameter.FollowthesizewithK (kilobytes),M(megabytes),orG(gigabytes).Thesizemust beatleast16M. Anticipateasmalldelayinoperationwhilethecommand initializesthefiles. Afterinstallation,youcanremoveorreplacelogfiles,and youcanincreaseordecreasetheirsize.Youcanadd storagefilesandincreasetheirsize,butyoucannot removestoragefilesordecreasetheirsize.ThewebMethods BrokerAdministratorsGuideprovidesinstructions.
UNIX or Linux
AnexampleofthiscommandforUNIXorLinuxisasfollows:
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
Youwillseethemessage,SuccessfullycreatedBrokerServerindata_directory. Note: Ifyouexperienceproblemsrunningthislongcommandinyourcurrentshell,try runningitinabashshell. MakesuretheBrokerMonitorandtheBrokerServerarerunningbyenteringthis command:

ps -ef | grep aw
Windows
AnexampleofthiscommandforWindowsisasfollows:
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
275
Youwillseethemessage,SuccessfullycreatedBrokerServerindata_directory. MakesuretheBrokerMonitorandtheBrokerServerarerunning.OpentheServices window.LocatetheservicewebMethodsBrokerServer6.5,portxxxx,andmakesureits statusisStarted.
Create a Combined Storage Session

RunthecommandbelowtocreatetheBrokerServer,itsaccompanyingfiles,anda combinedstoragesessionforconfigurationandruntimedata.Youmusttypetheentire commandonasingleline.
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
Argument
data_directory
Description FullyqualifiedpathtotheBrokerServerdatadirectory.If thepathincludesspaces,encloseitindoublequotation marks.ThedefaultBrokerServerdatadirectoryforUNIX orLinuxis/var/opt/webmethods/awbrokers65/default. ForWindows,itisC:\ProgramFiles\webMethods6\ Broker\data\awbroker65\default. BrokerServerruntimelicensekey. OnelinedescriptionfortheBrokerServer.Ifthestring includesspaces,encloseitindoublequotationmarks.The descriptionwillappearintheBrokerAdministratormain window. Thedefaultportis6849.IfanotherBrokerServerisusing thatport,youmustusethisargumenttoidentifytheport theBrokerServeryouarecreatingistouse. Bydefault,thecommandstartstheBrokerServerautomat icallyafteritcreatesit.IfyouwanttostarttheBroker Servermanuallylaterinstead,usethisargumenttopre ventthecommandfromstartingtheBrokerServer. Bydefault,thecommandwriteserrormessagestostderr andinformationmessagestostdout.Ifyouwanttowrite errormessagestostdoutandsuppressinformationmes sagesinstead,usethisargument.
-k license_key [-d description]
[-p port]
[-nostart]
[-S]
276
Argument
[-session_config qs [-qs_log_file file_name file_size] [-qs_storage_file file_name file_size [reserved_size]]]
Description Bydefault,thecommandcreatestwofilesinthedefault BrokerServerdatadirectory: LogfilenamedBroker.qs.logwithamaximumsizeof 32M StoragefilenamedBroker.qs.storwithamaximum sizeof512Mandaninitial(reserved)sizeof64M ThedefaultBrokerServerdatadirectoryforUNIXor Linuxis/var/opt/webmethods/awbrokers65/default.For Windows,itisC:\ProgramFiles\webMethods6\Broker\ data\awbroker65\default. Ifyouwanttouseadifferentnameforthelogorstorage file,oriftheBrokerServerdatadirectoryisnotinthe defaultlocation,usethefile_nameparametertospecifythe fullyqualifiedpathtothefile.Youcanalsousethe parametertocreateadditionalstoragefilesforthesession. Ifyouwanttospecifyadifferentmaximumsizeforthelog fileorthestoragefile,usethefile_sizeparameter.Follow thesizewithK(kilobytes),M(megabytes),orG(gigabytes). Forinformationonsettingthemaximumsizeofthelog fileandthestoragefile,seeConfigurewebMethods Brokeronpage 113. Ifyouwanttospecifyadifferentinitialsizeforthestorage file,usethereserved_sizeparametertospecifythesize followedbyK(kilobytes),M(megabytes),orG(gigabytes). Thesizemustbeatleast16M. Anticipateasmalldelayinoperationwhilethecommand initializesthefiles. Afterinstallation,youcanremoveorreplacelogfiles,and youcanincreaseordecreasetheirsize.Youcanadd storagefilesandincreasetheirsize,butyoucannot removestoragefilesordecreasetheirsize.ThewebMethods BrokerAdministratorsGuideprovidesinstructions.
-use_combined_storage
Tellsthecommandtocreateacombinedstoragesession forconfigurationandruntimedata.
277
UNIX or Linux
AnexampleofthiscommandforUNIXorLinuxisasfollows:
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
Youwillseethemessage,SuccessfullycreatedBrokerServerindata_directory. Note: Ifyouexperienceproblemsrunningthislongcommandinyourcurrentshell,try runningitinabashshell. MakesuretheBrokerMonitorandtheBrokerServerarerunningbyenteringthis command:

ps -ef | grep aw
Windows
AnexampleofthiscommandforWindowsisasfollows:
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
Youwillseethemessage,SuccessfullycreatedBrokerServerindata_directory. MakesuretheBrokerMonitorandtheBrokerServerarerunning.OpentheServices window.LocatetheservicewebMethodsBrokerServer6.5,portxxxx,andmakesureits statusisStarted.
278
Create the Default Broker on Any System
Create the Default Broker on Any System

Runthiscommand:
webMethods Broker_directory/bin/broker_create Broker[@Broker_Server[:port]] -default [-description text] [-createterr territory] [-jointerr Broker[@Broker_Server[:port]]]
Argument
Broker[@Broker_Server [:port]
Description BrokerspecifiesthenametogivetheBrokeryouare creating. Broker_Server[:port]identifiestheBrokerServeronwhich theBrokeristorun(thatis,theBrokerServeryoujust created).IftheBrokerServerisonthelocalhost,youdo nothavetospecifythesearguments.
[description text]
OnelinedescriptionoftheBroker.Ifthestringincludes spaces,encloseitindoublequotationmarks.The descriptionwillappearintheBrokerAdministratormain window. CreatesanewterritoryandmakestheBrokeryouare creatingthefirstmemberofthatterritory. IdentifiesanexistingBrokerandmakestheBrokeryouare creatingamemberofthesameterritoryofwhichthe existingBrokerisamember.
[-createterr territory] [-jointerr Broker[@Broker_Server [:port]]
Anexampleofthiscommandisasfollows:
webmethods6/Broker/bin/broker_create "Broker #1"@hostname:7700 -default
UseBrokerAdministratortomakesurethedefaultBroker(Broker#1)isrunning.For instructions,seethewebMethodsBrokerAdministratorsGuide.
Enable the Broker Server to Log Events to the UNIX or Linux System Log
IfyouwanttheBrokerServertologBrokerServereventstotheUNIXorLinuxsystem log,askyoursystemadministratortocreatethenecessaryentriesintheUNIXorLinux systemlogconfigurationfile.Thesystemadministratormustlogonasrootuserandrun thesecommands:
$ echo "local5.alert /var/log/broker.alert" >> /etc/syslog.conf $ echo "local5.info /var/log/broker.info" >> /etc/syslog.conf
279
Adjust Per-Process and Kernel Limits on HP-UX Systems

IfyouinstalledwebMethodsBrokeronanHPUXsystem,askyoursystemadministrator toadjusttheperprocessthreadlimitandsettheperprocessandkernellimitforthe maximumnumberofopenfiles.Forinstructions,seetheHPUXsystemmanual.
Set Locale on UNIX or Linux Systems

IfyouaregoingtorunwebMethodsBrokerinalocaleotherthanU.S.English,you probablysetyourshelltotheproperlocalebeforeinstallation.However,thissettingonly affectsthewaythewebMethodsInstallerstartsyourBrokerServerduringinstallation. WhenyourestarttheBrokerServer,theBrokerServerwillusethedefaultlocale,U.S. English.IfyouwanttosettheBrokerServertorunusingadifferentlocale,setthe environmentvariablesLC_ALLandLANGtothatlocale.
Enable Full Core Dumps on AIX Systems

OnAIXsystems,bydefault,theabilitytoperformfullcoredumpsisnotenabled.Ifyou wanttoenablethisability,dooneofthefollowing: Runthiscommand:
chdev -l sys0 -a fullcore=true
UsetheAIXSystemManagementInterfaceTool(SMIT).Runthecommandsmitty
chgsysandsetthevalueofEnablefullCOREdumptotrue.
YoudonothavetoreboottheAIXsystemforthischangetotakeeffect.
280
Index
Numerics
64-bit JDK, have installer install 81 Broker Server configure storage session 88, 114 data directory for 87, 113 log file size 88, 114 port for 87, 113 browsers, required 38
A
Access hardware requirements 40 installation location 18 Administrator hardware requirements 40 installation location 19 advanced options description of 70 use to install 76, 78, 108 valid combinations of 71
C
command line, use to install from an installation script on a Windows system 106 console mode use to install 107 use to uninstall 239 conventions used in this document 12 corrupt installations, overwrite 103, 124 Cross-Reference database component set up JDBC connection pool 170
B
Broker (webMethods Broker) adjust per-process thread limit on HP-UX system 280 adjust per-process thread limit on HP-UX systems 190 configure Brokers and JMS 20 data directory for Broker Server 87, 113 develop custom C messaging applications 20 develop custom Java messaging applications 20 develop custom JMS messaging applications 21 hardware requirements 40, 41 installation location 19 license key 87, 113 make sure default Broker is running 189 port for Broker Server 87, 113 set per-process and kernel limit for open files on HP-UX system 280 set per-process and kernel limit for open files on HP-UX systems 190 use non-default JDK 232 Broker Administrator, installation location 19
D
Data Connection Limited SNAP-IX 38 database components descriptions 260 drop My webMethods Server using commands 244, 247 install My webMethods Server using commands 138, 149 install My webMethods Server using configurator 183 install using SYS or SYSTEM user account 46 install Workflow 213 products that require them 260 where to install them 34, 35 database drivers, supported 44 database servers bandwidth 34 hardware 44 database URLs DB2 172 Oracle 171 SQL Server 171 Sybase 171
281
Index
database user 130, 132, 144, 146, 154, 155, 157, 164, 166 database user permissions 130, 144, 154, 155, 157, 164, 166 databases character set and sort order 44 encodings for international operating environments 50 page and block size 44 supported 44 DB2 URLs 172 dependencies among webMethods products 18 Deployer hardware requirements 40, 41 installation location 21 Developer browse services in Servicenet 22 develop C/C++ services 22 generate services from a .NET assembly 22 hardware requirements 40 installation location 22 rebuild C/C++ shared libraries 22 use non-default JDK 232 display problems on OS/400 systems 56, 74, 239 Document History database component set up JDBC connection pool 170 documentation additional 13 conventions used 12 feedback 13
H
hardware requirements for webMethods products 37 Hewlett-Packard SNAplus2 38
I
IBM Communications Server for NT 38 install display problems on OS/400 systems 56, 74, 239 from an installation image 110 from an installation script on a UNIX system 109 from an installation script on a Windows system 106 on a remote machine 67 on a Windows system using a wizard 74 on machines that cannot go outside firewall 70 specify server to download from 110 use a proxy server 81 use a proxy server to 70, 108 using console mode 107 installation image create 80, 109 description of 70 extra memory required to create 75, 77, 107 extra memory required to install from 66, 67 install from 110 installation log file 56, 74, 106 installation script create 79, 108 description of 70 install from on a UNIX system 109 install from on a Windows system 106 Integration Server access .NET environment 24 change access permissions for on UNIX and MAC OS X systems 193 cluster support 25 configure to write to a database 175 dedicate instance to running Monitor 30 develop C/C++ services 24 hardware requirements 40 identify compiler to use with Developer 191 identify JRE to use on OS/400 systems 193 increase memory on OS/400 systems 193
E
EDI Module hardware requirements 40 installation location 22 EDIINT Module hardware requirements 40 installation location 22 extended character set encoding support 24
F
firewall, install on machines that cannot go outside of 70
282
install in development environment as a Windows application 89, 115, 189 install in production environment as a Windows service 89, 115, 189 installation location 23 let portlets running in My webMethods Server use My webMethods Server users to call services 24 license key 89, 115 rebuild C/C++ shared libraries 24 store keys and certificates securely 24 streamline 194 support for extended character set encoding 24 use non-default JDK 232 WmDB package, use for backward compatibility 25 Integration Server Administrator, description of 23 Integration Server-webMethods Mainframe Package, installation location 25 international operating environments, support for 49 IS Core Audit Log database component set up JDBC connection pool 170
M
Mainframe (webMethods Mainframe) create and modify host connection pools and transactions 26 enable communication with Integration Server and Developer 26 hardware requirements 40 installation location 25 SNA communications server requirements 38 Mainframe Administrator, description of 25 Mainframe Package installation location 25 Mainframe Plug-in installation location 25 use to create and modify webMethods Mainframe host connection pools and transactions 26 Manager hardware requirements 40, 41 installation location 26 use non-default JDK 232, 233 Manager server change JDBC pool configuration 94, 118 install in development environment as a Windows application 93, 117 install in production environment as a Windows service 93, 117 license key 93, 117 use non-default JDK 232 Microsoft Host Integration Server 2000 38 Modeler browse services in Servicenet 28 give permissions for on UNIX system 197 hardware requirements 40 use non-default JDK 233 Modeler Repository hardware requirements 40 Modeler Repository database component configure 177 Monitor graphical display utility requirements 198 hardware requirements 40 installation location 30
J
JDBC connection pools change configuration of for Manager server 94, 118 change configuration of for Trading Networks 98, 122 set up 170 specify for Manager server database component during installation 94, 118 specify for Trading Networks database component during installation 97, 121 JDKs, required 38 JMS Administrator installation location 19 JREs, required 38
L
language packs 50 log file for installation 56, 74, 106 for uninstallation 238 Logging Utility installation location 20, 33
283
Index
My webMethods Server hardware requirements 40 use non-default JDK 233 My webMethods Server database component drop using commands 244, 247 install using commands 138, 149 install using configurator 183
O
operating systems, supported 38 Optimize hardware requirements 40, 41 Oracle URLs 171 OS/400 systems installer display problems 74 uninstaller display problems 239 OS/400 systems, installer display problems 56 overwrite corrupt installations 103, 124
RDBMS URLs DB2 172 Oracle 171 SQL Server 171 Sybase 171 reinstall corrupt installations 103, 124 remote machine, install on 67 remote machine, uninstall from 239 replace corrupt installations 103, 124 Reporting database component set up JDBC connection pool 170 required JREs/JDKs and browsers 38
S
script, description of 70 Servicenet hardware requirements 40, 43 installation location 31 register and manage Web services hosted in any Web serivce container 32 register and manage Web services hosted in Glue 32 register and manage Web services hosted in Integration Server 32 register and manage Web services hosted in WebLogic 32 register Web services hosted in .NET server 32 servlet engines supported by Workflow 39 SNA communications servers supported by webMethods Mainframe 38 software requirements for webMethods products 37 SQL Server URL 171 Staging database component set up JDBC connection pool 170 streamline Integration Server 194 support for international operating environments 49 supported operating systems 38 supported RDBMSs and database drivers 44 Sybase URL 171 SYS or SYSTEM user account for database install 46
P
Portal develop portlets 19 hardware requirements 40 installation location 18 manage ADAM users and groups 19 manage LDAP users and groups 19 monitor clustered Portal servers 19 work with Web services clients and portlets 19 Process Audit Log database component set up JDBC connection pool 170 Process Tracking Store database component configure 175 product dependencies 18 program code conventions in this document 12 proxy server, use to install 70, 81, 108
R
RDBMS character set and sort order 44 page and block size 44 supported 44
284
T
Trading Networks change JDBC pool configuration 98, 122 enable Manager server to manage Trading Networks Server 33 hardware requirements 41, 43 store keys and certificates securely 33 Trading Networks Console installation location 32 use non-default JDK 233 Trading Networks Server, installation location 32 Trading Networks Web Manager description of 32 troubleshooting information 13 typographical conventions in this document 12
U
uninstall from a UNIX system using a wizard 239 from a Windows system using a wizard 238 on a remote machine 239 using console mode 239 uninstallation log file 238 uninstaller, uninstall mode choices 238 URLs DB2 172 Oracle 171 SQL Server 171 Sybase 171
W
webMethods Installer run as a wizard on a Windows system 74 run in console mode 107 server, specify 110 webMethods products hardware requirements 37 software requirements 37 webMethods Uninstaller run as a wizard on a UNIX system 239 run as a wizard on a Windows system 238 run in console mode 239 uninstall mode choices 238
Windows application, install Integration Server as 189 Windows service, install Integration Server as 189 wizard use to install on a Windows system 74 use to uninstall from a UNIX system 239 use to uninstall from a Windows system 238 WmInstallLog.txt file 56, 74, 106 WmUninstallLog.txt file 238 Workflow does not support use of firewall 39 hardware requirements 41, 43 servlet engine requirements 39 use Apache Tomcat as servlet engine 39 use BEA WebLogic as servlet engine 39 use with Modeler 33 Workflow client installation location 33 use non-default JDK 233 Workflow Configurator 215 Workflow database component, install 213 Workflow Server configure to write to the Process Audit Log database 220 configure to write workflow models to database 222 connect to Broker 219 drop database tables 223 enable to send email notifications 220 install central 100, 123 install secondary 101, 123 installation location 33 provide authentication for 216 set up for automatic startup on Solaris, HP-UX, and AIX systems 213 synchronize with Broker 223 use Integration Server Tomcat as servlet engine 39
285
Index
286

Web Methods Installation Guide 6 5 and 6 5 1

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Web Methods Installation Guide 6 5 and 6 5 1

Hochgeladen von

Copyright:

Verfügbare Formate

webMethods

VERSION 6.5 AND 6.5.1

Document ID: WEBM-IG-65-20060811

Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1. Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2. Software and Hardware Support and Requirements . . . . . . . . . . . . . . . . . . . .

webMethods Installation Guide Version 6.5 and 6.5.1

Chapter 3. Support for International Operating Environments . . . . . . . . . . . . . . . . . . . . . . 49

Part II. Simple Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Chapter 4. Simple Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Part III. Advanced Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Chapter 5. Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

webMethods Installation Guide Version 6.5 and 6.5.1

Chapter 6. Advanced Installation Using the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

webMethods Installation Guide Version 6.5 and 6.5.1

Chapter 7. Advanced Installation Using Console Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

webMethods Installation Guide Version 6.5 and 6.5.1

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

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

webMethods Installation Guide Version 6.5 and 6.5.1

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

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

webMethods Installation Guide Version 6.5 and 6.5.1

webMethods Installation Guide Version 6.5 and 6.5.1

Part VI. Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Chapter 14. Uninstalling Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Chapter 15. Dropping Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

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

Appendix B. Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

webMethods Installation Guide Version 6.5 and 6.5.1

Appendix C. Create the Broker Server Configuration Manually . . . . . . . . . . . . . . . . . . . . . 267

webMethods Installation Guide Version 6.5 and 6.5.1

webMethods Installation Guide Version 6.5 and 6.5.1

About This Guide

About This Guide

IfyoumustperformcertainconfigurationtasksbeforeyoustartawebMethodsproduct, thisguideexplainsthoseconfigurationtasks.ThedocumentationforeachwebMethods productexplainshowtostarttheproductandhowtoperformconfigurationtasksafter theproductisstarted.

webMethods Installation Guide Version 6.5 and 6.5.1

webMethods Installation Guide Version 6.5 and 6.5.1

webMethods Installation Guide Version 6.5 and 6.5.1

webMethods Installation Guide Version 6.5 and 6.5.1

webMethods Installation Guide Version 6.5 and 6.5.1

webMethods Installation Guide Version 6.5 and 6.5.1

Planning Your Installation

webMethods Installation Guide Version 6.5 and 6.5.1

webMethods Installation Guide Version 6.5 and 6.5.1

If you want to... Developportlets ManageADAMusersandgroups ManageLDAPusersandgroups MonitorclusteredPortalservers WorkwithWebservicesclientsand portlets

Install this item... SDK ADAM LDAPBrowser RemotePortalLogViewer TCPTunnelMonitor

InstallwebMethodsBroker onamachineonthesame networkasother webMethodsproducts. InstallIntegrationServer, BrokerAdministrator,and JMSAdministratoron anothermachineonthe network.

webMethods Installation Guide Version 6.5 and 6.5.1

webMethods Installation Guide Version 6.5 and 6.5.1

If you want to... DevelopandruncustomJMSmessaging applicationsthatinteractwithyourBro ker Runsamplemessagingapplicationswith yourBrokerusingAPIsfordifferentpro gramminglanguages

Install this item... JMSClientAPI*

webMethods Installation Guide Version 6.5 and 6.5.1

EDI Module and EDIINT Module

Products Required on Same Machine as EDI Module IntegrationServer6.5 TradingNetworksServer6.5

EDI Module Requirements for Full Operation Developer6.5 TradingNetworksConsole6.5

webMethods Installation Guide Version 6.5 and 6.5.1

Products Required on Same Machine as EDIINT Module IntegrationServer6.5 TradingNetworksServer6.5

webMethods Installation Guide Version 6.5 and 6.5.1

Products Required on Same Machine as Integration Server None

Install this item... CommonAuthorizationPackage

ExtendedCharacterSetEncoding Support MicrosoftPackage PKISupport

webMethods Installation Guide Version 6.5 and 6.5.1

If you want to... Storeandtrackscheduledjobs,sessioncon text,andjobstrackedbyguaranteeddelivery forclusteredIntegrationServers

Install this item... RepositoryServer Note: Youcanbutdonothaveto installthisitemonanIntegration Serverhostmachine. WmDB

webMethods Installation Guide Version 6.5 and 6.5.1