4 Installation of Oracle Database Mobile Server

This chapter describes all of the details for you to install Oracle Database Mobile Server, including the following:

• Section 4.1, "Oracle Database Mobile Server Installation Considerations"

• Section 4.2, "Starting Oracle Universal Installer"

• Section 4.3, "Installing Oracle Database Mobile Server"

• Section 4.4, "Starting and Stopping Mobile Server"

• Section 4.5, "Testing Your Mobile Server Installation"

• Section 4.6, "Removing Demo Applications"

• Section 4.7, "How to Uninstall Oracle Database Mobile Server"

4.1 Oracle Database Mobile Server Installation Considerations

Note the following issues before you start your installation:

• Section 4.1.1, "Installing Multiple Languages on a Single Solaris Machine"

• Section 4.1.2, "National Language Support for Chinese, Japanese, and Korean"

• Section 4.1.3, "Mobile Server on a DHCP Server is Not Supported"

• Section 4.1.4, "Installing Mobile Server Using Multiple Languages"

4.1.1 Installing Multiple Languages on a Single Solaris Machine

With Oracle Database Mobile Server installed in a Solaris environment, you cannot install multiple languages on a single Solaris machine. Instead, you must perform a separate installation for each language.

4.1.2 National Language Support for Chinese, Japanese, and Korean

The mobile server and Mobile Development Kit have full National Language Support for Simplified Chinese, Japanese, and Korean.

4.1.3 Mobile Server on a DHCP Server is Not Supported

The Oracle Database Mobile Server can only be installed on a server with a static IP address.

4.1.4 Installing Mobile Server Using Multiple Languages

The Oracle Database Mobile Server can be installed with different character sets. It is important to ensure that the back-end Oracle Database supports the character sets as the Mobile Server. Failure to do this will result in unreadable content in the Mobile Manager.

4.2 Starting Oracle Universal Installer

Oracle Database Mobile Server uses Oracle Universal Installer to guide you through each step of the installation process. The Oracle Universal Installer provides the following features:

• Describes installation options for Oracle Database Mobile Server

• Detects pre-set environment variables and configuration settings

• Sets environment variables and configuration during installation

• Offers configuration options for a customized installation of Oracle Database Mobile Server

• Deinstalls products

The Oracle Universal Installer automatically checks your computer prior to installation to verify that your system meets operational requirements. Table 4-1 lists the prerequisite checks that are performed.

Table 4-1 Oracle Universal Installer Automatic Prerequisite Checks

Prerequisite Checks	See Also
Check for enough disk space for installation	Section 3.7, "Recommended System Configuration For UNIX"
On UNIX systems, checks for TMP and TMPDIR variable and sufficient swap space	Section 3.7, "Recommended System Configuration For UNIX"

You start the Oracle Universal Installer using different methods for each type of operating system, as detailed in the following steps:

• Section 4.2.1, "Starting the Oracle Universal Installer on Windows"

• Section 4.2.2, "Starting Oracle Universal Installer on UNIX"

4.2.1 Starting the Oracle Universal Installer on Windows

Follow the steps below:

• Log on as a member of the Administrators group for the computer on which you want to install Oracle Database Mobile Server.

• Download the installer package for Oracle Database Mobile Server (DMS) from Oracle technology network and unpack it to the target platform where you want to install the DMS or insert the CD-ROM labeled Oracle Database Mobile Server.

• Execute Disk1/install/win32/setup.exe for Windows 32bit system or Disk1/install/win64/setup.exe for Windows 64bit system.

• The "Welcome" screen appears.

4.2.2 Starting Oracle Universal Installer on UNIX

Depending on how you got the installer package for Oracle Database Mobile Server, follow below steps to install Database Mobile Server:

Note:

Ensure you are not logged in as the root user when you start the Oracle Universal Installer.

1. If you have purchased a CD labeled Oracle Database Mobile Server, insert the CD into the CD-ROM drive. Mount the installation CD-ROM. Run Oracle Universal Installer from the CD-ROM:

   1. Log in as the oracle user.

   2. Start the installer by entering the following commands:

      On Linux 32bit system, prompt> mount_point/Disk1/install/linux/runInstaller
      On Linux 64bit system, prompt> mount_point/Disk1/install/linux64/runInstaller
      On Solaris SPARC system, prompt> mount_point/Disk1/install/solaris/runInstaller
      On Solaris Intel system, prompt> mount_point/Disk1/install/intelsolaris/runInstaller
      On AIX system, prompt> mount_point/Disk1/install/aix/runInstaller
      On HP-UX Itanium system, prompt> mount_point/Disk1/install/hpia64/runInstaller
      

2. If you have downloaded the installer package for Oracle Database Mobile Server from Oracle technology network, unpack the installer package to the target platform:

   On Linux 32bit system, execute Disk1/install/linux/runInstaller
   On Linux 64bit system, execute Disk1/install/linux64/runInstaller
   On Solaris SPARC system, execute Disk1/install/solaris/runInstaller
   On Solaris Intel system, execute Disk1/install/intelsolaris/runInstaller
   On AIX system, execute Disk1/install/aix/runInstaller
   On HP-UX Itanium system, execute Disk1/install/hpia64/runInstaller
   

This launches Oracle Universal Installer, which installs Oracle Database Mobile Server.

4.2.2.1 Using the oraInventory Directory

