Search This Blog

SBL-SVC-00251

Applies to:

Siebel System Software - Version: 8.0.0.7 SIA [20426] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms


On : 8.0.0.x SIA version, ADM - Appication Deployment Manager

When creating a new project using the ADM Data Type "ADM Search Parent Category", by pressing 'Enable' and get error SBL-SVC-00251: A configuration error occurred. The Data Type <?> is using a missing or invalid Content Object. Please contact your Application Administrator.


ERROR
-----------------------
When pressing 'Enable' and get error SBL-SVC-00251: A configuration error occurred. The Data Type <?> is using a missing or invalid Content Object. Please contact your Application Administrator.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Go to Application Deployment Manager -> Deployment Projects;
2. Create a new record and set the name = Test, description = Test and export flag = true;

3. In the child Applet hit 'New' to create a new record and select from the Data Type Name pick list the "ADM Search Parent Category";
4. In the parent Applet hit 'Enable'.

5. Go to the Application Deployment Manager -> "Deployment Sessions" applet, create a new record and select the record that you have just created by step 2. (This should bring the record in the UI)

6. Now, hit the 'Deploy' button, set the location where you would like to export the ADM file, like C:\temp.
-> Check that now the C:\temp directory has two files: xx_ADM_Search_Parent_Category.xml and XX_ADM_Search_Parent_Category_des.xml

7. In the same Manager -> "Deployment Sessions" applet, create a new record and click Menu -> Deploy from File and add the location where you have exported the files from step 6.

The file path should point to the following:
--
C:\temp\ xx_ADM_Search_Parent_Category.xml
--

8. Hit the 'Import' button and the following error is shown:
**
Multiple matches found for instance of integration component 'Search Index Category BC' using search specification [Name] = "Catalog Category" in the business component 'Search Index Category BC', based on user key 'UserKey' (SBL-EAI-04390)
**


Cause


Cause Determination
--

Change Request/Bug: 10588612 - "ADM Search Parent Category Data Type" fails during import.

In the Integration Component (Search Category Available Fields IO) “Search Index Category BC”, only the field “Name” forms its UserKey. For the query based on search specification [Name] = "Catalog Category”, during ADM import there are multiple records in the table S_SRCH_CTGRY with the matching value. Therefore the error occurs.

The User key is not robust enough to identify records uniquely and so its not possible to use the "ADM Search Parent Category Data Type" functionality.



Solution


As a part of the fix provided by Change Request/Bug: 10588612 - "ADM Search Parent Category Data Type", the following changes are required:

1. Open the Siebel Tools and look for the following the IO's (Integration Objects):

Search Category Available Fields IO
Search Category Parent Category IO

2. Note that both have the IC "Search Index Category BC".
3. Select this IC (Integration Component) and drill down on the Integration Component Key to display the User key attribute.
4. Drill down on the Integration Component Key to see the fields from the BC "Search Index Category BC" that form part of the User key.
5. Currently, 'Name' is the field used, but search specification based on "Name" retrieves more than one record and hence the error.
--
*Multiple matches found for instance of integration component 'Search Index Category BC' using search specification [Name] = "Catalog Category" in the business component 'Search Index Category BC', based on user key 'User Key' (SBL-EAI-04390)*
--

6 - [FIX] -  In order to fix it, add "Connector Name"(available field) field also to the User Key for the BC 'Search Index Category BC', in both the IO's and then compile the changes to the srf and restart the Siebel Server and the application. Then proceed with the import and it should work.



Applies to:

Siebel CRM Call Center - Version: 8.0.0.2 [20412] - Release: V8

Information in this document applies to any platform.

Goal


Why does the following error message occure and what can be done to avoid it:

SBL-SVC-00251 A configuration error occurred. The Data Type %1 is using a missing or invalid Content Object. Please contact your Application Administrator.

Solution


The problem is that the content object either doesn't exist or is obsolete in the repository.

Firstly ensure that the right SRF file is used. The server component ADMBatchProc need to use an SRF file that contains the definitions of the Content Object.
If this is not the cause the data type has to be reconfigured to use a content object that exists.




Applies to:

Siebel CRM - Version: 8.0.0.3 SIA [20416] to 8.1 SIA [21039] - Release: V8 to V8
Information in this document applies to any platform.

Goal


Is it possible to import VALIDATION MESSAGES (DVM) via ADM?

In a scenario where it is necessary to import Rule Sets and/or Validation Messages from source to target environment, can they be imported using ADM instead of inserting them manually?


Solution

There is no vanilla ADM data type for Data Validation Manager; customers who created their own could not deploy successfully using ADM.
Customizations of ADM Data Types requires changes at IO and IC levels, which might be complex to be implemented. Therefore, here goes some possible customizations ideas:

- Configure integration objects, content objects in Siebel Tools for creating custom ADM data types for migration.
- Create new data type in adm_registry.xml file, which is used when using the method of Management Server, Management Agent, and ADM components to deploy. Possibly need to create a business service needed for Backup, Activate, RestoreActivate, etc., methods, whatever methods needed.

So far, several customers attempted, all failed at various stages and errors.

1. "SBL-SVC-00251: A configuration error occurred. The Data Type <?> is using a missing or invalid Content Object."

It happens because there are information on how new data type should be created in adm_registry.xml. It may need a custom business service to backup, activate, RestoreActivate, etc.

2. EAISiebAdpt EAISiebAdptErr 1 0000000a49413220:0 2008-12-11 16:43:11 [0] Cannot perform 'NewRecord' on the business component 'FINS Validation Rule'(SBL-EAI-04421) (IDS_WRN_EAI_SA_DML)

This error occurs when migrating Rule Sets to target environment, even though customer claimed Validation Messages can be migrated successfully via ADM using File Operation method, but not Rule Sets.

The Enhancement Request 10566034 was created to provide a vanilla ADM data type for Data Validation Manager.  The enhancement was submitted to Engineering; however, the enhanced feature request was rejected.
 

No comments:

Post a Comment