Tekslate Websphere MQ Free Tutorial
Introduction to Websphere MQ This document contains step by step technical information to learn MQ series, by using this one can start working with control and WebSphere MQ script commands through the Windows Explorer and UNIX/AIX Command line interface. ď‚— MQSeries runs on a variety of platforms. The MQSeries products enable programs to Communicate with each other across a network of unlike components, such as processors, subsystems, operating systems and communication protocols. MQSeries programs use a consistent application program interface (API) across all platforms. ď‚—
Overview of Websphere MQ Message in MQ An MQSeries message is simply a collection of data sent by one program and intended for another program. The message consists of control information and application specific data. The control information is required in order to route the message between the programs to some extent. A message can be classed as persistent or non- persistent. A persistent message will survive a software or hardware crash / reboot, once communicated to a queue manager, whereas a non-persistent message will not survive. Persistent messages are used as part of the implementation of the assured delivery service supported by MQSeries.
Queue Managers It is the queue manager that provides the queuing services to the application programs. A queue manager also provides additional functions so that administrators can create new queues, alter the properties of existing queues and control the operation of the queue manager. Many applications can make use of the queue manager’s facilities at the same time, and they can be completely unrelated. It is possible to connect queue managers on different platforms together, this is achieved via a mechanism called channels.
Queues Queues are named message repositories upon which messages accumulate until they are retrieved by programs that service those queues. Queues reside in, and are managed by, a queue manager. Programs access queues via the services provided by the queue manager. They can open a queue, put messages on it, get messages from it, and close the queue. It is also possible to programmatically set, and inquire about, the attributes of queues. Queues are either defined as local or remote. Local queues allow programs to both put messages on, and get messages off, while remote queues only allow programs to put messages on. Remote queues are used in order to provide put access to queues that are local to another platform.
Channels Channels are named links between platforms across which messages are transmitted. On the source platform the channel would be defined as a sender and on the destination platform as a receiver. It is the sender channel definition that contains the connectivity information, such as the destination platform’s name or IP address. Channels must have the same name on both the source and destination platform.
MQ Series Logging and Recovery All operations that affect the “state” of the Queue Manager and its objects are logged to a log file. What is “state”? Object definitions (queue manager, queues, processes, channels, etc) Queue content (messages) Message channel states are logged separately by each channel. There are two forms of Logging Circular – log records are written sequentially across several files, then “wrap” back to the first file. log records are written sequentially across files. New files are allocated as current files fill. No automatic reuse of file space! Problem: Length (in time) of longest running transaction vs amount of writes to log determines size of log needed.
JBoss client Directory This directory contains the Java libraries (JARs) required for clients that run outside the JBoss AS containers, such as: Web Service clients EJB clients JMX clients Used by external applications that need to access JNDI resources On Unix, to get the client CLASSPATH, run: ${jboss.home.dir}/bin/classpath.sh -c As of JBoss 5, the file client/jbossall-client.jar contains references to other JARs via ClassPath setting in its META-INF/MANIFEST.MF file. This makes it possible for external JBoss clients to just reference this one JAR file as opposed to many of them.
And Also Issues Interview Questions How to’s For More Websphere MQ Free Tutorials Please Visit: http://bit.ly/1z5mDBC