Technical experts from IBM share support knowledge for Application Integration Middleware products including WebSphere, CICS, and more! Blog managed by Steve Webb and Kelley Anders. We're following the IBM Social Computing Guidelines.
By now you have probably heard the news about WebSphere Application Server (WAS) v6.1 reaching the end of its Software Support Lifecycle on September 30th, 2013. But if you missed the deadline and now it's October you may be wondering what it is you need to do next to ensure you have IBM support.
We have pulled together a lot of information that outlines the options you have available from IBM in terms of migrating (upgrading) to a new version or obtaining a support extension (SE).
Like all platforms, specialized skills are just part of the territory when we talk about successfully migrating (upgrading) software. For those familiar with mainframes this has never been more true than in the z/OS environment where installation and migration tasks may entail extensive planning. When so many details have to be taken into account it can be easy to miss a simple step. Though relatively small, one misstep can mean missed targets or delays in rollouts to other environments until test systems are first up to snuff. So, while... [More]
I've had a few customers lately that are in a situation where they are still running old unsupported versions of WebSphere MQ. Specifically, a problem arises when they are still on MQ version 5.3 and want to upgrade to a recent version such as 7.1 or 7.5 as there is not direct route for upgrading MQ v5.3 to those versions. Here are links to migration documentation in the information center: For MQ v7.1: Migrating and upgrading WebSphere MQ For MQ v7.5: Planning WebSphere MQ version 6.0 to WebSphere MQ version 7.5 migration by platform If you... [More]
In the fall of 2011, I posted an article titled WebSphere Application Server Information Supercenter with links that may be particularly helpful when navigating the support information available for WebSphere Application Server (WAS). Since then we've had plenty of newsworthy activity, for example, the release of WAS V8.0 and V8.5 as well as some fix packs. Here is an updated list to bookmark that will help with keeping the top information at your fingertips. Version 8.0 and 8.5 Links: System Requirements for Application Client for WebSphere... [More]
In my job as a Project Leader in ITSO (also known as the IBM Redbooks team) I have published more than 100 books since 1999. My first two Redbooks publications even had the red covers. Anyone still remember them? I have always enjoyed working for ITSO, because of the opportunity to meet with people from all over the world and to be able to work on the leading-edge IBM products. Most of the Redbooks projects are run in one of the two ITSO centers in US --Raleigh and Poughkeepsie. However, recently we have started running some of these outside... [More]
Most migrations (upgrades) of WebSphere MQ go swimmingly, don't they? This is a good thing. But we'd like to see every single one of them fall into that bucket. To that end, it's crucial that you include the following information into your migration plans. This is because migration isn't just about moving forward, but it's also about allowing queue managers to co-exist in configurations where queue-sharing groups commingle data; where different levels of the base code may have been installed; and how to create a migration plan where you can... [More]
The idea behind this blog entry is to house multiple related links to WebSphere Application Server (WAS) V6.1 Going End of Support and Upgrading or Migrating to WAS V8.5. It's not the end of the world, but yes, WAS 6.1 is going out of support in September 2012 2013. What's your plan? Update: IBM has decided to extend the WebSphere Application Server V6.1 End of Support date, giving you another year of support while you plan your upgrade to one of the latest releases, the NEW End of Support date is September 30 2013! See the link above... [More]
WebSphere Commerce V7.0 Feature Pack 5.0 was recently released and many clients rushed to upgrade to the new environment so they could play with the new features. One of the prerequisites is to upgrade WebSphere Commerce to 220.127.116.11 fixpack, and as usual, while already one is at these maintenance tasks, it is good to upgrade also the underlying SW (software) stack, such as the WebSphere Application Server (WAS) fixpack level, to the latest. While running upgrades for WebSphere Commerce underlying SW stack such as WAS fixpacks, it's good to be... [More]
The launchpad, introduced in V7.5, helps you install the prerequisites and the product components, in the correct order. To understand the WODM components that the installer includes, read the section Composition of Operational Decision Management for version 7.5, and for version 8.0 see section Composition of WebSphere Operational Decision Management of the WODM information center. First of all, refer to the WODM Detailed System Requirements
to ensure that your configuration complies with the hardware and software requirements . Then,... [More]
When it comes to making the decision on when to upgrade the maintenance on a WebSphere MQ system, many people prefer not to think about it. They wait until they are forced to make the upgrade, either because they hit some very serious problems or because a version of MQ has gone unsupported. After going through a "forced" upgrade, it is very common for a person to look back at their experience and wish they could have avoided that scenario. Often times, the person will say "I wish I knew then what I know now". Thinking... [More]
The new channel authentication records were added to version 7.1 to give more precise control over access granted to a connecting system at the channel level. This feature allows you to define rules about whether certain inbound channels to a queue manager should be allowed or blocked. The rules can be set up to use IP address, SSL/TLS subjects distinguished Name, Client user ID or remote queue manager name. I'm not going to attempt to go over the features available here but bring a possible issue to your attention that might affect you... [More]
Following is support content available to help you with the task of planning and upgrading to a more current version of WebSphere DataPower SOA Appliance firmware: See a summary of the supported versions of WebSphere DataPower firmware in this IBM WebSphere DataPower Appliance Support Lifecycle document. More information about accessing the latest firmware versions is available in Supported firmware versions and recommended upgrade levels for WebSphere DataPower SOA Appliances . Be attentive to the details provided in Critical updates for IBM... [More]
Often, we receive Problem Records (PMRs) or Service Requests (SRs) requesting a fix for a specific APAR problem. If the fix is included with a published fixpack, we generally recommend that the user apply the latest fixpack rather than requesting an interim fix. Interim fixes are often not available on fix central for general download. We encourage users to apply the fixpack if possible. Interim fixes do not undergo the same rigorous 3 month cycle of thorough testing involved in certifying a FixPack. If a user wants an interim fix for... [More]
Thinking about upgrading, migrating, applying maintenance on UNIX tm ? How about 1 minute sanity check of your environment? Problems often occur during or after an upgrade, migration, or application of maintenance. If you have bad luck, there's a good chance everyone will become aware of that little thing you left out in your planning. It's just one of those things... you succeed in private, but fail in public. I can't change that fact, but what I can do is to help you avoid many issues with a simple, one-sentence tip. Here's the tip:... [More]
Clustering is a WebSphere MQ feature that is often confusing for many users. I’d like to provide some guidelines you can follow to ensure the optimum health for your cluster. Here’s a list of Ten Tips for MQ Clustering: Don’t issue refresh command unless absolutely necessary. The REFRESH CLUSTER command can cause temporary disruption to traffic as it clears out the local cache. It is not a command that should be issued on a routine basis. Have 2 Full Repositories (no more, no less). When updates are made within a cluster, two messages are sent... [More]
WebSphere Message Broker (WMB) version 6.0 brought with it many important changes to the WMB product: an updated eclipse-based Toolkit improved message parsing and transformation (including ESQL, XSLT, and Java tm ) even enhanced support for web services and many more... However, we are now beginning to see the sun set for WMB 6.0. You may have heard that the 'EOS' date for WebSphere MQ 6.0 was moved, but the same cannot be said of Message Broker! WebSphere Message Broker 6.0 reaches its 'End of Support' date on April 30th, 2011: For more... [More]
Ever since the end of support date for WebSphere Message Broker (WMB) V6.0 was announced, we have been receiving a lot of queries on migration from the older versions of Message Broker to the latest WMB V7.0. In this blog, I have tried to address some common questions around migration. You can migrate from your existing Message Broker components and its resources to WMB V7.0 in a streamlined fashion. You can also reverse migrate from a WMB V7.0 broker to the older version of broker provided you first migrated from this older version to V7.0 on... [More]
The End of Service date for WebSphere Data Interchange version 3.2 on z/OS was April 26, 2010, and I have seen a number of problem records dealing with the upgrade. I thought I would share some of the Lessons Learned that users have experienced while migrating to the new version of WebSphere Data Interchange version 3.3 on z/OS. The following are a few of the Lessons Learned that users have encountered while going through the steps outlined in the WebSphere Installation Guide for z/OS. This guide can be downloaded from the WebSphere Data... [More]