client server technologies

Client Server TechnologiesPresented by:Gord Davey

Presentation OverviewApplication Server EnhancementsJavX EnhancementsClient/Server Efficient CodingAutoUpdater

Application Server EnhancementsNT Service SupportEnhanced LoggingEnhanced Start-In and INI Improved User SwitchingTerminate/Break and Log Clearing Commands are now sent to the ServerFatal Error Log pvx.appserv.logSpeed Increase 6% to 10%and more

Application Server EnhancementsNT Service SupportSimple Install/Un-Install/Start/Stop

Application Server EnhancementsLogging EnhancementsClear All and Log RotationServer PID

Application Server EnhancementsStart-In and INI for spawned tasks enhanced

Application Server EnhancementsImproved User SwitchingUses DEF UID if available rather than suTerminate/Break and Log Clearing Commands are now sent to the ServerConfig may run as a different user from daemonFatal Error Log pvx.appserv.logTo /tmp (*nix) or current directory (windows)Miscellaneous:New Menu Item: Shutdown All ServersServer PID for each daemon displayedSpeed Increase 6% to 10%

Application Server EnhancementsImproved User SwitchingUses DEF UID if available rather than suTerminate/Break and Logging Clearing Commands are now sent to the ServerConfig may run as a different user from daemonFatal Error Log pvx.appserv.logTo /tmp (*nix) or current directory (windows)Miscellaneous:New Menu Item: Shutdown All ServersServer PID for each daemon displayedSpeed Increase 6% to 10%

JavX EnhancementsJavX V2.5 now comes in 3 editionsJavX SE Swing EditionClosest to ProvideX in terms of GUI ControlsIncludes: Grid, Formatted List Boxes, Tree View, List View, Report View, Full Button characteristicsJavX AE AWT EditionLightweight GUI InterfaceIncludes: list box, buttons, check boxes, radio buttons, etc., all in simplified formExcludes: Grid, Formatted List Boxes, Tree View, List View, Report View, Full Button characteristicsJavX LE Lite EditionHas no character mode or graphical mode user interface. Direct to Java Object Interface

JavX EnhancementsJavX SE Swing EditionFull range of GUI controls supported with virtually all optionsRequires Java 2 SE (Standard Edition) Runtime (version 1.42) or higherEquivalent to prior releases of JavXMost feature rich

JavX EnhancementsJavX AE AWT EditionLimited range of simplified GUI controls availableRequires Java 2 ME CDC PP (Micro Edition, Constrained Device Context, Personal Profile) Runtime (any version) or higherIntended for PDAs (Pocket PC, Windows CE Devices), Embedded Devices and Desktop PCs

JavX EnhancementsJavX LE Lite EditionHas no character or graphical user interface at allRequires Java 2 ME CDC FP (Micro Edition, Constrained Device Context, Foundation Profile) Runtime (any version) or higherIntended for Java devices that do not have a user interface (routers, gateways, printers)

JavX EnhancementsDirect to Java Object InterfaceUses ProvideX DEF OBJECT syntaxDEF OBJECT X,@(x,y,w,h)=[wdx]javax.swing.JSliderDEF OBJECT X,[wdx]JDBCDriverInstantiate and utilize Java Classes directly, manipulating properties, executing methods, listening for events and more.Allows for the use of the Java BeanShell class, which can take Java source code directly.

Client/Server Efficient CodingMinimize Data

Send only enough data to get the job doneAnalyze your screensPerhaps there is a different approach that might require less object loading (list box, drop box, grid)Make use of special features to minimize loading:Load-on-Demand feature for listboxesQuery object, which reads records one page at a time

Client/Server Efficient CodingMinimize Data

Be careful of CALLA CALL [WDX]SomeProg,X$ will send the current contents of X$ to the client and will receive it back.If X$ was 20,000 Xs on the way up, and it was not modified on the client, then 20,000 Xs will come backIn these cases, get the program on the WindX side to clear the unneeded variables before the CALL completes

