| Oracle® Database Lite Getting Started Guide Release 10.3 Part Number E12080-02 |
|
|
View PDF |
| Oracle® Database Lite Getting Started Guide Release 10.3 Part Number E12080-02 |
|
|
View PDF |
The following sections describe the steps for upgrading your Oracle Database Lite software:
Section 5.1, "Upgrade Your Oracle Database Lite from 5.0.2.x to 10g Release 3"
Section 5.2, "Upgrade Your Oracle Database Lite from 10g Release 1 or 2 to 10g Release 3"
The following sections describe the steps for upgrading your Oracle Database Lite software from 5.0.2.x to 10g Release 3:
Section 5.1.1, "What 5.0.2.x Versions Can I Upgrade to 10g Release 3?"
Section 5.1.2, "Pre-Upgrade Instructions for the 5.0.2.x Version"
Section 5.1.3, "Upgrade Your 5.0.2.x Version Mobile Server Repository"
Section 5.1.4, "Upgrade Your 5.0.2.x Version Existing Applications"
Section 5.1.5, "Upgrading BC4J Oracle Lite Mobile Client 5.0.2.x to Version 10g Release 2"
Section 5.1.7, "Use the Appropriate Context for Your Mobile Server"
Section 5.1.9, "Post-Upgrade Instructions for 5.0.2.x Version"
Section 5.1.11, "New Consolidator Sequence Properties Added During Upgrade"
Section 5.1.12, "Upgrade Oracle Database Lite Release 2 to Release 3"
Upgrading Oracle Database Lite from 5.0.2.x to 10g Release 3 can be performed on an installation in the same or a separate ORACLE_HOME. Table 5-1 details what version of Oracle Database Lite and iAS installation can be upgraded to Oracle Database Lite 10g Release 3.
Table 5-1 Upgrading 5.0.2.x Oracle Database Lite to 10.3.0.3
| From Installation <Version> | To Oracle Database Lite 10.3.0.3 Base | Same Oracle Home | Different Oracle Home |
|---|---|---|---|
|
5.0.2.x Standalone |
Standalone |
Not Supported |
Supported |
|
Oracle iAS 10.1.2.0.2 |
Not Supported |
Not Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Not Supported |
Not Supported |
|
|
Oracle WebLogic Server 11g R1 |
Not Supported |
Not Supported |
|
|
5.0.2.x and OAS 1.0.2.2 |
Standalone |
Not Supported |
Not Supported |
|
Oracle iAS 10.1.2.0.2 |
Not Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
|
Oracle WebLogic Server 11g R1 |
Not Supported |
Supported |
|
|
5.0.2.x and Apache 1.3.27 |
Any |
Not Supported |
Not Supported |
|
5.0.2.x and Oracle iAS 9.0.2.1 |
Any |
Not Supported |
Not Supported |
Note:
Applications use Oracle iAS 1.0.2.2 to enable SSL with 5.0.2; therefore, Apache or Oracle iAS 9.0.2 based configurations are not 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 4, "Installation of Oracle Database Lite" for instructions on how to install Oracle Database Lite. When the Repository Wizard is executed, see Section 5.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, execute
ORACLE_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 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 5.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
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.
Note:
Only the Mobile Development Kit has the full National Language Support for (Traditional and Simplified) Chinese, Japanese, and Korean (CJK). All other components, including Mobile clients, support CJK without the Traditional Chinese language. However, the Simplified Chinese language is supported.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, and the old Oracle Home. The new Oracle Home destination is taken from the environment variables. 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
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 Oracle Lite 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 2, 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 Oracle Lite BC4J Mobile client using the Oracle Lite 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 Oracle Lite 5.0.2.x BC4J Mobile client username and password.
After all the Oracle Lite 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 Oracle Application Server.
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 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 with either randomly-generated passwords or a common password, as follows:
Note:
The existing password will not be migrated. Instead, either choose to have the new password randomly generated or to use a common password, such asadmin.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 ldap://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.
Note:
If logging in to Mobile Manager results in a page that contains one workspace inside another workspace, then refresh the browser.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.
For full details on sequences, see Section 5.6, "Create a Sequence" in the Oracle Database Lite Developer's Guide.
Once you have completed the upgrade to Oracle Database Lite Release 2, then upgrade this version to Release 3, as described in Section 5.2, "Upgrade Your Oracle Database Lite from 10g Release 1 or 2 to 10g Release 3".
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, "To What Versions Can I Upgrade Oracle Database Lite?"
Section 5.2.6, "Upgrade Branch Office 10g Release 1 or 2 to version 10g Release 3"
Section 5.2.9, "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. See the Release Notes for the required patch numbers.
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-2 details what versions of Oracle Database Lite and OracleAS installation can be upgraded to Oracle Database Lite 10.3.0.3
Table 5-2 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 | Different Oracle Home |
|---|---|---|---|
|
10g R1 Standalone |
Standalone |
Supported |
Supported |
|
Oracle iAS 10.1.2.0.2 |
Not Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
|
Oracle WebLogic Server 11g Rel 1 |
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 |
Standalone |
Not Supported |
Supported |
|
Oracle iAS 10.1.2.0.2 |
Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
|
Oracle WebLogic Server 11g Rel 1 |
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-3 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 | Different Oracle Home |
|---|---|---|---|
|
10g R2 Standalone |
Standalone |
Supported |
Supported |
|
Oracle iAS 10.1.2.0.2 |
Not Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
|
Oracle WebLogic Server 11g Rel 1 |
Not Supported |
Supported |
|
|
10g R2 with Oracle iAS 9.0.4 |
Standalone |
Not Supported |
Not Supported |
|
Oracle iAS 10.1.2.0.2 |
Not Supported |
Not Supported |
|
|
Oracle iAS 10.1.3.1.0 |
Not Supported |
Not Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Not Supported |
Not Supported |
|
|
Oracle WebLogic Server 11g Rel 1 |
Not Supported |
Not Supported |
|
|
10g R2 with Oracle iAS 10.1.2 with patch 5723922 |
Standalone |
Not Supported |
Supported |
|
Oracle iAS 10.1.2.0.2 |
Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
|
Oracle WebLogic Server 11g Rel 1 |
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-4 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 | Different Oracle Home |
|---|---|---|---|
|
10.3.0.1 Standalone |
Standalone |
Supported |
Supported |
|
Oracle iAS 10.1.2.0.2 |
Not Supported |
Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Not Supported |
Supported |
|
|
Oracle WebLogic Server 11g Rel 1 |
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 |
Standalone |
Not Supported |
Not Supported |
|
Oracle iAS 10.1.2.0.2 |
Not Supported |
Not Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Supported |
Supported |
|
|
Oracle WebLogic Server 11g Rel 1 |
Supported |
Supported |
|
|
10.3.0.1 with Oracle iAS 10.1.3.1 |
Standalone |
Not Supported |
Supported |
|
Oracle iAS 10.1.2.0.2 |
Not Supported |
Not Supported |
|
|
Oracle iAS 10.1.3.5.0 |
Supported |
Supported |
|
|
Oracle WebLogic Server 11g Rel 1 |
Supported |
Supported |
Table 5-5 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 Lite" 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
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 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
If you have Oracle Database Lite 10g Release 1 or 2, then upgrade your Branch Office to 10g Release 3, as follows:
Note:
These steps assume that you have a 10g Release 1 or 2 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 3 Mobile Server in the same ORACLE_HOME directory where you installed Release 1 or 2.
Stop the Branch Office client executing as a Windows Service.
From the Branch Office client machine, which is being migrated to 10g Release 3, point your browser to http://<hostname>:<port>/webtogo/setup on the Mobile Server 10g Release 3.
Click on "Oracle Lite Branch Office Client" link from the list of Mobile clients. Download and save the setup.exe file into the BO_CLIENT_HOME\bin directory. Overwrite the existing setup.exe file.
Open a command prompt, navigate to the BO_CLIENT_HOME\bin directory, and execute the update.exe command to start the upgrade process. Alternatively, you can open Programs->Oracle Database Lite->Oracle Lite Update.
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.7.1, "Mobile Server Installed On Oracle Application Server 10.1.2.0.0"
Section 5.2.7.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.
Note:
If logging in to Mobile Manager results in a page that contains one workspace inside another workspace, then refresh the browser.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.
Note:
If logging in to Mobile Manager results in a page that contains one workspace inside another workspace, then refresh the browser.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 following sections describe how to upgrade each Oracle Lite Mobile client platform:
Section 5.3.1, "Upgrade the Oracle Lite Mobile Client Version 5.0.2.10 to Version 10g Release 3"
Section 5.3.2, "Upgrade the Oracle Lite Mobile Client 10g Release 1 or 2 to 10g Release 3"
Section 5.3.3, "Upgrade the Oracle Lite Mobile Clients from De-Supported Mobile Client Platforms"
Table 5-6 shows how each Oracle Lite Mobile client platform updates to the latest version.
Table 5-6 Upgrade Mobile Client 5.0.2.10 to 10g Release 3
| Mobile Client Platform | Upgrade Instructions |
|---|---|
|
Web-to-Go |
Automatic. User is prompted for username/password. |
|
Branch Office |
Supported, but manual steps required. See Section 5.1.6, "Upgrading 5.0.2.x Version Branch Office". |
|
BC4J |
Supported, but manual steps required. See Section 5.1.5, "Upgrading BC4J Oracle Lite Mobile Client 5.0.2.x to Version 10g Release 2". |
|
Win32 |
Not supported |
|
WinCE |
Supported from 5.0.2.9.0 and higher. Run |
|
Linux native clients |
Not applicable |
|
Linux Web-to-Go clients |
Not applicable |
Table 5-7 shows how each Oracle Lite Mobile client platform updates to the latest version.
Table 5-7 Upgrade Mobile Client Release 1 or 2 to 10g Release 3
| Mobile Client Platform | Upgrade Instructions |
|---|---|
|
Web-to-Go |
Automatic. |
|
OC4J |
Automatic. After the Mobile Client for OC4J is upgraded, the Web browser may not display the login page automatically. The user needs to click on the desktop browser shortcut for Mobile client for OC4J to open the login page. |
|
Branch Office |
Supported, but manual steps required. See Section 5.2.6, "Upgrade Branch Office 10g Release 1 or 2 to version 10g Release 3". |
|
BC4J |
Automatic. |
|
Win32 |
Supported. Run |
|
WinCE |
Supported. Run |
|
Linux native clients |
Not applicable for 10.0; for the 10.2 version, run |
|
Linux Web-to-Go clients |
Not applicable for 10.0; for the 10.2 version, it is automatic. |
For the Oracle Lite Palm, PPC2003 Emulator, and PPC2000 ARM Mobile client platforms, there is no upgrade option. These client device platforms are no longer supported for Oracle Database Lite.
Table 5-8 displays how you can migrate the following de-supported Mobile client platforms to currently available platforms:
Table 5-8 Upgrading De-Supported Mobile Client Platforms
| De-Supported Client Platform | Upgrade to this Available Platform |
|---|---|
|
Oracle Lite PPC2003 XScale |
Oracle Lite PPC2003 ARMV4 |
|
Oracle Lite WCESTD42 ARMV4 |
Oracle Lite PPC50 ARMV4I |
During the upgrade process, be sure to not cancel in the middle. If your device is Windows 5.0 or later, then you must perform the following after the CAB files are downloaded to the device:
Tap on the CAB files to extract the files to the device.
Tap on dmagent to execute start the Device Manager.
The following describes what happens for those Mobile client devices that want to continue to use the de-supported platforms:
Any client device that has a de-supported platform is given the option to migrate to the upgrade platform when they execute msync.exe or update.exe.
If you do not want to upgrade the client platform, then these clients can still synchronize with the Mobile Server; however, they will be prompted to upgrade each time.
You can continue to administer de-supported client platforms, as they will still appear in the platform tabs in the Mobile Manager. We will not disable them from your administration management GUI. However, they will not be included in 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 run as expected. And you may apply any patches for the application. However, you cannot deploy any new applications to that platform.
If you do upgrade the client platform, then you must re-package and re-publish each application as a new application for the new client platform.
|
 Copyright © 1997, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|