The Oracle Universal Installer creates the oraInventory directory the first time it is run on a computer. The oraInventory directory keeps an inventory of products that the Oracle Universal Installer installs on your computer, as well as other installation information. If you have previously installed Oracle products, then you may already have an oraInventory directory.

When a UNIX group name is created and specified, the Oracle Universal Installer grants the specified group the permission to write to the oraInventory directory. If another group attempts to run the installer, then they must have permission to write to the oraInventory directory. If they do not have permission, then the installation will fail.

The location of oraInventory is defined in the oraInst.loc file. See Table 4-2 for the location of the orainst.loc file for your system.

The latest installation log file is stored in:

/your_base_directory/oraInventory/logs/installActionstodays_date_time.log

The your_base_directory identifier is the location for your installation files and todays_date_time is the date and time of installation. Log file names of previous installation sessions take the form installActionstodays_date_time.log.

Do not delete or manually alter the oraInventory directory or its contents. Doing so can prevent the installer from locating products that you have installed on your system.

4.2.2.2 Location of Files on UNIX

The following table lists the location of the oratab and oraInst.loc file for each platform:

Table 4-2 File Locations for Each Platform

Platform	oratab and emtab	oraInst.loc
AIX	/etc	/etc
Solaris	/etc	/var/opt/oracle
Linux	/etc	/etc
HP-UX	/etc	/var/opt/oracle

4.3 Installing Oracle Database Mobile Server

Oracle Database Mobile Server consists of two main components: the Oracle Database Mobile Server and Mobile Development Kit. Each is installed separately from the Oracle Database Mobile Server installer package. The following sections describe all your installation options:

• Section 4.3.1, "GUI Install of the Mobile Server and MDK Components"

• Section 4.3.2, "Silent Install of the Mobile Server and MDK Components"

• Section 4.3.3, "Providing High Availability with a Farm of Multiple Mobile Servers"

• Section 4.3.4, "Install Oracle Database Mobile Server on Linux"

• Section 4.3.5, "Mobile Client Install"

4.3.1 GUI Install of the Mobile Server and MDK Components

Once the Oracle Universal Installer is initiated, perform the following steps to install Oracle Database Mobile Server:

1. On the "Welcome" screen, click "Next".

2. On the "Installation Types" screen, choose the type of installation to execute. Your options are as follows:

   • Mobile Server

   • Mobile Development Kit

   Each of these Install options is discussed in the following sections:

   • Section 4.3.1.1, "Installation of the Mobile Server"

   • Section 4.3.1.2, "Installation of Mobile Development Kit"

4.3.1.1 Installation of the Mobile Server

Install the Oracle Database Mobile Server from the Installation Types screen, as follows:

1. Choose "Mobile Server" and click "Next" (see, Figure 4-1). On Solaris, AIX and HP-UX platforms, only the "Mobile Server" installation type is available, so the "Select Installation Type" screen is not displayed.

   Figure 4-1 Select Mobile Server

   
   

2. On the "Specify Home" screen, as seen in Figure 4-2, enter the name for your mobile server installation and path where you want to install Oracle Database Mobile Server. Both fields cannot include any spaces. The path you specified is known as Oracle Home.

   Figure 4-2 Specify Home Details

   
   

3. Choose an empty directory to install Mobile Server. If the installation location you specified is not empty, you will get the warning as shown in Figure 4-3, you can ignore this warning.

   Figure 4-3 OUI Check

   
   

4. Click "Yes" to install the mobile server repository. Click "Yes" to launch Repository Wizard to install and configure mobile server repository during the installation process. Cick "No" to postpone the installing and configuring of mobile server repository to after the installation process. Click "Next".

   Figure 4-4 Mobile Server Repository Configuration

   
   

5. Click "Yes" or "No" to indicate if you want the demo applications installed on the server. Click "Next".

   Figure 4-5 Mobile Server Demo Application Configuration

   
   

6. Select the installation directory of your application server (on the "Specify Application Server Home" screen).

   • If you choose WebLogic as application server, specify WL_HOME as Application Server Home, where WL_HOME is the top-level installation directory for WebLogic Server.

   • If you choose Oracle GlassFish server or GlassFish server Open Source Edition as application server, specify as-install as Application Server Home, where as-install is the base installation directory for GlassFish Server.

   • If you choose TomEE as application server, specify CATALINA_HOME as Application Server Home, where CATALINA_HOME is the installation directory of TomEE Server.

   Figure 4-6 Specify Application Server Home

   
   

7. Select a JDK installed on your machine (on the "Specify JDK Home" screen). For more information, refer to Section 3.3.2, "JDK Platform Support". If your application server is WebLogic server, choose the same JDK you use for the WebLogic server. The JDK should be the version as described in Table 3-1, otherwise, Mobile server will use the JDK for your WebLogic server, and not the one you specify in this screen.

   Figure 4-7 Specify JDK Home

   
   

8. On the "Summary" page, click "Install" to start the installation of mobile server which is installed in your Oracle Home.

   Note:

   If you previously clicked Yes to install the mobile server repository, then the Repository Wizard is now launched to create and populate the repository with the Mobile Server schema.

   Figure 4-8 Installation of Mobile Server

   
   

