| Author |
Message
|
| DRM |
 Posted: Wed May 15, 2013 5:21 am Post subject: WMB 8 (FP1) builds and deployments |
 |
|
Newbie
Joined: 18 Apr 2013
Posts: 6
|
We are migrating from WMB 6.1 (FP9) to WMB 8 (FP1). We need to keep both versions running while we incrementally migrate services. Does anyone have any reasons why we should not build using our 6.1 process and deploy common code to both version 6.1 brokers and version 8 brokers?
I can see if we use new features (DFDL models for one), that 6.1 would not be able to build. But I am really looking to see if there are any underlying caveauts in deploying flows or jars built in 6.1 to 8.0.0.1 |
|
| Back to top |
|
 |
| DRM |
| Posted: Thu May 16, 2013 11:43 am Post subject: |
|
|
Newbie
Joined: 18 Apr 2013
Posts: 6
|
| No thoughts on this at all? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu May 16, 2013 12:06 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
What does the IBM documentation say about running different Versions of Broker?
What research have you done?
If you want an Official IBM Answer, you will need to raise a PMR.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu May 16, 2013 1:44 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I agree with smdavies - this should be clearly documented, and probably is.
I would also strongly recommend that you go straight to 8.0.0.2, which has been available for a while now. |
|
| Back to top |
|
|
| DRM |
| Posted: Thu May 16, 2013 1:50 pm Post subject: |
|
|
Newbie
Joined: 18 Apr 2013
Posts: 6
|
I am not sure if we'll go to 8.0.0.2, some internal policy. Still I have been able to find only migration information. My question is what issues or gotchas can happen if you build a bar in 6.1 and deploy to V8.
I cannot seem to find any information about that scenario. I have asked our IBM MQ/Broker specialist, but have not received a reply yet. |
|
| Back to top |
|
|
| huwgb |
| Posted: Thu May 16, 2013 4:03 pm Post subject: |
|
|
Novice
Joined: 07 May 2013
Posts: 21
|
We just went through this process.
Deployed 6.1 bar files onto WMB 8.0.0.1 broker (fp2 came out too late in the cycle to upgrade to)
We installed 8.0.0.1 onto new servers, brought down the old server, swapped IP addresses and brought up the new servers.
Most of our technical issues resulted from badly written code. Details below:
ASBITSTREAM function changed behaviour between 6.1 and 8.0.0.1:
Where 6.1 would accept an invalid MessageFormat ('XML1') and still function. 8.0.0.1 through an exception (valid formats were 'XML' or '' in our situation).
WMB 6.1 successfully parsed XMLNSC messages (With no validation) where the MessageSet was referred to by it's MRM ID Number. WMB 8.1 returned an exception (As it should) until we changed the code to refer to the Message Set name.
SAP JCO adapter 2.1.8 would allow a message to go through where the message contents did not match the interface (Too many decimal places). SAP JCO Adapter 3.0.x returned an exception (As it should have). Re-discovering the adapters did not make a difference.
Changes between MQ versions:
SSL OCSP/AIA lookups were turned on by default in WMQ 7.5, we had not configured it in the previous release so we got SSL exceptions until we disabled it (with a plan to re-enable it once we figure out what is needed)
After the IP Switchover we had to refresh the cluster repository to make the clustered queue managers point to the new IP addresses.
There were other minor issues but the majority of our problems were due to badly written code that still (somehow) worked in WMB 6.1. |
|
| Back to top |
|
|
|
|
