Skip Headers
Oracle® Database Mobile Server Installation Guide
Release 11.2

Part Number E29687-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

3 Requirements Before Installation or Development

Before you install, you must check to see that you have the correct hardware and software necessary for using Oracle Database Mobile Server on your operating system. The requirements for each type of operating system are detailed in the following sections:

3.1 Include the Latest Patches

For the latest information and patches, refer to Oracle MetaLink at the following Web site:

http://metalink.oracle.com

3.2 Release Notes

Read the Oracle Database Mobile Server Release Notes before installing Oracle Database Mobile Server, which are available as part of the documentation shipped with Oracle Database Mobile Server. The most up-to-date version is available at OTN at the following Web site:

http://otn.oracle.com/documentation/index.html

3.3 Supported Components and Technologies

The following sections detail the supported components and technologies:

3.3.1 Certified Oracle RDBMS to Use With Oracle Database Mobile Server

Use one of the following database versions with Oracle Database Mobile Server: Oracle 10g Release 1 (10.1.0), Oracle 10g Release 2 (10.2.0), or Oracle 11g.

3.3.2 JDK Platform Support

For all mobile clients, use JDK 1.6. or JDK 1.7. For the mobile server, the JDK version required depends on what version of the application server you are using.

Table 3-1 JDK Version Supported

Application Server Version Used JDK Version Supported

Oracle WebLogic Suite 11g

JRockit JDK 1.6 or Oracle JDK 1.6

JBM J9 VM 1.7 for AIX

Oracle WebLogic Suite 12c

JRockit JDK 1.6 update 19+

JBM J9 VM 1.7 for AIX

Oracle Glassfish 3.1

Oracle JDK 1.7

JBM J9 VM 1.7 for AIX

Oracle Application Server 10.1.3.5.0

Oracle JDK 1.6

Apache TomEE 1.0.0 Web Profile

Oracle JDK 1.6


You should install all of the patches required for the JDK version you are using on the Windows operating system. This is constantly under review and published on the JDK download page on the Oracle web site.

Install the Oracle JDK before installing the mobile server or Mobile Development Kit. If you have JDK 1.4.2 installed, upgrade to the right version of JDK as follows:

  1. Uninstall the existing JDK version 1.4.2. If you do not remove this version first, then mobile server will continue to use version 1.4.2.

  2. Install the required version of JDK. After installation, verify that the JDK bin directory is in the system path.

The JAVA_HOME environment variable must be set to the directory where the Java Development Kit has been installed. For more information on JAVA_HOME, see Section 3.7.1.2, "JDK_HOME and PATH" for settting the JAVA environment variables on Linux.

3.3.3 Certified Application Server Configurations

The following lists accepted configuration options for a middle-tier application server:

  • Oracle WebLogic Server 11g Release 1, Oracle WebLogic Server 12c

  • Oracle Glassfish Server 3.1. For more information, see the following site:

    http://www.oracle.com/technetwork/middleware/glassfish/documentation/index.html
    
  • Oracle Application Server 10g (10.1.3.5.0 OC4J Container andWeb Server)

    Note:

    Depending on the platform, iAS is installed with either the Oracle Application Server 10g Release 3 package or from the Oracle SOA Suite 10g (10.1.3.1.0) package. In addition, certain platforms have unique patches that need to be applied. For more information, refer to the Oracle Application Server documentation. Failure to install iAS properly will prevent Database Mobile Server from working correctly.
  • Apache TomEE 1.0.0 Web Profile

3.3.4 Certified Platforms and Technologies for the Mobile Server

You can install the mobile server on the following platforms:

  • Microsoft Windows XP Professional Edition with Service Pack 3 (32-bit)

  • Microsoft Windows 7 (32-bit and 64-bit)

  • Microsoft Windows 2003 (64-bit)

  • Microsoft Windows 2008 R2 (64-bit)

  • Oracle Enterprise Linux 5.0, or 6.0 with or without Unbreakable Enterprise Kernel (32-bit and 64-bit)

  • OpenSUSE 12 (64-bit)

  • Ubuntu 11 (64-bit)

  • Fedora 16 (64-bit)

  • Solaris 10 (64-bit, SPARC) and Solaris 11 (64-bit, X86)

  • AIX 6.1 (64-bit)

