AgileApps Support Wiki

Installing the Messaging Server: DEPRECATED

From AgileApps Support Wiki

Warn.png

Warning:

This feature has been deprecated and should not be used with the latest versions of AgileApps. This document is no longer being updated.


Prerequisites

Before starting the Messaging Server installation, the Application Server (appserver) should be installed.

Download the Messaging Server

  1. Download the messaging server https://agileappscloud.info/aawiki-src/download/files/messaging-server.tar.gz
  2. Unpack the archive to the application server directory.
    For example:
    cd {appserver}/
    gunzip messaging-server.tar.gz
    tar xfz messaging-server.tar

Install HornetQ

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

To install HornetQ:

  1. Download the release specified in the Software Requirements from
    http://www.jboss.org/hornetq/downloads.html
  2. Unpack the archive to the desired location.
    For example:
    cd {appserver}/
    tar xfz hornetQ-{version}.tar
  3. Edit {hornetq_install}/config/stand-alone/non-clustered/hornetq-users.xml
    Add the following code to the <configuration> section to create the admin user who will have access to the queue: 
    <user name="[USER_NAME]" password="[PASSWORD]">
   <role name="admin"/>
</user>
  4. Edit {hornetq_install}/config/stand-alone/non-clustered/hornetq-configuration.xml
    Replace the <security>...</security> section with the following: 
    <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>

Start HornetQ

Start HornetQ before proceeding with the next step in the installation:

{hornetq_install}/bin/run.sh

Notepad.png

Note:
HornetQ should always be started before launching the platform's messaging server.

Learn more: Server Restart Sequence

Configure 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
 (If running on the same server as the messaging server, enter 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.
 (A typical value is 2.)
5. Click [Save]
6. Restart the server to read the new configuration:
  1. Login as root
  2. {install-dir}/profiles/IS_default/bin/restart.sh

Create 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.

The same Java keystore, SSL certificate, and private key used for the application server can be used for the Messaging Server. So once that has been set up, nothing else needs to be done.

Learn more: Managing SSL Certificates.

Configure the Messaging Server

  1. Start the appserver:
    {appserver}/profiles/IS_default/bin/startup.sh
  2. Go to {appserver}/messaging-server/conf/.
    That directory contains two configuration files:
    • log4j.properties – standard Apache Log4J configuration file.
    • server.properties – Messaging Server configuration file.
  3. In server.properties, configure the 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 (7443)
      • 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
    • customer_db_server - put proper values for host, username and password to connect to the platform's MySQL Database
    • message_db_server - put proper values for host, username and password to connect to the Messaging Server Database.
      If the Messaging Server doesn't have a separate MySQL instance, copy the value of customer_db_server
  4. In platform's Service Provider Settings, set the Messaging Server Host parameter to the messaging server's hostname (or IP address) and port. For example, hostname:7443.
AppServer Installation

Follow these steps when running the Messaging Server on the same system as an appserver:

  1. Copy the messaging script to its target destination:
    cp {appserver_installation}/messaging-server/messaging /etc/init.d/
  2. Make messaging an autostart script:
    cd /etc/init.d/
    chkconfig –add messaging
Standalone Installation

For maximum performance, follow these steps to run the Messaging Server on a standalone system:

  1. Install MySQL on the Messaging Server instance. Use the same MySQL credentials as on the appserver.
  2. Import messagingdb.sql into MySQL on the Messaging Server system.
    Note:
    The MySQL instance used by the Messaging Server contains real-time data, only. There is no need for backups or database replication, as the data structures can be easily restored by re-running that SQL script.
  3. Copy these files from the appserver system to the Messaging Server system:
    • Copy the entire messaging-server directory to the installation directory.
    • Copy es.jar from the platform's tomcat/lib to messaging-server/lib
    • Copy the downloaded mysql connector library to messaging-server/lib
    • Copy the SSL keystore file directory to messaging-server/conf/ssl
  4. In startmessaging.sh, correct the path for each JAR used in Java classpath to reference the jars in messaging-server/lib
  5. In messaging-server/messaging correct the path for the cd command to go to {install-dir}/messaging-server
  6. Copy the messaging script to its target destination:
    cp messaging-server/messaging /etc/init.d/
  7. Make messaging an autostart script:
    cd /etc/init.d/
    chkconfig –add messaging
Verifying if the Messaging Server has Started
Run the following commands in the messaging server console:

Notepad.png

Note: If the server is not up and running, you will not see any output for these commands. In such scenarios, review the server log files.

  • netstat -anop | grep 7443 - Verify if the port 7443 is listening.
  • ps -ef |grep netty - Verify if the netty server is up and running.


Finding the Server Logs

  • messaging-server/logs/server.log contains the runtime log records for the Messaging Server
  • messaging-server/logs/startup.log contains startup and class loading errors
Retrieved from "https://agileappscloud.info/aawiki-src/index.php?title=Installing_the_Messaging_Server:_DEPRECATED&oldid=23542"