Installing the Messaging Server: DEPRECATED

From AgileApps Support Wiki
Revision as of 23:04, 24 January 2014 by imported>Aeric (→‎Configuring the Messaging Server)

Installing HornetQ

HornetQ is the Message Queue engine used by the Messaging Server.

To install HornetQ

  1. Download it from http://www.jboss.org/hornetq/downloads.html
    (For the release to use, see the Software Requirements.)
  2. Unpack the archive to the desired location (hornetq-2.2.14, at the the time of this writing).
  3. Edit {hornetq-folder}/config/stand-alone/non-clustered/hornetq-users.xml
  4. Create a new user by adding the following code to the <configuration> section:
    <syntaxhighlight lang="xml" enclose="div">

<user name="[USER_NAME]" password="[PASSWORD]">

  <role name="admin"/>

</user> </syntaxhighlight>

  1. Edit {hornetq-folder}/config/stand-alone/non-clustered/hornetq-configuration.xml
  2. Replace the <security>...</security> section with the following:
    <syntaxhighlight lang="xml" enclose="div">

<security-settings>

  <security-setting match="#">
     <permission type="createNonDurableQueue" roles="guest, admin"/>
     <permission type="deleteNonDurableQueue" roles="guest, admin"/>
     <permission type="createDurableQueue" roles="admin"/>
     <permission type="deleteDurableQueue" roles="admin"/>
     <permission type="consume" roles="guest, admin"/>
     <permission type="send" roles="guest, admin"/>
     <permission type="manage" roles="admin"/>
  </security-setting>

</security-settings> </syntaxhighlight>

Notepad.png

Note:

HornetQ is started using [hornetq-folder]/bin/start.sh.
It should be started before launching the platform's messaging server.
Learn more: Server Restart Sequence

Configuring the Platform's Service Provider Settings

  1. Go to the Service Provider URL: http://{yourDomain}/networking/Service?t=1&targetpage=ViewPort.jsp
  2. Log in as the admin user
  3. Go to Settings > Service Provider Settings > Service Configuration
  4. Set values for the following parameters:
HornetQ Host  IP address of the server where HornetQ is installed (default: localhost)
HornetQ Port  Default: 5445.
 Needs to be specified only if the port specified for the netty acceptor
 was changed in hornetq-configuration.xml  
HornetQ User
HornetQ Password
 Use the same credentials you specified in hornetq-users.xml
HornetQ QoS  The number of simultaneously working Message Queue listeners.
5. Click [Save]

Creating an SSL Keystore

The Messaging Server accepts only SSL-encrypted connections. It needs a valid SSL certificate to perform a Handshake and data exchange with client systems.

__TBD: Which of the following two paragraphs is correct?__
The same Java keystore, SSL certificate, and private key used for the application server can be used for the Messaging Server.

The same Java keystore used for the application server can be used for the Messaging Server. You can create the SSL certificate and private key in that keystore.

Learn more: Managing SSL Certificates.

Configuring the Messaging Server

  1. Go to {appserver_installation}/messaging-server/conf/.
    That directory contains two configuration files:
    • log4j.properties – standard Apache Log4J configuration file.
    • server.properties – Messaging Server configuration file.
  2. In server.properties, configure following parameters:
    • netty_port
      Use 443 if it is on a standalone system.
      If is on the same system as the appserver, then:
      • Use the default value (7007)
      • Add Apache Web Server proxy instructions (see end of document)
    • debug – set value to 1 to see content of all incoming HTTP requests in the log.
      Otherwise, use the default value (0).
    • ssl_keystore – absolute or relative path to your SSL keystore
    • ssl_keystore_password – password for your SSL keystore
  3. Edit {appserver_installation}/tomcat/webapps/networking/servicedesk/js/msg_server_link.js
  4. Replace the content of that file with this:
    var messagingServerHost = "[YOUR_LONGJUMP_HOST_NAME_OR_IP]";
  5. Copy the messaging script to its target destination:
    cp {appserver_installation}/messaging-server/messaging /etc/init.d/
  6. Make messaging an autostart script:
    cd /etc/init.d/
    chkconfig –add messaging