JMS Server App-bundle (Aspire 2)

Revision as of 00:32, 9 December 2015 by Dherrera (talk | contribs)
Jump to: navigation, search

For Information on Aspire 3.1 Click Here

JMS Server App-bundle (Aspire 2)
AppBundle Name  JMS Server service
Maven Coordinates  com.searchtechnologies.aspire:app-jms-server
Versions  2.2.2
Type Flags  None
Inputs  N/A
Outputs  N/A

If you're not sure what JMS is, have a look at the Wikipedia entry here.

The JMS Server service allows you to install a simple Java Message System server inside Aspire. You can then connect clients to send and/or JMS messages via queues or topics available on the server.

There are many uses for JMS messaging, but in side Aspire it's used in the file system staging repository to allow near real time updates from the content repository (for instance Documentum) and the search engine via the staging repository.

Aspire's JMS Server service uses code from the Apache ActiceMQ project to implement a JMS broker. It should be noted that Aspire's implementation is very simplistic, and if you need a JMS server that offers resilience, message forwarding or any advance messaging features, this is probably not the server for you. This implementation is more suited to testing or proof of concepts.


This section lists all configuration parameters available to install the JMS Server service Application Bundle.

General Application Configuration

Property Type Default Description
name String AspireMQ The name of the JMS broker that will run inside Aspire. The name should be unique on the network
connector Url tcp://localhost:61616 The url of the JMS service the server component will provide
debug Boolean false Controls whether debugging is enabled for the application. Debug messages will be written to the log files.

Configuration Example

To install the application bundle, add the configuration, as follows, to the <autoStart> section of the Aspire settings.xml.

  <application config="com.searchtechnologies.aspire:app-jms-server">
    <property name="name">MyServerName</property>
    <property name="connector">tcp://localhost:61616</property>
    <property name="debug">false</property>

Note: Any optional properties can be removed from the configuration to use the default value described on the table above.