This page details all of the services and applications that are running as part of the RAS operational environment, specifically on the raweb-prod servers.
All of these files and services are owned by the 'tomadm' user on the servers.
|Environment||Web Server||Database Server|
raweb-dev-02.uit.tufts.edu - new dev server
radb-test-05.uit.tufts.edu - same server as TEST
raweb-test-02.uit.tufts.edu - new test server
radb-test-05.uit.tufts.edu - new dev and test database server
|Stage||raweb-stage-01.uit.tufts.edu / raweb-stage-02.uit.tufts.edu||radb-stage-01.uit.tufts.edu / radb-stage-02.uit.tufts.edu|
|Prod||raweb-prod-01.uit.tufts.edu / raweb-prod-02.uit.tufts.edu||radb-prod-01.uit.tufts.edu / radb-prod-02.uit.tufts.edu|
Apache Tomcat 8.5.38
Installed at /usr/local/apache-tomcat-8.5.38
Hosts all publicly available web applications
webapps directory contains the following files:
There are a number of automated scripts and jobs which run via a cron schedule. Each of these is detailed below.
Purpose: Scans for budgets in the 'To Be Posted' state in the Award Budget tool, and populates the necessary data for that award+budget in the tables which PeopleSoft scans for new grant information. See the Peoplesoft Integration page for more details.
Schedule: Runs every five minutes on the 2s and 7s.
Purpose: Checks to see if there are any proposals in KC with rolodex (non-employee personnel) entries that cannot be found in the rolodex table. Set up to gather data for investigating an issue where rolodex entries are being removed from the table somehow (https://bugs.atech.tufts.edu/browse/RAS-1494).
Schedule: Runs every hour, on the hour.
Purpose: Scans the KC 'Sponsor' table, and automatically adds any new sponsors found to the appropriate location Sponsor Hierarchy (used for reporting purposes). New Federal sponsors cannot be added automatically as they need to be placed under the correct federal agency;
Schedule: Hierarchy update runs nightly at 11:45pm. Check for new federal sponsors runs nightly at 1:05am.
Purpose: Loads all person data from the Tufts LDAP server into a table within the KC database, then scans for new/updated person records and updates KC's person table appropriately. Runs in four steps:
Schedule: Copy of old data runs nightly at 11:50pm. Reading from LDAP server runs nightly at 12:00am. Updating the KC person table runs nightly at 12:15am. The error check runs nightly at 1:11am.
Purpose: Receives employee hire/termination/change events from HR and adds/removes security permissions as appropriate.
Schedule: Runs nightly at 12:25am. (Needs to be after the KC Person Feed, but before the Data Warehouse Update.)
Purpose: Stops and restarts the tomcat server every night. This was recommended by Kuali to prevent performance/memory issues.
Schedule: Server 1 restarts nightly at 12:30am; server 2 restarts nightly at 12:40am.
Purpose: Refreshes the database tables and views used by the Data Warehouse with current data.
Schedule: Runs nightly at 12:45 am. An error check which sends emails on any failures runs nightly at 1:10am.
Purpose: Sends an email alert when the LDAP person feed contained a unit number (aka Department ID) that is not already in the KC unit table. Units are added manually, as the LDAP feed does not contain the department name or school/campus info.
Schedule: Runs nightly at 1:00am.
Purpose: Loads the current list of 'keywords' from KC into a web page for easy reference. Updates the 'keywords' directory on the tomcat server (see above).
Schedule: Runs nightly at 1:15am.