Overview of Deployment for the Siebel Mobile Disconnected Application Client

This topic provides an overview of important factors to consider when configuring Siebel Server for Siebel Mobile disconnected application synchronization. When planning and executing the deployment of a mobile application using server synchronization, you must understand the hardware and network requirements. While these factors are generally applicable to all deployments, there are unique aspects to each customer configuration and implementation. Therefore, it is recommended that customers conduct detailed configuration, sizing, and production-readiness reviews. For help with detailed configuration, sizing, and production readiness reviews, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services. This is especially important for complex deployments, such as those supporting large numbers of users over wide, geographic areas.

You can also improve the performance and scalability of server synchronization deployments by working with the parameters of the Siebel application server component. For more information about the Siebel application server, see "Optimizing Siebel Server Process Management for Siebel Mobile Disconnected Application Synchronization".

Note: The recommendations in this chapter are general ones and are intended to raise your awareness of the key factors in Siebel Mobile disconnected application synchronization, performance, and scalability. These factors must be confirmed in your environment, and the usage patterns in your enterprise must be considered.

Overview of Siebel Server Topology

"Server and Components" shows the servers and components that are required to deploy server synchronization for a mobile application. The components are as follows:

• Siebel Mobile disconnected application database

• Siebel Server

• Siebel Web engine

• Siebel Mobile disconnected application

The synchronization components are as follows:

• Synchronization engine for the Siebel Mobile disconnected application, which resides on Siebel Server.

• Siebel Mobile disconnected Synchronization Client, which resides on the Siebel Mobile disconnected application.

Figure 6-1 Server and Components

Recommended Hardware and Network Configuration

The critical factor in sizing the implementation of a Siebel Mobile disconnected application is the expected, peak-synchronization load. When calculating this load, consider the following specific, mobile-application variables. You must consider these variables within the context of the hardware specifications, including memory and processor speed:

• Number of concurrent users

• Number of transactions

• Size of the data file

The following resources are available as you plan the implementation of your Siebel Mobile disconnected application:

• Refer to Microsoft and manufacturer documentation for comprehensive information on server hardware and registry parameters.

• For assistance with hardware planning and network implementations for mobile applications, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.