9. Provide the URL for the back-end Oracle database for the mobile server repository, as follows:

   • If you are connecting to a single Oracle database, provide the host name, port and SID or service name. This is shown in Figure 4-9.

     Figure 4-9 Provide Repository Database Information

     
     

   • If you are connecting to a single Oracle 12c Pluggable database (PDB), provide the host name, port number and service name. This is shown in Figure 4-10.

     Figure 4-10 Provide Repository Database information with Oracle Database 12c

     
     

   • If you are connecting to an Oracle RAC database, select the "Enter Custom JDBC URL" checkbox and enter the JDBC URL for this database. For an example of using Oracle Database Express Edition, see Figure 4-11.

     An Oracle RAC database URL takes the following format:

     jdbc:oracle:thin:@(DESCRIPTION=
      (ADDRESS_LIST=
        (ADDRESS=(PROTOCOL=TCP)(HOST=PRIMARY_NODE_HOSTNAME)(PORT=1521))
        (ADDRESS=(PROTOCOL=TCP)(HOST=SECONDARY_NODE_HOSTNAME)(PORT=1521))
      )
      (CONNECT_DATA=(SERVICE_NAME=DATABASE_SERVICENAME)))
     

     Figure 4-11 Enter JDBC URL for Back-End Database in Repository Wizard

     
     

   The mobile server installs its meta-data in the back-end database. If you are not sure of the values to enter for the URL, then you can query the data dictionary to obtain these values.

   For Oracle 10g and 11g Database, connect as SYSTEM user and run the following queries to retrieve the SID:

   select instance_name from v$instance;
    
   

   For Oracle 12c, connect as the administrator user of your Pluggable database and run the following queries to retrieve the service name:

   select name from dba_services;
   

   If you need to retrieve the port number, check the listener.ora file on the machine where the Oracle Database is installed.

   Click "Next".

   Note:

   You must enter the user name and password for the following 3 different accounts:

   • The Database Administrator account:

     • for Oracle database 10g or 11g, it is a master account to create the mobile server repository schema/user

     • for Oracle database 12c, it is a master account of your pluggable database to create the mobile server repository schema/user in that pluggable database

   • The Mobile Server Repository account: Used to access all the database objects used by the mobile server.

   • The Mobile Server Administrator account: Used to log into the Mobile Manager.

10. The Repository Wizard asks for a user name and password for the Database Administrator account, which will be used to connect to the back-end database, create the schema and assign database privileges for the mobile server.

    Figure 4-12 Specify Username/Password

    
    

    Before you provide the user name, this user has to have the following privileges to create the mobile server repository in the back-end database:

    • CREATE TABLESPACE, CREATE USER

    • The following privileges are required with the Admin option:

      ALTER ANY TABLE, ALTER SESSION, ALTER SYSTEM, ANALYZE ANY, CREATE SESSION, CREATE ANY SEQUENCE, CREATE ANY VIEW, CREATE ANY TRIGGER, CREATE ANY INDEX, CREATE ANY TABLE, CREATE ANY SYNONYM, CREATE ANY PROCEDURE, CREATE PROCEDURE, CREATE SEQUENCE, CREATE SYNONYM, CREATE TABLE, CREATE VIEW, CREATE INDEXTYPE, DELETE ANY TABLE, DROP ANY SEQUENCE, DROP ANY PROCEDURE, DROP ANY VIEW, DROP ANY SYNONYM, DROP ANY TRIGGER, DROP ANY INDEX, DROP ANY TABLE, INSERT ANY TABLE, SELECT ANY TABLE, SELECT ANY DICTIONARY, SELECT_CATALOG_ROLE, UPDATE ANY TABLE

    Note:

    You can set the mobile server privileges independently through an API. See Section 3.7, "Set DBA or Operational Privileges for the Mobile Server" in the Oracle Database Mobile Server Developer's Guide.

    Click "Next".

11. If this is a new repository, the following message is displayed:

    No existing repository found. A new repository will be installed.
    

    Otherwise, the following message is displayed (shown in Figure 4-13):

    One or more existing repositories were found.
    

    Select the schema you wish to upgrade or enable the "Create New Repository" check box.

    Figure 4-13 Create a New Repository or Upgrade an Existing Repository

    
    

    Click "Next".

12. Enter the user name and password for the Mobile Server Repository account. The default name is MOBILEADMIN. This schema contains all database objects used by the mobile server. When the mobile server accesses the repository, it uses the Mobile Server Repository user name/password. Also, check whether you want to install sample applications or not. Click "Next".

    Note:

    You should install the samples only on a development system; you should NEVER install the samples on a production mobile server. Doing so creates a security risk on your production environment.

    Figure 4-14 Enter Password for Mobile Server Repository

    
    

13. Enter the user name and password for the Mobile Server Repository account that you will use to log into the Mobile Manager.

    Figure 4-15 Mobile Server Administrator

    
    

14. Enter the Schema Name and Password for the schema where the demo applications are installed. When the user accesses the user data in the Mobile Server repository, the Mobile Server authenticates the schema user name and password before access is provided to the user data. Enter the Password for the sample users.

    Note:

    If you choose to install the samples, then the following mobile user accounts will be created: S11U1, JOHN, JANE, JACK, and JUNE. The password of the users is the one you specified in "Samples Clients Password".

    Figure 4-16 Enter Username and Password for the Demo Schema

    
    

