Data Validation Manager in Siebel

The Data Validation Manager business service can validate business component data based on a set of rules. In the case of a rule violation, a custom error message appears or a user-defined error code is returned.

The Data Validation Manager business service reduces the need for custom scripts, decreases implementation costs, and increases application performance.

To administer data validation rules, perform the following tasks:

1. Defining Error Messages for Data Validation (Administration - Data Validation > Validation Messages. )
2. Defining a Data Validation Rule Set (Administration - Data Validation > Rule Sets.)
3. Defining Rule Set Arguments
4. Defining Validation Rules
5. Defining Validation Rule Actions
6. Activating a Data Validation Rule Set

1.        Create Error Messages

2.       Create Rule sets and Rules and created desired expressions with the expression Builder

3.       Add the Error Message using the Return Code pick applet.

 Use Runtime Events or Workflow Process to triggerered from a runtime event to call the DVM bs.

Siebel Assignment Manager Made Simple

A lot of times it is seen that peple struggle with the assignment manager setup in siebel. The truth is that you need to follow a sequence of steps and you are done.


The first thing you would do is to find your assignment object in tools. If it is there well and good elso you need to create one.


Next question to be answered is whom should the record created be assigned(associated to)


Position? Employee? Organization?


Once you have answers proceed like this


Log into siebel Tools and create

a. Workflow Policy Column

b. Assignment Object (If not present)

c. Workflow Policy Component

d. Workflow Policy Component Col

e. Assignment Attribute

f. Assignment Criteria

Note:-Compile the changes to srf; Assignment Objects modification does not need any compilation

Create Assignment Rule select comparison method and add skill and skill items to the Assignment Candidates.

Use the following truth table given in bookshelf 

Table 38. Server Administration Tasks After Configuring Assignment Manager
Configuration Process	Compile .srf File	Restart Assignment Manager	Regenerate Triggers	Restart Workflow Monitor Agent1
Add or inactivate assignment objects	Yes	Yes	Yes	Yes
Configure assignment objects	No	Yes	Yes	Yes
Add, configure, or inactivate assignment attributes	Yes	Yes	Yes	Yes
Configure assignment attribute columns	No	Yes	Yes	Yes
Add, configure, or inactivate assignment criteria	Yes	Yes	Yes	Yes
Add, configure, or inactivate assignment criteria attributes	Yes	Yes	Yes	Yes
Activate, inactivate, or modify assignment policies	No	No	Yes	Yes

Use the following BS (Business Service) to trigger Assignment

BS:             Synchronous Assignment Manager Requests

Method:       Assign

Arg1:          AsgnObjName

Arg2:          ObjRowId (Row Id of record to be assigned)

This the simplest outline for assignment manager.Ofcourse you can always deep dive into the intrices of each object. Stay happy stay tuned

Assignment Manager Error Messages.Valuable information from the bookshelf

