Release 10.1A: OpenEdge Development:
AppBuilder

> ## Configuring a SmartProducer instance

> There are only a limited number of instance properties you need to configure.

> | To configure instance properties in the SmartProducer:

> 1. Begin by clicking the instance’s menu button and choosing Instance Properties. The SmartProducer properties dialog box opens:

> 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 entity to read it removes it from the queue. With the Publish-and-Subscribe mechanism, a single copy of the message can be read by all subscribing entities. This allows implementation of a form of multicasting.

> You cannot modify the Domain value at run time.

> - JMS partition — Select a JMS Partition from the dropdown list. 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.
> - 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: If you do not know the User, Password, and Client ID values at design time, you can check the Prompt-for-JMS-Login box and the values will be collected at run time.

> - Ping interval — Defaults to 0 (pinging off). Setting this field to some integer value (representing 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 overall system performance.
> - Prompt for JMS login — Defaults to cleared. Setting this check box causes the messaging object to prompt the user for login.
> - Priority — Defaults to 4. The value is read whenever a new message is sent. It establishes the priority for that message in the range 0 (lowest) to 9 (highest). You can modify the value at run time under program control.
> - Time to live — Defaults to 0 (no expiration). This field is evaluated for every new message. It establishes the length of time in milliseconds that the message can remain unread before being discarded as stale. You can modify the value at run time under program control.
> - Persistency — Defaults to PERSISTENT (message retained in the broker’s database). Other values supported are:

> NON_PERSISTENT (message not retained)

> NON_PERSISTENT_ASYNC

> UNKNOWN

> - Message type — Defaults to TextMessage. Other types supported are:

> BytesMessage — A stream of raw (uninterpreted) bytes. This is the default type when connecting to a SmartB2BObject; most other types require extra code.

> HeaderMessage — Known simply as type Message within the SonicMQ system. Use for shutdown messages.

> XMLMessage — A string representing an XML tree that can be parsed as a document. Do not use this type when connected to a SmartB2BObject.

> MapMessage — A set of name/value pairs, where names are of type string and values are Java primitives. You can read the entries in sequence or randomly by reference to the name.

> StreamMessage — A stream of Java primitives, read sequentially.

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