![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
For the last four weeks, we have been trying to upgrade an 'integration system' that lies between two communicating systems and passes their messages on. Rather like the post office trying to send mail.
We've been doing this slowly, upgrading the interface groups one at a time.
The first two were upgraded, no problem.
The third got stuck on a major change of message structure that they were performing at the same time as we were trying to upgrade. That doesn't go through until late July, so...we're stuck waiting on them.
The fourth...
We moved all the connections across and...promptly found it didn't work. It didn't help that to actually test this, we needed to borrown someone from the business who is BUSY and didn't have the time to hold our hand while we tried to fix things that were not working. So we applied for access. Twiddled our thumbs for a week (doing other things), then got the access. Applied for training. Twiddled our thumbs for a week while they worked out that we didn't want full formal training, just a basic 'how to do this thing' so we could kick a few messages around without having to pull a business person off work every time.
Once we had access and training, we were set!
Except that the connections weren't working. Our system was sending through New Server to the Receiving System, but the Receiving System was sending responsed back through Old Server.
So...Receiving System needs to change things up so they send back through New Server instead of Old Server, right?
No, we are told. Receiving System sends it back from whence it came, which means that Old Server must be hijacking New Server's messages, or New Server isn't set up properly. (Don't you love people who know your system better than you do? And by 'people', I mean 'men', and by 'love' I mean 'loathe'.)
Dude says this for FOUR WEEKS.
We ask for logs, he gives us logs and tells us that it's all working on his side. He tells us that his system - Receiving System - returns the message back to the IP address from which it came. He implies that we haven't set things up correctly, or haven't done our job right, and that it's nothing to do with him.
In the last week, he's gotten REALLY STRIDENT about this. Almost every message has the jab of "It's not me, it's you" underlying it. Even his messages this morning are blaming:
- "failed at your end?"
- "yes, but you know what is interesting..."
- "have you checked..."
And then at lunchtime, he announces that he has to create a new connection entirely for the New Server to point our connections to, so that the Receiving System will send things back through New Server.
FOUR WEEKS.
We sent another message through and this time we got a message back, although it was getting stuck when it came back on our end. So we did a small fix for that and BINGO. WE ARE COOKING WITH GAS!
There was, of course, no apology. There never is.
Just got a call from the system architect of the project, he's very 'chuffed' (his words; he's british background).
Then I get an email from Dude. "blah blah blah not convinced that the new queue creation is the cause of this".
So I sent receipts. With timestamps. And detailed instructions. And copied in the system architect and the business head who we've been working with.
Mate? You want receipts? I GOT RECEIPTS. You can't pin this on us and squirrel out of your responsibilities; our system logs EVERYTHING. All the messages we sent to you this morning that didn't work. When the old system connections were turned off, so it can't have been our system connections. When you created the new connections. When the messages started turning up from you...
FUCKER, YOU'VE BEEN STONEBALLING US FOR THE LAST MONTH. YOU COULD HAVE GRACEFULLY BOWED OUT AND ADMITTED THAT YOU COCKBLOCKED US ALL THE WAY. THE FACT THAT YOU DIDN'T? THAT YOU TRYNA PIN THIS ON US? IMMA SCORCH YOU TO THE GROUND, MATE. AND I'LL DO IT WITH MY FUCKING LIPSTICK PERFECT.
Oh, I was polite. Exquisitely polite. Maybe a little socially awkward, like explaining something to someone stupid. But he wanted proof. So I gave him proof.
We've been doing this slowly, upgrading the interface groups one at a time.
The first two were upgraded, no problem.
The third got stuck on a major change of message structure that they were performing at the same time as we were trying to upgrade. That doesn't go through until late July, so...we're stuck waiting on them.
The fourth...
We moved all the connections across and...promptly found it didn't work. It didn't help that to actually test this, we needed to borrown someone from the business who is BUSY and didn't have the time to hold our hand while we tried to fix things that were not working. So we applied for access. Twiddled our thumbs for a week (doing other things), then got the access. Applied for training. Twiddled our thumbs for a week while they worked out that we didn't want full formal training, just a basic 'how to do this thing' so we could kick a few messages around without having to pull a business person off work every time.
Once we had access and training, we were set!
Except that the connections weren't working. Our system was sending through New Server to the Receiving System, but the Receiving System was sending responsed back through Old Server.
So...Receiving System needs to change things up so they send back through New Server instead of Old Server, right?
No, we are told. Receiving System sends it back from whence it came, which means that Old Server must be hijacking New Server's messages, or New Server isn't set up properly. (Don't you love people who know your system better than you do? And by 'people', I mean 'men', and by 'love' I mean 'loathe'.)
Dude says this for FOUR WEEKS.
We ask for logs, he gives us logs and tells us that it's all working on his side. He tells us that his system - Receiving System - returns the message back to the IP address from which it came. He implies that we haven't set things up correctly, or haven't done our job right, and that it's nothing to do with him.
In the last week, he's gotten REALLY STRIDENT about this. Almost every message has the jab of "It's not me, it's you" underlying it. Even his messages this morning are blaming:
- "failed at your end?"
- "yes, but you know what is interesting..."
- "have you checked..."
And then at lunchtime, he announces that he has to create a new connection entirely for the New Server to point our connections to, so that the Receiving System will send things back through New Server.
FOUR WEEKS.
We sent another message through and this time we got a message back, although it was getting stuck when it came back on our end. So we did a small fix for that and BINGO. WE ARE COOKING WITH GAS!
There was, of course, no apology. There never is.
Just got a call from the system architect of the project, he's very 'chuffed' (his words; he's british background).
Then I get an email from Dude. "blah blah blah not convinced that the new queue creation is the cause of this".
So I sent receipts. With timestamps. And detailed instructions. And copied in the system architect and the business head who we've been working with.
Mate? You want receipts? I GOT RECEIPTS. You can't pin this on us and squirrel out of your responsibilities; our system logs EVERYTHING. All the messages we sent to you this morning that didn't work. When the old system connections were turned off, so it can't have been our system connections. When you created the new connections. When the messages started turning up from you...
FUCKER, YOU'VE BEEN STONEBALLING US FOR THE LAST MONTH. YOU COULD HAVE GRACEFULLY BOWED OUT AND ADMITTED THAT YOU COCKBLOCKED US ALL THE WAY. THE FACT THAT YOU DIDN'T? THAT YOU TRYNA PIN THIS ON US? IMMA SCORCH YOU TO THE GROUND, MATE. AND I'LL DO IT WITH MY FUCKING LIPSTICK PERFECT.
Oh, I was polite. Exquisitely polite. Maybe a little socially awkward, like explaining something to someone stupid. But he wanted proof. So I gave him proof.
Tags:
no subject
no subject
Nope. Not taking that.
no subject
no subject