Skip Headers

Oracle® Application Server 10g Upgrading from Release 1 (1.0.2.2.x) to 10g (9.0.4)
10g (9.0.4)
Part No. B13674-02
  Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous Next  

5 Upgrading to OracleAS Wireless

This chapter contains step-by-step instructions for upgrading Oracle9iAS Wireless. It contains the following sections:

5.1 OracleAS Wireless Upgrade Items

An upgrade item is an aspect of configuration that is acted upon during upgrade: a file, executable, or a setting that you must add, change, or delete/replace in the 10g (9.0.4) installation. OracleAS Wireless upgrade items are described in Table 5-1.

Table 5-1 OracleAS Wireless Upgrade Items

Upgrade Item Location in Release 1 (1.0.2.2.x) Location in 10g (9.0.4) Notes
Database schema

The database schema has been modified and enhanced significantly in Oracle Application Server 10g (9.0.4). The wireless schema must be upgraded.
Model objects

Model objects are modified because new model objects have been introduced and schema changes have been made. Model objects in the following groups are affected:
  • group

  • role

  • user

  • service list

  • transformer

  • logical device

  • adapters

User Agent property files Properties file in middle tier Database Previously, the HTTP user agent header to logical device mapping was stored as a plain properties file. In this release, the mapping is stored in the database. This information must be moved from the Java properties file to the database.
Transformers

Because persistent representation between the transformer and logical device has been modified since Oracle9iAS Release 1 (1.0.2.2), a separate Java program is now used to upgrade to the new table schema.
Site and Node configuration property Properties files in middle tier Database
User information in the PanamaUser Table Wireless Repository orclUserV2 user attributes in Oracle Internet Directory

5.2 Components Related to OracleAS Wireless

Oracle Application Server Wireless can be integrated with Oracle Internet Directory, OracleAS Web Cache, and OracleAS Portal. In Oracle Application Server 10g (9.0.4), user information is stored centrally in OID. The SSO (Single Sign-On) server uses an OID repository to authenticate users.

5.3 Preliminary OracleAS Wireless Upgrade Tasks

Before you begin upgrading, ensure that the tasks below have been performed. The necessity of installing the Oracle Application Server 10g (9.0.4) Infrastructure and Portal and Wireless middle tier is discussed in Section 1.1, "The Oracle9iAS Release 1 (1.0.2.2.x) to Oracle Application Server 10g (9.0.4) Upgrade Process", but it is repeated here with some additional steps specific to the OracleAS Wireless component (creation of backups at certain points in the process).

  1. Back up the Oracle9iAS Release 1 (1.0.2.2.x) database and middle tier.

  2. Go to the patch download page by accessing this link:

    http://updates.oracle.com/ARULink/PatchSearch/process_form?aru=5993750

  3. Click Download.

    The connect to updates.oracle.com dialog box appears.

  4. Enter your MetaLink user name and password.

    The Patch Download page appears.

  5. Click Download and save the p3509336_9040_GENERIC.zip file.

  6. Unzip the file by issuing this command:

    unzip p3509336_9040_GENERIC.zip

    The directory ias1022_10gupgrade is created.

  7. Copy the prepare_exp.sql file from the ias1022_10gupgrade/sql/ directory to the <source_MT_OH>/panama/sql directory.

  8. Drop the spatial indexes in the Oracle9iAS Wireless schema in the Oracle9iAS Release 1 (1.0.2.2.x) database by issuing the following command:

    sqlplus <iAS 1022 user>/<password>@<iAS 1022 db SID> @prepare_exp.sql

    where:

    • iAS 1022 user is the Oracle9iAS Wireless schema user

    • password is the Oracle9iAS Wireless schema user's password

    • iAS 1022 db SID is the SID

    for example:

    sqlplus myself/welcome@iasdb @prepare_exp.sql

  9. Create a dump of the Oracle9iAS Release 1 (1.0.2.2.x) Wireless schema by issuing the following command:

    exp system/<password> owner=<iAS 1022 wireless user> consistent=y file=<exported>.dmp log=<exported>.log

    where:

    • iAS 1022 user is the iAS database user

    • password is the iAS database user's password

    • exported is the descriptive name given to the exported schema and the associated log file

    for example:

    exp system/welcome owner=myself consistent=y file=my_schema.dmp log=my_schema.log

  10. Install the Oracle Application Server 10g (9.0.4) Infrastructure.

  11. Install the Oracle Application Server 10g (9.0.4) Portal and Wireless middle tier. Do not configure the Wireless component during installation.


    Note:

    If you install the Oracle Application Server 10g (9.0.4) middle tier on a computer other than that on which the Oracle9iAS Release 1 (1.0.2.2.x) middle tier is installed, you need to upload the Oracle9iAS Release 1 (1.0.2.2.x) Panama folder to the 10g (9.0.4) middle tier computer after installing 10g (9.0.4), and unzip the file.

    If the Oracle Application Server 10g (9.0.4) middle tier is on a different computer from the Oracle9iAS Release 1 (1.0.2.2.x) middle tier, set the environment variables as follows in the 10g (9.0.4) Oracle home as follows:

    • ORACLE_HOME to the Oracle Application Server 10g (9.0.4) middle tier Oracle home

    • ORACLE_SID to the Wireless schema

    • (UNIX) PATH to $ORACLE_HOME/bin:$PATH

      (Windows) PATH to %ORACLE_HOME\bin:%PATH


  12. Back up the Oracle Application Server 10g (9.0.4) database and middle tier.

  13. Create an inventory of all of the alerts and customizations made to Oracle9iAS Wireless in Oracle9iAS Release 1 (1.0.2.2.x). The alerts from Oracle9iAS Release 1 (1.0.2.2.x) are not supported in 10g (9.0.4), so they must be re-created there as part of the upgrade process.

