Embed Size (px)
Citation preview
SX.e Administration
• Components
• NT and the Staging PC
• Considerations
• Performance
SX.e Components
D a ta b a s e S e r v e r (U n ix )
C o d eS e r v e r (N T )
P CC lie n t
P CC lie n t
A p p lic a tio n S e r v e r(N T T S /C itr ix )
P CC lie n t
Other OSClient
Brow serC lient
P rogre ss Da ta ba se- Handles Data- Handles Client Reques ts- Unix OS
NT File S e rve r- P rovides Code for Clients- W indows NT/2000 S erver OS
Applica tion Clie nt(s)- E xecutes S X.e GUI Code- Needs P rogress Runtim e- W indows 32bit OS
Thin Clie nt- Only Handles A pplication I/O- A ny supported c lient (OS /type)
Grey areas indicate the location of SX.e GUI execution.
SX.e ComponentsUnix Box – Progress 8
• Different Brokers provide services on different TCP/IP ports– DB Broker, must start first – shutdown last
– AppServer Broker (GUI Clients)
– OI Broker (ODBC connections, Brio, ClipShip)
netstat –a | grep LISTEN | pg
ps –ef | grep nxtdb.pf
ps –ef |grep apbk
ps –ef |grep oibk
SX.e ComponentsUnix Box – Progress 9
• Different Brokers provide services on different TCP/IP ports (Progress 9)– AdminServer
– AppServer Broker (GUI Clients)
– OI Broker (ODBC connections)
netstat –a | grep LISTEN | pg
ps –ef | grep adminserver
ps –ef |grep nameserver
ps –ef |grep apbk
SX.e ComponentsNT Box(es)
• Staging PC / Code Server
– Compile Code (Staging PC)
– Host Code (Code Server)
• Windows Terminal Server
– Host Clients (GUI application)
– Host Clients (character application)
SX.e ComponentsClients
• Windows PC
– GUI application
– Character application
• Windows PC
– Terminal Server client
SX.e Administration
• Components
• NT and the Staging PC
• Considerations
• Performance
NT and the Staging PCNT Admin
• User Management (User Manager)– Guest Account
• Code Server (may need to enable)
• CMI Server (enable, unless share is modified)
• Shares and File/Dir Permissions– CMI Server
• \\server\cmi
– Staging PC• \\server\ins$ (Client installs from here)
• \\server\nxt$ (runtime code if Code Server)
• \\server\cod$ optional (test code area)
NT and the Staging PCStaging PC
• Primary purpose is to compile and distribute SX.e code.
• If Code server, NT Server* required for the larger number of connections needed.
• Do not put on a Terminal Server.
• Do not combine functionality on NT Servers beyond “two”. It is cheaper and better performing to have multiple NT servers than one monolithic server.
– NT Servers are scalable for the “one” or “two” functions they serve, but not for more functions.
– Put Exchange on its own hardware platform.
NT and the Staging PCPatches
• With General Release patches, an email notification is sent to the customer.– With No Custom Code issues, the email provides a link to
the patch download
– With Custom Code issues, an email is sent saying so. They will need to talk to SI for necessary code changes.
• For Pre-Release patches– Login to CustomerCare.NxTrend.com
– Scroll down to the bottom of the page under Release Information
– Click on a Pre-Release hyperlink for your version
– Email request
– Same code review will take place, with the same email procedures as a General Release above.
NT and the Staging PCPatches cont.
• Follow patch installation procedures on CustomerCare.NxTrend.com.
• Newer GUI patches will automatically compile code and create a new library file, standard.pl
• Compile code for AppServer and Char through MARC and do at the same time as a push.
• Recommend a full test env. Test database env on Unix box, and test env on the staging box.
• For Progress patches, be sure to shutdown database and truncate.
NT and the Staging PCSX.learning - CMI
• Two basic forms
– CMI-Managed, files hosted by server
– CMI-Solo, files from CD-ROM
• Large dataflow requirements for clients, especially with sound
• Patches from CustomerCare.NxTrend.com
– Click on Doc, click on CMI, scroll down
– Separate patches may exist for Admin, Student, Server
SX.e Administration
• Components
• NT and the Staging PC
• Considerations
• Performance
ConsiderationsGeneral
• Redundancy provides for 100% uptime
• UPS services for all equipment and servers (extended runtime – 60mins)
• Make sure everything is scalable
• Network printing, rather than serial
• Client bandwidth throughout entire path
• Infrastructure can be used for other purposes
ConsiderationsNetwork
• 100Mbit switched environment
• Local (LAN based) name resolution• WINS and DNS
• Code resident on the PC client or on a server (possible network traffic)
ConsiderationsWAN
• Client bandwidth on each segment
• Committed Information Rate (CIR)
• Quality of Service (QOS)
• Bandwidth Shaping
ConsiderationsInternet
• Quality of Service (QOS)
• Security– Firewalls (limit/route access)
– VPN’s (grant/deny access)• Provide for encryption
• Account driven
– NAT (Network Address Translation)
• Bandwidth Shaping
ConsiderationsThin Client
• Graphical terminal session
• Processing takes place on a central host
– Concentrate horsepower
– Easier security and administration
• Clients only process input and output
– Smaller bandwidth demands (12Kbit), shorter data streams (bursts)
ConsiderationsWindows Thin Client
• Requires NT 4.0 Terminal Server or 2000 Server with Terminal Services (NTTS)
• Requires separate CAL’s – client licenses
• Can be enhanced with Citrix Metaframe
• User accounts can be tied to the Domain
SX.e Administration
• Components
• NT and the Staging PC
• Considerations
• Performance
PerformanceNetwork
• Ethernet Networks are CSMA/CD
• Eliminate port saturation, <%50 (30/60)
• Backbone is X times faster than segments
• Switched (switches) over Shared (hubs)
• Use Full Duplex where possible
• To a user, the network is only as fast as the slowest link to the resource (constraint), physically or logically
PerformanceUnix Server
• Live Env ((10MB * users) + 200MB) * 1.5
• Test Env ((10MB * users) + 200MB)
• 35 users per disk
• Dual controllers for RAID
• 1 side of mirror on each controller
• Reboot monthly
• D&L yearly
PerformanceUnix Server
• Memory usage (vmtune)
• Paging usage (lsps –a)
• Check paging activity (vmstat 4)
• Increase –B (MARC) -bi (truncate script)
• Check print dirs (on striped array)
• Reboot monthly
• D&L yearly
PerformanceNT Server
• Dual CPU, lots of RAM (best bang for buck)
• Run NTFS on all file systems
• Run a disk defragmenter weekly
• Increase virtual memory to 2x RAM
• Antivirus software (exclude *.pl)
• Reboot monthly
• Rely on hardware redundancy over tape backups; mirroring, etc.
PerformanceBusiness
• Bandwidth Needed– Determine # of users & location– Determine capacity demand for each
• Application performance (sub-sec or not)
• % Uptime required
More Information
• NT www.microsoft.com/ntserver
• Networking www.techrepublic.com
www.cisco.com, www.ibm.com, www.hp.com
msdn.microsoft.com/library/default.asp
• Thin Client www.citrix.comwww.microsoft.com/windows2000/technologies/terminal/default.asp
• NxTrend customercare.nxtrend.com
