This guide is intended to help customers prepare for the smoothest transition to IguanaX, guiding you through the first steps in migrating your existing Iguana v6 channels to IguanaX components. Our migration tools are evolving as we work with customers on their unique Iguana use cases.
Here are a few steps to set up your environment and get started with our migration tools before meeting with us to review your IguanaX environment:
Export your Iguana v6 channels to a Git repository with your Git service provider.
If you do not have one, then you can set up a free account with Bitbucket or Github.
If you have not done this before, we’ve prepared this guide for how to do it: Exporting Iguana 6 code to a Repository. Let us know if you need additional help!
Some customers have tried to share git repos with GitLabs - although you can import IguanaX components from any git repository - it unfortunately has not be the smoothest platform to work with in our experience.
Add any environmental variables used by your channels to IguanaX.
See Environment Variables for where and how to add these in IguanaX.
Import and run the channel converter in IguanaX to convert your version 6 channels
Follow along the steps to import the tool into IguanaX and give it a try: Iguana 6 Channel Importer
It’s guaranteed to not 100% successfully convert your channels the first time you run it, but this is an important step for us to identify what the problems are and get moving on addressing them. Every time we go through this process with a customer we found we have been able to improve our process. We are trying to move quickly to identify and solve problems.
If you’re interested in having our team work directly with you on your migration path, contact support@interfaceware.com. You can provide us access to your Iguana 6 channels using one of the following methods:
1) Give us access to the cloud git repository with your channels
This step entails copying the SSH link (ex. git@bitbucket.org:johndoe/iguanaxrepo.git) and sending it to us. Please ensure that your repository is public so that we may pull the channels into Iguana X for testing (this change is made on Bitbucket or Github).
Of course be super careful not to put any Patient Health Information (PHI) in this repo. But making your channels available means we can move a lot faster to help make sure your interfaces will port over to IguanaX easily. If you need some help getting this configured let us know.
Additional information we will need to setup our environment...
Make sure every Translator that needs sample data contains at least one good sample data message so we can see how the channel is supposed to run. Just remember no real PHI please!
A list of environment variables used by your channels - one of the best practices is to document these variables in your translator components. It’s really helpful.
Looking forward to working with you! Together we make our lives better by making to possible to transition to a cleaner simpler and more reliable way of building and maintaining interfaces.