Configuring Virtual Hosts for RFC

Procedure

The Unified Connectivity for RFC introduces a new type of virtual host (VH). Until now, the concept of virtual host was restricted to HTTP and SMTP communication.

The new virtual hosts for RFC make it possible to split a "physical" port into multiple virtual channels for RFC communication too and configure it accordingly.

Note For security reasons, it may be necessary to run some RFC communications using SNC (Secure Network Connection) only. To do this, you can use a dedicated virtual host (Secure VH). For more details, see More Information.

Proceed as follows to configure a virtual host for RFC:

Choose transaction UCONCONF (UCON configuration) and select Virtual Host.
Choose Execute.
Double-click the required virtual host to display the detail data on the right side of the screen.

Note
Currently, only DEFAULT_HOST is available.
Choose Change to modify the configuration of the virtual host.

Note the following points when configuring a virtual host for RFC:

There should be a DEFAULT_HOST in every system.
A virtual host for RFC should cover all servers. If you do not enter all servers, you see a warning when the configuration is checked.

Note
The virtual host is client-specific.
You make your entries under Configuration Data in the same way as in transaction SM59 (for editing RFC destinations): A host address is converted automatically to a host name if you choose the option Host Name and to an IP address if you choose the option IP Address.
If you have a system with a dynamic IP address, you should select Host Name. The IP address is then resolved later at runtime.

Note
You can also enter the placeholder "*" for all fields. This means that this virtual host is used to address all servers (value "*" for Host Name) across all ports (value "*" for Port) and all protocols (values"*" for SNC).