GUI Environment Training Feb 12, 2004 Jeremiah Curtis

SX.e Infrastructure Unix Server Staging Server Gui Clients

Unix Server Appbroker – Path – connect.pf – ubroker.properties

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

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

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

Staging Server Install Directories pf, ini Library files Shares

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

NXTSETUP.INI Where found: –CD Media (staging and patch) –nxt /client (and ins$) –Staging/code/trend (always unencrypted) Contents: –[version] current= baseline=yes lastbaseline= ProgressMin=9.1B08 ProgressMax=9.9 ProgressVer=9.1B StartupParams=-rereadnolock -D 500 LocalStagingParams= LocalClientParams=-TB 8 –pls –[encryption] xcode="R&D"

Nxt \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

NXTCLIENT.INI [Staging] DBNames=sx30list of database physical names DBServices=sx30corresponding service names for services file DBPorts=8005corresponding port numbers AppserverService=sx30aAppservice name DatabaseHost=chefUnix host name RdDir=/release/sx30/rd/tmpDefault directory for FTP StagingMachine=JBAUMGAR2000Used to create netpath.pf on clients HiddenShare=$If $ then shares will be hidden NxtShare=NxTRel1$Sharename network clients will point to CodeShare=Rel1COD$for convenience - not referenced ClientShare=Rel1INS$Install share point for new clients ProgressShare=Prog9.1B$Progress installation share name used by install ProgressNetShare=DLC9.1B$If set, is the Network Progress share for clients ProgressDir=C:\NxTProg\9.1Blocal code server progress setup (From cd) Environment=NxTRel1 DLC=c:\dlc91Blocal version of dlc for execution ShellObjectFolder=NxTrend Technologyfor start menu icons StartMenuIcon=YESif add login icon to start menu

NXTCLIENT.INI (part 2) [Patch] SXPatchPath=D:\SXPATCH\setup.inxIf SX patch was installed [Compression] Compression=DZ_EZ32.DLLIf compression enabled [Progress]for Auto Batch install ProgressBatch=YES ProgressCompany=NxTrend Technology Inc. ProgressProducts=ClientNetworkingProgressSerials= ProgressControls=Z9CRS XQEXM KMCYJ ProgressDefaults=TRUE ProgressVer=9.1B

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 – PushDate=- date/time of last push – PushFile=- destination file location – PushFileDate=- timestamp of file

Sample NXTSTAGING.INI [staging0] SetupType=Staging ClientPushFlag=TRUE [server1] SetupType=Server ClientPushFlag=TRUE helpPushDate= helpPushFile=\\DEPLOY2\NxTRel1$\Client\Code\help.zip helpPushFileDate= [fullpush2] SetupType=Client ClientPushFlag=TRUE [netclient3] SetupType=Client ClientPushFlag=False

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]=\\ \NxT $

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 -ld nxt -N tcp -H chef -S - cache nxt.csh

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]=\\ \NxT $"

Patch Install Download Patch Custom Code Test env first Compile Conversion programs

Compiles Gui Compiler Logs

GUI Clients Terminal Server Client PC’s Progress install

ODBC ODBC Access Setup

Windows Admin Backups –Important Directories File usage User Tracking

Network Admin Connectivity Requirements

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

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

Questions?