5.4 OracleAS Wireless Upgrade Tasks

This section provides instructions for upgrading each item identified in Section 5.1, "OracleAS Wireless Upgrade Items". It is divided into the following subsections:

5.4.1 Obtaining the 10g (9.0.4) Instance OracleAS Wireless Schema Password

You need the Wireless database schema password to perform the upgrade. Follow these steps to obtain the password from Oracle Internet Directory:

  1. Ensure that Oracle Internet Directory and Oracle Application Server Single Sign-On are running.

  2. Execute the wireless-pwd.sh. script (available in the ias1022_10gupgrade/bin directory) by issuing this command:

    (UNIX) ./wireless-pwd.sh <OID host> <OID port> <OID password>

    (Windows) wireless-pwd.bat <OID host> <OID port> <OID password>

    where:

    • OID host is the hostname of the OID server

    • OID port is the port of the OID server

    • OID password is the password of the OID administrative user (orcladmin)

    for example:

    ./wireless-pwd.sh oidhost.mycompany.com 3060 welcome1

    The script executes and generates output.

  3. Note the value of orclpasswordattribute, which is the Wireless schema password you will use when prompted during the upgrade procedure.

5.4.2 Preparing the Middle Tier Oracle Home Environment

To prepare the environment, follow these steps in the 10g (9.0.4) middle tier Oracle home:

  1. Stop OPMN and all of the components it manages by issuing this command from <destination_MT_OH>/opmn/bin:

    opmnctl stopall

  2. Ensure that Oracle Enterprise Manager 10g is running. To start it, issue this command from <destination_MT_OH>/bin:

    emctl start em

5.4.3 Dropping and Creating OracleAS Wireless Schema