15. Complete the required information to deploy the Mobile Server on a WebLogic, GlassFish or TomEE Server.

    To deploy the Mobile Server on a WebLogic Server or GlassFish Server in a new domain, follow the instructions below:

    • Choose "Yes" for "Create a New Domain for the Mobile Server" option.

    • Choose "Yes" if you want to install iOS MDM support for the "Create an HTTPS listener for MDM" option, otherwise choose "No".

    • Specify a "Domain Name" for the new domain.

    • Select "Administration Server" (in Server Type) if deploying the Mobile Server on a WebLogic Administration Server, or select Managed Server if deploying the Mobile Server on a WebLogic Managed Server. The "Server Type" is only required if you are deploying the Mobile Server on a WebLogic Server.

    • Specify a name for the WebLogic Managed Server in "Managed Server Name". The "Managed Server Name" is only required if you are deploying the Mobile Server on a WebLogic Managed Server.

    • In Admin Port:

      • Specify an "Administrative Server" port for WebLogic. This is required for both - that is, if you are deploying the Mobile Server on a WebLogic Administration Server or on a Managed Server.

      • Specify an "Administration Port" for GlassFish.

        Ensure the port you specified is available.

    • In Server Port:

      • Specify a "Managed Server" port for WebLogic. The "Server Port" is only required if you are deploying the Mobile Server on a WebLogic Managed Server.

      • Specify a "Server Port" for GlassFish.

        Ensure the port you specified is available.

    • Specify a port number for WebLogic or GlassFish HTTPS listener in MDM Port if you specify to install iOS MDM support. This listener will be configured with two-way SSL.

    • Specify a name for the domain administrator in Admin Username. If you are deploying the Mobile Server on a WebLogic Server, the administrator name is set to weblogic.

    • Specify a password for the domain administrator in Admin Password. The WebLogic Server requires that the password is at least eight characters in length and contains at least one non-alphabetic character; otherwise, you will receive the following error: "The value for Admin Password is not valid."

    Note:

    The WebLogic domain directory is created by default as %APP_SERVER_HOME%\..\user_projects\domains\%Domain Name%; the GlassFish domain directory is created as %APP_SERVER_HOME%\domains\%Domain Name%. For example:

    If WebLogic is installed at C:\Oracle\Middleware\wlserver_10.3, and you specify "mobileserver" as the new domain name, then C:\Oracle\Middleware\user_projects\domains\mobileserver will be created and domain configuration files are stored at that directory.

    If GlassFish is installed at C:\glassfish3\glassfish, and you specify "mobileserver" as the new domain name, then C:\glassfish3\glassfish\domains\mobileserver will be created and domain configuration files are stored at that directory.

    Figure 4-17 Deploy the Mobile Server on a New WebLogic Server Domain

    
    

    Figure 4-18 Deploy the Mobile Server on a New GlassFish Server Domain

    
    

    To deploy the mobile server on an existing domain under Weblogic and Glassfish, follow the instructions:

    • Choose "No" for the "Create a new domain for the Mobile Server" option.

    • Choose "Yes" if you want to install iOS MDM support for the "Create an HTTPS listener for MDM" option, otherwise choose "No".

    • Specify a name for the existing domain in Domain Name. The "Domain Name" is only required if you are deploying the Mobile Server on a GlassFish Server.

    • Specify the "Domain Directory" for the existing domain.

    Note:

    For WebLogic, set the domain directory to the folder where your domain configuration files are stored; for GlassFish, set the domain directory to the parent of the folder where your domain configuration files are stored. For example:

    If you want to deploy mobile server on an existing WebLogic domain called "msDomain", and the domain configuration files are stored at C:\Oracle\Middleware\user_projects\domains\msDomain, then you should specify "C:\Oracle\Middleware\user_projects\domains\msDomain" as the Domain Directory.

    If you want to deploy mobile server on an existing GlassFish domain called "msDomain", and the domain configuration files are stored at C:\glassfish3\glassfish\domains\msDomain, then you should specify "C:\glassfish3\glassfish\domains" as the Domain Directory.

    • Select "Administration Server" (in Server Type) if you are deploying the Mobile Server on a WebLogic Administration Server, or select Managed Server if you are deploying the Mobile Server on a WebLogic Managed Server. The "Server Type" is only required if deploying the Mobile Server on a WebLogic Server.

    • Specify the "Administration Port" (in Admin Port) of the existing GlassFish Server domain. The "Admin Port" is only required if you are deploying the Mobile Server on a GlassFish Server.

    • Specify the "Server Port" of the existing GlassFish Server domain. The "Server Port" is only required if you are deploying the Mobile Server on a GlassFish Server.

    • Specify a port number for WebLogic or GlassFish HTTPS listener in MDM Port if you specify to install iOS MDM support. This listener will be configured with two-way SSL.

    • Specify the administrator name of the existing domain (in Admin Username).

    • Specify the password of the domain administrator (in Admin Password).

    Figure 4-19 Deploy the Mobile Server on an Existing WebLogic Server Domain

    
    

    Figure 4-20 Deploy the Mobile Server on an Existing GlassFish Server Domain

    
    

    To deploy the mobile server under TomEE, follow the instructions:

    • Specify the "Server Port" value with HTTP connector port value in default Service named "Catalina" of TomEE server.

      Ensure the port you specified is available.

    Note:

    You can look for the HTTP connector port value in %CATALINA_HOME%\conf\server.xml, where CATALINA_HOME is the installation directory of TomEE server.

    For example, the following is part of a content from %CATALINA_HOME%\conf\server.xml. In this example, the HTTP connector port value in default Service named "Catalina" is 8080.

    <Service name="Catalina">

    <Connector port="8080" protocol="HTTP/1.1"

    connectionTimeout="20000"redirectPort="8443" />

