The following sections describe the steps for upgrading your Oracle Database Mobile Server software:
Section 5.2, "Upgrade Your Oracle Database Lite from 10g Release 1 or 2 to 10g Release 3"
Section 5.3, "Upgrade Oracle Database Mobile Server 11g Release 1 to 11g Release 2"
This version of the Oracle Database Mobile Server contain most of the components of the previous Oracle Database Lite product, with a few exceptions. The Oracle Lite client is no longer supported. Instead, all synchronization originates from either a Berkeley DB or SQLite client. Thus, if you have been using Oracle Database Lite in the past, all Oracle Database Lite Mobile Clients will need to be migrated to either of these supported mobile clients. In addition, your mobile server needs to be upgraded to the 11g version of the mobile server. You can either upgrade your Mobile Server from 10.3.0.3.0 to 11.1.0.0.0 and then to 11.2.0.0.0 or upgrade from 10.3.0.3.0 to 11.2.0.0.0 directly.
The following sections detail how you can migrate Oracle Database Lite 10.3.0.3.0 to Oracle Database Mobile Server 11g Release 1 or Release 2 for both your existing mobile server and mobile clients.
Before you can migrate the mobile server of your Oracle Database Lite 10.3.0.3.0 to Oracle Database Mobile Server 11g, perform the following:
Upgrade to a supported Oracle Database Lite Version
You can only migrate an Oracle Database Lite version 10.3.0.3.0 to Oracle Database Mobile Server 11g. Therefore, if your current version of Oracle Database Lite is previous to version 10.3.0.3.0, this must first be upgraded to Oracle Database Lite 10.3.0.3.0 and all patches applied before migrating to Oracle Database Mobile Server 11g. Details for migrating Oracle Database Lite versions 10.1 and 10.2 to Oracle Database Lite version 10.3 is described in Section 5.2, "Upgrade Your Oracle Database Lite from 10g Release 1 or 2 to 10g Release 3".
Table 5-1 shows what software is supported when migrating from an Oracle Database Lite 10.3.0.3 and its installed application server to Oracle Database Mobile Server 11g Release 1 and supported application servers.
Table 5-1 Upgrading Oracle Database Lite 10.3.0.3.0 to Oracle Database Mobile Server 11.1.0.0.0
| From Previous Oracle Database Lite Version | To Oracle Database Mobile Server 11g Release 1 Base | Same Oracle Home | Separate Oracle Home |
|---|---|---|---|
|
Oracle Database Lite 10.3.0.3 Standalone |
Oracle WebLogic Server 11g Release 1 |
Not Supported |
Supported |
|
Glassfish 3.1 |
Not Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
|
Oracle Database Lite 10.3.0.3 with WebLogic 11g Release 1 |
Oracle WebLogic Server 11g Release 1 |
Supported |
Supported |
|
Glassfish 3.1 |
Not Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
|
Oracle Database Lite 10.3.0.3 with Oracle iAS 10.1.3.5.0 |
Oracle WebLogic Server 11g Release 1 |
Not Supported |
Supported |
|
Glassfish 3.1 |
Not Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Supported |
Supported |
Table 5-2 shows what software is supported when migrating from an Oracle Database Lite 10.3.0.3.0 and its installed application server to Oracle Database Mobile Server 11g Release 2 and supported application servers.
Table 5-2 Upgrading Oracle Database Lite 10.3.0.3.0 to Oracle Database Mobile Server 11.2.0.0.0
| From Previous Oracle Database Lite Version | To Oracle Database Mobile Server 11g Release 2 Base | Same Oracle Home | Separate Oracle Home |
|---|---|---|---|
|
Oracle Database Lite 10.3.0.3.0 Standalone |
Oracle WebLogic Server 11g Release 1, Oracle WebLogic Server 12c |
Supported |
Supported |
|
Glassfish 3.1 |
Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Supported |
Supported |
|
|
Apache TomEE 1.0 |
Supported |
Supported |
|
|
Oracle Database Lite 10.3.0.3.0 with WebLogic 11g Release 1 |
Oracle WebLogic Server 11g Release 1, Oracle WebLogic Server 12c |
Supported |
Supported |
|
Glassfish 3.1 |
Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Supported |
Supported |
|
|
Apache TomEE 1.0 |
Supported |
Supported |
|
|
Oracle Database Lite 10.3.0.3.0 with Oracle iAS 10.1.3.5.0 |
Oracle WebLogic Server 11g Release 1, Oracle WebLogic Server 12c |
Supported |
Supported |
|
Glassfish 3.1 |
Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Supported |
Supported |
|
|
Apache TomEE 1.0 |
Supported |
Supported |
If you use OID 10.1.2 to manage user information for Oracle Database Lite 10.3.0.3.0, upgrade to OID version 10.1.4 or 11.1.1.5.
Note:
If you are not currently using OID, but would like to use OID with Oracle Database Mobile Server 11g, follow instructions in Section 5.2.6, "Migrate Your Users From the Mobile Server Repository to the Oracle Internet Directory (OID)".Table 5-3 shows supported OID versions when migrating from Oracle Database Lite 10.3.0.3 to Oracle Database Mobile Server 11g. Refer to Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management 11g Release 1 (11.1.1) for detailed instructions on how to upgrade OID.
Table 5-3 Upgrading OID When Migrating Oracle Database Lite 10.3.0.3.0 with OID to Oracle Database Mobile Server 11.1.0.0.0 or 11.2.0.0.0
| Installed Application Server and OID Version | Upgrade To OID Version |
|---|---|
|
Oracle iAS 10.1.3.5.0 with OID 10.1.2 |
Oracle iAS 10.1.3.5.0 with OID 10.1.4 or OID 11.1.1.5 |
|
Oracle iAS 10.1.3.5.0 with OID 10.1.4 |
You can continue using Oracle iAS 10.1.3.5.0 with OID 10.1.4 or upgrade to OID 11.1.1.5 |
|
WebLogic 11g Release 1 with OID 10.1.4 |
You can continue using WebLogic 11g Release 1 with OID 10.1.4 or upgrade to OID 11.1.1.5 |
If you are using Oracle Database Lite 10.3.0.3.0 Mobile Server Standalone, migrate to one of the supported application servers on a separate ORACLE_HOME: Apache TomEE, OracleAS, WebLogic, or Glassfish. See Section 3.3.3, "Certified Application Server Configurations" for details on supported application servers.
If you are currently using WebLogic or OracleAS, you can do one of the following:
You can continue to use the installed application server as your application server as long as the version is a supported version.
If you plan to upgrade Oracle Database Lite 10.3.0.3.0 to Oracle Database Mobile Server 11.1.0.0.0, and switch to a different application server, you must install Mobile Server in a separate ORACLE_HOME.
If you plan to upgrade Oracle Database Lite 10.3.0.3.0 to Oracle Database Mobile Server 11.2.0.0.0, and switch to a different application server, you can install Mobile Server either in the same ORACLE_HOME or in a separate ORACLE_HOME.
See Section 5.1.3.1.1, "Migrating in the Same ORACLE_HOME" and Section 5.1.3.1.2, "Migrating in a Separate ORACLE_HOME" for additional information.
If you have OracleAS installed as the application server, but you want to migrate to WebLogic Server, refer to Oracle WebLogic SmartUpgrade directions on the following site:
http://www.oracle.com/technetwork/middleware/downloads/smartupgrade-085160.html
You must apply all patches before upgrading from Oracle Database Lite 10.3.0.3.0 to Oracle Database Mobile Server 11g Release 1.
If you have multiple mobile servers in a farm that use the same mobile server repository on a back-end Oracle database, perform the following:
Shut down all mobile servers before you start the upgrade.
Upgrade one of these mobile servers and the mobile server repository.
Upgrade each additional mobile server that uses the repository.
Restart all mobile servers.
The following sections describe how to migrate from Oracle Database Lite 10.3.0.3.0 to the Oracle Database Mobile Server 11.1.0.0.0 or 11.2.0.0.0:
Migrating Oracle Database Lite 10.3.0.3.0 to Oracle Database Mobile Server 11.1.0.0.0 or 11.2.0.0.0 is supported in the same or separate ORACLE_HOME.
Refer to Table 5-1 and Table 5-2 for the supported cases for migrating to Oracle Database Mobile Server 11.1.0.0.0 and 11.2.0.0.0 respectively in the same ORACLE_HOME.
Install Oracle Database Mobile Server 11.1.0.0.0 or 11.2.0.0.0 in ORACLE_HOME.
Launch Oracle Universal Installer, on Select Installation Type page, select Mobile Server.
On the Specify Home Details page, choose the same ORACLE_HOME as your previous installation.
Follow the instructions to complete the install.
Execute the Repository Wizard to upgrade the repository.
If you choose to run Repository Wizard during install, the Repository Wizard launches automatically.
Alternatively, you can launch the Repository Wizard after installation. Refer to Section 5.1.3.2, "Upgrade Your Mobile Server Repository".
Execute the application upgrade assistant to upgrade user applications to the new repository. For more information, refer to Section 5.1.4, "Upgrade Your Existing Applications".
Refer to Table 5-1 and Table 5-2 for the supported cases for migrating to Oracle Database Mobile Server 11.1.0.0.0 and 11.2.0.0.0 respectively in a separate ORACLE_HOME.
Install Oracle Database Mobile Server 11.1.0.0.0 or 11.2.0.0.0 in a new ORACLE_HOME.
Launch Oracle Universal Installer, on Select Installation Type page, select Mobile Server.
On the Specify Home Details page, choose a new ORACLE_HOME that is different from your previous installation
Follow the instructions to complete the install.
Execute the Repository Wizard to upgrade the repository.
If you choose to run Repository Wizard during install, the Repository Wizard launches automatically.
Alternatively, you can launch Repository Wizard after installation. Refer to Section 5.1.3.2, "Upgrade Your Mobile Server Repository".
Execute the application upgrade assistant to upgrade user applications to the new repository. For more information, refer to Section 5.1.4, "Upgrade Your Existing Applications".
Uninstall the previous mobile server version from the old ORACLE_HOME.
Launch Oracle Universal Installer, click Deinstall Products.
Choose the previous mobile server that you want to uninstall, and click Remove.
During installation of Oracle Database Mobile Server, the Repository Wizard detects if Oracle Database Lite 10.3.0.3.0 is installed and initiates the upgrade process, as follows:
Note:
If you need to start the Repository Wizard independent of the install process, execute one of the following:Windows: %ORACLE_HOME%\Mobile\Server\admin\repwizard.bat
Linux: $ORACLE_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 to install the sample applications. Click Next.
A summary screen appears. Click Next.
After the repository is upgraded, click Finish.
In Oracle Database Mobile Server 11g, the repository location is set to %ORACLE_HOME%\Mobile\Server\admin\repository directory, which is different from previous releases.
You can upgrade all existing applications with the Application Upgrade Assistant. Since the Oracle Database Mobile Server 11g repository is in a new location, the Application Upgrade Assistant moves applications from the old to the new repository location.
The Application Upgrade Assistant is located as follows:
On Windows:
%ORACLE_HOME%\Mobile\Server\admin\ApplicationUpgradeAssistant.bat
On Linux:
$ORACLE_HOME/mobile/server/admin/ApplicationUpgradeAssistant.sh
On the command-line, supply the following:
Mobile server repository name and password
The ORACLE_HOME for the old mobile server repository
The ORACLE_HOME for the new mobile server repository
Note:
If you are upgrading from the sameORACLE_HOME, specify the same values for the old ORACLE_HOME and 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\ora10gR3 and the new ORACLE_HOME is C:\Oracle\Middleware\wlserver_10.3, execute the Application Upgrade Assistant as follows:
ApplicationUpgradeAssistant mobileadmin manager
C:\Oracle\ora10gR3 C:\Oracle\Middleware\wlserver_10.3
The Application Upgrade Assistant will not upgrade applications for de-supported platforms, as follows:
Applications on desupported platforms on Oracle Lite, Web-to-Go, OC4J, and BC4J platforms will not be upgraded.
The default system folders and default application files for previous releases will not be upgraded, which includes admin-web, msadmin, olsetup, devmgr, META-INF, plugins, setup, and webtogo.
In Oracle Database Mobile Server 11g, the Mobile Manager application is named mobile. However, if you deployed an application with the same name in Oracle Database Lite, the Application Upgrade Assistant will not upgrade it due to a name conflict. You will need to manually change your application name and redeploy it on the new Mobile Server.
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.
For more information, refer to Section 4.3.1.6 " Managing OID Users in the Mobile Server" in the Oracle Database Mobile Server Administration and Deployment Guide.
Berkeley DB and SQLite Mobile Clients installed with the Oracle Database Lite Mobile Server version 10.3.0.3.0 can be upgraded to Oracle Database Mobile Server 11g.
Table 5-4 shows what mobile client platforms can be upgraded to the Oracle Database Mobile Server 11.1.0.0.0 or 11.2.0.0.0.
Table 5-4 Upgrading Mobile Clients
| Client Device Platform | Upgrade Instructions |
|---|---|
|
SQLite or Berkeley DB Mobile Clients on Win32 |
Run |
|
SQLite or Berkeley DB Mobile Clients on Pocket PC 6.0, 6.5 |
Run |
|
SQLite or Berkeley DB Mobile Clients on Linux |
Run |
|
SQLite Mobile Client on Android |
Run |
|
SQLite Mobile Client on Blackberry |
De-install the previous client version and install the appropriate 11g mobile client |
|
SQLite or Berkeley DB Mobile Clients on Pocket PC 5.0 |
Run update.exe or msync.exe, which launches update.exe after the synchronization completes. This is only supported to upgrade from 10.3.0.3.0 to 11.2.0.0.0 |
To upgrade mobile client on Android, if server port is changed after server upgrade, please modify SERVER_URL parameter in [NETWORK] section in devmgr.ini before running update. Usually you can find devmgr.ini at /mnt/sdcard/oracle.mobileclient.To upgrade mobile clients on Win32, Windows Mobile and Linux platforms, please follow the instructions below, which apply to these upgrade scenarios:
Upgrade BDB or SQLite client from 10.3.0.3.0 to 11.1.0.0.0
Upgrade BDB or SQLite client from 10.3.0.3.0 to 11.2.0.0.0
Shutdown your applications.
Check available software update and install it. Ensure that your device is enabled to receive software updates from the Mobile Server. You can either run update.exe or msync.exe, which automatically launches update.exe after the synchronization completes.
Update.exe might not work if the server port is changed after Mobile Server upgrade. In this case follow the instructions below to run msync.exe:
Write OSE.FILES=YES in [DEFAULT] section in ose.ini. You can set OSE.FILES=NO if you want to disable OSE.FILES option after the client upgrade process completes.
Run msync.exe and specify the new server URL in 'Server URL' field, so that the update.exe is able to connect to Mobile Server with the new server URL. The update.exe should find available software updates on the server and display the option for you to install the update.
After you update your mobile client, check if NAME and TYPE parameters are written in [DMC] section in devmgr.ini. If they are missing, copy them from the old configuration file polite.ini.
If you are using the SQLite client, the client upgrade process is completed. If you are using the BDB client upgraded from 10.3.0.3.0 to 11.1.0.0.0 or 11.2.0.0.0, double check if the old BDB environment files are removed during client upgrade. If not, follow the instructions to finish the upgrade process:
Shutdown your applications and SyncAgent if it is running.
Backup the BDB databases.
Remove environment files __db.xxx (xxx stands for 3 digits) in *.db-journal folders from where BDB databases are stored.
Restart your application and SyncAgent if needed.
For Web-to-Go, OC4J, BC4J, and Branch Office Mobile Client platforms, there are no upgrade options since these client device platforms are no longer supported in Oracle Database Mobile Server 11g.
Table 5-5 shows how to migrate de-supported Mobile client platforms to available platforms in Oracle Database Mobile Server 11g Release 1 or 11g Release 2.
Note:
Do not cancel in the middle of the upgrade process.Table 5-5 Upgrading from De-Supported Mobile Client Platforms
| De-Supported Mobile Client Platform | Upgrade to the Available Platform |
|---|---|
|
SQLite or Berkeley DB Mobile Clients on Pocket PC 2003 |
SQLite or Berkeley DB Mobile Clients on Pocket PC 6.0 |
|
SQLite or Berkeley DB Mobile Clients on Pocket PC 5.0 |
SQLite or Berkeley DB Mobile Clients on Pocket PC 6.0 |
Note:
SQLite and Berkerley DB Mobile Clients on Pocket PC 5.0 are supported in Oracle Database Mobile Server 11g Release 2, but not supported in 11g Release 1.If your device is Windows Mobile 6.0 or later, you must perform the following after the CAB files are downloaded to the device:
Click on the CAB files to extract the files to the device.
Start the update by executing update.exe, which detects available upgrade options and prompts the user to upgrade.
If you do not upgrade mobile client devices for de-supported platforms, you can still synchronize data and perform adminstration duties with the following restrictions:
You can continue to administer de-supported client platforms, and they will appear in the platform tabs in the Mobile Manager. However, these platforms will not be available on the setup page for you to create new clients using these platforms.
The applications that already exist on the de-supported client platforms will still execute as expected. You may also apply any patches for the application. However, you cannot deploy any new applications to that platform.
If you do upgrade the client platform, you must re-package and re-publish each application as a new application for the new client platform.
If you have Oracle Database Lite 10g Release 1 or 2, you must upgrade to the latest version. The following sections describe the steps for upgrading your software:
Section 5.2.1, "Supported Versions for Upgrading Oracle Database Lite"
Section 5.2.8, "Remove Duplicate Mobile Server IDs from the Repository"
Upgrading Oracle Database Lite from 10g Release 1 or 2 to 10g Release 3 is supported in the same or a separate ORACLE_HOME from the previous installation. Before you upgrade your Mobile Server from Oracle Database Lite 10g Release 2 to Release 3, be sure to apply all patches first.
The following sections describe how to perform the upgrade:
The Oracle Universal Installer detects the earlier version and uninstalls this version. All deployed application files and existing configuration files remain to be used by the new installation. When prompted, you can re-execute the Repository Wizard, which detects that the repository exists and runs the repository upgrade instead of the install.
These steps are the standard steps to follow when upgrading a Mobile Server in a separate ORACLE_HOME directory.
Install the desired version of Oracle Application Server into the new ORACLE_HOME. This step is optional.
Install Mobile Server in the new ORACLE_HOME.
Execute the Repository Wizard to upgrade the repository.
Execute the application upgrade assistant.
Uninstall the previous Mobile Server version from the old ORACLE_HOME.
Table 5-6 details what versions of Oracle Database Lite and OracleAS installation can be upgraded to Oracle Database Lite 10.3.0.3
Table 5-6 Upgrading Oracle Database Lite 10.1.x to Oracle Database Lite 10.3.0.3
| From <Version> | To Oracle Database Lite 10.3.0.3 Base | Same Oracle Home | Separate Oracle Home |
|---|---|---|---|
|
10g R1 Standalone |
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
Oracle WebLogic Server 11g Rel 1, Oracle WebLogic Server 12c |
Not Supported |
Supported |
|
|
10g R1 with Oracle iAS 9.0.2 |
Any |
Not Supported |
Not Supported |
|
10g R1 with Oracle iAS 9.0.3 |
Any |
Not Supported |
Not Supported |
|
10g R1 with Oracle iAS 9.0.4 |
Any |
Not Supported |
Not Supported |
|
10g R1 with Oracle iAS 10.1.2 with patch 5723922 |
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
Oracle WebLogic Server 11g Rel 1, Oracle WebLogic Server 12c |
Not Supported |
Supported |
For Oracle Database Lite 10.0, support was removed for installations with Oracle iAS 9.0.2, 9.0.3 and 9.0.4. In addition, the OC4J version in the standalone installation is Oracle iAS version 9.0.4. You can apply the patch that enables support for Oracle iAS 10.1.2 and upgrades the version of standalone OC4J to Oracle iAS 10.1.2. The patch is 5723922: Needs migration path from Oracle iAS and OC4J 9.0.4.x to Oracle iAS 10.1.2.
In Oracle Database Lite 10.0, the path used was mobile/j2ee/home. However, in Oracle Database Lite 10.3, this was modified to use the mobile/j2ee/mobileserver path. This may cause problems with certain Oracle iAS upgrades.
Table 5-7 Upgrading Oracle Database Lite 10.2.x to Oracle Database Lite 10.3.0.3
| From <Version> | To Oracle Database Lite 10.3.0.3 Base | Same Oracle Home | Separate Oracle Home |
|---|---|---|---|
|
10g R2 Standalone |
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
Oracle WebLogic Server 11g Rel 1, Oracle WebLogic Server 12c |
Not Supported |
Supported |
|
|
10g R2 with Oracle iAS 9.0.4 |
Oracle iAS 10.1.3.5.0 |
Not Supported |
Not Supported |
|
Oracle WebLogic Server 11g Rel 1, Oracle WebLogic Server 12c |
Not Supported |
Not Supported |
|
|
10g R2 with Oracle iAS 10.1.2 with patch 5723922 |
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
Oracle WebLogic Server 11g Rel 1, Oracle WebLogic Server 12c |
Not Supported |
Supported |
For Oracle Database Lite 10.2, support was removed for installations with Oracle iAS 9.0.4. In addition, the OC4J version in the standalone installation is Oracle iAS version 9.0.4. You can apply the patch that enables support for Oracle iAS 10.1.2 and upgrades the version of standalone OC4J to Oracle iAS 10.1.2. The patch is 5723922: Needs migration path from Oracle iAS and OC4J 9.0.4.x to Oracle iAS 10.1.2.
Table 5-8 Upgrading Oracle Database Lite 10g Release 3 to Oracle Database Lite 10.3.0.3
| From <Version> | To Oracle Database Lite 10.3.0.3 Base | Same Oracle Home | Separate Oracle Home |
|---|---|---|---|
|
10.3.0.1 Standalone |
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
Oracle WebLogic Server 11g Rel 1, Oracle WebLogic Server 12c |
Not Supported |
Supported |
|
|
10.3.0.1 with Oracle iAS 10.1.2 |
Standalone |
Not Supported |
Supported |
|
Oracle iAS 10.1.2.0.2 |
Supported |
Supported |
|
|
Oracle iAS 10.1.3.1.0 |
Not Supported |
Supported |
|
|
10.3.0.1 with Oracle iAS 10.1.3 |
Oracle iAS 10.1.3.5.0 |
Supported |
Supported |
|
Oracle WebLogic Server 11g Rel 1, Oracle WebLogic Server 12c |
Supported |
Supported |
|
|
10.3.0.1 with Oracle iAS 10.1.3.1 |
Oracle iAS 10.1.3.5.0 |
Supported |
Supported |
|
Oracle WebLogic Server 11g Rel 1, Oracle WebLogic Server 12c |
Supported |
Supported |
Table 5-9 Upgrading Oracle Database Lite with OID to Oracle Database Lite 10.3.0.3
| From <Version> | From OID <Version> | To OID <Version> | Supported? |
|---|---|---|---|
|
5.0.2.10 |
Oracle iAS 9.0.2 |
Any |
Not Supported |
|
10.0.0 |
Oracle iAS 9.0.2 |
Any |
Not Supported |
|
Oracle iAS 9.0.3 |
Any |
Not Supported |
|
|
Oracle iAS 9.0.4 |
Any |
Not Supported |
|
|
Oracle iAS 10.1.2. |
Oracle iAS 10.1.2 with OID 10.1.2 |
Supported |
|
|
Oracle iAS 10.1.2. |
Oracle iAS 10.1.3.5.0 with OID 10.1.4 |
Supported |
|
|
10.2.0.2 |
Oracle iAS 9.0.4 |
Any |
Not Supported |
|
Oracle iAS 10.1.2 with OID 10.1.2 |
Oracle iAS 10.1.2.0.2 with OID 10.1.2 |
Supported |
|
|
10.3.0.1 |
Oracle iAS 10.1.2 with OID 10.1.2 |
Oracle iAS 10.1.2 with OID 10.1.2 |
Supported |
|
Oracle iAS 10.1.3.1 with OID 10.1.4 |
Oracle iAS 10.1.3.x with OID 10.1.4 |
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 or 2 to the Release 3 in the same Oracle Home OR you can install the Release 2 of Oracle Database Lite in a separate Oracle home than your Database Lite 10g Release 1 or 2 home.
See Chapter 4, "Installation of Oracle Database Mobile Server" for instructions on how to install Oracle Database Lite. When the Repository Wizard is executed, see Chapter 5, "Upgrade Your Mobile Server Repository" for directions on how to upgrade the repository on the back-end database.
When you migrate any of your mobile servers to an instance running on a WebLogic Server, the the mobile server URL and port may change. Each client application, including msync.exe, that interacts with these mobile servers must apply the new server URL on the client side.
When the mobile server URL change occurs, perform the following on each client:
Stop all processes on the client.
Modify the URL on the client by opening msync.exe, change the server URL, and apply the changes.
Perform a synchronization.
During installation of Oracle Database Lite 10g Release 3, the Repository Wizard detects if Release 1 or 2 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\repwizardEnter 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 5.2.2, "Pre-Upgrade Instructions".
You have to upgrade existing applications only if you installed Oracle Database Lite 10g Release 3 in a separate ORACLE_HOME than Oracle Database Lite 10g Release 1 or 2. Thus, once you have installed the Oracle Database Lite 10g Release 3 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 or 2 to your the new ORACLE_HOME for Oracle Database Lite 10g Release 3.
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 and 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 3, or install new sample applications. The Release 1 or 2 samples will still work in Release 3 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
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.
When you migrate users from a mobile server repository into OID, you cannot have duplicate users in OID. So, if you migrate users from two repositories into a single OID, and you have users with the same name, but different passwords on two separate repositories, the user that is first migrated into OID is the one that is valid. The second attempt to migrate an existing username into OID from a different repository will not migrate and no message is provided. This can be a problem if you have two users in different repositories with different passwords.
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.
The following sections describe how to migrate your users based on which Oracle Application Server you have installed:
Section 5.2.6.1, "Mobile Server Installed On Oracle Application Server 10.1.2.0.0"
Section 5.2.6.2, "Mobile Server Installed on Oracle Application Server 10.1.3.1.0 or Higher"
Perform the following to migrate your users to OID:
Set the IAS_MODE 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> <OID admin name> <OID subscriber name>
For example, the default setting would be:
oiduser <ORACLE_HOME> mobileadmin manager 389 ldap://myhost-pc1.com
welcome1 orcladmin dc=us,dc=oracle,dc=com
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> <OID admin name> <OID subscriber name>
where the common password is specified by you.
The oiduser tool generates the LDAP.bat, oiduser.dat and mobile_oid_user 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 LDAP.bat executable uses oiduser.dat and the mobile_oid_user executable uses the generated 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 LDAP.bat from the command-line with the oiduser.dat as input on the machine where the application server resides. This creates the oiduserfile.Idif file.
Execute the mobile_oid_user file from the command-line on the application server 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.
Perform the following to enable user authentication from OID on the Mobile Server:
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.
Perform the following to migrate your users to OID:
Set the IAS_MODE parameter in the webtogo.ora file to YES.
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> <OID admin name> <OID subscriber name>
For example, the default setting would be:
oiduser <ORACLE_HOME> mobileadmin manager 389 ldap://myhost-pc1.com
welcome1 orcladmin dc=us,dc=oracle,dc=com
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> <OID admin name> <OID subscriber name>
where the common password is specified by you.
All users from the Mobile Server Repository are now migrated to the OID with the required passwords.
If you want to enable Oracle Single Sign on on the Mobile Server then perform the following:
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 or 2 from your system. Only perform these steps if you have installed Oracle Database Lite 10g Release 3 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 or 2 installation. Click Installed Products.
On the Inventory screen, select the '+' next to the ORACLE_HOME for your 10g Release 1 or 2 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 or 2 to Release 3, 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
The upgrade from Oracle Database Mobile Server 11g Release 1 to 11g Release 2 is straightforward. You can upgrade Oracle Database Mobile Server either in the same ORACLE_HOME or in a separate ORACLE_HOME. Table 5-10 shows what software is supported when upgrade from an Oracle Database Mobile Server 11g Release 1 and its installed application server to Oracle Database Mobile Server 11g Release 2 and supported application servers.
Table 5-10 Upgrading Oracle Database Mobile Server 11.1.0.0.0 to 11.2.0.0.0
| From Oracle Database Mobile Server 11g Release 1 | To Oracle Database Mobile Server 11g Release 2 | Same Oracle Home | Separate Oracle Home |
|---|---|---|---|
|
Oracle Database Mobile Server 11.1.0.0.0 with GlassFish 3.1 |
Oracle WebLogic Server 11g Release 1, Oracle WebLogic Server 12c |
Supported |
Supported |
|
GlassFish 3.1 |
Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Supported |
Supported |
|
|
Apache TomEE 1.0 |
Supported |
Supported |
|
|
Oracle Database Mobile Server 11.1.0.0.0 with WebLogic 11g Release 1 |
Oracle WebLogic Server 11g Release 1, Oracle WebLogic Server 12c |
Supported |
Supported |
|
GlassFish 3.1 |
Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Supported |
Supported |
|
|
Apache TomEE 1.0 |
Supported |
Supported |
|
|
Oracle Database Mobile Server 11.1.0.0.0 with Oracle iAS 10.1.3.5.0 |
Oracle WebLogic Server 11g Release 1, Oracle WebLogic Server 12c |
Supported |
Supported |
|
GlassFish 3.1 |
Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Supported |
Supported |
|
|
Apache TomEE 1.0 |
Supported |
Supported |
Refer to Section 5.1.2, "Mobile Server Farm Upgrade"for instructions on how to upgrade Mobile Server in a farm.
The following sections describe how to upgrade from Oracle Database Mobile Server 11.1.0.0.0 to Oracle Database Mobile Server 11.2.0.0.0:
Upgrading Oracle Database Mobile Server 11.1.0.0.0 to 11.2.0.0.0 is supported in the same or in a separate ORACLE_HOME. For more information, see:
Refer to Table 5-10 for the supported cases for upgrading Oracle Database Mobile Server 11.1.0.0.0 to 11.2.0.0.0 in the same ORACLE_HOME.
Install Oracle Database Mobile Server 11.2.0.0.0 in the same ORACLE_HOME.
Launch Oracle Universal Installer. On Select Installation page, select "Mobile Server".
On the "Specify Home Details" page, choose the same ORACLE_HOME as your previous installation.
Follow the instructions to complete the install.
Execute the Repository Wizard to upgrade the repository.
If you choose to run Repository Wizard during install, the Repository Wizard launches automatically.
Alternatively, you can launch the Repository Wizard after installation. Refer to Section 5.1.3.2, "Upgrade Your Mobile Server Repository".
Refer to Table 5-10 for the supported cases for upgrading Oracle Database Mobile Server 11.1.0.0.0 to 11.2.0.0.0 in a separate ORACLE_HOME.
Install Oracle Database Mobile Server 11.2.0.0.0 in a new ORACLE_HOME.
Launch Oracle Universal Installer, on Select Installation Type page, select "Mobile Server".
On the "Specify Home Details" page, choose a new ORACLE_HOME that is different from your previous installation.
Follow the instructions to complete the install.
Execute the Repository Wizard to upgrade the repository.
If you choose to run Repository Wizard during install, the Repository Wizard launches automatically.
Alternatively, you can launch Repository Wizard after installation. Refer to Section 5.1.3.2, "Upgrade Your Mobile Server Repository".
Execute the application upgrade assistant to upgrade user applications to the new repository. For more information, refer to Section 5.1.4, "Upgrade Your Existing Applications".
Uninstall the previous Mobile Server from the old ORACLE_HOME.
Launch Oracle Universal Installer, click "Deinstall Products".
Choose the previous mobile server that you want to uninstall, and click "Remove".
For information on upgrading the mobile server repository, refer to Section 5.1.3.2, "Upgrade Your Mobile Server Repository".
For information on upgrading existing applications, refer to Section 5.1.4, "Upgrade Your Existing Applications".
Berkeley DB and SQLite Mobile Clients installed with the Oracle Database Mobile Server 11.1.0.0.0 can be upgraded to 11.2.0.0.0. Table 5-11 shows the mobile client platforms that can be upgraded to 11.2.0.0.0.
Table 5-11 Upgrading Mobile Clients
| Client Device Platform | Upgrade Instructions |
|---|---|
|
SQLite or Berkeley DB Mobile Clients on Win32 |
Run update.exe or msync.exe, which launches update.exe after the synchronization completes. |
|
SQLite or Berkeley DB Mobile Clients on Pocket PC 6.0, 6.5 |
Run update.exe or msync.exe, which launches update.exe after the synchronization completes. |
|
SQLite or Berkeley DB Mobile Clients on Linux |
Run update or msync, which launches update after the synchronization completes. |
|
SQLite Mobile Clients on Android |
Run update. |
|
SQLite Mobile Clients on BlackBerry |
De-install the previous client version and install the 11.2 mobile client. |
To upgrade mobile client on Android, if server port is changed after server upgrade, please modify SERVER_URL parameter in [NETWORK] section in devmgr.ini before running update. Usually you can find devmgr.ini at /mnt/sdcard/oracle.mobileclient
To upgrade mobile clients on Win32, Windows Mobile and Linux platforms, please follow the instructions below:
Shutdown your applications.
Check available software update. Ensure that your device is enabled to receive software updates from the Mobile Server. You can either run update.exe or msync.exe, which automatically launches update.exe after the synchronization completes.
Update.exe might not work if the server port is changed after Mobile Server upgrade. In this case follow the instructions below to run msync.exe:
Run msync.exe and specify the new server URL in 'Server URL' field, so that the update.exe is able to connect to Mobile Server with the new server URL.
The update.exe will find the available software updates on the server and display the option for you to install the update.
Install the software update. A new mobile client would be downloaded and installed.
Restart you applications.