3.3.5 Certified Platforms for the Mobile Development Kit

The Mobile Development Kit (MDK) is certified for Oracle JDK 1.6 and 1.7 and can be installed on the following platforms:

  • Microsoft Windows 2003 (64-bit)

  • Microsoft Windows 2008 R2 (64-bit)

  • Microsoft Windows XP Professional Edition with Service Pack 3 (32-bit)

  • Microsoft Windows 7 (32-bit and 64-bit)

  • Oracle Enterprise Linux 5.0, or 6.0 containing Unbreakable Enterprise Kernel (32-bit and 64-bit)

  • Ubuntu 11 (64-bit)

3.3.6 Certified Versions for OID Support

The following versions of OID are supported in conjunction with the mobile server:

  • OID 10.1.4.

  • OID 11.0

3.3.7 Certified Browsers

You can use any of the latest modern browsers.

3.4 Installation Requirements for the Oracle Database and Application Server in Working With Oracle Database Mobile Server

The following sections describe installation requirements for the Oracle Database and the application server you choose to use:

3.4.1 Installation Requirements for the Oracle Database for Working With a Mobile Client

When you synchronize the mobile client, your changes are updated in an Oracle back-end database. Thus, you must have either the Standard or Enterprise Edition Oracle database to use the synchronization ability of Oracle Database Mobile Server.

3.4.2 Installation Requirements for Using an Application Server With Oracle Database Mobile Server

Oracle Database Mobile Server uses a middle-tier application server to communicate between the mobile clients and the back-end Oracle database.

Install the appropriate application server before installing Oracle Database Mobile Server, which can be Oracle Application Server 10.1.3.5.0, Oracle WebLogic Server 11g, Oracle WebLogic Server 12c, Oracle Glassfish 3.1 or Apache TomEE 1.0.

Note:

For more information about how Oracle Database Mobile Server works with the middle-tier and the back-end database, see Chapter 1, "Overview for Designing Mobile Applications" in the Oracle Database Mobile Server Developer's Guide.

The following sections provide additional information when installing certain application servers:

3.4.2.1 Installing Oracle WebLogic Server 12c Release 1

Make sure that you install Oracle WebLogic before installing Oracle Database Mobile Server.

Oracle WebLogic Server 12c Release 1 uses some updated Java APIs which are included in its own distribution. You must prepare the related jar files after installation of JRockit 1.6 and Oracle WebLogic Server 12c.

