Progress
AppBuilder
Developer’s Guide


Configuring a SmartConsumer Instance

There are only a limited number of instance properties you need configure. Follow these steps:

  1. Begin by clicking the instance’s menu button and choosing Instance Properties. The instance-properties dialog box opens (all fields shown as enabled for illustration):
  2. Change the default values that do not meet your needs:
    • Domain — Defaults to Publish-and-Subscribe. Setting this value to Point-to-Point creates a single copy of the message. Although a number of entities might have access to the message, the first one that reads the message deletes it from the pipeline. With the Publish-and-Subscribe mechanism, all subscribing entities can read the message. This allows implementation of a form of multicasting.
    • The Domain value is not modifiable at run time.

    • JMS Partition — Select a Partition from those listed. If there are no JMS Partitions listed, you can define as many as you like using the Service Parameter Maintenance Tool available on the PRO*Tools toolbar. For information about how to use that tool, see the online help.
    • Ping Interval — Defaults to 0 (pinging off). Setting this field to some integer value in seconds causes the connection to the SonicMQ broker to be tested at that rate for the duration of the JMS session. It is good practice not to ping frequently, since pinging decreases system performance.
    • Log File — Defaults to empty. Set this field to the pathname of the error-log file that will be used when running in batch mode.
    • Shutdown — Defaults to empty. Set this field to the identifier for the Topic (Publish-and-Subscribe) or Queue (Point-to-Point) to be used for shutting down this SmartConsumer instance when running in batch mode. Sending any message to this destination causes this SmartConsumer object to begin the shutdown process.
    • JMS User — Set this field to identify the user of the JMS Broker connection.
    • JMS Password — Set this field to be the password that corresponds to the JMS User identifier.
    • JMS Client ID — Set this field to a value unique to this client. This field is used to resolve ambiguities in cases where multiple clients might be using the same subscription and user names.
    • NOTE: You can supply the User, Password, and Client ID values at design time if you know them. Otherwise, check the Prompt-for-JMS-Login box and the object will prompt the user for them at run time.

    • Prompt for JMS Login — Defaults to cleared. Setting this check box causes the object to prompt the user for login.
    • Destination — Set this field to create/update an identifier for the destination Topic/Queue.
    • Message Selector — If you wish to filter incoming messages according to values in header fields or properties, enter the expression here. The SmartConsumer object will perform the test on incoming messages and discard from the inbound queue/topic any messages that fail the test. Example: company_name = "ABC" AND priority < 4. Any message received from company ABC with a priority of 3 or less will be discarded without notice. The syntax is a subset of the syntax defined in SQL-92.
    • Durable Subscription — Defaults to cleared. Enabled only when Domain is Publish-and-Subscribe. Set this check box to preserve the current subscription across JMS sessions.
    • Subscription Name — Enabled only for Durable Subscriptions. Set this field to create/update a subscription name.
    • Unsubscribe on Session Close — Defaults to cleared. Enabled only for Durable Subscriptions. Setting this check box causes the selected subscription to be cancelled when the JMS session ends.

Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095