Table 2. Documentation Changes in Siebel Remote and Replication Manager Administration Guide, Version 8.1, Rev A
|
|
Siebel Remote Support for Tablet Personal Computers |
New topic. Siebel Remote for the tablet personal computer supports the full Siebel functionality. |
How Siebel Remote Manages the Size of the Local Database |
Modified topic. It is recommended that the local database be no larger than 700 MB. |
Synchronization Validation |
Modified topic. Data that is used with Data Validation Manager is not intended to be routed. |
Support for Oracle Real Application Clusters with Siebel Remote |
Modified topic. Usage of Active or Active Oracle Real Application Clusters (Oracle RAC) is not supported with Siebel Remote. |
Process of Configuring the Siebel Server |
New topic. Guides you through the configuration process. |
"Using the Show Advanced Objects Parameter to Make Advanced Parameters Visible" on page 66 |
New topic. You can make an advanced object visible. |
Setting the Password of the Local Database Administrator by Default |
New topic. If you do not specify a value for the New DBA password parameter, then Generate New Database sets the password according to certain rules. |
Options for Configuring the Siebel Server |
Modified topic. You can set the number of transactions that are routed for each second. Only one Transaction Processor can run for each database installation within an enterprise that includes more than one Siebel Server. |
Setting the Threshold at which Siebel Remote Routes Transactions |
Modified topic. You can set the number of transactions that are routed for each second. |
Modifying the Configuration File |
Modified topic. Includes new steps when using Quick Start, and options to locate the SRF file. |
Verifying Database Connectivity on UNIX or DB2 |
Modified topic. You can use odbcsql to verify database connectivity to SQL Anywhere on the UNIX or DB2 operating system. |
"Logging in to the Local Database" on page 97 |
Modified topic. You can use the Adaptive Server Anywhere utility to log in to the local database. |
Process of Configuring Encryption and Authentication for the Remote Client |
Modified topic. Siebel Business Applications use MSCRYPTO or RSA to encrypt the username and password that is used for synchronization and initialization. |
Format of the Remote Client Name, Database Name, Login ID, and Windows Password |
Modified topic. The client name, password, and login ID must adhere to a specific format. Modified topic. The client name, password, and login ID must adhere to a specific format. |
Avoiding a Transaction Processor Failure That Is Due to a File System That Has Moved |
Modified topic. The Transaction Processor might fail if the file system is moved. |
Modifying a Routing Model |
Modified topic. If you use the docking wizard, then you must index database columns. |
Limiting Access to the Global Accounts View |
New topic. You can limit access to the My Global Accounts view for the Remote client. |
Opening Multiple Remote Client Sessions |
New topic. You cannot open multiple sessions with Siebel QuickStart. |
Updating a Change to a Responsibility |
New topic. It is not necessary to reextract the server database when a responsibility is changed. |
Extracting the Server Database |
Modified topic. Includes new steps to extract a database that is not encrypted, and to specify a password for the DBA. |
How Siebel CRM Manages Changes in the S_DOCK_SESSION Table |
New topic. It is not necessary to resynchronize the Remote client in order to clean up the S_DOCK_SESSION table. |
Using a Transaction Log to Optimize Performance |
New topic. You can use a transaction log to allow SQL Anywhere to write notes that detail changes as they occur. |
Extracting a Database to a CD-ROM or Other Portable Media |
New topic. You must delete certain files in the docking directory. |
Extracting a Database for Use with Siebel Tools |
New topic. A single database must be used for Siebel Tools and the Remote client, and a Siebel developer must use the Standard Routing Model. |
Options for Initializing the Local Database |
New topic. There are new topics for options available when initializing the local database. |
Initializing the Local Database as a Nonadministrative User When Using Vista |
Modified topic. A Remote user can initialize the local database when the Remote client operates on Microsoft Vista. |
Deactivating a Large Number of Remote Clients |
New topic. Stop the Transaction Processor and Transaction Router before you deactivate a large number of Remote clients. |
Cleaning the Cache of the Dispatch Board |
New topic. Do not alter the S_DSP_BRD_LOG table or directly modify how it is used. |
Configuring Traces for a Server Component |
Modified topic. Certain server components can be used with tracing. References to sources that provide additional information about tracing are also provided. |
Viewing Reports on the Remote Client |
Modified topic. The Product Version field describes the Siebel Anywhere Upgrade kit that the Remote user applied. If UTC is allowed, then some fields in the User Preferences screen use the GMT (Greenwich Mean Time) time zone to display time. |
Using the Client Status View with Siebel Anywhere |
Modified topic. The Product Version field is not updated with the version information until after the upgrade finishes. |
Displaying Local Time in the User Preferences Screen |
Modified topic. If UTC is allowed, then some fields in the User Preferences screen use GMT. |
Installing Servers and File Systems on the Regional Node |
Modified topic. Requirements for installing the Siebel Server on the regional node and for network connectivity have changed. |
Installing the Server Database Configuration Utilities on the Regional Node |
Modified topic. The Siebel Database Server is renamed to Database Configuration Utilities. |
Adjusting the Shared Pool Size for Parallel Database Extract |
New topic. You can adjust a parameter to meet the cache requirements for a parallel database extract. |
Configuring the Replication Agent Server Component |
Modified topic. Some steps have changed for starting the Replication Agent, and for automatically starting Replication Agent when the Siebel Server starts. |
Adding a User to a Regional Node |
New topic. If a Remote user is assigned to the Siebel Administrator position, then a large download might occur. |
Upgrading a Regional Node |
Modified topic. Replication Manager and the Remote client must contain the same database schema and SRF file. You must index the table columns that are changed during an upgrade. |
Generating Reporting Relationships |
Modified topic. It might be necessary to perform the Generate Reporting Relationships process if you upgrade. |
Backing Up and Recovering the Siebel Enterprise Server |
New topic. There are certain precautions you must take when backing up the entire server database or user schema. |
Troubleshooting a Client-Side Merge Problem |
Deleted topic. CSM Logging is no longer used. |
Using the Work Offline Feature of Internet Explorer |
Modified topic. Be sure to inform Remote users to not use the Work Offline feature. |
Using the Txnskip Utility to Examine Skipped Transactions |
Modified topic. You can identify skipped transactions and use the txnskip utility to identify Remote users who require reextraction. |
Running the Visutl Utility on a Cluster |
New topic. You can run the visutl utility on a cluster. |
Differences in the Literature List When Connected to the Local Database |
New topic. There are differences in the literature list when connected to the local database. |
Server Component Parameters |
Modified topic. Parameters for server components are consolidated into a single topic. |
Parameters of the Transaction Router Server Component |
For a large deployment, Id Db Size can be increased to improve performance of the Transaction Router. |
Parameters of the Database Extract Server Component |
Modified topic. You can reduce the amount of time that is required to configure an environment for a developer. |
Operation Types for the Operation Field of the Transaction Log List |
Modified topic. The N and Q operations can be used to clean up orphaned records. |
"Standard Routing Model" on page 386 |
New topic. Describes dock objects not included with the standard routing model. |
Parameters of the Regional Database Initialization Program |
Modified topic. The File System parameter must point to the att file system directory. |
