Oracle9i Application Server Migrating from Oracle9iAS Release 1 (1.0.2.2.x) to Release 2 (9.0.2) Release 2 (9.0.2) for Windows NT/2000 Part Number A96157-02 |
|
This chapter explains how to change the necessary configuration files, application deployment files, and metadata schema in order to migrate Wireless components. It contains these sections:
This section provides instructions for migrating Oracle9iAS Wireless. The only supported migration path is from Oracle9iAS Wireless 1.0.2.2.0 (the most recent production version) to Release 2 (9.0.2).
Note: In the examples in this document, when a username and password are noted as orcladmin welcome1, these are the username and password supplied at the time of installation. |
The following modifications are required to migrate Oracle9iAS Wireless 1.0.2.2.0 to Release 2 (9.0.2).
Previously, the HTTP user agent header to logical device mapping was stored as a plain Java property file. In this release, the mapping is stored in the database. This information must be migrated from the Java property file to the database.
Because persistent representation between the transformer and logical device has been modified in Release 2 (9.0.2), a separate Java program is used to upgrade to the new table schema.
The site and node configuration properties stored in the Java property files in Oracle9iAS Wireless 1.0.2.2.0 should be migrated to the database.
User information stored in the panama
user table must be migrated to the OID.
This section explains how to migrate from Oracle9iAS Wireless Release 1 (1.0.2.2.0) to Oracle9iAS Wireless Release 2 (9.0.2). assuming that Release 2 (9.0.2) will always be installed in a different Oracle home from the prior Oracle 9iAS releases (a separate Oracle home is required for the new installation).
tnsnames.ora
) corresponding to the Oracle9iAS Wireless Release 1 (1.0.2.2.0) Repository database.
Before completing an in-place migration, you must delete the Wireless Provisioning Profile Entry.
The Wireless post-installer creates a provisioning profile entry pointing to a default Wireless schema in OID. For an in-place migration, this entry should be deleted by running the following script:
ORACLE_HOME/bin/oidprovtool operation=delete ldap_host=<ldap_host> ldap_ port=<ldap_port> ldap_user_dn='cn=orcladmin' ldap_user_password=<password of cn=orcladmin> application_ dn='orclApplicationCommonName=Wireless1, cn=Wireless, cn=Products,cn=OracleContext' organization_dn=<default subscriber dn>
For example:
oidprovtool operation=delete ldap_host=stpc497.us.oracle.com ldap_port=389 ldap_user_dn="cn=orcladmin"
ldap_user_password="welcome1"
application_dn="orclApplicationCommonName=Wireless1, cn=Wireless, cn=Products, cn=OracleContext" organization_dn="dc=stpc497, dc=com"
ORACLE_HOME_2\wireless\sql\aq_grants.sql
script.
The command syntax is:
sqlplus Adminuser/Adminpassword@SID @./aq_grants.sql ias10220_wireless_ schemaname
for example:
sqlplus system/manager@0817 @./aq_grants.sql ptg102_user
ptgUpgrade.bat
in the ORACLE_HOME_2\wireless\upgrade
directory, supplying the Oracle9iAS Wireless Release 1 (1.0.2.2.0) Oracle home, Oracle9iAS Wireless Release 1 (1.0.2.2.0) connect string, and Oracle9iAS Wireless Release 2 (9.0.2) Oracle home. For example:
The command syntax is:
ptgUpgrade.bat ORACLE_HOME_1 old connect string ORACLE_HOME_2 admin user admin password hostname port https port
for example:
ptgUpgrade.bat d:\wireless1022 ptg1022_user/ptg1022_ passwd@wirelessdbservicename d:\iasv2 orcladmin welcome1 iasv2.mydomain.com 7778 4444
Registrar.bat
script in Oracle9iAS Wireless Release 9.0.2 ORACLE_HOME_2\wireless\sample
directory as shown below.
portalRegistrar.bat ias_admin_user device_portal_url
for example:
portalRegistrar.bat orcladmin http://upgradedv2machine.mycompany.com:7777/ptg/rm
ORACLE_HOME_2\sysman\emd\targets.xml
to point to the newly upgraded database repository. Make the changes shown in bold to the target entry corresponding to oracle_wireless
.
<Property NAME="ConfigDBPort" VALUE="port number of upgraded database"/> <Property NAME="ConfigDBpassword" VALUE="schema password of upgraded database" ENCRYPTED="FALSE"/> <Property NAME="MachineName" VALUE="machine name of upgraded database"/> <Property NAME="ConfigDBSID" VALUE="SID of upgraded database"/> <Property NAME="ConfigDBMachineName" VALUE="machine name of upgraded database"/> <Property NAME="UserName" VALUE="schema name of upgraded database" ENCRYPTED="FALSE"/> <Property NAME="Port" VALUE="port number of upgraded database"/> <Property NAME="SID" VALUE="SID of upgraded database"/> <Property NAME="ConfigDBUserName" VALUE="schema name of upgraded database" ENCRYPTED="FALSE"/> <Property NAME="ORACLE_HOME" VALUE="no modification required"/> <Property NAME="password" VALUE="schema password of upgraded database" ENCRYPTED="FALSE"/> <Property NAME="host" VALUE="fully qualified host name of wireless middle tier"/>
If the Oracle9iAS Wireless Release 1 (1.0.2.2.0) installation is on computer mc1 (and its repository database is on db1) and the Oracle9iAS Wireless Release 2 (9.0.2) installation is on computer mc2 (and its repository database is on db2):
ORACLE_HOME_2\wireless\sql\aq_grants.sql
script.
The command syntax is:
sqlplus Adminuser/Adminpassword@SID @./aq_grants.sql ias10220_wireless_ schemaname
for example:
sqlplus system/manager@0817 @./aq_grants.sql ptg102_user
ORACLE_HOME
_1\panama\
from machine mc1 to a temporary directory (tmp
is used in this example), and modify the file
tmp\panama\server\classes\oracle\panama\spatial\spatial.properties
to replace the ORACLE_HOME_1
prefix for each property with the absolute path to the temporary directory.
For example, if the temporary directory was \tmp
, modify the file \tmp\panama\server\classes\oracle\panama\spatial\spatial.properties
to change entries of the form:
file.providers.config.xml.geocoding = \
ORACLE_HOME_ 1\panama\server\classes\oracle\panama\spatial\geocoder\Geocoders.xml
to the form:
file.providers.config.xml.geocoding = \
tmp\panama\server\classes\oracle\panama\spatial\geocoder Geocoders.xml
ptgUpgrade.bat
script, supplying the location of the copied temporary directory, the Oracle9iAS Wireless Release 1 (1.0.2.2.0) connect string, and the Oracle9iAS Wireless Release 2 (9.0.2) Oracle home. For example:
ptgUpgrade.bat d:\tmp ptg1022_user/ptg1022_passwd@wirelessdbservicename
d:\iasv2 orcladmin welcome1 iasv2.mydomain.com 7777 4443
Registrar.bat
script in Oracle9iAS Wireless Release 9.0.2 ORACLE_HOME\wireless\sample
directory as shown below.
portalRegistrar.bat ias_admin_user device_portal_url
for example:
portalRegistrar.bat orcladmin http://upgradedv2machine.mycompany.com:7777/ptg/rm
ORACLE_HOME_2\sysman\emd\targets.xml
, to make the following changes (in bold) to the target entry corresponding to oracle_wireless
.
<Property NAME="ConfigDBPort" VALUE="port number of upgraded database"/> <Property NAME="ConfigDBpassword" VALUE="schema password of upgraded database" ENCRYPTED="FALSE"/> <Property NAME="MachineName" VALUE="machine name of upgraded database"/> <Property NAME="ConfigDBSID" VALUE="SID of upgraded database"/> <Property NAME="ConfigDBMachineName" VALUE="machine name of upgraded database"/> <Property NAME="UserName" VALUE="schema name of upgraded database" ENCRYPTED="FALSE"/> <Property NAME="Port" VALUE="port number of upgraded database"/> <Property NAME="SID" VALUE="SID of upgraded database"/> <Property NAME="ConfigDBUserName" VALUE="schema name of upgraded database" ENCRYPTED="FALSE"/> <Property NAME="ORACLE_HOME" VALUE="no modification required"/> <Property NAME="password" VALUE="schema password of upgraded database" ENCRYPTED="FALSE"/> <Property NAME="host" VALUE="fully qualified host name of wireless middle tier"/>
Repository migration is required if you want to migrate data in the current database to the one installed as part of the Oracle9iAS Wireless Release 2 (9.0.2) Infrastructure tier. The current database will be no longer used after Repository migration.
exp
. For example:
exp system/manager owner=ptg102_user file=exported.dmp log=exported.log
An output file, exported.dmp
, is created.
ORACLE_HOME_2\wireless\sql\create_aq_user
. For example:
SQL>@create_aq_user.sql ptg20_user welcome
ptg20_user)
and password (welcome)
. For example:
SQL> connect pt20_user welcome
Execute the create_all SQL script. For example:
SQL> @create_all.sql
exported.dmp
file on that computer.
imp
. For example:
imp system/manager fromuser=ptg102_user touser=ptg20_user file=exported.dmp
commit=y ingore=n log=imported.log
From Oracle9iAS Wireless Release 2 (9.0.2), to support Single Sign-on, users' information stored in the Wireless Repository will be migrated to the OID (which is part of Oracle9iAS Wireless infrastructure).
This step is mandatory regardless of whether the migration is in-place or Repository migration, and whether the installations of Oracle9iAS Wireless Release 1 (1.0.2.2) and Release 2 (9.0.2) are on the same or different computers.
Oracle Internet Directory does not support all possible password hashing schemes. Currently supported schemes include MD4, MD5, SHA and UNIX Crypt. For an exhaustive list of supported password hashing schemes, see "Appendix F" in Oracle Internet Directory Administration Guide. For dealing with non-supported password hashing schemes, see the same section of the above-mentioned guide.
Before migrating users to the Oracle Internet Directory, the default password hashing scheme of the Oracle Internet Directory must be changed to the scheme used in Oracle9iAS Wireless Release 1.0.2.2. To perform this step, see "Chapter 17, Directory Storage of User Authentication Credentials" in Oracle Internet Directory Administration Guide.
The default password policy for the subscribers in OID requires user passwords to be a minimum of 5 characters long with at least one numeric character. Before uploading existing users to OID the password policy of the default subscriber should be modified to make sure that the passwords of the existing users conform to the password policy of the subscriber. For more information on password policies see Chapter 18, "Password Policies" in Oracle Internet Directory Administrator's Guide.
ptgUpgradeRepository.bat
on the machine on which Oracle9iAS Wireless Release 2 (9.0.2) is installed. For example:ptgUpgradeRespoitory.sh ldap_host ldap_port ldap_dn ldap_password subscriber_name connect_str
where:
ldap_host
is the location of the OID server
ldap_port
is the port of the OID server
ldap_dn
is the DN of the OID admin user
ldap_password
is the password of the OID admin user
subscriber_name
is the subscriber name specified at installation time. This by default is the DNS domain name of the machine on which Oracle9iAS is installed.
connect_str
is the connect string to the old database schema (format is: user/password@machine_name.domain:port:sid)
for example:
ptgUpgradeRepository.sh myhost.mydomain 389 'cn=orcladmin' welcome1 'mySubscriberName' ptg102_user/ptg102_password@myhost.mydomain:1521:o817
These steps are required only if any customizations in the form of hooks have been introduced in Oracle9iAS Wireless Release 1 (1.0.2.2.0):
ORACLE_HOME_2\j2ee\OC4J_wireless\config\application.xml
file under the Oracle9iAS Wireless Release 2 (9.0.2) installation, adding a library path directive that points to the copied classes. This ensures that they are included in the classpath of the server.
You may choose to migrate your existing installation to an Oracle9iAS Release 2 (9.0.2) instance with multiple middle tiers. However, the migration scripts should be run only once from any one middle tier. The typical steps to perform when migrating an Oracle9iAS Wireless Release 1 (1.0.2.2.0) instance to an Oracle9iAS Release 2 (9.0.2) installation with multiple middle tiers are:
targets.xml
file for each middle-tier instance as detailed in "Both Installations on Same Computer" or "Installations on Separate Computers".
After migration, you must complete the following procedures.
After migrating services that are based on the URL adapter, ensure that the input parameters are still valid. If not, modify them from the Service Designer:
URLs that were hosted on the old instance itself, such as http://mymachine.foo.com:7777/portal/URLtest.jsp
may not be valid any longer. In this particular instance, a solution could be to copy URLtest.jsp
to
[New OracleHome]/j2ee/applications/webtool/webtool-web
and modify the service referring to it, following the above-mentioned steps.
You must restart all servers on both the middle and infrastructure tiers after completing the migration process.
|
![]() Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|