2. Application Migration

3. Application Migration Agenda Typical Client Applications JDeveloper Application Migration Assistant Typical Middleware and Access Methods used to connect to RDBMS Web Applications MS Access Applications Delphi Applications ESQL/C Applications

4. Application Migration Typical Client Applications Typical client software Visual Basic VC++ C# ESQL/C 4GL Access Delphi Web Applications Typical middleware ODBC ODBC + Access methods (DAO, RDO, ADO) OLE/DB.NET BDE

5. Application Migration JDeveloper Application Migration Assistant Identifies and allows easy navigation between statements in the code that may require modification to work on the Oracle platform. Analyzes complete projects or single files. Generates an Analysis Report that summarizes project statistics. Uses regular expressions in XML format that provide a search rule capability to identify issues Allows rules to be customized so you can augment the search capability

6. Application Migration ODBC drivers for Oracle Oracle ODBC www.oracle.com Microsoft ODBC www.eu.microsoft.com Datadirect ODBC www.datadirect.com

7. Application Migration Microsoft ODBC Less supported functionality than Oracle’s No Built-in Scrollable Cursor Support ResultSets supported via PL/SQL Indexed by Arrays only (non transparent support)

8. Application Migration Oracle ODBC Based on latest Oracle OCI Emulation capabilities Built-in Scroll Cursor ResultSets are supported transparently Supports an Array Interface Supports LOB

9. Application Migration Datadirect ODBC Built-in Scroll Cursor ResultSets supported transparently Full LOB Support Supports an Array Interface Additional cost

10. Application Migration ODBC Issues & parameters ODBC driver must support Oracle reference cursors if using stored Sub Programs with resultsets. Oracle and Datadirect ODBC driver do not require extra parameters for REF Cursors. ODBC PassThrough Mode will potentially require re-coding of SQL statements ODBC AutoCommit Parameter needs consideration ODBC array processing considerations Oracle ODBC Driver Rows Pre-Fetch parameter. HandoutHandout

11. Application Migration ODBC Example Our driver maps REF CURSORS to Result sets transparently, Using the same call against a SQL Server / Sybase TSQL Stored Sub Program And a converted Oracle PL/SQL Sub Program {call read_position (2)} HandoutHandout

12. Application Migration ODBC Extended SQL Syntax Use the ODBC extended SQL extensions to create generic SQL statements allows the ODBC driver to convert SQL syntax on the fly outer joins functions (date, time, timestamp,...) datatype conversions Oracle9i instroduces support for ANSI SQL including support for the CASE statement, ANSI compliant joins HandoutHandout

13. Application Migration ODBC extended SQL syntax select c.name, p.description from customer c left outer join product p on c.preferred_product = p.product_id select c.name, p.description from customer c left outer join product p on c.preferred_product = p.product_id select c.name, p.description from customer c, product p WHERE c.preferred_product = p.product_id(+) select c.name, p.description from customer c, product p WHERE c.preferred_product = p.product_id(+) select c.name, p.description from {oj customer c left outer join product p on c.preferred_product = p.product_id} select c.name, p.description from {oj customer c left outer join product p on c.preferred_product = p.product_id} SQL Server / Sybase Oracle ODBC extended syntax for outer joins HandoutHandout

14. Application Migration ODBC extended SQL syntax SELECT SUBSTRING(DESCRIPTION, 1, 5) FROM PRODUCT SELECT SUBSTR(DESCRIPTION, 1, 5) FROM PRODUCT SELECT {FN SUBSTRING (DESCRIPTION, 1, 5)} FROM PRODUCT SQL Server / Sybase Oracle ODBC extended syntax for scalar functions HandoutHandout