Client/Server Efficient CodingMinimize Send/Receive Occurrences

Items such as FID( ), FIB( ), FIN( ), OBJ( ), MSE( ), etc., must be retrieved from the workstationAvoid code that asks for these types of items repeatedlyConsider:for x=1 to 10000; y=fin(chan,numrec);a*=5; next; y=fin(chan,numrec)y=fin(chan,numrec);for x=1 to 10000;a*=5; next; y=fin(chan,numrec)10001 packet requests versus 2 packet requests


Any variable or function that requires data from WindX will cause the system to pause until it has an answerFor example, when using TXW( ) and TXH( ) to determine the sizes of text at various point sizes:It is better to put the code in a CALL and make one CALL across a WindX connection, than it is to repeatedly call TXW( ) and TXH( )Note: This is true for any function, not just for TXW( ) and TXH( )


When dealing with Objects and their Dynamic Properties, try to use the newer _PropList$ and _PropValues$ to retrieve or set multiple properties at onceWhen dealing with properties, try to organize your code so that sets and gets are grouped togetherDont do a property get, then a set, then a get, then a set, then a get

AutoUpdaterFeatures Server-Side SetupServer-Side Directory StructureServer-Side Configuration

AutoUpdaterFeatures

Automated software updating for Client/Server environmentsWindX Stand-Alone (Version 4.11 and higher)WindX Plug-in (Version 4.11 and higher)ProvideX with WindX (Version 5.10 and higher)Repository based systemSoftware to be pushed resides on the ServerNo client software installation requiredCustomizable to include your software requirementsRequires V7 ProvideX on Server, with a V7 activation keyWill perform Upgrades, Downgrades or RepairsIntelligent restart capability if session is severed

AutoUpdaterFeatures

Assigns Show updates of the Add or Remove Programs dialogue in WindowsConfigurable User InteractionAutomated COM and DLL registrationWill detect and shutdown other client sessions currently invoked on Workstation that are using same executableNo client reboot required after an upgrade, downgrade, or repairWindows 9X, NT, 2000, XP, Server 2003 compliantHas logging capability

AutoUpdaterServer-Side Setup

Download the required .zip (Windows) or .taz (UNIX or Linux) file for the version you wish to auto upgrade or downgrade from our Web Site www.pvx.com or ftp.pvx.comUnzip/untar the file into the Servers /lib/_repository directoryTurn on the AutoUpdater in its configuration file

...thats it - youre done!

AutoUpdaterServer-Side Directory Structure

When installing ProvideX Version 7, a new directory will be created: \lib\_updater\cinfo (software that is moved to clients machine to obtain all the clients information; i.e., version, startup information, libraries, etc.)windx.upd (main control program for WindX update)autoupdate.pvc (AutoUpdate engine that performs all required functions for the product update; i.e., windx.upd)Contains the autoupdate.conf (default configuration setup file)

AutoUpdaterServer-Side Directory Structure

Once you download and unzip/untar the required repository file, the _repository directory will contain Software to be deployed to the client workstations \lib\_repository\\ manifest.conf (holds information about the product version on each file and deployment type; i.e., WindX Standalone, Plug-in, or ProvideX)

AutoUpdaterServer-Side Configuration

Text based configuration fileCopy the autoupdate.conf , default config file to autoupdatecustom.conf to customize your configurationConfiguration file contains identification tags [Defaults] All settings defined under this tag are the defaultsYou may add user-specific settings by adding tags for each user[] i.e. [10.100.10.10][+:+] i.e. [10.100.10.10:MyBox][] i.e. [Tom]SettingsBroken up into 3 partsDefaults, Debug, and ProductsSettings may be placed in both Defaults or Product sectionsSpecific order: Defaults, Products, User-Defined


