Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-ICF (Application Component) Internet Communication Framework⤷
SHTTP (Package) Development Class for HTTP Communication
Basic Data
| Data Element | ICF_NODE |
| Short Description | ICF: GUID of ICF Service/Alias |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SYSUUID_25 | |
| Data Type | CHAR | Character String |
| Length | 25 | |
| Decimal Places | 0 | |
| Output Length | 25 | |
| Value Table |
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 | 0 | |
| Medium | 18 | ICF Node GUID |
| Long | 30 | GUID of ICF Service Node |
| Heading | 0 |
Documentation
Definition
Name of a service in the Internet Communication Framework
Use
In the ICF (Internet Communication Framework), each HTTP service is positioned in a tree structure so that there is a path to each HTTP service that runs through the parent nodes of this HTTP service. This access path corresponds, for the most part, to the URL used to address the HTTP service. Each service under a parent service must have a unique service name.
The name of a HTTP service is also used in the name of a BSP application. See also the documentation about creating an ICF service.
Dependencies
For more information about the ICF, refer to the SAP Library under the SAP Web Application Server - Web Applications (BC-MAS) - SAP Web Application Server - Internet Communication Framework.
For more information about BSP applications, refer to the SAP Library under the SAP Web Application Server - Web Applications (BC-MAS) - SAP Web Application
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 700 |
