The following sections describe configuration parameters for the mobile server:
Section A.1, "Configuration Parameters for the MOBILE.ORA File"
Section A.2, "Data Synchronization Requirements in INIT.ORA"
The mobile server uses the mobile.ora
file to initialize the mobile server; thus, if you modify these parameters, you must restart the mobile server to receive the change.
The following sections define system-wide parameters for the mobile server in the mobile.ora
file:
Table A-1 lists the APPLICATIONS
parameters and their usage definitions.
Table A-1 APPLICATIONS Parameters
Parameter | Definition |
---|---|
|
Location for the Packaging Wizard help file. This is only used with MDK. and only for the purpose of Debug / Support. |
|
Name of the XML file used by the Packaging Wizard to store the application information. This is only used for Debug / Support. |
[The following MOBILE
parameters control the behavior of the mobile server.
Table A-2 lists MOBILE
parameters and their usage definitions.
Parameter | Definition |
---|---|
|
Encrypted user password. Users must not try to edit the encrypted password. This parameter can be set by navigating to the following URL.
|
|
Admin port for starting the mobile server. |
|
JDBC URL that the mobile server uses to connect to the mobile server repository in the back-end Oracle database. For a description of the syntax for the JDBC URL, see Section 2.2, "Connecting to the Back-End Oracle Database". |
|
Encrypted user name. Users must not try to edit the encrypted user name. This parameter can be set by navigating to the following URL.
|
|
Set to YES to turn on this feature to force the DeviceManager to synchronize the cached data on user-related events, such as create, edit or delete user. |
|
Mobile Server Installation Type, which describes the application server type where the mobile server is running. Do NOT modify, for internal use only. |
|
Set this parameter to designate what type of IP address the client uses. If you are using a dynamic (DHCP) dynamic IP address, set the parameter to If using DHCP, the underlying code needs to know to not use the IP address that was used for the previous connection/synchronization. If you are using DHCP and have set this parameter to Internally, the Disabling Java IP caching may effect performance with the additional DNS lookups. In addition, there is a risk of DNS spoofing. See the Sun Microsystems Java documentation for more information. |
|
Limits the number of threads available in the connection pool. If threading problems occur, set this parameter to 0 or 1. |
|
Location of the Oracle Home where the mobile server is installed. |
|
The port number on which the mobile server is running. |
|
This parameter provides security for accounts with administrator access. With this parameter, the mobile server can be configured to allow login requests to a specified set of IP addresses for accounts with administrator access. With this parameter, you can also restrict access to the Mobile Server Startup feature. Only valid login requests from a browser that runs on machines whose IP address is listed as a value of this parameter will be granted access. For example, Note: Users who have administrator access should not connect through a proxy server. |
Set this parameter if a Reverse proxy is used with the mobile server. See Section 9.6.1, "Using a Reverse Proxy to Communicate from Internet to Intranet" for details. |
|
|
Turn this parameter on (TRUE) if you want to enable Oracle Single Sign on (SSO) authentication on the mobile server. If this parameter is turned on then the users trying to connect to the mobile server in the online mode will receive the login page from the SSO server. |
|
Number of attempts to modify a JDBC connection before timing out. |
|
If this parameter is set to |
|
This URL is used by applications to connect to the mobile server repository database. For a description of the syntax for the JDBC URL, see Section 2.2, "Connecting to the Back-End Oracle Database". |
|
If set to yes, searches for Java classes in the computer's classpath before searching the mobile server repository. |
The following FILESYSTEM
parameters control the behavior of the mobile server repository.
Table A-3 lists [FILESYSTEM]
parameters and their definitions.
Table A-3 FILESYSTEM Parameters
Parameter | Definition |
---|---|
|
Root Directory. Valid only for OS file system. This directory path format applies to the environment where the mobile server runs on Solaris. Replace |
|
Root directory. Valid only for OS file system. This directory path format applies to the environment where the mobile server runs on Windows NT. Replace |
The following DEBUG
parameters control the debugging messages in the mobile server.
Table A-4 lists DEBUG
parameters and their definitions.
Parameter Name | Definition |
---|---|
|
Trace destinations are
|
|
Used to turn the trace feature on ( |
|
Used as base name to arrange trace files in sequential order starting from For example: If you set the following parameters.
then, the Trace files will be named Sample Value: |
|
Used to specify an individual trace file pool for every individual user. Applicable only when the File option is the Trace destination. If set to If set to Example: |
|
The default value is 5. This parameter specifies the number of files in the trace file pool. If the pool limit is reached, the trace output is overwritten to the first file in the pool. See also |
|
Used as the maximum file size in MB for trace files. If the threshold value is about to be reached, the trace feature generates output to the next trace file in the pool. For more information, see |
|
There are three levels of trace messages:
In addition, all errors and exceptions are sent to level -1, which have the binary 11111111. All Java The parameter value for EXAMPLE: If you set the following parameters, 3 & 1 (Basic) = 1 > 03 & 2 (SQL) = 2 > 03 & 4 (Function) = 0 = 0 |
|
The trace output is generated to the named machine, on which the synchronized trace can be viewed using the Example: |
|
Machine name where |
|
Trace output is generated to the named port on the |
|
List of valid user names. The user trace and system trace information which is listed is generated as trace output. If the value is an empty string Note: As the administrator, you must not use the Example: If you set this parameter as follows, |
The CONSOLIDATOR
parameters control the behavior of Data Synchronization. The values that are listed in the following table are default values.
Table A-5 Consolidator Parameters
Parameter Name | Definition |
---|---|
|
Specifies in seconds the delay between successive attempts to apply a client's In Queue. Related to the |
|
Comma-separated list of users, where each user's downloaded data is cached. |
|
If set to However, if you are developing an application and you are executing a test, such as a performance test, you will resend the same client request to the server repeatedly to test how the server responds under heavy load. Only in this case would you want to set this parameter to |
|
Specifies in seconds the MGP timeout for the compose phase for each user to complete. If the compose phase for this user does not complete, MGP retries the compose phase for this user in the next cycle. If the compose consistantly fails then increase timeout value. Monitor the MGP logging to evaluate how long the compose takes to complete; then add 50% to the value ensure that slightly larger datasets compose completely. |
|
Configure whether to validate a database connection before retrieving (borrowing) it from the connection pool. By default, this value is YES. |
|
Configure whether to validate the database connection before releasing it back to the connection pool. By default, this value is YES. If the examination determines that the connection is not valid, then it is destroyed instead of being returned to the connection pool. |
|
Enables pooling of database connections if set to YES. |
By default, before the MGP processes the Compose phase for a user, it checks to see if user data has been uploaded into the In Queue. If so, then the Compose is not performed to ensure that user data is not overwritten. Instead, the Compose phase is not executed until the MGP runs the Apply/Compose phase again. Setting |
|
|
Specify the index attributes for the In Queue table indexes, which exist in the back-end Oracle database. These can include the storage characteristics and the following attributes: |
|
Specify the physical and/or table properties for the In Queue tables, which exist in the back-end Oracle database. These can include the storage characteristics and the following properties: |
|
This is the |
|
If set to |
|
The amount of time in seconds that the Job Scheduler sleeps in each loop. |
|
Specifies in the number seconds the delay between successive attempts to lock the log tables. Related to the |
|
Control the magic number checking of publication items. If enabled, and there is a mismatch between the server and the client magic numbers, the publication item receives a complete refresh. If set to A shared publication item has the following characteristics:
|
|
Specify the index attributes for the map table indexes, which exist in the back-end Oracle database. These can include the storage characteristics and the following attributes: |
|
Specify the physical and/or table properties for the map tables, which exist in the back-end Oracle database. These can include the storage characteristics and the following properties: |
|
Specifies the maximum number of times the MGP retries to apply the client In Queue data before terminating the apply phase. |
|
JDBC performance parameter which defines the number of DML records (inserts only) to send from the mobile server to the back-end Oracle database at one time. Without batching, each record is sent to the database one at a time. These records are originally from client. This only applies to insert, and not to delete or update records. |
|
Specifies the number of attempts to lock the logs before giving up the compose phase. |
|
Specifies the number of threads spawned within the MGP process. This parameter value should be set to an equivalent number of CPUs. We recommend this value is set to 1.5 times the number of CPUs. The default is 3. |
The You may want to modify the See Section 2.7.1.10, "BeforeSyncMapCleanup" in the Oracle Database Mobile Server Developer's Guide for more information. |
|
|
How often should MGP compose phase look for map table records that are marked for deletion but have been re-added to the subscription. By default, this is set to 1. If the application logic guarantees that such records never exist, then this check may be skipped altogether by setting the value to –1, which improves MGP compose performance. |
|
If set to |
|
If set to |
|
This is a server-side parameter that defines the filename of the resume buffer for the client users. By default, we use memory mapped file; however, with this parameter, users can provide their own storage files. The size of this file is specified by the For more information on how to use |
|
|
|
The You can enable maximum concurrent clients by setting |
|
The |
|
The |
|
The |
By default, before the MGP processes the Compose for a user, it checks to see if user data has been uploaded into the In Queue. If so, then the Compose for the user is not performed to ensure that user data is not overwritten. Instead, the Compose phase is not executed until the MGP runs the Apply/Compose phase again. Setting |
|
Specifies how long (in milliseconds) the MGP sleeps before scheduling the next client's apply phase. By default, it is set to 2 milliseconds. |
|
|
The number of prepared statements to be cached for each connection. These statements are not re-parsed by the database when they are prepared again. To turn off caching, set this variable to |
|
If set to |
|
If set to |
|
Specifies the directory where the binary trace file, which includes the request and response data, is written. This file is created to cache the data in transport, so that if a failure occurs, Oracle Database Mobile Server can recover. You initialize this binary trace file by selecting the Data Trace Type checkbox. |
|
Specifies whether the JVM implementation of ZIP or the Oracle pure Java version for compression should be used. This is a performance parameter, where depending on a particular environment, each implementation may have different performance results. By default, this is set to YES to use the JVM implementation. |
Data Synchronization uses a log engine that supports the following parameters for logging:
GLOBALLogger
SYNCLogger
MGPLogger
MGPAPPLYLogger
MGPCOMPOSELogger
Each parameter sets up a logger for a component which you can use to specify the trace level, trace type, trace destination, trace file pool size, trace file size, and trace users in the following sample format.
<X>Logger=TRACE_LEVEL=<
trace_level
>|TRACE_TYPE=<
trace_type[,trace_type...]
>|TRACE_DESTINATION=<
trace_destination
>[|TRACE_FILE_POOL_SIZE=<
trace_file_pool_size
>|TRACE_FILE_SIZE
=<trace_file_size
>|TRACE_USER=<
trace_users
>]
Note:
Separate each parameter with the '|
' symbol. Separate values with a comma ',
'.
If there are any invalid values in the definition, the whole definition is ignored.
For each logger, the trace level, type, and destination parameters are mandatory.
The parameters TRACE_FILE_POOL_SIZE
and TRACE_FILE_SIZE
are only applicable for the GLOBALLogger
only.
If you define the LOCAL_CONSOLE
, then you must also define SYNCLogger
and GLOBALLogger
.
Table A-6 lists the parameters for each logger.
Table A-6 Acceptable Parameter Values
Parameter | Description |
---|---|
|
Trace Level parameter can be set to the following trace message levels:
Examples:
|
|
|
|
The administrator can set this parameter to any of these destinations: Sample Value: |
|
The default value is 2. This parameter specifies the number of files in the trace file pool. If the pool limit is reached, the trace output is overwritten to the first file in the pool. See also |
|
Used as the maximum file size in MB for trace files. If the value is about to be reached, the trace feature generates output to the next trace file in the pool. For more information, see |
|
List of valid user names. The listed user trace information and system trace information is generated as output. If the value is an empty string |
The new log engine does not support the parameters that have been used in the old log engine. They are:
TRACE_REMOTE_PORT
TRACE_REMOTE_MACHINE
TRACE_REMOTE_HOST
The parameters in Table A-7 are used for configuring external authentication.
Table A-7 EXTERNAL_AUTHENTICATION
Parameter | Description |
---|---|
|
The external |
|
The mobile server caches the user instantiated through the external authenticator for a period of time in order to improve efficiency. Provide the number of sections for this period. The default expiration time for the cached user object is 30 minutes (or 1800 seconds). |
The following sections describe the Data Synchronization requirements for Oracle and Oracle parameter settings in the init.ora
file:
You should set the following parameters in the file init.ora
as given below:
Table A-8 lists parameters that must be set in the file init.ora
:
Check values for processes and DML_LOCKS
. Massive concurrent synchronization processes use the maximum amount of resources. For each one of the concurrent clients, Data Synchronization requires one database connection (one session, one transaction). Therefore, the parameter value of PROCESSES
must be set to be no less than the maximum number of concurrent clients.
During the sync, the Data Synchronization will make changes to the publication map tables. One DML lock is needed for each client and changed publication:
DML_LOCKS
= (Number of changed publications) * (Maximum number of concurrent clients)
During the first and second sync, all publication map tables are changed for each client. So, the required DML locks are:
DML_LOCKS
= (Number of publications) * (Maximum number of concurrent clients)
If you have a large number of publications, the default DML_LOCKS
may not be sufficient. You should set it explicitly in the file init.ora
. For example, CRM has approximately 50 publications. For 30 concurrent first syncs, Data Synchronization needs 1500 DML locks. The default value for DML_LOCKS
with PROCESSES
set to 200 is 1000.