Follow the steps below before you deploy Oracle Database Mobile Server 11g Release 2 in WebLogic Server 12c.

  1. create directory structure of $JAVA_HOME/jre/lib/endorsed, where JAVA_HOME is the directory in which JRockit was installed.

  2. copy $WL_HOME/endorsed/*.jar to $JAVA_HOME/jre/lib/endorsed.

Note:

If you fail to do the above preparation, the deployment of Mobile Server will run into an "Exception thrown by startServer: java.lang.reflect.InvocationTargetException" error. These steps are only required by WebLogic Server 12c.

3.4.2.2 Installing Oracle Glassfish Server Version 3.1

Make sure that you install Oracle Glassfish server before installing Oracle Database Mobile Server.

3.4.2.3 Installing OracleAS Version 10.1.3.5.0

Install OracleAS before installing Oracle Database Mobile Server. When installing OracleAS, choose the Integrated Web and J2EE Server installation option.

In the OracleAS version 10.1.3.5.0 install, choose the Advanced Installation Mode. In the second screen, you will see the following options:

  1. J2EE Server and Process Management

  2. Web Server and Process Management

  3. Integrated Web Server, J2EE Server and Process Management

  4. Oracle Toplink

Select ONLY option 3, the Integrated Web Server, J2EE Server and Process Management. This option provides all of the functionality that you need. Do not select any of the other options, as then your OracleAS installation will be missing functionality that is necessary for Oracle Database Mobile Server.

After the installation of Oracle Application Server 10.1.3.5.0 and before the installation of Oracle Database Mobile Server, follow Doc (ID 444462.1) to upgrade the Oracle Application Server embedded JDK 1.5 to JDK 1.6, the embedded JDK can be found at <ORACLE_HOME>/jdk, this is the minimum JDK version Oracle Database Mobile Server requires. Post the installation of Oracle Database Mobile Server, refer to Doc (ID 420303.1) to use the latest thin JDBC Driver with Oracle Database Mobile Server. Restart the Oracle Application Server before you start using the Oracle Database Mobile Server.

Find the related document from Oracle Internal Support website (https://support.us.oracle.com - Knowledge - Search by Doc ID).

3.4.2.4 Installing Apache TomEE 1.0.0 Web Profile

Make sure that you install Apache TomEE 1.0.0 web profile before installing Oracle Database Mobile Server.

3.5 Hardware Requirements for Mobile Server on Windows

Before you install the mobile server, you must check to see that you have the correct hardware necessary for your Windows machines that use Oracle Database Mobile Server.

The hardware requirements for each component of Oracle Database Mobile Server for Windows are described in the following table:

Table 3-2 Hardware Requirements for Windows

Component Hardware Requirements for this Component

Oracle Database Mobile Server

CPU: Pentium 4, 3 GHz

Disk Space: 1 GB

RAM: 1 GB

Swap Space: 1535 MB

Oracle Database Mobile Server using OracleAS

See the OracleAS documentation for the OC4J container requirements.

Swap Space: 1535 MB

Oracle Database Mobile Server using Oracle WebLogic Server

See the "Oracle Fusion Middleware System Requirements and Specifications" document for the specific release version in the Oracle Fusion Middleware documentation.

Oracle Database Mobile Server using Oracle Glassfish Server

See the "Hardware and Software Requirements in Oracle GlassFish Server 3.1 Release Notes" document in the Oracle Fusion Middleware documentation.

Mobile Development Kit

CPU: Pentium 4, 3 GHz

Disk Space: 512 MB

RAM: 512 MB

Swap Space: 1535 MB


Note:

The requirements for mobile server is related to the number of users synchronizing and the amount of data transferred.

3.6 System Requirements For UNIX Systems

Before you install, you must check to see that you have the correct hardware and software that satisfy the minimum and general system requirements for the Web server on the UNIX machines that use Oracle Database Mobile Server. See the Web server documentation for these requirements.

3.7 Recommended System Configuration For UNIX

This section describes the following system configurations for UNIX-based systems:

3.7.1 Setting UNIX Environment Variables

The following sections describe the environment variables that must be set before starting Oracle Universal Installer:

Note:

Ensure your PATH, CLASSPATH and library path environment variables do not exceed 1024 characters. Longer values might generate errors such as "Word too long" during installation.

Refer to Table 3-3 for the name of the library path environment variable for your platform.

Table 3-3 lists the names of the library path environment variables for each platform.

Table 3-3 Library Path Environment Variable

Platform Library Path Environment Variable

Linux

LD_LIBRARY_PATH

Solaris

LD_LIBRARY_PATH

AIX

LIBPATH


3.7.1.1 ORACLE_HOME and MOBILE_HOME

The Oracle home directory is the root directory in which Oracle software is installed. For Oracle Database Mobile Server, you can also use MOBILE_HOME environment variable to specify the root directory in which you want to install Mobile Server or Mobile Development Kit. The CLASSPATH contains the entire path you enter for ORACLE_HOME; thus, the length of ORACLE_HOME effects the length of the CLASSPATH. There are limits to the length of the values of the CLASSPATH values with JDK. If the ORACLE_HOME path is long, this will result in a long CLASSPATH and might cause problems running Oracle Database Mobile Server. The workaround is to shorten ORACLE_HOME path.

The ORACLE_HOME environment variable must be set before starting the installer, which must be set to the directory where you want to install.

3.7.1.2 JDK_HOME and PATH

The Linux, Solaris and AIX platforms require the JDK_HOME environment variable be set to the directory where the Java Development Kit has been installed. If the JDK has not been installed, please install it before proceeding with the installation. For the appropriate JDK version, see Section 3.3.2, "JDK Platform Support".

Before installation of a Linux/Solaris/AIX mobile server and the Linux MDK, set JDK_HOME to the JDK home directory. Table 3-4 provides examples for the location where the JDK could be installed on the system.

Table 3-4 JDK_HOME Environment Variables

Platform Sample JDK_HOME Environment Variable

Linux

/opt/java1.6

AIX

/usr/java7_64


Initialize the JDK_HOME and PATH environment variables, as follows:

export JDK_HOME=/path/to/jdk
export PATH=$JDK_HOME/bin:$ORACLE_HOME/bin:$PATH 

3.7.1.3 DISPLAY

Set the DISPLAY environment variable to refer to the X Server that will display the installer and Oracle Database Mobile Server. The format of the DISPLAY environment variable is:

hostname:display_number.screen_number

For example, set the DISPLAY environment variable, as follows:

setenv DISPLAY myhost:0.0

Oracle Database Mobile Server requires a running X server to properly create graphics for the installer, Web applications, and management tools. The frame buffer X server installed with your operating system requires that you remain logged in and have the frame buffer running at all times. If you do not want to do this, then you must use a virtual frame buffer, such as X Virtual Frame Buffer (XVFB) or Virtual Network Computing (VNC).

See Also:

  • Your operating system documentation for more information on the DISPLAY environment variable.

  • Oracle Technology Network (http://otn.oracle.com) for further information about obtaining and installing XVFB or other virtual frame buffer solutions. Search OTN for "frame buffer".

3.7.1.3.1 Installing From a Remote Machine

Setting the DISPLAY environment variable enables you to run the Oracle Universal Installer remotely from another workstation. On the system where you launch the Oracle Universal Installer, set DISPLAY to the system name or IP address of your local workstation.

Note:

You can use a PC X emulator to run the installer if it supports a PseudoColor color model or PseudoColor visual. Set the PC X emulator to use a PseudoColor visual, and then start the installer. Refer to the X emulator documentation for instructions on how to change the color model or visual settings.

If you get an Xlib error similar to "Failed to connect to server", "Connection refused by server," or "Can't open display" when starting the installer, then run the commands on your local workstations as listed in the following table.

Shell Types On the Server Host Machine Where the Installer is Running In the Session on Your Host
C Shell prompt> setenv DISPLAY <hostname>:0.0 prompt> xhost +<hostname>
Bourne/Korn Shell prompt> DISPLAY=<hostname>:0.0;export DISPLAY prompt> xhost +<hostname>

3.7.1.4 TMP and TMPDIR

During installation, Oracle Universal Installer uses a temporary directory for swap space. This directory must meet the requirements listed in Section 3.6, "System Requirements For UNIX Systems" before installing Oracle Database Mobile Server. The installation may fail if you do not have sufficient space. The installer checks for the TMP and TMPDIR environment variable to locate the temporary directory. If the TMP environment variable is not set, then the installer uses the /tmp directory. If the TMPDIR environment variable is not set, then the installer uses the /var/tmp directory. Set the TMP and TMPDIR environment variable using the commands in the following table.

C Shell Bourne/Korn Shell
prompt> setenv TMP full_path prompt> TMP=full_path;export TMP
prompt> setenv TMPDIR full_path prompt> TMPDIR=full_path;export TMPDIR

3.7.2 Pre-Install Requirements Before Installing the MDK on LINUX

Of all of the UNIX platforms, the MDK is only supported on the Linux platform.

But before installing the MDK on your Linux system, modify the following environment variables:

Table 3-5 Linux Environment Variable

Linux Environment Variable Description

JDK_HOME

Point to the JDK installation directory

ORACLE_HOME

ORACLE_HOME point to the root folder of the Mobile Development Kit installation

LD_LIBRARY_PATH

/usr/lib:$JDK_HOME/jre/lib/i386:$JDK_HOME/jre/lib/i386/server:$ORACLE_HOME/mobile/sdk/bin:$LD_LIBRARY_PATH

CLASSPATH

.:$ORACLE_HOME/mobile/sdk/bin/jsync.jar

PATH

$JDK_HOME/bin:$ORACLE_HOME/mobile/sdk/bin:$PATH


3.7.3 Creating UNIX Accounts and Groups

The following UNIX account and groups are required for the installation process:

3.7.3.1 UNIX Group Name For the Oracle Universal Installer Inventory

Use the admintool or groupadd utility to create a group name. In the following text the group name is oinstall. The oinstall group will own Oracle Universal Installer's oraInventory directory. The oracle user account that runs the installer must have the oinstall group as its primary group and dba as its secondary group.

For more information on these utilities, refer to your operating system documentation.

3.7.3.2 UNIX Account to Own Oracle Software

The oracle account is the UNIX account that owns Oracle software for your system. You must run Oracle Universal Installer from this account.

Create an oracle account with the properties listed in Table 3-6.

Table 3-6 Oracle Account Properties

Variable Property

Login Name

Select any name to access the account. This document refers to the name as the oracle account.

Group Identifier

The oinstall group.

Home Directory

Select a home directory consistent with other user home directories.

Login Shell

The default shell can be either the C, Bourne, or Korn shell.


Note:

Do not use root as the oracle account.

3.7.4 Configuring Kernel Parameters and Shell Limits for UNIX

Depending on your operating system, see one of the following sections for information on checking the software requirements:

3.7.4.1 Configuring Shell Limits and System Configuration Parameters on AIX

On AIX systems, you do not need to configure kernel parameters. However, Oracle recommends that you set shell limits and system configuration parameters as described in this section.

3.7.4.1.1 Configuring Shell Limits for AIX Systems

Verify that the shell limits shown in the following table are set to the values shown. The procedure following the table describes how to verify and set the values.

Table 3-7 Shell Limits

Shell Limits as shown in smit Recommended Value

Soft FILE size

-1 (Unlimited)

Soft CPU time

-1 (Unlimited) -- this is the default value

Soft DATA segment

-1 (Unlimited)

Soft STACK size

-1 (Unlimited)


To view or change the current value specified for these shell limits, follow these steps:

  1. Enter the smit command: #smit chuser

  2. In the User Name field, enter the user name of the Oracle software owner, such as oracle.

  3. Scroll down the list and verify that the value shown for the soft limits listed in the previous table is -1. If necessary, modify the existing value to be -1.

  4. Press F10 to exit.

3.7.4.1.2 Configure System Configuration Parameters for AIX

Verify that the Maximum number of processes allowed for each user is set to 2048 or greater. The procedure following the table describes how to verify and set the value.

  1. Enter the smit command: #smit chgsys

  2. Verify that the value shown for Maximum number of PROCESSES allowed per user is greater than or equal to 2048.

  3. Press F10 to exit.

Ensure that the ARG_MAX setting is set to the maximum value for AIX 5L:

  1. Check the ARG_MAX setting, as follows:

    prompt> getconf ARG_MAX
    
  2. If the value is less than 524288, then run the following command as the root user:

    #chdev -l sys0 -a ncargs=128
    

3.7.4.2 Configuring Kernel Parameters on HP-UX

Verify that the kernel parameters shown in the following table are set either to the formula shown or to values greater than or equal to the recommended value shown. The procedure following the table describes how to verify and set the values.

Table 3-8 Kernel Parameters for HP-UX

Parameter Recommended Formula or Value

nfile

3000

nproc

2048


To view or modify the current value or formula specified for these kernel parameters, do the following:

  1. Optionally, set the DISPLAY environment variable to specify the display of the local system, as follows:

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=localhost:0.0 ; export DISPLAY
      
    • C shell:

      $ setenv DISPLAY localhost:0.0
      
  2. Start System Administration Manager (SAM): #/usr/sbin/sam

  3. Choose the Kernel Configuration area, then choose the Configurable Parameters area.

  4. Check and possibly modify the value or formula specified for each of these parameters.

  5. Exit from SAM.

  6. If you modified the value specified for any parameter, then reboot the system with the following: # /sbin/shutdown -r -now

  7. If necessary, when the system restarts, log in and switch the user to root.

3.7.4.3 Configuring the Kernel Parameters on Linux

Verify that the kernel parameters shown in the following table are set either to the formula shown, or to values greater than or equal to the recommended value shown. The procedures following the table describe how to verify and set the values.

Table 3-9 Kernel Parameters on Linux

Parameter Value File

file-max

131072

/proc/sys/fs/file-max


To view or modify the current value specified for these kernel parameters, do the following:

  1. Enter the following command to view the current value of the file-max kernel parameter:

    # /sbin/sysctl -a | grep file-max
    
  2. To modify the value, do the following:

    1. Create or edit the /etc/sysctl.conf file and add the following.

      fs.file-max = 131072
      

      By specifying the values in the /etc/sysctl.conf file, they persist when you reboot the system.

    2. Change the current values of the kernel parameter with the following command:

      # /sbin/sysctl -p
      

      Review the output from this command to verify that the values are correct. If the values are incorrect, then perform these steps again.

    3. On UnitedLinux only, enter the following command to cause the system to read the /etc/sysctl.conf file when it reboots:

      # chkconfig boot.sysctl on
      

3.7.4.4 Set Shell Limits for the User oracle

To improve the performance of the software on Linux systems, you must increase the following shell limits for the oracle user, depending on the user's default shell:

Table 3-10 Shell Limits for Linux Systems

Bourne or Bash Shell Limit Korn Shell Limit C or tcsh Shell Limit Hard Limit

nofile

nofile

descriptors

16384

noproc

processes

maxproc

16384


To increase the shell limits, do the following:

  1. Add the following lines to the /etc/security/limits.conf file, where the arrow (->) represents the tab character:

    * -> -> soft -> nproc -> -> 2047
    * -> -> hard -> nproc -> -> 16384
    * -> -> soft -> nofile -> -> 2047
    * -> -> hard -> nofile -> -> 16384
    
  2. Add the following line to the /etc/pam.d/login file, if it does not already exist:

    session required /lib/security/pam_limits.so
    
  3. Depending on the oracle user's default shell, make the following changes to the default shell start-up file:

    • For the Bourne, Bash, or Korn shell, add the following lines to the /etc/profile file:

      if [ $USER = "oracle" ]; then
         if [ $SHELL = "/bin/ksh" ]; then
           ulimit -p 16384
           ulimit -n 16384
         else
           ulimit -u 16384 -n 16384
         fi
      fi
      
    • For the C or tcsh shell, add the following lines to the /etc/csh.login file:

      if ( $USER == "oracle" ) then
          limit maxproc 16384
          limit descriptors 16384
      endif
      

3.8 System Requirements for Mobile Clients

The system requirements for either mobile client—Berkeley DB or SQLite—are covered in the Oracle Database Mobile Server Mobile Client Guide.

3.9 Setting Up Location of the Datafile on the Server

If you do not want to have the datafile for your Oracle Database Mobile Server applications stored in the default location in the Oracle database, then modify the database configuration file to include the directory where you want your datafile stored. Configure the default directory for new data files in the db_create_file_dest parameter. Once updated, restart the Oracle database. This must be done before installing Oracle Database Mobile Server. Refer to your database administration guide for details on how to modify the db_create_file_dest parameter.

3.10 Defining Synchronization Tablespace

By default, the synchronization tablespace is SYNCSERVER, and is stored in the mobilexx.dbf file in the default location for the database under ORACLE_HOME, where xx is a number between 1 and 25. The tablespace name, filename, and file location for the tablespace is defined in the $ORACLE_HOME/Mobile/Server/admin/consolidator_o8a.sql script file, which is executed during the mobile server installation process. So, if you want to modify the tablespace, there are a few tasks you need to perform BEFORE you install the mobile server.

Tablespace layout across multiple disks can improve the performance of mobile server data synchronization, as it reduces movement of the disk heads and improves I/O response time.

For full details on how to alter the synchronization tablespace, see Section 1.2.6, "Synchronization Tablespace Layout" in the Oracle Database Mobile Server Troubleshooting and Tuning Guide for more information.