Oracle A54857-03 - Manual (Page 64)

7-6 Oracle Web Application Server™ Installation Guide
1. The upgrade tool updates the [DynApps] section to Web Application
Server 3.0.1.
In WebServer 2.0, the section is:
[DynApps]
%ORACLE_HOME%/ows2/lib/libndwll.so ndwlld_DynamicInit
%ORACLE_HOME%/ows2/lib/ndwrd.so sndwrdini_init
%ORACLE_HOME%/ows2/lib/ndwp.so ndwp_dinit
In WebServer 2.1, the section is:
[DynApps]
%ORACLE_HOME%/ows21/lib/ndwfss.so oracle_adp_init
The upgrade tool will update the entry to:
[DynApps]
%ORAWEB_HOME%/lib/libwrl.so oracle_adp_init
2. The upgrade tool updates the svserver_name.cfg from Oracle 1.2 format to
2.1 format.
Merge WebServer 2.x sv server_name.app into Web Application Server 3.0.1 wrb.app
In Web Application Server 3.0.1 there is only one wrb.app file that stores the
cartridge application related information, as opposed to one svserver.app per
listener in Oracle WebServer 2.x.
The upgrade tool does not alter default cartridges such as JAVA, Live HTML,
PL/SQL and HELLO in the Web Application Server 3.0.1 wrb.app file, which
allows you to use the Web Application Server 3.0.1 default cartridges after the
upgrade.
The upgrade tool updates JAVA settings such as CLASSPATH and
LD_LIBRARY_PATH. The JAVA settings CLASSPATH and
LD_LIBRARY_PATH are found in WebServer 2.x svserver.app and are
appended into Web Application Server 3.0.1 wrb.app’s JAVA setting. After this,
the upgrade tool detects conflicts in:
• user-defined cartridges in the [Apps] section of svserver.app
• application directory mapping in the [AppDirs] section of the svserver.app
• cartridge section parameters and application protection in the
[AppsProtection] section of the svserver.app
It also indicates conflicts between the WebServer 2.x svserver.app and Web
Application Server 3.0.1 wrb.app by showing the conflicts in table format before
it merges svserver.app into wrb.app.