Tuesday, January 17, 2012

Weblogic 10.3.5: Configure uniform distributed queues on Weblogic Cluster

Create uniform distributed queues in a system module

When configuring uniform distributed queues, WebLogic Server uniformly creates the necessary members on the JMS servers to which a JMS module is targeted. This ensures the consistent configuration of all distributed destination parameters, particularly in regards to weighting, security, persistence, paging, and quotas.
The legacy weighted distributed queue feature is still available for users who prefer to manually fine-tune distributed queue members. However, Oracle strongly recommends configuring uniform distributed queues to ensure the consistent configuration and deployment of queue members across a cluster.
To create a distributed queue:
  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit
  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 queue 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, select Distributed Queue from the list of JMS resources, and then click Next.
  6. On the Distributed Queue Properties page, define the uniform distributed queue's basic properties:
    1. In Name, enter a name for the uniform distributed queue. Once you create a uniform distributed queue, you cannot rename it. Instead, you must delete it and create another one that uses the new name.
    2. In JNDI Name, enter the JNDI name used to look up the uniform distributed queue within the JNDI namespace. Applications use the JNDI Name to look up the distributed queue. If you do not specify a JNDI name for the distributed queue, it will not be available for JNDI lookup even after it has been targeted to a server resource. Therefore, you will only be able to access the distributed queue using the javax.jms.queueSession.createqueue() API or in an application-scoped context.
    3. In Destination Type,specify how members of this uniform distributed queue are created. Oracle recommends using the default setting of Uniform.
    4. Optionally, in Template, specify the template to use when creating this uniform distributed queue. Templates provide an efficient means of defining multiple destinations with similar configuration values.
  7. Click Next to proceed to the targeting page or click Finish to create the uniform distributed queue.
    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 uniform distributed queue.
    Caution: If you click Finish at this point, the uniform distributed queue will be created but without any targeting information. As a result, the uniform distributed queue will not be deployed and thus will not be available to applications until you manually select a subdeployment target.
  8. For basic default targeting, accept the default targets presented in the Targets box and then click Finish. The default targets are based on the parent JMS system module targets. Upon clicking Finish, the configured uniform distributed queue 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 uniform distributed queue's Configuration: General page.
  9. For advanced targeting, click Advanced Targeting, which allows you to select an existing subdeployment or to create a new one. A subdeployment is a mechanism by which JMS module resources (such as stand-alone destinations, uniform distributed destinations, and connection factories) are grouped and targeted to server resources (such as JMS servers, server instance(s), or cluster).
    • To select an existing subdeployment for the uniform distributed queue, select one from the Subdeployments drop-down. When a valid subdeployment is selected, its targeted JMS server(s), server(s), or cluster appear as selected in the Targets box. (A subdeployment with stand-alone destinations can only be targeted to a single JMS server.) Click Finish to add the uniform distributed queue to the selected subdeployment.
    • To create a new subdeployment for the uniform distributed queue, click the Create a new Subdeployment button. On the Subdeployment Properties page, enter a name for the subdeployment, and then click OK. On the ensuing subdeployment targeting page, select a JMS server(s), server instance(s), or cluster in the Targets box. (A subdeployment with stand-alone destinations can only be targeted to a single JMS server.) Click Finish to add the uniform distributed queue to the new subdeployment.
    Upon clicking Finish, the configured uniform distributed queue 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.
  10. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.








Distributed queue gets created as follows

No comments:

Post a Comment

SOA Cloud 12c GIT Repository

When a project is created, you can choose to initialize the project with one project Git repository for the project. A Maven repository is a...