5Configuring the Remote Client
Configuring the Remote Client
This chapter describes the work you must do to configure the remote client. It includes the following topics:
Process of Configuring the Remote Client
This process is a step in Roadmap for Implementing Siebel Remote.
You do the following work to configure the remote client:
Configuring the Siebel Remote Hardware, Software, and Network
This task is a step in Process of Configuring the Remote Client.
This topic describes how to install the hardware and software, and then establish network connectivity.
To configure the hardware, software, and network for Siebel Remote
Install and configure the hardware and software for a Siebel application.
This step might include configuring users. Do not modify the ODBC code page settings from multiple byte to single byte. For more information, see the Siebel Installation Guide for the operating system you are using.
Establish network connectivity.
Install the hardware and software on the remote client that this client requires to exchange files with the Siebel Server. This step might include choosing communication settings and installing networking cards or software. For more information, see the Siebel Installation Guide for the operating system you are using and see the Certifications tab on My Oracle Support.
Modifying the Siebel Configuration File for Siebel Remote
This task is a step in Process of Configuring the Remote Client.
The remote client reads configuration parameters in the Siebel configuration file to determine the location of the Siebel Server folders, the Siebel File Server folders, and the server database installation. The siebel.cfg file for Siebel Sales is an example of a configuration file.
You must set the values for the configuration parameters before you configure Siebel Remote. If you install a Siebel application, then the Siebel installation program creates a siebel.cfg file in the bin folder on the remote client. This file includes default values for each configuration parameter.
Siebel Remote reads the configuration parameters from the configuration file that the Windows shortcut specifies for the remote client or for the synchronizer, depending on whether the user starts synchronization while using the remote client or uses the stand-alone synchronizer. The Installer sets up the shortcut to use siebel.cfg as the configuration file, by default. You can modify this setting.
Siebel Remote reads the configuration information from the configuration file when it does a synchronization. For example, if you use Siebel Call Center, then it reads configuration information from the uagent.cfg file. The user can choose the File menu, Database, and then the Synchronize menu item to start a synchronization.
To modify the Siebel configuration file for Siebel Remote
Locate, and then open the configuration file in a text editor.
For more information, see Locating the Siebel Application Configuration File.
Locate the [Siebel] section, and then do the following:
Set the ClientRootDir parameter.
The ClientRootDir parameter is the name of the installation folder that resides on the remote client.
Set the DockRepositoryName parameter.
The DockRepositoryName parameter is the name of the Siebel runtime repository that you are currently using, such as Siebel Repository. This parameter must contain the same value as the Siebel runtime repository on the Siebel Server.
If the user connects to a VPN and the connection is lost, then Siebel Remote might display the following error message:
Page cannot be displayed.
If you encounter this, and restarting the Mobile Web Client does not reconnect, then set EnableFQDN to False. Setting EnableFQDN to False might affect other functionality, such as the behavior of a pop-up blocker. For more information, see the Siebel Installation Guide for the operating system you are using.
Locate the [LOCAL_XE] section, and then do the following work:
Set the DockConnString parameter.
The DockConnString parameter is the logical network address of the Siebel Server where Siebel Remote connects to synchronize. For more information, see Formatting the DockConnString Parameter and Using VPN When Synchronizing Through the Internet.
Set the TableOwner parameter.
The TableOwner parameter is the name of the account on the local database where the Siebel schema resides. The default value is SIEBEL.
Set the DockTxnsPerCommit parameter.
For more information, see Recommended Configurations for Setting the Number of Transactions That Siebel Remote Applies Before a Commit.
Optional. Modify the configuration file to use a different data source.
If your organization requires data and applications that are stored on separate devices, then you can use a data source that is different from the one that you specify in the [LOCAL_XE] section of the configuration file.
Caution: Make sure you modify the description of the existing local data source in the configuration file. Do not add more local data sources to the configuration file because Siebel Remote does not support these additional local data sources.Save your modifications, and then close the configuration file.
Implement your modifications across the Siebel Enterprise.
You must apply any modification that you make to the Siebel runtime repository to the Siebel Servers that serve the modified application to the Web clients. For more information, see Upgrading a Regional Node.
Recommended Configurations for Setting the Number of Transactions That Siebel Remote Applies Before a Commit
The following table describes recommended configurations for setting the number of transactions that Siebel Remote applies before a commit. The DockTxnsPerCommit parameter sets the number of transactions that Siebel Remote applies to the local database before it does a commit. You must set this configuration parameter to a value that satisfies the requirements at your site. The default value is 500.
Table Recommended Configurations for Setting the Number of Transactions
| Situation | Recommended Configuration |
|---|---|
The user uses the Synchronize Database menu item of the File menu in a Siebel application. |
Set the DockTxnsPerCommit parameter to a high value. A merged transaction does not lock out another user. This configuration improves performance. |
The user uses a stand-alone synchronizer. |
Set the DockTxnsPerCommit parameter to a high value only if the program is the only active user on the server database. For more information, see Using the Stand-Alone Synchronizer. |
The Siebel application applies transactions while the user accesses the server database through this Siebel application. |
Set the DockTxnsPerCommit parameter to a low value to prevent locking out other users while Siebel Remote merges transactions. |
Verifying Database Connectivity on UNIX
You can use odbcsql to verify database connectivity on a UNIX operating system.
To verify database connectivity on UNIX
Set the SIEBEL_UNIXUNICODE_DB environment variable to ORACLE or DB2.
Test the connection using odbsql.
For more information, see Siebel Installation Guide for UNIX.
Formatting the DockConnString Parameter
Siebel Remote uses the DockConnString parameter, located in the [LOCAL_XE] section of the configuration file, to synchronize to the Siebel Server. This parameter contains the name of the computer where you install the Siebel Server software and where you extract the remote client. Make sure you set the DockConnString parameter in the configuration file before you initialize the remote client. You must use the following format when you set the DockConnString parameter:
siebel_server_name::sync_port_number:TLS
where:
siebel_server_name is the logical network address of the Siebel Server that the remote client uses to connect and synchronize.
sync_port_number is the TLS or TCP/IP port number that Siebel Remote dedicates to the Synchronization Manager. If you do not specify any value, then the default value is 40400. For more information, see the following.
TLS (optional). As of Siebel CRM 19.6 Update, Siebel Remote supports TLS for synchronization, where the necessary configuration has been done on the server and the clients. If you do not specify TLS, then no encryption is used. For more information, see Configuring TLS Encryption for Siebel Remote.
The following examples are valid values for the DockConnString parameter:
SIEBAPP1::9000:TLS SIEBAPP1::9000 SIEBAPP1:TLS SIEBAPP1
Setting the Synchronization Manager Port Number
You can modify the default value of the port number that you specify in the DockConnString parameter. You can also specify this port number as a command line option when you start the Siebel Server.
To modify the Synchronization Manager port number
Make sure advanced parameters are visible.
For more information, see Making Advanced Server Parameters Visible.
To use the administrative interface to modify the port number, do the following work:
Locate the record for the Synchronization Manager server component.
For more information, see Locating the Record for a Server Component.
In the bottom applet, click the Parameters tab, click Advanced, and then query the Parameter field for Static Port Number.
Specify a value in the Value on Restart field.
Restart the Siebel Server.
To use the Server Manager command line interface to modify the port, do the following work:
On the Siebel Server, navigate to the following folder:
SIEBEL_ROOT\binOpen the Server Manager command line.
For more information, see Opening the Command Line Interface for Server Manager.
Enter the following command:
srvrmgr> change param portnumber=port_number for comp synchmgrTo display the current port number value, you can enter the following command:
srvrmgr> list advanced param portnumber for comp synchmgr
Update the remote client configuration file so that it matches the setting you specified in this procedure.
For more information, see Modifying the Siebel Configuration File for Siebel Remote.
Using VPN When Synchronizing Through the Internet
It is recommended that every synchronization occur within the corporate firewall. If your deployment must support synchronization to the Internet from outside the firewall, then it is recommended that you use a VPN (Virtual Private Network). If there is a firewall on the network between the remote client and the Siebel Server, or between the VPN Server and the Siebel Server, then the port for synchronizing with the Siebel Server must be opened on the firewall, and this port must be a port other than port 80.
If you do not use a VPN connection, then it is possible that your Internet Service Provider (ISP) or another host on the router could block communication on the port that you specify for synchronizing.
Creating a Remote Client
This task is a step in Process of Configuring the Remote Client.
You do one of the following to create a remote client:
Using an Administrative View to Create a Remote Client
You can use an administrative view to create a remote client.
To use an administrative view to create a remote client
Make sure you already configured the user as a user in the Siebel application.
This user will use the remote client that you create in this topic.
Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Make sure the user possesses access to the required views in the user responsibilities.
For more information, see Views That Siebel Remote Users Require.
Navigate to the Administration - Siebel Remote screen, and then the Mobile Clients view.
In the Parent Server form, query the Server Name field to locate the correct server.
If your deployment does not use Replication Manager, then the correct server is Headquarters (HQ). For more information, see Overview of Siebel Replication Manager.
For more information, see How Siebel Remote Populates the App Server Name Field.
In the Mobile Clients list, click New.
In the Mobile Client field, enter the remote client name.
It is recommended that you use the User ID of the remote client that you specify in Step 8. You cannot use Unicode characters in the login ID. If the user login ID contains Unicode characters, then the initialization will fail.
In the User ID field, click the select icon, and then choose the user ID for the user.
Siebel Remote uses the user ID to access the local database during initialization and synchronization.
In the Routing Model field, click the select icon, and then choose the data routing model that Siebel Remote uses to route data to the user.
For more information, see Controlling the Data That Siebel Remote Routes to Clients.
In the Language(s) field, click the select icon, and then choose the preferred language or languages for the user. If the preferred languages are not available, then click New and follow the instructions that the administrative view displays in the dialog boxes.
For more information, see User Language Preferences.
Complete the remaining fields:
If the authentication method in the Siebel Server Component Parameters is Siebel, then the Synchronization Manager uses the Sync Password field. You can set the password in this field, and then communicate it to the user. To display this field, it might be necessary for you to use Columns Displayed.
If you do not use the Standard routing model, then add the user to the responsibility:
Navigate to the Administration - Application screen, and then the Responsibilities view.
In the Responsibility field, query for the Responsibility that contains the Routing Model suffix.
The Responsibility that contains the Routing Model suffix references the data routing model that you assigned in Step 9. For more information, see Limiting the Views That a Remote Client Displays.
In the Users list, add a new record.
In the Add Users dialog box, choose the user, and then click OK.
Views That Siebel Remote Users Require
The following table describes the views that a Siebel Remote user requires. For more information about configuring employees and providing access to views, see Siebel Applications Administration Guide.
Table Views That a Siebel Remote User Requires
| View | Description |
|---|---|
Mobile User Summary View |
Displays the current state of the remote client. The user can use it to get information about when Siebel Remote extracted and initialized the remote client, and to get information about the last synchronization. To display this view, the user navigates to the User Preferences screen, and then the Mobile User Summary view. |
Dock Session Log |
Displays information about each synchronization, including information about conflicts and other results of each synchronization. To display this view, the user navigates to the User Preferences screen, and then the Remote Status view. |
Auto Synchronization View |
Allows each user to do the following work:
The feature known as Auto Synchronization in previous releases is now named TrickleSync. The view for configuring TrickleSync is still named the Auto Synchronization view. To display this view, the user navigates to the User Preferences screen, and then the DB Synchronization view. |
How Siebel Remote Populates the App Server Name Field
Siebel Remote does not populate the App Server Name field until you run the Database Extract for the user. When Siebel Remote creates the S_NODE record for the remote client, the App Server Name field is NULL. If you use EIM to create remote clients, then the Mobile Clients list does not display any records that do not contain headquarters (HQ) as the parent server.
Siebel Remote stores the parent server in the following columns of the EIM_NODE table:
PAR_NAME
PAR_NODE_TYPE_CD
EIM does not require these columns. Siebel Remote does require them. If you use the Mobile Clients view to enter users, then Siebel Remote populates these columns, by default.
For more information about EIM, see Using EIM to Create Multiple Siebel Remote Clients. For more information about headquarters nodes, see Overview of Siebel Replication Manager.
Format That Siebel Remote Uses for the Remote Client Name, Database Name, Login ID, and Windows Password
The following table describes important format requirements that you must follow when you define a remote client name, database name, login ID, or password for a Microsoft Windows user account. Each of these items must meet the formatting requirements for Oracle Database XE or Microsoft Windows.
Table Format Requirements for the Remote Client Name, Database Name, Login ID, and Windows Password
| Object | Length | Case |
|---|---|---|
Client Name |
Can contain more than eight characters. |
Uppercase or lowercase. |
Database Name |
Cannot exceed 30 bytes. The limit is 30 characters in a single byte character set, or 15 characters in a double byte character set. |
Uppercase only. |
Login ID |
Cannot exceed 50 characters. |
Uppercase only. |
Password |
Can contain more than eight characters. |
Uppercase or lower case. |
Siebel Remote uses the remote client name to create inbox and outbox folders on the Siebel Server. This name must conform to a specific format.
The remote client name, database name, login ID, or Windows password can contain only the following items:
Roman characters
Alphanumeric characters
The underscore (_)
Character Usage
The remote client name, database name, login id, or Windows password cannot contain any of the following items:
Any special character listed in Setting Password and Lockout Preferences, except for the underscore (_).
Any of the following special characters:
\ (backslash)
dash (-), except for the server database name, which can contain a dash
" (quotation mark)
/ (slash)
(space)
| (vertical bar)
Unicode Usage for the User Login ID
If the user login ID contains Unicode characters, then the initialization fails. You cannot use Unicode in the user login ID.
User Language Preferences
A language preference allows the user to download data in a preferred language for the following dock objects that contain translation tables:
LOV
Product
Literature
Catalog
Catalog Category
This configuration helps optimize the size of the local database. Siebel Remote sets the Language field to empty to make sure the user receives data in all the languages for these dock objects, by default. Siebel Remote routes data for each of the other dock objects to the remote client according to the visibility rules.
For more information, see Transaction Router Server Component.
Using EIM to Create Multiple Siebel Remote Clients
You can use EIM (Enterprise Integration Manager) to do a batch load if Siebel Remote must load a significant amount of data, such as when it creates a large number of remote clients. If you use EIM to import records to the server database, then Siebel Remote logs transactions in the file system to improve performance. If a remote client possesses read and write access to the records that EIM imports during an EIM session, then it is strongly recommended that you use row by row logging. For more information, see Siebel Enterprise Integration Manager Administration Guide.
If your deployment includes Replication Manager, then Siebel CRM supports this EIM functionality only on the Siebel Server of the headquarters node. For more information about headquarters nodes, see Overview of Siebel Replication Manager. For more information on how to load data in interface tables, and then populate base tables, see Siebel Enterprise Integration Manager Administration Guide.
Using Transaction Logging with EIM or Assignment Manager
If you use EIM or Assignment Manager, and if the Enable Transaction Logging check box contains a check mark, then Siebel Remote logs modifications in the S_DOCK_TXN_LOG table, and then synchronizes them to the remote clients. If a large amount of data exists, then the Transaction Processor and Transaction Router might require a significant amount of time to process the modifications for each remote client. It might take so long that it is faster to reextract the remote client, and then apply the extract remotely.
It is recommended that you turn off transaction logging while EIM runs to avoid a rapid expansion of the S_DOCK_TXN_LOG table. After EIM finishes loading data, you must turn on transaction logging and reextract the remote clients. This configuration also prevents the risk of overloading the Transaction Processor and the Transaction Router.
A larger batch typically improves performance for EIM but can also cause problems for Siebel Remote. If you use EIM and Siebel Remote, then it is recommended that you limit batch sizes to 1000 or fewer records.
For more information, see Modifying the S_DOCK_TXN_LOG Table.
To use transaction logging with EIM or Assignment Manager
Disable transaction logging.
For more information, see Disabling Transaction Logging
Use EIM to load data or use Assignment Manager to assign data.
Make sure you limit batch sizes for EIM to 1000 or fewer records.
Enable transaction logging.
For more information, see Step 1 in the topic Configuring System Preferences for Transaction Logging.
Using Set-Based Logging for EIM
EIM logs transactions differently according to the following value of the LOG TRANSACTIONS TO FILE parameter:
TRUE. EIM logs transactions in the following folder with only one marker logged in the S_DOCK_TXN_LOG table:
FileSystem\eimFALSE. EIM logs transactions in sets to reduce database contention in the S_DOCK_TXN log. It only records one transaction for each EIM set in the S_DOCK_TXN_LOG table.
Avoiding Transaction Processor Failures That Are Caused by Moving the File System
The Transaction Processor might fail with an error that is similar to the following:
Unable to open User Txn Log file for reading or writing in FileSystem\eim\*.dx.
The following situation can cause this error:
EIM runs with the LOG TRANSACTIONS TO FILE parameter set to the default TRUE to collect EIM transactions in the
FileSystem\eimfolder.You move the file system from the
FileSystem\eimfolder to another folder, such asNewFileSystem\eim.You delete the
FileSystem\eimfolder.You start the Transaction Processor.
The master transaction in the S_DOCK_TXN_LOG table indicates that the EIM log exists in the FileSystem\eim folder. The Transaction Processor fails when it cannot open the FileSystem\eim\*.dx file. For more information, see Modifying the S_DOCK_TXN_LOG Table.
To avoid Transaction Processor failures that are caused by moving the file system
Before you move the file system, make sure the Transaction Processor finishes processing all transactions that exist in the
FileSystem\eimfolder.If you already moved the file system, then do the following:
Create the
FileSystem\eimfolder.Copy all DX files from the
NewFileSystem\eimfolder to theFileSystem\eimfolder.
Start the Transaction Processor.
Process of Configuring Encryption and Authentication for the Remote Client
This task is a step in Process of Configuring the Remote Client.
You do the following tasks to configure encryption and authentication for the remote client:
Configuring TLS Encryption for Siebel Remote
This task is a step in Process of Configuring Encryption and Authentication for the Remote Client.
As of Siebel CRM 19.6 Update, Siebel Remote supports Transport Layer Security (TLS) for Synchronization Manager synchronization with remote clients.
To use TLS encryption, SHA-2 certificate files must be deployed on the Siebel Server and the remote clients and TLS encryption must be configured for the Synchronization Manager component and the remote clients. If the parameters do not match each other, then a connection error occurs. For more information about using certificates and key files for TLS authentication, see Siebel Security Guide. For information about setting parameters for servers and clients, see Siebel System Administration Guide.
To configure TLS encryption on Siebel Server
Deploy the certificate files on the Siebel Server. For example, on Microsoft Windows you might deploy the certificate in a directory like
C:\siebelcerts. Perform this step if you have not already configured TLS for this Siebel Server.In the Siebel application, make sure advanced parameters are visible.
For more information, see Making Advanced Server Parameters Visible.
Set the Communication Type (alias CommType) parameter server component to TLS for the Synchronization Manager component.
To use the administrative interface, you do the following steps:
Locate the record for the Synchronization Manager server component. For more information, see Locating the Record for a Server Component.
In the bottom applet, click the Parameters tab, click Advanced, and then query the Parameter field for Communication Type.
Set the Value on Restart field to TLS.
Alternatively, you can set this parameter in Server Manager by using a command like the following:
srvrmgr> change param CommType=TLS for comp SynchMgr
See also Opening the Command Line Interface for Server Manager.
If the Encryption Type (alias Crypt) parameter is set to RSA (or any other value) for Synchronization Manager, then set it to None.
Set the KeyFilePassword, KeyFileName, CertFileName, and CACertFileName parameters at the enterprise level to specify the certificate files you have deployed, using commands like the following. Perform this step if you have not already configured TLS for this Siebel Server.
srvrmgr> change ent param KeyFilePassword=pwd srvrmgr> change ent param KeyFileName=key_file_name srvrmgr> change ent param CertFileName=cert_file_name srvrmgr> change ent param CACertFileName=CA_cert_file_name
Note: The parameter values must include the full path and file name for each file referenced. For example, for CACertFileName, you might set CA_cert_file_name to a value like/export/home/sblqa1/certs/cacert.pem.Stop the Siebel Server system service, and then restart it.
To configure TLS encryption on each remote client
Deploy a copy of the same certificate file that you deployed on the server and specified using the CACertFileName parameter.
You must deploy this certificate file in the
SIEBEL_CLIENT_ROOT\siebelcertsdirectory, such asC:\Siebel\Client\siebelcerts. Create this directory if it does not exist.Create a configuration file named configuration.properties in the directory where you deployed the certificate file. Edit the file in a text editor like Notepad and include an entry like the following to specify the certificate file:
[CertificationInfo] CACertFileName=SIEBEL_CLIENT_ROOT\siebelcerts\cacert.pemFor example, set a value like
C:\Siebel\Client\siebelcerts\cacert.pem.Edit the application configuration file (such as siebel.cfg or uagent.cfg) in a text editor like Notepad. In the [LOCAL_XE] section, change the value of the DockConnString parameter for the local database. Add :TLS at the end of the value. (If necessary, first remove the values RSA or None at the end of the line, including preceding colons.)
For more information, see Formatting the DockConnString Parameter and Modifying the Siebel Configuration File for Siebel Remote.
Configuring Encryption for the Local Database Password
This task is a step in Process of Configuring Encryption and Authentication for the Remote Client.
To add a layer of security, encryption removes the relationship that exists between the password that Siebel Remote stores in the local database and the unencrypted password that the user enters. You can configure RSA SHA-1 encryption, which is a one-way hashing algorithm. Siebel Remote applies this algorithm to the local database password before it sends this password to the local database for authentication. Siebel Remote uses the security adapter on the remote client to encrypt the local database password. You must configure the Siebel Server and the remote client to encrypt the local database password.
Related Topic
To configure encryption for the local database password
Make sure synchronization is configured for encryption.
For more information, see Process of Configuring Encryption and Authentication for the Remote Client.
Make sure the parameters in the configuration file on the remote client contain the values that Siebel Remote requires to encrypt the local database password.
For more information, see Configuration File Parameters That Siebel Remote Uses to Encrypt the Local Database Password.
Make sure you set the following parameter correctly when you extract the server database:
Encrypt client Db password
For more information, see Setting Encryption on the Local Database Password.
Configuration File Parameters That Siebel Remote Uses to Encrypt the Local Database Password
The following table describes the parameters and their values that you must set to encrypt the local database password. Siebel CRM comes predefined with most of these values already set. However, it is strongly recommended that you confirm them. For more information, see Modifying the Siebel Configuration File for Siebel Remote and Setting Encryption on the Local Database Password.
Table Configuration File Parameters That Siebel Remote Uses to Encrypt the Local Database Password
| Section | Parameter and Value | Description |
|---|---|---|
InfraSecMgr |
SecAdptName = DBSecAdpt |
DBSecAdpt is the default name for the section in the configuration file that defines the security adapter. |
SecAdptMode = DB |
DB (database authentication mode) is the only supported authentication mode that Siebel Remote uses for local database authentication. |
|
DBSecAdpt |
SecAdptDllName = sscfsadb |
Specifies the DLL name for the default security adapter. This is a default setting and applies in Windows and UNIX environments. |
DataSourceName = Local |
Specifies to apply this security adapter section to the [LOCAL_XE] data source section in this configuration file. |
|
DBSecAdpt_PropagateChange = TRUE |
TRUE allows the user to modify the local database password. |
|
Local |
DSHashUserPwd = TRUE |
Set to TRUE to encrypt the local database password in the Local data source. If you configure the Siebel Server to enable local database password encryption, then the Upgrade Wizard makes this setting when it initializes the local database. |
DSHashAlgorithm = RSASHA1 |
Use RSA SHA-1 encryption. If you configure the Siebel Server to enable local database password encryption, then the Upgrade Wizard makes this setting when it initializes the local database. |
Creating Accounts and Passwords
This task is a step in Process of Configuring Encryption and Authentication for the Remote Client.
You must create an account for each client to authenticate a remote client when it synchronizes. The authentication method you choose determines the account you must create.
To create accounts and passwords
Create an account and password according to the type of authentication you use. Use values from the following table.
| Authentication | Work You Must Do |
|---|---|
AppServer authentication |
Create a user account on the Siebel Server for each remote client:
For more information, see How the Change Password Functionality Affects Authentication. |
Database authentication |
Create a database account and password for each remote client. |
Siebel authentication |
Do the following:
|
SecurityAdapter authentication |
Create the accounts and passwords that your third party authentication system requires. For example, it might be necessary for you to create records in an LDAP folder. |
No authentication |
Do not create accounts or passwords for authentication. |
How the Change Password Functionality Affects Authentication
If you use the change password functionality on the remote client while connected to the Siebel Server, then Siebel Remote modifies the server password and stores it in a table that is specific to the server database, and not in a Siebel table. In this situation, the remote client is not synchronized with the local database. The user must continue to use the old user password to access the local database until the next time Siebel Remote reextracts the node.
Summary of Accounts, User IDs, and Passwords That Siebel Remote Uses
The following table summarizes the accounts, user IDs, and passwords that Siebel Remote uses.
Table Summary of Accounts, User IDs, and Passwords That Siebel Remote Uses
| Password, User ID, or Account | Description |
|---|---|
Local Database Password |
Maintains different credentials to access and synchronize the local database. For more information, see Setting the Local Database Password. |
User ID for the Local Database |
The user ID for the local database. |
User ID and password on the server database |
For more information, see Parameters of the Synchronization Manager Server Component. |
Password for the DBA account |
Configured when you run the Generate New Database server component. For more information, see Parameters of the Generate New Database Server Component. |
Synchronization password |
For more information, see Configuring the Remote Client to Automatically Synchronize. |
Authentication accounts and passwords |
For more information, see Creating Accounts and Passwords. |
User name and password for the Siebel Gateway |
For more information, see Registering a New Password with the Siebel Gateway. |
Table owner password on the regional database |
For more information, see Parameters of the Regional Database Initialization Program. |
Setting the Local Database Password
This task is a step in Process of Configuring Encryption and Authentication for the Remote Client.
Using different credentials to access and synchronize the local database provides a layer of security against unauthorized access to the local database and the server database. The user can redefine the password for the local database so that it is different from the synchronization password. For more information, see About the Siebel Enterprise and the Siebel Enterprise Server.
To modify the local database password
Start the remote client.
Log in to the local database.
For more information, see Logging in to the Local Database.
Navigate to the User Preferences screen, and then the Profile view.
Enter the new password in the Password field and in the Verify Password field.
Click Save.
Controlling the Data That Siebel Remote Routes to Clients
This topic describes how to configure dock objects and routing models that allow you to control the data that Siebel Remote routes to clients. It includes the following information:
You can use any of these topics to configure dock objects.
For more information, see How Siebel Remote Filters the Data It Synchronizes.
Using Selective Retrieval to Route Data
You can assign a remote client to the Selective Retrieval routing model. You can also assign the user to a responsibility that corresponds to the Selective Retrieval routing model, such as the Selective Retrieval Routing Model responsibility.
For more information about:
Selective retrieval, see Selective Retrieval Routing Model.
Assigning a routing model when you register a remote client, see Configuring the Remote Client to Automatically Synchronize.
Modifying a routing model, see Modifying the Routing Model for a Remote Client.
Assigning a responsibility, see Siebel Security Guide.
Enabling Records for Selective Retrieval While Logged in as a User
This topic describes how to enable a record for selective retrieval while logged in as a user.
To enable records for selective retrieval while logged in as a user
Log in to the Siebel application using a direct connection to the Siebel Server.
Do not log in with a connection to the local database. Use the User ID that is associated with the user that you must enable for selective retrieval.
Navigate to the screen that contains the record you must synchronize.
Selective Retrieval supports the following screens:
Accounts
Contacts
Opportunities
Projects
Service Requests
Navigate to a predefined view for the chosen screen.
For example, navigate to the My Accounts view or the All Accounts view of the Accounts screen, or the Project List view of the Projects screen.
Query for the record that you must include in future synchronizations.
In the list or in the form that the Siebel application displays for the record, click Menu, and then choose Make Available Offline.
Disabling Records for Selective Retrieval While Logged in as a User
This topic describes how to disable a record for selective retrieval while logged in as a user.
To disable records for selective retrieval while logged in as a user
Do Step 1 in the topic Enabling Records for Selective Retrieval While Logged in as a User except log in to the Siebel application using a direct connection to the Siebel Server or the local database.
Do Step 2 through Step 5 in the procedure in the topic Enabling Records for Selective Retrieval While Logged in as a User except choose the Make Unavailable Offline menu item.
Enabling Records for Selective Retrieval While Logged In as an Administrator
This topic describes how to enable a record for selective retrieval while logged in as an administrator.
To enable records for selective retrieval while logged in as an administrator
Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to an administrative view that displays the record you must synchronize:
For an account, navigate to the Accounts screen, and then the Accounts Administration view.
For a contact, navigate to the Contacts screen, and then the Administration view.
For an opportunity, navigate to the Opportunities screen, and then the Opportunities Administration view.
For a project, navigate to the Administration - Data screen, and then the Projects view.
For a service request, navigate to the Service screen, and then the Service Requests List view. Use the visibility filter to display All Service Requests.
Query for the record that you must include in future synchronizations for a user.
If the object is an account, contact or opportunity, then click Menu, choose Columns Displayed, and then move the field described in the following list to Selected Columns:
For an account, display the Account Team field in the Accounts list.
For a contact, display the Contacts Team field in the Contacts list.
For an opportunity, display the Sales Team in the Opportunities list.
For a project, skip this step. The Members field is already visible in the Details area of the Project form.
For a service request, skip this step. A service request contains a single owner. The owner is the only user for whom you can enable the record for synchronization.
Click Save.
Display the dialog box according to the type of record you are enabling for selective retrieval:
For an account, click the select icon in the Account Team field to display the Account Team Member dialog box.
For a contact, click the select icon in the Contact Team field to display the Access List dialog box.
For an opportunity, click the select icon in the Sales Team field to display the Team Members dialog box.
For a project, in the Details area of the Projects form, click the select icon in the Members field.
For a service request, skip this step, and proceed to Step 8.
In the Selected list, choose the user with whom Siebel Remote must synchronize the record, scroll to the right, make sure the Available Offline check box contains a check mark, and then click OK.
For a service request, in the All Service Requests list, click Menu, and then choose the Make Available Offline menu item.
Disabling Records for Selective Retrieval While Logged in as an Administrator
This topic describes how to disable a record for selective retrieval while logged in as an administrator.
To disable records for selective retrieval while logged in as an administrator
Do Step 1 through Step 6 in the previous procedure.
Remove the record from selective retrieval:
For an account, contact, opportunity, or project, do Step 7 in the previous procedure, except make sure the Available Offline check box does not contain a check mark.
For a service request, do Step 8 in the previous procedure, except choose the Make Unavailable Offline menu item instead of the Make Available Offline menu item.
Using Responsibilities to Route Data
Some routing models include a predefined responsibility. You can use the responsibility and the routing model to control the data that Siebel Remote routes to a remote client.
To use responsibilities to route data
Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to the Administration - Application screen, and then the Responsibilities view.
In the Responsibilities list, query the Responsibility field for the name of the routing model, such as Sales Manager Routing Model.
Examine the Views list.
Use the responsibility and the routing model to control the data that Siebel Remote routes to a remote client.
Modifying a Routing Model
If you use the Database Extensibility feature to create an extension table, then you can sometimes use the docking wizard in Siebel Tools to create a routing rule. You can use this wizard for a custom table that you have not yet placed in a dock object or for a custom extension column that you have not yet added to a predefined table. If you use this wizard to create a new rule, then to maintain optimum performance, it is recommended that you index the server database columns that the new rule affects. For help with modifying a routing model, see Getting Help from Oracle. For more information about the docking wizard, see Configuring Siebel Business Applications.
Limiting the Views That a Remote Client Displays
This task is a step in Process of Configuring the Remote Client.
This topic includes the following information:
You can use one or more of these topics to limit how Siebel Remote displays views in the remote client
You can assign a user to a routing model to optimize the size of the local database that Siebel Remote uses for this user. You can limit the views that the user can access to match the data that Siebel Remote routes to the user. It is recommended that you limit views for all users except users who use the Standard routing models or models that are similar to the Standard models, such as the Life Sciences User routing model.
Determining the views a user can access depends on the responsibilities that you assign to this user and on the views that you assign to each responsibility. Each view that is associated with a responsibility includes a Local Access flag. You can turn this flag off to remove access to the view. This limitation applies only if the user uses a remote client (Mobile Web Client). It does not apply if the user uses the Siebel Web Client.
Limiting Access to Views by Modifying Responsibilities
This topic describes how to limit access to a view by modifying the user responsibilities. For important caution information, see How Positions, Organizations, and Responsibilities Affect Access.
To limit access to views by modifying responsibilities
Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Identify the responsibilities that are assigned to this user:
Navigate to the Administration - User screen, and then the Users view.
Query the User ID field for the user that Siebel Remote must limit access.
Click the select icon in the Responsibility field.
Examine the Selected window to identify the responsibilities that are assigned to this user.
You can assign a user to multiple responsibilities, and each of these responsibilities can include the same view. If the Local Access check box does not contain a check mark for the view in any of the responsibilities that are assigned to the user, then the view is not available on the remote client. In this situation, the view does not display in any navigation element on this client, including the Site Map.
Identify the views that the user does not require.
Navigate to the Administration - Application screen, and then the Responsibilities list.
Query the Responsibility field for the primary responsibility that is assigned to the user.
In the Views list, query the View Name field for the view that the user does not require.
Make sure the Local Access check box does not contain a check mark.
Repeat Step 6 and Step 7 for each additional view that the user does not require.
Repeat Step 5 and Step 8 for each additional responsibility that is assigned to the user.
Inform the user that they must log out and then log back in to the remote client.
For more information, see Updating a Responsibility.
Limiting Access to Views by Disabling Local Access in Routing Model Responsibilities
This topic describes how to limit the views that a routing model responsibility allows. A routing model responsibility is a type of responsibility that includes Routing Model as the suffix in the responsibility name. The Sales Representative Routing Model is an example of a routing model responsibility. If you use this configuration, then is not necessary for you to examine the local access settings for other responsibilities.
To limit access to views by disabling local access in routing model responsibilities
Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to the Administration - Application screen, and then the Responsibilities list.
Locate the responsibilities that contain the routing model suffix. Do the following work:
Click Query.
Enter the following value in the Responsibility field:
*Routing Model*
Press Enter.
Siebel CRM displays the following routing model responsibilities:
Sales Representative Routing Model
Sales Manager Routing Model
Minimal Data Routing Model
Analyst Routing Model
In the Views list, add a view to the responsibility that the user must not access.
Make sure the Local Access check box does not contain a check mark for the view you added in Step 4.
Optional. Repeat Step 4 and Step 5 to limit access to more views.
Limiting Access to Views for All Responsibilities
Limiting access to a view provides a more global way to limit access than limiting access to a view according to a responsibility. If you use the procedure that this topic describes, then Siebel Remote limits access to the view for every responsibility that references the view.
To limit access to views for all responsibilities
Log in to the Siebel Server with administrator privileges.
For more information, see Logging in to the Siebel Database as an Administrator.
Navigate to the Administration - Application screen, and then the Views list.
In the Views list, query the Name field for the view where you must limit access.
Make sure the Default Local Access check box does not contain a check mark.
The Views list includes the entire list of views that the Siebel application displays. It includes a subordinate Responsibilities list that allows you to identify the responsibilities that Siebel CRM associates with a view. The Local Access flag determines if a view is available for the user that Siebel CRM assigns to the responsibility.
Limiting Access to the Global Accounts View
It is recommended that you limit access to the My Global Accounts view for the remote client. The My Global Accounts view references tables that private dock objects use. For example, the table that the Global Account Detail - Sub Account view references is a part of the following visibility:
Dynamic Hierarchy Dock Object with Private
If the user accesses this view, then Siebel CRM might display an error message that is similar to the following message:
The selected record is not included as part of your responsibility.
The Global Accounts view is not of the All visibility type. It is recommended that the view not be available to the user. Data visibility is one of the following types:
Enterprise
Limited
Private
This visibility controls only data routing from the Siebel Server to the remote client. It does not control the visibility of any views on the remote client. The responsibility that Siebel CRM uses for the remote client determines if a view is visible.