®       ®    PROGRESS                                   ®    OPENEDGE                                   ®    OpenEdge Appl...
© 2011 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.These materials and all Pr...
Contents   Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Contents                   AppServer broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Contents   4.   Configuring a Web Services Adapter Installation . . . . . . . . . . . . . . . . . . . . . . . .           ...
Contents                      Customizing the default administrator’s permissions and action settings. .                  ...
Contents                 Trimming running agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Contents                   Connecting programmatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Contents                   Configuring BrokerConnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Contents                        appServiceProtocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Contents   C.      Reference to Dynamic Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   ...
Contents     Figures     Figure 1:    AppServer run-time components . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Contents   Tables   Table 1:    AppServer run-time components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Contents     Table 49:   AppServer configuration entity names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Contents   Procedures   web.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Contents16         OpenEdge Application Server: Administration
Preface               This Preface contains the following sections:               •    Purpose               •    Audience...
PrefacePurpose           This manual provides a central point of reference for configuring and managing the           foll...
PrefaceOrganization               Part 1, Introduction               Chapter 1, “Overview of Server and Services Administr...
Preface          Part 4, WebSpeed Administration          Chapter 9, “Configuring WebSpeed in Windows”              Descri...
Preface               Part 7, Appendices               Appendix A, “Reference to OpenEdge Web Service Properties.”        ...
Preface          References to ABL data types          ABL provides built-in data types, built-in class data types, and us...
Preface                      Convention                                 Description                Fixed-width bold       ...
Preface          In this example, STREAM stream, UNLESS-HIDDEN, and NO-ERROR are optional:          Syntax           DISPL...
Preface               Long syntax descriptions split across lines               Some syntax descriptions are too long to f...
Preface          After displaying a message, OpenEdge proceeds in one of several ways:          •      Continues execution...
Preface               To use the pro command to obtain a message description by message number:               1.   Start t...
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
OE Application Server Administratoion
Upcoming SlideShare
Loading in...5
×

OE Application Server Administratoion

