In Local JMS, you create destinations by setting the localJMSQueueNames and localJMSTopicNames properties of the /atg/dynamo/messaging/MessagingManager component. For example:

localJMSQueueNames+=/Orders
localJMSTopicNames+=/RegistrationEvents,/FinancialEvents

When a Nucleus-based application starts up, it creates these destinations. To access a Local JMS destination in your code, you use JNDI references of the form:

localdms:/local{queue-or-topic-name}

For example, localdms:/local/Orders.

You can also use the DMS configuration file (discussed in the Configuring Patch Bay section) to create Local JMS destinations. These destinations are specified by name, separated into topics and queues:

<dynamo-message-system>
  <patchbay>
    ...
  </patchbay>

  <local-jms>

    <topic-name>/MyApp/RegistrationEvents</topic-name>
    <topic-name>/MyApp/FinancialEvents</topic-name>
    ...

    <queue-name>/MyApp/Orders</queue-name>
    ...
  </local-jms>
</dynamo-message-system>

When a Nucleus-based application starts up, it create these destinations with the JNDI names localdms:/local/MyApp/RegistrationEvents, localdms:/local/MyApp/FinancialEvents, and localdms:/local/MyApp/Orders.

Remember that Local JMS keeps no state, so adding these topics and queues simply creates named locations for messages to be sent locally. Nothing is actually added to a back-end storage system.