A Foreign Server represents a JNDI provider that is outside WebLogic server. It contains information that allows a local WebLogic Server instance to reach a remote JNDI provider, thereby allowing for a number of foreign connection factory and destination objects to be defined on one JNDI directory.
Once you create a foreign server, you cannot rename it. Instead, you must delete it and create another one that uses the new name.
Caution: If you click Finish at this point, the foreign server will be created but without any targeting information. As a result, the foreign server will not be deployed and thus will not be available to applications until you manually select a subdeployment target, as described in Specify a subdeployment for foreign servers.
On the targeting page, you can either simply accept the parent JMS system module's default targets or proceed to an advanced targeting page where you can use the subdeployment mechanism for targeting this foreign server.
Upon clicking Finish, the configured foreign server is added to the module's Summary of Resources table, which displays its default targets. The default targeting will also be reflected by the Default Targeting Enabled checkbox on the foreign server's Configuration: General page.
Upon clicking Finish, the configured foreign server is added to the module's Summary of Resources table, which displays the user-defined subdeployment name and its targets. You can also reconfigure subdeployment targets later if you wish. For more information about managing subdeployments, refer to Configure subdeployments in JMS system modules.
For more information about these fields, refer to Configuration Options.
After you finish
Continue by configuring foreign connection factory and foreign destination objects. You can configure one or more foreign connection factories and foreign destinations (queues or topics) for each foreign server. For more information, see: