Difference between revisions of "Installing the Messaging Server: DEPRECATED"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
Line 61: | Line 61: | ||
====Configuring the Messaging Server==== | ====Configuring the Messaging Server==== | ||
# Go to <tt>{appserver_installation}/messaging-server/conf/</tt>.<br>That directory contains two configuration files: | |||
:* <tt>log4j.properties</tt> – standard Apache Log4J configuration file. | |||
:* <tt>server.properties</tt> – Messaging Server configuration file. | |||
#: | |||
# In <tt>server.properties</tt>, configure following parameters: | |||
#* <tt>netty_port</tt> | |||
#:: Use 443 for standalone server instance. | |||
#:: If is on the same system as the appserver: | |||
#::* Use the default value (7007) | |||
#::* Add Apache Web Server proxy instructions (see end of document) | |||
#* <tt>debug</tt> – set value to “1” if you want to see content of all incoming HTTP requests in the log | |||
#* <tt>ssl_keystore</tt> – absolute or relative path to your SSL keystore | |||
#* <tt>ssl_keystore_password</tt> – password for your SSL keystore | |||
#: | |||
# Edit <tt>{appserver_installation}/tomcat/webapps/networking/servicedesk/js/msg_server_link.js</tt> | |||
# Replace the content of that file with this: | |||
#: <tt>var messagingServerHost = "[YOUR_LONGJUMP_HOST_NAME_OR_IP]";</tt> | |||
#: | |||
# Copy the messaging script (<tt>{appserver_installation}/messaging-server/messaging) to <tt>/etc/init.d/</tt> | |||
# cd <tt>/etc/init.d/</tt> | |||
# Make <tt>messaging</tt> an autostart script: | |||
#: <tt>chkconfig –add messaging</tt> |
Revision as of 22:58, 24 January 2014
Installing HornetQ
HornetQ is the Message Queue engine used by the Messaging Server.
To install HornetQ
- Download it from http://www.jboss.org/hornetq/downloads.html
(For the release to use, see the Software Requirements.) - Unpack the archive to the desired location (hornetq-2.2.14, at the the time of this writing).
- Edit {hornetq-folder}/config/stand-alone/non-clustered/hornetq-users.xml
- 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>
- Edit {hornetq-folder}/config/stand-alone/non-clustered/hornetq-configuration.xml
- 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>
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
- Go to the Service Provider URL: http://{yourDomain}/networking/Service?t=1&targetpage=ViewPort.jsp
- Log in as the admin user
- Go to Settings > Service Provider Settings > Service Configuration
- 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.xmlHornetQ User
HornetQ PasswordUse 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
- 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.
- In server.properties, configure following parameters:
- netty_port
- Use 443 for standalone server instance.
- If is on the same system as the appserver:
- Use the default value (7007)
- Add Apache Web Server proxy instructions (see end of document)
- debug – set value to “1” if you want to see content of all incoming HTTP requests in the log
- ssl_keystore – absolute or relative path to your SSL keystore
- ssl_keystore_password – password for your SSL keystore
- Edit {appserver_installation}/tomcat/webapps/networking/servicedesk/js/msg_server_link.js
- Replace the content of that file with this:
- var messagingServerHost = "[YOUR_LONGJUMP_HOST_NAME_OR_IP]";
- Copy the messaging script ({appserver_installation}/messaging-server/messaging) to /etc/init.d/
- cd /etc/init.d/
- Make messaging an autostart script:
- chkconfig –add messaging