OZ zorgverzekeringen Financiële resultaten 2001

Optimising information flows: Migrating to the
SAS® Information Delivery Portal 2.0
SAS Forum,
Copenhagen, 17
Agenda
• Introduction
• Why should I use the Information Delivery Portal?
• Why should I choose Portal 2.0?
• Migration issues from Portal 1.x or SAS/Intrnet
• Conclusion
Introduction (1): OZ health insurance
• Medium size health insurance company
• Operating mainly in the southwestern part of the Netherlands
• Both public and private health insurance
• About 560.000 insurees in the public system and 35.000 in the
private insurance
• 650 Employees
Introduction (2): OZ and SAS
• Working with SAS since 1997
• Started with Base, SAS/Graph, SAS/Stat, SAS/Access and
SAS/Connect
• SAS/Intrnet since 2000
• SAS Information Delivery Portal since 2003
• SAS 9.1 and Portal 2.0 since 2004
Why should I use the Information Delivery Portal
• One (management)information channel
• Better manageable then lots of ‘loose’ SAS/Intrnet applications
• Integrated security model
• ‘Ease of use’ for the end-user
• Ability for the end-user to create his or her ‘own’ Portal
Why should I choose Portal 2.0? (1)
• Take full advantage of the new SAS 9.1 architecture
• Centrally registered metadata that can be used in for example EG
• Stored Processes made in EG are very easy to deploy in Portal
2.0 and register in the metadata-server
• Both JSP-application and Portlets created in AppDev are very
easy to deploy in Portal 2.0
• Enhanced security-model
Why should I choose Portal 2.0? (2)
• Improved look
-and-feel
look-and-feel
• For userauthentication, integration with the operating system
(amongst others) can be created
• Stored processes are very similar to SAS/Intrnet programs
because of streaming output
• The manageabilty is much better than it was in Portal 1.x
• The usability for the end-user is much greater
Migration issues(1): SAS/Intrnet to Portal 2.0
• Minor changes to the SAS-program
• Registration of the stored process in the metadata
-server
metadata-server
• Developing an input.jsp to let the user select the parameters for
the execution of the program
Migration issues (2): Portal 1.x to Portal 2.0
• Totally different concept of Portal 2.0
• Minor changes to the SAS-programs
• Semi-automatic registration of the portal users and their
permissions in the metadata-server
• Registration of all content (windows, links, stored processes etc.)
by hand in the metadata-server
Migration issues (3): Portal 1.x to Portal 2.0
• All access-control registrations by hand in the metadata-server
(based upon Access Control Templates)
Templates
• Developing new inputforms for stored processes that used the
default inputform
• Possible changes to existing JSP-applications
Conclusion
• Migration from portal 1.x to portal 2.0 must not be taken lightly
• Migration of SAS/Intrnet-applications to Portal 2.0 is pretty easy
• The advantages that come with Portal 2.0 and the SAS 9.1
infrastructure (especially the enhanced manageability, security
and usability) make it all worthwhile (in the end)
Contact
Erwin van Dongen
[email protected]
Paul Smeekens
[email protected]
More information:
http://support.sas.com/rnd/web/portal/index.html
http://support.sas.com/rnd/eai/index.html
Managementconsole: Stored process
Managementconsole: Access Control Template
Management Console: Register Stored Process
Portal 2.0: Editing a page
Portal 2.0: An input.jsp
Portal 2.0: The corresponding output
Portal 2.0: The homepage
Portal 2.0: Two different users
Portal 2.0: The concept
Cliënt pc
Cliënt pc
Webserver
Cliënt pc
Metadata server
Stored Process
Stored Process
Stored Process
WebDAV server
Stored Process Server