Middleware News

WebSphere MQ V7.5 delivers a single Universal Messaging solution. It enables the simple, rapid, reliable, and secure transport of data and messages between applications, systems, and services. WebSphere MQ is the market-leading, message-oriented middleware product that delivers a reliable, proven universal messaging backbone for almost 10,000 organizations of different sizes, spanning many industries around the world Customers gain access to previously separately installable capabilities, enabling more complete solutions for data and message movement along with reduced complexity. Get the advantage of a smaller install footprint, simpler maintenance and eliminate the need for separate packages. Add as you need. Enhancements include Integrated Managed File Transfer – WebSphere MQ File Transfer Edition, previously available separately, is now integrated as an optional feature of WebSphere MQ server component as WebSphere Managed File Transfer Service. Additional separately ins

dspmqinf Display WebSphere® MQ configuration information (Windows and UNIX platforms only). Purpose Use the dspmqinf command to display WebSphere MQ configuration information. Optional parameters -s StanzaType The type of stanza to display. If omitted, the QueueManager stanza is displayed. The only supported value of StanzaType is QueueManager. -o stanza Displays the configuration information in stanza format as it is shown in the .ini files. This format is the default output format. Use this format to display stanza information in a format that is easy to read. -o command Displays the configuration information as an addmqinf command. Information about the installation associated with the queue manager is not displayed using this parameter. The addmqinf command does not require information about the installation. Use this format to paste into a command shell. Return codes Return code Description 0 Successful operation 39 Bad command-line parameters 44 Stanza

dspmqver New types of information are displayed by dspmqver to support multiple installations. The changes might affect existing administrative scripts you have written to manage WebSphere® MQ. The changes in output from dspmqver that might affect existing command scripts that you have written are twofold: Version 7.5 has extra -f field options. If you do not specify a -f option, output from all the options is displayed. To restrict the output to the same information that was displayed in earlier releases, set the -f option to a value that was present in the earlier release. Compare the output for dspmqver in Figure 1 and Figure 2 with the output for dspmqver -f 15 in Figure 3. Figure 1. Default dspmqver options in WebSphere MQ version 7.0.1 dspmqver Name:        WebSphere MQ Version:     7.0.1.6 CMVC level:  p701-L110705 BuildType:   IKAP - (Production) Figure 2. Default dspmqver options in WebSphere MQ version 7.5 dspmqver Name:        WebSphere MQ Version:     7.1

You can also specify the maximum number of active channels. You can do this to prevent your system being overloaded by a large number of starting channels. If you use this method, you should set the disconnect interval attribute to a low value to allow waiting channels to start as soon as other channels terminate. Each time a channel that is retrying attempts to establish connection with its partner, it must become an active channel. If the attempt fails, it remains a current channel that is not active, until it is time for the next attempt. The number of times that a channel will retry, and how often, is determined by the retry count and retry interval channel attributes. There are short and long values for both these attributes. See Channel attributes for more information. When a channel has to become an active channel (because a START command has been issued, or because it has been triggered, or because it is time for another retry attempt), but is unable to do so because the

You can set server-connection channel limits to prevent client applications from exhausting queue manager channel resources and to prevent a single client application from exhausting server-connection channel capacity. A maximum total number of channels can be active at any time on an individual queue manager, and the total number of server-connection channel instances are included in the maximum number of active channels. If you do not specify the maximum number of simultaneous instances of a server-connection channel that can be started, then it is possible for a single client application, connecting to a single server-connection channel, to exhaust the maximum number of active channels that are available. When the maximum number of active channels is reached, it prevents any other channels from being started on the queue manager. To avoid this, you must limit the number of simultaneous instances of an individual server-connection channel that can be started, regardless of whi

Use the  Channels  queue manager properties page from the WebSphere® MQ Explorer, or the  CHANNELS stanza in the qm.ini file, to specify information about channels. MaxChannels= 100 | number The maximum number of channels allowed. The default is 100. MaxActiveChannels= MaxChannels_value The maximum number of channels allowed to be active at any time. The default is the value specified on the  MaxChannels  attribute. MaxInitiators= 3 | number The maximum number of initiators.  The default and maximum value is 3. Any value greater than 3 will be taken as 3. MQIBindType=FASTPATH| SHARED The binding for applications: FASTPATH Channels connect using  MQCONNX  FASTPATH; there is no agent process. SHARED Channels connect using SHARED. PipeLineLength= 1 | number The maximum number of concurrent threads a channel will use. The default is 1. Any value greater than 1 is treated as 2. When you use pipelining, configure the queue managers at both ends of the channel to hav