1 / 29

SXe on Windows 2000

SXe on Windows 2000. Installing Windows 2000 Server, Progress, and SXe. Windows 2000 Systems. Windows vs. Unix Windows offers: Friendly User Interface Less Specialized Administration Less Expensive and Less Complex Windows brings with it: Friendly User Interface

yannis
Download Presentation

SXe on Windows 2000

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SXe on Windows 2000 Installing Windows 2000 Server, Progress, and SXe

  2. Windows 2000 Systems • Windows vs. Unix • Windows offers: • Friendly User Interface • Less Specialized Administration • Less Expensive and Less Complex • Windows brings with it: • Friendly User Interface • Easier to Break for Inexperienced Administrators • Untested on Higher Numbers of Users (50+) • Unstable?

  3. Why Windows Fails Windows systems fail most often because of culture, not from the technology.

  4. Why Windows Fails • Circumstances that make Windows Fail • Treated Like Workstations • Too Easy to Access and Use • Poor Change Control • Not Patched Properly • Inexperienced Administrators • Browsing the Internet • Downloading Cool Things • Playing Games

  5. How to Make Windows Work • Microsoft’s Answer • MOF • http://www.microsoft.com/business/services/MOFoverview.asp • Wizards • Auto updates • Certifications • NxTrend’s Answer • Education of MA’s • Education of Customers • Emphasis on a cultural shift in the approach to Windows 2000 Servers.

  6. Best Practices for a Stable MS System • Culture • Hardware • OS • Recovery

  7. Best Practices for a Stable MS System • Culture • It is a Server • Carefully Dedicated Function • Combine functions in tested configurations only • Control Changes (Change Management) • Journaling • Testing

  8. Best Practices for a Stable MS System • Hardware • Use Server Class Hardware • Physical Security • Redundancy • RAID • Processors • Network Card / Switches • UPS / Power Supplies • Redundant Servers / Clustering

  9. Best Practices for a Stable MS System • OS • Fresh Installs, not OEM Installs or Existing OS’s • OS Standards • Patches • Hotfixes • Critical Updates • Security Updates • Service Packs • Standard Software • Virus Protection • Security • User level • Physical • Patches

  10. Best Practices for a Stable MS System • Recovery • System Diagrams and Inventory • Warranty Active and Adequate • Backups Running and TESTED • Recovery Plan • Network Outage • Hardware Failure • Full Rebuild Times • Contact Lists • Automated Monitoring • Engineering Assessment

  11. Windows 2000 Stability The Key to SXe on 2000 Change in approach to Windows Servers

  12. SXe Hardware Requirements • RAM • 1.5G for 25 • 2.5G for 50 • Processors • 2 Pentium III processors for 50 people • Network • 20k of committed bandwidth per terminal client • Disks • RAID • RAID 1 for OS • RAID 10 for Data • I/O • 4G OS and 9G Data as the minimum.

  13. OS Installation Start OS Installation

  14. OS Installation Finish OS Installation

  15. Progress Installation Install Progress

  16. Progress Installation Progress License Codes

  17. SXe Installation GUI SXe Installation

  18. SXe Installation CHUI SXe Installation

  19. SXe Application Setup and Test • Enter license code • Re-login

  20. SXe Application Setup and Test • CONV (Conversions) • Re-login • Set up printers • SASP (Set up printers) • SASC (Set print directory) • SARSE and SAPJ (Check jobs and Report Manager) • SASO (Setup System Security)

  21. Available for reverse compatibility only Old SXe Function • Terminal Server Client • Full Progress install • Full SX code install • Preferred deployment method • 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

  22. SXe Application Function • Windows 2000 Server Components • SX Database • SX Staging Server • Terminal Services • Configuration • No MARC • Separate directories for backend database & staging environment • Smaller user configurations

  23. SXe Administration • Staging Environment • Root dir. e:\NxT{env} • Client dir. e:\NxT\Client or \\sysname\INS$ • Database Environment • Root dir. e:\Sxe{env} • Database e:\Sxe\db\nxt.db • Code dir e:\Sxe\rd\src • Library e:\Sxe\rd\lib

  24. SXe Administration • Location of Scripts • E:\sxe\rd\bin • Location of Logs • E:\sxe\rd\logs • E:\sxe\rd\tmp (report logs)

  25. SXe Administration • Starting Stopping DB and components • Starting the Database • Start Admin Server Service • E:\sxe\rd\bin\nxtall.start.bat • Stopping the Database • E:\sxe\rd\bin\nxtall.stop.bat • Stop Admin Server Service • Starting Report Mangers • E:\sxe\rd\bin\rptmgr.start.bat • Stopping Report Managers • E:\sxe\rd\bin\rptmgr.stop.bat

  26. SXe Administration • Schedule Backups • T-F Daily • S Full • The Full Backup • Rdclean • Configuring Backups • Backup.data.full.bat • Backup.data.daily.bat • Backup.bks • Nxt.env.bat

  27. SXe Administration • Restores • Same as Unix • Take down DB • DB Backup files should be in the backup directory • Run Restore.db.bat

  28. SXe Administration • Using Terminal Services • What is it? • Terminal Services and Temporary Files • Citrix

  29. SXe on Windows 2000 • Future • Future of 3rd Party Apps • Clippership • eSales • FRx • Future Functionality • AI • Rdclean • Report Manager Cleanup • Dump and Loads

More Related