Enterprise Architecture Securely scaling to hundreds of thousands of users, processing millions of pages and documents, to and from thousands of printers & multi-function devices. Enterprise Architecture Security High Availability Load Balancing Security Security Printers & MFDs Servers Users: File Print Security Printers & MFDs Servers/Datacenter Users: File Print Security firewall Presentation Tier Printers & MFDs firewall Users: File Print Datacenter Application Tier firewall Data Tier Highly Available & Load Balanced Configurations Presentation Tier Printers & MFDs Users: File Print Datacenter Application Tier Data Tier NSi Output Manager in a Highly Available & Load Balanced Configuration Application Tier Admin Configuration SMTP: 25 or SSL (Accounting Messages, Denied Jobs) WCF (HTTP/S): 8100 - 8199 Output Manager - Authentication - Release Print WCF (HTTP/S): Optional Load Balancer Example (F5) Database Manager (DBM) Service : This is the “master” service, which is the OM environment’s sole point of communication with its Database. The other services interact with this service. Rules Agent Service LPR: 515 Socket: 9100 IPP: 631 Output Service SNMP Service SNMP: 161 Printers & MFDs nodes dependent on environment (min 3x) Input Service Input Service Windows Print Service Windows Print Service HA: Independent Servers (also use VM redundancy – i.e. vMotion HA: Windows Clustering or Load Balancer SMB: 445 SQL: 1433 Data Tier Data Tier HA: Appropriate RAID HA: SQL Clustering SMB: 445 SMB Print Queues: 445 Users: File Print WCF: ~ Presentation Tier Application Tier Cluster Detail One cluster (or Load Balancer), external IP x.x.215.96 Application Tier Node 3: x.x.215.99 Node 2: x.x.215.98 Application Tier Application Tier Database Manager (DBM) Service : This is the “master” service, which is the OM environment’s sole point of communication with its Database. The other services interact with this service. Database Manager (DBM) Service : This is the “master” service, which is the OM environment’s sole point of communication with its Database. The other services interact with this service. Database Manager (DBM) Service : This is the “master” service, which is the OM environment’s sole point of communication with its Database. The other services interact with this service. Rules Agent Service Rules Agent Service Rules Agent Service Output Service Output Service Output Service SNMP Service SNMP Service SNMP Service Data Tier Data Tier HA: Appropriate RAID HA: Appropriate RAID 3 or more recommended nodes Node 1: x.x.215.97 NSi Output Manager in a Highly Available & Load Balanced Configuration Application Tier Database Manager (DBM) Service Printers & MFDs LPR: 515 Socket: 9100 IPP: 631 Output Service Data Tier SQL: 1433 Output Manager - Authentication - Release Print WCF (HTTP/S): HA: SQL Clustering SNMP Service SNMP: 161 Input Service Data Tier SMB: 445 Users: File Print SMB Print Queues: 445 Rules Agent Service HA: Windows Clustering HA: Appropriate RAID (Accounting Messages, Denied Jobs) WCF (HTTP/S): 8100 - 8199 SMTP: 25 or SSL Admin Configuration NSi Output Manager in a Highly Available & Load Balanced Configuration Application Tier Database Manager (DBM) Service Printers & MFDs LPR: 515 Socket: 9100 IPP: 631 SNMP: 161 Output Service Data Tier SQL: 1433 Output Manager - Authentication - Release Print WCF (HTTP/S): HA: SQL Clustering SNMP Service Input Service Rules Agent Service Data Tier SMB: 445 NJE/RJE Mainframe HA: Windows Clustering HA: Appropriate RAID Line of Business App SMTP: 25 or SSL Email, FTP, Folder, etc. Admin Configuration Output Manager (OM) Core Components Database: The SQL(E) database is the central data repository for OM (Office). The Database stores all configuration data, information and settings for printers and documents, parameters for alerts/rules/reports, and logs all activities. Database Manager (DBM) Service: This is the “master” service, which is the OM environment’s sole point of communication with its Database. The other services interact with this service. 1To Input Service1: Responsible for receiving documents from any Source you’ve defined into OM (Office). Output Service1: Responsible for sending documents from OM (Office) to any Destination you’ve defined. SNMP Service1: Responsible for detecting and monitoring the status of printers and documents sent to them. Rules Agent Service1: Responsible for managing any Adhoc, Business, or Alert Rules built in the environment. function, this service must be pointed towards a correctly configured OM DBM Service. File Store: The raw data of the documents/print jobs are stored in an OM File Store Server Configuration Utility: A small application installed automatically when one or more OM services is installed. It interfaces with any OM Service running locally on a server. It can stop, start and configure OM Services. It can also be used to define OM Administrators. NSi AutoStore in a Highly Available & Load Balanced Configuration Application Tier Process & Route Servers Mainframes Groupware & Collaboration Presentation Tier Capture Servers MFDs Various Ports & Protocols Content Management HA: Independent Servers File, Fax, Email SMB: 445 Data Tier SMB: 445 HA: Independent Servers Custom Applications ERP, Line of Business Applications, Electronic Health Record HA: Appropriate RAID NSi AutoStore – Single Server Mainframes MFDs Various Ports & Protocols Capture & Process & Route Server Groupware & Collaboration Content Management File, Fax, Email Custom Applications ERP, Line of Business Applications, Electronic Health Record NSi Mobile in a Highly Available & Load Balanced Configuration DNS Load Balancer Data Center Application Tier Mainframes Presentation Tier Users: Mobile Mobile Servers HTTP/S: 3291 Groupware & Collaboration Content Management File, Fax, Email HTTP/S: 8067 for myFiles Every port specified can be configurable ERP, Line of Business Applications, Electronic Health Record HA: See previous architecture TCP/IP: 1433 HA: using independent servers behind session capable load balancer NET TCP: 808 Proxy and/or Firewall HTTP/S: 443 Custom Applications for configuration data Data Tier HA: Appropriate RAID / SQL Clustering NSi in a Highly Available & Load Balanced Configuration Data Tier (stats) Application Tier Admin Configuration SMTP: 25 or SSL HA: SQL Clustering (Accounting Messages, Denied Jobs) WCF (HTTP/S): 8100 - 8199 Data Tier SQL: 1433 Temporary (TTL – Optional DNS Load Balancer Example (F5) Output Manager - Authentication - Release Print WCF (HTTP/S): sec/min) Database Manager (DBM) Service : This is the “master” service, which is the OM environment’s sole point of communication with its Database. The other services interact with this service. Rules Agent Service LPR: 515 Socket: 9100 IPP: 631 Mainframes Output Service SNMP Service HA: Appropriate RAID SNMP: 161 Printers & MFDs SMB: 445 Input Service Window Print Service SMB: 445 30% of users Custom Applications Data Tier SMB: 445 30% of users Input Service Users: File Print File, Fax, Email HA: Windows Clustering/LB nodes dependent on environment (min 3x) SQL: 1433 30% of users Input Service Capture Servers Window Print Service Process & Route Servers Window Print Service Presentation Tier WCF: ~ Application Tier Content Management Presentation Tier Optiona l DNS Load Balance r Exampl e (F5) SMB Print Queues: 445 Groupware & Collaboration Data Tier Temporary (TTL – days) HA: Appropriate RAID HA: SQL Clustering ERP, Line of Business Applications, Electronic Health Record HA: Independent Servers HA: Independent Servers WebSphere MQ Source HTTP/S: 3291 Presentation TierMobile Servers Users: Mobile Mainframe HTTP/S: 443 Line of Business App Email, FTP, Folder, etc. HTTP/S: 8067 Proxy and/or Firewall HA: using independent servers behind session capable load balancer for configuration data for myFiles Data Tier HA: Appropriate RAID / SQL Clustering TCP/IP: 1433 NET TCP: 808 Optiona l DNS Load Balance r Exampl e (F5) Print: Supporting more than 50M pages per your print Scan: Supporting more than 10M pages per your scan Enterprise Architecture Distributed Output Manager with Branches Locations OM Distributed Print Normal Windows Printing Local Office HQ Office Direct IP Printing Printing via Windows Print Servers OM Distributed Print Printing via Output Manager Local Office HQ Office Printing via Windows Print Servers Concerns around Network Bandwidth OM Distributed Print Printing via Output Manager Local Office HQ Office Printing via Windows Print Servers Prints are stored locally, but still requires network connection for authentication, and to upload print stats. Management is all done at HQ Enterprise Architecture Definitions Definitions • Production • Disaster Recovery • Development • Test • High Availability • Disaster Recovery Definitions: High Availability No single point of failure, often using a Load Balancer and/or a Cluster Servers Disk Database NSi Output Manager in a Highly Available & Load Balanced Configuration Application Tier/ Backend Servers Print Printers & MFDs nodes dependent on environment Presentation Tier/ HA: Windows Clustering or Load Balancer Load Balancer (i.e. F5) Users: File Print Manual Load Balancing Or using Load Balancer Frontend Servers Data Tier Data Tier HA: Appropriate RAID HA: SQL Clustering Definitions: Disaster Recovery Can be a 100% mirror of Production/Primary, or a subset Production/Primary Disaster Recovery
© Copyright 2024