RFC Basic Scenario Process

Use

On the basis of specially prepared RFC statistics records, an administrator decides which remote-enabled function modules (RFMs) are to be exposed to the outside and assigns them to a Default Communication Assembly that is provided by the framework together with the default configuration and default host. Only these RFMs in the default CA are then able to be reached from the outside, outside access is blocked for all the other RFMs: They can no longer be accessed from outside the system but can still be called for system-internal scenarios such as load balancing and asynchronous scenarios.

Process

Logging Phase

To achieve this protection, you must first find out which RFMs must be reachable from the outside in the affected system.

For this you persist the RFC calls with the UCON Framework in the relevant server system using a freely-definable time period in the logging phase. This happens without affecting performance by the framework saving the intended part of the statistics records collected by the system.

After the selected time period has expired, it is possible to assign all RFMs called from the outside to the default CA or to assign all RFMs that are to be exposed by default CA individually. However, it is possible to assign additional RFMs to the default CA or to remove an assignment.

Evaluation Phase

After the logging phase has expired, an evaluation or simulation phase follows. The duration of this phase can be selected individually. Here you can check without risks if you need to expose more RFMs for the business scenarios running in the system than those that are already in the default CA.

In this evaluation phase there are no consequences if calling an RFM does not pass the runtime checks of Unified Connectivity. In this way you can find out which RFMs you still need to assign to the default CA without an RFM with errors possibly blocking production scenarios.

Production Phase

If the security that all required RFMs are in the default CA exists after the logging and evaluation phase, the UCON runtime checks can be activated in a third phase (final or production phase). RFC server security scenario protection exists from this point: Only the RFMs in the default CA are still reachable from the outside at runtime. If an RFM (that is not in the default CA) is called from the outside, a runtime error is created with corresponding error message and error logging in the system log.