SBL-DAT-00610: Access denied to invoke business service '%1' for search specification '%2'

Applies to:

Siebel System Software - Version: 7.7.1 SIA [18306] - Release: V7
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306] Pub Sect
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: IBM AIX 5100-03

This document was previously published as Siebel SR 38-1409242127.

Symptoms

In Siebel version 7.7, a data map has been created (based on a working Siebel 7.5.3 version mapping). 

One of the mappings invokes a custom business service using expression InvokeServiceMethod.  The following is inclued in a Source Expression in the EAI Data Mapper :-

InvokeServiceMethod("Custom Service", "GetUserAccountId", "loginName=" + [submitter], "Account Id")

When the mapper service ('EAI Data Transformation Engine') is executed, the following error is reported :-

SBL-DAT-00610: Access denied to invoke business service 'Custom Service' for search specification 'InvokeServiceMethod("Custom Service", "GetUserAccountId", "loginName=[submitter]", "Account Id")'

The same Business Service can be executed without error in the Business Service Simulator in the client.

Cause

Siebel system has made a security change from Siebel 7.5.3 to 7.7 that requires the explicit registration of the business service. In order to use the InvokeServiceMethod function in the Siebel dedicated client in version 7.7 (and above), the business service name that is called by the InvokeServiceMethod function has to be added as the "BusinessServiceQueryAccessList" parameter value under [Siebel] section in corresponding configuration file as follows:

[Siebel]
BusinessServiceQueryAccessList = BusSvc1,BusSvc2,...

In the customer case, the business service “Custom Service" has to be added under [Siebel] section and it should look as below:

[Siebel]
BusinessServiceQueryAccessList = Custom Service

Change Request Bug 12-NC2VUV has been logged to address this documentation enhancement request.

Alternatively, if the InvokeServiceMethod function is called from a server component, the business service name has to be specified as value for the “Business Service Query Access List” server component parameter.

For example, if the repeating component calls the Workflow Process Manager server component to execute a workflow process and the data mapping is called in the Workflow Process, the business service name has to be added as value of the “Business Service Query Access List” component parameter for the Workflow Process Manager server component. Then, the server component should be restarted to take effect after change the component parameter value.

Solution

