Show TOC

Background documentationCommunication Components Locate this document in the navigation structure

 

The following three types of communication components are available: Business system, business component, and integration process component. You use different Web Services depending on your type.

The following elements are not dependent on the type.

WSDL Description

Element

Description

CommunicationComponentID

Specifies the object key for a communication component.

The object key of a communication component consists of a party name (PartyID) and the name of the communication component (ComponentID).

Note Note

Note that communication components must never have the same object key, even if they are of different types. Otherwise conflicts can occur when creating and changing these objects.

End of the note.
Business System

The Web Service for a communication component of type business system is described by the external definition BusinessSystemService.

The external definition contains structure elements of the following table.

Note that a business system in the Integration Directory represents an object of the same name in the System Landscape Directory (SLD). Many of the attributes of a business system (communication component) are defined in the business system in the SLD and cannot be changed in the Integration Directory. Therefore, therefore a difference is made between read and write access.

WSDL Description

Element

Description

BusinessSystemRestricted

Defines a business system with all attributes for write access.

  • MasterLanguage, AdministrativeData, and Description

    For more information, see: Cross-Object-Type Elements

  • BusinessSystemID: Object key of the Business System; based on the type CommunicationComponentID.

  • AdditionalIdentifier: Adapter-specific identifiers for the business system

    You can only specify additional identifiers for the Marketplace adapter (DDID) for a business system. Adapter-specific identifiers for the RFC and IDoc adapters are transferred from the SLD and cannot be changed in the Integration Directory.

    That is why the value DocDestinationID is set for the element schemeld. For the elementvalue you can specify a string with a maximum length of 36 characters.

  • AssignedUser: Assigned (service) user to whom access to the runtime environment is to be restricted.

BusinessSystem

Defines a business system with all attributes for read access.

Contains the same elements as for BusinessSystemRestricted, plus the following additional element:

  • IsThirdParty: Identifies whether the business system is an SAP or a non-SAP component.

  • AdditionalIdentifier: Shows other alternative identifiers from the SLD.

Business Component

The Web Service for a business component is described by the external definition BusinessComponentService.

The external definition contains structure elements of the following table.

WSDL Description

Element

Description

BusinessComponent

Defines the business component with all attributes.

  • MasterLanguage, AdministrativeData, and Description; more information: Cross-Object-Type Elements

  • BusinessComponentID: Object key; based on the type CommunicationComponentID.

  • InboundInterface: List of inbound interfaces for this business component; based on the type DesignObjectID.

  • OutboundInterface: List of outbound interfaces for this business component; based on the type DesignObjectID.

  • AdditionalIdentifier: Adapter-specific identifiers for the communication component; based on the type CommunicationComponentAdditionalIdentifier.

    In addition to a DDID for the Marketplace adapter (see business system), you can enter identifiers in the following way:

    • Logical System: schemeID = LogicalSystem; value has a maximum length of 10

    • TechnicalSystem: schemeID = TechnicalSystem; value is in the form <systemID> or <systemID>#<client>, where <systemId> can have a maximum of 8 characters and <client> a maximum of 3.

  • IsThirdParty: Identifies whether the business component is an SAP or a non-SAP component.

  • AssignedUser: Assigned (service) user to whom access to the runtime environment is to be restricted.

Integration Process Component

The Web Service for an Integration Process component is described by the external definition IntegrationProcessService.

The external definition contains structure elements of the following table.

WSDL Description

Element

Description

IntegrationProcess

Defines the integration process component with all attributes.

  • MasterLanguage, AdministrativeData, and Description; more information: Cross-Object-Type Elements

  • IntegrationProcessID: Object key; based on the type CommunicationComponentID.

  • RepositoryIntegrationProcess: Reference to Integration Process in ES Repository

    Based on the type DesignObjectID.

  • AdditionalIdentifier: Adapter-specific identifiers for the communication component; based on the type CommunicationComponentAdditionalIdentifier.

    You can enter the same types of identifiers as with a business component.