| Author |
Message
|
| emiddleware |
 Posted: Mon Mar 09, 2015 3:09 am Post subject: Migration plan from WMB v6 to IIB v9 |
 |
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
Hi,
Before we migrate our application to IIB v9 , our client wants to validate certain points.
1) To review the IBM IIB Environment and list the pros and cons of migration from WMB v6 to IIB v9
2)To understand if migrating to IIB will provide us with any added benefit of a more advanced development environment. As an exercise, we should also know the effort required for migration.
3) How to estimate the efforts required for migration ?
Thanks.
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Mar 09, 2015 4:20 am Post subject: Re: Migration plan from WMB v6 to IIB v9 |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| emiddleware wrote: |
Hi,
Before we migrate our application to IIB v9 , our client wants to validate certain points.
1) To review the IBM IIB Environment and list the pros and cons of migration from WMB v6 to IIB v9
2)To understand if migrating to IIB will provide us with any added benefit of a more advanced development environment. As an exercise, we should also know the effort required for migration.
3) How to estimate the efforts required for migration ?
Thanks. |
How about moving off an unsupported version to a supported version?
This alone should be enough incentive. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Mar 09, 2015 4:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Yes, it sounds like your client understands very well what they wish you to accomplish.
If you were hoping for someone to provide you with a detailed and step-by-step guide to accomplishing these things, I strongly suspect you will be disappointed.
There's really no reason to migrate from MB v6 to IIBv9, unless the customer wants to be assured that they can receive support from IBM, run the product on modern platforms and modern OS versions, connect to SSL enabled endpoints with current and secure protocols and ciphers, be able to connect to a significantly wider set of endpoints with a significantly improved development experience.
But of course, you know all of this already and have told them this. |
|
| Back to top |
|
|
| emiddleware |
| Posted: Sun Mar 15, 2015 9:46 pm Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
I have some queries related to migration from WMB v6 to IIB v9
1) Message SETS can be ported without effort, but changes may require rebuild in DFDL format -? True ?
2) Message FLOWS can be ported without issue - True ?
3) I have webservices implemented in my existing system in WAS. How can migrate that implementation in IIB v9 ?
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Mar 16, 2015 3:35 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| 1) Message SETS can be ported without effort, but changes may require rebuild in DFDL format -? True ? |
False. Message sets can still be edited in IIB. DFDL is a better technology, but message sets are not deprecated and probably never will be.
| Quote: |
| 2) Message FLOWS can be ported without issue - True ? |
True. But you will be advising your client to run their regression tests on the IIB system before deploying in production, of course 
| Quote: |
| 3) I have webservices implemented in my existing system in WAS. How can migrate that implementation in IIB v9 ? |
By re-implementing them in IIB. See the knowledge center for details of web services support in IIB.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| joebuckeye |
| Posted: Mon Mar 16, 2015 5:27 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 365
Location: Columbus, OH
|
| emiddleware wrote: |
| 2) Message FLOWS can be ported without issue - True ? |
As long as your v6 message flows aren't using any plug-in nodes you should be fine.
If they use plug-in nodes then you will have to see how the functionality provided by the those nodes is handled in IIB. |
|
| Back to top |
|
|
| emiddleware |
| Posted: Tue Mar 17, 2015 2:30 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
I am investigation two more factors for migration.
1) Webservices
2) Pub-sub model.
1) Webservices - > We have WAS and IBM HTTP Server. I am not sure where the webservices are hosted.. But I know that the operations are defined and the vendors put their invoices in the server location. The connector picks up the file. The Webservices role comes here. Via this, the message will be put into JMS. Here the message is converted and put into the IBM MQ. Then the WMB message flow gets triggered.
So, how do I migrate these webservices to IIB ? Do I have to re-create the WSDLs once again ?
2) Pub-sub model - > The messaging architecture is used as pub-sub model. The message is published to various destinations.. In IIB, its taken care by MQ v.5 ... How do I accomplish at architecture level, even if its mentioned in Knowledge central.
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 17, 2015 4:50 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| emiddleware wrote: |
| 1) Webservices - > We have WAS and IBM HTTP Server. I am not sure where the webservices are hosted.. |
Well you should probably figure that out before you start migrating things!
| emiddleware wrote: |
| The connector picks up the file. The Webservices role comes here. |
So you do know where the webservice is hosted. All you now need to do is define what you mean by "the connector" - the broker connector? The broker proxy connector exported to WAS? Connector code running natively in WAS? We can't know if you don't tell us.
| emiddleware wrote: |
| Via this, the message will be put into JMS. Here the message is converted and put into the IBM MQ. Then the WMB message flow gets triggered. |
So wherever the webservice is running, it's not running in WMB because the flow isn't triggered until the webservice puts the message to the queue?
| emiddleware wrote: |
| So, how do I migrate these webservices to IIB ? Do I have to re-create the WSDLs once again ? |
And yet now you say the webservices are in WMB and need to migrate. This is very confusing, and I think part of that is you don't seem to have a clear handle on how the current set up is laid out.
If the current WSDLs are in WMB, they'll be in message sets and migrate like any other message set. If that's where they are.
| emiddleware wrote: |
| 2) Pub-sub model - > The messaging architecture is used as pub-sub model. The message is published to various destinations.. In IIB, its taken care by MQ v.5 ... How do I accomplish at architecture level, even if its mentioned in Knowledge central. |
I'll assume you mean MQv7.5 and that's just a simple typo. They don't make keybaords like they used to.....
You accomplish this like you used to accomplish this. The only difference is that in v6.0 the pub/sub engine was in the broker, in IIB it's in the queue manager the broker is sitting on. So your pub/sub topology / heirarchy / cluster / whatever you're using is identical because you have exactly the same number of v7.5 queue managers as you had v6.0 brokers in exactly the same topology / heirarchy / whatever assuming you're just changing the software level.
It's just configured in WMQ not WMB. And documented in the WMQ InfoCenter. IIB code will publish on the same topics it always did. Sorted.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Mar 17, 2015 5:09 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Vitor wrote: |
You accomplish this like you used to accomplish this. The only difference is that in v6.0 the pub/sub engine was in the broker, in IIB it's in the queue manager the broker is sitting on. So your pub/sub topology / heirarchy / cluster / whatever you're using is identical because you have exactly the same number of v7.5 queue managers as you had v6.0 brokers in exactly the same topology / hierarchy / whatever assuming you're just changing the software level.
It's just configured in WMQ not WMB. And documented in the WMQ InfoCenter. IIB code will publish on the same topics it always did. Sorted. |
And remember in V6 you had all the pub/sub hierarchy set up at the broker level (IIRC). You may / will have to do that setup at the queue manager level. I suggest you read up on the migration documents an look specifically for the pub/sub section. There used to be some scripts in broker 7.x for this. Don't know if they are still there in IIB 9. You may end up being more comfortable with doing a manual setup of pub /sub, especially if doing a side by side upgrade. If we're talking about some of the more exotic master/slave pub/sub models and such I would encourage you to revisit the setup docs both in MQ and broker and make sure you fully understand this, and test it, before going into a live environment...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| emiddleware |
| Posted: Tue Mar 17, 2015 10:34 pm Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
| Vitor wrote: |
| emiddleware wrote: |
| 1) Webservices - > We have WAS and IBM HTTP Server. I am not sure where the webservices are hosted.. |
| Quote: |
| Well you should probably figure that out before you start migrating things! |
I see the WSDL files are present in WMB. I see the operations defined.
| emiddleware wrote: |
| The connector picks up the file. The Webservices role comes here. |
| Quote: |
| So you do know where the webservice is hosted. All you now need to do is define what you mean by "the connector" - the broker connector? The broker proxy connector exported to WAS? Connector code running natively in WAS? We can't know if you don't tell us. |
The connector and adapter all is by a thirdparty - by another company called Equinox. The connector runs in a separate Linux box. WAS,WMQ and WMB runs together in another separate Linux box.
| emiddleware wrote: |
| Via this, the message will be put into JMS. Here the message is converted and put into the IBM MQ. Then the WMB message flow gets triggered. |
So wherever the webservice is running, it's not running in WMB because the flow isn't triggered until the webservice puts the message to the queue?
| emiddleware wrote: |
| So, how do I migrate these webservices to IIB ? Do I have to re-create the WSDLs once again ? |
| Quote: |
| And yet now you say the webservices are in WMB and need to migrate. This is very confusing, and I think part of that is you don't seem to have a clear handle on how the current set up is laid out. |
True. I am still understanding the architecture. Now I find that the WSDLs are created in WMB. When I see the production support document, a webservices recycle, Config manager is involved. So 100% sure that its created in WMB.
If the current WSDLs are in WMB, they'll be in message sets and migrate like any other message set. If that's where they are.
| emiddleware wrote: |
| 2) Pub-sub model - > The messaging architecture is used as pub-sub model. The message is published to various destinations.. In IIB, its taken care by MQ v.5 ... How do I accomplish at architecture level, even if its mentioned in Knowledge central. |
I'll assume you mean MQv7.5 and that's just a simple typo. They don't make keybaords like they used to.....
You accomplish this like you used to accomplish this. The only difference is that in v6.0 the pub/sub engine was in the broker, in IIB it's in the queue manager the broker is sitting on. So your pub/sub topology / heirarchy / cluster / whatever you're using is identical because you have exactly the same number of v7.5 queue managers as you had v6.0 brokers in exactly the same topology / heirarchy / whatever assuming you're just changing the software level.
It's just configured in WMQ not WMB. And documented in the WMQ InfoCenter. IIB code will publish on the same topics it always did. Sorted. |
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| emiddleware |
| Posted: Tue Mar 24, 2015 3:35 am Post subject: Regarding Configuration manager Proxy |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
Hi All,
I had imported the artifacts of WMB into IIB v9.
For one commonflow, the build path was showing error for Configmanagerproxy.jar.
I searched for the jar but its not available.
As there is no concept of configmanager in IIB, how to manage this ?
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Mar 24, 2015 4:31 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
ConfigManagerProxy.jar is there in 9.0.0.2 (note the spelling)
it is in the %MQSI_FILEPATH%\Classes directory (on Windows at least)
_________________
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 |
|
|
| emiddleware |
| Posted: Tue Mar 24, 2015 5:44 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
Thanks smdavies... Got it.. Now checking for other jar's buildpath.... many thanks..
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| emiddleware |
| Posted: Fri Apr 10, 2015 1:52 am Post subject: Importing WSDL from WMB 6.1 to IIB v9 |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
Hi,
In WMB v6.1 there is a message flow project called ABCServices which contains many message flows and also WSDLs.
I imported this message flow project as Integration project in IIB v9 toolkit.
I get error like
The resource 'ABCServicesV0.5.1.wsdl' cannot belong in Message Broker project 'ABCService'. This resource can belong within an Application or Library. ABCServicesV0.5.1.wsdl /ABCService/wsdl Unknown Message Broker Project Resource Problem
By right clicking on the error , I choose the quickfix option. It leads me to converting to 'Application' or 'Library'. I don't want to go to these options as I have many references to other message flow projects. If I conver 'ABCService' to Application or Library, I can't make references...
How do I seperate the WSDLs from this message flow project ? Kindly guide me . Thanks.
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Apr 10, 2015 2:26 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I'd go back to V6 and start there.
Create a nessage set project and copy the WSDL files etc into that.
Delete the files from the flow project and create a reference in the flow project so that it 'links' to the Message Set.
Then you can export BOTH projects and import them into IIB 9.
Then go through the steps of converting them to a Library (the message set) and an Application (the flow).
_________________
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 |
|
|
|
|
