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:
Section 3.5, "Hardware Requirements for Mobile Server on Windows"
Section 3.9, "Setting Up Location of the Datafile on the Server"
For the latest information and patches, refer to Oracle MetaLink at the following website:
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 website:
The following sections detail the supported components and technologies:
Section 3.3.1, "Certified Oracle RDBMS to Use With Oracle Database Mobile Server"
Section 3.3.3, "Certified Application Server Configurations"
Section 3.3.4, "Certified Platforms and Technologies for the Mobile Server"
Section 3.3.5, "Certified Platforms for the Mobile Development Kit"
Use one of the following database versions with Oracle Database Mobile Server: Oracle Database 10g, Oracle Database 11g, or Oracle 12c Pluggable Database.
Different JDKs are supported for mobile client, Mobile Server and Mobile Development Kit. For all non Java mobile clients, use 32-bit Oracle JDK 1.7 or 1.8. For pure Java mobile client and Mobile Development Kit, use 32-bit Oracle JDK 1.7 or 1.8 on 32-bit platform, and 64-bit Oracle JDK 1.7 or 1.8 on 64-bit platform. For the mobile server, the JDK version required depends on what target platform you are going to run the mobile server and what version of the application server you are using. Refer to Table 3-1 for detailed information.
Table 3-1 JDK Version Supported
| Application Server Version Used | JDK Version Supported |
|---|---|
|
WebLogic Server 11g Release 1 |
JRockit JDK 1.6 or Oracle JDK 1.6 IBM J9 VM 1.7 for AIX HP-UX 11i JDK for HP-UX |
|
WebLogic Server 12c Release 1 (12.1.1, 12.1.2 or 12.1.3) |
Oracle JDK 1.7 or 1.8 IBM J9 VM 1.7 for AIX HP-UX 11i JDK for HP-UX |
|
Oracle GlassFish 3.1 |
Oracle JDK 1.7 IBM J9 VM 1.7 for AIX HP-UX 11i JDK for HP-UX |
|
GlassFish Server 4 Open Source Edition |
Oracle JDK 1.7 or Oracle JDK 1.8 IBM J9 VM 1.7 for AIX HP-UX 11i JDK for HP-UX |
|
Apache TomEE 1.7 Web Profile |
Oracle JDK 1.7 or Oracle JDK 1.8 HP-UX 11i JDK for HP-UX |
Install JDK before installing the mobile server or Mobile Development Kit.
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 website.
The JDK_HOME environment variable must be set to the directory where the Java Development Kit has been installed. For more information on JDK_HOME, see Section 3.7.1.2, "JDK_HOME and PATH" for settting the JAVA environment variables on Linux.
The following lists accepted configuration options for a middle-tier application server:
Oracle WebLogic Server 11g Release 1, Oracle WebLogic Server 12c Release 1 (12.1.1, 12.1.2 and 12.1.3)
Oracle GlassFish Server 3.1. For more information, see the following site:
http://www.oracle.com/technetwork/middleware/glassfish/documentation/index.html
GlassFish Server Open Source Edition 4.0. For more information, see the following site:
Apache TomEE 1.7.0. For more information, see the following site:
You can install the mobile server on the following platforms:
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 13.1 (64-bit
Ubuntu 14.04 (64-bit)
Fedora 20 (64-bit)
Solaris 10 (64-bit, SPARC) and Solaris 11 (64-bit, X86)
AIX 6.1 (64-bit)
Microsoft Windows 8 (64-bit)
HP-UX Itanium 11i v3 (64-bit)
The Mobile Development Kit (MDK) is certified for Oracle JDK 1.7 and 1.8 and can be installed on the following platforms:
Microsoft Windows 2003 (64-bit)
Microsoft Windows 2008 R2 (64-bit)
Microsoft Windows 7 (32-bit and 64-bit)
Microsoft Windows 8 (64-bit)
Oracle Enterprise Linux 5.0, or 6.0 containing Unbreakable Enterprise Kernel (32-bit and 64-bit)
Ubuntu 14.04 (64-bit)
The following versions of OID are supported in conjunction with the mobile server:
OID 10.1.4.
OID 11.0
You can use any of the latest modern browsers.
The following sections describe installation requirements for the Oracle Database and the application server you choose to use:
When you synchronize the mobile client, your changes are updated in an Oracle back-end database. Thus, you must have either the Express or Standard or Enterprise Edition Oracle database to use the synchronization ability of 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 WebLogic Server 11g, Oracle WebLogic Server 12c, Oracle GlassFish 3.1, GlassFish Server Open Source Edition 4.0, or Apache TomEE 1.7.
Note:
Oracle Database Mobile Server uses ISO-8859-1 for URL decoding. Ensure that the application server uses the same configuration. For example, you can start Weblogic with extra configuration options as below:export JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.http.URIDecodeEncoding=ISO-8859-1"
${WLS_DOMAIN_DIR}/bin/startWebLogic.sh
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:
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:
Create directory structure of $JAVA_HOME/jre/lib/endorsed, where JAVA_HOME is the directory in which JRockit was installed.
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.Ensure that you install Oracle GlassFish server before installing Oracle Database Mobile Server.
Ensure that you install GlassFish Server Open Source Edition 4.0 before installing Oracle Database Mobile Server.
Ensure that you install Apache TomEE 1.6 web profile before installing Oracle Database Mobile Server.
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 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. |
|
GlassFish Server Open Source Edition 4.0 |
See "Hardware and Software Requirements" in GlassFish Server Open Source Edition Release Notes. |
|
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.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.
This section describes the following system configurations for UNIX-based systems:
Section 3.7.2, "Pre-Install Requirements Before Installing the MDK on LINUX"
Section 3.7.4, "Configuring Kernel Parameters and Shell Limits for UNIX"
The following sections describe the environment variables that must be set before starting Oracle Universal Installer:
Note:
Ensure yourPATH, 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 |
|
|
Solaris |
|
|
AIX |
|
|
HP-UX |
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.
The Linux, Solaris, AIX and HP-UX 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, install it before proceeding with the installation of the Mobile Server or the Mobile Development Kit. For the appropriate JDK version, see Section 3.3.2, "JDK Platform Support".
Before installation of a Linux/Solaris/AIX/HP-UX mobile server and the Linux MDK, set JDK_HOME to the JDK home directory.
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
Note:
Here, $ORACLE_HOME is the root directory where you have installed the Mobile Server.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://www.oracle.com/technetwork/documentation/index.html) for further information about obtaining and installing XVFB or other virtual frame buffer solutions. Search OTN for "frame buffer".
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> |
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 |
Of all of the UNIX platforms, the MDK is only supported on the Linux platform.
But before installing the MDK on your Linux system, set the following environment variables:
The following UNIX account and groups are required for the installation process:
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.
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-5.
Table 3-5 Oracle Account Properties
| Variable | Property |
|---|---|
|
Login Name |
Select any name to access the account. This document refers to the name as the |
|
Group Identifier |
The |
|
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 useroot as the oracle account.Depending on your operating system, see one of the following sections for information on checking the software requirements:
Section 3.7.4.1, "Configuring Shell Limits and System Configuration Parameters on AIX"
Section 3.7.4.3, "Configuring the Kernel Parameters on Linux"
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.
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.
| 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:
Enter the smit command: #smit chuser
In the "User Name" field, enter the user name of the Oracle software owner, such as oracle.
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.
Press F10 to exit.
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.
Enter the smit command: #smit chgsys
Verify that the value shown for "Maximum Number of Processes" allowed per user is greater than or equal to 2048.
Press F10 to exit.
Ensure that the ARG_MAX setting is set to the maximum value for AIX 5L:
Check the ARG_MAX setting, as follows:
prompt> getconf ARG_MAX
If the value is less than 524288, then run the following command as the root user:
#chdev -l sys0 -a ncargs=128
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.
To view or modify the current value or formula specified for these kernel parameters, do the following:
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
Start System Administration Manager (SAM): #/usr/sbin/sam
Choose the "Kemel Configuration" area, then choose the "Configurable Parameters" area.
Check and possibly modify the value or formula specified for each of these parameters.
Exit from SAM.
If you modified the value specified for any parameter, then reboot the system with the following: # /sbin/shutdown -r -now
If necessary, when the system restarts, log in and switch the user to root.
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.
To view or modify the current value specified for these kernel parameters, do the following:
Enter the following command to view the current value of the file-max kernel parameter:
# /sbin/sysctl -a | grep file-max
To modify the value, do the following:
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.
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.
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
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-9 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:
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
Add the following line to the /etc/pam.d/login file, if it does not already exist:
session required /lib/security/pam_limits.so
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
The system requirements for mobile client are covered in the Oracle Database Mobile Server Mobile Client Guide.
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 information on how to modify the db_create_file_dest parameter.
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. Here <ORACLE_HOME> is the root installation directory of Oracle Database. 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 repository installation process. Here <ORACLE_HOME> is the root installation directory of Database Mobile Server. 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 more information 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.