Setup: Configuring the Siebel CRM Server
Configuring Siebel Customer Relationship Management (CRM) involves making required changes in the database and in the Siebel Mobile client configuration files.
To configure Siebel CRM
- Back up the database.
- Configure the Siebel Mobile client.
- Configure the Siebel database.
- Compile the project configuration changes.
- Configure the List of Values for the Siebel Server and Opportunity projects.
- Configure the object map for the Solution Starter.
- Import and activate workflow processes.
- Configure the Siebel Tools application.
- Apply database configuration changes.
- Recompile the Siebel projects.
You can easily revert to your previous Siebel Server configuration by restoring the settings to their previous values, as long as you have backed up your files or kept a record of changes. However, undoing changes to the database itself is more difficult, because the database is compiled. To help prevent loss of your configuration, before you make changes to the Siebel Mobile client, be sure to back up the Siebel generic sample database.
To back up the Siebel sample database
- Browse to the directory [Siebel root]\client\SAMPLE\UTF8.
- Locate the Sse_samp.dbf database file, which the Solution Starter will use, and make a copy of it in case you need to revert to your original configuration. Rename the copy to indicate it is the backup generic sample database, such as Sse_samp_vanilla.dbf.
You must change the Siebel Mobile client configuration file so that the Project Server to Siebel Solutions Starter can use it.
To configure the Siebel Mobile client
- Browse to the Siebel Mobile client installation directory, [Siebel Root]\tools\bin\enu\.
- Open the configuration file Tools.cfg, copy the entire
ConnectStringline in the
[Sample]section, and paste it as a new line.
- Type a semicolon ( ; ) at the beginning of the first
ConnectStringline to comment it out.
- Change the new
ConnectStringparameter to the path of your sample database. The
ConnectStringparameter should look similar to the following:
To change the Sse_samp.dbf database to reflect the modifications needed for building the Project Server to Siebel Solution Starter, you must lock the Siebel projects and import the Siebel project archive. The following procedures describe the process.
Locking the Siebel projects before updating them avoids potential database corruption from other users or processes.
To lock the Siebel projects
- Start the Siebel Tools application and log on as SADMIN.
- In the Object Explorer window, select All Projects.
- Click the Types tab and select Project. The Project window shows a list of all the Siebel projects.
- Create a new project named MS Office Project. You will import the project data in the next section.
- Select the Locked field for each of the following projects, as shown in Figure 1.
MS Office Project
PS Feature Tracking
PS Project Management
PS Project Management (SSE)
PS Project Plan Integration
PS Project Plan Integration (SSE)
PS Subcontractor Assignment
Siebel Universal Agent
Time Sheet (SSE)
Figure 1. Lock Siebel sample database projects
A Siebel project archive stores all project objects in a file with a .sif extension. The Solution Starter includes the project archive in the Siebel Archive directory of the Solution Starter download.
To import a Siebel project archive
- Extract the file ChangedProjects.sif from [SolutionStarterPath]\Siebel Archive\ChangedProjects.zip.
- On the Siebel Tools menu, click Import from Archive.
- On the File menu, click Open, select the file [SolutionStarterPath]\Siebel Archive\ChangedProjects.sif to import, and then click Open.
The Import Wizard - Preview page appears, showing a list of all the objects it will import.
- Under Conflict resolution, click Overwrite the object definition in the repository (Figure 2). Click Next.
Figure 2. Import Wizard, conflict resolution
- In the Import Wizard – Review Conflicts and Actions dialog box, click Next.
The Siebel message box appears, and lists the number of changes that Siebel will make to your repository. Click Yes to accept the changes.
- The Import Wizard – Summary page shows all of the changes made (Figure 3). When the wizard is done applying changes (without errors), click Finish.
Figure 3. Import Wizard – Summary page
Now that you have made all of the requisite changes to the Siebel configuration, you must compile the changes so that Siebel can use them.
Recall that you manually added the new project named MS Office Project and then locked it, in the section Lock Siebel Projects. When you imported ChangedProjects.sif the MS Office Project details are imported. In the following procedure the projects must be locked to be compiled.
Note Make sure that you back up the generic Siebel repository file (.srf file), so that a copy of it exists in a location other than the currently selected Siebel repository file path.
To compile configuration changes
- Open the Siebel Tools application.
- On the Tools menu, click Compile Projects.
- In the Object Compiler dialog box, make sure Locked projects is selected
- Enter the correct path in the Siebel repository file box (Figure 4), for example:
- Click Compile.
Siebel compiles the project with the configuration changes you have made, along with the Siebel repository file, to produce the client application for the Project Server to Siebel Solution Starter.
Figure 4. Siebel Tools– Object Compiler dialog box
You must configure the Siebel Solution Starter application for the List of Values (LOV) parameters. These include both server-specific and opportunity-specific parameters.
To configure for server-specific parameters
- Open a Siebel application such as Siebel Sales or Siebel Call Center, and log on as SADMIN.
- Configure the predefined List of Values to use for the Project Server to Siebel Solution Starter as follows.
- Click the Site Map icon, and then click the Application Administration tab.
- Click the LOV Explorer link to show the List of Values Explorer, and then click New in the List Of Values – Type applet.
- In the Type field, type MSOP_OPPORTUNITY_THRESHOLD and click Save (Figure 5).
Similarly, add MSOP_PROJECT_SERVER_NAME. It is not necessary to add OPTY_TYPE, since it already exists by default.
Note Check your spelling carefully because you will import workflow objects that reference these specific values.
Figure 5. Siebel application administration - adding predefined variables
- In the Show drop-down list box, select List of Values.
- In the List of Values applet click New, and then click the icon in the Type field. This will display the Pick Value Type applet.
- In the Pick Value Type page in the Query applet (Figure 6), do the following:
- In the Find drop-down list box, select Type.
- In the Starting with text box type MSOP, and then click Go.
- The Type list should now contain both of the LOVs you just created.
Figure 6. Siebel List of Values
- Select MSOP_OPPORTUNITY_THRESHOLD, and then click OK.
- Enter the values shown in Table 1 into the List of Values view for the new LOV parameters. Select the Active and Translate check boxes to set them to True for each LOV parameter (Figure 7). For example, your server URL might be http://myserver/projectserver.
Table 1. Siebel LOV parameter creation
LOV Parameter Display Value Language Independent Code Language Name Active Translate MSOP_OPPORTUNITY_THRESHOLD 20 20 English American True True MSOP_PROJECT_SERVER_NAME <your server URL> <your server URL> English American True True
Note The Display Value field has a 30 character maximum limit, and is used only for the user interface value. If your Project Server URL is more than 30 characters, it will be truncated in the display. However, Siebel uses the full Language Independent Code value internally.
Figure 7. Siebel List of Values, server-specific parameters
You will now add the Project Server template names to the Opportunity types (OPTY_TYPE) in the List of Values view, in the same way you added the server-specific parameters. See Figure 8.
To configure opportunity-specific parameters
- For each Project Server template, create a new OPTY_TYPE record in the Type list.
- Type the template name in both the LOV and Display Value fields (Figure 9 does not show the LOV column).
- Set the Language Independent Code to English-American.
- Select the Active and Translate check boxes for each LOV parameter. They are set to True when checked.
Table 2. Siebel opportunity workflow LOV parameters
LOV parameter Display value Language independent code Active Translate Commercial Construction Commercial Construction English-American True True New Business New Business English-American True True Software Development Software Development English-American True True
Figure 8. Siebel opportunity-specific parameters
Next you must configure the Solution Starter data mapping, so the Siebel Business Objects map correctly to the data.
To configure data mapping
- Click the Site Map icon and then click the Integration Administration link.
- Click the Data Map Editor link.
- In the Integration Object Map applet, click Import Data Map in the applet drop-down menu.
- Click Browse in the EAI DTE Import dialog box, and select the data mapping file MSOP - ProjectServer1.xml from the Data Map directory where you installed the Solution Starter files. (The path shown in Figure 9 is C:\Siebel.Connector\Setup\Data Map\.) Click Import.
Figure 9. Siebel EAI DTE Import page
If you enter the query MSOP*, you should now see MSOP – Project Server 1.
You must configure the Siebel workflows for the Project Server to Siebel Solution Starter. To start the process, click the Site Map icon, and in the main window click the Business Process Administration tab. In the Show drop-down list box, click Workflow Processes. You will need to configure each of the three workflow processes.
To configure each workflow process
- In the Workflow Processes applet, click Import Workflow on the applet drop-down menu (Figure 10).
Figure 10. Siebel Workflow Processes applet
- In the Workflow Process Import dialog box, click Browse and navigate to the Workflow directory where you installed the Solution Starter. Select a workflow process file and click Import. You can only select one file at a time. Repeat the import process for each of the three workflow files: MSOP - AssignmentsGet.xml, MSOP - SblCreateProject.xml, and MSOP - SblGetProjectData.xml.
After the three workflow process files are imported, you must activate them before they can be used.
To activate each workflow process
- In the Workflow Processes applet, click Query. Type MSOP* in the Name field, then click GO to show the three imported workflows.
- Click a workflow record to select it, and then click Activate (Figure 11). Do this for each of the three workflow records; the Status field of an activated workflow changes from In Progress to Active.
Figure 11. Siebel workflow processes
- After all three of the workflow processes are activated, log off of Siebel.
Now that the List of Values is configured in the application you opened (for example, the Siebel Sales application), your next step will be to configure the Siebel Tools application.
To configure the Siebel Tools application
- Start the Siebel Tools application and log on as SADMIN.
- On the View menu, click Options.
- In the Development Tools Options dialog box, click the Scripting tab, and then type [Siebel root]\client\public\enu in the Browser script compilation folder box (replace [Siebel root] with the actual path on your computer, such as C:\sea751). Click OK (Figure 12).
Figure 12. Siebel Workflow — Development Tools Options dialog box
An additional column is added to one of the Siebel database tables during configuration. After compilation is completed, you must apply configuration changes.
To create a new ODBC data source and apply configuration changes
- Open the Windows Server 2003 Control Panel, double-click Administrative Tools, and then double-click Data Sources (ODBC).
- In the ODBC Data Source Administrator dialog box, on the User DSN tab, click Add.
- In the Create New Data Source dialog box, select the Siebel database driver name to set up a data source. For example, click Siebel Database c:\sea751\tools. Click Finish.
- In the ODBC Configuration dialog box, on the ODBC tab, type any name you want in the Data source name box. For example, type MSOP_SiebelData to indicate that this data source is used by Project Server.
- On the Database tab, type the following in the Start line box (C:\sea751 is the Siebel installation folder):
C:\sea751\tools\bin\dbeng8.exe -q -m -x NONE -gp 4096 -c40m -ch60m
- Click Browse and select the database file: C:\sea751\client\SAMPLE\UTF8\sse_samp.dbf
- On the Advanced tab, in the Character Set box, type UTF8.
- Click OK twice.
- Start Siebel Tools, log on as SADMIN, browse to the Table object in the Object Explorer pane, and then query for S_Proj* in the Object dialog box.
- Select the table S_PROJ_RSRC in the Tables pane, and then click Apply (Figure 13). Siebel shows a warning message box before the change is applied; click OK to apply the change.
Note The warning message appears only with the sample database.
Figure 13. Applying changes to the Project Server database
- In the Apply Schema dialog box, enter the field values as shown in Table 3.
Note The ODBC data source name is the name you entered in the ODBC Configuration dialog box.
Table 3. Siebel schema field names and values
Field Name Value Privileged user ID dba ODBC data source MSOP_SiebelData Privileged user password sql
- Click Apply to save the changes. Siebel displays a message box, Changes successfully applied.
Recompile all of the Siebel projects to enable the configuration changes you have made.
To enable configuration changes
- Start the Siebel Tools application and log on as SADMIN.
- In the Tools menu, click Compile Projects. In the Object Compiler dialog box, click All Projects.
- Browse to the Siebel repository file:
Select the file, and then click Compile.
The next step is to set up custom project templates. For more information, see Configuring Project Server.