1. From Client Server to WEB Rizwan Akhtar Tangible Technologies 703-568-3702 rakhtar@tangible-tech.com

2. What we will discuss today ► Developer/2000 Client Server Components and their integration ► Migration from Client Server to Web. ► Integration of Developer/2000 components in Web environment.

3. Developer/2000 Client/Server runtime installation 8i Database Server File Server with Application and Devloper/2000 runtime installed Client machine with registry entries Three tier Client/Server Database ServerDeveloper/2000 runtime installed 8i Two tier Client/Server

4. Client Server Deployment Issues ► Not available from every where ► Individual Client machine installation and configuration required ► Updates have to be propagated to all Client machines. ► Memory requirement for Client Machines are generally higher to run Developer/2000 Application

5. Web Forms Are we there yet ? ► Forms Server under 9 IAS is much more reliable “now” ► Client Server forms and reports can be deployed as is (one set of runtime)* ► SSL can be implemented with the use of Forms Servlet ► Newer versions of IE and Netscape are much more reliable. ► Use of Forms Servlet instead of Forms CGI is more memory efficient. ► Hardware to support a heavy middle tier machine has become more affordable *Key mapping for runtime and.gif icons needed

6. 9 IAS Forms and Reports WEB Server 8i Database Server Client machine Oracle Jinitiator on IE or Netscape 9IAS Application Server running Forms Listener Servlet 9 IAS Application Server running Oracle Reports Server 9 IAS

7. Oracle 9IAS Application Server ► Oracle HTTP Server powered by Apache ► Oracle 9i Portal and Portal to Go ► Oracle 9i Developer Forms and Report Services ► Oracle 9i Web Cache ► Oracle 9i Database Cache

8. Oracle 9i Developer Forms and Reports Services ► Oracle Developer Forms Server  Forms CGI (Pre Oracle Forms 6i Patch3)  Forms ListenerServlet ► The ListenerServlet enables Webforms to maintain the connections between Forms Java Applet and Forms Web Runtime through the standard Apache web server port ► Oracle Developer Reports Server  Reports CGI  Reports ListenerServlet (to be supported soon) ► Oracle JInitiator or JVM on IE 5.0 and above ► Oracle HTTP listener powered by Apache

9. Installation ► Oracle 9IAS Enterprise Edition ► Separate Oracle Homes for the Database and Oracle 9IAS Application Server  Isuites (IAS Home)  Oracle_806 (Developer Home)  OraHome81 if same machine for DB ► Customize configuration files

10. Apache Configuration Files ► httpd.conf  Main Apache server configuration file. HTTP listener's settings such as directory mappings, protection, SSL, ports, hostname & domains, etc. ► oracle_apache.conf  Included in httpd.conf to bind other IAS configuration files. It contains includes to other configuration files. ► 6iserver.conf  6i configuration file for Apache listener. It is read when the Apache listener starts. Included in oracle_apache.conf. ► jserv.conf  Directives for Jserv module. Included by httpd.conf ► ApJServManual auto ► ApJServProperties "C:\ORACLE\iSuites\Apache\Jserv\conf\jserv.properties" ► plsql.conf  Directives for mod_plsql, such as virtual paths handled by mod_plsql. This file is Included by oracle_apache.conf file. ► Reference  http://httpd.apache.org/docs/ http://httpd.apache.org/docs/

11. ListenerServlet Configuration ► zone.properties  Each servlet has his own properties file, known as zone.properties. The zone property file contain settings specific to a single servlet zone ► repositories=DEVELOPER_HOME\forms60\java\f60srv.jar ► f60listener.servlet.f60listener.code=oracle.forms.servlet.ListenerServlet ► More documentation at http://java.apache.org/jserv/zones.html http://java.apache.org/jserv/zones.html ► jserv.properties  Main configuration file for Jserv engine. This file contains properties passed to the JVM and a list of servlet zones and their property files. ► wrapper.path=IAS_HOME\bin;DEVELOPER_HOME\bin;C:\winnt;C:\winnt\system32 ► wrapper.env=PATH=IAS_HOME\bin;DEVELOPER_HOME\bin;C:\winnt;C:\ ► change the line wrapper.env=ORACLE_HOME=IASHOME to wrapper.env=ORACLE_HOME=DEVELOPERHOME ► basejini.htm  Default base HTML file to run a form on the web using JInitiator-Style tags to include the Forms applet. This file takes its input from formsweb.cfg ► formsweb.cfg  Parameter file used by when initiating web connection to run a form. These parameters will replace the ones in base.htm or basejini.htm. Modify this file to tailor the html page used to start your forms application. Key parameters are  serverURL=“http://hostname:port/servlets/f60listenenr”  connectMode=“http”  jinit_download_page=/jinitiator/us/jinit_download.htm ► URL to call web forms  http://hostname:port/dev60cgi/ifcgi60.exe?form=test.fmx http://hostname:port/dev60cgi/ifcgi60.exe?form=test.fmx  http://hostname:port/dev60cgi/ifcgi60.exe?config=swp_win http://hostname:port/dev60cgi/ifcgi60.exe?config=swp_win  http://hostname:port/dev60cgi/ifcgi60.exe http://hostname:port/dev60cgi/ifcgi60.exe

12. Compatibility Issues ► IE 4.0 or higher or Netscape 4.7 or below recommended. Netscape 6.0 or higher not supported ► JIntiator 1.8.0.0 or higher required with FormsServlet ► JVM (Java Virtual Machine) only works with IE  http://hostname:port/dev60cgi/ifcgi60.exe?confi g=IE50native http://hostname:port/dev60cgi/ifcgi60.exe?confi g=IE50native http://hostname:port/dev60cgi/ifcgi60.exe?confi g=IE50native

15. Reports Server Configuration ► Install Reports Server as a service using “rwmts60.exe -install tcpip “ ►.ora created under [Oracle Developer_Home\reports60\server ► Modify tnsnames.ora on the reports server machine ► = ( ADDRESS= (PROTOCOL=TCP) (HOST= ) (PORT= )) ► REPORTS60_PATH on the reports server machine must be set to the directory containing reports.

16. Oracle Reports Integration ► Run_product  Can only be used in a client server environment  Cannot take advantage of the report server  Is going to be obsolete soon ► Run_report_object  Can be used in a client server environment or web environment to integrate forms with report  Takes advantage of the reports server  Can be used to deploy reports on the web when coupled with web.show_document  Cannot be used on the web to display the reports parameter window ► Rwcli60.exe  Used from command line to a call a report with command line parameters ► Rwcgi60.exe  Uses report server  Can be used to run reports on the web when used in a URL ► http://mymachine.domain/dev60cgi/rwcgi60.exe?server=rep_server+report=test.rep+para mform=html+destype=cache+desformat=pdf

18. Other Helpful Commands ► GET_APPLICATION_PROPERTY(USER_INTERFACE)  Returns “web” or “win32” depending on the environment ► Web.show_document  Forms built that can be used to call any web page from within a PL/SQL trigger ► Web.show_document(http://www.yahoo.com) http://www.yahoo.com ► Web.show_document(“http://mymachine.domain/dev60cgi/rwcgi60.ex e?server=rep_server+report=test.rep+paramform=html+destype=cac he+desformat=pdf”);

19. Questions