Siebel Medical Handheld Guide > Deploying Siebel Handheld Applications >

Overview of Deployment for the Siebel Handheld Application Client

This topic provides an overview of important factors to consider when planning a Siebel Handheld application deployment using Direct Server Synchronization (DSS). One aspect of successful planning and execution of a Handheld application deployment using DSS is to understand hardware and network requirements. While these factors are generally applicable to all deployments, there are unique aspects to each customer configuration and implementation strategy. 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 DSS deployments by working with the Siebel application server component parameters. For more information about the Siebel application server, see Optimizing Siebel Server Process Management for Direct Server Synchronization.

NOTE:  The recommendations in this chapter are general ones and are intended to raise your awareness of the key factors in Siebel Handheld application synchronization, performance, and scalability. These factors must be confirmed for your actual environment, and the usage patterns in your enterprise must be taken into consideration.

Siebel Server Topology Overview   

The diagram in Figure 5 shows the servers and components that are required to deploy Direct Server Synchronization for a Handheld application. The components are the Siebel Handheld application database, Siebel Server, Siebel Web engine, and Siebel Handheld application. The synchronization components are the synchronization engine for the Siebel Handheld application which resides on Siebel Server, and the Siebel Handheld Synchronization Client which resides on the Siebel Handheld application.

CAUTION:  Companion Synchronization uses Siebel Remote to complete the synchronization process to the Siebel Server from the laptop. The remote mobile user's routing model must be set to Handheld User. Otherwise, synchronization fails. For more information about Siebel Remote, see Siebel Remote and Replication Manager Administration Guide.

Figure 5. Servers and Components

Recommended Hardware and Network Configuration

There are many factors to take into account when designing and implementing your server and network hardware and architecture, and sizing your Siebel Handheld application database. The critical factor in sizing the implementation for a Siebel Handheld application is the expected peak synchronization load. Specific Handheld application variables to consider in calculating this load are: the number of concurrent users, number of transactions, and size of the data file. These variables must be considered within the context of the hardware specifications, including memory and processor speed.

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

• Refer to Microsoft and manufacturer documentation for comprehensive information on server hardware and registry parameters.
• For specific recommendations on the following topics, refer to Bulletin 476964.1 on My Oracle Support. This document was previously published as Siebel Technical Note 405.
  • Server architecture
  • Server hardware and registry parameters
  • Database server sizing
  • Database tuning
  • Dial-Up and network
  • Wireless
  • VPN (Virtual Private Networks)
• The Handheld Review Package assists customers with planning their hardware and network implementations for Handheld applications. For help with Handheld Review Package, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.