Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

This is something we are building out incrementally starting with a few customers. It’s evolving and proving very helpful in helping us figure out how we can streamline the conversion process.

 You'll need 10.1.81 or newer - this video shows how the converter is meant to run
 So far we are having success with the converter

We’ve successfully helped a few customers use the converter. It’s been extremely helpful in quickly identifying issues we need to address to help them port over.

If you want to try this - please reach out and we can arrange a Zoom to try it with you - well be happy to walk you through it.

 Create a component using +FROM URL - use git@bitbucket.org:interfaceware/iguanaconverter.git
git@bitbucket.org:interfaceware/iguanaconverter.git

This the component repository:

https://bitbucket.org/interfaceware/iguanaconverter/

 Edit the custom GitRepo component property to point to a channel export from Iguana 6

Another good repo to try is:

https://bitbucket.org/interfaceware/export

or in copy paste-able form:

https://bitbucket.org/interfaceware/export

The default for this is currently:

https://github.com/interfaceware/iguana-tools

or copy paste-able:

https://github.com/interfaceware/iguana-tools

Funnily enough most of the ‘tools’ in this repo no longer make sense in the context of Iguana X. But it’s a helpful starting point for my conversion prototype work.

 Run the component to import and convert all the Iguana 6 channels into components.

It should generate a link a number of components corresponding to your channels.

 From reading the code of the converter how could a more detailed map of LLP server components be done?

Go have a look at CHAN/CHANllpSource.lua

This code has the mapping of configuration information from Iguana 6 into Iguana X.

 Some areas that we are expanding on

This is a work in progress. What we are doing is going through a practical process of exploring how in practice customers use Iguana. What are the important use patterns that we have to make easy to bring across into the new system.

We aim to quickly identify our customers can get the majority of their interfaces ported over in a smooth safe fashion.

 Where is this going?

We are optimistic we can automate most of the work in converting Iguana 6 to Iguana X code. Doing the conversion in this way is very powerful since it will give final control to each customer to go the last mile in terms of doing the conversion in manner which helps you each get the best conversion possible.

It makes it possible to customize the script to target specific problems that might only impact on your user cases of Iguana. More to say about that later.

For now we are working with a number of customers to use this tool to accelerate the process of identifying and eliminating gaps and making Iguana X a practical platform to migrate to.

  • No labels