DONE-10: Adminserver Survival Tips Brian Bowman Product Manager, Data Management Group

2© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Agenda n Introduction n Importance of the Adminserver n Adminserver Architecture n How to Make Better Use if it n Summary

3© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Ken Wilner, VP of Technology PSC February, 2005 “I don’t know why you want to talk about it – it just runs!”

4© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Introduction n Introduced in Version 9.0A n Provides a common infrastructure and interface for Server management n First Plugins: AppServer™, WebSpeed®, NameServer, Database n The complete configuration point for the deployment environment

5© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips What is the AdminServer? n A consistent interface for managing Progress products n Administrative access to Progress products installed on your network n Remote configuration and management capabilities An administrative framework to provide…

6© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Agenda n Introduction n Importance of the Adminserver n Adminserver Architecture n How to Make Better Use if it n Summary

7© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips What does it do? It’s not really the engine…

8© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips What does the AdminServer do today? n Fathom™ Management n AppServer Brokers and Servers n WebSpeed Transaction Servers & Agents n NameServer n Databases n DataServers n WebSpeed Messenger n Sonic 4GL Adapter n Web Services Adapter It configures and manages:

9© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips What does it do? It’s more like the ignition system of your application

10© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Agenda n Introduction n Importance of the Adminserver n Adminserver Architecture n How to Make Better Use if it n Summary

11© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips AdminServer The Basic Picture Request to start WebSpeed WebSpeed is Started Admin Server Something Goes In… Something Comes Out…

12© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Adminserver Tip “Never start the adminserver as root” n Opens you up to security issues n Causes all other processes to start as root

13© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips AdminServer An Advanced Picture Admin Server Progress Explorer Browser Plugin WebSpeed Broker WS Server Plugin AppServer Broker AS DB Server Plugin Database Broker Fathom Management 4GL Java.Net

14© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips How the AdminServer Works n An extensible framework for hosting plugins –Loads plugins and accepts management requests –Local and remote request from Progress Explorer and the command line interface n Manages Client Connections n Plugins provide management functions for a particular product –Database, WebSpeed, AppServer, etc. –Some plugins are adapters (WSA, AIA, WS messenger) n The real work is in the plugins Adminserver Plug-ins are:

15© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Progress Admin Server (20931) conmgr.properties AdminServerPlugins.dat /.properties Progress Explorer RMI DB Broker (7835) TCP ubroker.properties RMI AS Broker (3050) WS Broker (3055) Name Server (5162) RMI Client UDP (1) TCP (2) UDP TCP (2) How the Adminserver Communicates Fathom Management (6835) TCP

16© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Adminserver Tip “Document and monitor all of the ports (#’s & types) that you use for the adminserver.”

17© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips How the AdminServer Works n AdminServerPlugins.[dat|properties] file –Text file that contains a list of server plugins to start –Only those products that are licensed on that machine will start –Stored in $DLC directory – V9 –Stored in $DLC/properties directory – R10 –Treat as read-only; do not modify Plug-ins

18© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips How the AdminServer Works n Ubroker.properties file –Text file that contains configuration information for all OpenEdge™ instances –Only those instances that are configured will start –Stored in $DLC/properties directory –Modifiable via PE or any editor –If modified by editor – use validation tools (*config) Configuration Files

19© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips How the AdminServer Works n connmgr.properties file –Text file that contains configuration information for all OpenEdge databases –Only those databases that are configured for autostart will start when adminserver starts –Stored in $DLC/properties directory –Modifiable via PE or any editor –If modified by editor – use validation tools (*config) Configuration Files

20© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Adminserver Tip “Back up your configuration files.”

21© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Why should I worry about it? You know it’s there (or hope it is)… but don’t ever want to use it…

22© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Agenda n Introduction n Importance of the Adminserver n Adminserver Architecture n How to Make Better Use if it n Summary

23© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Sometimes you want something that can go anywhere…

24© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips But parks like a dream…

25© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Then why not have the best of both?

26© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips How can I make better use of it? n Load Balancing n High Availability n Debugging n Security n Fathom Management

27© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Load Balancing Client(s) Machine A Inventory 70% Payroll (C) NameServer Inventory (A and B) Location transparency Load balancing Machine C Payroll Machine B Inventory 30%

28© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Roy Ellis, Principle Engineer PSC May, 2005 “With the adminserver you can do remote configuration and management from almost anywhere!”

29© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Web Server Name Server (Load balancing) CHUI GUI Web Client Web Browser Sonic ESB Application Server (Site 1) Application Server (Site 2) Reporting Backup (Site 2) Name Server (Load balancing) Production (Site 1) User TierApplication TierData Tier HTTP Direct Connect TCP/IP Messaging Fathom Replication.Net SQL High Availability Application

30© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Adminserver Tip “Never shut down the adminserver unless you are upgrading or installing.” n There is typically no reason to shut it down n Removes the ability for remote access to the application

31© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Debugging Logging Levels n Can set how much is written to log files –Level 1: Errors and Information –Level 2: Terse (default) –Level 3: Verbose n Security Logging –Log Specific user authentication / authorization –Default: log both success and failed operations –Can change so only failed logins are recorded JVMARGS=$JVMARGS –DLogLevelSecurity = 2

32© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Adminserver Tip “Raise the logging level on your adminserver and manage the extra volume.” n This gives you more insight into what is happening after the fact.

33© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Many Types of Security…

34© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Security Options n User-group authorization – 9.1D –Format: -admingroup group[:group…] –Minimum 1 valid group name Watch out for specifying group authorization without any users! n User authenticated to OS’s security system n Sub-process startup can be authenticated as well

35© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Adminserver Tip “Start each broker process under a different user name.” n This gives you the ability to identify which processes are doing what

36© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Agenda n Introduction n Importance of the Adminserver n Adminserver Architecture n How to Make Better Use if it n Summary

37© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Benefits of Understanding the Adminserver FeatureBenefit Single configuration location for OpenEdge Adding a new server or re- configuring an existing server is easy. Single process to start & stop complete application Confidence that adding a new server will be correct and start & stop. Remote Configuration You can manage multiple remote systems from one place with one tool.

38© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Summary n Now you have a better understanding of what it does for you n Now you understand why it exists n Make use of the features it offers

39© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Questions? Brian Bowman

40© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips Thank you for your time!

41© 2005 Progress Software Corporation DONE-10: Adminserver Survival Tips