|Bookshelf Home | Contents | Index | PDF|
NOTE: If a new configuration is created, a configuration is split or merged with another configuration, or the name of an existing configuration is changed, the ComponentName parameter on the corresponding Siebel clients must also be updated so that the clients can detect any upgrades.
At times, you may need to add components to an existing configuration. Any custom component that you create must be added to a configuration before you can use it to distribute upgrades. The following procedure describes how to perform this task.
Adding components to a configuration is a step in Process of Limiting Distribution of an Upgrade Kit.
In most cases, the configurations provided with Siebel Anywhere are sufficient. However, you can create new configurations for special situations or to represent different installed clients within your company.
Creating a new configuration is a step in Process of Limiting Distribution of an Upgrade Kit.
For example, if everyone in your company uses Siebel Sales and you need to distribute certain upgrades to employees in remote offices separately from the rest of the company, you would create a new configuration to accommodate this situation. The employees in the remote offices would be temporarily associated with the new configuration so that you could distribute the special upgrade just to them. (See Assigning Employees to a Configuration for details on associating specific employees with a configuration.)
Also, you may need to create different configurations based upon language usage. If there is a set of the users in your company only using English (ENU) and another set using both English (ENU) and German (DEU), you should create two different configurations.
NOTE: The recommended method for creating a new configuration is to copy an existing configuration and modify the copy, as this method minimizes the possibility for error. The following procedure describes the use of this method. However, it is also possible to use standard Siebel application techniques to create a new record and fill in the necessary fields.
The purpose of assigning employees to configurations is to handle uncommon situations, such as having one particular employee retrieve and test a kit. In most cases, testing is done using special test accounts and test configurations, and regular employees are associated with a specific configuration based on a ComponentName entry in the CFG file of an application.
Assigning employees to a configuration is a step in Process of Limiting Distribution of an Upgrade Kit.
For example, in the Siebel Sales application the ComponentName in the default CFG file (siebel.cfg) would be Siebel Sales Client by default. This means that everyone using the Siebel Sales application is automatically associated with the Siebel Sales configuration.
Assigning employees to a configuration in the Employees list in the Upgrade Configurations view can be used in place of the entry in the CFG file, or as a method for overriding the entry in the CFG file.
CAUTION: It is strongly recommended that you run only the Siebel Smart Web Client for user accounts that have Siebel administrator responsibilities, to make sure that administrative tasks are performed while connected to the HQ server, and to make sure that the administrator is not prevented from logging in for reasons related to component versions. However, if you run the Siebel Developer Web Client for any administrator account, it is strongly recommended that the account not be associated with a Siebel Anywhere configuration. This precaution also helps prevent version-related login problems.
Siebel Anywhere will not allow an Employee to be dynamically associated with more than one configuration. For example, if the employee JSMITH is dynamically associated with Configuration A and the Siebel administrator then associates JSMITH with Configuration B, JSMITH will automatically be disassociated from Configuration A and only dynamically associated with Configuration B.
CAUTION: If an employee is accidentally associated with an incorrect configuration, that employee is disassociated from the correct configuration, and may not have access to upgrades that are distributed to the correct configuration. For this reason, it is best to correct the configuration assignment without delay.
If an employee will use more than one installation of the Siebel client in the same Siebel software implementation, do not associate that employee with a configuration. For example, if the Employee JSMITH chooses to install and use both Siebel Call Center and Siebel Sales, then that employee should not be dynamically associated with a Siebel Anywhere configuration. The reason is the upgrade kit for one configuration will likely be different than the upgrade kit for another configuration.
In this example, the CFG file would be different for the Siebel Call Center and Siebel Sales configurations. If JSMITH were dynamically associated to the Call Center configuration and logged on using the Siebel Sales client, the version check would only detect that there was a new upgrade kit and would not differentiate between the two installations of the Siebel client.
If the login is specified under an Employees view, then Siebel Anywhere does not check the CFG file any further and only checks the version of the component listed under the associated configuration for that client. Typically, Siebel Anywhere groups users by the product they use, for example Call Center or Sales Client, which is determined by the CFG file the user uses.
NOTE: The first time a Mobile Web Client connects to the Remote Server to initialize the local database, Siebel Anywhere does a version check for the client using the Upgrade Configuration specified in the CFG file. Siebel Anywhere cannot detect a dynamic configuration assignment at this time. However, after the Mobile Web Client successfully initializes the local database, Siebel Anywhere can detect any dynamic configuration assignment for that client.
NOTE: When it initializes the local database for the first time, Siebel Anywhere uses the configuration in the CFG file. It does not use the configuration defined in the Employees view under the Administration - Siebel Anywhere Screen.
Removing employees from a configuration is a step in Process of Limiting Distribution of an Upgrade Kit.
|Siebel Anywhere Administration Guide|