OTN Home > Oracle WebLogic Server 10.3.4.0 Documentation > Administration Console Online Help > Create a quota for destinations in a system module

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Create a quota for destinations in a system module


JMS quotas are used to control the allotment of system resources available to destinations. For example, you can specify the number of bytes or messages that a destination is allowed to store, or specify whether the quota can be shared be all destinations that refer to it.

To create a JMS quota:

  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 you want to configure the quota 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 Quota from the list of JMS resources.
  6. Click Next.
  7. On the JMS Quota Properties page:
    1. In Name, enter a name for the quota.
    2. In Bytes Maximum, enter the total number of bytes that can be stored in a destination that uses this quota.
    3. In Messages Maximum, enter the total number of messages that can be stored in a destination that uses this quota.
    4. In Policy, select the delivery policy to determine whether to allow smaller message send requests to be satisfied before larger ones when a destination has exceeded its message quota. The default FIFO (first in, first out) policy blocks subsequent newer sender requests until there is enough space for the first request in line, or denies the newer requests with a quota exception if the newer requests time out. The Preemptive policy allows newer smaller send requests to preempt previous larger requests when there is sufficient space for smaller messages on the destination, but not sufficient space for the older larger requests.
    5. In Shared, specify whether this quota is shared by destinations that refer to it.

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

    For more information about these fields see Configuration Options.

  8. Click OK.
  9. 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).

Back to Top