1 / 17

Survivable Network Analysis

Survivable Network Analysis. Oracle Financial Management Services Ali Ardalan Qianming “Michelle” Chen Yi Hu Jason Milletary Jian Song. FMS Mission Overview. Provide financial service applications Core Financial Applications Self Service Web Applications

irma
Télécharger la présentation

Survivable Network Analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Survivable Network Analysis Oracle Financial Management Services Ali Ardalan Qianming “Michelle” Chen Yi Hu Jason Milletary Jian Song

  2. FMS Mission Overview • Provide financial service applications • Core Financial Applications • Self Service Web Applications • Application Desktop Integrator Applications • Integrate feeder systems • Facilitate billing, reporting, reconciliation

  3. FMP Deployment Requirements • Support all major campus desktop platforms • Achieve excellent performance on all platforms • Implement a ‘thin client’ • Minimize software installation, distribution and maintenance • Leverage existing infrastructure • Mitigate any/all security risks

  4. Users • Casual users • Expense reports, purchasing • Self-service web application • Fulltime users • Business managers, accountants • Desktop applications • Feeder systems • Payroll, grants management, charge back systems

  5. System Architecture

  6. Data Processing Layer • System core layer • Oracle database • Accompanied with concurrent processing and administration Servers • Offsite machine to serve as backup • Data mirrored every 5 minutes

  7. Physical Layout Production Server Disaster/Recovery Machine Fiber link to campus Development Server Cyert Hall Machine Room 6555 Penn Ave

  8. Application Layer • Intermediate layer • Includes forms, web, and application servers. • Provides different forms of data presentation to work with diverse applications

  9. Desktop Client Layer • Customer front-end • Includes all major campus desktop users • ‘Thin client’ • Supports multiple platforms • Microsoft, Mac and Unix

  10. System Impact • Uptime is not mission-critical • Switchover to backup machine comes at a cost of 2 days • Feeder systems will function on their own • Most affected • General ledger • Billing/invoice generation

  11. Existing Security Measures • Secure Socket Layer (SSL) for transmission of sensitive data • Secure Shell (SSH) access • Kerberos identification • Separate realm • Firewall • Disaster/Recovery plan • Piecemeal components

  12. Policies and Practices • Internal • Promote knowledge transfer • Access policies • External • Departmental contact responsible for assigning rights and privileges within department • Heavy reliance on campus-wide policy regarding appropriate use of computing resources

  13. Team Activities • Weekly meeting • Evaluating progress and milestone • Assigning tasks to team members • Planning for the next step • Analytical sessions • Analyzing system architecture and components

  14. Next Step • Next joint meeting on October 10 • Essential service and asset selection • Scenario traces and components • Document request and gathering • Disaster/Recovery Plan • Security Policies • Oracle Application Integration Methodology • Field trip to the off-site data center

  15. Client Meetings 9/25 Preliminary Meeting 10/10 Meeting # 2 (11/6-11/9) Meeting # 3 (11/27-11/29) Meeting # 4 Presentations 9/28 Preliminary Presentation 11/2 Presentation # 2 11/14 Presentation # 3 12/5 Presentation # 4 Project Timeline & Milestones Team Meetings - Tuesdays 8:30 - 10:30pm & Sundays 2:00 - 4:00pm

  16. Project Timeline SNA Phase I. II. III. IV. Meeting #1 Presentation #1 Meeting #2 Presentation #2 Meeting #3 Presentation #3 Meeting #4 Final Presentation September October November December

  17. Project Client Contacts Primary Contact • Mary Ann Carr, Director of Administrative Computing • Business Needs, Policy Issues, Documentation, Direction Secondary Contacts • Bob Rittager, Development Team Leader • Security Issues, Integration, Roles & Responsibilities • Brian Gallew, • System Administration, Hardware, Disaster Recovery, Security • Massimo Bigliardo, Database Admin. • Database Administration, Software

More Related