Skip Headers

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
Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

5
Migrating Wireless Components

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:

Migrating Oracle9iAS Wireless

Migrating Oracle9iAS Wireless

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.



Warning:

Back up the Repository before beginning any migration activities.


Migration Scope

The following modifications are required to migrate Oracle9iAS Wireless 1.0.2.2.0 to Release 2 (9.0.2).

Migrating User Agent Property Files to Database

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.

Upgrade Transformers Due to Table Schema Changes

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.

Migrate Site and Node Configuration Property to Database

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.

Migrate Panama User Table to OID

User information stored in the panama user table must be migrated to the OID.

Migration Path

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).

  1. Back up the Repository.

  2. Install Oracle9iAS Wireless Release 2 (9.0.2) software as a fresh installation if in-place Repository upgrade is desired. (The in-place Repository upgrade enables you to continue to use the existing database as the Wireless schema Repository. However, migrating the Repository is recommended over an in-place migration). The Repository upgrade occurs on the current Repository instead of on a new one as part of the Oracle9iAS Wireless Infrastructure Repository.

Before You Begin

  1. Set the environment variables ORACLE_HOME JAVA13_HOME to point to the newly installed Oracle9iAS Wireless Release 2 (9.0.2) location, and ORACLE_HOME_2\JDK, respectively.

  2. Create a named service entry (if one does not exist, in tnsnames.ora) corresponding to the Oracle9iAS Wireless Release 1 (1.0.2.2.0) Repository database.


    IMPORTANT:

    Ensure that the Oracle9iAS Wireless Release 1 (1.0.2.2) database has at least the 8.1.7.1.0 patchset applied. Without this patch, the SSO server will not function after migration.



    IMPORTANT:

    Ensure that the Oracle9iAS Wireless Release 9.0.2 OC4J instances are shut down. To do this, issue the command opmnctl stopall from the ORACLE_HOME_2\opmn\bin directory. The Oracle Enterprise Manager daemon should, however, be running. This daemon can be started (if not already running) by invoking emctl start from ORACLE_HOME_2\bin.


In-place Migration

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"


Note:

Type the command as a single line.


Both Installations on Same Computer

  1. Using the Oracle Enterprise Manager (EM) console, change the database schema to point to the Repository database of the Oracle9iAS Wireless Release 1 (1.0.2.2.0) installation. See the Oracle Enterprise Manager documentation for information on how to change the database schema.

    See Also:

    Oracle Enterprise Manager Configuration Guide, Oracle Enterprise Manager Administrator's Guide, and Oracle Enterprise Manager Concepts Guide in the Oracle9iAS Documentation Library.

  2. Connect to the Oracle9iAS Wireless Release 1 (1.0.2.2.0) Repository database as the administrative user and run the 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
    
    
  3. Run the script 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
    
    


    Note:

    While running the ptgUpgrade script, several 'Unique Constraint' violations may occur, because the new bootstrap file has user-agent entries that clash with existing user-agent entries. The violations may be safely ignored.


  4. A mobile gateway URL must be registered with Oracle Portal. This step is necessary only if Oracle Portal is enabled/configured. Run the portalRegistrar.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
    
    
  5. Edit the Oracle Enterprise Manager file 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"/>
    
Installations on Separate Computers

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):

  1. Using the EM console, change the database schema to point to the Repository database of the Oracle9iAS Wireless Release 1 (1.0.2.2.0) installation.

  2. Connect to the Oracle9iAS Wireless Release 1 (1.0.2.2.0) Repository database as the administrative user and run the 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
    
    
  3. Copy the entire directory structure

    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
    
    
  4. On mc2, run the 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
    
    


    Note:

    While running the ptgUpgrade script, several 'Unique Constraint' violations may occur, because the new bootstrap file has user-agent entries that clash with existing user-agent entries. The violations may be safely ignored.


  5. A mobile gateway URL must be registered with Oracle Portal. This step is necessary only if Oracle Portal is enabled/configured. Run the portalRegistrar.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
    
    
  6. The Oracle Enterprise Manager targets file must be modified to point to the newly upgraded database repository. For this purpose, edit the file 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"/>
    
