GUI Environment Training

1. GUI Environment Training Feb 12, 2004 Jeremiah Curtis jcurtis@nxtrend.com

2. SX.e Infrastructure • Unix Server • Staging Server • Gui Clients

3. Unix Server • Appbroker • Path • connect.pf • ubroker.properties

4. SX.e GUI Clients • Full Push Client • Full Progress install • Full SX code install • Code Server • Full Progress install • Full SX code install • Code Bundle • Network Client • Little Progress code • No SX code

5. SX.e Thin Clients • Windows Terminal Server • Full Push Client • Host based model • Virtual Computers for multiple users • No extended deployment issues WAN

6. SX.e Thin Clients • Windows Terminal Server and Citrix • Runs directly on the Terminal Server • Improves WAN performance with ICA Protocol • Web based access • ICA Client access WAN

7. Staging Server Install • Directories • pf, ini • Library files • Shares

8. Files In Setup Distribution • SETUP.EXE – main setup program • SETUP.INX – the script • README.TXT – latest update doc • NXTSETUP.INI – version info • Support files • Data*.cab and hdr • Ikernel.ex_ & layout.bin – installshield • SYSTEM subfolder • Dll’s and OCX’s copied and registered to window’s system folder

9. Where found: CD Media (staging and patch) nxt<env>/client (and <env>ins$) Staging/code/trend (always unencrypted) Contents: [version]current=3.0.000baseline=yeslastbaseline=3.0.000ProgressMin=9.1B08ProgressMax=9.9ProgressVer=9.1BStartupParams=-rereadnolock -D 500LocalStagingParams=LocalClientParams=-TB 8 –pls [encryption]xcode="R&D" NXTSETUP.INI

10. Nxt<env>\Client Directory • Contains copy of the setup from CD for installation on clients • Creates and Modifies these files: • NXTCLIENT.INI – database /setup params • NXTSTAGING.INI – push client types and names • NXTSTAGING.LOG – push results • Do not delete these files during uninstall, if doing re-install

11. NXTCLIENT.INI • [Staging]DBNames=sx30 list of database physical namesDBServices=sx30 corresponding service names for services fileDBPorts=8005 corresponding port numbersAppserverService=sx30a Appservice nameDatabaseHost=chef Unix host nameRdDir=/release/sx30/rd/tmp Default directory for FTPStagingMachine=JBAUMGAR2000 Used to create netpath.pf on clientsHiddenShare=$ If $ then shares will be hiddenNxtShare=NxTRel1$ Sharename network clients will point toCodeShare=Rel1COD$ for convenience - not referenced ClientShare=Rel1INS$ Install share point for new clientsProgressShare=Prog9.1B$ Progress installation share name used by installProgressNetShare=DLC9.1B$ If set, is the Network Progress share for clientsProgressDir=C:\NxTProg\9.1B local code server progress setup (From cd)Environment=NxTRel1 DLC=c:\dlc91B local version of dlc for execution ShellObjectFolder=NxTrend Technology for start menu iconsStartMenuIcon=YES if add login icon to start menu

12. NXTCLIENT.INI (part 2) • [Patch]SXPatchPath=D:\SXPATCH\setup.inx If SX patch was installed • [Compression]Compression=DZ_EZ32.DLL If compression enabled • [Progress] for Auto Batch installProgressBatch=YESProgressCompany=NxTrend Technology Inc.ProgressProducts=ClientNetworkingProgressSerials=002921471ProgressControls=Z9CRS XQEXM KMCYJProgressDefaults=TRUEProgressVer=9.1B

13. NXTSTAGING.INI • For each client (including staging and server) installed from this staging / code server • [Section] = the name of the machine • Values in the section • SetupType= - Staging, Server, Client • ClientPushFlag= - TRUE or FALSE • <file>PushDate= - date/time of last push • <file>PushFile= - destination file location • <file>PushFileDate= - timestamp of file

14. Sample NXTSTAGING.INI • [staging0]SetupType=StagingClientPushFlag=TRUE • [server1]SetupType=ServerClientPushFlag=TRUEhelpPushDate=200103051915helpPushFile=\\DEPLOY2\NxTRel1$\Client\Code\help.ziphelpPushFileDate=200103051915 • [fullpush2]SetupType=ClientClientPushFlag=TRUE • [netclient3]SetupType=ClientClientPushFlag=False

15. Installation Local PF Files (machine specific) • Local/local.pf (normally empty) • -T c:\temp (win95 only) • -T “%TEMP%” used in shortcut (98/nt/2000) • Local/netpath.pf • -param PROPATH=server-propath.ini [server]=\\<codeserver>\NxT<env>$

16. PF’s in Code Directory (common for all) • Code/login.pf • -pf ..\Local\netpath.pf-pf startup.pf-p li.p • Code/startup.pf • -pf ..\Local\local.pf-rereadnolock -D 500 • Code/connect.pf • -db <dbname> -ld nxt -N tcp -H chef -S <service> -cache nxt.csh

17. PF’s in Staging Code (staging machine) • Staging\code\push.pf • This modifies the standard login to prompt user to push code (after a test login) • -pf ..\Local\pushparam.pf -pf startup.pf-p li.p • Staging\code\ab.pf • Launch appbuilder with same login propath • Staging\local\pushparam.pf • -param "PUSH-CODE PROPATH=server-propath.ini [server]=\\<staging>\NxT<env>$"

18. Patch Install • Download Patch • Custom Code • Test env first • Compile • Conversion programs

19. Compiles • Gui Compiler • Logs

20. GUI Clients • Terminal Server • Client PC’s • Progress install

21. ODBC • ODBC Access • Setup

22. Windows Admin • Backups • Important Directories • File usage • User Tracking

23. Network Admin • Connectivity Requirements

24. Test Environments • Test Company • Same files on disk • Access to other company data • Test Environment • Full copy of files on disk • Snapshot in time

25. Support Architecture • Points of access • UNIX • Windows • Staging Server • Code Server • Client • Network access • Telnet • FTP/SFTP • SSH • PCAnywhere • Dial up Internet

26. Questions?