Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
CA-EPT-RCC (Application Component) Remote Control and Communication Framework⤷
RCC_CUST (Package) RCCF: Customizing
IMG Activity
| ID | RCCC_ENG_DEST | Edit Destinations |
| Transaction Code | S_BSD_38000013 | (empty) |
| Created on | 20080408 | |
| Customizing Attributes | RCCC_ENG_DEST | Edit Destinations |
| Customizing Activity | RCCC_ENG_DEST | Edit Destinations |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | RCCC_ENG_DEST |
Use
In this IMG activity, you process the destinations for external engines in the Remote Control and Communication Framework (RCCF).
A destination is not necessarily just a different engine server. Several destinations can reference the same engine server via their communication links.
In general, destinations are used to limit the number of runs per engine server and distribute them among several servers. The RCCF does not carry out true load balancing. If the priorities are equal and there is the same number of free remaining slots, it merely distributes the runs evenly among the available destinations. Distribution takes place only among the destinations of the relevant application in each case.
If several destinations reference the same server (also different applications), the RCCF nevertheless takes only the destinations that are assigned to the requested application into account when carrying out the load balancing. It does not consider either the destinations of the other applications or the underlying engine servers themselves in each case.
The RCCF does not take destinations whose status you have not set to active into account for engine runs.
In selecting the destinations for an engine run, the RCCF also takes priorities into account. The lower the value, the higher the priority. The priority with the value 1 thus represents the highest priority. Load balancing is supported for destinations of the same priority only.
You must also choose the communication type and its communication link. We recommend always using RFC in the standard system.
If you choose GRID as communication type, this necessitates a correspondingly installed GRID on the engine servers. Such an installation can only be effected via the SCM Expert Services and is also supplied only on the basis of a customer project. For further information on SCM Expert Services, refer to the SAP Note 689101.
Requirements
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | RCCC_ENG_DEST | 0 | BSD0000021 | Remote Control and Communication Framework |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| RCCC_ENG_DEST | S - Table (with text table) | SM30 |
History
| Last changed by/on | SAP | 20080408 |
| SAP Release Created in | 701 |
