The following sections describe the steps for upgrading your Oracle Database Lite software:
Section 3.1, "Upgrade Your Oracle Database Lite from 5.0.2.x to 10g Release 2"
Section 3.2, "Upgrade Your Oracle Database Lite from 10g Release 1 to 10g Release 2"
The following sections describe the steps for upgrading your Oracle Database Lite software from 5.0.2.x to 10g Release 2:
Section 3.1.1, "What 5.0.2.x Versions Can I Upgrade to 10g Release 2?"
Section 3.1.2, "Pre-Upgrade Instructions for the 5.0.2.x Version"
Section 3.1.3, "Upgrade Your 5.0.2.x Version Mobile Server Repository"
Section 3.1.4, "Upgrade Your 5.0.2.x Version Existing Applications"
Section 3.1.5, "Upgrading BC4J Mobile Client 5.0.2.x to Version 10g Release 2"
Section 3.1.7, "Use the Appropriate Context for Your Mobile Server"
Section 3.1.9, "Post-Upgrade Instructions for 5.0.2.x Version"
Section 3.1.11, "New Consolidator Sequence Properties Added During Upgrade"
Upgrading Oracle Database Lite from 5.0.2.x to 10g Release 2 is only supported in a separate ORACLE_HOME from the previous installation; thus, an existing Oracle Database Lite 5.0.2.x installation cannot be upgraded to the Oracle Database Lite 10g Release 2 in the same ORACLE_HOME. Table 3-1 details what version of Oracle Database Lite and iAS installation can be upgraded to Oracle Database Lite 10g Release 2.
Table 3-1 Upgrading 5.0.2.x Oracle Database Lite to 10g Release 2
| 10gR2 Standalone (diff Oracle Home) | 10g R2 and iAS 10.1.x | 10g R2 and iAS 10.1.x with OID | 10g R2 and iAS 9.0.4 | 10g R2 and iAS 9.0.4 with OID | |
|---|---|---|---|---|---|
| 5.0.2.x Standalone | Supported | Supported | Not Supported | Supported | Not Supported |
| 5.0.2.x and iAS 9.0.2 | Supported | Supported | Not Supported | Supported | Not Supported |
| 5.0.2.x and iAS 9.0.2 with OID | Not Supported | Not Supported | Supported | Not Supported | Supported |
| 5.0.2.x and iAS 9.0.3 | Supported | Supported | Not Supported | Supported | Not Supported |
| 5.0.2.x and iAS 9.0.3 with OID | Not Supported | Not Supported | Supported | Not Supported | Supported |
In order to upgrade your Oracle Database Lite 5.0.2.x installation, perform the following:
If you are upgrading a 5.0.2.10 Mobile Server that uses Oracle9iAS (version 9.0.4), then remove references to the wtgias.conf and wtgapach.conf files from the Oracle9iAS oracle_apache.conf or the HTTP httpd.conf configuration files before you perform the upgrade for the Mobile Server. The following line is an example of the reference to the wtgias.conf file:
include "c:\olite502\Mobile\Server\bin\wtgias.conf"
If you have multiple Mobile Servers that use the same Mobile Server Repository on a back-end database, you must shut down all of these Mobile Servers before you start the upgrade. Then, upgrade one of these Mobile Servers and the Mobile Server Repository. After this upgrade completes successfully, you can upgrade each additional Mobile Server that uses the Repository. After all of the shared Mobile Servers are upgraded, you can restart them.
Install the current version of Oracle Database Lite in a separate Oracle Home than your 5.0.2.x version.
|
WARNING: Upgrading Oracle Database Lite version 5.0.1.x or previous versions is not supported with this process. You must first upgrade to 5.0.2.x before starting this process. |
See Chapter 2, "Installation of Oracle Database Lite" for instructions on how to install Oracle Database Lite. When the Repository Wizard is executed, see Section 3.1.3, "Upgrade Your 5.0.2.x Version Mobile Server Repository" for directions on how to upgrade the repository on the back-end database.
During installation of Oracle Database Lite 10g Release 2, the Repository Wizard detects if you have a 5.0.2.x version of Oracle Database Lite installed and starts the upgrade process, as follows:
|
Note: If you need to start the Repository Wizard outside of the install process, executeORACLE_HOME\Mobile\Server\admin\repwizard |
Enter the SYSTEM password. Click Next.
Select the schema that you are going to upgrade. Click Next.
Enter the password for the Mobile Server Repository—MOBILEADMIN—and click Yes for installing sample applications. Click Next.
A summary screen appears. Click Next.
After the repository is upgraded, click Finish.
To upgrade each individual Mobile Server, follow the instructions in Section 3.1.2, "Pre-Upgrade Instructions for the 5.0.2.x Version".
Once you have installed the Oracle Database Lite 10g Release 2 in a new Oracle Home and the Repository Wizard has upgraded the Mobile Server Repository successfully, you must execute the Application Upgrade Assistant to upgrade your existing applications.
|
Note: Before you upgrade the application, you must remove references to thewtgias.conf and wtgapach.conf files from the Oracle9iAS oracle_apache.conf or the HTTP httpd.conf configuration files before you perform the upgrade for the Mobile Server. The following line is an example of the reference to the wtgias.conf file:
include "c:\olite502\Mobile\Server\bin\wtgias.conf" |
The Application Upgrade Assistant moves the applications from the 5.0.2.x Oracle Home to your new 10g Release 2 Oracle Home. In addition, the assistant transforms your Mobile applications to the new application model. In previous versions, you could create a single Mobile application for all platforms with a single dataset. In 10g, you must create a single Mobile application for each platform, each with its own dataset. Thus, if you have the myapp application, the Application Upgrade Assistant transforms your myapp application into the following:
Web platform: named myapp and exists in the myapp directory
Win32 platform: named myapp_win32 and exists in the myapp/win32 directory
Palm OS platform: named myapp_palm and exists in the myapp/palm directory
WinCE platform: named appropriately by the language and in a directory that is also named according to the language, as follows:
English: The application is named myapp_wce_Pocket_PC_us_arm and exists in the /myapp/wce/Pocket_PC/us/arm directory.
Chinese: The application is named myapp_wce_Pocket_PC_cn_arm and exists in the /myapp/wce/Pocket_PC/cn/arm directory.
Japanese: The application is named myapp_wce_Pocket_PC_jn_arm and exists in the /myapp/wce/Pocket_PC/jn/arm directory.
Korean: The application is named myapp_wce_Pocket_PC_ko_arm and exists in the /myapp/wce/Pocket_PC/ko/arm directory.
Each application is upgraded with the dataset and access rights that was in the original application.
In addition, Oracle Database Lite 10g Release 2 uses OC4J for all middle-tier functionality. Thus, all Mobile Web applications must now be contained within a J2EE WAR or JAR file. The Application Upgrade Assistant converts your applications by adding the required XML files and packages your Web applications into a WAR file and publishes these applications. However, for all future applications, you must create the XML files and package them into a WAR or JAR file.
The Application Upgrade Assistant is located in the following locations:
On a Windows environment:
ORACLE_HOME\mobile\server\admin\ApplicationUpgradeAssistant.bat
On a UNIX environment:
ORACLE_HOME/mobile/server/admin/ApplicationUpgradeAssistant.sh
On the command-line, supply the Mobile Server Repository Name, the Mobile Server Repository Password, the old Oracle Home and the new Oracle Home. For example, on a Windows system, where the repository name is mobileadmin, its password is manager, the old Oracle Home is c:\oracle\ora502 and the new Oracle Home is c:\oracle\ora10g, execute as follows:
ApplicationUpgradeAssistant mobileadmin manager c:\oracle\ora502 c:\oracle\ora10g
In previous versions, Web-to-Go applications retrieved the OraUserProfile class as follows:
OraUserProfile p = ((OraHttpServletRequest)req).getUserProfile();
For Oracle Database Lite 10g, all existing and future Mobile applications must retrieve the OraUserProfile class with the following lines:
HttpSession s = request.getSession(true);
OraUserProfile p = (OraUserProfile)s.getAttribute ("x-mobileserver-user");
You must manually modify all existing Mobile applications to use the new method of retrieving the OraUserProfile class and then republish the application to complete the upgrade process for your 5.0.2.x Mobile applications.
If you have Oracle Database Lite 5.0.2.x, perform the following steps to upgrade your BC4J mobile client to 10g Release 2:
Upgrade the existing Oracle Database Lite 5.0.2.x to Oracle Database Lite 10g Release 2.
If you have any 5.0.2.x Web-to-Go clients, which are upgrading to the 10g release, then first upgrade all your Web-to-Go clients before continuing to step 3.
Add following line in the [WEBTOGO] section of server side webtogo.ora file and restart Mobile Server:
CLIENT_502_UPGRADE_TYPE = BC4J
Login into the BC4J mobile client using the 5.0.2.x BC4J mobile client user.
Perform a synchronization.
Select Yes when prompted for "Do you want to upgrade".
The upgrade progran prompts for username and password, use the 5.0.2.x BC4J mobile client username and password.
After all the BC4J mobile clients are upgraded, remove the CLIENT_502_UPGRADE_TYPE = BC4J parameter from the server side webtogo.ora file and restart the Mobile Server.
To upgrade your 5.0.2.x version Branch Office to the 10g version of Oracle Database Lite, perform the following steps:
Upgrade the existing Oracle Database Lite 5.0.2.x to Oracle Database Lite 10g Release 2.
If you have any 5.0.2.x Web-to-Go clients, which are upgrading to version 10g , then first upgrade all all of these Web-to-Go clients before continuing to step 3.
Add following line in the [WEBTOGO] section of server side webtogo.ora file and restart Mobile Server:
CLIENT_502_UPGRADE_TYPE = BOS
Login into the Branch Office Client using the 5.0.2.x Branch Office user.
Perform a synchronization.
Select Yes when prompted for "Do you want to upgrade".
The upgrade program prompts for a username and password, where you will provide the 5.0.2.x Branch Office username and password.
After all of the Branch Office clients are upgraded, remove the CLIENT_502_UPGRADE_TYPE = BOS parameter from the server side webtogo.ora and restart the Mobile Server.
The servlet context that you use for all Web-to-Go applications is changed for this version. You must add the /webtogo/ servlet context to all URLs for your Web-to-Go applications. For example, in the past, you tested your Mobile Server using <hostname:port>/sample1/hello. For Oracle Database Lite 10g, enter <hostname:port>/webtogo/sample1/hello.
If you want, you can use the Oracle Internet Directory (OID) for storing and retrieving user information instead of the Mobile Server Repository. To facilitate using OID, you must first migrate all user information from the repository into OID. Once migrated, you can use OID instead of the repository.
OID is part of the Oracle9iAS or OracleAS application server.
Migrate your existing users in the repository to the OID through the oiduser tool, which is located in ORACLE_HOME\mobile\server\bin. The oiduser tool migrates your existing users with either randomly-generated passwords or a common password.
Set the SSO_ENABLED parameter in the webtogo.ora file to YES.
If you are using Oracle9iAS, then explicitly grant permission to the webtogo.jar file to enable calls originating from this JAR file by adding the following content to the jazn-data.xml file, which is located in the ORACLE_HOME/config directory:
<grant>
<grantee>
<codesource>
<url>file:$MIDTIER_ORACLE_HOME/mobile/server/bin/webtogo.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.ias.repository.schemaimpl.CheckRepositoryPermission</class>
<name>connectAs</name>
</permission>
</permissions>
</grant>
Migrate the user information using the oiduser tool, for either randomly-generated passwords or a common password, as follows:
To use randomly-generated passwords for each user, execute the oiduser tool without the -P option, as follows:
oiduser <Oracle_Home> <Mobile Server Repository username> <Mobile Server Repository password> <OID port number> <OID host name> <OID password>
For example, the default setting would be:
oiduser <Oracle_Home> mobileadmin manager 389 myhost-pc1.com welcome1
To use a common password for all users, provide the common password with the -P option, as follows:
oiduser <Oracle_Home> <Mobile Server Repository username> <Mobile Server Repository password> <-P> <common password> <OID port number> <OID host name> <OID password>
where the common password is specified by you.
Executing oiduser generates the mobile_oid_user.bat and oiduserfile.Idif files.
Copy the mobile_oid_user.bat and oiduserfile.Idif files to the same directory in the application infrastructure machine where OID is installed. You can copy them to any directory, as the mobile_oid_user.bat is an executable that uses the oiduserfile.Idif file.
|
Note: Themobile_oid_user.bat executable requires that the ldapadd executable is in the PATH. The ldapadd executable is part of the application server installation. |
Execute the mobile_oid_user.bat file from the command-line on the application server infrastructure machine. This creates the Oracle Database Lite users in the OID.
All users from the Mobile Server Repository are now migrated to the OID with the passwords, as designated in step 1.
Set the SSO_ENABLED parameter in the webtogo.ora file to NO.
Login to Mobile Manager as the administrator and select the appropriate server.
Click on the Administration tab.
Click Edit Config File to edit the webtogo.ora file for this server.
If SSO_ENABLED has a hash mark (#) before it, eliminate the hash mark and set SSO_ENABLED to YES.
Click Apply.
Restart both the application server and the Mobile Server.
After upgrading the Mobile Server and before you synchronize, perform the following for your Web-to-Go, BC4J, and Branch Office clients:
Modify the SERVER_URL parameter in the webtogo.ora file on the Mobile client in the WebToGo directory and append the /webtogo context to the end.
Restart the Web-to-Go client and synchronize.
Once you have completed all of the upgrade exercises, you can now remove the 5.0.2.x version of the Oracle Database Lite from your system. This is not a required step, but is recommended for clarity in the future.
Start up the Oracle Universal Installer by double-clicking on setup.exe.
On the File Locations screen, enter the Oracle Home and path for the 5.0.2.x installation. Click Installed Products.
On the Inventory screen, select the '+' next to the Oracle Home for your 5.0.2.x installation. Then, click the box next to the 5.0.2.x installation that you are going to remove. Click Remove.
On the Confirmation screen, click Yes.
When the removal is complete, click Close.
To exit the Installer, click Exit.
Optionally, you can go into your directories and remove the directory where the 5.0.2.x installation existed.
Any upgrade from a previous version of the Mobile Server upgrades the Consolidator Sequences to a new Sequence model, which contains additional property information. The new Sequence properties have the following default values:
You can modify any of these properties through the Java modifySequence API, which is described fully in the Consolidator Admin API Specification JavaDoc.
If you have Oracle Database Lite 10g Release 1, you must upgrade to the latest version. The following sections describe the steps for upgrading your software:
Section 3.2.1, "To What Versions Can I Upgrade Oracle Database Lite?"
Section 3.2.6, "Upgrading Branch Office 10g Release 1 to version 10g Release 2"
Section 3.2.9, "Remove Duplicate Mobile Server IDs from the Repository"
Upgrading Oracle Database Lite from 10g Release 1 to 10g Release 2 is supported in the same or a separate ORACLE_HOME from the previous installation.
Table 3-2 details what versions of Oracle Database Lite and Oracle iAS installation can be upgraded to Oracle Database Lite 10g Release 2.
Table 3-2 Upgrading 10g Release 1 Oracle Database Lite to 10g Release 2
| 10gR2 Standalone | 10g R2 and iAS 10.1.x | 10g R2 and iAS 10.1.x with OID | 10g R2 and iAS 9.0.4 | 10g R2 and iAS 9.0.4 with OID | |
|---|---|---|---|---|---|
| 10g R1 Standalone | Supported | Supported | Not Supported | Supported | Not Supported |
| 10g R1 and iAS 9.0.2 | Supported | Supported | Not Supported | Supported | Not Supported |
| 10g R1 and iAS 9.0.2 with OID | Not Supported | Not Supported | Supported | Not Supported | Supported |
| 10g R1 and iAS 9.0.3 | Supported | Supported | Not Supported | Supported | Not Supported |
| 10g R1 and iAS 9.0.3 with OID | Not Supported | Not Supported | Supported | Not Supported | Supported |
| 10g R1 and iAS 9.0.4 | Supported | Supported | Not Supported | Supported | Not Supported |
| 10g R1 and iAS 9.0.4 with OID | Not Supported | Not Supported | Supported | Not Supported | Supported |
In order to upgrade your Oracle Database Lite Installation, perform the following:
If you have multiple Mobile Servers that use the same Mobile Server Repository on a back-end database, you must shut down all of these Mobile Servers before you start the upgrade. Then, upgrade one of these Mobile Servers and the Mobile Server Repository. After this upgrade completes successfully, you can upgrade each additional Mobile Server that uses the Repository. After all of the shared Mobile Servers are upgraded, you can restart them.
You can upgrade your existing Database Lite 10g Release 1 to the release 2 in the same Oracle Home OR you can install the Release2 of Oracle Database Lite in a separate Oracle home than your Database Lite 10g Release 1 home.
See Chapter 2, "Installation of Oracle Database Lite" for instructions on how to install Oracle Database Lite. When the Repository Wizard is executed, see Chapter 3, "Upgrade Your Mobile Server Repository" for directions on how to upgrade the repository on the back-end database.
During installation of Oracle Database Lite 10g Release 2, the Repository Wizard detects if Release 1 is installed and initiates the upgrade process, as follows:
|
Note: If you need to start the Repository Wizard outside of the install process, executeORACLE_HOME\Mobile\Server\admin\repwizard |
Enter the SYSTEM password. Click Next.
Select the schema that you are going to upgrade. Click Next.
Enter the password for the Mobile Server Repository—MOBILEADMIN—and click No for installing the sample applications. Click Next.
A summary screen appears. Click Next.
After the repository is upgraded, click Finish.
To upgrade each individual Mobile Server, follow the instructions in Section 3.2.2, "Pre-Upgrade Instructions".
You have to upgrade existing applications only if you installed Oracle Database Lite 10g Release 2 in a separate ORACLE_HOME than Oracle Database Lite 10g Release 1. Thus, once you have installed the Oracle Database Lite 10g Release 2 in a new ORACLE_HOME and the Repository Wizard has upgraded the Mobile Server Repository successfully, execute the Application Upgrade Assistant to upgrade your existing applications.
The Application Upgrade Assistant moves applications from the ORACLE_HOME for Oracle Database Lite 10g Release 1 to your the new ORACLE_HOME for Oracle Database Lite 10g Release 2.
The Application Upgrade Assistant is located in the following locations:
On a Windows environment:
ORACLE_HOME\mobile\server\admin\ApplicationUpgradeAssistant.bat
On a UNIX environment:
ORACLE_HOME/mobile/server/admin/ApplicationUpgradeAssistant.sh
On the command-line, supply the following:
Mobile Server Repository Name
Mobile Server Repository Password
The old ORACLE_HOME
The new ORACLE_HOME
For example, on a Windows system, where the repository name is mobileadmin, password is manager, the old ORACLE_HOME is c:\oracle\ora10gR1 and the new ORACLE_HOME is c:\oracle\ora10gR2, execute the Application Upgrade Assistant, as follows:
ApplicationUpgradeAssistant mobileadmin manager c:\oracle\ora10gR1 c:\oracle\ora10gR2
For the sample applications, you can either upgrade the existing sample applications, use the existing samples in Release 2, or install new sample applications. The Release 1 samples will still work in Release 2 without any upgrade.
To install samples use following command:
demoinstaller -install [Database_Administrator_User_Name] [Database_Administrator_Password] [Repository_Owner] [Repository_Password] [Demo_user_name ][Demo_password ]
For Example:
demoinstaller -install system manager mobileadmin manager master master
The demoinstaller utility is located in the following directories:
On a Windows environment:
ORACLE_HOME\mobile\server\demos\demoinstaller.bat
On a UNIX environment:
ORACLE_HOME/mobile/server/demos/demoinstaller.sh
If you have Oracle Database Lite 10g Release 1, then upgrade your Branch Office to 10g Release 2, as follows:
|
Note: These steps assume that you have a 10g Release 1 Branch Office environment already configured and synchronized. If you do not have this environment currently configured, you do not need to upgrade. |
Install Oracle Lite 10g Release 2 Mobile Server in the same ORACLE_HOME directory where you installed Release 1.
Stop the Branch Office client executing as a Windows Service.
Open a command prompt, navigate to the BO_CLIENT_HOME\bin directory, and start the Branch Office Client by issuing the webtogo -d0 command.
Login into the Branch Office Client using the Release 1 Branch Office user.
Perform a synchronization.
Select Yes when prompted for "Do you want to upgrade". The Web-to-Go component of the Branch Office Client upgrades.
Once the upgrade completes, then the Branch Office client restarts as a Windows Service. In order to perform the next step, stop the service.
Open another command prompt, navigate to the BO_CLIENT_HOME\bin directory, and invoke update.exe to upgrade the Branch Office Component.
|
Note: The upgrade fails if you invokeupdate.exe without stopping the Branch Office client running as a service. |
Start the Branch Office client either as a Windows Service or from the command prompt invoking webtogo -d0.
You can use the Oracle Internet Directory (OID), which is part of the Oracle application server, for storing and retrieving user information instead of the Mobile Server Repository. To use OID, you must migrate all user information from the existing repository into OID.
Migrate existing users in the repository to OID through the oiduser tool, which is located in ORACLE_HOME\Mobile\Server\bin. The oiduser tool migrates existing users with either randomly-generated passwords or a common password.
Set the SSO_ENABLED parameter in the webtogo.ora file to YES.
If you are using Oracle9iAS, then explicitly grant permission to the webtogo.jar file, which enable calls originating from this JAR file. Grant this permission by adding the following to the jazn-data.xml file, which is located in the ORACLE_HOME/config directory:
<grant>
<grantee>
<codesource>
<url>file:$MIDTIER_ORACLE_HOME/mobile/server/bin/webtogo.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.ias.repository.schemaimpl.CheckRepositoryPermission</class>
<name>connectAs</name>
</permission>
</permissions>
</grant>
Migrate the user information using the oiduser tool, for either randomly-generated passwords or a common password, as follows:
To use randomly-generated passwords for each user, execute the oiduser tool without the -P option, as follows:
oiduser <ORACLE_HOME> <Mobile Server Repository username> <Mobile Server Repository password> <OID port number> <OID host name> <OID password>
For example, the default setting would be:
oiduser <ORACLE_HOME> mobileadmin manager 389 myhost-pc1.com welcome1
To use a common password for all users, provide the common password with the -P option, as follows:
oiduser <ORACLE_HOME> <Mobile Server Repository username> <Mobile Server Repository password> <-P> <common password> <OID port number> <OID host name> <OID password>
where the common password is specified by you.
The oiduser tool generates the mobile_oid_user and oiduserfile.Idif files. Copy these files to the same directory in the application infrastructure machine where OID is installed. You can copy them to any directory, as the mobile_oid_user is an executable that uses the oiduserfile.Idif file.
|
Note: Themobile_oid_user executable requires that the ldapadd executable is in the PATH. The ldapadd executable is part of the application server installation. |
Execute the mobile_oid_user file from the command-line on the application server infrastructure machine. This creates the Oracle Database Lite users in the OID.
All users from the Mobile Server Repository are now migrated to the OID with the passwords, as designated in step 1.
Set the SSO_ENABLED parameter in the webtogo.ora file to NO.
Login to Mobile Manager as the administrator and select the appropriate server.
Click on the Administration tab.
Click Edit Config File to edit the webtogo.ora file for this server.
If SSO_ENABLED has a hash mark (#) before it, then eliminate the hash mark and set SSO_ENABLED to YES. Click Apply.
Restart both the application server and the Mobile Server.
Once you have completed all of the upgrade exercises, you can now remove the Oracle Database Lite 10g Release 1 from your system. Only perform these steps if you have installed Oracle Database Lite 10g Release 2 in a separate ORACLE_HOME. In addition, this is not required, but is recommended for clarity.
Start the Oracle Universal Installer by double-clicking on setup.exe.
On the File Locations screen, enter the ORACLE_HOME and PATH for the 10g Release 1 installation. Click Installed Products.
On the Inventory screen, select the '+' next to the ORACLE_HOME for your 10g Release 1 installation. Then, click the box next to the installation that you are going to remove. Click Remove.
On the Confirmation screen, click Yes.
When the removal is complete, click Close.
To exit the Installer, click Exit.
After migrating Oracle Database Lite 10g Release 1 to Release 2, you will see duplicate entries in the Mobile Manager Farms page. To delete these entries from the repository, use the unregistermobileserver utility:
unregistermobileserver <MobileServerId>
Following is the location of unregistermobileserver:
On a Windows environment:
ORACLE_HOME\mobile\server\admin\unregistermobileserver.bat
On a UNIX environment:
ORACLE_HOME/mobile/server/admin/unregistermobileserver.sh