Skip to main content

Websphere Message Broker Deployment methods

Deployment methods
===================

Choose the appropriate method of deployment to suit the way in which you are working. You can use the WebSphere® Message Broker Toolkit, the WebSphere Message Broker Explorer, the mqsideploy command, or functions described by the Administration API for WebSphere Message Broker (also known as the CMP API).

Using the WebSphere Message Broker Toolkit
============================================

The Brokers view of the WebSphere Message Broker Toolkit displays all the brokers on the local machine that you have defined, and any remote brokers that you have defined connections to. If you expand a broker, all the execution groups within that broker are displayed together with deployed message flows, and their associated resources. You can drag a message flow or a broker archive (BAR) file from the Broker Development view onto an execution group to deploy it. Alternatively, you can right-click an execution group to select a message flow or a BAR to deploy to the selected execution group.

You might typically use the WebSphere Message Broker Toolkit if your primary role is as an application developer, or if you are new to WebSphere Message Broker.
Using the WebSphere Message Broker Explorer
The Navigator view of the WebSphere Message Broker Explorer displays all the brokers on the local machine that you have defined, and any remote brokers that you have defined connections to. If you expand a broker, all the execution groups within that broker are displayed together with deployed message flows, and their associated resources. You can import broker archive (BAR) files into the WebSphere Message Broker Explorer. The BAR files are displayed in the Broker Archive Files folder in the WebSphere Message Broker Explorer. You can drag a broker archive (BAR) file from the Broker Archive Files folder onto an execution group to deploy the contents of the broker archive. Alternatively, you can right-click on an execution group or broker archive file and select Deploy File to deploy resources to an execution group. You can also drag BAR files from your file system directly onto an execution group to deploy the contents of the broker archive.

You might typically use the WebSphere Message Broker Explorer if your primary role is as a WebSphere Message Broker administrator.
Using the mqsideploy command
You can deploy from the command line using the mqsideploy command. On the command line, you specify the connection details as well as parameters specific to the deployment.

You might typically use the mqsideploy command in a script when you are more familiar with WebSphere Message Broker.
Using the CMP API
You can control deployment from a Java™ program by using functions described by the CMP API. You can also interrogate the responses from the broker and take appropriate action.

Java applications can also use the CMP API to control other objects, such as brokers and execution groups. Therefore, you can use the CMP API to create and manipulate all your brokers and associated resources programmatically.
Deployment results
Whichever deployment method you use, any configuration changes will be attempted immediately:

* If you are using the WebSphere Message Broker Toolkit, the Deployment Log view will be updated to show the results when your deployment completes. If the deployment fails, the reason for the failure will be displayed in this view.
* If you are using the WebSphere Message Broker Explorer, you can see the deployment status for all users connected to the broker. The Administration Queue shows all deployments that are currently being processed by the broker, and the Administration Log shows all recent configuration requests and changes made to the broker.
* If you use the mqsideploy command, the command completes when the broker has completely processed the deployment request, or when the wait time defined by the -w parameter has expired, whichever occurs first. The results of the deployment are displayed as output from the command.
* If you are using the CMP API, you can view the results of the deployment in the following ways:
o Review the DeployResult object which is returned from the deployment methods.
o Access the LogProxy object that represents the administration log.
o Access the AdminQueueProxy object that represents the administration queue.
Labels:

Comments

Post a Comment

adsrerrapop

Popular posts from this blog

Troubleshooting Java/JMS SSL Configurations - Middleware News

 This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...
Post a Comment
Read more

Using telnet to test connectivity between IBM Websphere MQ Client and MQ server - Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin...
Post a Comment
Read more

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...
143 comments
Read more