16. A summary screen appears informing you if a repository is installed or not. Click "Next".

17. The installation screen appears. Wait until the install is completed. Click "Next".

18. Once the repository wizard is finished, click "Finish" to leave the wizard.

19. Click "Exit" to complete the installation.

20. Review the installation log files repository.log or popolate.log for any errors, which are located in ORACLE_HOME\mobile\server. The repository.log file contains all general installation information on a successful installation, and installation errors on a failed installation. Sometimes, if an unexpected exception occurred and was not caught by OUI, a file named popolate.log is created and contains the exception stack.

21. When you configure multiple mobile servers against a single repository, this is known as a farm. You must enable the Device Manager, Mobile Manager and mobile client to work properly in a farm environment. For information on configuring all mobile servers to act properly in a farm, see Section 1.2, "Manage Mobile Server Farms" in the Oracle Database Mobile Server Administration and Deployment Guide.

22. When installation is completed, launch script runmobileserver on Linux or runmobileserver.bat on Windows to start the Mobile Server.

4.3.1.2 Installation of Mobile Development Kit

Install Mobile Development Kit from the Installation Types screen by performing the following:

1. Choose the "Mobile Development Kit" and clicking "Next".

   Figure 4-21 Select Mobile Development Kit

   
   

2. On the "Specify Home Details" screen, enter the name and path where you want to install Mobile Development Kit, which cannot include any spaces.

   Figure 4-22 Specify Home Details

   
   

3. On the "Summary" screen, click Install. Click "Exit" to return to the installation screen.

You have now installed the Mobile Development Kit.

4.3.2 Silent Install of the Mobile Server and MDK Components

You can execute a command-line tool that runs the installer in silent mode. That is, it installs either the Mobile Development Kit or the mobile server for you without having to use the Installation GUI. The following sections describe how to silently install these components on either the Windows or UNIX platforms:

• Section 4.3.2.1, "Silent Install for Mobile Server or Mobile Development Kit on Windows"

• Section 4.3.2.2, "Silent Install Mobile Server or the Mobile Development Kit on UNIX"

• Section 4.3.2.3, "Configuration File for Deploying Mobile Serve"

4.3.2.1 Silent Install for Mobile Server or Mobile Development Kit on Windows

The setup.exe command can be executed to run the installer in silent mode for Windows, as follows:

setup.exe  -responseFile 
/full_directory_path/stage/Response/oracle.mobile.install_type_2.rsp 
-silent -nowelcome

There are two response files that contain variables that define how the mobile server or the MDK are installed. The following sections describe the response files:

• Section 4.3.2.1.1, "Response File for Mobile Server Install"

• Section 4.3.2.1.2, "Response File for MDK Install"

4.3.2.1.1 Response File for Mobile Server Install

Variables to be filled for silent install in the response file oracle.mobile.install_type_2.rsp to install Oracle Database Mobile Server are as follows:

• Define the ORACLE_HOME destination directory, as follows:

  ORACLE_HOME="C:\MobileServer"
  

• Define the name for your Oracle Home, as follows:

  ORACLE_HOME_NAME="MobileServer"
  

• Provide the hostname, port, and user for the back-end database, where the repository is to be installed, as follows:

  s_repo_jdbc_url="jdbc:oracle:thin:@<host>:<port>:<sid>"
  

• Specify true or false if the repository is to be created on the back-end database, as follows:

  b_repository=true
  

• Provide the database system user name and password, as follows:

  s_db_admin_name="myuser"
  s_db_admin_pwd="mypwd"
  

• Provide the mobile server schema name and password, as follows:

  s_mobile_schema_name="myschema"
  s_mobile_schema_pwd="myschemapwd"
  

• Provide the demo schema user name and password, as follows:

  s_demo_schema_name="demoschema"
  s_demo_schema_pwd="demoschemapwd"
  

• Provide the demo client password, as follows:

  s_demo_client_pwd="Welcome1"
  

• Provide the mobile server administrator user name and password, as follows:

  s_mobileserver_admin_name="adminuser"
  s_mobileserver_admin_pwd="adminpwd"
  

• Specify true or false to indicate whether the samples are to be installed, as follows:

  b_mobile_samples=true
  

• Specify application server home, as follows:

  s_appserver_home="/path/to/appserver"
  

  Refer to Step 7 in Section 4.3.1.1, "Installation of the Mobile Server" for how to set application server home.

• Specify the configuration file for mobile server deploy. For more information, refer to Section 4.3.2.3, "Configuration File for Deploying Mobile Serve". Note that b_repository must set to true if you want to deploy mobile server:

  s_dep_conf_file="/path/to/mobileserver_config.ini"
  

• Specify JDK home, as follows:

  oracle.mobile.server:java_path="/path/to/jdk"
  

4.3.2.1.2 Response File for MDK Install

Variables in the oracle.mobile.install_type_1.rsp response file to install MDK, are as follows:

• Define the ORACLE_HOME destination directory, as follows:

  ORACLE_HOME="C:\MDK"
  

• Define the name for your Oracle Home, as follows:

  ORACLE_HOME_NAME="MDK"
  