After setting the BusinessServiceQueryAccessList parameter (in the [Siebel] section of the client cfg file, the error no longer occurred.

Applies to:

Siebel System Software - Version: 7.8.2.4 SIA [19224] and later   [Release: V7 and later ]
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2.4 [19224] HEB Fin Svcs
Database: IBM DB2 8.2
Application Server OS: IBM AIX 5L 5.2 ML6
Database Server OS: IBM AIX 5L 5.3

This document was previously published as Siebel SR 38-3418355193.

Symptoms

We are trying to set two (2) Business Services names at the 'Fins Heb' component parameter : Business Service Query Access List

We've set it value as follows:

ABC General Methods, ABC DM Functions

for some reason the second BS does not recognized when we invoking it from a Data Trans' Engine BS using a simple workflow.

At runtime, this resulted in the following error :-


ObjMgrQueryLog Warning 2 0 2007-08-06 14:07:23 (query.cpp (9393)) SBL-DAT-00610: Access denied to invoke business service 'BNP DM Functions' for search specification 'InvokeServiceMethod ("BNP DM Functions", "PersonalizationMethod", "Key1=a,Key2=2", "B")

Cause

The issue was caused by incorrect syntax. There should be no space after the comma.

Solution

After removing the space between the service names, InvokeServiceMethod worked as expected. Change request 12-NC2VUV has previously logged to provide documentation on this parameter.

References

BUG:12-NC2VUV - PLEASE ADD THE STEPS TO USE INVOKESERVICEMETHOD FUNCTION IN DATA MAPPING.
NOTE:538237.1 - InvokeServiceMethod in EAI Data Mapper Returns Error " SBL-DAT-00610: Access denied to invoke business service 'Custom Service' "

Applies to:

Siebel Server Sync - Microsoft Exchange Server - Version: 7.0.4 [14068] and later   [Release: V7 and later ]
Generic UNIX
Area(s):SSSE / Exchange Server Integration
Release(s):V7 (Enterprise)
Database(s):All Supported Databases
App Server OS(s):Windows 2003, Windows 2000
Latest release tested against:V7 (Enterprise)
Keywords:ssse, ConvertToSiebelFormat, inbound, sync, synchronization, Outlook, Exchange, InboundDispatcher

This document was previously published as Siebel Alert 1249.

Description

In Siebel Server Sync for Exchange (SSSE) 7.7.2.x and 7.8.2.x, inbound contact synchronization from Outlook to Siebel may fail with the following errors in the PIMSIEng_##.log:

 

PIMSIEngSvc PIMSIError 2 0 2006-02-07 18:54:15 (inboundsvc.cpp (822)) InboundDispatcher: Method call Failed, Current Function: ConvertToSiebelFormat Reason:Data Mapper Service Failed to Execute.Data message is not in EAI formatInput To Data Mapper:

 

PIMSIEngSvc PIMSIError 2 0 2006-02-07 18:54:15 (inboundsvc.cpp (723)) InboundDispatcher: User: TEST02, Error: Siebel Inbound Cannot processes the message.There has been an error converting the message to Siebel Format.Please ensure PIMSI EAI Data Maps are valid

 

ObjMgrBusServiceLog Error 1 0 2006-02-07 18:54:15 (service.cpp (666)) SBL-DAT-00610: Access denied to invoke business service '<?>' for search specification '<?>'

 

This error occurs because contact addresses are included in the inbound synchronization and need to be converted from Microsoft Exchange to Siebel format via the use of a business service for parsing. The component needs to reference the appropriate business service in order to complete the conversion.

 

Change Request Bug 12-HJQ1OT has been logged to address this product defect.

Likelihood of Occurrence

This error will appear in all initial installations of SSSE in 7.7.2.x and 7.8.2.x. This behavior does not apply to client side PIMSync implementations in any version.

Possible Symptoms

Inbound contact synchronization, including inserts and updates from Microsoft Exchange, will fail with the errors noted above.

Workaround or Resolution

1. On the SSSE Siebel Server machine, navigate to the siebsrvr\bin directory in a command prompt. Instantiate the environment variables by running the following batch file:

 

siebenv.bat

 

2. Log into the Siebel Server Manager:

 

srvrmgr /u SADMIN /p [PASSWORD] /g [GATEWAY_HOST] /e [ENTERPRISE_NAME] /s [SIEBEL_SERVER_LOGICAL_NAME]

 

For example, if your environment is as follows:

 

Gateway	MACHINE_A
Enterprise	ent78
Siebel Server	srvr78 on host MACHINE_B

 

Then the srvrmgr command will be as follows:

 

srvrmgr /u SADMIN /p SADMIN /g MACHINE_A /e ent78 /s srvr78

 

3. Once inside the srvrmgr prompt, enter the following command:

 

change param BusinessServiceQueryAccessList="SSSE Address Parser (eScript)" for comp PIMSIEng

 

4. Exit the server manager.

 

5. Restart the Siebel Service.

 

Change Request Bug 12-1EVJ8MY has been logged as a documentation enhancement request to update Siebel Bookshelf with this information.

References

BUG:12-1EVJ8MY - DOCUMENT PARAMETER BUSINESSSERVICEQUERYACCESSLIST="SSSE ADDRESS PARSER (ESCRIPT)" FOR COMP PIMSIENG
BUG:12-HJQ1OT - INBOUND SERVICE NOT CONVERTING THE INTERMEDIATE MESSAGE TO SIEBEL FORMAT CORRECTLY

Applies to:

Siebel System Software - Version: 7.7.2.6 [18372] - Release: V7
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2.6 [18372]
Database: Oracle 9.2.0.1
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM AIX 5L 5.2

This document was previously published as Siebel SR 38-3342643401.

Goal

Is their a way in the Siebel data mapper or data map editor to create a map that converts source integration component data to upper case in the destination integration component by using a case translation function in the source expression, or do we have to use custom mapping to achieve this ?

Solution

Data Mapping Using Data Map supports only a subset of Siebel Query Language Expressions that do not require context of a business component is supported by EAI Data Mapping Engine.

Siebel Query Language Expressions that are not supported: BCName(), Count(mvlink), IsPrimary(), Min (mvfield), Max(mvfield), ParentBCName(),
ParentFieldValue(field_name), Sum(mvfield), GetXAVal(), GetXAValAsNum(),
GetXAValAsInt(), GetXAValAsDate(), and XAIsClass().

No uppercase function exists for the Siebel Query Language Expression.

Please reference the complete list of Siebel Query Language Expressions on Bookshelf > Siebel Personalization Administration Guide > Siebel Query Language.

However the uppercase / data mapper requirement could be achieved by invoking a simple business service to uppercase the incoming string value when the EAI Data Mapping Engine BS is processed. The InvokeServiceMethod Siebel Query Language function is used to invoke the custom Business Service.

Development Steps:

1) Create a custom business service and simple script based on the toUpperCase() function to uppercase the incoming string.

2) Siebel system has made a security change on 7.7 /7.8 that require the explicit registration of the business service.

In order to use the InvokeServiceMethod function in Siebel dedicated client 7.7, the business service name that is called by the InvokeServiceMethod function has to be added as the “BusinessServiceQueryAccessList” parameter value under [Siebel] section in corresponding configuration file as follows:

[Siebel]
BusinessServiceQueryAccessList = BusSvc1,BusSvc2,...

If the InvokeServiceMethod function is called in Siebel Web client 7.7, the business service name has to be specified as value for the “Business Service Query Access List” server component parameter.

For additional information please reference :-

InvokeServiceMethod in EAI Data Mapper Returns Error " SBL-DAT-00610: Access denied to invoke business service 'Custom Service' " (Doc ID 538237.1)

3) To invoke the custom BS when the EAI Data Mapping Engine BS is executed the following expression needs to be included in on of the source expression of the Data Map used.

InvokeServiceMethod ("A TestDataMapper", "UpperCase", "InputStr='"+[Integration Field Name]+"'", "OutputStr")

The InvokeServiceMethod returns the value of the return property from the returnProperty set of the specified business service after invoking the method with the context.  For example :-

InvokeServiceMethod ("BusServ", "PersonalizationMethod", "Key1=a,Key2=2", "ReturnProperty") invokes the business service method PersonalizationMethod in business service BusServ, and passes it the context Key1=a,Key2=2 and returns the value set by the business service in the property ReturnProperty.