This topic contains 1 reply, has 2 voices, and was last updated by  Eliot Muir 3 years, 10 months ago.

Strategy question: Upgrading Iguana across multiple machines

  • We have a fairly large number of Iguana instances, but they are installed on CPE distributed across many customer sites. All of them are older versions (between 4.0.14 and 4.5.7) using Python VMDs. I am preparing a migration plan to get all of them up to 5.5.6 and using translator scripts. I’m curious about what would be considered “best practice” in accomplishing this.

    My current plan is to bring up a second Iguana instance on each CPE, and rewrite the interface code in the translator. Fortunately, most of our interfaces are rather simple HL7 parsers mostly concerned with ADT, so I think it’s reasonable to do a from-scratch rewrite using LUA. Once we’ve tested the new version and confirmed the output is the same as the existing Python-based interface, we can change the channels so the one on the 4.x box doesn’t respond, while the 5.5 does, and that should be a wrap for the migration.

    Thoughts?

    -Robert James,
    Interface Analyst,
    GetWellNetwork, Inc.

    Seems the right approach – I always encourage upgrades to be done in this manner.

You must be logged in to reply to this topic.