Develop and deploy your next
app on the IBM Bluemix
|Mission:Messaging: Easing administration and debugging with circular queues
The standard behavior of a queue when it fills up is to stop accepting messages. New messages cannot be enqueued and it is up to the application to determine whether to stop and wait for the queue to drain or to discard the messages. For many use cases though, it would be convenient if the newest messages pushed the oldest messages off of the queue. The result would be that the queue always contained the latest messages rather than the oldest ones and the application or channel never blocks. This installment of Mission:Messaging demonstrates how to achieve this using the built-in features of IBM WebSphere MQ, SupportPac MA01, and some sample "glue" code written in Perl.
|Articles||30 Mar 2011|
|Mission:Messaging: End-to-end encryption with WebSphere MQ Advanced Message Security
Traditionally, middleware, such as IBM WebSphere MQ, has operated within the trusted internal network and the security model has relied heavily on protection at the perimeter. But now, extranets and VPNs are blurring the boundaries of the perimeter and attackers are routinely penetrating firewalls. IBM WebSphere MQ Advanced Message Security extends the functionality available in the base WebSphere MQ product to include security at the message level. This enables a much finer-grained security model and helps to achieve regulatory compliance; for example, when implementing a Payment Card Industry Data Security Standard (PCI-DSS) compliant solution. This article takes a look at how WebSphere MQ Advanced Message Security can help you improve your messaging security.
|Articles||10 Nov 2010|
|Mission:Messaging: Using a Windows service to start WebSphere MQ File Transfer Edition client agents
Replacing FTP clients with IBM WebSphere MQ File Transfer Edition client agents on a user's desktop is a great way to provide enterprise visibility and manageability to these file transfers. The user can start the WebSphere MQ File Transfer Edition agent or put it into the Startup folder to have Windows start it automatically. But what if the client agent needs to run on a Windows server instead of a desktop? Here, there is no user session and no startup folder. It is possible to make a service out of fteStartAgent, but this starts a child process and so it is difficult for Windows to monitor the process for restart. It is also possible to directly call the classes that fteStartAgent calls, but this requires use of undocumented interfaces that could change in a future version. It is always best to avoid using undocumented functionality if possible. This installment of Mission: Messaging illustrates one way of addressing this requirement using fteStartAgent and WebSphere MQ triggering.
|Articles||14 Jul 2010|
|Mission:Messaging: Understanding WebSphere MQ authorization and the setmqaut command
This installment of Mission:Messaging looks under the covers at the interactions between profiles, accounts and groups, for a comprehensive look at IBM WebSphere MQ authorization and the tools used to manage these settings.
|Articles||03 Mar 2010|
|Mission:Messaging: WebSphere MQ cluster design and operation
IBM WebSphere MQ clusters provide ease of administration and workload distribution, plus they play an important part in making messaging solutions highly available. But the cluster must be healthy in order to realize the full benefits. This installment of Mission:Messaging provides some tips on building a healthy cluster and how to keep it that way.
|Articles||09 Dec 2009|
|Mission:Messaging: Ten WebSphere MQ SupportPacs I can't live without
SupportPacs are add-ons that complement the IBM WebSphere MQ family of products. SupportPacs cover a wide variety of functions including planning, administration, development, testing, operations, and troubleshooting. With literally hundreds to pick from, the options can be overwhelming when deciding which would be the best ones for you. There is no definitive list of the "best" SupportPacs out there, but these are the ones I consider to be indispensible.
|Articles||30 Sep 2009|
|Mission:Messaging: Scripted WebSphere MQ key file management for UNIX and Windows
Although the iKeyman GUI makes interactive key management easy, human-driven processes are time consuming, can be prone to errors, and might not produce consistent results. Scripts address all of these issues. In addition, command line tools provide easy access to advanced options, such as FIPS compatibility and choice of signature algorithm. Whether you have a large deployment or just a few queue managers, when it comes to key management, scripts are the key to quality, consistency, repeatability, and efficiency.
|Articles||24 Jun 2009|
|Mission:Messaging: Circular logs vs. linear logs
IBM WebSphere MQ provides two logging options. Circular logs provide transaction recovery and require no maintenance. Linear logs provide recovery from media failure but need to be managed. Which is best and how do you choose?
|Articles||08 Apr 2009|
|Mission:Messaging: Planning for SSL on the WebSphere MQ network
Avoid the two most common pitfalls of implementing SSL on your IBM WebSphere MQ messaging network by learning from those who have been there. Even if you have already deployed SSL, you might find a few suggestions here that will help you tighten it up.
|Articles||28 Jan 2009|
|Mission:Messaging: Migration, failover, and scaling in a WebSphere MQ cluster
Certain aspects of service orientation are best served using an IBM WebSphere MQ cluster. The cluster provides the location independence, run time resolution of names, and concurrency required by SOA applications. For these reasons, adoption of SOA is driving migrations from point-to-point messaging networks to clustered environments. This article looks at how migration, failover, and the scaling of queue managers are affected in an SOA context.
|Articles||12 Nov 2008|
|Mission:Messaging: Embracing cultural change in the WebSphere MQ community
The WebSphere MQ community has been using the same best practices for a long time, and with all of the change that has occurred in the industry, today's underlying processing model has drifted far from the model that existed when these best practices were developed. This difference represents significant potential risk, but we have an opportunity now, as a community, to close this gap and bring our best practices in line with the use cases currently employed.
|Articles||03 Sep 2008|
|Mission:Messaging: WebSphere MQ, PCI DSS, and security standards
When it comes to IBM WebSphere MQ, what is considered âreasonable careâ or âdue diligenceâ in the absence of a formal security standard? This article explores how the PCI Data Security Standard might be applied to WebSphere MQ both inside and outside the payment card industry to answer this question.
|Articles||18 Jun 2008|