15Reference Materials for Siebel Remote
Reference Materials for Siebel Remote
This chapter describes reference information for Siebel Remote. It includes the following topics:
Values for System Preferences
The following table lists values for system preferences for Siebel Remote. You specify these values in the Remote System Preferences view of the Administration - Siebel Remote screen.
Table Values for System Preferences for Siebel Remote
| System Preference | Default Value | Other Values |
|---|---|---|
Docking Timestamp Source |
Client Transaction Time |
Server Database Merge Time |
Enable Mobile Password Expiration |
Check box contains a check mark, by default. |
No check mark |
Enable Mobile Password Syntax Check |
Check box contains a check mark, by default. |
No check mark |
Enable Mobile Web Client Lockout |
Check box contains a check mark, by default. |
No check mark |
Enable Transaction Logging |
Check box contains a check mark, by default. |
No check mark |
Expiration Period |
5 |
Positive integer greater than zero is a valid value. |
Failed Login Attempts |
2 |
Positive integer is a valid value. |
Intersection Table Conflict Resolution |
Merge |
You can use the following values:
|
Intersection Table Merge Rule |
First In |
Last In |
Lockout Period |
1 |
Positive integer is a valid value. |
Merger Friendly Notification |
Conflicts |
You can use the following values:
|
Merger Transactions Commit |
50 |
You can use the following values:
|
Minimum Number of Characters |
5 |
Integers from 1 through 15 are valid. |
Optimized Visibility Check |
Check box contains a check mark, by default. |
No check mark |
Password Content |
Alphanumeric Special Character |
You can use the following values:
|
SFM: Maximum File Attachment (KB) |
100 |
Positive integer is a valid value. |
System Conflict Resolution |
Server Wins |
Client Wins |
Visibility Rules Per Statement |
50 |
Not applicable. |
Visibility Rules Per Statement 1 |
20 |
Not applicable. |
Visibility Rules Per Statement N |
1 |
Not applicable. |
Warning Period |
2 |
Positive integer is a valid value. |
Server Component Parameters
This topic describes parameters for server components that Siebel Remote uses. It includes the following information:
For information about how to use generic parameters with these server components and how to use the Server Manager utility to manage server components, see Siebel System Administration Guide.
Parameters of the Synchronization Manager Server Component
The following table describes some of the parameters you can use with the Synchronization Manager server component.
Table Some of the Parameters of the Synchronization Manager Server Component
| Name | Alias | Required | Description |
|---|---|---|---|
Authentication Method |
Authentication |
Optional |
Method that Siebel Remote uses to authenticate remote clients. You can use one of the following values:
|
Database Connection Timeout |
DBConnectionTimeout |
Optional |
Determines if the Siebel Server attempts to prevent automatic closure of an idle database connection. In some situations, your database software might automatically close the connection if it is idle longer than an amount of time. This might occur when Siebel Remote initializes a local database when there is a slow communications link to the Siebel database (server database), such as might be the case with some connections to IBM DB2 on z/OS. If the Database Connection Timeout for parameter is 0, then the Siebel Server does not attempt to prevent database connection timeouts. If the Synchronization Manager server component reaches the timeout, then it exits with an error message. To configure the Siebel Server to prevent a database connection timeout, you can set the value of the Database Connection Timeout parameter to a value that is smaller than the timeout period for your database software. If the idle time reaches the value that you assign to this parameter, then the Siebel Server creates activity on the Siebel database connection to prevent a timeout. To set this parameter, you can use the Server Manager command line or the administrative screens. If you use the administration screens, then you must click the Advanced button in the header of the Component Parameters list. For more information, see Making Advanced Server Parameters Visible. |
Domain Name |
NTDomain |
Optional |
If your implementation uses AppServer authentication, then the Domain Name parameter specifies the Windows domain name for the user name and password. To use password authentication with Windows, you must provide the Windows user with rights to the Siebel Server. |
Communication Type |
CommType |
Optional |
Specifies whether you are encrypting synchronization with remote clients using TLS. You can use one of the following values:
For more information, see Configuring TLS Encryption for Siebel Remote. |
Encryption Type |
Crypt |
Optional |
Specifies whether you are encrypting synchronization using RSA. You can use one of the following values:
Note: Encryption Type (Crypt) no longer applies to Siebel Remote synchronization with remote clients.
|
Maximum Number of Cached Thread Contexts |
MaxCtxCache |
Optional |
Maximum number of cached thread contexts that a multithreaded server maintains. The default value is 10 cached contexts. |
Maximum Task Number |
MaxTasks |
Optional |
Maximum number of synchronizations that the Synchronization Manager server component can service simultaneously. The default value is 100. |
Minimum Number of Cached Thread Contexts |
MinCtxCache |
Optional |
Minimum number of cached thread contexts that a multithreaded server maintains. The default value is 2 cached contexts. |
Siebel File System |
FileSystem |
Optional |
Siebel File System location for the Siebel Enterprise. For more information, see About the Siebel Enterprise and the Siebel Enterprise Server. |
Static Port Number |
PortNumber |
Optional |
The TCP/IP port number that is dedicated to the Synchronization Manager server component. The default value is 40400. For more information, see Formatting the DockConnString Parameter. |
Parameters of the Transaction Processor Server Component
The following table describes the parameters of the Transaction Processor server component.
Table Parameters of the Transaction Processor Server Component
| Name | Alias | Required | Description |
|---|---|---|---|
Clean DX Files Iterations |
CleanFilesIter |
Optional |
Specifies how frequently the Transaction Processor server component deletes DX files from the |
Clean Transaction Iterations |
CleanTxnsIter |
Optional |
Specifies how frequently the Transaction Processor server component deletes transactions from the master transaction log table of the Siebel database. You specify this parameter as the number of iterations. The default value is 10. |
Maximum Reads per Iteration |
MaxRead |
Optional |
Specifies the maximum number of operations to read for each iteration. The default value is 0, which configures the Transaction Processor server component to read outstanding operations in the Master Transaction Log. |
Sleep Time |
SleepTime |
Optional |
Specifies the time, in seconds, to sleep between iterations. When the Transaction Processor server component wakes up, it processes transactions. The default value is 60. |
TS Block Size |
TSBlockSize |
Optional |
Specifies the block size for the dobjinst.dbf visibility database, in bytes. The Transaction Processor server component stores data in blocks. This block size is different from the block size that the operating system uses. The default value is 4096 bytes. For help with modifying this parameter, see Getting Help from Oracle. |
TS Cache Size |
TSCacheSize |
Optional |
Specifies the cache size for the dobjinst.dbf visibility database, in kilobytes. The default value is 4096 kilobytes. For help with modifying this parameter, see Getting Help from Oracle. |
Write Compressed DX Files |
WriteCompressed |
Optional |
Specifies to write DX files in compressed format. The default value is FALSE. Leave this parameter at the default value. For help with modifying this parameter, see Getting Help from Oracle. |
Parameters of the Transaction Router Server Component
The following table describes some of the parameters of the Transaction Router server component.
Table Some of the Parameters of the Transaction Router Server Component
| Name | Alias | Required | Description |
|---|---|---|---|
Id Db Recreate |
IdDbRecreate |
Optional |
A cache that stores the data that Siebel Remote requires to examine visibility. It recreates visdata.dbf, which is the visibility ID database. The default value is FALSE, which configures Siebel Remote to not recreate the Siebel database every time the Transaction Router starts. For more information, see Making Advanced Server Parameters Visible. |
Id Db Size |
IdDbSize |
Optional |
The size of the visdata.dbf file, which is the visibility ID database, and the amount of memory that Siebel Remote allocates on the Siebel Server for all instances of the Transaction Router. You use this parameter only if the visdata.dbf file is present, or if the Id Db Recreate parameter is set to True. The default value is 50MB, which is optimal in most situations. To improve Transaction Router performance in a large deployment, you can increase this value. The recommended maximum value is 200 MB. |
Maximum reads per iteration |
MaxRead |
Optional |
The maximum number of operations that the Transaction Router processes for a user during each run. The default value is 10000. |
Maximum seconds per iteration |
MaxSecs |
Optional |
The longest duration that a Transaction Router instance works for one user during each run. The default value is 300 seconds. |
Maximum writes per file |
MaxWrite |
Optional |
The maximum number of operations the Transaction Router server component writes for each DX file. The default value is 5000. |
Node Division Factor |
NodeDivFactor |
Optional |
The maximum number of users a Transaction Router instance processes during each run. The Transaction Router processes the fractional number of users that Siebel Remote computes using this parameter as a factor. For example, if the value of this parameter is 5, and if there are 100 users on the Siebel Server, then the Transaction Router processes 100 divided by 5, or 20 users. The default value is 5. |
Operation Routing Rate Threshold |
RouteRateThreshold |
Optional |
The minimum rate of database transactions that the Transaction Router routes for each second. If the Transaction Router server component performs below this minimum, then Siebel Remote creates an alert. |
Read client list iterations |
ReadClientsIter |
Optional |
The number of iterations that occur before the Transaction Router refreshes the list of users to process from the Siebel database. The default value is 10 iterations. |
Set Application Server Name |
SetAppName |
Optional |
Upgrades remote clients from previous versions of Siebel CRM to version 4.0 and later. The default value is TRUE. At start-up, the Transaction Router server component searches the Siebel database for remote clients whose Siebel Server value is not set, and that have a docking folder on the local server. This parameter sets the Siebel Server name in the Siebel database for each of these clients. |
Sleep Time |
SleepTime |
Optional |
Time to sleep, in seconds, between iterations. The default value is 60. |
TS Cache Size |
TSCacheSize |
Optional |
Cache size for the dobjinst.dbf file in kilobytes. The default value is 2048 kilobytes. It is recommended that the maximum value not exceed the number of users on the Siebel Server multiplied by the size of the largest dobjinst.dbf file. |
Write compressed dx files |
WriteCompressed |
Optional |
Write DX files in compressed format. The default value is TRUE. |
Parameters of the Transaction Merger Server Component
The following table describes some of the parameters of the Transaction Merger server component.
Table Some of the Parameters of the Transaction Merger Server Component
| Name | Alias | Required | Description |
|---|---|---|---|
Error Mode |
ErrorMode |
Optional |
Determines how Siebel Remote handles a database error that occurs during a Transaction Merger process. The default value is STOP. You can use one of the following values:
|
Sleep Time |
SleepTime |
Optional |
Time to sleep, in seconds, between iterations. The default value is 60. |
Parameters of the Generate New Database Server Component
The following table describes some of the parameters of the Generate New Database server component.
Table Some of the Parameters of the Generate New Database Server Component
| Name | Alias | Required | Description |
|---|---|---|---|
Interface Tables |
IFaceTbls |
Optional |
Create interface tables and indexes. The default value is FALSE. |
Use DDL File |
UseDdlFile |
Optional |
Use when you create a new template file. The default value is FALSE, which configures Siebel Remote to read the schema directly from the Siebel database. Set Use DDL File to FALSE only if you run the Generate New Database component after you modify the schema. Generate New Database then reads the latest schema from the Siebel database instead of from the DDL file. |
Warehouse Tables |
WarehouseTbls |
Optional |
Use to create Warehouse tables and indexes. The default value is FALSE. |
Parameters of the Database Extract Server Component
The following table describes some of the parameters of the Database Extract server component.
Table Some of the Parameters of the Database Extract Server Component
| Parameter Name | Alias | Required | Description |
|---|---|---|---|
CD directory |
CDDir |
Optional |
Name of a folder where Siebel Remote copies the snapshot files that the initialization uses. |
Client Name |
Client |
Required |
Name of the remote client for which Siebel Remote is extracting a database. This value corresponds to the Mobile Client Name field in the Mobile Clients view. For more information, see Specifying Client Names. |
Database Init Method |
InitMethod |
Optional |
Method for creating the Siebel Remote database. The default value is Oracle XE. |
Number of Data Import Threads |
DatImpThrdNum |
Optional |
Set this parameter to run DbXtract as a multithreaded component with the specified number of threads. The default value is 3. |
Extract all Repository Tables |
ExtractRepos |
Optional |
Configures Siebel Remote to include repository tables in a database extract. Values are TRUE and FALSE. If the Extract all Repository Tables parameter is set to TRUE, then the Get is not necessary. Not using the Get can reduce the amount of time that you require to configure an environment for a developer. |
Last Extract Date |
ExtractSince |
Optional |
Specifies a date-time value for extraction. You must use the following format: YYYY-MM-DD HH:MM:SS If specified, then the Database Extract server component extracts a remote client only if Siebel Remote has not extracted this client since the date-time value that you specify in the Last Extract Date parameter. |
Last Sync Date |
SyncSince |
Optional |
Specifies a date-time value for synchronization. You must use the following format: YYYY-MM-DD HH:MM:SS If specified, then the Database Extract server component synchronizes a remote client only if Siebel Remote has not extracted this client since the date-time value that you specify in the Last Extract Date parameter. |
Maximum data file size |
DatFileSize |
Optional |
Sets the maximum size of a data file in megabytes:
|
Message Language Code |
Language |
Optional |
Extract messages for this language. The default value is ENU. |
Mobile Client Version |
ClientVersion |
Optional |
Specifies the remote client software version, which determines whether parallel extraction is supported. This parameter is important during an upgrade. The default value is 2000. |
Move Siebel Remote Client |
Move |
Optional |
For more information, see Using the Move Siebel Remote Client Parameter. |
Nodes Per Group |
NodesPerGroup |
Optional |
if the Optimal Mode parameter is TRUE, then the Nodes Per Group parameter specifies the number of users who Siebel Remote extracts together as a group. The default value is 35. |
Optimal Mode |
OptMode |
Optional |
Specifies to use the optimal mode to extract a group of users. The default value is FALSE. |
Save Client Transactions |
SaveTxns |
Optional |
Save pending client transactions during database initialization. The default value is TRUE. This feature does not work during an upgrade. The Save Client Transactions parameter is valid only for the remote client. |
Truncate TS Table |
TruncateTSTable |
Specifies to truncate the S_DOCK_INITM_n table instead of deleting it after the Siebel database extract task completes. Used in the cleanup phase. The default value is FALSE. If you run the Database Extract server component with the Truncate TS Table parameter set to TRUE, then the user ID that you use to run the server component must possess administrator privileges on the Siebel Server. |
|
TS Block Size |
TSBlockSize |
Optional |
Block size for the dobjinst.dbf file in bytes. The default value is 0. Siebel Remote automatically calculates the block size depending on the total number of rows that are visible in the remote client. |
TS Cache Size |
TSCacheSize |
Optional |
Cache size for the dobjinst.dbf file in kilobytes. The default value is 2048 kilobytes. |
TS Table Number |
TSTableNum |
Number of database tables in the dobjinst.dbf file that are available for Database Extract. The range is 1 through 48. The default value is 1. This parameter is the end number of the S_DOCK_INITIM_n table, where n is the TS Table Number. |
Specifying Client Names
To specify a list of client names, you add a list of these names to the Client Name parameter and use a comma to separate each name. To specify the name of a file that contains a list of client names, you can use the at sign (@) as the first character in the value that you specify for the Client Name parameter followed by the file name. To separate each client name in this file, you must use one of the following delimiters:
New line
Comma
Space
Tab
Period
Semicolon
To specify a wildcard, you can use one of the following formats:
To match a single character, use a question mark (?).
To match zero or more characters, use an asterisk (*).
Using the Move Siebel Remote Client Parameter
If the remote client is currently registered on a Siebel Server that is not the current server, and if you set the Move Siebel Remote Client parameter to TRUE, then the following occurs:
The Database Extract server component sets the Siebel Server name of the remote client to the local Siebel Server.
The following server components on the old server stop servicing this remote client in the next iteration:
Transaction Router
Transaction Merger
Database Extract
You can also use the Move Siebel Remote Client parameter to move a regional node in the same way you that you use this parameter to move a remote client.
The default value is FALSE.
If you attempt to extract a remote client that Siebel Remote already extracted for a different server, then the Database Extract server component returns an error.
Parameters of the Replication Agent Server Component
The following table describes the parameters of the Replication Agent server component.
Table Parameters of the Replication Agent Server Component
| Parameter | Alias | Required | Description |
|---|---|---|---|
HQ Application Server Comm param |
CommParam |
Optional |
The colon-separated list of communications parameters that the regional server uses to connect to the parent Siebel Server. |
HQ Application Server Name |
HQ |
Required |
The Dock Connect String of the parent Siebel Server. For more information, see Setting the HQ Application Server Name Parameter. |
Iterations |
Iterations |
Optional |
Specifies the number of times that the Replication Agent server component connects to the parent node. You typically set this parameter to zero (0) to configure the Replication Agent to loop forever or until the server administrator stops it. If you set the Iterations parameter to 1 and then start Replication Agent, then a single synchronization occurs. The default value is 0. |
Maximum txns per commit |
MaxCommitTxns |
Optional |
Specifies the number of transactions that Siebel Remote applies before it commits these transactions to the Siebel database. The default value is 100. |
Maximum writes per file |
MaxWrite |
Optional |
Limits the size of a DX file. Breaks the DX files that Siebel Remote sends to the parent Siebel Server into smaller, more manageable files. Replication Manager closes the existing DX file and then starts writing to a new DX file when the current DX file reaches the maximum number of operations that you specify in the Maximum writes per file parameter. The default value is 10000. |
Receive files |
RecvFiles |
Optional |
You can use one of the following values:
The default value is TRUE. |
Receive txns |
RecvTxns |
Optional |
You can use one of the following values:
The default value is TRUE. |
Send txns |
SendTxns |
Optional |
You can use one of the following values:
The default value is TRUE. |
Sleep time |
SleepTime |
Optional |
The time period, in seconds, that configures Replication Agent to sleep between synchronizations. The default value is 60. |
Field Descriptions for Administration Screens
This topic describes fields that you can use in the administration screens that you use with Siebel Remote. It includes the following information:
Fields in the Siebel Remote Client Status Form
The following table describes fields of the Siebel Remote Client Status form.
Table Fields of the Siebel Remote Client Status Form
| Column | Field | Description |
|---|---|---|
Extracted on Server |
Last Sessions |
Time when Siebel Remote extracted this client. |
Seconds |
Amount of time required to extract the remote client. |
|
File name |
First file name for the extracted records. |
|
Rows extracted |
Row count of extracted records. |
|
Snapshot (Kbytes) |
Total size in kilobytes for extracted records. |
|
# of Files in File System |
Number of files in file system for this client. |
|
File System (Kbytes) |
Size of files in file system, in kilobytes. |
|
Max Transaction |
Maximum transaction ID when Siebel Remote extracted this client. |
|
Initialized on Client |
Last Session |
Time when Siebel Remote initialized the local database. |
Seconds |
Amount of time required to initialize the local database. |
|
Free Disk (Kbytes) |
Free disk space available on the local computer where you installed the remote client. |
|
Database (Kbytes) |
The size in kilobytes of the local database. |
|
# of Files in File System |
Number of files in the local file system. |
|
File System (Kbytes) |
Total size in kilobytes of files in the local file system. |
|
Product Version |
System information for the computer where the local database resides. |
|
Current status |
Last Session |
Time when Siebel Remote performed the last synchronization. |
Seconds |
Duration of the last synchronization. |
|
Free Disk (Kbytes) |
Free disk space available of the local computer where you installed the remote client. |
|
Database (Kbytes) |
Current size of the local database. |
|
# of Files in File System |
Number of files in the local file system. |
|
File System (Kbytes) |
Current size in kilobytes of files in the local file system. |
|
Total Sessions |
Total number of times this client has synchronized so far. |
|
Product Version |
Current system information for the remote client. |
Fields in the Siebel Remote Client Diagnostics Form
The following table describes fields of the Siebel Remote Client Diagnostics form.
Table Fields of the Siebel Remote Client Diagnostics Form
| Field | Description |
|---|---|
Name |
Node name. |
Type |
INIT, ROUTE, RECEIVE, MERGE, CLEAN, SESSION. |
Local |
Flag to indicate it is for current or local databases. |
Created |
The time that Siebel Remote created the record. |
Last updated |
The time that Siebel Remote last updated the record. |
Last file |
The last file number that Siebel Remote processed for the node. |
Last transaction id |
The last transaction number that Siebel Remote processed for the node. |
Last trxn duration (sec) |
The time required to process transaction in the latest session. |
Total duration (sec) |
Total time required to process transaction for the node. |
Last trxn size (bytes) |
Size of transactions processed for the node during last session. |
Total (bytes) |
Total size of transactions processed for the node. |
Last trxn operations |
Number of operations processed for the node during last session. |
Total operations |
Total number of operations processed for the node. |
Last transactions |
Number of transactions processed for the node during last session. |
Total transactions |
Total number of transactions processed for the node. |
Total attachment (bytes) |
Total size of file attachments processed for the node. |
Total attachments |
Total number of file attachments. |
Last attachment (bytes) |
Size of file attachments for the node during the last session. |
Last attachments |
Number of file attachments for the node during the last session. |
Additional information |
More detailed information about the node. |
Fields in the Synchronization Sessions List
The following table describes fields in the Synchronization Sessions list.
Table Fields in the Synchronization Sessions List
| Field | Description |
|---|---|
Synchronization Starts |
Date and time when Siebel Remote started the synchronization. |
Synchronization Ends |
Date and time when the synchronization ended. If the synchronization did not complete successfully, then this field is empty. |
Transactions |
The number of transactions that Siebel Remote synchronized to the user during the session. |
Transaction Size (MB) |
The total size in MB of the transactions that Siebel Remote synchronized to the user during the session. |
Client Merge Duration (Min) |
The amount of time in minutes required to merge transactions on client. |
Fields in the Siebel Remote Upload Statistics Form
The following table describes fields in the Siebel Remote Upload Statistics form.
Table Fields in the Siebel Remote Upload Statistics Form
| Field | Description |
|---|---|
Last Session |
Duration of the last synchronization. |
Last File |
Last transaction file that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server. |
Last Transaction |
Last transaction that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server. |
Transaction Count - Last |
Number of transactions that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server during the last synchronization. |
Transaction Count - Total |
Total transactions that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server since the last database extract. |
Operation Count - Last |
Number of operations that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server during the last synchronization. |
Operation Count - Total |
Total number of operations that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server since the last database extract. |
KBytes - Last |
Size of transactions that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server during the last synchronization, in kilobytes. |
KBytes - Total |
Size of transactions that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server since the last database extract, in kilobytes. |
Duration (Seconds) - Last |
Duration of last synchronization that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server, in seconds. |
Duration (Seconds) - Total |
Total duration of all synchronizations since the last database extract, in seconds. |
Attachment Files - Last |
Number of file attachments that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server during the last synchronization. |
Attachment Files - Total |
Number of file attachments that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server since the last database extract. |
Attachment Size (KBytes) - Last |
Size of file attachments that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server during the last synchronization, in kilobytes. |
Attachment Size (KBytes) - Total |
Size of files that Siebel Remote created on the remote client, received on the Siebel Server, or applied on the Siebel Server since the last database extract, in kilobytes. |
Fields in the Siebel Remote Download Statistics Form
The following table describes fields in the Siebel Remote Download Statistics form.
Table Fields in the Siebel Remote Download Statistics Form
| Field | Description |
|---|---|
Last Session |
Date and time of last session that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client. |
Last File |
Last transaction file that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client. |
Last Transaction |
Last transaction that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client. |
Transaction Count - Last |
Number of transactions that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client during the last synchronization. |
Transaction Count - Total |
Total transactions that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client since the last database extract. |
Operation Count - Last |
Number of operations that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client during the last synchronization. |
Operation Count - Total |
Total number of operations that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client since the last database extract. |
KBytes - Last |
Size of transactions that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client during the last synchronization, in kilobytes. |
KBytes - Total |
Size of transactions that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client since the last database extract, in kilobytes. |
Duration (Seconds) - Last |
Duration of the last synchronization, in seconds. |
Duration (Seconds) - Total |
Total duration of all synchronizations since the last database extract of the node, in seconds. |
Attachment File Count - Last |
Number of file attachments that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client during the last synchronization. |
Attachment File Count - Total |
Number of file attachments that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client since the last database extract of this node. |
Attachment Size (KBytes) - Last |
Size of the file attachments that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client during the last synchronization. |
Attachment Size (KBytes) - Total |
Size of all file attachments that Siebel Remote created on the Siebel Server, received on the remote client, or applied on the remote client since the last database extract of this node. |
Operation Types for the Operation Field of the Transaction Log List
The following table describes operation types for the Operation Field of the Transaction Log list.
Table Operation Types for the Operation Field of the Transaction Log List
| Operation Type | Description |
|---|---|
A |
Execute a Data Definition Language (DDL) statement for a database schema update. |
B |
Delete a dock object instance. A data merge deletes all member table rows only for a server to client operation. |
C |
Delete a record as a result of deleting a dock object instance for a server to client operation only. |
D |
Delete a single row. |
E |
Delete multiple rows. |
F |
Delete cascading rows. |
G |
Merge multiple rows. |
H |
Insert a record as a result of downloading a dock object instance only for a server to client operation. |
I |
Insert a single row. |
J |
Contain transactions in an external file. |
K |
Execute a marker transaction to indicate the start of a client-side transaction. |
L |
Update the record of a child table that might cause conflict. |
M |
Execute a marker transaction to stop processing a user, and then continue. |
N |
Remove any orphan child records that exist in the Siebel database that resulted from a remote client-side merge or cascade delete transaction that was performed on the client database using the W operation. |
O |
Update conflict ID. |
P |
Execute a simple Data Manipulation Language (DML) statement that uses pass through. |
Q |
Delete records of a child table that match the foreign key value. This operation is a compensation operation that Siebel Remote performs as the result of a client-side merge or cascade delete transaction that the W operation performed on the client database. This compensation operation cleans up any orphan child records that exist in the Siebel Server as a result of such a transaction in the remote client. |
R |
Update the foreign key column of child table records. |
S |
Shadow operation. |
T |
Delete records of a child table that might cause conflict. |
U |
Update a single row. |
V |
Update multiple rows. |
W |
Compacted operation of a cascade or client-side merge transaction. |
X |
Insert set-based rows. |
Y |
Update set-based rows. |
Z |
Delete set-based rows. |
Predefined Administrative Reports
The following table describes the predefined administrative status reports. The View column describes the view you can use to start the report. For more information, see About Siebel Replication Manager.
Table Predefined Administrative Status Reports for Siebel Remote and Replication Manager
| Name of Report | View | Description |
|---|---|---|
Active Mobile Users Usage Graph |
Synchronization Sessions |
Displays information for server nodes that contain users. This report takes the start date as a parameter from the user and then creates the following details for each day that occurs between the start date and the current date, in the form of a graph:
|
Active Mobile Users Usage Table |
Synchronization Sessions |
Displays information for server nodes that contain users. This report takes the start date as a parameter from the user and then creates the following details for each day that occurs between the start date and the current date in the form of a table:
|
Mobile User Summary Report |
Client Status |
This report displays the following information for server nodes that contain users:
This report also indicates if the user is active. If the user is not active, then displays the last accessed date and the name of the Routing Model that is associated with the user. |
Regional Node Status Report |
Client Status |
Displays information for server nodes that contain subordinate regional nodes, including the following information about the regional node:
The report also indicates if the regional node is currently active or end dated and the routing group of the regional node. |
Synchronization Frequency Report |
Synchronization Sessions |
Displays how frequently Siebel Remote synchronizes each user for a period of time. Each line of the report includes the following information:
|
Synchronization Session Report |
Synchronization Sessions |
Displays information about synchronizations for every user for a period of time. The report provides user information and details of these synchronizations. |
Transaction Backlog Status Report |
Transaction Log |
Displays information about transactions that are pending in the queue from active users and regional nodes. It starts with the most recent transaction that Siebel Remote created on the headquarters node at the time you run the report. Fields in this report include the name of the remote client and the number of pending transactions. For more information about headquarters nodes, see Overview of Siebel Replication Manager. |
Transaction Processor Status Report |
Processor Status |
Displays the status of active and inactive Transaction Processor entries that exist in the current Siebel Server. This report includes the following information:
|
Transaction Router Backlog Report |
Transaction Log |
Displays the following information:
Latency is the time difference between the time when Siebel Remote routed the last transaction to the user or regional node and the time when you run the report. |
Siebel Server Features on a Regional Node
Although most Siebel Server processes run only on the Siebel Server of the headquarters node, you can use some features and server components on regional nodes.
The following table lists the features and server components that you can use on regional nodes.
Table Server Features and Server Components You Can Use on a Regional Node
| Item | Type | Member of | Notes |
|---|---|---|---|
Advanced Search |
feature |
Not applicable. |
Not applicable. |
Basic Siebel Call Center functionality |
feature |
Not applicable. |
Associated with the Call Center Object Manager server component. Includes the following items:
|
Basic Siebel Sales functionality |
feature |
Not applicable. |
Associated with Sales Object Manager server component. Includes the same items as the Basic Siebel Call Center functionality. |
Call Center Object Manager |
server component |
Siebel Call Center component group |
Not applicable. |
Communications Configuration Manager |
server component |
Communications Management component group |
Used by the Computer Telephony Integration (CTI) feature. |
Communications Outbound Manager |
server component |
Communications Management component group |
Not applicable. |
Communications Session Manager |
server component |
Communications Management component group |
Used by the Computer Telephony Integration (CTI) feature. |
CTI (Computer Telephony Integration) |
feature |
Not applicable. |
Associated with Communications Configuration Manager and Communications Session Manager server components. Siebel Remote does not support live call transfer from a user on one regional node to a user on another regional node. |
Database Extract |
server component |
Disconnected Mobile Synchronization component group |
Siebel Remote uses some of the components in this component group (alias MobileSync). |
Document Server |
server component |
Siebel eDocuments component group |
For the Correspondence, Proposals, and Presentations features. |
EAI Object Manager |
server component |
Enterprise Application Integration (EAI) component group |
Not applicable. |
Field Service Object Manager |
server component |
Field Service component group |
Not applicable. |
Generate New Database |
server component |
Siebel Remote component group |
Not applicable. |
MQSeries Server Receiver |
server component |
Enterprise Application Integration (EAI) component group |
Not applicable. |
MSMQ Receiver |
server component |
Enterprise Application Integration (EAI) component group |
Not applicable. |
Outbound Communications |
feature |
Not applicable. |
Associated with the Communications Outbound Manager server component. |
Parallel Database Extract |
server component |
Disconnected Mobile Synchronization component group |
Not applicable. |
Replication Agent |
server component |
Siebel Remote component group |
Not applicable. |
Report Server |
feature |
Not applicable. |
Can be used to create reports on the regional node. |
Runtime Events |
feature |
Not applicable. |
Siebel Remote does not support runtime events that contain wait states on a regional node. |
Sales Object Manager |
server component |
Siebel Sales |
Not applicable. |
Self Service Object Manager |
server component |
Siebel Call Center component group |
Not applicable. |
State Model |
feature |
Not applicable. |
Not applicable. |
Synchronization Manager |
server component |
Siebel Remote component group |
Not applicable. |
Transaction Merger |
server component |
Siebel Remote component group |
Not applicable. |
Transaction Processor |
server component |
Disconnected Mobile Synchronization component group |
Not applicable. |
Transaction Router |
server component |
Disconnected Mobile Synchronization component group |
Not applicable. |
Workflow Process Batch Manager |
server component |
Workflow Management component group |
Not applicable. |
Workflow Process Manager |
server component |
Workflow Management component group |
Not applicable. |
Workflow Processes |
feature |
Not applicable. |
Associated with the Workflow Process Batch Manager and the Workflow Process Manager server components. Siebel Remote does not support the following kinds of workflow processes on a regional node:
Oracle’s Siebel Remote does not support a workflow policy or a persistent workflow in a replicated environment. |
Parameters of the Regional Database Initialization Program
The following table lists some of the parameters and corresponding flags that are available for the Srvrinit utility.
Table Parameters and Command Line Flag for the Srvrinit Utility
| Parameter | Flag | Description | Required |
|---|---|---|---|
16K Table Space |
ks |
For IBM DB2 installations only, provide the name of the 16K Table space. For more information, see the Siebel Installation Guide for the operating system you are using. |
No |
32K Table Space |
ls |
For IBM DB2 installations only, provide the name of the 32K Table space. For more information, see the Siebel Installation Guide for the operating system you are using. |
No |
File System |
filesystem |
File system folder on the regional node. The file system parameter must reference the parent folder of the |
Yes |
Help |
? help |
Help for usage. |
No |
Index Space |
is |
For Oracle Database and IBM DB2 installations only. Space on the regional database where indexes are created. |
No |
Initialize on new database |
init |
Specifies if the regional database is empty or not:
The default value is N. An old transaction might be invalid for the new schema and can cause failure. You must set this parameter to Y during a major upgrade. |
No |
(Not applicable.) |
comm |
Communication parameters for low-bandwidth connections. |
No |
(Not applicable.) |
l |
Language code. The default value is enu. |
No |
(Not applicable.) |
v |
Verbose mode, that you can set to Y or N. The default value is N. |
No |
ODBC Data Source |
d |
Name of ODBC data source to connect to the regional node. |
Yes |
Parent AppServer Name |
dockconnstring |
Name of the Siebel Server at the parent node where Siebel Remote does the Siebel database extract. |
Yes |
Regional Server Name |
n |
Name of the regional node. |
Yes |
Repository Name |
reposname |
Name of the repository, which is typically Siebel Repository. |
Yes |
Run in Parallel/Number of Threads |
para |
Specifies to run srvrinit in parallel. Specifies the number of threads to run. |
No |
Schema Qualifier |
sq |
For IBM DB2 for z/OS only, the name that the Srvrinit utility uses to qualify database objects it creates that the Siebel application requires. |
Yes |
Server Root Directory |
homedir |
Root folder of the Siebel Server on the Regional node. In this document, |
Yes |
Table Grouping File |
tg |
For IBM DB2 for z/OS only. Full path to the storage control file, which is a file that contains declarations for database objects. |
Yes |
Table Owner Password/Privileged User Password |
tp |
Password of the table owner on the regional database. For IBM DB2 for z/OS, this password is the same as the Privileged User Password, which is the password for Privileged User ID. |
Yes |
Table Owner/Privileged User ID |
t |
Logon of the Table Owner on the regional database. It must include privileges to create database objects. For IBM DB2 for z/OS, this logon is the same as the Privileged User ID. This account is a user account that includes the necessary database authority and privileges to create, access, and modify Siebel database objects and native database objects and the operations that are required to implement the Siebel application. These environments include rigid controls on user identification. An account must correspond to a real person. |
Yes |
Table Space |
ts |
For IBM DB2 and Oracle Database installations only. Space on the regional database where tables are created. |
No |
User Name |
u |
User name to authenticate the regional database with the Siebel Server of the headquarters node. You can use a database user who is associated with the regional database during the setup, but this user must possess administrator privileges to create logins in the master database, such as SADMIN. For more information about headquarters nodes, see Overview of Siebel Replication Manager. |
Yes |
User Password |
p |
Password to authenticate the regional database with the Siebel Server of the headquarters node. If you configure the users on the regional database, then Replication Manager uses the password that you specify. |
Yes |