AllowUpgrade=Y or N (if null then default is N)Indicates whether an upgrade should take place if clients workstation version ID is lower than version in autoupdate.conf

AllowDownGrade=Y or N (if null then default is N)Indicates whether a downgrade should take place if clients workstation version is higher than version in autoupdate.conf


AllowCompare=Y or N (if null then default is N)Indicates whether repair should take place if clients workstation version is same as version in autoupdate.conf

CompareFrequency=D or W or M or 2TuesdayD = Once DailyW = Once WeeklyM = Once Monthly2Tuesday = Every Second Tuesday of the monthFormat is Number+Day (Fri or Friday)


Interactive=Silent or Prompted (if not set, the default is Prompted)


CurrentVersion=7.00.0000This is the value that all client sessions will be compared against to identify whether an update is to proceed

RepositoryPrefix=pvxWindx.upd will take this value + CurrentVersion and look in this directory within the repository directory to get manifest information on what files to move i.e.,CurrentVersion = 7.00.0000RepositoryPrefix=PVXDirectory to look in will be \lib\_repository\pvx.7.00.0000


LogLevel=0 -> 9 (if null then default is 0)

KillProcessMsg=Y or N (if null then default is N)Indicates if the user will receive a message box advising them that a session running with the same executable is going to be terminated


AllowClientInitiation=Y or N (if null then default is N)Displays dialogue advising user on what will happen


AllowClientCancellation=Y or N (if null then default is N)Indicates if all the user dialogues contain a Close or Cancel buttonLookandFeel= 4,3,22 (Windows 3.1 style)3 (Windows 95 style)4 (XP style)

AutoUpdater[DEFAULTS]INTERACTIVE= SILENTALLOWUPGRADE=YALLOWDOWNGRADE=YALLOWCOMPARE=YCOMPAREFREQUENCY=MLOOKANDFEEL=4[DEBUG]LOGLEVEL=0[PRODUCTS]1=ProvideX2=WindX Standalone3=WindX Plugin4=JavX[PRODUCT:ProvideX]IDENTIFIER=PVXCURRENTVERSION=7.00.0000REPOSITORYPREFIX=pvx[PRODUCT:WindX Standalone]IDENTIFIER=WXSCURRENTVERSION=7.00.0000REPOSITORYPREFIX=pvx[PRODUCT:WindX Plugin]IDENTIFIER=WXPCURRENTVERSION=7.00.0000REPOSITORYPREFIX=pvx[10.100.1.1]ALLOWUPGRADE=NExample autoupdate.conf file

AutoUpdater# Manifest.conf - For ProvideX and WindX Version 7.00.0000# issued: July 2005

pvxcom.exe ;Ver=5.10.2000;ASCII;ID=WXS,PVX;Reg=9;RegInstall=pvxcom.exe /unregserver;RegUnInstall= /unregserver Pvxwin32.exe ;Ver=7.00.0000 # This is a remarkExample manifest.conf file

THANK YOU!End of Presentation

THANK YOU!End of Presentation

Copyright 2005 Best Software Canada Ltd. All rights reserved. No part of this publication may be reproduced, or transmitted in any form or by any means, electronic, mechanical, photocopied, recorded or other, without prior written consent of Best Software Canada Ltd.

NT Service Support Requires ProvideX V7 with a V7 activation key.Each server daemon will be run as a separate service. This can cause difficulties with ProvideX User Count licensing. If you have more than one daemon running, and they are set to interact with the desktop, then they will share the total user license count. However, if they do not interact with the desktop, then they will not be able to share the user count. Example: Server daemons A and B, and 5 workstations, 1,2,3,4 and 5.If all 5 connect to Daemon A, you will use 6 user slots - one for the daemon and one for each of the WindX workstations 1 through 5.If all 5 of those workstations also connect to server B, and each runs one session, then you will use another 6 user slots - one for the B server daemon and one for each of the 5 workstations. This means you will have used 12 user slots in total.However, if you set both daemons A and B to interact with the desktop, and each of the 5 workstations connect one session to both server A and server B, then you will only use a total of 6 user slots, rather than a total of 12.

