Chapter 6: Deploying Oracle Tools to the Web

Overview

A book with Oracle Web Development in the title would be of use mainly as a paperweight if it didn t discuss the issues and methods surrounding deploying and running applications over the Web. Up until this point, we have looked at development tools that were not specifically created for the development of web-enabled applications (IV, which discuss Oracle Portal and Java respectively, will discuss development environments that have their basis in web deployment). This potential limitation is mitigated by the advanced features of Oracle Application Server 10 g that provide developers and administrators the ability to serve these components over the Web in an environment that is secure, stable, and scalable. This chapter will discuss techniques for deploying these components in such a way as to minimize the impact of moving to a deployment architecture that is fundamentally different from the client/server architecture you may be accustomed to. As we will see, Oracle has made a great effort to make the transition of these legacy applications to the Web simple, while giving developers and administrators all of the benefits of web-based applications.

Note  

It is important to note that when discussing web applications in this chapter, we are referring to intranet-based or extranet-based web applications. Due to performance, download times, footprint, and JInitiator requirements, it is not practical to deploy these applications in an Internet environment.

Note  

In this chapter, Form(s) with a capital F refers to the form(s) developed with the Oracle Forms Builder tool that comes as part of the Oracle Development Suite as opposed to an HTML form, and Report(s) with a capital R refers to reports developed with Oracle Reports .

If Oracle provides environments such as Oracle Portal and tools such as JDeveloper that have their basis in web deployments, why even bother with tools such as Oracle Forms, Oracle Reports, and Oracle Discoverer? There are many reasons for this (discussed in the appropriate chapters), but some of the prevalent reasons include:

  • Legacy applications and legacy knowledge. The move to the Web greatly decreases administration costs, particularly for large installations where many users are spread over a large distance. Keeping the client machines (which probably have different versions of operating systems, different service packs , etc.) consistent enough to allow all of them to run Oracle s tools (Forms runtime, Discoverer Desktop, etc.) can be daunting at best and impossible at worst. Moving applications to the Web allows system administrators to simplify their deployment environments, but does your organization have the resources to rewrite all of your applications in a web-based tool such as Oracle Portal or Java? Most organizations will not take on the task of rewriting all of the applications that drive their business for the Web. In many organizations, the knowledge regarding the business rules and practices of the organization has been accumulated by developers that do not have the skills in Oracle Portal or Java to translate those business rules into web-based applications quickly without a significant investment in training.

  • Tool feature set incompatibilities and complexity. Oracle Portal has wizards that allow the development of forms and reports, but these Portal components do not have all of the functionality of the respective Oracle Forms and Oracle Reports products. Oracle JDeveloper 10 g allows complete control of all aspects of your application, but has a much higher learning curve.

  • Impedance mismatch. This term refers to the inherent difficulties between working with an object-oriented language such as Java and the relational aspects of a relational database such as Oracle. Oracle provides an extremely robust tool called TopLink that simplifies and eliminates many of the barriers of communication between Java and Oracle, but it is one more tool that your developers will need to be trained on.

In Chapter 1, we discussed the different types of Oracle Application Server 10 g installations. You will recall that there were three different types of installations:

  • J2EE and Web Cache Provides a HyperText Transfer Protocol (HTTP) server and Oracle Application Server Containers for J2EE (OC4J) containers for the deployment of Java applications.

  • Portal and Wireless Provides all of the components in the J2EE and Web Cache installation plus support for wireless devices and the Oracle Portal environment.

  • Business Intelligence and Forms Includes support for serving Oracle Forms, Oracle Reports, and Oracle Discoverer workbooks and worksheets over the Web. This chapter focuses on the Business Intelligence and Forms features of Oracle Application Server 10 g .

In Chapter 14). There are many issues when moving these components to the Web, not the least of which is the fundamental architecture change from client/server to web deployment. This chapter addresses the major issues and provides a road map for a seamless transition of Oracle Forms, Reports, and Discoverer workbooks and worksheets to the Web.



Oracle Application Server 10g Web Development
Oracle Application Server 10g Web Development (Oracle Press)
ISBN: 0072255110
EAN: 2147483647
Year: 2004
Pages: 192

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net