Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-STW (Application Component) Social Media ABAP Integration Library⤷
S_CLB_CUST (Package) Customizing of the Collaboration Platform Library
Basic Data
| Data Element | CLB_DEST_GW_HUB |
| Short Description | Collaboration: Destination of Gateway Hub |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RFCDEST | |
| Data Type | CHAR | Character String |
| Length | 32 | |
| Decimal Places | 0 | |
| Output Length | 32 | |
| Value Table | RFCDES |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | GW Dest. |
| Medium | 15 | Gateway Dest. |
| Long | 20 | Gateway Destination |
| Heading | 32 | Gateway Dest. |
Documentation
Definition
This field specifies the RFC destination of the SAP Gateway Hub system that is addressed in collaboration scenarios.
Use
You have to specify this destination if you actively use a collaboration scenario that requires a Gateway system, such as the OData Service Registry.
If the collaboration layer or SAIL component is located on the Gateway hub itself, you can leave the field empty.
Dependencies
The Gateway add-on Backend Event Publisher (BEP) also provides a Customizing as part of the implementation guide:
SAP NetWeaver > Gateway Service Enablement > Backend OData Channel > SAP NetWeaver Gateway Settings.
These Customizing settings allow the definition of multiple hub destinations. For collaboration scenarios, it is important to fix one of these destinations with an external service provider.
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 740 |
