Oracle Http Server in the Oracle Database has the following changes: 1. The maximum number of Apache Jserve processes supported by Apache Jserve Server has increased from Apache's default maximum value 25 to the maximum 128, this value is not real-time configuration. Second, JDK / JRE Certification Oracle is authenticated to establish and configure a Java application with the MOD_JSERV module using both JDK / JRE 1.2.2_01 and JDK / JRE 1.2.2_07. In version 9.2.0.1.0, all Java class libraries (such as BC4J, XDK) are loaded and compiled with JDK 1.1.8_10. These compile classes are authenticated in the version of Java JRE support, and they must be reheated. Third, the demand for module MOD_PLSQL uses the MOD_PLSQL module for a specific backend database, you need to manually install Oracle PL / SQL WEB Toolkit (OWA PL / SQL Packages) on a specific backend database. Owa Pl / SQL Packages should be installed in Sys database mode, make sure you only have it once. Note that the Oracle Application Server (OAS) user that already exists is migrated to Oracle HTTP Server, the old version of these packs must be replaced. For more information on the PL / SQL gateway in Oracle HTTP Server, please check http: //hostname.domain: Port / PLS / Admin_ / Title.htm. Fourth, restore the OWA package of the application server When you install a new MOD_PLSQL OWA package, they are placed in the Sys database user mode, which will bring problems with the Oracle Application Server, if they use the OAS PL / SQL CARTRIDGE component, You encounter these problems and want to continue using the OAS PL / SQL CARTRIDGE component, you must re-establish some synonyms, so that these synonyms refer to the OWA package. The steps to establish synonyms on the source database are as follows: 1. The SYS account is connected to the database 2 in SQL * Plus. Run the following command in SQL * Plus, which will delete all OWA publicity symbols established in the Oracle HTTP Server installation process.
drop public synonym OWA_CUSTOM; drop public synonym OWA_GLOBAL; drop public synonym OWA; drop public synonym HTF; drop public synonym HTP; drop public synonym OWA_COOKIE; drop public synonym OWA_IMAGE; drop public synonym OWA_OPT_LOCK; drop public synonym OWA_PATTERN; drop public synonym OWA_SEC; Drop public synonym owa_text; drop public synonym owa_util; drop public synonym owa_init; drop public synonym owa_cache; drop public synonym wpg_docload;
3. Connect to the OWA package installation mode OAS_PUBLIC, make sure the user has CREATE PUBLIC SYNONYM permissions, if not, you must do this to this user. 4. Run the following command. This will re-establish the OWA common synonym to refer to the OWA package of Oracle Application Server.
create public synonym OWA_CUSTOM for OWA_CUSTOM; create public synonym OWA_GLOBAL for OWA_CUSTOM; create public synonym OWA for OWA; create public synonym HTF for HTF; create public synonym HTP for HTP; create public synonym OWA_COOKIE for OWA_COOKIE; create public synonym OWA_IMAGE for OWA_IMAGE; create public synonym OWA_OPT_LOCK for OWA_OPT_LOCK; create public synonym OWA_PATTERN for OWA_PATTERN; create public synonym OWA_SEC for OWA_SEC; create public synonym OWA_TEXT for OWA_TEXT; create public synonym OWA_UTIL for OWA_UTIL; create public synonym OWA_INIT for OWA_CUSTOM; create public synonym OWA_CACHE for OWA_CACHE; create public Synynym WPG_DOCLOAD for WPG_DOCLOAD; 5. Preventing Oracle HTTP Server when reinstalling in the same Oracle home directory, confirming Httpd.conf, jserv.conf, zone.properties, and all you have changed Oracle HTTP Server configuration Document copy file. These profiles may be overwritten by news parts depending on the way you install Oracle9i. 6. Add memory for Apache JSERV applications if the Apache Jserve log file or browser reports "Out of Memory" because JVM memory overflows, which typically happens in the JVM. The steps of the maximum value of the memory pool allocated to the JVM are as follows: 1. Add a line in the file $ oracle_home / apache / jserv / etc / jserv.properties
Wrapper.bin.parameters = -mx
Wrapper.bin.parameters = -MX128M
2. Restart Web Server Seven, NLS Precautions 1. When mod_plsql is configured for mod_plsql, environment variable NLS_LANG is configured at each Web Server instance rather than in the DAD level configuration. Make sure that the environment variable NLS_LANG is configured correctly before starting your Oracle HTTP Server instance. 2. For Oracle PSP (PL / SQL Pages) For Oracle PSP, environment variables NLS_LANG must load PL / SQL Server Page (PSPS) to database configurations in using the LOADPSP command line program. 3. Using JDBC OCI8 drivers in JSERV and OracleJSP If you are connected to a database via a JDBC OCI8 drive, you need a suitable NLS_LANG setting in file jserv.properties. For example: wrapper.env = nls_lang = American_america.utf8 8. Configure the listener.ora file for EJBS in version 9.2.0.1.0, Oracle HTTP Server installation does not configure the listener.ora file to run Enterprise JavaBeans (EJBS), in order to run EJBS, you need to configure the listener.ora file: listener = (Description_List = (address_list = (address = = ipc))) (address_list = (address = (Protocol = IPC) (key = ICache))) (address = (protocol = TCP) (host =
