Websphere MQ & Websphere MB
What is Websphere Message Queue? 2
What is Websphere Message Broker? 2
Websphere Message Queue Installation 3
Websphere Message Broker Installaion 5
MQInput Node & MQOutput Node 10
Overview
What is Message Queue?
Message queues are software-engineering components used for interprocess communication, or for inter-thread communication within the same process. They use a queue for messaging – the passing of control or of content. Group communication systems provide similar kinds of functionality.
Message queues provide an asynchronous communications protocol, meaning that the sender and receiver of the message do not need to interact with the message queue at the same time. Messages placed onto the queue are stored until the recipient retrieves them. Message queues have implicit or explicit limits on the size of data that may be transmitted in a single message and the number of messages that may remain outstanding on the queue.
What is Websphere Message Queue?
The power of IBM® WebSphere® MQ is its flex ibility combined with reliability, scalability and security. This flexibility provides a large number of design and implementation choices. Making informed decisions from this range of choices can simplify the development of applications and the administration of a WebSphere MQ messaging infrastructure.
Applications that access a WebSphere MQ infrastructure can be developed using a wide range of programming paradigms and languages. These applications can run within a substantial array of software and hardware environments. Customers can use WebSphere MQ to integrate and extend the capabilities of existing and varied infrastructures in the information technology (IT) system of a business.
What is Websphere Message Broker?
WebSphere Message Broker is a powerful information broker that allows both business data and information, in the form of messages, to flow between disparate applications and across multiple hardware and software platforms. Business rules can be applied to the data that is flowing through the message broker in order to route, store, retrieve, and transform the information.
WebSphere Message Broker is built upon WebSphere MQ and therefore supports the same transports. However, it also extends the capabilities of WebSphere MQ by adding support for other protocols, including real-time Internet, intranet, and multicast endpoints.
Installation
Websphere Message Queue Installation
To install WebSphere MQ, follow the instructions for installing with the Advanced Installation.If need to use WebSphere MQ Explorer, ensure that WebSphere Eclipse Platform V3.3 is installed,if not the software requirement check should displayed like follow:
The Eclipse Platform is included in the Message Queue installation folder by default, so click the CD-ROM button and navigate to the setup.exe to install.
After the installation completely, the software check should be displayed like follow:
Now, navigate to WebSphere MQ installation tab, select the installation language and launch the installer button to install WebSphere MQ.
After the installation complete. Websphere MQ service has been installed. To verify that the WebSphere MQ service is running, perform any of the following tasks:
Check the system tray icon to see whether WebSphere MQ is running.
Figure 3-4 shows the system tray icon for WebSphere MQ in the started state
(left icon) and the stopped state (right icon).
If WebSphere MQ is not running, right-click the system tray icon, then click
Start WebSphere MQ .
Check the Services list for the IBM MQSeries® status. The status should be
Started. To open Services, click Start→Control Panel→Administrative Tools →Services .
If WebSphere MQ is not running in the Services window, right-click IBM MQSeries
then click Start.
Websphere Message Broker Installaion
Double-click the mqsilaunchpad.exe file which is usually located in the root directory.
The Launchpad contains links to the following information:
l The Installation Guide, which contains a link to the most recent version of the Installation Guide that is available on the Internet
l The product readme file, which contains last minute, undocumented changes to the product, and a link to the most recent version of the readme file available on the Internet
l The Quick Tour, which is a graphical overview of the product.
Just install the Websphere Message Broker, Websphere MB toolkit & Explorer by steps as the list.
First to install Websphere Message Broker V8
Whitout any configuration, just follow the “next”.
After Websphere Message Broker installation is completely, the explorer will be install by install mananger
Then is Websphere Message Broker Toolkit, it install by IBM Installation Manger
After all the installation completely and currectly, the Installation Guide will be displayed like follow:
Configuration
Message Queue Manager
First, a WebSphere MQ administrator creates a queue manager. The crtmqm command creates a queue manager. Fox example create a queue manager called QMA.
To start this queue manager and make it available for applications, use the strmqm command
as shown:
The queue manager must be running before you use the runmqsc command. It works in two ways:
l Type the commands directly.
l Use input direction to work with a text file that contains a list of commands. For example, entering runmqsc QMA < commands.mqsc runs the commands in the file.
The commands in follow are examples that are used to create the local queue QUEUE1.
Message Broker
For any message broker project, they always deploy the project in a broker and it is belong the Message Queue. So we could use the mqcreate command to create message broker for the project to deploy. There is an example as follow:
mqsicreatebroker <brokername> -i <username> -a <password> -q <broker_queue_manager >
The Message Queue just use the system reouces to operate the database. So if the Message Queue need to connect to Database, then we need to configurate the system odbc resource and bind the system odbc resource and the broker together use the following command:
mqsisetdbparms <remote broker> -n <system database resource> -u <username> -p <password>
mqsireload <remote broker> -e <excute group>
BTW: For x64 windows system, the system resource config panel is the “odbcad32.exe” under C:\WINDOWS\SysWOW64 folder.
Message Broker Node
MQInput Node & MQOutput Node
The message input & output node are mesage queue included object ,it can support received,send,read-only,queue operation,can auto matically split into message fragments large messages,but also can auto matically message fragments to form a complete message.
HTTP Nodes
It is similar to the MQ node, to provide Http/Https access and input message can be resolved, then transfer to the input
The Http node include:
- HTTPInput
- HTTPReply
- HTTPRequest
- HTTPHeader
MQInput nodes and MQReply nodes in the request / response model used in pairs, and HTTPRequest nodes as the client calls the external system
Use MQInput nodes and MQReply nodes can interact with Web Service, Web Service MQInput node
Access point use HTTPRequest nodes and Web service interaction, the input message in whole or in part as sent to the service request; the node will according to the configuration from the input message specifies the content structure of HTTP or HTTP over SSL (HTTPS) request, and sends it to Web service.
Compute Node
The Compute nodes is used to construct one or more new output message.
These output message may be created by modifying the input message, or may (or may not) is used to create the new information from the database.It can use the input message elements (e.g., head, head field and the main data), the related environment and its exception list to create a new output message.
Compute node:
l With the latest news - a group assignment statement structure
l In between - replication message parser
l Message conversion to another code set from a code
l Message conversion from one format to another format
It can be achieved using ESQL MB for data manipulation functions, including the format conversion, message splitting polymerization, database operation, dynamic parameter setting.
Java Compute Node
Java Compute node is a general-purpose programmable node
It suppot Java programming language, Java 6
It provide similar "Compute node" function, through the realization of Java
- without the need for ESQL programming skills and experience
It provide complete Java plug-in API access mode
It can automatic generation of Java code framework -, the compilation and packaging automatic.
The message tree can use XPath to query and set
– for parsing and constructing the XML data more simple
It can support database access.
– JDBC type 4, the standard XA support
It also can use the ESQL in the Java grammar, support services