QUICK LINKS

Support
Issue Tracker
[Services]
Questions
[uAchieve 4.5 Applications]
[uAchieve 5.0 Application]
[uAchieve 5.1 Application]
Transferology
TES
[Training & Conferences]
Accessibility

Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Home page for the PeopleSoft - Transfer Rule extractor

T-Rex will remove the need for PeopleSoft schools to provide transfer rule flat file imports and work through the import process with Halena. Subscribing schools using the flat file import are only allowed two imports per year and must resolve the error/validation issues identified by Halena during the import file vetting stages.

T-Rex goals

  1. Keep the remote Extractor as light as possible.
  2. Provide necessary compatibility for various PeopleSoft releases.
  3. Make the install/configuration, at the school, as simple as possible.
  4. Automate a weekly transfer rule extract, and data send to CollegeSource.
  5. Lab allows PeopleSoft schools to define necessary mappings/translations (i.e. source or send departments, school identifiers, etc.). This is a key element in ensuring weekly automation while eliminating the need for school specific customizations to the codebase.
  6. Provide configurable logging to facilitate troubleshooting when support questions/issues arise.
  7. Facilitate use of extracted data by TFO and TES.

 

We believe the above goals are satisfied by the following solution components:

  • Java program to perform weekly transfer rule extract, and data send to CollegeSource.
  • Provide PeopleSoft schools with downloadable zip file and installation instructions.
  • The zip file contains:
    • Several shell/batch scripts
    • A sub directory with the necessary java libraries
    • An extractor.properties file for configuration
  • Installation requires school to schedule the weekly extract and send process via their preferred platform scheduling service (cron, FireDaemon, etc.)

Milestones for Brett

  1. Review current CSI usage of PeopleSoft database tables. The sub items identify several important, open questions, but most likely not all relevant questions.
    1. What are the things we don't yet know, that we don't know?
    2. Are we using the correct PeopleSoft database tables?
    3. Are other PeopleSoft database tables more appropriate?
    4. Since PeopleSoft versions 8.9 and 9.0 have PeopleSoft database table changes occurred which we must account for?
    5. Since PeopleSoft versions 8.9 and 9.0 have PeopleSoft database table changes occurred which we should account for?
    6. Are there occasional school data customizations in the identified PeopleSoft database tables which may be problematic?
    7. Are there other things we don't know?
    8. Is there a different table access approach we should consider?
    9. Review the significant SQL WHERE clauses in use and recommend any revisions.
  2. Provide relevant information regarding PeopleSoft's transfer rule changes since V8.9 along with future PeopleSoft directions which impact this project.
  3. Identify the high level details of an alternative all PeopleSoft approach.
    1. What are the elements/components of the proposed all PeopleSoft approach?
    2. What are the advantages of the proposed all PeopleSoft approach?
  4. Use Brett's Findings and Recommendations to provide document detailing findings, answers, concerns and recommendations.
  5. Participate in wrap-up meeting to review the Findings and Recommendations.

Test Database

PeopleSoft Missouri TEST database

origin.jdbc.url=jdbc:oracle:thin:@192.168.20.181:1521:db11g
origin.jdbc.username=PS_89_UM
origin.jdbc.password=olddb2015

  • No labels