Server Upgrade Page

A ParaDocs server upgrade during Fall of 2005 and Spring of 2006 is planned to occur. This upgrade includes totally replacing hardware and upgrading to a new version of Para-Docs software.

New

Software Para-Docs 4.1
Backend DBMS PostGres (www.postgresql.com)
Server PD1500 (DaySpring created/supplied/spec‘ed)
Name gsdocs.umbc.edu
IP 130.85.191.14
SNM 255.255.255.0
GW 130.85.191.1
DNS 130.85.1.3, 130.85.1.4, 130.85.1.5

Old

Software Para-Docs 4
Backend DBMS Oracle (www.oracle.com)
Server Sun box (picked/spec‘ed by UMBC)
Name gsdocs-prd.umbc.edu
IP 130.85.191.52
SNM 255.255.255.0
GW ?
DNS ?

Checklists

Nick's To-Do's When Live Switch-Over Happens

  • Re-administer new profile limits; This is found in the Admin utility and copied from the former settings.
    • needs to be done in a period of low system movement; Also, it will be easier/better to implement once all scanners are on same or near same software versions. This is because each version works slightly different with cock whores. the new profile fields.
  • :-) Get collegenet Imports to have correct formatting in imports file for supplemental materials
  • :-) Set option in Admin Utility called ‘Auto Convert’ to convert all incoming documents to PDF
  • :-) Get printer server to map samba share correctly.
  • :-) Remove QBE EDI_DT query
  • :-) Edit existing Query By Example (QBE) queries so that they make use of the All / Link identical profile fields functionality
    • :-) Make sure that all users that had the queries in the past, get them assigned again
  • :-) Get login from MyUMBC portal to work.
  • :-) Edit correct Global variables through web interface
    • :-) $PD_strict_path variable on; this assures that users across tree nodes (MATH, ADPS) cannot see other documents in other tree nodes.

After Live Switch Over To-Do

  • Harden and restrict the server by ridding of excess cron processes and scripts; see /etc/conr.hourly/ /etc/cron.daily/ /etc/cron.weekly/ etc
  • Move server behind firewall.
  • Modify workflow autostart queries so that they work optimally
    • rid of other documents types when not needed
    • rid of non needed checks for status
    • fix references to tracks in query logic (only some programs seperate by tracks)
    • Consolidate Auto Start Workflow Queries to be all in one query instead of in 3
  • Provide user training class(es) for GPC and GPD users. Reserve a lab and do it in there? Volunteer to come or force them to come?
  • Discuss possibility of ending faxing of decision sheets. Could Decision sheets come in pre-filled?
  • Install Nagios client / plugins for monitoring of the servers stats. See here for explanation of what Nagios does.
  • EDI DE fix. Everything that should be EDI_DE is being scanned into EDI. We need to discuss how the users use the system, what the true layout of our business is, and then how it should be setup. Also talk about how it may change in the near future. This group alone contains 40% of our workflow errors.
    • :-) It should be scanning into EDI group and tree nodes. Collegenet imports need to be fixed.
    • It should be modified in Paradocs Tables Access database as prog and path == EDI.
    • It should be added to workflow as EDI_DE.
  • Decide what to do with old server; talk to Steven Ostrove in OIT
  • Decision Sheet can be done with a new document type that is just a profile form. You can customize the form using “New Profile Limits”.
  • Use Auto number to assign 90101 SSNs?
  • :-?Better auditing of workflows. In an ideal world, all incoming documents go to a workflow, to the correct group, and show up. In the real world 5% of our documents may be getting lost, not showing up, mis-coded, etc. We need to discuss wide-reaching solutions.
    • I gave up on this. We need another employee that did document checking and root cause analysis and fixing, but management has given no absolute response
  • :-) Clean out old deleted queries in Stored Query Manager
  • :-) user ‘ugdata1’ queries are messed up. They are not returning results.
    • Most of the ugdata queries are graduate style queries on graduate documents which are not seeable by ugdata users
  • :-) In tree configuration, make sure that all existing groups(programs) are under Graduate Admissions
  • :-) Change user queries so that they “Link Identical Profile Fields across DocTypes”
  • :-) ‘Reboot on power-on’ option turned on in BIOS
    • must be on, machine reboots fine
  • :-) Learn how to access machine (su access) and document it
    • ssh gsdocs.umbc.edu, su -

Backend custom data links and operations

Status By Date

Status Log - A log in timeline fashion of major happenings and updates during the upgrade

 
systems/paradocs/server_upgrade.txt · Last modified: 12.07.2006 18:50 by 130.85.181.153
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki