-
Language:
English
-
Language:
English
6.2. Installing Clients on All Other Platforms
Downloading the client packages
You can download the messaging client packages for JBoss A-MQ, as follows:
- Navigate to the Red Hat Software Downloads page on the Red Hat Customer Portal.
- Select A-MQ under Integration Platforms in the sidebar menu (or using the drop-down menu for the Product field).
- Choose version
6.2.1or6.2.0from the Version drop-down list on the Software Downloads page. - Click Download next to the client package that you want to download.
Available 6.2.1 messaging client packages
The available client packages are shown in Table 6.2, “Messaging Client Packages”.
Table 6.2. Messaging Client Packages
| Package Name | Description |
|---|---|
|
Red Hat JBoss A-MQ 6.2.1 AMQP 1.0 JMS Client 0.5.0
jboss-a-mq-6.2.1-apache-qpid-jms-0.5.0.redhat-1-bin.zip
|
Provides the Qpid JMS client 0.5.0 library.
|
|
Red Hat JBoss A-MQ 6.2.1 QPID C++ Client for Windows 64bit Visual Studio 2012 v3.34.4.1
jboss-a-mq-6.2.1-qpidcpp-x64-VS2012-3.34.4.1.zip
|
Provides the Qpid CMS client library for Windows.
Important: The Qpid C# libraries (
org.apache.qpid.messaging*.dll) and examples included in this archive (under the dotnet_examples directory) are not supported. JBoss A-MQ supports only the Qpid C++ client libraries.
|
|
Red Hat JBoss A-MQ 6.2.1 C++ Client
jboss-a-mq-cpp-6.2.1.redhat-084.zip
| Provides the Apache ActiveMQ C++ client library source code for building on Linux, UNIX, and Windows. |
|
Red Hat JBoss A-MQ 6.2.1 AMQP 1.0 .NET Client for Windows SDK
jboss-a-mq-6.2.1-amqpnetlite-1.1.0.3-1-sdk.zip
| Provides the AMQPNet.Lite SDK for developing AMQP 1.0 .NET clients on Windows. |
|
Red Hat JBoss A-MQ 6.2.1 .NET Client
jboss-a-mq-nms-6.2.1.redhat-084.zip
| Provides the Apache ActiveMQ NMS .NET client library for Windows. |
Copy the archive files to the desired location and decompress them using the appropriate utility for your platform.
After extracting the archives, you can distribute their contents with your client applications that need them. In the case of CMS, you need to build the C++ library from source and include that in your CMS application.
Warning
Do not unpack the archive files into a folder that has spaces in its path name. For example, do not unpack into
C:\Documents and Settings\Greco Roman\Desktop\fusesrc.
Available 6.2.0 messaging client packages
The available client packages are shown in Table 6.2, “Messaging Client Packages”.
Table 6.3. Messaging Client Packages
| Package Name | Description |
|---|---|
|
Red Hat JBoss A-MQ 6.2.0 AMQP 1.0 JMS Client
apache-qpid-jms-0.2.0.redhat-1-bin.zip
|
Provides the Qpid JMS client library.
|
|
Red Hat JBoss A-MQ 6.2.0 QPID C++ Client for Windows 64bit Visual Studio 2012 v3.32.3.1
qpid-cpp-x64-VS2012-3.32.3.1.zip
|
Provides the Qpid CMS client library for Windows.
Important: The Qpid C# examples included in this archive (under the
dotnet_examples directory) are not supported. JBoss A-MQ supports only the Qpid C++ client libraries.
|
|
Red Hat JBoss A-MQ 6.2.0 C++ Client
jboss-a-mq-cpp-6.2.0.redhat-133.zip
| Provides the Apache ActiveMQ C++ client library source code for building on Linux, UNIX, and Windows. |
|
Red Hat JBoss A-MQ 6.2.0 AMQP 1.0 .NET Client for Windows SDK
amqpnetlite-sdk-1.1.0.2.zip
| Provides the AMQPNet.Lite SDK for developing AMQP 1.0 .NET clients on Windows. |
|
Red Hat JBoss A-MQ 6.2.0 .NET Client
jboss-a-mq-nms-6.2.0.redhat-133.zip
| Provides the Apache ActiveMQ NMS .NET client library for Windows. |
Copy the archive files to the desired location and decompress them using the appropriate utility for your platform.
After extracting the archives, you can distribute their contents with your client applications that need them. In the case of CMS, you need to build the C++ library from source and include that in your CMS application.
Warning
Do not unpack the archive files into a folder that has spaces in its path name. For example, do not unpack into
C:\Documents and Settings\Greco Roman\Desktop\fusesrc.
