| Author |
Message
|
| scravr |
 Posted: Wed Jan 31, 2024 12:21 am Post subject: WMB 7 Migration to ACE 12 |
 |
|
Partisan
Joined: 03 Apr 2003
Posts: 388
Location: NY NY USA 10021
|
HI Guys.
I started working with MQSI V1 over 20yrs ago....
and now i have one of these strange Q:
I got a call to join a new project migrating WMB7 to ACE12.
Should I take it or it will be too crazy difficult.
Whats the simplest and fastest steps to go through?
Thank You
MA |
|
| Back to top |
|
 |
| zpat |
| Posted: Wed Jan 31, 2024 4:47 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
I am sure your experience will guide you.
I would assume - do NOT upgrade existing brokers in place.
Build new brokers and then migrate the applications to them by an export and import process. Testing in parallel before cutover.
IBM docs will list restrictions on flow migration between v7 to v8 to v9 to v10 to v11 to v12.
Simple and/or fast are not terms I would use for this.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| joebuckeye |
| Posted: Wed Jan 31, 2024 7:51 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 364
Location: Columbus, OH
|
| I think some of the biggest potential headaches will be things that were add-in nodes for v7 that either became real nodes in a later version or simply no longer exist for the more recent versions and will need something to replace them. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Feb 01, 2024 5:26 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9400
Location: US: west coast, almost. Otherwise, enroute.
|
Moved to Broker forum
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| missing_link |
| Posted: Thu Feb 01, 2024 6:04 am Post subject: |
|
|
Acolyte
Joined: 08 Jan 2004
Posts: 59
|
My previous client was doing exactly that....moving from v7 (on prem) to v11/v12 (on Open Shift) - a complete re-architecting of the integration platform.
As mentioned above - need to export projects from v7 and import to v12. There will be specific product differences (i.e. converting to applications and libraries).
Ignoring any specific platform and framework changes, the biggest challenges from a purely code perspective (from what i remember) were Mapping nodes and SAP Adapters. |
|
| Back to top |
|
|
| scravr |
| Posted: Sat Feb 03, 2024 3:15 am Post subject: |
|
|
Partisan
Joined: 03 Apr 2003
Posts: 388
Location: NY NY USA 10021
|
| missing_link wrote: |
My previous client was doing exactly that....moving from v7 (on prem) to v11/v12 (on Open Shift) - a complete re-architecting of the integration platform.
As mentioned above - need to export projects from v7 and import to v12. There will be specific product differences (i.e. converting to applications and libraries).
Ignoring any specific platform and framework changes, the biggest challenges from a purely code perspective (from what i remember) were Mapping nodes and SAP Adapters. |
on https://www.ibm.com/docs/en/app-connect/12.0?topic=migration-behavioral-changes-in-version-120
it say mapping and DB nodes are not supported any mote on ace 12.
how export-7/import-12 will work with these nodes? |
|
| Back to top |
|
|
| missing_link |
| Posted: Mon Feb 05, 2024 7:34 am Post subject: |
|
|
Acolyte
Joined: 08 Jan 2004
Posts: 59
|
[quote="scravr"][quote="missing_link"]My previous client was doing exactly that....moving from v7 (on prem) to v11/v12 (on Open Shift) - a complete re-architecting of the integration platform.
As mentioned above - need to export projects from v7 and import to v12. There will be specific product differences (i.e. converting to applications and libraries).
Ignoring any specific platform and framework changes, the biggest challenges from a purely code perspective (from what i remember) were Mapping nodes and SAP Adapters.[/quote]
on https://www.ibm.com/docs/en/app-connect/12.0?topic=migration-behavioral-changes-in-version-120
it say mapping and DB nodes are not supported any mote on ace 12.
how export-7/import-12 will work with these nodes?[/quote]
try it and see?
for mapping nodes you'll need to go through whatever steps are necessary to convert the v7 nodes to the v12 mapping nodes - or you can get rid of them and export the maps to ESQL via the v7 plugin.
is there anything that you can do in those database nodes that can't be done in a compute node? There are still some database nodes, there are specific ones that no longer exist. |
|
| Back to top |
|
|
| joebuckeye |
| Posted: Mon Feb 05, 2024 11:44 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 364
Location: Columbus, OH
|
| missing_link wrote: |
| for mapping nodes you'll need to go through whatever steps are necessary to convert the v7 nodes to the v12 mapping nodes - or you can get rid of them and export the maps to ESQL via the v7 plugin. |
Way back when we migrated from v5 to v6 (or was it v6 to v7?) we were bitten by mapping node issues, so it was decided we were no longer allowed to use mapping nodes so all of our transformations since then have been in ESQL or XSLT or <shudder> WTX/ITX.
Can't say I disagree with that decision as we've never had to worry about that sort of issue since. |
|
| Back to top |
|
|
| scravr |
| Posted: Mon Feb 05, 2024 12:21 pm Post subject: |
|
|
Partisan
Joined: 03 Apr 2003
Posts: 388
Location: NY NY USA 10021
|
| joebuckeye wrote: |
| missing_link wrote: |
| for mapping nodes you'll need to go through whatever steps are necessary to convert the v7 nodes to the v12 mapping nodes - or you can get rid of them and export the maps to ESQL via the v7 plugin. |
Way back when we migrated from v5 to v6 (or was it v6 to v7?) we were bitten by mapping node issues, so it was decided we were no longer allowed to use mapping nodes so all of our transformations since then have been in ESQL or XSLT or <shudder> WTX/ITX.
Can't say I disagree with that decision as we've never had to worry about that sort of issue since. |
Right. Never liked mapping and DB nodes.
I remember re-write mapping when migrated from v7 to v8 long ago.
I guess I need to do it again !!! |
|
| Back to top |
|
|
| missing_link |
| Posted: Tue Feb 06, 2024 12:10 am Post subject: |
|
|
Acolyte
Joined: 08 Jan 2004
Posts: 59
|
[quote="joebuckeye"][quote="missing_link"]for mapping nodes you'll need to go through whatever steps are necessary to convert the v7 nodes to the v12 mapping nodes - or you can get rid of them and export the maps to ESQL via the v7 plugin.[/quote]
Way back when we migrated from v5 to v6 (or was it v6 to v7?) we were bitten by mapping node issues, so it was decided we were no longer allowed to use mapping nodes so all of our transformations since then have been in ESQL or XSLT or <shudder> WTX/ITX.
Can't say I disagree with that decision as we've never had to worry about that sort of issue since.[/quote]
Same!! Created one in v5, then rewrote in ESQL when we migrated to v6.1. Have never written another one!!
For the v7 to v11 migration, we exported them as ESQL - problem solved!  |
|
| Back to top |
|
|
|
|
