Notice. RuffaloCODY 65 Kirkwood North Road SW Cedar Rapids, Iowa 52404

Transcription

1

2 Notice The information in this document is the sole property RuffaloCODY. All rights to this publication are reserved. This document shall not be reproduced, copied or disclosed without the express written permission of: RuffaloCODY 65 Kirkwood North Road SW Cedar Rapids, Iowa If a purchase, license or non-disclosure agreement is in place, the terms of said agreement shall govern this document RuffaloCODY All rights reserved.

3 Table of Contents CAMPUSCALL SERVER PREPARATION...4 CAMPUSCALL SERVER SPECIFICATIONS...5 SUGGESTED UPGRADES TO BASE CONFIGURATION...6 HARDWARE SETUP...7 SYSTEM SETUP...7 SHARED FOLDERS...9 MAPPING SHARED SHARED FOLDERS FIREWALL EXCEPTIONS... 11

4 CAMPUSCALL SERVER PREPARATION This document is intended to assist the campus technical staff in preparing the CAMPUSCALL server for remote installation of or upgrade to CAMPUSCALL. Prior to the RuffaloCODY Implementation Team beginning the installation of CAMPUSCALL, basic setup on the server will need to be completed and remote access will need to be established from RuffaloCODY to the server.

5 CAMPUSCALL SERVER SPECIFICATIONS BASE CONFIGURATION Dell PowerEdge 1900/2900 (Tower) or 1950/2950 (Rack Mount) or comparable system: Dual (2) 3.2GHz/2MB Cache 800MHz FSB Xeon Processors 4GB DDR2 SDRAM 266MHz (2x1GB) 1-73GB 10K RPM Ultra 320 SCSI Hard Drive or 2-36GB 10K RPM Ultra 320 SCSI Hard Drives (Note: See partition setup information under System Setup. CAMPUSCALL requires a physical or logical D: drive partition) Dual NICs 48x IDE CD-ROM 17 Inch (16.0 Viewable) CRT Monitor Keyboard, Mouse 3 Year - Next Business Day Onsite Warranty Important Note: The configuration above is totally suitable for running the CAMPUSCALL application in nearly all environments. As a Base Configuration, however, it does not contain any sort of hardware redundancy. Please be aware there is an increased risk of downtime with this type of configuration.

6 SUGGESTED UPGRADES TO BASE CONFIGURATION (RECOMMENDED BY RUFFALOCODY OR AS REQUIRED BY CAMPUS IT STANDARDS) Dual core Xeon Processors Multiple processors (four processors instead of two) Additional hard drive space 15K RPM Ultra 320 SCSI Hard Drives Raid 1 or 5 Configuration with 2 or 3 disk drives, respectively. (With PERC4/ei 128MB controller or comparable) Redundant Power Supply w/ Straight and Y-Cords Site-specific Backup Software Standalone Server: Tape Backup Unit - Dell PowerVault 100T DAT72 Tape Backup - Stand alone 1500 Uninterruptible Power Supply (UPS) (or comparable) Server located in a campus data center: Enterprise backup system and software Uninterruptible Power Supply If you have any questions about the server specifications, please contact the CAMPUSCALL Implementation team.

7 HARDWARE SETUP The CAMPUSCALL server will need to be unboxed and setup. In most cases, when the server is located within the campus datacenter, it will be rack mounted in a cabinet within the datacenter. SYSTEM SETUP The drives on the server should be configured at follows: C: 20-30GB this will be used for the Windows 2008 Server Operating System D: Remaining hard drive space should be allocated to this drive for the installation of Oracle and the CAMPUSCALL applications. Note the D: drive is required for the installation of CAMPUSCALL. The Windows 2008 Server Operating system should be installed on the C: drive. Note: Microsoft IIS should not be installed on the server Install any antivirus software as per institution policies. The server should be connected to the campus network. If the server is to be part of the campus domain, join the server to the domain. All Windows 2003 or 2008 Server Operating system updates and patches should be installed. Install any other utilities or software as per institution policies and procedures. A static IP address should be assigned and configured on the CAMPUSCALL server. Note: If the server name and /or IP address needs to be changed at any time following the installation, please contact CAMPUSCALL Support at (800) PRIOR to making any of these changes. Making changes to the server name and/or IP address will cause problems with both Oracle and CAMPUSCALL and in most cases cause CAMPUSCALL to no longer function. Please contact CAMPUSCALL Support at (800) PRIOR to making any of these changes so that we can work through the process with you to keep CAMPUSCALL up and running. Establish a user on the server (may be either local or domain user) with local administrative rights to be used by the CAMPUSCALL Implementation Team for the installation and for ongoing use by CAMPSUCALL Support. Set up any VPN accounts and/or users needed to access the server. Communicate connection information to the CAMPUSCALL Implementation Team to allow them to begin the installation process

8 Install any backup software to be used on the server. The CAMPUSCALL Implementation Team will need access to our secure FTP site from the server to upload the installation software to the server. Please inform the CAMPUSCALL Implementation Team of any restrictions your site may have on this process. Network access to the server through Windows file sharing during the call center installation process will make things go more quickly.

9 SHARED FOLDERS A number of shared folders will be set up by the CAMPUSCALL Implementation Team on the CAMPUSCALL server: Holding: Used for stored reports that are batched and scheduled to run through CAMPUSCALL. Anyone needing access to these reports will need access to this shared folder. Loader_in: Used to store control files, data files, log files and applications to load data into CAMPUSCALL. Individuals loading data into CAMPUSCALL will need access to this folder. Data_Out: Used to store data files extracted from CAMPUSCALL using the Selection Wizard and Upload Process. This files will normally be used to merge with your pledge letter for pledge confirmations. Backups: Used to store the daily exports from the CAMPUSCALL system (in most cases, the exports are scheduled to run automatically with the End of Day process). This folder should be backed up on a regular basis. Someone on site should be assigned to verify that exports are running properly. See the CAMPUSCALL Disaster Recovery document for complete backup procedures. The permissions to these folders are assigned through the local group CC_Operations. The CC_Operations group may also be set up at a domain group, if so desired by the campus IT staff. Individuals needing access to any of these shared folders will need to be added to the CC_Operations group on the server, either by adding a local user account to the server or by adding the domain user to this group.

10 MAPPING SHARED SHARED FOLDERS Once the user is added to the CC_Operations group on the server, they will need to connect to these shared folders using a mapped network drive from the local computer. This is done as follows: Right click on My Computer and select Map Network Drive Enter the path to the CAMPUSCALL server in the box labeled Folder. Note the example below this box. This should reference both the server name and share name Example: \\campuscall\holding In some cases, this reference may need to use the server IP address Example: \\ \holding Verify that the Reconnect at logon box is checked. Click on Finish to complete this process.

11 FIREWALL EXCEPTIONS If there is a firewall in place between the call stations and the server, the call stations will need access to the server on the following ports during production calling: Protocol / Port Usage TCP 8080 (CAMPUSCALL) TCP 7327 (CAMPUSCALL Reports Plus) Administrative stations that will be loading and extracting data to and from the CAMPUSCALL system will need these additional ports: Protocol / Port Usage TCP 139 (Window file and print sharing) TCP 445 (Window file and print sharing) UDP 137 (Window file and print sharing) UDP 138 (Window file and print sharing) TCP 1521 (Oracle)