• Specify JDK home, as follows:

  oracle.mobile.windows_mdk:java_path="/path/to/jdk"
  

4.3.2.2 Silent Install Mobile Server or the Mobile Development Kit on UNIX

You can install the mobile server and/or the Mobile Development Kit by using the runInstaller command, which is on the top level of the CD or the downloaded ZIP file for the product.

There are two response files that contain variables that define how the mobile server or the MDK are installed, which are located in the stage/Response folder of the CD or ZIP file.

4.3.2.2.1 Response File for Mobile Server Install

The response file for installing the mobile server is oracle.mobile.install_type_2.rsp. The variables that you can modify in this file for defining your install are as follows:

• Define the ORACLE_HOME destination directory, as follows:

  ORACLE_HOME="/home/user/mobileserver"
  

• Define the name for your Oracle Home, as follows:

  ORACLE_HOME_NAME="MobileServer"
  

• Provide the hostname, port, and user for the back-end database, where the repository is to be installed, as follows:

  s_repo_jdbc_url="jdbc:oracle:thin:@<host>:<port>:<sid>"
  

• Specify true or false if the repository is to be created on the back-end database, as follows:

  b_repository=true
  

• Provide the database SYSTEM user name and password, as follows:

  s_db_admin_name="myuser"
  s_db_admin_pwd="mypwd"
  

• Provide the mobile server schema name and password, as follows:

  s_mobile_schema_name="myschema"
  s_mobile_schema_pwd="myschemapwd"
  

• Provide the mobile server demo schema user name and password, as follows:

  s_demo_schema_name="demoschema"
  s_demo_schema_pwd="demoschemapwd"
  

• Provide the demo client password, as follows:

  s_demo_client_pwd="Welcome1"
  

• Provide the mobile server admin user name and password, as follows:

  s_mobileserver_admin_name="adminuser"
  s_mobileserver_admin_pwd="adminpwd"
  

• Specify true or false to indicate whether the samples are to be installed, as follows:

  b_mobile_samples=true
  

• Specify application server home, as follows:

  s_appserver_home="/path/to/appserver"
  

  Refer to Step 7 in Section 4.3.1.1, "Installation of the Mobile Server" for how to set application server home.

• Specify the configuration file for mobile server deploy. Refer to Section 4.3.2.3, "Configuration File for Deploying Mobile Serve" for more information.

  Note:

  b_repository must set to true if you want to deploy mobile server.

  s_dep_conf_file="/path/to/mobileserver_config.ini"
  

• Specify JDK home, as follows:

  oracle.mobile.server:java_path="/path/to/jdk"
  

4.3.2.2.2 Response File for MDK Install

The response file for installing the MDK is oracle.mobile.install_type_1.rsp. You can define the variables in this file for your install as follows:

• Define the ORACLE_HOME destination directory, as follows:

  ORACLE_HOME="/home/user/mdk"
  

• Define the name for your Oracle Home, as follows:

  ORACLE_HOME_NAME="MDK"
  

• Specify JDK home, as follows:

  oracle.mobile.linux_mdk:java_path="/path/to/jdk"
  

4.3.2.2.3 Execute Silent Install of Mobile Server and MDK on UNIX

After modifying the response files, if you want to install both the mobile server and the MDK, then execute the runInstaller command twice. Each execution is provided a different response file. The following installs the mobile server, as follows:

./runInstaller  -responseFile 
    /full_directory_path_to_response_file/oracle.mobile.install_type_2.rsp 
    -silent -nowelcome

where the options for this command are as follows:

Table 4-3 The runInstaller Command Options

Command Option	Description
responseFile	Provide the path and name of the response file for the component that you are installing. There are two response files: one for installing the mobile server and one for installing the MDK.
silent	Always use this option, as it defines that this is a silent installation.
nowelcome	Stops the GUI from displaying.

4.3.2.3 Configuration File for Deploying Mobile Serve

The configuration file specified in s_dep_conf_file variable is used to specify the required information to deploy mobile server. The file must be an INI format file. You can find the sample configuration file at %ORACLE_HOME%\Mobile\Server\admin\mobileserver_config.ini.

Refer to Table 4-4, "Configuration File for Deploying Mobile Server on WebLogic, GlassFish and and TomEE Servers" and Table 4-5, "Sample Configuration File" for information on specifying the configuration to deploy mobile server:

Table 4-4 Configuration File for Deploying Mobile Server on WebLogic, GlassFish and and TomEE Servers