1,529

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,529
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "OE Application Server Administratoion"

  1. 1. ® ® PROGRESS ® OPENEDGE ® OpenEdge Application Server: ® Administration
  2. 2. © 2011 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.These materials and all Progress® software products are copyrighted and all rights are reserved by Progress Software Corporation. Theinformation in these materials is subject to change without notice, and Progress Software Corporation assumes no responsibility for any errorsthat may appear therein. The references in these materials to specific platforms supported are subject to change.Actional, Apama, Artix, Business Empowerment, Business Making Progress, DataDirect (and design), DataDirect Connect, DataDirectConnect64, DataDirect Technologies, DataDirect XML Converters, DataDirect XQuery, DataXtend, Dynamic Routing Architecture,EdgeXtend, Empowerment Center, Fathom, Fuse Mediation Router, Fuse Message Broker, Fuse Services Framework, IntelliStream, IONA,Making Software Work Together, Mindreef, ObjectStore, OpenEdge, Orbix, PeerDirect, POSSENET, Powered by Progress, PowerTier,Progress, Progress DataXtend, Progress Dynamics, Progress Business Empowerment, Progress Empowerment Center, ProgressEmpowerment Program, Progress OpenEdge, Progress Profiles, Progress Results, Progress Software Business Making Progress, ProgressSoftware Developers Network, Progress Sonic, ProVision, PS Select, Savvion, SequeLink, Shadow, SOAPscope, SOAPStation, Sonic, SonicESB, SonicMQ, Sonic Orchestration Server, SpeedScript, Stylus Studio, Technical Empowerment, WebSpeed, Xcalia (and design), and YourSoftware, Our Technology–Experience the Connection are registered trademarks of Progress Software Corporation or one of its affiliates orsubsidiaries in the U.S. and/or other countries. AccelEvent, Apama Dashboard Studio, Apama Event Manager, Apama Event Modeler,Apama Event Store, Apama Risk Firewall, AppsAlive, AppServer, ASPen, ASP-in-a-Box, BusinessEdge, Cache-Forward, CloudEdge,DataDirect Spy, DataDirect SupportLink, Fuse, FuseSource, Future Proof, GVAC, High Performance Integration, ObjectStore Inspector,ObjectStore Performance Expert, OpenAccess, Orbacus, Pantero, POSSE, ProDataSet, Progress Arcade, Progress CloudEdge, ProgressControl Tower, Progress ESP Event Manager, Progress ESP Event Modeler, Progress Event Engine, Progress RFID, Progress RPM, PSEPro, SectorAlliance, SeeThinkAct, Shadow z/Services, Shadow z/Direct, Shadow z/Events, Shadow z/Presentation, Shadow Studio,SmartBrowser, SmartComponent, SmartDataBrowser, SmartDataObjects, SmartDataView, SmartDialog, SmartFolder, SmartFrame,SmartObjects, SmartPanel, SmartQuery, SmartViewer, SmartWindow, Sonic Business Integration Suite, Sonic Process Manager, SonicCollaboration Server, Sonic Continuous Availability Architecture, Sonic Database Service, Sonic Workbench, Sonic XML Server, The BrainsBehind BAM, WebClient, and Who Makes Progress are trademarks or service marks of Progress Software Corporation and/or its subsidiariesor affiliates in the U.S. and other countries. Java is a registered trademark of Oracle and/or its affiliates. Any other marks contained hereinmay be trademarks of their respective owners. Third party acknowledgements — See the “Third party acknowledgements” section on page 27. December 2011Last updated with new content: Release 11.0.0 Product Code: 4496; R11.0.0For the latest documentation updates see OpenEdge Product Documentation on PSDN (http://communities.progress.com/pcom/docs/DOC-16074).
  3. 3. Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Part 1 Introduction 1. Overview of Server and Services Administration . . . . . . . . . . . . . . . . . . . . . . . . 41 AppServer for OpenEdge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 AppServer Internet Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 OpenEdge Web Services Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 WebSpeed Transaction Server and Messenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 OpenEdge Adapter for SonicMQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 OpenEdge Adapter for Sonic ESB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Configuring the OpenEdge runtime container for Sonic. . . . . . . . . . . . . . . 47 Automatic upgrade of OpenEdge containers . . . . . . . . . . . . . . . . . . . . . . . 48 Part 2 AppServer and Internet Adapter Administration 2. Configuring and Managing the AppServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Run-time components and operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Distribution of components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Fault-tolerant NameServers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Fault-tolerant AppServers and load balancing . . . . . . . . . . . . . . . . . . . . . 56 Operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 IPv6 networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 SSL-enabled AppServer operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 AppServer startup and shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 AppServer administration framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 AppServer clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 OpenEdge Management, OpenEdge Explorer, and the management utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 NameServers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63OpenEdge Application Server: Administration 3
  4. 4. Contents AppServer broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 AppServer agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 AppServer and NameServer properties file (ubroker.properties) . . . . . . . . 64 Text editor and configuration utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Preparing for AppServer administration . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Configuring AppServer components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 General steps for using OpenEdge Management or OpenEdge Explorer to configure an AppServer instance. . . . . . . . 66 Configuring an AppServer with OpenEdge Management or OpenEdge Explorer . . . . . . . . . . . . . . . . 67 Editing the properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Setting up the environment for AppServer execution . . . . . . . . . . . . . . . . . . . . . . . . 75 Environment variable settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Working directory settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 AppServer and NameServer log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 OpenEdge remote SmartDataObject support . . . . . . . . . . . . . . . . . . . . . . 76 Customizing the AppServer agent executable . . . . . . . . . . . . . . . . . . . . . . 76 Starting and managing an AppServer instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Requirements for starting an AppServer. . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Starting and managing an AppServer with OpenEdge Management or OpenEdge Explorer . . . . . . . . . . . . 77 Starting and managing an AppServer with the management utilities . . . . 79 Specifying the server pool parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Tuning for operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Managing AppServer agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Managing code pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Code-page settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Run-time conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Checking for failed client connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Failure detection and response. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Time out value tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 AppServer operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Configuring the AppServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Configuring clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 HTTP, AIA, and SSL configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Summary of management tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 3. Configuring and Managing the AppServer Internet Adapter . . . . . . . . . . . . . . . . 93 Installing the AppServer Internet Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 General AIA administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Security considerations for AIA administration . . . . . . . . . . . . . . . . . . . . . . 94 Installing and configuring Web servers and Java servlet engines . . . . . . . . . . . . . . 96 Enabling the Web server or JSE for SSL operation . . . . . . . . . . . . . . . . . . 98 Configuring AIA components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 General steps for using OpenEdge Management or OpenEdge Explorer to configure an AIA instance . . . . . . . . . . . . . 99 Configuring an AIA with OpenEdge Management or OpenEdge Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Configuring an AIA by editing the properties file. . . . . . . . . . . . . . . . . . . . . 102 Viewing AppServer Internet Adapter connection and configuration information . . . . 104 Connection status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Part 3 Web Services Adapter Administration4 OpenEdge Application Server: Administration
  5. 5. Contents 4. Configuring a Web Services Adapter Installation . . . . . . . . . . . . . . . . . . . . . . . . 109 Moving the WSA sample Web application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Configuring the JSE to recognize the WSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Tuning the JSE to handle large Web service messages . . . . . . . . . . . . . . . . . . . . . 112 Modifying the WSA’s default Web service security settings . . . . . . . . . . . . . . . . . . . 113 Enabling the WSA for HTTPS client connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Installing WSA on a DMZ server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 5. Managing the Web Services Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 WSA administration architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 WSA administration prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Web server and JSE configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Constructing URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 WSA as a JSE Web application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Defining a Web application for the WSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Creating one or more WSA instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Creating a WSA instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Creating multiple WSA instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Starting and testing a WSA instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Starting the WSA and its instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Testing a WSA instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Configuring and managing a WSA instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Properties of a WSA instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Modifying properties of a WSA instance . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Statistics of a WSA instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Configuring the WSA for Web services . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 6. Deploying and Managing OpenEdge Web Services. . . . . . . . . . . . . . . . . . . . . . . 133 Initializing a WSA instance’s default Web service properties . . . . . . . . . . . . . . . . . . 134 Security considerations for Web service administration . . . . . . . . . . . . . . . 135 Deploying a Web service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Versioning Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 After deploying Web services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Changing the Web service deployment directory . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Enabling a Web service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Administering a deployed Web service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Web service file management for deployed Web services . . . . . . . . . . . . . . . . . . . . 143 Options for providing the WSDL file to a client. . . . . . . . . . . . . . . . . . . . . . 143 Exporting and importing Web services. . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Monitoring and tuning Web services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Typical Web service administration scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Deploying a new version of your Web service . . . . . . . . . . . . . . . . . . . . . . 145 Changing Web service properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 7. Web Services Adapter Security Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . 147 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Role of the JSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Role of the WSA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 JSE and WSA security files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Security features available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Initial settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Alphabetical list of configuration instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Controlling access to Web services, WSDL, and WSA administration using one JSE security-constraint . . . . . . . 154 Controlling access to Web services, WSDL, and WSA administration using user-authorization role-names . . . . . 155OpenEdge Application Server: Administration 5
  6. 6. Contents Customizing the default administrator’s permissions and action settings. . 157 Customizing the PSCOper role’s permissions and action settings . . . . . . 158 Customizing WSA administration roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Disabling access to all Web services, to all WSDL, or to all WSA administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Disabling authentication for WSA administration . . . . . . . . . . . . . . . . . . . . 161 Disabling the deploying and undeploying of Web services . . . . . . . . . . . . 162 Disabling WSDL listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 Enabling authentication for Web services. . . . . . . . . . . . . . . . . . . . . . . . . . 163 Enabling authentication for WSDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Enabling multiple user roles to access Web services, WSDL, or WSA administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Enabling Web services per user and per application . . . . . . . . . . . . . . . . . 168 8. Using the WSA Management Utility (WSAMAN) . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Overview of the WSAMAN utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Functions for managing a WSA instance . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Functions for managing a Web service. . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Part 4 WebSpeed Administration 9. Configuring WebSpeed in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 WebSpeed configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 WebSpeed administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 The AdminService. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 OpenEdge Management or OpenEdge Explorer . . . . . . . . . . . . . . . . . . . . 185 Defining or configuring WebSpeed with OpenEdge Management or OpenEdge Explorer . . . . . . . . . . . . . . . . 185 WebSpeed command-line utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 NameServer command-line utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Setting up WebSpeed on the Web server machine . . . . . . . . . . . . . . . . . . . . . . . . . 191 Installing the Messenger executable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Configuring Netscape Web servers for NSAPI Messengers. . . . . . . . . . . . 192 Restarting the Netscape Web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Placing static files on the Web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Overview of the ubroker.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Starting the AdminService . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Setting up the WebSpeed environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Setting environment variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 Configuring WebSpeed components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Eliminating the NameServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 Understanding the NameServer’s load-balancing option . . . . . . . . . . . . . . 202 Starting the WebSpeed Transaction Server and NameServer . . . . . . . . . . . . . . . . . 204 Maintaining the WebSpeed Transaction Server and NameServer log files . . . . . . . 206 Configuring a WebSpeed Messenger-only installation . . . . . . . . . . . . . . . . . . . . . . . 207 Starting WebSpeed to test the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Testing your configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Using OpenEdge Management or OpenEdge Explorer to check status. . . 209 Using the query option to check status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Viewing the Messenger Administration page . . . . . . . . . . . . . . . . . . . . . . . 210 Running the status.p procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Managing the WebSpeed Transaction Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Dynamically starting additional agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2116 OpenEdge Application Server: Administration
  7. 7. Contents Trimming running agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Stopping the WebSpeed broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Accessing help on WTBMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Managing the WebSpeed Messenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 10. Configuring WebSpeed on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 WebSpeed configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 WebSpeed administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 The AdminServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 OpenEdge Management or OpenEdge Explorer . . . . . . . . . . . . . . . . . . . . 218 WebSpeed command-line utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 NameServer command-line utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Setting up WebSpeed on the Web server machine . . . . . . . . . . . . . . . . . . . . . . . . . 221 Installing the Messenger executable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Configuring the Netscape Web server for the NSAPI Messenger . . . . . . . 222 Restarting the Netscape Web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Placing static files on the Web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Overview of the ubroker.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 The ubroker.properties file structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Editing the ubroker.properties file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 Starting the AdminServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Setting up the WebSpeed environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Setting environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Configuring WebSpeed components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Load balancing with the NameServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Starting the WebSpeed Transaction Server and NameServer . . . . . . . . . . . . . . . . . 235 Maintaining the WebSpeed Transaction Server and NameServer log files . . . . . . . 237 Configuring a WebSpeed Messenger-only installation . . . . . . . . . . . . . . . . . . . . . . . 238 Starting WebSpeed to test the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Testing your configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Using OpenEdge Management or OpenEdge Explorer to check status . . 240 Using the query option to check status . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Viewing the Messenger Administration page . . . . . . . . . . . . . . . . . . . . . . . 241 Running the status.p procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Managing the WebSpeed Transaction Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Dynamically starting additional agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Trimming agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 Stopping the Transaction Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Accessing help on WTBMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Managing the WebSpeed Messenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 11. WebSpeed Dynamic Code-page Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Basic browser-agent interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 How dynamic code-page support works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Summary of code-page conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Configuring the agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Tasks for the WebSpeed developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Determining the MIME code-page name . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Storing the MIME code-page name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Accessing WEB-CONTEXT’s HTML-CHARSET attribute . . . . . . . . . . . . . 256 Converting code-page names between MIME and OpenEdge formats . . . 257 Additional notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 12. Connecting WebSpeed to a Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Connecting to an OpenEdge RDBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260OpenEdge Application Server: Administration 7
  8. 8. Contents Connecting programmatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Connecting to a local database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 Connecting to a remote database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 Connecting to a non-OpenEdge data source through a DataServer . . . . . . . . . . . . 263 DataServer and WebSpeed architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Setting up and running the DataServer. . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Creating an international Web site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Setting up Transaction Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Configuring agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Directing Web requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 13. WebSpeed Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Changing WebSpeed applications from development mode to production mode . . 272 Set the agent application mode to production. . . . . . . . . . . . . . . . . . . . . . . 272 Disable the WebSpeed Messenger Administration utility . . . . . . . . . . . . . . 274 Disabling WSMAdmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Establish the WebSpeed Messenger Administration Internet Protocol List (Optional) . . . . . . . . . . . . . . . . . 276 Check the status of the Debug mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Changing additional settings to minimize security risks . . . . . . . . . . . . . . . . . . . . . . 279 Port numbers and WebSpeed server names . . . . . . . . . . . . . . . . . . . . . . . 279 Minimize the PROPATH entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Techniques to minimize unauthorized access to WebSpeed Messengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Restrict your file upload directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 WebSpeed configuration considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Authenticating a password using SpeedScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Validating a password using SpeedScript. . . . . . . . . . . . . . . . . . . . . . . . . . 281 Securing data transmissions between WebSpeed client and server components . . 283 Secure HTTP Protocol (HTTPS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Secure Sockets Layer (SSL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 Maximizing WebSpeed compatibility with your firewall . . . . . . . . . . . . . . . . . . . . . . . 286 WebSpeed TCP port details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Important firewall considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Network Address Translation (NAT) and the WebSpeed distributed configuration. . . . . . . . . . . . . . . . . . . . . . . 287 Using the NameServer client port range value settings with a firewall . . . 290 14. Using Active Server Pages with WebSpeed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Setting up the WebSpeed ASP (WSASP) Messenger . . . . . . . . . . . . . . . . . . . . . . . 292 Accessing the WebSpeed ASP Web page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Enabling the WebSpeed ASP example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Part 5 Messaging and ESB Administration 15. OpenEdge Adapter for SonicMQ Administration . . . . . . . . . . . . . . . . . . . . . . . . . 297 Introducing the OpenEdge Adapter for SonicMQ . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Client connections to the OpenEdge Adapter for SonicMQ . . . . . . . . . . . . 298 Installing the OpenEdge Adapter for SonicMQ . . . . . . . . . . . . . . . . . . . . . 299 SSL-enabled BrokerConnect operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 HTTPS security for BrokerConnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Configuring and administering the OpenEdge Adapter for SonicMQ . . . . . . . . . . . . 301 Configuring ClientConnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Configuring ServerConnect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3018 OpenEdge Application Server: Administration
  9. 9. Contents Configuring BrokerConnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 Editing BrokerConnect attributes in ubroker.properties . . . . . . . . . . . . . . . 305 Configuring BrokerConnect from the command line . . . . . . . . . . . . . . . . . 307 Maximizing performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Performance comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Optimizing message size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 StreamMessage, MapMessage, and TextMessage . . . . . . . . . . . . . . . . . . 308 Remote and local calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Message reuse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Discardable messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Setting the CLASSPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Internationalization considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 16. Configuring and Managing the OpenEdge Adapter for Sonic ESB . . . . . . . . . . 313 Introduction to the OpenEdge Adapter for Sonic ESB . . . . . . . . . . . . . . . . . . . . . . . 314 Installation of the OpenEdge Adapter for Sonic ESB . . . . . . . . . . . . . . . . . . . . . . . . 315 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Confirming the Sonic Management Console is configured properly (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Using the OpenEdge Adapter for Sonic ESB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Editing OpenEdge service properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 Creating an OpenEdge service instance . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Editing an instance of an OpenEdge service . . . . . . . . . . . . . . . . . . . . . . . 328 Exposing a service as a standard Web service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Deploying a service instance in Sonic ESB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Security considerations for OpenEdge Adapter for Sonic ESB . . . . . . . . . . . . . . . . 333 Part 6 OpenEdge Resource Monitoring 17. Enabling Actional Monitoring of OpenEdge Resources . . . . . . . . . . . . . . . . . . . 337 Enabling Actional Interceptors for OpenEdge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 OpenEdge AppServer Interceptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 OpenEdge Adapter for Sonic ESB Interceptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341 OpenEdge Adapter for SonicMQ Interceptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 WebSpeed Interceptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 OpenEdge Web Services Adapter Interceptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 AppServer Internet Adapter (AIA) Interceptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345 OpenEdge Batch Client Interceptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Web Services Out Interceptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 OpenEdge Database Client Interceptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Part 7 Appendices A. Reference to OpenEdge Web Service Properties. . . . . . . . . . . . . . . . . . . . . . . . . 351 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Summary of properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Setting Service properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 Alphabetical reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 appServiceHost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 appServiceName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 appServicePort. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355OpenEdge Application Server: Administration 9
  10. 10. Contents appServiceProtocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 connectionLifetime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 idleSessionTimeout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 initialSessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 maxSessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 minIdleConnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 minSessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 noHostVerify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 noSessionReuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 nsClientMaxPort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 nsClientMinPort. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 nsClientPicklistExpiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 nsClientPicklistSize. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 nsClientPortRetry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 nsClientPortRetryInterval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 requestWaitTimeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 serviceFaultLevel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 serviceLoggingLevel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 staleO4GLObjectTimeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 waitIfBusy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 B. Command and Utility Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 ADAPTCONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 ADAPTMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 AIACONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 ASBMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 ASCONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 ESBOEGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 NSCONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 NSMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 PROADSV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 WSACONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 WSAMAN deploy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 WSAMAN disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 WSAMAN enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 WSAMAN export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 WSAMAN getdefaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 WSAMAN getprops (Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 WSAMAN getprops (WSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 WSAMAN getstats (Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 WSAMAN getstats (WSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 WSAMAN import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 WSAMAN list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 WSAMAN query (Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 WSAMAN query (WSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 WSAMAN resetdefaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 WSAMAN resetprops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 WSAMAN resetstats (Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 WSAMAN resetstats (WSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 WSAMAN setdefault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 WSAMAN setprops (Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 WSAMAN setprops (WSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 WSAMAN undeploy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 WSAMAN update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 WSCONFIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 WTBMAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41110 OpenEdge Application Server: Administration
  11. 11. Contents C. Reference to Dynamic Server Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Dynamic properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419OpenEdge Application Server: Administration 11
  12. 12. Contents Figures Figure 1: AppServer run-time components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Figure 2: AppServer administration framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Figure 3: AIA client connection information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Figure 4: AIA configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Figure 5: WSA administration architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Figure 6: Directory structure of the WSA as a JSE Web application . . . . . . . . . . . . . . 122 Figure 7: The local DataServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Figure 8: Remote DataServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Figure 9: WebSpeed configuration that supports an international Web site . . . . . . . . 266 Figure 10: The WebSpeed ASP Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Figure 11: OpenEdge Native Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Figure 12: OpenEdge Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31812 OpenEdge Application Server: Administration
  13. 13. Contents Tables Table 1: AppServer run-time components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Table 2: AppServer configuration entity names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Table 3: AppServer agent status indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Table 4: AppServer utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Table 5: Management tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Table 6: AIA configuration entity names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Table 7: Moving the installed sample Web application . . . . . . . . . . . . . . . . . . . . . . . . 110 Table 8: URL components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Table 9: Sample aliases for URL components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Table 10: web.xml file items to check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Table 11: ubroker.properties properties of a WSA instance . . . . . . . . . . . . . . . . . . . . . 129 Table 12: Statistics of a WSA instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Table 13: Setting the WSA instance’s default Web service properties . . . . . . . . . . . . . 134 Table 14: Web service order info version 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Table 15: Web service order info version 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Table 16: File created when a Web service is deployed . . . . . . . . . . . . . . . . . . . . . . . . 138 Table 17: Actions for administering a deployed and enabled Web service . . . . . . . . . . 142 Table 18: Statistics for a Web service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Table 19: Initial settings for JSE security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Table 20: Initial settings for WSA security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Table 21: Controlling Web service, WSDL, and administration access using JSE security constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Table 22: Controlling Web service, WSDL, and administration access using role names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Table 23: Requiring Web service user authorization for Web service, WSDL, and administration access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Table 24: Disabling access to Web services, WSDL, and administration . . . . . . . . . . . 160 Table 25: Setting the appAuth property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Table 26: Setting the wsdlAuth property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Table 27: Enabling multiple user roles for Web services, WSDL, and administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Table 28: Setting security constraints for multiple user roles on Web services, WSDL, and administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Table 29: Enabling Web services per user and per application . . . . . . . . . . . . . . . . . . . 169 Table 30: Sample Web service security constraints by application and role name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Table 31: Sample Web service user roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Table 32: WSA management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 Table 33: Web service management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Table 34: Windows NT WebSpeed Messengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Table 35: Netscape Web server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Table 36: Weight factors based on percentage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Table 37: Weight factors based on arbitrary sums . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 Table 38: UNIX WebSpeed Messengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Table 39: Netscape Web server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Table 40: NSAPI Messenger settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Table 41: Options for invoking the CGI Messenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Table 42: MIME and OpenEdge code-page equivalents . . . . . . . . . . . . . . . . . . . . . . . . 255 Table 43: Remote connection parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 Table 44: Agent application mode descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Table 45: Default port number to change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Table 46: Network communications requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Table 47: Registration Mode connection— OpenEdge Management or OpenEdge Explorer . . . . . . . . . . . . . . . . . . 288 Table 48: RegistrationMode Connection—ubroker.properties file . . . . . . . . . . . . . . . . . 289OpenEdge Application Server: Administration 13
  14. 14. Contents Table 49: AppServer configuration entity names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Table 50: BrokerConnect attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Table 51: OpenEdge AppServer Interceptor properties . . . . . . . . . . . . . . . . . . . . . . . . . 340 Table 52: OpenEdge Adapter for Sonic ESB Interceptor property . . . . . . . . . . . . . . . . . 341 Table 53: OpenEdge Adapter for SonicMQ Interceptor properties . . . . . . . . . . . . . . . . 342 Table 54: WebSpeed Adapter Interceptor properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 Table 55: OpenEdge Web Services Adapter Interceptor properties . . . . . . . . . . . . . . . 344 Table 56: AppServer Internet Adapter Interceptor properties . . . . . . . . . . . . . . . . . . . . 345 Table 57: OpenEdge Batch Client Interceptor startup parameters . . . . . . . . . . . . . . . . 346 Table 58: OpenEdge Database Client Interceptor properties . . . . . . . . . . . . . . . . . . . . 348 Table 59: Service properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Table 60: requestWaitTimeout property values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 Table 61: serviceLoggingLevel property values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Table 62: ADAPTMAN command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Table 63: Summary view output fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Table 64: Additional detail view output fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Table 65: ASBMAN command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 Table 66: NSCONFIG command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 Table 67: NSMAN command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Table 68: PROADSV command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Table 69: Setting the SOAP format for deployment using WSAMAN . . . . . . . . . . . . . . 386 Table 70: Setting the SOAP format for import using WSAMAN . . . . . . . . . . . . . . . . . . . 396 Table 71: Setting the SOAP format for update using WSAMAN . . . . . . . . . . . . . . . . . . 408 Table 72: WSCONFIG command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 Table 73: WTBMAN command examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 Table 74: allowRuntimeUpdates property values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41614 OpenEdge Application Server: Administration
  15. 15. Contents Procedures web.xml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Using SMQConnect on a client example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301OpenEdge Application Server: Administration 15
  16. 16. Contents16 OpenEdge Application Server: Administration
  17. 17. Preface This Preface contains the following sections: • Purpose • Audience • Organization • Using this manual • Typographical conventions • Examples of syntax descriptions • OpenEdge messages • Third party acknowledgementsOpenEdge Application Server: Administration 17
  18. 18. PrefacePurpose This manual provides a central point of reference for configuring and managing the following OpenEdge® Application Server products and OpenEdge adapters: • OpenEdge AppServer™ • AppServer Internet Adapter • OpenEdge Web Services Adapter • WebSpeed® Transaction Server • WebSpeed Messenger • OpenEdge Adapter for SonicMQ® • OpenEdge Adapter for Sonic ESB® All of these products and adapters share one or more of the following common features: • Comprise part of the OpenEdge Application Server product set • Rely on the Unified Broker framework for configuration and administration • Rely on the OpenEdge NameServer for fault-tolerance and availability • Play a unique role within OpenEdge application and integration services to help you develop and deploy applications as part of a Service Oriented Architecture (SOA)Audience This manual is for you if you need to configure and manage any of the OpenEdge Application Server products and OpenEdge adapters that it features. This manual is also for you if you need to deploy AppServer applications, WebSpeed applications, ABL applications that include JMS messaging using SonicMQ, or if you need to deploy OpenEdge Web services within the OpenEdge or Sonic ESB environment. For more information on these products and adapters, see OpenEdge Getting Started: Application and Integration Services. For most of these products and components it is helpful to be familiar with the Unified Broker framework. For more information on this framework, see OpenEdge Getting Started: Installation and Configuration.18 OpenEdge Application Server: Administration
  19. 19. PrefaceOrganization Part 1, Introduction Chapter 1, “Overview of Server and Services Administration” Introduces the OpenEdge server and adapter products who’s management is described in this manual, and provides references for more information on product architecture and usage. Part 2, AppServer and Internet Adapter Administration Chapter 2, “Configuring and Managing the AppServer” Describes the components, tools, and procedures for managing an AppServer installation. Chapter 3, “Configuring and Managing the AppServer Internet Adapter” Describes the components, tools, and procedures for managing an AppServer Internet Adapter installation. Part 3, Web Services Adapter Administration Chapter 4, “Configuring a Web Services Adapter Installation” Describes the basic features of Web Services Adapter (WSA) management and some post installation configuration tasks. Chapter 5, “Managing the Web Services Adapter” Describes how to create and manage a WSA Web application in the context of a Java servlet engine (JSE), how to create and manage WSA servlets in the context of a WSA Web application, and how to create and manage corresponding WSA instances in the context of the OpenEdge environment using the Unified Broker framework. Chapter 6, “Deploying and Managing OpenEdge Web Services” Describes how to deploy and manage OpenEdge Web services in the context of a single WSA instance, and how to export and import Web services between WSA instances. Chapter 7, “Web Services Adapter Security Configurations” Describes the components of WSA security and how to create and manage common WSA security configurations, listed for reference by alphabetical order. Chapter 8, “Using the WSA Management Utility (WSAMAN)” Introduces the WSAMAN command-line utility to perform many of the WSA and Web service management tasks that are otherwise performed using OpenEdge Management or OpenEdge Explorer.OpenEdge Application Server: Administration 19
  20. 20. Preface Part 4, WebSpeed Administration Chapter 9, “Configuring WebSpeed in Windows” Describes the basic requirements and procedures for configuring a WebSpeed installation in Windows. Chapter 10, “Configuring WebSpeed on UNIX” Describes the basic requirements and procedures for configuring a WebSpeed installation on UNIX. Chapter 11, “WebSpeed Dynamic Code-page Support” Describes how to manage dynamic code-page support for internationalizing WebSpeed installations. Chapter 12, “Connecting WebSpeed to a Data Source” Describes how to connect a WebSpeed application to an OpenEdge data source, such an OpenEdge RDBMS or DataServer. Chapter 13, “WebSpeed Security” Describes the components of WebSpeed security and how to use them to manage secure WebSpeed installations and applications. Chapter 14, “Using Active Server Pages with WebSpeed” Describes how to manage a WebSpeed installation to incorporate Microsoft Active Server Pages (ASP) in a WebSpeed application. Part 5, Messaging and ESB Administration Chapter 15, “OpenEdge Adapter for SonicMQ Administration” Describes the components, tools, and procedures for managing a SonicMQ Adapter installation to provide Java Message Service (JMS) messaging for an ABL client of a SonicMQ JMS. Chapter 16, “Configuring and Managing the OpenEdge Adapter for Sonic ESB” Describes the components, tools, and procedures for managing OpenEdge Web services as OpenEdge services installed and enabled through the Sonic ESB Adapter on the Sonic Enterprise Service Bus (Sonic ESB). Part 6, OpenEdge Resource Monitoring Chapter 17, “Enabling Actional Monitoring of OpenEdge Resources” Describes how to enable supported OpenEdge server, client, and service resources for monitoring by Progress® Actional®.20 OpenEdge Application Server: Administration
  21. 21. Preface Part 7, Appendices Appendix A, “Reference to OpenEdge Web Service Properties.” Describes how to access and provides an alphabetical reference to configuration and run-time properties used to manage both OpenEdge Web services in the OpenEdge environment and OpenEdge services in the Sonic ESB environment. Appendix B, “Command and Utility Reference” Describes the syntax for commands and utilities documented in this manual. If this manual provides the primary documentation for a command or utility, the syntax for that command or utility appears in this appendix. Appendix C, “Reference to Dynamic Server Properties” Lists the server properties that can be changed at runtime.Using this manual OpenEdge provides a special purpose programming language for building business applications. In the documentation, the formal name for this language is ABL (Advanced Business Language). With few exceptions, all keywords of the language appear in all UPPERCASE, using a font that is appropriate to the context. All other alphabetic language content appears in mixed case. For the latest documentation, see the OpenEdge Product Documentation Overview page on PSDN: http://communities.progress.com/pcom/docs/DOC-16074. References to ABL compiler and run-time features ABL is both a compiled and an interpreted language that executes in a run-time engine. The documentation refers to this run-time engine as the ABL Virtual Machine (AVM). When the documentation refers to ABL source code compilation, it specifies ABL or the compiler as the actor that manages compile-time features of the language. When the documentation refers to run-time behavior in an executing ABL program, it specifies the AVM as the actor that manages the specified run-time behavior in the program. For example, these sentences refer to the ABL compiler’s allowance for parameter passing and the AVM’s possible response to that parameter passing at run time: “ABL allows you to pass a dynamic temp-table handle as a static temp-table parameter of a method. However, if at run time the passed dynamic temp-table schema does not match the schema of the static temp-table parameter, the AVM raises an error.” The following sentence refers to run-time actions that the AVM can perform using a particular ABL feature: “The ABL socket object handle allows the AVM to connect with other ABL and non-ABL sessions using TCP/IP sockets.”OpenEdge Application Server: Administration 21
  22. 22. Preface References to ABL data types ABL provides built-in data types, built-in class data types, and user-defined class data types. References to built-in data types follow these rules: • Like most other keywords, references to specific built-in data types appear in all UPPERCASE, using a font that is appropriate to the context. No uppercase reference ever includes or implies any data type other than itself. • Wherever integer appears, this is a reference to the INTEGER or INT64 data type. • Wherever character appears, this is a reference to the CHARACTER, LONGCHAR , or CLOB data type. • Wherever decimal appears, this is a reference to the DECIMAL data type. • Wherever numeric appears, this is a reference to the INTEGER, INT64, or DECIMAL data type. References to built-in class data types appear in mixed case with initial caps, for example, Progress.Lang.Object. References to user-defined class data types appear in mixed case, as specified for a given application example.Typographical conventions This manual uses the following typographical conventions: Convention Description Bold Bold typeface indicates commands or characters the user types, provides emphasis, or the names of user interface elements. Italic Italic typeface indicates the title of a document, or signifies new terms. SMALL, BOLD Small, bold capital letters indicate OpenEdge key functions CAPITAL LETTERS and generic keyboard keys; for example, GET and CTRL. KEY1+KEY2 A plus sign between key names indicates a simultaneous key sequence: you press and hold down the first key while pressing the second key. For example, CTRL+X. KEY1 KEY2 A space between key names indicates a sequential key sequence: you press and release the first key, then press another key. For example, ESCAPE H. Syntax: Fixed width A fixed-width font is used in syntax statements, code examples, system output, and filenames. Fixed-width Fixed-width italics indicate variables in syntax statements. italics22 OpenEdge Application Server: Administration
  23. 23. Preface Convention Description Fixed-width bold Fixed-width bold indicates variables with special emphasis. UPPERCASE Uppercase words are ABL keywords. Although these are fixed width always shown in uppercase, you can type them in either uppercase or lowercase in a procedure. This icon (three arrows) introduces a multi-step procedure. This icon (one arrow) introduces a single-step procedure. Period (.) All statements except DO, FOR, FUNCTION, PROCEDURE, and or REPEAT end with a period. DO, FOR, FUNCTION, PROCEDURE, colon (:) and REPEAT statements can end with either a period or a colon. [] Large brackets indicate the items within them are optional. [] Small brackets are part of ABL. {} Large braces indicate the items within them are required. They are used to simplify complex syntax diagrams. {} Small braces are part of ABL. For example, a called external procedure must use braces when referencing arguments passed by a calling procedure. | A vertical bar indicates a choice. ... Ellipses indicate repetition: you can choose one or more of the preceding items.Examples of syntax descriptions In this example, ACCUM is a keyword, and aggregate and expression are variables: Syntax ACCUM aggregate expression FOR is one of the statements that can end with either a period or a colon, as in this example: FOR EACH Customer NO-LOCK: DISPLAY Customer.Name. END.OpenEdge Application Server: Administration 23
  24. 24. Preface In this example, STREAM stream, UNLESS-HIDDEN, and NO-ERROR are optional: Syntax DISPLAY [ STREAM stream ][ UNLESS-HIDDEN ] [ NO-ERROR ] In this example, the outer (small) brackets are part of the language, and the inner (large) brackets denote an optional item: Syntax INITIAL [ constant [ , constant ] ] A called external procedure must use braces when referencing compile-time arguments passed by a calling procedure, as shown in this example: Syntax { &argument-name } In this example, EACH, FIRST, and LAST are optional, but you can choose only one of them: Syntax PRESELECT [ EACH | FIRST | LAST ] record-phrase In this example, you must include two expressions, and optionally you can include more. Multiple expressions are separated by commas: Syntax MAXIMUM ( expression , expression [ , expression ] ... ) In this example, you must specify MESSAGE and at least one expression or SKIP [ (n) ], and any number of additional expression or SKIP [ ( n ) ] is allowed: Syntax MESSAGE { expression | SKIP [ ( n ) ] } ... In this example, you must specify {include-file, then optionally any number of argument or &argument-name = "argument-value", and then terminate with }: Syntax { include-file [ argument | &argument-name = "argument-value" ] ... }24 OpenEdge Application Server: Administration
  25. 25. Preface Long syntax descriptions split across lines Some syntax descriptions are too long to fit on one line. When syntax descriptions are split across multiple lines, groups of optional and groups of required items are kept together in the required order. In this example, WITH is followed by six optional items: Syntax WITH [ ACCUM max-length ][ expression DOWN ] [ CENTERED ] [ n COLUMNS ][ SIDE-LABELS ] [ STREAM-IO ] Complex syntax descriptions with both required and optional elements Some syntax descriptions are too complex to distinguish required and optional elements by bracketing only the optional elements. For such syntax, the descriptions include both braces (for required elements) and brackets (for optional elements). In this example, ASSIGN requires either one or more field entries or one record. Options available with field or record are grouped with braces and brackets: Syntax ASSIGN {[ FRAME frame ] { field [ = expression ] } [ WHEN expression ] } ... | { record [ EXCEPT field ... ] }OpenEdge messages OpenEdge displays several types of messages to inform you of routine and unusual occurrences: • Execution messages inform you of errors encountered while OpenEdge is running a procedure; for example, if OpenEdge cannot find a record with a specified index field value. • Compile messages inform you of errors found while OpenEdge is reading and analyzing a procedure before running it; for example, if a procedure references a table name that is not defined in the database. • Startup messages inform you of unusual conditions detected while OpenEdge is getting ready to execute; for example, if you entered an invalid startup parameter.OpenEdge Application Server: Administration 25
  26. 26. Preface After displaying a message, OpenEdge proceeds in one of several ways: • Continues execution, subject to the error-processing actions that you specify or that are assumed as part of the procedure. This is the most common action taken after execution messages. • Returns to the Procedure Editor, so you can correct an error in a procedure. This is the usual action taken after compiler messages. • Halts processing of a procedure and returns immediately to the Procedure Editor. This does not happen often. • Terminates the current session. OpenEdge messages end with a message number in parentheses. In this example, the message number is 200: ** Unknown table name table. (200) If you encounter an error that terminates OpenEdge, note the message number before restarting. Obtaining more information about OpenEdge messages In Windows platforms, use OpenEdge online help to obtain more information about OpenEdge messages. Many OpenEdge tools include the following Help menu options to provide information about messages: • Choose Help→ Recent Messages to display detailed descriptions of the most recent OpenEdge message and all other messages returned in the current session. • Choose Help→ Messages and then type the message number to display a description of a specific OpenEdge message. • In the Procedure Editor, press the HELP key or F1. On UNIX platforms, use the OpenEdge pro command to start a single-user mode character OpenEdge client session and view a brief description of a message by providing its number.26 OpenEdge Application Server: Administration
  27. 27. Preface To use the pro command to obtain a message description by message number: 1. Start the Procedure Editor: OpenEdge-install-dir/bin/pro 2. Press F3 to access the menu bar, then choose Help→ Messages. 3. Type the message number and press ENTER. Details about that message number appear. 4. Press F4 to close the message, press F3 to access the Procedure Editor menu, and choose File→ Exit.Third party acknowledgements Progress OpenEdge v11.0 may incorporate ANT v1.5.4. Such technology is subject to the following terms and conditions: The Apache Software License, Version 1.1, applies to all versions of up to ant 1.6.0 included. The Apache Software License, Version 1.1 - Copyright (C) 2000-2003 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names "Ant" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED ``AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For moreOpenEdge Application Server: Administration 27

×