Generating the SourceSystems.config file

The IBM® InfoSphere® DataStage® server generates the configuration file named SourceSystems.config whenever you save changes to the list of InfoSphere DataStage source systems on a InfoSphere DataStage client machine. This file tells the RFC Server Manager which RFC Servers should run with what configuration information. For an example of this file, see Example of the SourceSystems.config file.

Periodically, the RFC Server Manager inspects the content of this file and compares it to the in-memory list of the RFC Servers currently running. The actions taken by the RFC Server Manager depend on the content of this file as follows:

• New Source Systems. If new Source Systems are listed in the catalog file, the RFC Server Manager launches a new RFC Server instance for each. It configures these according to the Source System that they represent.
• No Corresponding Source System. If RFC Servers that are already running no longer have a corresponding Source System listed in the catalog file, the RFC Server Manager shuts down those RFC Servers. An RFC Server always completes any data loading that is in progress before termination.
• Changed Properties. If the properties of a Source System change, the RFC Server Manager shuts down the corresponding RFC Server and restarts it with the new configuration information.

An RFC Server establishes a connection with a specific SAP BW host machine at the time of invocation. This connection is maintained until the RFC Server Manager determines that the SAP BW host machine is no longer available. The Server Manager attempts to reestablish the connection for one minute. If unsuccessful, the Server Manager disables the Server. Once the SAP BW system is available, the SAP Administrator can be used to re-enable the RFC Server.