Activating asynchronous remote queue definitions

The queue manager can activate its asynchronous remote queue definitions and home server queues at startup time. In the Java™ code base, activating asynchronous remote queue definitions results in an attempt to transmit any messages they contain, while activating home server queues results in an attempt to get any messages that are waiting on their assigned store-and-forward queue. The activateQueues() rule allows this behavior to be configured.

The default rule just returns true.
public boolean activateQueues()    {
    return true; /* activate queues on queue manager start-up */
}

/*As with other rules examples above,
    a check can be made to see if the current */
/* time is inside the cheap-rate transmission period.
    This information can then */
/* be used to determine whether queues should be activated or not.

public boolean activateQueues()    {
    if ( timeToTransmit() )    {
        return true;
    }
    else    {
        return false;
    }
}

If activateQueues() returns false, the remote queue definitions are only activated when a message is put onto them. Home server queues can be activated by calling the queue manager's triggerTransmission() method.

In the C code base, activation of home server queues and asynchronous queues does not result in any attempts to transmit or pull down pending messages. Only explicit calls to the queue manager's triggerTransmission() function have this result. There is no implementation of an activateQueues rule in the C code base. Activation of queues occurs at queue manager startup.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.