-->
edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Configure JMS template

Configure JMS template subdeployments for error destinations


A destination's specified error destination must be targeted to the same JMS server as the destination itself, which makes it difficult for multiple destinations to use a template's specified error destination since destinations can targeted to different JMS servers. However, you can define template subdeployments for error destinations so that any number of destination subdeployments (groups of queue or topics) will use only the error destinations associated with those destination subdeployments, since the destination subdeployment names will match the template's subdeployment names.

For example, if a hundred queues share the same template, with fifty in a queue subdeployment targeted to one JMS server and the other fifty in another queue subdeployment targeted to another JMS server, then you can configure two separate template subdeployments: one with the same subdeployment name used by the first fifty queues and the other with the same subdeployment name used by the second fifty queues. This way, each template subdeployment can point to a different error queue, with the destinations in the first subdeployment using the first error queue, and the destinations in the second subdeployment using the second error queue.

To configure error destination subdeployments for a JMS template:

  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, navigate to the template resource that you want to configure:

  3. Click the Configuration > Subdeployments tab.

  4. On the Subdeployments page:

    1. In SubDeployment Name, enter a SubDeployment name for an error destination that matches a subdeployment name for destinations configured to use this template.

    2. In Error Destination, select a pre-configured error destination associated with a destination subdeployment configured to use this template.

    For more information about these fields, see Configuration Options.

  5. Save your changes:

  6. 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).
} } (document.images){ dcs_imgarray[dcs_ptr] = new Image; dcs_imgarray[dcs_ptr].src = dcs_src; WT[myMeta.name.substring(3)]=myMeta.content; } if DCSext[myMeta.name.substring(7)]=myMeta.content; } } } } for (N in DCS){P+=A( N, DCS[N]);} for (N in WT){P+=A( "WT."+N, WT[N]);} for (N in DCSext){P+=A( N, DCSext[N]);} //} aCrumb=aCookie[i].split("="); if (crumb==aCrumb[0]){ return aCrumb[1]; } } return null; } i=0;i