Error Code	Error Text1	Resolution
ERR_ASG_ALREADY_ASSIGNED	Assigned this object %1 (more recently than requested %2).	This is just information.
ERR_ASG_ASSIGN_REPLY	Selected %3 rules, %5 organizations, and %4 people for %1 (%2).	This is just information.
ERR_ASG_BASSIGN_REPLY	Assigned %1 rows for %2.	This is just information.
ERR_ASG_LOADING_OBJECT	Unable to load assignment object %1.	The configuration of the assignment object is not correct. Use Siebel Tools to check the configuration of the assignment object.
ERR_ASG_BDENORM_REPLY	Denormalized %1 rows for %2.	This is just information.
ERR_ASG_CANNOT_ASSIGN_ LOCKED_ROW	Cannot assign this item because it is in a locked state. (Object Name = %1, Object Row Id = %2.)	If you want to assign this object, please uncheck the Lock Assignment field for the object being assigned. Otherwise, this is just information.
ERR_ASG_DENORM_REPLY	Denormalized %1 rows for %2.	This is just information.
ERR_ASG_DUP_CONFLICT	Unable to update row (%1) because updated values violate unique index with an existing row (%2).	Check the data on your team table on the object row_ID where it failed.
ERR_ASG_INVALID_BU_ DFLT_NAME	Default organization %1 for assignment object %2 is not found in the organizations table. Please check that Default Organization - %1 is a valid organization.	Use Siebel Tools to set the Default Organization parameter for the assignment object to a valid organization in the database.
ERR_ASG_INVALID_EMP_ DFLT_NAME	Default employee %1 for assignment object %2 is not found in the employees table.	Use Siebel Tools to set the Default Employee parameter for the assignment object to a valid employee in the database.
ERR_ASG_INVALID_POSTN_ DFLT_NAME	Default position %1 for assignment object %2 is not found in the positions table.	Use Siebel Tools to set the Default Position parameter for the assignment object to a valid position in the database.
ERR_ASG_INVALID_STORE_ COL_NUM	Assignment criteria attribute %1 has an invalid store column.	Check the Store Column value for your assignment criteria attribute and make sure it lies between 1 and 4.
ERR_ASG_INVALID_WF_ LINK_COL	Assignment attribute column (%1) references invalid workflow component column (%2).	Check the Workflow Policy Component Column property of the assignment attribute column, and make sure it points to a valid and active workflow policy component column.
ERR_ASG_ITEM_ATTR_HAS_ NO_ATTR	Assignment Criteria %1, Assignment Criteria Attribute %2 has no attribute defined. Verify in Siebel Tools that the Assignment Criteria %1 has an assignment criteria attribute defined and active. Recompile the server repository file to apply changes made on assignment criteria configuration if necessary.	Not applicable or no further explanation should be needed.
ERR_ASG_ITEM_ATTR_HAS_ NO_ITEM	Item(%2) not found for item attribute (%1). Please make sure that the item(%2) is active.	Make sure that the Parent Assignment Item Type of the Assignment Criteria Attribute(%1), points to a valid and active assignment criteria.
ERR_ASG_ITEM_NOT_ FOUND	Assignment Criteria %1 has an invalid assignment attribute. Please check the assignment criteria configuration on Siebel Tools using the Validate tool, and note that it is a requirement to recompile the server SRF after adding or deleting assignment criteria records.	Not applicable or no further explanation should be needed.
ERR_ASG_LOADING_GROUP	Unable to load assignment rule %1 from the database. Please check the assignment rule definitions to make sure that all the required information is correct and press the Release button to recreate the rule cache data file.	Not applicable or no further explanation should be needed.
ERR_ASG_LOADING_OBJECT	Unable to load assignment object %1."	Check the configuration of the assignment object.
ERR_ASG_LOV_VALUE_NOT_ FOUND	No LOV value found for Type [%1], Value [%2].	Make sure expertise values for skills are valid, belonging to LOV type EXPERTISE_CD (defined through Application Administration screens).
ERR_ASG_MATCHASSIGN_ REPLY	Qualified and selected %3 rules, %5 organizations, and %4 people for %1 (%2).	This is just information.
ERR_ASG_MATCH_REPLY	Qualified %3 rules, %5 organizations, and %4 people for %1 (%2).	This is just information.
ERR_ASG_NO_OBJ_COL_FOUND	Assignment object %1 has no columns.	Not applicable or no further explanation should be needed.
ERR_ASG_NOT_EMP_POSTN	Employee or Position not specified for assignment object %1.	If person-based assignment, make sure that at least one of the four properties (Position Table, Position Primary Column, Employee Table, Employee Primary Column) for assignment object %1 has a valid non-null value. If organization-based assignment, make sure that at least one of the two properties (Org Table, Org Primary Column) for assignment object %1 has a valid non-null value.
ERR_ASG_NO_WF_COLS_ IN_ATTR	Assignment attribute %1 has no workflow columns.	Not applicable or no further explanation should be needed.
ERR_ASG_NO_WF_OBJECT	No workflow object available for assign object = %1.	Make sure that the Parent Workflow Object property of the Assignment Object % points to a valid workflow object.
ERR_ASG_OBJECT_NOT_FOUND	Assignment object %1 is not registered in the Siebel repository. Please make sure that %1 is a valid assignment object name and the value you input is identical to what you see in the application. Please review the Assignment Manager documentation for details on the required parameters before running an Assignment Manager task.	Not applicable or no further explanation should be needed.
ERR_ASG_PERSON_OBJECT_ NUM_ATTR_MISMATCH	Number of attributes do not match with assignment object for person object %1.	Not applicable or no further explanation should be needed.
ERR_ASG_PR_TBL_ROW_ NOT_FOUND	RowId [%1] in table [%2] not found.	Make sure that request submitted is for a valid Row Id in table (%2).
ERR_ASG_UPDATE_FAILED	Unable to update row %1 (%2).	Check the log file for database related error, and correct the error.
ERR_ASG_PARSING_VALUE	Unable to parse criteria value %1.	Not applicable or no further explanation should be needed.
ERR_ASGN_KEY_NO_MATCH	Assignment Key %1 does not match the Request Key.	Make sure that the AsgnKey parameter is set to the Row Id of one of the assignment groups mapped to the server.

Siebel Server is not coming up...What should we check?

1. Validate that the .srf file is not corrupt by testing the srf on a dedicated environment.
if the dedicated client is facing issues possibly 2 reasons must be there
a.srf file is corrupt
b.db itself is down
Take the necessary action

2. Stop siebel servers after executing ./siebenv.sh and command stop_server all

