3.1.4.82 GetSystemUtilityTypeNameForLobSystem

This operation is used to retrieve the implementation-specific identifier of the module that executes operations in the line-of-business (LOB) system corresponding to the specified LobSystem.

The following is the WSDL port type specification of the GetSystemUtilityTypeNameForLobSystem WSDL operation.

 <wsdl:operation name="GetSystemUtilityTypeNameForLobSystem" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
   <wsdl:input wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetSystemUtilityTypeNameForLobSystem" message="tns:BusinessDataCatalogSharedService_GetSystemUtilityTypeNameForLobSystem_InputMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:output wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetSystemUtilityTypeNameForLobSystemResponse" message="tns:BusinessDataCatalogSharedService_GetSystemUtilityTypeNameForLobSystem_OutputMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetSystemUtilityTypeNameForLobSystemArgumentExceptionFault" name="ArgumentExceptionFault" message="tns:BusinessDataCatalogSharedService_GetSystemUtilityTypeNameForLobSystem_ArgumentExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetSystemUtilityTypeNameForLobSystemArgumentNullExceptionFault" name="ArgumentNullExceptionFault" message="tns:BusinessDataCatalogSharedService_GetSystemUtilityTypeNameForLobSystem_ArgumentNullExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetSystemUtilityTypeNameForLobSystemArgumentOutOfRangeExceptionFault" name="ArgumentOutOfRangeExceptionFault" message="tns:BusinessDataCatalogSharedService_GetSystemUtilityTypeNameForLobSystem_ArgumentOutOfRangeExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetSystemUtilityTypeNameForLobSystemBdcExceptionStateFault" name="BdcExceptionStateFault" message="tns:BusinessDataCatalogSharedService_GetSystemUtilityTypeNameForLobSystem_BdcExceptionStateFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetSystemUtilityTypeNameForLobSystemInvalidOperationExceptionFault" name="InvalidOperationExceptionFault" message="tns:BusinessDataCatalogSharedService_GetSystemUtilityTypeNameForLobSystem_InvalidOperationExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetSystemUtilityTypeNameForLobSystemMetadataExceptionStateFault" name="MetadataExceptionStateFault" message="tns:BusinessDataCatalogSharedService_GetSystemUtilityTypeNameForLobSystem_MetadataExceptionStateFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
 </wsdl:operation>

The protocol client sends a BusinessDataCatalogSharedService_GetSystemUtilityTypeNameForLobSystem_InputMessage request message, and the protocol server MUST respond with a BusinessDataCatalogSharedService_GetSystemUtilityTypeNameForLobSystem_OutputMessage response message, unless any one of the conditions in the following table is met.

If any one of the conditions in the following table is met, the protocol server MUST instead respond  with a SOAP fault containing the corresponding error complex type, serialized as specified in section 2.2.4. If more than one error condition is encountered, the protocol server MUST respond with exactly one error complex type, determined in an implementation-specific manner.