Iguana 5.5

What’s new in 5.5.5


Major enhancements

New Iguana Demo [top]

Upon product installation, you have the option to load four pre-built demo channels into your Iguana environment. These channels demonstrate some common integration tasks:

  • Reading and delivering messages
  • Translating and filtering messages
  • Mapping messages to a database
  • Creating a web service to respond to message requests

Additional Information

 

Improved HTTPS Settings [top]

To improve web service capabilities, we’ve made some enhancements to Iguana’s HTTP(S) settings:

New default setting

Before: When configuring a ‘From HTTPS’ source component, you must choose a method of connection. If you choose “Translator”, you must also browse to the Iguana Settings tab and change the ‘From HTTP Channels Server’ setting to “Use dedicated port”.

Now: Because we strongly recommend that you always choose “Translator” when creating a ‘From HTTPS’ source component, we’ve made “Use dedicated port” the default setting. This eliminates the cumbersome extra step.

New URL matching

Before:  When configuring a ‘From HTTPS’ source component, you must indicate which URL Iguana should listen on for incoming data/requests. Before, Iguana would search for an exact match before directing that incoming data to the channel. For example, let’s say that you assigned “/foo” to ChannelA, and “/foo/bar” to ChannelB. If Iguana received data from “/foo”, it knows to redirect it to ChannelA. When receiving data from “/foo/bar”, Iguana knows to redirect it to ChannelB. However, if Iguana received data from “/foo/bar/subpage”, it would not send it anywhere because there is no exact match.
Now: Iguana can identify which channel is assigned to what incoming data using directory-style subpath matching. For example, let’s say that you assigned “/foo” to ChannelA. Like before, when receiving data from “/foo”, Iguana knows to redirect it to ChannelA. With our new enhancement, Iguana also knows that data from “/foo/bar” and “/foo/bar/subpage” must also be directed to ChannelA.  This improvement means that you only have to set up one channel per root URL.

Note: If multiple channels are a potential match, Iguana will use the channel with the longest matching spec.

Additional Information

 

Leave A Comment?

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.