Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
David M. Walker
Technical Leader
Professional Services
Introduction
Requirements
Networking
Conclusion
Modular
Resilient
Scaleable
Database Server
(multi node cluster)
Batch/Print Server
(two node cluster)
Server Network
(FDDI)
Application
Server
(free standing)
Client Networks
Traditional ‘Server’
Resilience
!! Use OPS for fail over
!! Use disk mirroring
Scaleability
!! Use OPS for ‘out of box’ growth
–! Modular Application Design Useful
!! Use disk striping
Two Type
!! ‘Host’ Based
!! ‘Client’ Based
Clone machines provide resilience and scaleability
‘Thin’ Clients
‘Thick’ Clients
Resilience options
!! Use database to hold queue
!! Cluster aware batch manager
!! Use fail over file systems to move queue
Scaleability
!! Design manager to run programs where resource is
available (e.g. Application or Batch Server)
Resilience options
!! Use database to hold queue
!! Cluster aware print manager
!! Use fail over file systems to move queues
Options
!! Distributed across application servers
–! Large number of complex queues to manage
–! Needs intelligent printers
–! Interferes with application server work
–! Not very scaleable or resilient
!! Centralized printer server
–! Single point queue management
–! Output must be sent to server for queuing which
increases network traffic
Options (continued)
!! Hybrid print servers
–! Central Queue Manager (CQM)
–! Local queues on Application Servers address by CQM
only
–! Large number of simple queues to manage
–! No large network file transfers
Database Server
!! Use ‘Hot’ & ‘Cold’ backups
!! Use OPBRU where available
!! Use resilient media (3480 or 3490)
!! Use low capacity media with tape managers
Application, Batch and Print Servers
!! Use standard Configurations
!! Keep transient files of separate file systems from static
code