com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.

Output ActiveMQ JMS Event Adapter

The configurations of the Apache ActiveMQ output JMS event adapter are explained below. It can be configured with XML, map, JSON, and text output mapping types.

Prerequisites

Follow the steps below to set up the prerequisites before starting the configuration.

  1. Install  Apache ActiveMQ JMS

    This guide uses ActiveMQ versions 5.7.0 or below. If you want to use a later version, for instructions on the necessary changes to the configuration steps, go to Apache ActiveMQ Documentation.

  2. Add the following ActiveMQ JMS-specific JAR files to  <PRODUCT_HOME>/repository/components/lib/ directory. 
    • <ACTIVEMQ_HOME>/lib/activemq-core-xxx.jar  
    • <ACTIVEMQ_HOME>/lib/geronimo-j2ee-management_1.1_spec-1.0.1.jar  

Configuring the ActiveMQ output JMS event adapter

You can configure the ActiveMQ output JMS event adapter either using the management console or using a configuration file as explained below. This deploys the event adapter in the  <PRODUCT_HOME>/repository/deployment/server/outputeventadaptors/ directory.

Configure using the management console

Follow the instructions below to configure ActiveMQ output JMS event adapter using the management console.

  1. Start ActiveMQ, and then start the product.

  2. Log in to the product's management console, and click Configure.
  3. Click Output Event Adaptors in the Event Processor Configs menu, and then click Add Output Event Adaptor.
  4. Enter details as shown in the below example. 
    create output JMS event adapter
  5. Click Add Event Adaptor.

Configure using a configuration file

Follow the instructions below to configure ActiveMQ output JMS event adapter using a configuration file.

  1. Create an XML file with the following ActiveMQ output JMS event adapter configurations.  Output event adapter implementation must start with  <outputEventAdaptor>  as the root element.

    <outputEventAdaptor name="activemqJmsOutputAdaptor" statistics="disable"
      trace="disable" type="jms" xmlns="http://wso2.org/carbon/eventadaptormanager">
      <property name="java.naming.provider.url">tcp://localhost:61616</property>
      <property name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</property>
      <property name="transport.jms.ConnectionFactoryJNDIName">TopicConnectionFactory</property>
      <property name="transport.jms.DestinationType">topic</property>
    </outputEventAdaptor>
  2. Add the XML file to the <PRODUCT_HOME>/repository/deployment/server/outputeventadaptors/ directory. Since hot deployment is enabled, you can simply add/remove files to deploy/undeploy to/from the server.

After an adapter is successfully added, it gets added to the list of adapters displayed under  Event Processor Configs  in the  Configure  menu of the product's management console. Click  Edit to change its configuration and redeploy it. This opens an XML-based editor allowing you to edit the event adapter configurations from the UI.  Do your modifications and click  Update . You can also delete it, enable/disable statistics or enable/disable tracing on it using the provided options in the UI.

Configuring output JMS event adapter message properties

For instructions on configuring output JMS event adapter message properties, see Configuring Output JMS Event Adapter Message Properties.

 

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.