Of course, in one sense, there if "no problem" but is he wants to use three different products then there will be inevitably. Paying IBM to support all of them is one option. As for the original question, there is no way to prevent one vendor from blaming another's product. The easiest way to get the problem resolved is to submit a detailed, accurate description of the problem, preferably with a test case, that demonstrates that the problem lies with one particular vendor. I've done a lot of support and I can't tell you how many times people call and say "x is broken" and they don't describe the problem or provide any diagnostic data to support it. The first thing a support person is going to do is to throw it back at you and say "give me more detail." It's no wonder why people complain so much about support when they don't even help themselves in the first instance. In my experience, ore than 80% of the questions are answered in the documentation (for the stuff I support). Of course, no one reads it, they want the answer spoon fed to them. Pathetic. If you're using complex software you damn well better read the documentation (yes, a lot of it is poorly written -- that's another thread). Web app servers, networks, different databases -- all these make the problem that much more complex. Another poster said "tell them to certify their products with the other software you want to use." This is a nice idea but if there's no business case for it it won't happen. If IBM is pushing WebSphere there's no real reason for them to bother certifying that Weblogic works with DB2. The answer is: read the documentation, keep up to date on the fixes and patches, and, when there is a problem (and there will be) send everything: the steps you took, the documentation you read, what you thought would happen, what did happen and provide data to back it up. More is better than less. As usual i've found another link that deals with this matter.
Slashdot Mirror
The Link is here.
Of course, in one sense, there if "no problem" but is he wants to use three different products then there will be inevitably. Paying IBM to support all of them is one option. .
As for the original question, there is no way to prevent one vendor from blaming another's product. The easiest way to get the problem resolved is to submit a detailed, accurate description of the problem, preferably with a test case, that demonstrates that the problem lies with one particular vendor.
I've done a lot of support and I can't tell you how many times people call and say "x is broken" and they don't describe the problem or provide any diagnostic data to support it. The first thing a support person is going to do is to throw it back at you and say "give me more detail." It's no wonder why people complain so much about support when they don't even help themselves in the first instance. In my experience, ore than 80% of the questions are answered in the documentation (for the stuff I support). Of course, no one reads it, they want the answer spoon fed to them. Pathetic.
If you're using complex software you damn well better read the documentation (yes, a lot of it is poorly written -- that's another thread).
Web app servers, networks, different databases -- all these make the problem that much more complex.
Another poster said "tell them to certify their products with the other software you want to use." This is a nice idea but if there's no business case for it it won't happen. If IBM is pushing WebSphere there's no real reason for them to bother certifying that Weblogic works with DB2. The answer is: read the documentation, keep up to date on the fixes and patches, and, when there is a problem (and there will be) send everything: the steps you took, the documentation you read, what you thought would happen, what did happen and provide data to back it up. More is better than less.
As usual i've found another link that deals with this matter