Siebel Administration >  Set up Developer account in Siebel

Set up developer account in Siebel

Login Setup:

Developers work on Siebel Tools to configure Siebel and they are connected to Local Database. Local database contains all the object definitions plus the subset of actual data from the server.

To get all this information from the server, we follow a process of extracting all the object definitions from the server and storing into our local database.

Before we connect to the server and be able to extract the database, do these steps.

1) Install Tools, sample database and local client.

2) After the installation modify the tools.cfg & uagent.cfg

Change the Enterprise name in [Local] and [ServerDataSrc] to the Name of the Enterprise Server

The image below is from our Training environment.

The parameters in the tools.cfg file that need to be changed are

ConnectString = url_of_database

GatewayAddress = gateway_ip_address

EnterpriseServer = ENTERPRISE_NAME

Create a Database User Account:

Developers need a database based Siebel account. The user must have sse_role and connect role in Siebel database if you are using Oracle.

Setup Developers as Siebel Employees:

Setup each developer to be a Siebel Employee as described in the steps below.

·Login to Siebel Server using the login SADMIN/SADMIN or as any other account

that has Siebel Administrator responsibility or any account that has rights to the Administrator-User-> Employees screen.

· Go to Site-Map -> Administration-User-> Employees

· Create a new Record with First Name, Last Name and desired login Id.

Assign a Position and Responsibility to this User. Responsibility and position should be Siebel Administrator.

Check that Siebel Remote Group is Online/Active

Login as Siebel Administrator; go to Administration -Server Configuration -> Enterprises

In the second Applet from the top, select Component Groups. If Siebel Remote Component Group is disabled, you should enable it.

After enabling this Component Group, you should restart Siebel Servers/Gateway Servers.

After restarting, check that these components are Online/Running.

This can be checked from Server Manager or Administration Server Management -> Components Screen.

All these components should be online if the Siebel Remote Component Group is enabled.

Setup Developers as Mobile Clients:

After setting up developers as employees, you must register developers as mobile client.

This will provide information for extracting local database for that user. Follow the steps below.

· Login as either SADMIN or any other account having access to employee screens.

· Go to Site Map -> Administration-Siebel Remote -> Mobile Clients.

· In the Mobile Clients list, click New and fill up the following details.

Mobile Client = Siebel User ID (If something else is selected, the process could face issues)

User ID = Siebel User ID.

Routing Model = MOBILE CLIENT - EXTRACT ONLY

Generate Database:

Generate New Database Template alias GenNewDb is a Siebel Component. We need to run this job as the next step.

From application level menu, go to SiteMap -> Administration-Server Management-> Jobs

On the top applet, click New to create a new job and enter the following parameters

Under Component/Job Field select Generate New Database

Under Requested Server, enter server name where the job should run.

We must tell the developer which Server he should use to extract the local database.

In the bottom applet, enter Job Parameters by clicking ‘New’ button.

In Name field, select “SQL Anywhere Database”.

Use the default value sse_utf8.dbf

Click Start in the top applet to submit the Job.

After few minutes refresh and check the status of the Job should change to Success.

This process generates a database template for Siebel Server

Extract Database:

This process extracts data from the server database for the requested mobile user and stores temporarily into a compressed file onto the server.

Go to SiteMap -> Administration-Server Management-> Jobs

In the top applet, click New to create a new job and enter the following parameters

Under Component/Job Field select Database Extract

Under Requested Server, enter server name where the job should run. Select

In the bottom applet, enter Job Parameters by clicking New

Client Database encryption method = none

Client Name = Siebel User ID

Encrypt client Db password = False

Extract all Repository Tables = TRUE

In the top applet click Start to submit the Job

.
This will take a few minutes and the job status should change to Success.

After successfully running this step, you should now observe that a directory structure gets created normally under

$siebsrvr_root\DOCKING\.

In other servers, this folder should not be there.

Initializing Client:

This step has to be done by the developer. He should have edited Siebel.cfg and tools.cfg before to point to the correct Siebel server and database.

The developer should make one more change in tools.cfg

DockConnString =Siebel_Server_IP
Or
DockConnString =Siebel_Server_IP::40400

Launch Siebel Tools. Connect to Local.

The following message will appear "The local Siebel database was not found. Would

you like to connect to the Siebel Remote server to initialize the local database?"

Click Yes

This message appears because Siebel Tools could not find the database file sse_data.dbf . The correct location of the dbf file is set in tools.cfg .

In the tools.cfg file, there is a [Local] section. The parameter ConnectString should show you where the DBF file should be.

After we click ‘Yes’, enter client_name, user_id and passwords. To avoid complication, keep userid=client_name while creating remote user.

Enter the password and click ‘Continue’

Siebel Tools will start downloading and would take a while.

After this process is complete your Siebel Tools will Open.

If the initialization was successful you will see the database file see_data.dbf

in the folder mentioned in tools.cfg. In our case it is D:\Siebel\8.1\Tools_1\LOCAL

The developer will have to do a GET and also set his debug parameters correctly. He might have to make additional setup changes in his local computer.

Errors that we faced

siebel@server_name:/siebel/8.1/siebsrvr/enterprises/ent_name/log> vi DbXtract_0092_96468994.log
"DbXtract_0092_96468994.log" 167 lines, 21349 characters
1021 2013-01-29 10:57:44 2013-01-29 10:57:45 +0100 000000a7 001 ffff 0001 09 DbXtract 96468994 7885 1 /siebel/8.1/siebsrvr/enterprises/ent_name/log/DbXtract_0092_96468994.log 8.1.1.3 [21219] ENU
GenericLog GenericError 1 000bc5aa4fcf5f7d:0 2013-01-29 10:57:44 (smisched.cpp (911) err=327763 sys=0) SBL-DBX-00083: Unable to start due to incorrect system preference setting
TaskConfig TaskCfgParamError 1 000bc5aa4fcf5f7d:0 2013-01-29 10:57:45 ***********Dumping Parameters for the current task (96468994) because of
errors**********

Solution:
This error occurred when we tried to extract database for a user. To solve this,
Go to Administration Siebel Remote-> Remote System Preferences
Enable Transaction Logging.

After that restart Siebel servers.

SBL-DBX-00038: No local database template found.

This error happened when we tried to extract database for a user.

The solution was to run the Generate New Database again, on the same server where you are trying to extract the user’s database.