Migrate the Repository

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.

  1. Export the existing database information using exp. For example:

    exp system/manager owner=ptg102_user file=exported.dmp log=exported.log 
    
    

    An output file, exported.dmp, is created.

  2. Connect to the Oracle9iAS Wireless Release 2 (9.0.2) Repository database as the administrative user and create a new schema using ORACLE_HOME_2\wireless\sql\create_aq_user. For example:

    SQL>@create_aq_user.sql ptg20_user welcome 
    
    
  3. Connect as the newly created user with the new username (ptg20_user) and password (welcome). For example:

    SQL> connect pt20_user welcome
    
    
  4. Execute the create_all SQL script. For example:

    SQL> @create_all.sql
    
    
  5. Use the EM console to change the Wireless connect string to point to this new schema.

  6. If the Oracle9i database is on a different computer, use ftp to put the exported.dmp file on that computer.

  7. Import the Oracle9i database using imp. For example:

    imp system/manager fromuser=ptg102_user touser=ptg20_user file=exported.dmp 
    commit=y ingore=n log=imported.log
    
    


    Notes:

    For some object types the AQ uses, an object ID validation failure may occur. If this happens, you should consider using the TOID_NOVALIDATE parameter to disable validation on those types (when using Oracle Import Utility).

    Setting commit=y will improve performance since lengthy rollback processing will be avoided.


  8. Perform an upgrade by following the steps provided in "Both Installations on Same Computer" or "Installations on Separate Computers", depending on whether the Oracle9iAS Wireless Release 1 (1.0.2.2) and Oracle9iAS Wireless Release 2 (9.0.2) installations are on the same or different computers.

Migrate Users


Note:

This procedure may be skipped if, as part of another migration, users have already been migrated from component-specific repositories to Oracle Internet Directory (OID).


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).


Note:

In Oracle9iAS Release 2 (9.0.2), user information is stored in OID, where user names are case-insensitive. This is different from earlier versions of Oracle9iAS Wireless, in which user names were case-sensitive.


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.

  1. Change the Password Policy of Default Subscriber in OID.

    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.

  2. Migrate the users from the database repository to OID by running 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:

    for example:

    ptgUpgradeRepository.sh myhost.mydomain 389 'cn=orcladmin' welcome1 
    'mySubscriberName' ptg102_user/ptg102_password@myhost.mydomain:1521:o817
    
    

Additional Steps for Migrating Customizations

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):

  1. Ensure that the classes for the hooks are copied to computer mc2 and modify the 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.

  2. If applications or servlets have been added as part of customization and require migration, refer to the Oracle9iAS documentation on migrating existing applications.

Migrating with Multiple Middle Tiers

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:

  1. Install an Oracle9iAS Release 2 (9.0.2) Infrastructure tier.

  2. Install as many Oracle9iAS Release 2 (9.0.2) middle tiers as necessary to point to this infrastructure tier.

  3. Upgrade the Oracle9iAS Wireless Release 1 (1.0.2.2) instance from any one middle tier.

  4. With the Enterprise Manager console, change the schema for each of the mid-tiers to point to the upgraded database/repository.

  5. Edit the targets.xml file for each middle-tier instance as detailed in "Both Installations on Same Computer" or "Installations on Separate Computers".

Post-Migration Tasks

After migration, you must complete the following procedures.

Migrating URL Adapter-Based Services

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:

  1. Click the radio-button next to the service to select it.

  2. Click Edit.

  3. Choose Input parameters from the side tab.

  4. Enter the new URL.

    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.

Restart Servers

You must restart all servers on both the middle and infrastructure tiers after completing the migration process.


Go to previous page Go to next page
Oracle
Copyright © 2002 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index