In prior releases, no restrictions were placed on the naming of the entries in the NATIVE and
FOREIGN sections of the
GWICONFIG file. Beginning with the eLink TCP 3.2, each entry in the
NATIVE section of the
GWICONFIG files must have a corresponding entry with an identical name in the
DM_LOCAL_DOMAINS of the
DMCONFIG file. Each entry in the
FOREIGN section of the
GWICONFIG file must have a corresponding entry with an identical name in the
DM_REMOTE_DOMAINS section of the
DMCONFIG file.
Because service routing is now determined by the contents of the DMCONFIG file, services in the
LOCAL_SERVICES section of the
GWICONFIG file no longer need to be tied to
NATIVE entries in that file. As a result, the
NATIVE keyword is no longer valid for entries in the
LOCAL_SERVICES section. Services are now tied to local domains in the
DMCONFIG file, by specifying the corresponding
LDOM in the service entry in the
DM_LOCAL_SERVICES section, or by applying default service assignment rules.
For the same reasons, services in the REMOTE_SERVICES section of the
GWICONFIG file no longer need to be tied to
FOREIGN entries in that file. As a result, the
FOREIGN keyword is no longer valid for entries in the
REMOTE_SERVICES section. Services are now tied to remote domains in the
DMCONFIG file, by specifying the corresponding
RDOM in the service entry in the
DM_REMOTE_SERVICES section, or by using a routing statement to specify data-dependent routing, or by applying default service assignment rules. For information about configuring data-dependent routing using the
ROUTING command, refer to the Oracle Tuxedo documentation.
