3.1.4.64 GetLobSystemDataByLobSystem

The GetLobSystemDataByLobSystem operation retrieves Business Logic Modules<82> associated with the specified LobSystem.

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

 <wsdl:operation name="GetLobSystemDataByLobSystem" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
   <wsdl:input wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetLobSystemDataByLobSystem" message="tns:BusinessDataCatalogSharedService_GetLobSystemDataByLobSystem_InputMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:output wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetLobSystemDataByLobSystemResponse" message="tns:BusinessDataCatalogSharedService_GetLobSystemDataByLobSystem_OutputMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetLobSystemDataByLobSystemArgumentExceptionFault" name="ArgumentExceptionFault" message="tns:BusinessDataCatalogSharedService_GetLobSystemDataByLobSystem_ArgumentExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetLobSystemDataByLobSystemArgumentNullExceptionFault" name="ArgumentNullExceptionFault" message="tns:BusinessDataCatalogSharedService_GetLobSystemDataByLobSystem_ArgumentNullExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetLobSystemDataByLobSystemArgumentOutOfRangeExceptionFault" name="ArgumentOutOfRangeExceptionFault" message="tns:BusinessDataCatalogSharedService_GetLobSystemDataByLobSystem_ArgumentOutOfRangeExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetLobSystemDataByLobSystemBdcExceptionStateFault" name="BdcExceptionStateFault" message="tns:BusinessDataCatalogSharedService_GetLobSystemDataByLobSystem_BdcExceptionStateFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetLobSystemDataByLobSystemInvalidOperationExceptionFault" name="InvalidOperationExceptionFault" message="tns:BusinessDataCatalogSharedService_GetLobSystemDataByLobSystem_InvalidOperationExceptionFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
   <wsdl:fault wsaw:Action="http://www.microsoft.com/Office/2009/BusinessDataCatalog/BusinessDataCatalogSharedService/GetLobSystemDataByLobSystemMetadataExceptionStateFault" name="MetadataExceptionStateFault" message="tns:BusinessDataCatalogSharedService_GetLobSystemDataByLobSystem_MetadataExceptionStateFault_FaultMessage" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"/>
 </wsdl:operation>

The protocol client sends a BusinessDataCatalogSharedService_GetLobSystemDataByLobSystem_InputMessage request message, and the protocol server MUST respond with a BusinessDataCatalogSharedService_GetLobSystemDataByLobSystem_OutputMessage response message, unless any faults occur.

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.

Error complex type

Condition

AccessDeniedExceptionState (from namespace http://schemas.datacontract.org/2004/07/Microsoft.BusinessData.Infrastructure)

The security principal in whose context the protocol client is operating is not authorized to edit  the specified LobSystem, and the CameThroughRemoteAdminService header specified in section 3.1 is present in the SOAP request.

ArgumentOutOfRangeException (from namespace http://schemas.datacontract.org/2004/07/System)

The MetadataObjectId of the specified LobSystem is set to zero ("0").<83>

MetadataObjectNotFoundExceptionState (from namespace Microsoft.SharePoint.BusinessData)

The specified LobSystem does not exist.<84>