Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Grant KFS access to publish deployment objects into IET SVN (NEED JIRA TICKET for access setup)

Open Issues

  1. Person data - KFS needs to migrate out of KIM
    1. Direct deposit info
    2. Mailing addresses for check
  2. Sythentic keys
    1. Reserve block for manually created <10K
    2. >10k for programatic
    3. May need to bump that 10k number up to leave enough room
    4. AI: Move to 100k (NEED JIRA TICKET)

Process

  1. KFS: CMF # / Version #
  2. Migration program can push things into tag area where only migrators have access - purge from trunk once migrate
  3. Migration #
  4. KFS = Test Long term, KFS TST would use Rice dev-int
    1. KFS TST refreshed weekly
  5. KFS QA = Rice Test
    1. Bring up as first integration - Since Rice Dev-Int will be live Jan 4, we should point KFS-QA to RICE-DEV-INT.
  6. Lockdown SVN to each application (read/write access)
  7. Use XML poller service (XMLPollerLifeCycle) - XML ingester
    1. dev.mode off
    2. Import XML workflows via polling processes
    3. Background process run as system user
    4. 3 dir structure: Pending, Processed, Failed
      1. Runs in file system alphabetical order
  8. Remote Identity Service
    1. TST/QA - Utilize KIM via KSB
  9. (NEED JONATHAN'S PICTURE OF WHITEBOARD)