15. Application Migration ODBC extended SQL syntax SELECT CONVERT (CHAR, PRICE) FROM PRODUCT SELECT TO_CHAR (PRICE) FROM PRODUCT SELECT {FN CONVERT (PRICE, SQL_CHAR} FROM PRODUCT SQL Server / Sybase Oracle ODBC extended syntax for scaler fucntions (2) HandoutHandout

16. Application Migration ODBC extended SQL syntax SELECT * FROM ORDERS WHERE DEL_DATE > '1998-06-10' SELECT * FROM ORDERS WHERE DEL_DATE > TO_DATE('1998-06-10','YYYY-MM- DD') SELECT * FROM ORDERS WHERE DEL_DATE > {D ' 1998-06-15 ' } SQL Server / Sybase Oracle ODBC extended syntax for date functions SELECT * FROM ORDERS WHERE DEL_DATE > {TS ' 1999-01-17 13:00:00 ' } SELECT * FROM ORDERS WHERE DEL_DATE > {TS ' 1999-01-17 13:00:00 ' } N/A SELECT * FROM ORDERS WHERE DEL_DATE > TO_DATE('1999-01-17 13:00:00','YYYY-MM-DD HH24:MI:SS') SELECT * FROM ORDERS WHERE DEL_DATE > TO_DATE('1999-01-17 13:00:00','YYYY-MM-DD HH24:MI:SS') HandoutHandout

17. Application Migration Microsoft Access Methods - ODBC MS Access uses DAO only VB / SQL Server applications historically use RDO RDO cursor libraries provide support for scrolling cursors even if the ODBC driver does not (e.g. RDO client batch cursor library) make sure to select PK columns in the base SELECT statement ADO and.NET are the more recent access methods.

18. Oracle provides an OLE/DB provider with the same level of functionality as its ODBC driver OO4O is an OLE server providing full native support for Oracle (written ib OCI) Available through VB Object and VC++ Class Proprietary Interface Do not confuse OO4O and OLE/DB Application Migration Microsoft Access Methods – OLE/DB

19. Application Migration Microsoft Access Methods -.NET Oracle provides a.NET driver the ODP.Net XML Support Resultset Support Minor changes required to SQLHelper class.NET Developer Center http://www.oracle.com/technology/tech/dotnet/index.html Oracle Developer Tools for Visual Studio.NET

20. MS applications tend to use Active Server Pages on the client. ASPs tend to use ADO to communicate to the Database backend although.NET ODP is now becoming common. Can be easily migrated to use the Oracle OLE/DB provider behind ADO ODBC also possible via OLE/DB provider for ODBC Could leave as is or migrate to JSP (Java Server Pages). Application Migration Web Applications

21. Oracle9iAS Migration Kit for ASP Oracle9iAS Migration Kit for ASP (Active Server Pages) enables customers with Microsoft IIS/ASP applications, facing performance, scalability and reliability problems, to migrate to the Java 2 platform, Enterprise Edition (J2EE). Understanding that Microsoft customers have large investments in existing technology and personnel, Oracle provides a phased approach to migration, allowing customers to embrace, improve and finally replace the Microsoft technology stack. HandoutHandout

22. Oracle9iAS Migration Kit for ASP Embrace Deploy the ASP application to Oracle9iAS Implement Oracle9iAS Web Cache to speed the delivery of both static and dynamic content Choose your deployment platform: Windows, Linux, Solaris and many others supported by Oracle9iAS Improve Take advantage of Oracle specific technology not available from ASP applications Allow ASP applications to integrate with J2EE applications Replace Migrate ASP applications to JSP applications Customers are no longer reliant on any Microsoft technology HandoutHandout

23. Oracle9iAS Migration Kit for ASP Current release version 1.2 supports Embrace and Improve. Future release to support Replace phase. HandoutHandout

24. Migrate the structure and data of your Microsoft Access database(s) to an Oracle database Enable your unmodified Microsoft Access forms and reports to work with your Oracle database through an ODBC connection Avoid Attached Tables (DAO/Jet) for better performance ! Migrate both 16-bit Access 2.0 databases and 32- bit Access 7.0 databases Replaces the former Migration Assistant for MS Access Application Migration MS Access Applications HandoutHandout

25. Application Migration Delphi Applications Delphi 6 normally uses BDE Borland Database Engine (BDE) maps quite well to Oracle although performance is not good when run against >8i. Native access to Oracle should be used (e.g. CoreLab’s ODAC (http://www.crlab.com) (Oracle Data Access) – same as BDE but closer to Oracle (directly in OCI)S

26. Application Migration Delphi Applications Use the BDE with native Oracle Driver, ODAC (preferably) or ADO. Use local Schema Cache Define Rowsetsize to use Arrayinterface Object Names should be in capital Letters Use Varchar2 Datatype in the Database Not portable SQL needs to be changed Outer Joins Select List Subqueries … Null Value Handling needs be checked

27. Deployment Features Oracle IIS Proxy Plug-In Oracle Services for MTS Security Integration Directory Integration HandoutHandout

28. Common Deployment Scenarios HandoutHandout

29. Oracle 9iAS Proxy Plugin Goal Goals Enable customers to use IIS* or iPlanet with 9iAS No modifications to back-end applications HandoutHandout

30. Oracle 9iAS Proxy Plugin Features Converts IIS and iPlanet into reverse proxy servers URL partitioning to support multiple back-end servers Single Sign On Security support No application change required Certified with all Oracle 9iAS Release 2 components Licensing No additional cost for deployment Distributed on Integration CD and OTN HandoutHandout

31. Oracle 9iAS Proxy Plugin Architecture Firewall IIS plugin config /portal /ifs /j2ee.asp 9iAS - 1 9iAS - 2 9iAS - 3 OHS HandoutHandout

32. Proxy Plugin - Features Reverse Proxy Makes a HTTP v1.1 request of the backend server Sends the response - unaltered - to the requester Co-exist: Active Server Pages and J2EE apps Access both from the same corporate IIS listener Applies URL Name Space mapping Reads from configuration file at IIS startup Proxies to different servers based on configuration Multiple 9iAS Backends Beta / Production can be hosted from the same IIS HandoutHandout

33. Proxy Plug-in Security Features Single Sign On Integrates with Oracle 9iAS Release 2 SSO Server Makes IIS applications work with SSO too! All other backend 9iAS security mechanisms supported Client Information Client IP information forwarded to back-end 9iAS Client User Name information also forwarded Client Certificate information is not forwarded SSL Proxy plug-in uses http (not https) to Backend Server HandoutHandout

34. Deployment Features Oracle IIS Proxy Plug-In Oracle Services for MTS Security Integration Directory Integration HandoutHandout

35. Oracle Services for MTS Integrate Oracle databases with MS Distributed Transaction Coordinator (DTC) Oracle DB as resource manager in DTC transactions Oracle Services for MTS acts as a proxy between DTC and the Oracle DB OraMTS supports Oracle databases on any platform OraMTS itself runs on Windows HandoutHandout

36. Oracle Services for MTS OraMTS supported only by data access drivers provided by Oracle Supports OO4O, OCI, ADO/OLE DB, ODBC,.NET OO4O and OCI provide high performance, compatibility Transactional operations Enlistment and completion Recovery Connection pooling HandoutHandout

37. OraMTS Operations Enlistment Application requests that OraMTS enlist a connection OraMTS proxy joins transaction with DTC DTC generates transaction ID OraMTS starts Oracle global transaction Oracle uses transaction ID on connection HandoutHandout

38. OraMTS Operations Completion DTC calls proxy for two-phase commit operation Proxy relays commit operation to database Database performs commit operation Proxy relays outcome of commit operation to DTC DTC adjusts state of transaction (e.g. committed) HandoutHandout

39. OraMTS Operations Recovery Database recovery job checks for in-doubt transactions Recovery job requests outcome from recovery daemon through reenlistment Daemon queries DTC for outcome Recovery job commits/aborts the transaction HandoutHandout

40. OraMTS Architecture Architecture Each MTS instance has its own OraMTS instance No changes necessary for existing applications MTS/COM+ OraMTS integration layer RM proxy cache OraMTS recovery daemon OraMTS recovery job Oracle HandoutHandout

41. OraMTS Architecture Multiple proxies per database Higher performance, scalability, availability No single point of failure OraMTS X Proxy (A) Proxy (B) OraMTS Y Proxy (B) A B HandoutHandout

42. Oracle Services for MTS Optimizations Use a high-performing data access driver OCI is highest-performing Minimize use of Windows OS authentication Verifying Windows OS security credentials is resource intensive.NET support OraMTS can participate in transactions using any.NET programming language HandoutHandout

43. Deployment Features Oracle IIS Proxy Plug-In Oracle Services for MTS Security Integration Directory Integration HandoutHandout

44. Oracle wallets stored in Windows registry Improves security of wallets Oracle wallets in registry (user profile), rather than file system PKI single sign-on support with the registry Oracle Wallet Manager - encrypts Oracle Enterprise Login Assistant - decrypts Security Services Windows registry/AD Oracle wallet HandoutHandout

45. Security Services Microsoft Certificate Store integration Oracle PKI and Windows PKI interoperate Oracle and non-Oracle apps use common Windows PKI credentials Wallet Resource Locator sets usage Oracle PKI uses Microsoft CryptoAPI PKI operations: signing, encryption, decryption, verification, and validation Oracle PKI Windows PKI CryptoAPI HandoutHandout

46. Deployment Features Oracle IIS Proxy Plug-In Oracle Services for MTS Security Integration Directory Integration HandoutHandout

47. Directory Services Enterprise security using native authentication and Active Directory Single sign-on through Kerberos/NTLM native authentication Oracle enterprise users and roles stored in AD Increase scalability, reduce administrative overhead Map Windows users/OUs/domains (X.509) to global users in database Map Windows groups to enterprise roles Manage enterprise roles in AD through Enterprise Security Manager HandoutHandout

48. Directory Services Oracle Net naming with Active Directory Store and resolve Net names through AD Eliminate tnsnames.ora on clients Centralize configuration, reduce administration Register databases with AD (LDAP naming) Enhanced tools support for storing Net naming Windows Explorer, AD Users and Computers Oracle DB Configuration Assistant, Net Manager, Net Configuration Assistant HandoutHandout

49. Deployment Features Oracle IIS Proxy Plug-In Oracle Services for MTS Security Integration Directory Integration HandoutHandout

50. A Q & Q U E S T I O N S A N S W E R S