Bookshelf Home | Contents | Index | Search | PDF |
Siebel Remote and Replication Manager Administration Guide > Siebel Remote Concepts > Siebel Remote Architecture >
Siebel Remote Flow Diagram
Figure 2 illustrates the Siebel Remote flow process. Numbers in the diagram relate to explanations in Table 1. The purpose of this diagram and table is to provide a general overview of the process.
After Table 1, there are smaller diagrams for the two parts of the Remote flow process—data downflow (Figure 3) and data upflow (Figure 4).
Table 2 lists notes on the Siebel Remote flow process (Figure 2).
Table 2. Siebel Remote Flow Diagram Notes Topic Comments Remote Configuration File
- The DockConnString is the logical Siebel server name. This represents the server where a mobile client was extracted. It should be populated when the client is first initialized.
- An important configuration parameter, AutoStopDB, is part of the Local configuration. Its default is FALSE, which means the local database engine will keep running after Siebel eBusiness Applications shut down. This will help shorten the startup time when the user restarts Siebel eBusiness Applications. If AutoStopDB is set to TRUE, the local database engine will shut down automatically when the Siebel eBusiness Applications shut down.
- In the local database connecting string, -q means the local database is started in quiet mode. This prevents a SQL Anywhere window from showing up. However, a SQL Anywhere icon will appear on the Windows task bar, whether or not the -q parameter is used. This provides the user with a way to manually stop the database engine, if the user leaves the engine running after Siebel eBusiness Applications shut down.
- On the local database connect string, the - m means truncate transaction log after checkpoint; -x NONE means do not load any network drivers; -gp 4096 tells the engine that the database page size is 4,096 bytes;
-c40m -ch60m sets the initial cache size to 40 MB, with a maximum of 60 MB. The cache sizes are suggested values that the user can adjust. However, the SQL Anywhere engine will determine the actual cache size within the given range of values.- In Siebel 7.5, users can specify the sorting order on Local and Sample databases. To enable this feature, users modify their CFG file (for example, siebel.cfg, uagent.cfg). The SortCollation parameter in the CFG file determines the sorting order of the SQL Anywhere database. For more details about this topic, see Siebel Web Client Administration Guide.
Authentication A Synchronization Manager component parameter—you identify the type of authentication used during synchronization. Options include:
- Siebel. Synchronization Manager will compare the password used to login to the local db to the Sync Password stored in a Siebel table within the server database.
- Siebel/db password. Synchronization Manager will compare the password used to login to the local db to the mobile Web client's user name and password to connect to the server database.
- Operating system password (Win 2000 and UNIX). Synchronization Manager will compare the password used to login to the local db to the operating system password for the user on the application server.
Synchronization Frequency Siebel Systems recommends that mobile users synchronize against the server at least daily. There is an automatic mechanism to help enforce frequent synchronization. Users can invoke autosynchronization on their laptops. For more detail about this topic, see Using Autosynchronization.Figure 3 illustrates the Remote downflow of data. See Table 1 for explanation of the numbered steps.
Figure 4 illustrates the Remote upflow of data transactions. See Table 1 for explanation of the numbered steps.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Remote and Replication Manager Administration Guide, Version 7.5, Rev. A Published: 18 April 2003 |