Administration Console Online Help

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
2. In the Administration Console, expand Services > Messaging and select JMS Modules.
3. In the JMS Modules table, click the name of JMS module in which to configure the foreign server resource.
4. On the module's Settings page, click the New button in the Summary of Resources table.
5. On the Create a New JMS System Module Resource page, use the Type drop-down to select Foreign Server.
6. Click Next.
7. In the resulting Foreign Servers table, click New.
8. On the Foreign Server Properties page, enter a name for the foreign server.

   Note: Once you create a foreign server, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

9. Click Next.
10. On the targeting page:
    1. In Subdeployments, select a subdeployment for the foreign server. If necessary, you can create a new subdeployment by clicking the Create a New Subdeployment button. A subdeployment is a mechanism by which JMS module resources (such as queues, topics, and connection factories) are grouped and targeted to a server resource (such as JMS servers, server instances, or cluster).

       When a SubDeployment is selected, its targeted JMS server, server, or cluster appear as selected in the Targets box.

    2. If you are not using subdeployments, in the Targets box, select the JMS server, server, or cluster on which to deploy the foreign server.

    You can also reconfigure deployment targets later if you wish. For more information about targeting foreign servers, refer to Configuration Options.

11. Click Finish.
12. To configure additional properties for the new foreign server, click it in the Summary of Resources table.
13. On the Configuration: General page:
    1. In JNDI Initial Context Factory, enter the name of the class that must be instantiated to access the JNDI provider. This class name depends on the provider and vendor that are being used.
    2. In JNDI Connection URL, enter the URL that WebLogic Server uses to contact the JNDI provider. The syntax of this URL depends on which JNDI provider is being used. For WebLogic JMS, leave this field blank if you are referencing WebLogic JMS objects within the same cluster.
    3. In JNDI Properties, specify any additional properties that must be set for the JNDI provider. These properties will be passed directly to the constructor for the JNDI provider's InitialContext class.

       Note: The JNDI Properties values may be a name=value list of properties, separated by commas.

    For more information about these fields, refer to Configuration Options.

14. Click Save.
15. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).