3. Check that no Siebel processes for the enterprise are still running.
Windows: Check Task Manager for any Siebel process for the enterprise still running.
Solaris: Execute ps -ef | grep [directory path] (eg. ps -ef | grep /app/siebel/siebsrvr).
ps -ef|grep sieb also finds all active siebel process
Ensure that all processes for that enterprise are killed.
use kill -9 pid to achieve the same

4. Delete any file that exists in directory %SIEBEL_ROOT%\sys with name like:
osdf.[SiebelEnterprise].[SiebelServer]
Where
[SiebelEnterprise] = The Siebel Enterprise name
[SiebelServer] = The Siebel Server name.

5. Delete any file that exists in directory %SIEBEL_ROOT%\admin with name like:
*.shm
dhm files are shared memory files. This file should be automatically deleted when the Siebel server is shut down, if it still exists when the Siebel server is down then it has been corrupted and not correctly removed.

6.Delete fdr and core files as these file eat up large amounts of memory.

7.Cleanup unwanted logarchive and log files so that fresh logs can be monitered and space can be freed up.

8.Try to restart server after executing ./siebenv.sh and command start_server all
Note- At this point if the server still does not restart, you need to check the enterprise log for the reason. The enterprise log is located in:
%SIEBEL_ROOT%\enterprises\[SiebelEnterprise]\[SiebelServer]\log
The enterprise log has name with format:
[SiebelEnterprise].[SiebelServer].log

9. If no enterprise logs are getting creted there are connectivity issues with the database:
i.e change of db password for SADMIN user
db server is down
(Come to this conclusion ony if you skipped the first step)
run odbcsql from siebsrvr/bin to check connectivity issues
odbcsql /u SADMIN /p SADMIN /s DSN Name

10. Any changes which lead to the corruption of siebns.dat will also result in the servers not coming up.
usually NameSrvr logs tell us connectivity related information and errors like key not found.Try reverting to an old working siebns.dat file.

11.If the environment is LDAP authenticated any changes in the LDAP trees can also affect the environment.please verify the same.

12.Check the SCBroker and SRBroker logs;you would get a hint.

13.Use netstat -an|grep 2320 for verifying that the gateway service port is listening.

14.Use netstat -an|grep 2321 for verifing that the SRBroker/SCBroker port is listening
So that is a long list.Thought there can be other reasons too; I have only mentioned those encountered by me.I will keep on updating when I find newer reasons.Till then stay tuned.

About the rulecache.dat file in Assignment Manager setup

The rule cache file contains the most recent copy of assignment rule, criteria, candidates, skills, and skill items information from the last time assignment rules were released. A cache file is recreated every time assignment rules are released or when skills have expired.

Depending on the mode in which you run Assignment Manager, the following cache files are used:

• rulecache.dat
  This file contains information about all active rules in the database. When Assignment Manager runs in default mode, this file is used by each of the three assignment operation modes (interactive, batch, and dynamic assignment).
• rulecache_SERVERNAME.dat
  This file (where SERVERNAME is the name of the Siebel Server) contains information about the rules in the rule groups assigned to a particular Siebel Server and is used when server key mappings are defined.
• batchrulecache_RULEGROUPID.dat
  When batch assignment runs in rule group mode, you can specify whether it uses the default mode cache file (rulecache.dat) or a separate cache file by way of the Independent Rule Group Cache parameter.
• If you set this parameter to FALSE, it uses the default mode cache file (see rulecache.dat previously described in this topic).
• If you set this parameter to TRUE, it creates a separate cache file, batchrulecache_RULEGROUPID.dat (where RULEGROUPID is the Assignment Key parameter you passed along with the request).
  There can be multiple cache files of this type, because you can use batch assignment in rule group mode for different rule groups. This rule group cache file is a smaller file, therefore providing better performance than the default mode cache file. Performance is better because the batchrulecache_RULEGROUPID.dat file only has information about some rules for some rule groups, while the rulecache.dat file has information about all active rules for all rule groups.

Hope this information was helpful.stay tuned

Generate Triggers using Siebel Client

To generate triggers using the GUI

1.             In the Siebel client, from the application-level menu, choose Navigate > Site Map > Administration - Server Management > Jobs.

2.             In the Jobs list, click New.

3.             From the Component/Job drop-down list, select Generate Triggers. This creates a new line entry but does not start the task.

4.             In the Job Parameters list, click New to modify parameter settings.

5.             Enter your Privileged User name and Privileged User password.

6.             In the Job Detail form applet, from the applet-level menu, select Start Job.

7.             To view changes to the state, refresh the screen by clicking Run Query(Alt+Enter) from the applet menu.

8.             Upon completion, the Status field contains either Success or Error. It is recommended that you view the log details.