On the computer on which the Infrastructure database is installed, follow these steps to drop and create the OracleAS Wireless schema:

  1. Issue the commands below to drop the schema:

    sqlplus <DBA user>/<DBA password>@<service name>

    drop user wireless cascade;

    where:

    • DBA user is the DBA user name

    • DBA password is the DBA user's password

    • service name is the database name

    for example:

    sqlplus system/welcome1@asdb

    drop user wireless cascade;

  2. Create new wireless schema using the create_aq_user.sql script, available in <destination_MT_OH>/wireless/repository/sql/. Issue this command:

    sqlplus <DBA user>/<DBA password>@<service name> @create_aq_user.sql WIRELESS <wireless password>�;

    where:

    for example:

    sqlplus system/welcome1@asdb @create_aq_user.sql WIRELESS UmS7rubt;

  3. On the computer on which the 10g (9.0.4) Infrastructure is installed, set the ORACLE_HOME environment variable to <destination_Infra_OH> and the PATH environment variable to $ORACLE_HOME/bin.

  4. If the source and destination Oracle homes are on different computers, use FTP to transfer the .dmp file generated in Section 5.3, "Preliminary OracleAS Wireless Upgrade Tasks" to the current computer.

  5. Determine whether the Wireless schema's tablespace in Oracle9iAS Release 1 (1.0.2.2.x) exists in the Oracle Application Server 10g (9.0.4) Infrastructure database by following these steps:

    1. Connect to the Oracle9iAS Release 1 (1.0.2.2.x) database as the SYS user.

    2. Execute the query:

      select username, default_tablespace from dba_users where username 'WIRELESS';

      The query result resembles the following:

      USERNAME                    DEFAULT_TABLESPACE

      --------------------------- -----------------------

      WIRELESS                    USERS

    3. Connect to the Oracle Application Server 10g (9.0.4) database as the SYS user.

    4. Execute the query:

      select tablespace_name from dba_tablespaces where tablespace_name '<tablespace name>';

      If the tablespace exists, the query returns the tablespace name (in the examples, the name is USERS). If it does not, then create the tablespace by following Step e. If it exists, continue with Step f.

    5. Issue this command:

      create tablespace <tablespace name> datafile '<datafile name>' SIZE <free space>M;

      where:

      tablespace name is the name of the tablespace (the name returned by the query on the Oracle9iAS Release 1 (1.0.2.2.x) database)

      datafile name is the name of the datafile (the same name as in the Oracle9iAS Release 1 (1.0.2.2.x) database)

      free space is the amount of memory in megabytes to allocate to the tablespace

      for example:

      create tablespace USERS datafile '/private1/mig/as10ginfra/oradata/asdb/user.dbf' SIZE 200M;

    6. Ensure that the memory of the existing tablespace is at least 200 MB by executing this query:

      select (SUM (BYTES)/(1024 * 1024)) from dba_free_space where TABLESPACE_NAME='<tablespace name>';

      The query returns a value for MEMORY. If it is less than 200, continue with Step g to increase it. If it is 200 or more, continue with Step 6.

    7. Obtain the file name of the tablespace with this query:

      select TSNAME, FNAME from sysfiles where TSNAME='<tablespace name>'

    8. Allocate additional memory to the tablespace by issuing this command:

      alter tablespace <tablespace name> datafile '<datafile name>' RESIZE <free space>M;

      where:

      tablespace name is the name of the tablespace (the same name as in Oracle9iAS Release 1 (1.0.2.2.x))

      datafile name is is the name of the datafile specified by the FNAME value in the query result produced in step g.

      free space is the amount of memory in megabytes to allocate to the tablespace; in this case it needs to be 200 or greater

      for example:

      alter tablespace USERS datafile '/private1/mig/as10ginfra/oradata/asdb/users01.dbf' RESIZE 200M;

  6. Import the Wireless data from the .dmp file into the Metadata Repository, using the import tool imp. To do this, issue the following command:

    imp system/<password> fromuser=<1022 wireless schema user> touser=<904 wireless schema user> file=exported.dmp commit=y ignore=n log=imported.log

    where:

    • password is the SYS user password

    • 1022 wireless schema user is the owner of the Wireless schema in Oracle9iAS Release 1 (1.0.2.2.x)

    • 904 wireless schema user is the owner of the Wireless schema in Oracle Application Server 10g (9.0.4)

    for example:

    imp system/welcome1 fromuser=scott touser=fred file=exported.dmp commit=y ignore=n log=imported.log

    You may safely ignore the warning message "Import terminated successfully with warnings."

  7. Ensure that the ORACLE_HOME and PATH environment variables and the ORACLE_SID are set to point the 10g (9.0.4) middle tier.

  8. Configure the database connection in the <destination_MT_OH>/wireless/server/classes/oracle/panama/core/admin/system.properties file by following these steps:

    1. Set standalone=true.

    2. Modify db.connect.string to use the THIN driver and comment out all remaining db.connect.string settings.

      The db.connect.string has the following format:

      wireless/<wireless password>@hostname:port:sid

      for example:

      wireless/UmS7rubt@usunnad27.us.oracle.com:1521:asdb

    3. Set db.driver=THIN.

  9. If the Oracle9iAS Release 1 (1.0.2.2.x) and the Oracle Application Server 10g (9.0.4) middle tiers are on different computers:

    In the <source_MT_OH> /panama/server/classes/oracle/panama/spatial/spatial.properties file, change all absolute paths to the path of the current Oracle9iAS Release 1 (1.0.2.2.x) Oracle home.

    For example:

    file.providers.config.xml.geocoding = /private1/home/iaswbm/ias1022/panama/serve�r/classes/oracle/panama/spatial/geocoder/Geocoders.xml (The path resembles this prior to uploading the panama folder to the 10g (9.0.4) instance's computer.)

    Assume that the new Oracle9iAS Release 1 (1.0.2.2.x) instance (the panama folder of Oracle9iAS Release 1 (1.0.2.2.x)) in the 10g (9.0.4) computer is /private1/ias1022. Then the path above would be as follows:

    file.providers.config.xml.geocoding = /private1/ias1022/panama/serve�r/classes/oracle/panama/spatial/geocoder/Geocoders.xml�

5.4.4 Executing the OracleAS Wireless Upgrade Script

A script, ias1022-902.sh, is provided in the ias1022_10gupgrade/bin directory to perform the upgrade. Follow these steps in the 10g (9.0.4) Oracle home to execute the script:

  1. Issue the following command:

    (UNIX) ./ias1022-902.sh <source_MT_OH> <destination_MT_OH> <script path> <connect str> <admin password>

    (Windows) ias1022-902.bat <source_MT_OH> <destination_MT_OH> <script path> <connect str> <admin password>

    where:

    • source_MT_OH is the path to the Oracle home of the Oracle9iAS Release 1 (1.0.2.2.x) installation

    • destination_MT_OH is the path to the Oracle home of the 10g installation

    • script path is the path to the ias1022_10gupgrade directory

    • connect str is the connect string for the wireless schema (to be specified as user/password@sid)

    • admin passwd is the password of the admin user specified during the Oracle9iAS Release 1 (1.0.2.2.x) installation

    for example:

    ./ias1022-902.sh /private1/mig/ias1022 /private1/mig/as10gmid /private1/mig/ias1022_10gupgrade wireless/UmS7rubt@asdb manager


    Note:

    source_MT_OH can have two different values, depending on the configuration upgraded:
    • If the source and destination middle tiers are on different computers, and the panama directory of the Oracle9iAS Release 1 (1.0.2.2.x) was uploaded to the 10g (9.0.4) computer under /private1, then source_MT_OH is private1.

    • If the source and destination middle tiers are on the same computer, then source_MT_OH is the path to the Oracle9iAS Release 1 (1.0.2.2.x).


  2. In the <destination_MT_OH>/wireless/server/classes/oracle/panama/core/admin/system.properties file, set standalone=false. This causes the upgrade process to obtain database connections from Oracle Internet Directory.

  3. Configure the OracleAS Wireless 10g (9.0.4) component by following these steps:

    1. Access Oracle Enterprise Manager 10g with the following URL:

      http://<hostname>:<port>

      A login dialog box appears for the Oracle Enterprise Manager 10g administrative user. The default name of this user is ias_admin, and the default port is 1810.

    2. Enter the administrative user password.

      The Application Servers page appears.

    3. In the Standalone Instances section, click the middle tier instance.

    4. In the System Components section, click Configure Component.

      The Select Component page appears.

    5. Select Wireless from the drop-down list.

      A password dialog appears.

    6. Enter the orcladmin password and then click Finish.�

      The configuration process begins, and continues for approximately one hour.

  4. Register OracleAS Wireless with Oracle Application Server Single Sign-On using the ssoreg.sh script on UNIX or the ssoreg.bat script on Windows. The script is available in the ias1022_10gupgrade/bin directory. Issue this command:

    (UNIX) ./ssoreg.sh

    (Windows) ssoreg.bat

  5. Migrate the users using the ptgUsrMigrate.sh script on UNIX or the ptgUsrMigrate.bat script on Windows. The script is available in the ias1022_10gupgrade/bin directory. Issue this command:

    (UNIX) ./ ptgUsrMigrate.sh <ldap host> <ldap port> <ldap dn> <ldap password> <connect str> <script path> (Windows)

    ptgUsrMigrate.bat <ldap host> <ldap port> <ldap dn> <ldap password> <connect str> <script path>

    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 like cn=<admin_user>

    • ldap password is the password of the OID admin user

    • connect str is the connect string to the wireless schema, in the format user/password@hostname:port:sid

    • script path is the path to the ias1022_10gupgrade directory

    for example:

    ./ptgUsrMigrate.sh usunnad27.us.oracle.com 3060 cn=orcladmin welcome1 wireless/UmS7rubt@usunnad27.us.oracle.com:1521:asdb /private1/mig/ias1022_10gupgrade

  6. Execute the populateGuid.sh script on UNIX or the populateGuid.sh script on Windows. The script is available in the ias1022_10gupgrade/bin directory. Issue this command:

    (UNIX) ./populateGuid.sh <connect str>

    (Windows) populateGuid.bat <connect str>

    where connect str is the connect string for the Wireless schema

    for example:

    ./populateGuid.sh wireless/UmS7rubt@asdb

  7. Start the opmn process. Issue this command:

    <destination_MT_OH>/opmn/bin/opmnctl startall

5.5 Validating the OracleAS Wireless Upgrade

After the upgrade is complete, follow these steps to validate its success:

  1. Log in to OracleAS Wireless as the user that managed Oracle9iAS Wireless, and verify that you can access all of the services you could access in Oracle9iAS Release 1 (1.0.2.2.x).

  2. Check the groups and services to verify that they are upgraded. Use the web-based tool to see if the groups and users in Oracle9iAS Release 1 (1.0.2.2.x) are upgraded properly.

  3. Test the new features of OracleAS Wireless in 10g (9.0.4). Refer to the Oracle Application Server Wireless Administrator's Guide in the 10g (9.0.4) documentation library.