Oracle Application Server
Successful businesses know that presenting their data in a timely and meaningful way provides a powerful advantage over the competition. To that end, businesses continue to need ever-more-powerful tools for producing high-quality reports from the masses of disparate data sources kept in every major corporation today.
For many years, Oracle Reports has maintained its position as the premier reporting tool for Oracle databases by keeping pace with rapid shifts in technology. As rapidly as technology has shifted, Oracle Reports has moved from character-based, to graphical-based, to client/server, and now to multi-tier Web-based development and deployment.
Oracle Reports has always been the reporting tool for use in conjunction with an Oracle database. But, until now, companies found it difficult to retrieve data outside a relational database.
Now Oracle Reports fills this gap and enables you to combine multiple sources of data into a single published source�a truly universal publishing solution. Oracle Reports makes publishing information easy by allowing you to access any data , and publish it in any format , anywhere !
You can find more information about these exciting new features in Oracle Reports in the �Oracle Reports New Features� whitepaper available or the Oracle Reports Data Sheet on OTN (/products/reports).
Development of Oracle Reports requires the licensing of Oracle Developer Suite which includes the Oracle Reports Developer.
Deployment of Oracle Reports requires the licensing of Oracle Application Server. You must have a licensed version of Oracle Application Server to deploy Oracle Reports even if you plan on using a third party Application Server.
This paper covers our direction with Oracle Reports and is divided into two sections:
· Section 1 - Deprecated functionality
· Section 2 - Obsolete Functionality
Oracle Reports 6i is the last version of Oracle Reports to support both a character-mode and a client/server GUI reports viewer. Oracle will support Oracle Reports 6i until December 2003, with extended support available till 2005.. These dates are based on the obsolescence of some underlying component of Oracle Reports 6i relies upon, including operating systems.
For customers using Oracle Forms 6 i, to call Oracle Reports, the only change necessary will be to update the Form from using run_product to run_report_object, since Oracle Reports now runs all reports through the Oracle AS Reports Services.
Client/server customers wishing to stay with Oracle Forms 6i and Oracle Reports 6i after December 2003 will have extended support mode only until 2005 at which time support for Oracle Reports 6i will cease. At this point, customers may continue to run their applications in an unsupported mode or choose to migrate to the latest version of the Oracle Forms and Oracle Reports.
We hope that this document provides you with the information necessary to prepare for your future reporting needs using Oracle Reports. As always, we are interested in your feedback pertaining to Oracle Reports and our obsolescence plan. Please email your comments to firstname.lastname@example.org.
Section 1 deprecated* functionality in Oracle Reports
*The functionality is no longer documented and its use is discouraged, as it will be dropped in a subsequent release. However, most existing applications using this functionality will continue to run without modification.
As with any product, time takes its toll on the usefulness of technology. This section lists those functions that have reached a point where they no longer contribute significantly to the usefulness of the tool, and alerts you to functions that are no longer documented. Their use is discouraged, as they will be dropped in a subsequent release of Oracle Reports.
· User Exits/Call Interface
· Command line options
· SRW.SET_ATTR built-in
· Miscellaneous built-ins
· Miscellaneous items
A user exit is a call to an external function that is executed within Oracle Reports. One of the issues with User Exits is the need to remake the executables to link in all the User Exits. This makes troubleshooting and upgrades to the product very difficult. In Oracle Reports, you can call Java methods using the ORA_JAVA package and the Java importer. This reduces the need to have User Exits in a report and allows for a more open and portable deployment. You may also use the ORA_FFI package, which provides a foreign function interface for invoking C functions in a dynamic library. With the availability of these new built-ins, the use of User Exits is discouraged in Oracle Reports , though makefiles will still be supplied to permit you to continue to work with existing User Exits.
User Exit built-ins
rwcgi.exe (Win32) and rwcgi(UNIX) - Moving away from using Common Gateway Interface (CGI), which will no longer be supported after Oracle Reports. Use Servlet or JSP instead.
Command line options
The srw.set_attr function was originally designed to save time and resources by changing attributes within a single built-in function. Over time, each of these functions has become a separate built-in. The srw.set_attr functionality has remained for compatibility, but has been documented as a non-recommended approach; we recommend that you use the newer built-in specified in the following table. Here is an example of srw.set_attr:
If :sal > 2000 then srw.attr.mask := srw.face_attr + srw.sz_attr + srw.weight_attr + srw.style_attr + srw.gcolor_attr; srw.attr.face := �times�; srw.attr.sz := 18; srw.attr.weight := srw.bold_weight; srw.attr.style := srw.underline_style; srw.attr.gcolor := �blue�; srw.set_attr(0, srw.attr); end if; RETURN (TRUE);
The following code performs the function as the above without using srw.set_attr:
If :sal > 2000 then srw.set_font_face(�times�); srw.set_font_size(18); srw.set_font_weight(srw.bold_weight); srw.set_font_style(srw.underline_style); srw.set_text_color(�blue�) end if; RETURN (TRUE);
The following table lists other deprecated functionality for built-ins.
Section 2 Obsolete features in Oracle Reports
This section describes items removed from Oracle Reports. By continuing to remove obsolete functionality (and replacing it with new technology), Oracle Reports ensures that our customers have the functionality they need for successful e-Business development and deployment. These changes are consistent with moving away from the client/server model and towards Web-based deployment.
rwrun60c executable (UNIX) � Character-Mode Runtime/Viewer
Oracle Reports no longer includes the special character mode runtime user interface executable (rwrun60c), which was specific to the UNIX operating system.
Note that character-mode reports can still be designed in Reports Builder and character- mode output produced with Oracle Reports by using rwrun.exe with the mode=character option on the command line.
Client/server user interface (GUI) for Reports Runtime (rwrun) executable
In Oracle Reports, the runtime executable (rwrun.exe) no longer displays the Parameter Form or screen preview (i.e., no graphical user interface for client/server reports). If the report contains parameters, they must be passed on the command line. If the paramform=yes command line is used, it will be ignored. If the destype=preview parameter is used, an error will be generated stating that this format is no longer supported. This makes rwrun.exe equivalent in functionality to rwclient.exe (i.e., it will run the report through the Reports Server instead of directly calling a Reports engine). You can still use rwrun.exe to send the output to the file, printer, or other supported formats.
In Oracle Reports , all reports are run through Oracle AS Reports Services. This allows you to take full advantage of the Reports Server for security and distribution functionality. It also allows for a more streamlined architecture and consistency within the product.
Oracle Reports will supply a mechanism that allows users running Oracle Forms 6i applications to use the Oracle Reports Services. To leverage this service from within Forms it is required to use the run_report_object instead of run_product for running reports. Further information can be found on the Oracle Technology Network () in the Forms Reports integration paper.
Oracle Graphics is no longer used to create charts in Oracle Reports. Instead, Oracle Reports uses a new Graph Wizard, which will offer a much greater selection of graph types as well as more control over the look and feel of the graph directly from within Reports Builder.
Existing 6i reports containing Oracle Graphics charts will execute under Oracle Reports, but will require a 6i installation of Oracle Graphics on the same machine in a separate ORACLE_HOME. This functionality will remain only for the Oracle Reports release. We strongly suggest that all Oracle Graphics objects be recreated using the new Graph Wizard.
Because of the underlying technology, there is no migration path or conversion mechanism available to convert Oracle Graphics charts to the new Graph Wizard format.
Oracle Graphics executables will not be shipped with Oracle Reports:
Executables no longer available in Oracle Reports
Changes to the Batch and Background command line options