Parameters	Description
domain_name	String type, required for WebLogic and GlassFish. Name of the WebLogic Server domain or GlassFish Server domain. If deploying the Mobile Server on a WebLogic Server and 'create_new_domain=false', this parameter is not required.
domain_dir	String type, required for WebLogic and GlassFish. Domain directory. Refer to Step 16 in Section 4.3.1.1, "Installation of the Mobile Server" for how to set the domain directory.
admin_user	String type, required for WebLogic and GlassFish. Name of the domain administrator.Note: Use 'weblogic' as the administrator user name if you are creating a new domain for WebLogic Server.
admin_password	String type, required for WebLogic and GlassFish. Password of the domain administrator, please change the password after deployment. Note: WebLogic Server requires that the password is at least eight characters in length and contains at least one non-alphabetic character.
server_port	Integer type, required for GlassFish, TomEE and WebLogic Managed Server. Set it to the server port for GlassFish and TomEE. If deploying the Mobile Server on a WebLogic Managed Server and 'create_new_domain=true', this parameter is required, set it to the Managed Server port
admin_port	Integer type, required for WebLogic and GlassFish. Set it to domain administration port for GlassFish. If deploying the Mobile Server on either a WebLogic Administration Server or a Managed Server, and 'create_new_domain=true', this parameter is required. Set it to Administration Server port for WebLogic.
create_new_domain	Boolean type, optional. Set to 'true' to create a new domain, or set to 'false' to use an existing domain, default value is 'true'.
force_deploy	Boolean type, optional. If set to 'true', redeploy the Mobile Server even if it has already been deployed or already exists, default value is 'false'.
managed_server_name	String type, required for WebLogic if deploying the Mobile Server on a WebLogic Managed Server. Managed Server name.
target_server_type	String type, required for WebLogic. Set to 'A' if deploying the Mobile Server on a WebLogic Administration Server. Set to 'M' if deploying the Mobile Server on a WebLogic Managed Server.

Table 4-5 Sample Configuration File

Server Type	Sample Configuration
WebLogic Server configuration	Specify the configuration parameters in [WLS] section[WLS]domain_name=mobileserver_wlsdomain_dir=C:\Oracle\Middleware\user_projects\domains\mobileserver_wlsadmin_user=weblogicadmin_password=welcome1admin_port=7001server_port=7009managed_server_name=ManagedServertarget_server_type=Mcreate_new_domain=trueforce_deploy=true
GlassFish Server configuration	Specify the configuration parameters in [GFS] section[GFS]domain_name=mobileserver_gfsdomain_dir=C:\glassfish3\glassfish\domainsadmin_user=adminadmin_password=welcome1server_port=8090admin_port=8089create_new_domain=trueforce_deploy=true
TomEE Server configuration	Specify the configuration parameters in [TOMEE] section[TOMEE]server_port=8080force_deploy=true

4.3.3 Providing High Availability with a Farm of Multiple Mobile Servers

In some cases, you may want to have multiple mobile servers using the same mobile server repository on an Oracle database or an Oracle RAC database. For example, as Figure 4-23 shows, if you wanted to load balance your mobile clients across multiple mobile servers, you could add a load balancer—such as Oracle Web Cache—before the shared mobile servers, and then your clients would be balanced across these mobile servers, of which each accesses the same data in the shared repository.

This is the type of configuration that entails an Oracle Database Mobile Server Farm.

Figure 4-23 Multiple Mobile Servers Sharing a Repository

Description of "Figure 4-23 Multiple Mobile Servers Sharing a Repository"

You can install multiple mobile servers, each on its own host, that use the same mobile server repository, as follows:

1. Install the load balancer. Refer to Section 9.6 "Using a Load Balancer" in Administration and Deployment Guide for instructions about how to install a load balancer. Oracle Database Mobile Server certifies Oracle Web Cache as a load balancer. You can use any load balancer as long as the JSESSIONID is used.

2. Install the first mobile server and the mobile server repository following the instructions in Section 4.3.1.1, "Installation of the Mobile Server".

3. Install additional mobile servers. For each subsequent mobile server, follow the instructions in Section 4.3.1.1, "Installation of the Mobile Server", supplying the same JDBC URL for the back-end Oracle database where the mobile server repository exists. Select Yes for creating the repository, which registers the shared mobile server with the repository.

4. Configure mobile servers with the load balancer URL. Because the mobile client accesses any of these mobile servers through a load balancer, you need to configure each mobile server with the load balancer URL. This ensures that when the setup.exe is downloaded by the client, the executable automatically includes the load balancer URL, instead of the mobile server URL.

   This process is similar to how the mobile server is configured to use with a reverse proxy. Configure both the reverse_proxy and DM_AUTO_SYNC_CACHE parameters in the mobile.ora configuration file, as follows:

   [MOBILE]
   REVERSE_PROXY=http://<load_balancer_hostname>:<port_number>/mobile
   DM_AUTO_SYNC_CACHE=YES
   

5. In a configuration with multiple mobile servers and a load balancer, you must ensure that the load balancer is configured to route HTTP requests within the same HTTP session to the same mobile server. To do this, configure the load balancer to honor the JSESSIONID cookie. When a user logs into a mobile server, an HTTP session is created for that user. An HTTP cookie with the name JSESSIONID is sent back to the mobile client. Subsequent HTTP requests from the mobile client will contain the HTTP cookie, which allows the mobile server to identify the session for that user. Refer to Section 9.6 "Using a Load Balancer" in Administration and Deployment Guide for more instructions about how to configure the load balancer to use with a mobile server farm.

   If the load balancer uses a different algorithm to distribute HTTP requests, such as round-robin or server-load based, then the mobile server will not work correctly.

6. Perform additional configuration for device management and data synchronization for all mobile servers in the farm as described in Section 1.2, "Manage Mobile Server Farms" in the Oracle Database Mobile Server Administration and Deployment Guide.

4.3.4 Install Oracle Database Mobile Server on Linux

The following sections provide considerations when installing Oracle Database Mobile Server on a Linux platform:

• Section 4.3.4.1, "Patch Required if Using Linux Redhat 3.0"

• Section 4.3.4.2, "Providing Enough Swap Space on the Linux Platform"

4.3.4.1 Patch Required if Using Linux Redhat 3.0