Application Server Enhancements

NT Service Support (continued) Name: A unique service name. This is generated automatically.Display Name and Description: These items are what users will see displayed in the NT Services ListingStart Type: May be set to Automatic, Manual or DisabledDomain, User Name and Password: If you wish to run the service as a user other than Local System then you may set those properties here.Interact With Desktop: This is only valid when running as the Local System account (not when running as another user)Install / Un-Install: Adds or Removes the service from Windows.Start / Stop: To Start or Stop the service, use the Start/Stop buttons on the Server Tab. If the service is not installed, then selecting Start will start it on the Desktop.Note: Changing any NT Service properties when the App Server daemon is running will require the daemon to be stopped, un-installed, re-installed and re-started.Logging EnhancementsLogging commands are now sent to the server daemon. Clear, Clear All and Rotate will all be processed by the daemon when it is running, or by the configuration screen if it is not running. This allows logs to be cleared, etc., while the daemon is running. Previously they could not be cleared unless the daemon was stopped.Clear All (new button) Clears all the current logs that exist for the currently-named server. It will not clear any rotated logs.Rotate (new button) This will cause the logs to be renamed with the following format: file.log becomes YYYYMMDD.HHMMSS.file.log within the currently-named server directory (*appserv/servername/*.log). If the server is running, it will complete and close the existing logs, rotate them, initialize/re-create the current log files and re-open any required logs to provide the requested logging.

Enhanced INI and Start-InINI and Start-In are used for spawned tasks, and not just for starting the application server daemon.The order for determining the INI and Start-In Directory for spawned tasks has been enhanced. Previously, the Servers INI and the Start-In Directory were used only if the application server daemon was started from within the Configuration Screen. If the daemon was started outside of the configuration, these two items would not be used.

Enhanced INI and Start-In (continued)New INI BehaviorIf starting the application server daemon from within the configuration screen, then the old rules apply - the server daemon will be started with this INI. If the server daemon is started outside of the configuration screen, then the INI given on the command line is used, and the INI specified in the server tab is ignored. Any sessions spawned by the daemon will now use the following, in order:#1 - INI from the *client icon, if given, and if the application named on the icon allows for INI overrides (see the Apps Tab, Detail of App).#2 INI from the application detail screen, if given (See Apps Tab, Detail of App).#3 (New) The INI specified on the Server tab.#4 The INI used by the server daemon, either from the daemons command line (if started externally) or the Servers INI if given on the Server Tab.Note: INIs are only valid in a Windows environment.

New Start-In Directory BehaviorFor starting the server daemon there is no change. The Start-In Directory on the server tab is valid only if the configuration screen is used to start the daemon. If the daemon is started externally, then the Start-In Directory will be set based on that external launch. The new behavior affects the sessions which are spawned from within the daemon. The rules are applied in the following order:#1 Start-In from the *client icon, if given, and if the application named on the icon allows for Start-In overrides (see the Apps Tab, Detail of App).#2 Start-In from the application detail screen, if given (See Apps Tab, Detail of App).#3 (New) The Start-In Directory specified on the Server tab.#4 The Start-In used by the server daemon, either from the daemons command line (if started externally) or the Start-In Directory if given on the Server Tab.

MiscellaneousImproved User SwitchingValid for UNIX and Linux platforms only. Wherever the ProvideX DEF UID command is available, it will be used to allow newly-spawned sessions to be started as a particular user. If the DEF UID command fails for any reason, then an su will be attempted. By using DEF UID it will eliminate the su events from the typical su log file for the OS in question. For DEF UID or su to be effective, the server daemon must be running as root. When not running as root, the behavior has been enhanced so that the spawned applications will not attempt a DEF UID or an su, and will simply launch as whatever user the server daemon is currently running as.Commands Now Sent to ServerThe Terminate and Interrupt commands from the Sessions tab, as well as the Clear, Clear All and Rotate commands from the Logging tab are all now sent to the server daemon for processing, provided the server daemon is currently running. The net effect of this is that these commands will successfully execute because they are now executed by the same user that the daemon is running as. If the daemon is running as an NT Service these commands will occur within the context of the NT Service. This also allows the Configuration screen to be run as a different user to the server daemon (provided the daemon was started outside of the configuration. Miscellaneous (continued)Fatal Error Log (New)An additional log has been created where, if there is a fatal error or warning that needs to be given during the start-up of a server daemon, those errors and warnings will be posted to the fatal error log. This log is named pvx.appserv.log and will be placed in the /tmp directory for UNIX or Linux, or in the app servers current Start-In directory under MS Windows. This will help diagnosis should the server daemon not start or fail prior to opening any of its normal configured log files. New warnings are now written to this file when: A) the server daemon is not run as root B) the server daemon is not using a UMASK of 0.Shutdown All Servers (New)A new command to shutdown all currently-running application server daemons has been added to the File drop down menu.Server PIDThe Process ID of the server daemon is now shown in the Configurations status box for the currently selected application server.Speed ImprovementA tightening of the code in the application server daemon has basically reduced line numbers and built more compound statements. Also, the switching to large arrays for buffer management has shown an overall speed increase within the server daemon, averaging 6% to 10% faster execution.Due to the use of very large dimensions arrays, and the use of DEF UID, the minimum version of ProvideX that this edition of the Application Server will run on is now V6.10. A ProvideX Version 7 activation key is required to use the NT Service abilities of the Application Server.JavX EnhancementsJavX SE runs with:Java 2 SE (Standard Edition) Runtime, version 1.42 or higherJava 2 EE (Enterprise Edition) Runtime, version 1.42 or higher

JavX EnhancementsJavX AE runs with:Java 2 ME CDC PP (Micro Edition, Constrained Device, Personal Profile) Device with limited user interface (PDA)Java 2 SE (Standard Edition) Runtime, version 1.42 or higherJava 2 EE (Enterprise Edition) Runtime, version 1.42 or higher

JavX Enhancements JavX LE runs with:Java 2 ME CDC FP (Micro Edition, Constrained Device, Foundation Profile) Device with no user interface (gateway, router)Java 2 ME CDC PBP (Micro Edition, Constrained Device, Personal Basis Profile) Device with extremely limited user interface (printer, automotive telemetrics)Java 2 ME CDC PP (Micro Edition, Constrained Device, Personal Profile) Device with limited user interface (PDA)Java 2 SE (Standard Edition) Runtime, version 1.42 or higherJava 2 EE (Enterprise Edition) Runtime, version 1.42 or higher

JavX EnhancementsDirect to Java Object Interface

Note: Using the @(x,y,w,h) will embed the Java component into the ProvideX window.

0010 ! 0012 ! This program creates an AWT FRAME and Button0014 ! and places it on a Frame. This demonstrates the flexibility of the OCX0015 ! interface in JavX0020 ! 0030 def object AWTWINDOW,"[wdx]java.awt.Frame"0040 def object AWTBUTTON,"[wdx]java.awt.Button"0050 def object EXITBUTTON,"[wdx]java.awt.Button"0080 def object AWTMULTI_LINE,"[wdx]java.awt.TextArea"0090 !

Direct to Java Object Interface (Continued)

0100 ! PRINT awtWindow'*0110 AWTWINDOW'SETSIZE(260,320)0120 AWTWINDOW'SHOW()0130 AWTBUTTON'SETBOUNDS(30,246,80,40)0140 EXITBUTTON'SETBOUNDS(140,246,80,40)0150 AWTBUTTON'SETLABEL("Hit Me!")0160 EXITBUTTON'SETLABEL("Exit")0170 AWTMULTI_LINE'SETBOUNDS(25,45,200,200)0180 ! add events0190 execute "[wdx]on event java.awt.event.ActionListener from "+str(AWTBUTTON)+" preinput 10"0191 execute "[wdx]on event java.awt.event.ActionListener from "+str(EXITBUTTON)+" preinput 20"0200 ! 0210 AWTWINDOW'SETLAYOUT(*-1)0220 AWTWINDOW'ADD(*AWTBUTTON)0230 AWTWINDOW'ADD(*EXITBUTTON)0240 ! 0250 EXITBUTTON'LINE=17.50260 EXITBUTTON'COL=180270 EXITBUTTON'LINES=30280 EXITBUTTON'COLS=90290 ! 0300 AWTWINDOW'ADD(*AWTMULTI_LINE)0310 AWTWINDOW'VALIDATE()0320 AWTWINDOW'REPAINT()0330 obtain A$0340 EVT=ctl0350 if EVT=10 then {0360 ! 0370 LOADTEXT$="Ctl :"+str(EVT)0380 CURTEXT$=AWTMULTI_LINE'GETTEXT$()0390 AWTMULTI_LINE'SETTEXT(CURTEXT$+" "+LOADTEXT$)0400 goto 03300410 }0411 if EVT=20 then {0412 goto CLEAN_UP0420 } else {0421 goto 03300430 }0440 ! Direct to Java Object Interface (Continued)

0460 ! clean up0470 CLEAN_UP:0480 AWTWINDOW'REMOVE(*AWTBUTTON)0490 AWTWINDOW'REMOVE(*AWTMULTI_LINE)0500 AWTWINDOW'HIDE()0510 AWTWINDOW'DISPOSE()0520 delete object AWTWINDOW0530 delete object AWTBUTTON0540 delete object AWTMULTI_LINE0550 end

How the autoupdate.conf file is readThe entire file is read into a *memory file:All default information All Debug informationProduct listProduct information pertinent to the software the Client is connecting withAny user-defined information

In this example all updates will be taken from the directory \lib\_Repository\pvx.7.00.0000All users will be upgraded except 10.100.1.1

Auto Updater

Example autoupdate.conf File (continued)

[DEFAULTS]INTERACTIVE= SILENTALLOWUPGRADE=YALLOWDOWNGRADE=YALLOWCOMPARE=YCOMPAREFREQUENCY=MLOOKANDFEEL=4[DEBUG]LOGLEVEL=0[PRODUCTS]1=ProvideX2=WindX Standalone3=WindX Plugin4=JavX[PRODUCT:ProvideX]IDENTIFIER=PVXCURRENTVERSION=7.00.0000REPOSITORYPREFIX=pvx[PRODUCT:WindX Standalone]IDENTIFIER=WXSCURRENTVERSION=7.00.0000REPOSITORYPREFIX=pvx[PRODUCT:WindX Plugin]IDENTIFIER=WXPCURRENTVERSION=7.00.0000REPOSITORYPREFIX=pvx[10.100.1.1]ALLOWUPGRADE=NManifest.confVer = Current Version of the specified fileASCII/BINARY = File transfer type (Default is BINARY)ID = Is the value determined by cinfo to identify which product is on the work stationWXS = WindX StandaloneWXP = WindX PluginPVX = ProvideX with WindX withinREG = Windows registering options0 = Register and unregister the file with regsvr329 = Custom expression where you supply the command to be issued

Auto Updater

Example Manifest.conf File (continued)

# Manifest.conf - For ProvideX and WindX Version 7.00.0000# issued: July 2005

pvxcom.exe ;Ver=5.10.2000;ASCII;ID=WXS,PVX;Reg=9;RegInstall=pvxcom.exe /unregserver;RegUnInstall=/unregserver Pvxwin32.exe ;Ver=7.00.0000 # This is a remark

client server technologies

Documents