Web Methods Installation Guide 6 5 and 6 5 1
Web Methods Installation Guide 6 5 and 6 5 1
Web Methods Installation Guide 6 5 and 6 5 1
Installation Guide
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.
Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Part I.
15 17
18 18 19 19 21 22 22 23 25 26 28 28 29 30 30 31 32 33 34 36
37
38 38 38 39 39 39 41
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
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
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
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
Contents
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
10
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
11
Contents
12
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
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
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
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
Whenyouinstall webMethodsBroker,you actuallyinstallaBroker Serverandadefault My webMethods Broker.TheBrokerServer Server managestheflowof documentsand communicationamongBrokers,Brokerclients,JMSclients,andvariousapplications. BrokersarethesoftwaretowhichBrokerclientsandJMSclientsconnect.
IS Core Audit Log
19
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
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
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
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
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
Developer
22
Integration Server
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
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
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
C/C++SDK
24
webMethods Mainframe
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
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
Install this item... MainframePlugin Note: InstallontheDeveloperhostmachine. MainframePackage Note: InstallontheIntegration Server/webMethodsMainframehostmachine.
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
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
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
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
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
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
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
My webMethods Server
My webMethods Server My webMethods Server
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
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
RegisterandmanageWebservices hostedinGlue
RegisterandmanageWebservices hostedinanyWebservicecontainer
RegisterWebserviceshostedin Microsoft.NETserver
RegisterandmanageWebservices hostedinIntegrationServer
Trading Networks
Trading Networks Trading Networks Console Trading Networks Server
Developer
Integration Server
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
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
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 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
34
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
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
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
Developer
Workflow interfaces Monitor interface Servicenet interface Manager/Optimize interface Access or Portal My webMethods Server
Servicenet registry
Servicenet
My webMethods Server
Manager server
Manager Server
36
CHAPTER
37
38
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
RAM (MB)
Virtual/Swap (MB)
CPUs
NothingbeyondMywebMethodsServer.
NothingbeyondIntegrationServer 128(256) 1
1 1 1 1
100
500 500 4 50
1 1 1
NothingbeyondMywebMethodsServer.
500 500
1000(2000) 1000(2000)
1000 1000
1 1
40
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.
41
Thecontrollerrequiresadditionalharddrivespaceforlogfiles.Therecommended amountis100MB.Thecontrollerrequires7MBofharddrivespaceforeachlogfile. Inadevelopmentenvironment,thecontrollerhasthesehardwarerequirements: Hard Drive Space (MB) 100 Virtual/ Swap (MB) 1000
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
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
Hardware Recommendations
ProvideasmuchRAMaspossibletodatabaseservers.Makesurethedatabaseserversuse thefastestdiskdrivesavailable;RAIDlevel10isthefastestRAIDlevelthatsupports redundancy.
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.
46
TherighttoexecuteDBMS_JOBdoesnotallowausertotouchanyjobsexcepttheirown. Jobsarecreatedinthecontextoftheuser,notasSYSorSYSTEM.
47
48
CHAPTER
49
Overview
webMethodsproductsaredesignedforuseanywhereintheworldandenableyouto exchangedatawithsystemsanduserswhospeaklanguagesotherthanyourown.For specificinformationonthetesting,configuration,capabilities,andlimitationsofany webMethodsproduct,seetheproductsreadme.
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
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
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.
e 2
IfyouaregoingtoinstalltheManagerserverorTradingNetworksServer,askyour databaseadministratortosetupadatabaseuser,password,andpermissionsforeach
56
productsdatabasecomponent.Eachdatabaseusermustbeabletoselect,insert, update,anddeleterowsfromthetablesinitsdatabasecomponent.
TheinstallertakesseveralsecondstounzipandlaunchitsJVM,thendisplaysthe welcomepanel.
ClickNext.
57
ProvidetherequestedinformationandthenclickNext.
58
Windows only
ProvidetherequestedinformationandthenclickNext. Important! DonotinstallwebMethodsBrokerinthesamedirectoryasaprewebMethods6 versionofwebMethodsBrokerorinthesamedirectoryasanyotherwebMethodsBroker product. IfyouareinstallingWorkflowandaregoingtouseIntegrationServersTomcatpackageas yourWorkflowservletengine,youcannotinstallIntegrationServerintoadirectory whosepathcontainsspacesbecauseofaproblemrelatingto1.4.xJDKs.Forexample,you cannotinstallIntegrationServerinthedirectoryProgramFiles\webMethods6. Intherootdirectoryyouspecify,theinstallerwillautomaticallyinstalleachproductina subdirectorynamedaftertheproduct.
59
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
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
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
65
66
2 3
67
NFS-Mounted Partition
IfyouaregoingtoconfigureBrokerServertocreatedatafilesonanNFSmounted partition,mountthepartitionusingthecommandbelow.Theoptionsonthecommand helpprotectdataintegrity.
mount -o hard,nointr,proto=tcp host:/path /mount_point
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
69
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
71
72
CHAPTER
73
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).
74
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
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
TheinstallertakesseveralsecondstounzipandlaunchitsJVM,thendisplaysthe welcomepanel.
NavigatetothedirectorythatcontainsthewebMethodsInstallerandstartthe installerbyenteringthiscommand:
java -jar webMethodsInstaller65.jar -console
76
HPUX Linux
*ThecommandvariesslightlybasedontheversionoftheJREyouhaveinstalled.
77
TheinstallertakesseveralsecondstounzipandlaunchitsJVM,thendisplaysthe welcomepanel.
78
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
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
user name and password for installer to use to log on to proxy server
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.
84
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
85
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.
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
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.)
88
Configure Products
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
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
Important! Donotuselocalhosttoidentifythehostmachines.
90
Configure Products
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
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
92
Configure Products
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
driver to use to communicate with database see below database user and password for Manager server to use to log in to database
jdbc:wm:sqlserver://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
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
Important! Donotuselocalhosttoidentifythehostmachines.
95
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
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
1433 5000
97
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
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
99
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
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
101
102
103
104
CHAPTER
105
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).
106
NavigatetothedirectorythatcontainsthewebMethodsInstallerandstartthe installerbyenteringthiscommand:
java -jar webMethodsInstaller65.jar -console
107
HPUX Linux
*ThecommandvariesslightlybasedontheversionoftheJREyouhaveinstalled.
Ifyouwanttouseaproxyservertoinstall,createorrunaninstallationscriptorimage, downloadwebMethodsproductsfromyourownserver,orinstalla64bitJDK,addthe parameterslistedbelowinanyorderafter-jar webMethodsInstaller651.jar. Parameter Use an HTTP proxy server to install
-proxyHost host
Variables
-proxyPass password
-socksProxyPort port
Fullyqualifiednameofthefileinwhichto savethescript.
Fullyqualifiednameofthefileinwhichto savethescript.
108
Parameter
Variables
-writeScript script_file
Edit a script
-editScript script_file
Fullyqualifiednameofthefilethatcontains thescripttoedit.
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
Variables
Fullyqualifiednameofthefilethatcontains theinstallationimagefromwhichtoinstall.
-serverVersion version
Letsyouinstalla64bitJDKona64bitSolaris, HPUX,orAIXoperatingsystem.
110
Intherootdirectoryyouspecify,theinstallerwillautomaticallyinstalleachproductina subdirectorynamedaftertheproduct.
Finding Items
Thetablebelowindicatesthelocationofcertainitemsintheinstallerproducttree. This item... BrokerAdministrator,JMSAdministrator,LoggingUtility, MainframePackage,ModelerDesignPackage,ProcessRunt ime,ServicenetPackage,andWorkflowServlet Productuserinterfaces(forexample,Monitoruserinterface) ExtendedCharacterSetEncodingSupportandServicenet ClientAPI Is listed under... IntegrationServer
111
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
115
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
OptimizecreatesaJDBCconnectionpoolforeachdatabasecomponent.Ifyoulaterneed tomodifytheconnectionpools,seethewebMethodsDatabaseGuideforinstructions.
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
jdbc:wm:sqlserver://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
1433
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.
Important! AllServicenetcomponentsarepreconfiguredtousethedefaultSubnet port.If youdistributeServicenetcomponentsovermultiplemachines,changingtheSubnet port fromthedefaultwillrequireyoutoperformmanualconfigurationtasksafterinstallation. However,ifyouintendtosetupmorethanoneServicenetenvironment,youmustusea differentsubnetportforeachenvironmenttopreventconflicts. ServicenetcreatesaJDBCconnectionpoolforeachdatabasecomponent.Ifyoulaterneed tomodifytheconnectionpools,seethewebMethodsDatabaseGuideforinstructions.
120
Default Port
1521
1521
SQL Server
jdbc:wm:sqlserver://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
1433
Sybase
jdbc:wm:sybase://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
5000
DB2 UDB
jdbc:wm:db2://host_or_IPaddress:port; databaseName=database_name; PackageName=package_name
50000
121
Box or Prompt
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
124
5 6
125
126
PART
IV
127
128
CHAPTER
129
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.
2 3
130
Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components
GotoChapter 12,IdentifyingDatabasesforUsebyProducts.
Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components
Set Up Database Users
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
2 3
Saveandclosethefile.
132
Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components
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
ISCOREAUDIT_DBLINK
134
Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components
Property PROCESS_SCHEMA
ISCORE_SCHEMA
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.
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%
136
Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components
Installthedatabasecomponentbyrunningthiscommand:
sqlplus database_user@service_name @code/create_database_component_ 6-5_ora.sql %DBCALL_INPUT_STRING%
c 2
Saveandclosethefile.
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.
137
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
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.
database_server_host
database_server_port
SID
140
Reinstall the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet Database Component
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
143
Overview
ThischapterexplainshowtoinstallwebMethodsdatabasecomponentsinSQLServer. 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.
2 3
144
Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components
GotoChapter 12,IdentifyingDatabasesforUsebyProducts.
Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components
Set Up Database Users
Youcancreatedatabasesanddatabaseusersaspartoftheinstallationprocessdescribed inthissectionoryoucanhaveyourdatabaseadministratorsetthemup. Ifyouwantyourdatabaseadministratortosetupthedatabasesanddatabaseusers,ask thedatabaseadministratortocreateonedatabaseanddatabaseuserforeachdatabase component.Assignthedatabaseuserthepermissionslistedinthe
145
Saveandclosethefile.
146
Install the Analysis, Archive, Manager Server, Process Audit Log, Process Tracker, and Servicenet Database Components
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
Saveandclosethefile.
148
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,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.
149
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.
150
Parameter
database
Entry Nameofthedatabaseinwhichtoinstallthedatabasecompo nent. Administratoruserforthedatabaseserver. Administratorpasswordforthedatabaseserver. DatabaseuserforMywebMethodsServer,Access,orPortal tousetocommunicatewiththedatabase.Thedatabaseuser mustbeuniqueforthedatabaseserver. Passwordforthedatabaseuser. Tellsthecommandtocreateadatabaseanddatabaseuserand installthedatabasecomponentinthenewdatabase.
database_user_ password 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.
151
Parameter
database
Entry Nameofthedatabaseinwhichtoinstallthedatabasecompo nent. Enterthesamevalueyouenterfordatabase_user. Enterthesamevalueyouenterfordatabase_user_password. DatabaseuserforMywebMethodsServer,Access,orPortalto usetocommunicatewiththedatabase. Passwordforthedatabaseuser. Tellsthecommandtoinstallthedatabasecomponentinan existingdatabaseusinganexistingdatabaseuser.
database_user_ password n
Reinstall the Analysis, Archive, Process Audit Log, Process Tracker, or Servicenet Database Component
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
153
Overview
ThischapterexplainshowtoinstallwebMethodsdatabasecomponentsinDB2.Database componentsareinstalledusingdifferentmethods;thesectionheadingsindicatewhich databasecomponentsarecoveredineachsection. 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.
154
GotoChapter 12,IdentifyingDatabasesforUsebyProducts.
155
Saveandclosethefile.
156
Install the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components
Install the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components
Set Up Database Users
Askyourdatabaseadministratortosetupthedatabaseuser,password,andpermissions foreachdatabasecomponent.Eachdatabaseusermustbeabletoselect,insert,update, anddeleterowsfromthetablesinitsdatabasecomponent.
Saveandclosethefile.
157
158
Install the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components
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
ManagerServer
code/managerserver/create/db2_mgr_c_ddl_tables_indexes.sql
159
c 2
Saveandclosethefile.
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
160
Install the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components
databasecomponent,theISCoreAuditLogdatabasecomponent,orboth,depending onthedatayouwanttoarchive.
161
162
CHAPTER
11
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.
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.
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
GotoChapter 12,IdentifyingDatabasesforUsebyProducts.
165
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
Install the Archive, Process Audit Log, Reporting, and Staging Database Components
Set Up Database Users
Askyourdatabaseadministratortosetupthedatabaseuser,password,andpermissions foreachdatabasecomponent.Eachdatabaseusermustbeabletoselect,insert,update, anddeleterowsfromthetablesinitsdatabasecomponent.
2 3
166
Install the Archive, Process Audit Log, Reporting, and Staging Database Components
ProcessAuditLog
Reporting
Staging
167
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
168
CHAPTER
12
169
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
Identify the Databases that Contain the Cross-Reference, Document History, IS Core Audit Log, Process Audit Log, Reporting, and Staging Database Components
Default Port
1521
1521
SQL Server
jdbc:wm:sqlserver://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
1433
Sybase
jdbc:wm:sybase://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
5000
171
Box
50000
FortheArchive,Reporting,andStagingdatabase components:
BatchPerformanceWorkaround=true
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
Identify the Databases that Contain the Cross-Reference, Document History, IS Core Audit Log, Process Audit Log, Reporting, and Staging Database Components
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
ClickSave Settings.
173
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
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.
176
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.
177
Property URL
Default Port
1521
SQL Server
jdbc:wm:sqlserver://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
1433
DB2 UDB
jdbc:wm:db2://host_or_IPaddress:port; databaseName=database_name; PackageName=package_name;
50000
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
178
PART
179
180
CHAPTER
13
181
Post-Installation Checklist
Thechecklistbelowidentifiestasksyouneedtoperformtomakeabasicinstallationof webMethodsproductsoperational.Subsequentsectionsinthischapterorbookprovide detailedinstructions.Sectionsinthischapteralsoprovidedetailedinstructionsforother tasksyoumightwantorneedtoperform. Product Access,My webMethods Server,Portal webMethods Broker Task RunthePortalServerConfigurator Page 183
Deployer
Integration Server
191 191 192 192 196 196 197 197 198 198
Monitor
SetupauthenticationtorunMonitorservices InstallSVGplugin
182
Configure Logging
Most products
ConfigurecommunicationbetweenMywebMethodsServer andotherwebMethodsproducts
Configure Logging
YoucanlogvarioustypesofdataforwebMethodsproducts.Fordetailedinformationand instructionsonsettinguplogging,seethewebMethodsLoggingGuide.
183
IfyouareconfiguringMywebMethodsServeralone,theconfiguratordisplaystheGeneral tab.IfyouareconfiguringAccessorPortal,theconfiguratordisplaystheNew Server Instancetab.Thistabletsyoucreateservers.SinceyouareconfiguringthedefaultAccess orPortalserver,clickNext.InNew Portal Server Instance Namefield,typeanameforthe defaultserveroracceptthedefaultname(default).ClickNext.Theconfiguratordisplays theGeneraltab.
184
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.
186
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
ClickNext.Theconfiguratortakestheappropriateaction,thendisplaysthePortaltab.
188
Service.ClickInstall webMethods Portal Server as a Windows Service.Inaseparate window,theconfiguratorchangesthe servertoaWindowsservice.ClickStart webMethods Portal Windows Service.
Make Sure the Broker Server is Running and the Default Broker Exists
Onmostsystems,afterinstallation,BrokerMonitorautomaticallystartsBrokerServer, whichbeginsrunningwithadefaultBroker.Usethebroker_statuscommandtomake suretheBrokerServerisrunningandthedefaultBrokerexists,asfollows:
189
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.
UsetheAIXSystemManagementInterfaceTool(SMIT).Runthecommandsmitty
chgsysandsetthevalueofEnablefullCOREdumptotrue.
YoudonothavetoreboottheAIXsystemforthischangetotakeeffect.
190
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}
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.
192
Saveandclosethefile.
193
Saveandclosethefile.
WmFlatFile WmOmiAgent
194
Package WmOmiIs
WmWin32
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
InIntegrationServerAdministrator,gotothePackages
195
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
196
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
197
fortheWmComauthpackage.Completethepageasfollows: Entry Selectthecheckbox. MachinethathostsMywebMethodsServer. PortforMywebMethodsServer.ThedefaultportforMy webMethodsServeris8080. UsernameforIntegrationServertousetologontoMy webMethodsServer.Youcanusethedefaultusernameor createausernameinMywebMethodstouse.Forinstructions oncreatingusernames,seeMywebMethodsServer AdministratorsGuide. Passwordfortheusername. MonitorgrouptowhichtoassigntheMywebMethodsusers whoaretryingtorunMonitorservicesonIntegrationServer. ClickMonitorAdministrators.
198
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}
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.
3 4
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
Saveandclosethefile.
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>
Saveandclosethefile.
Deploythepluginbyrunningthiscommand:
ant deploy.wlplugin
203
204
Saveandclosethefile,thenrestartallServicenetcomponents.
WAN
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.
Subnetlocators andanon defaultportyou specifiedduring installation Subnetlocators andanon defaultportyou specifiedduring installation
Configureallpluginsandintermediariesto usethenewport.SeeConfigureServicenet ComponentstoUseSubnetLocatorson page 208. Configureallcomponentstousethenon defaultport.SeeConfigureServicenet ComponentstoUseSubnetLocatorson page 208.
206
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
207
Gotothe<discovery>sectionandsetthe<useLocator>elementtostatic.For example:
<discovery> <noPath>fabric://failover&monitor</noPath> <useLocator>static</useLocator> <useSignatures>true</useSignatures>
Saveandclosethefile,thenrestartallServicenetcomponents.
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
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>
3 4
210
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>
Saveandclosethefile.
212
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
213
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
Tostartthegraphicalconfigurator,gototheWorkflowServer_directory/bin directoryandenterthiscommand:
./configure.sh
Tostartthenongraphicalconfigurator,gototheWorkflow Server_directory/bindirectoryandenterthiscommand:
./configure.sh -nogui
TheConfiguratordisplaystheJDK Parameterspanel.
215
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.
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.
217
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
219
ClickNext.TheconfiguratordisplaystheSMTP 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
Default Port
1521
1521
SQL Server
jdbc:wm:sqlserver://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
1433
Sybase
jdbc:wm:sybase://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
5000
DB2 UDB
jdbc:wm:db2://host_or_IPaddress:port; databaseName=database_name; PackageName=package_name;
50000
221
Default Port
1521
SQL Server
jdbc:wm:sqlserver://host_or_IPaddress:port; databaseName=database_name;SelectMethod=cursor
1433
DB2 UDB
jdbc:wm:db2://host_or_IPaddress:port; databaseName=database_name; PackageName=package_name;
50000
446
222
223
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.
RepeatthesestepsforeveryWorkflowclient.
224
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
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
Ifyouwanttouseclientsideauthentication,alsoaddthisparameter:
-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.
226
4 5 6
Ifyouwanttouseclientsideauthentication,alsoaddthisparameter:
-Dbroker.ssldname= CN=cn_info,O=organization,L=location,ST=state,C=country
Saveandclosethefile.
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
Ifyouwanttouseclientsideauthentication,alsoaddthisparameter:
-Dbroker.ssldname= CN=cn_info,O=organization,L=location,ST=state,C=country
Saveandclosethefile. 7 RestartBEAWebLogic.
6 7
228
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
GototheWorkflowclient_directory/bindirectoryandrunthe clientmgr.shscript.
Managerserver
Monitor
2 3 Workflow
230
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
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.
1 2 1 2 3
Managerserver
1 2
232
Product Modeler
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
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
Overview
UninstallwebMethodsproductsusingthewebMethodsUninstaller.ThewebMethods Installerinstalledallfilesyouneedtoruntheuninstaller. Youcanruntheuninstallerusingdifferentmodes,asfollows: System Windows UNIX,Linux,orMacOSX OS/400 Mode wizard wizardorconsolemode consolemode
238
b c
239
240
241
242
CHAPTER
15
243
Drop the Analysis, Archive, Process Tracker, and Servicenet Database Components
Dropthesedatabasecomponentsbydroppingtheschemathroughthedatabase administrationutilityprovidedbyyourdatabasevendor.
244
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.
database_server_host
instance
database_server_port
245
Forexample,thefollowingcommanddropstheMywebMethodsServerdatabase componentfromthemywebmserver_dbinstanceontheoraserverdatabaseserver:
dbdrop.bat oraserver:1521 mywebmserver_db sys syspassword mywebmserveruser
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 the Analysis, Archive, Process Tracker, and Servicenet Database Component
Dropthesedatabasecomponentsbydroppingthedatabasethroughthedatabase administrationutilityprovidedbyyourdatabasevendor.
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_server_host
database
database_server_port
Forexample,thefollowingcommanddropstheMywebMethodsServerdatabase componentfromthemywebmserver_dbdatabaseonthesqlserverdatabaseserver:
dbdrop.bat sqlserver:1433 mywebmserverdb sa password mywebmserveruser
248
Drop the Analysis, Archive, Manager Server, Process Audit Log, and Process Tracker Database Components
YoucandropthesedatabasecomponentsusingthewebMethodsDatabaseInstalleror youcandropthemmanually.
249
250
251
252
APPENDIX
Default Ports
Default Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
253
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
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
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
256
Default Ports
Default Port
Protocol/Port Type
HTTP
RMI
257
258
APPENDIX
Database Components
Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Monitor Service pub.monitor.archive:setOperationParameters . . . . . . . . . . . . . . . . . . . . . . 264
259
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
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
261
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
ThePRTcanwriteprocessexecutiondatatothisdatabasecompo nent.Bydefault,thePRTwritestoRAM. Monitorbuiltinservicescanwriteprocessstatusdataextracted fromtheProcessAuditLogdatabasecomponentandaggregated intodailystatisticstothisdatabasecomponent.Monitordisplays thisdata. Note: ReportingisavailableonlyondatacollectedafterJanuary1, 2003.Also,thereportsareonlyavailableinEnglish.Theyarenot localizedandarenotavailableintheJAlanguagepack.
262
Descriptions
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
ISCOREAUDIT _DBLINK
PROCESS_SCHEMA
IfyoudonotwanttoarchivefromtheProcessAuditLog databasecomponent,enternull. ISCORE_SCHEMA String IfyouwanttoarchivefromtheISCoreAuditLog databasecomponent,enterthefollowingfortheISCoreAudit Logdatabasecomponent: RDBMS Oracle SQLServer Entry Databaseuser Databasename
264
DB2
Schemaname
265
266
APPENDIX
267
Overview
YoumustcompletetheinstructionsinthisappendixifyoudidnotusethewebMethods InstallertocreatetheBrokerServerconfiguration.Youdidnotusetheinstallertocreate theBrokerServerconfigurationinthesecases: YouinstalledwebMethodsBrokeronaUNIXorLinuxsystemasanonrootuser.In thiscaseyoumustcompletealltasksinthischapter. YouinstalledonaUNIXorLinuxsystemasrootuseroryouinstalledonaWindows system,butyouwantedtospecifyadifferentstoragesizethanisavailablethrough theinstalleroryouwantedtocreateacombinedstoragesessionforconfigurationand runtimedata.InthiscaseyoumustcompletealltasksinthischapterexceptSetUp BrokerMonitoronUNIXorLinuxSystems(NonRootUser)onpage 270. Important! YoumusthaveinstalledwebMethodsBrokerusingthewebMethodsInstaller fortheinstructionsinthisappendixtowork.YoushouldneverinstallwebMethods Brokerbycopyingtheproductfilesfromonedirectorytoanother.
268
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
Saveandclosethefile.
269
Run as Daemon
1 2 LoginunderthenonrootuserIDyouusedtoinstallwebMethodsBroker. IfyouconfiguredBrokerServertocreatedatafilesonanNFSmountedpartition,go tothewebMethodsBrokerdirectoryandopentheS45broker65fileinatexteditor. TheS45broker65fileisthescriptthatstartsandstopsBrokerMonitor.
270
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 &
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
272
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.
[-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.
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
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
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.
[-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
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
278
Argument
Broker[@Broker_Server [:port]
[description text]
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
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