If you install Oracle Database Mobile Server on Linux Redhat 3.0 and the following error occurs, apply the 3006854 patch and start the installation again.

Error occurred during initialization of VM Unable to load native library: /tmp/myhost/jre/lib/i386/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference.

4.3.4.2 Providing Enough Swap Space on the Linux Platform

If the swap space is not sufficient on your Linux machine, then modify the value for the SWAP_SPACE variable in the install/linux/oraparam.ini file. The default value is set to SWAP_SPACE=1536. For example, if your machine is not as powerful, decrease the swap space; for example, SWAP_SPACE=1024.

4.3.5 Mobile Client Install

The mobile client can use either Berkeley DB, SQLite or JavaDB database. For instructions on how to install the mobile client, see Chapter 2, "Installing the Mobile Client" in the Oracle Database Mobile Server Mobile Client Guide.

4.4 Starting and Stopping Mobile Server

The following describes how to start and stop the mobile server on the windows machine and on the UNIX machine:

• Section 4.4.1, "Starting Mobile Server"

• Section 4.4.2, "Stopping Mobile Server"

4.4.1 Starting Mobile Server

• To start the Mobile Server on a Windows machine, use one of the options below:

  • On the Windows Start Menu, navigate to All Programs -> Oracle Database Mobile Server 12c -> Mobile Server. Click on Mobile Server item to start the Mobile Server (Right-click and use Run as Administrator on Windows 7 or later version).

  • Open a command prompt (use Run as Administrator on Windows 7 or later version), change the directory to %MOBILE_HOME%\Mobile\Server\bin, and run the script runmobileserver.bat.

  • Start the Application Server on which the Mobile Server is deployed. The Mobile Server then automatically starts.

• To start the Mobile Server on a UNIX machine, use one of the options below:

  • Open a shell, change the directory to $MOBILE_HOME/mobile/server/bin and run the script runmobileserver.

  • Start the Application Server on which the Mobile Server is deployed. The Mobile Server then automatically starts.

4.4.2 Stopping Mobile Server

• To stop the Mobile Server on a Windows machine, use one of the options below:

  • Open a command prompt (use Run as Administrator on Windows 7 or later version), change the directory to %MOBILE_HOME%\Mobile\Server\bin, and run the script stopmobileserver.bat.

  • Stop the Application Server on which the Mobile Server is deployed. The Mobile Server then automatically stops.

• To stop the Mobile Server on a UNIX machine, use one of the options below:

  • Open a shell, change the directory to $MOBILE_HOME/mobile/server/bin and run the script stopmobileserver.

  • Stop the Application Server on which the Mobile Server is deployed. The Mobile Server then automatically stops.

Note:

• The runmobileserver and stopmobileserver scripts contain the default Java flags. If you want to modify the flags for how Mobile Server is started or stopped, you can modify the scripts as appropriate.

• On WebLogic Server release 12.1.2, if the Derby Server is installed, it is automatically started when WebLogic Server starts. If you do not want to start the Derby Server, pass noderby as an argument to the startWebLogic command. For example, in the runmobileserver.bat script, call %WLS_DOMAIN_DIR%\bin\startWebLogic.cmd noderby.

• If the Mobile Server is deployed on a WebLogic Managed Server, and you are starting the Mobile Server for the first time, ensure the Administration Server is running in the same domain. To start the Administration Server, call the script:

  • %WLS_DOMAIN_DIR%\bin\startWebLogic.cmd (Windows)

  • $WLS_DOMAIN_DIR/bin/startWebLogic.sh (UNIX)

    The WLS_DOMAIN_DIR is the WebLogic Server domain directory. For more information, see http://docs.oracle.com/middleware/1212/wls/START/overview.htm#i1070184 (Starting an Administration Server with a Startup Script)

4.5 Testing Your Mobile Server Installation

To verify your installation, open your browser, input Mobile Server URL http://<Mobile_Server_hostname>:<port>/mobile, and check that the Mobile Manager login page is displayed, as shown in Figure 4-24.

Figure 4-24 Mobile Manager Login Page

Log on to the "Mobile Manager" with the Mobile Server Administrator user name and password and the Mobile Server Farm Page is displayed.

4.6 Removing Demo Applications

Before you use Oracle Database Mobile Server in a production environment, you may wish to remove the demo applications. To remove the demo applications, execute the following batch file:

demoinstaller [-install | -uninstall] <sys_user> <sys_pwd> <mobile_user> <mobile_pwd>

where the options are as follows:

Option	Description
-install or -uninstall	-install: install the demos -uninstall: remove the demos
<sys_user> <sys_pwd>	Provide the system user name and password that are used to drop the schema in which the demos are installed.
<mobile_user> <mobile_pwd>	Provide the mobile server log on user name and password, which is necessary to remove the demos from the repository.

The removal process enables you to delete the schema into which the applications were installed. If you did not use the schema for any other purpose, then allow the batch file to remove the demo application schema.

4.7 How to Uninstall Oracle Database Mobile Server

Uninstall the Oracle Database Mobile Server components through the Oracle Universal Installer, also perform the following tasks:

1. Delete the following directories:

   • ORACLE_HOME\Mobile

   • If you are using WebLogic, delete the <app_server_deployment_dir>\mobile directory.

2. Drop TABLESPACE SYNCSERVER INCLUDING CONTENTS

3. Delete the Mobile01.dbf database file from the operating system.