wM v8.x for MIS replacement

Hi,

I was wondering if anyone went through a migration or replacement for their MIS connectivity when upgrading to wM v8.x. Basically, did you go with EntireX from SAG or purchase a third-party to enable the mainframe for web services. We have MIS for CICS connectivity and a custom adapter for IDMS.

We just moved from 7.1.2 to 8.0 and in our case, the team from Mainframe exposes us the WSDL (generated from Rational rose dev) and we are consuming them to send\receive data to\from CICS. The client did not want to use the EntireX adapter to communicate with Mainframe (not sure why!). No issues so far!

Cheers,
Akshith

Thanks Akshith. How long did it take you guys to upgrade/migrate from 7.1.2 to v8? Did you upgrade on top of v7.1.2? Did the upgrade in parellel? How long did it take? How long did it take for you to replace MIS to more of a web services solution?

how long did it take you guys to upgrade/migrate from 7.1.2 to v8?

About a month. This includes the 8.0 installation, DB components installation (nightmare), migrating the Application code and testing the code. I did an upgrade for a client not long ago from 6.1 to 7.1.2 and compared to that this migration was fun, easy and quick!

Did you upgrade on top of v7.1.2?

No, we did the upgrade in parallel. We were supposed to get rid of our old boxes (hosting WM) so we started with a fresh install on the new boxes.

How long did it take for you to replace MIS to more of a web services solution?

We started using web services from 7.1.2 itself and did not have to do anything new in 8.0.

Cheers,
Akshith

Akshith,

How long did it take to upgrade from 6.x to 7.x?

There were lot of components in that project like IS,TN,Broker,SAP Adapters (I had to rewrite lot of code and create RFCs. Client used to use routing calls earlier.),DB’s (moving from MSSQL 2000 to 2005),Workflow server and Process manager aka MWS. Also this project had a deliverable to add some additional code to handle new partners in TN. Altogether it took somewhere around 6 months to move but we had to spend another 3 months to fix the deprecated items from 6.1 to 7.1.2 and get a sign off.

Trying to get a working env which had MSSQL jobs and stored procedures for archiving Core Audit, Process Audit and TN itself took a month and we had issues with TN and had to get a TN DOC fix from SAG.

Over all it took about 9 months starting from scratch to the time the project went to Production, it was a fixed bid for us.

Cheers,
Akshith

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.