SCS Advertising System requirements for Layout-8000, SCS/ClassPag, AdMAX, and CAS/CDS
Client Requirements
- Xming and PuTTY for Windows Vista/7/8/10
- Native X11 support on Linux
- X11 application (XQuartz) for Mac OSX
- X2Go for low bandwidth network connections
- Current web browser (Chrome, Firefox, IE, Opera, Safari) for CAS/CDS
- 2 GHz processor or faster
- 1 GB RAM or better
- Desktop software (such as InDesign) may have additional client requirements.
Layout | ClassPag | AdMAX | CAS/CDS | |
Xming/ PuTTY/ X2Go |
| | | |
X11 Linux/Mac | | | | |
Web Browser | |
Server Requirements
- RHEL/CentOS v7 64-bit
- X11 windowing system
- CUPS printing system
- printers to be configured on the server – Postscript level 2 network printer(s)
- Sendmail or Postfix
- Apache server
- CPU - Two 2.5 GHz processors or better.
- RAM - OS plus up to 10 users, minimum 4 GB, or OS plus up to 20 users, minimum 6 GB, or OS plus up to 40 users, minimum 8 GB. Add 2GB of RAM for each additional 20 users.
- A “/u” file system with a minimum of 100 GB free disk space – consolidation/data center 150 GB to 200 GB free disk space for Layout-8000 and SCS/ClassPag. When AdMAX is included, allocate an additional 100GB. AdMAX sites that use external editors (such as InDesign) to build ads should allocate an additional 200 GB of disk space. CAS/CDS sites should allocate 300 GB of disk space for /u. CAS/CDS sites should provide a network resource that can store up to 1 TB of archived ads for restoration of expired ads.
- Local Administrator privileges for application installation.
- Two active instances of the VM (or physical servers) are necessary to implement SCS High Availability (HA) Application Mirroring. One to act as the Primary server and the other to act as the Standby server. A shared IP address is used to control which server is the production server at any given time. All client connections to the pair of servers should use the shared IP address.
- When assigning a name to the servers, we suggest avoiding the use of “primary”, “standby”, and “secondary”. These titles can become confusing when roles are reversed.
- When moving an SCS application from an existing server to a new server create all users and printers with names that match exactly to the names used on the existing server. This will simplify the configuration of the new server.
- All users should belong to the “scs” group.
- All users should have an individual home directory. This directory should be in /u/users_scs.
- SSH access to the SCS Advertising servers will need to be available for support, configuration and upgrades to the applications.
- We recommend using SMB for all mounts. Macs unable to use SMB may require netatalk to be installed and configured on the servers.
- The servers will need to have external Internet access to process credit cards, receive SCS upgrades, OS updates and general application support.
RHEL/CentOS package selection
- Click on “Software Selection”.
- Under “Base Environment”, select “Server with GUI”.
- Under “Add-Ons for Selected Environment”, select:
- E-mail Server
- FTP Server
- File and Storage Server
- Hardware Monitoring Utilities
- Network File System Client
- Performance Tools
- PostgreSQL Database Server
- Print Server
- Remote Management for Linux
- Compatibility Libraries
- Development Tools
- Security Tools
Services to enable on the SCS Advertising server
- cups
- httpd
- sendmail
- smb
- sshd
- rsync
Ports to enable on the SCS Advertising server
- 21 – ftp
- 22 – ssh
- 80 – http
- 139 & 445 - smb
Comments
0 comments
Please sign in to leave a comment.