Transcript OSIRIS Client Support Issues A workshop for the ITSS Conference Niall Hedderley, MIS.

OSIRIS Client Support Issues
A workshop for the ITSS Conference
2002
Niall Hedderley, MIS
Objectives
• Background on OSIRIS
• Introduction to types of clients
• An overview of the client-side technical
support issues.
History
• Current Central Finance System: Prophecy
– Over 8 years old
– Support issues:
• Client rarely used for other purposes
• Printing issues
OSIRIS: Background
• OSIRIS
– Oxford Strategic Integrated Resource
Information System
• OSIRIS Project
– New technology
– Additional capabilities
– Re-working of operating practices
Server Side
• SunFire 4800 Database server
• Multiple SunFire 280R Application/frontend servers
• Off-site “hot spare” hardware
Types of Users
• Browser-based
– Majority of users
– Functions as (and beyond) Prophecy client
• Native Win32-based
– Minority of users
– Functions beyond existing facilities
Browser-Based Clients
• Browser versions:
– Netscape 4.x
– Internet Explorer 5.x
• Client platforms, recommended minimum:
– PC: 300MHz / 128MB
– Macintosh: 200MHz / 128 MB
– Display capable of 1024 x 768
• Java-based plug-in: Jinitiator
JInitiator
• Required for all browser access to OSIRIS
• Java-based browser plug-in
– Provides the presentation layer
– Java 2, JRE 1.3
– 40 bit RC4 encryption of data in transit
• Versions for Win32 and Macintosh
Browser-Based Client Issues
• Java plug-in versions:
– Will change over time
– Need to match database versions
• Network install issues:
– For speed, keep the plug-in local to the machine
Browser-Based Client Example
Win32 Clients
• Win32 Clients are not expected to be for all users
– More powerful reporting tools
– “desktop integration” tools
• Client Platforms, recommended minimum:
– 300 MHz / 128MB
– Windows NT or 2000
– “50MB RAM available and 230 MB disk space
available”
– 256MB suggested
Win32 Client Installation
• Install locations: Oracle Homes
– Acts as a installation root for a group of
applications
– Holds both programs and configuration
information
Win32 Client Configuration
• The TNSNAMES file
• Translates database names to access methods
• Applies to all applications in a Oracle Home
• Custom file: to be centrally supplied
Printing
• Majority of printing direct from browser or
Win32 client
• Some specialist printing may require
PostScript 3
Networking
• Bandwidth issues:
– Browser-based clients: Low
• Presentation layer from plug-in
– Native Win32 clients: Depending on demand
Routes to Help
• OSIRIS web pages
(www.admin.ox.ac.uk/finance/osiris)
• OSIRIS helpdesk
• Mailing lists
Timescales
• OSIRIS expected “go-live”:
February 2003
• Conference Room Pilots: Spring/Summer 2002
• IT Survey: Summer 2002
OSIRIS Client Support Issues
A workshop for the ITSS Conference
2002
Niall Hedderley, MIS