iNTERFACEWARE Products Manual > Installing and Using Iguana > Getting Started > Upgrading Iguana > Converting Multiple LLP Clients That Use The Same Port When Upgrading From Iguana 3.3 |
|
Looking for Iguana v.5 or v.6? Learn More or see the Help Center.
In Iguana 3.3, multiple channels that have LLP Client as their destination component could use the same port to transmit messages, and an additional channel with LLP Listener as its source component could read messages from this port. In Iguana 4.0 and later, multiple LLP Client destination components cannot use the same port. However, the same task can be accomplished using To Channel destination components and the From Channel source component:
If you are upgrading from Iguana 3.3 to the most recent version of Iguana, converting from the LLP Client/LLP Listener solution to the To Channel/From Channel solution is done automatically for you. If your ChannelConfiguration.xml file specifies multiple LLP Client destination components that use the same port, Iguana will convert these channels to use To Channel instead of LLP Client. The LLP Listener source component that reads messages from this port is converted to a From Channel source component. These conversions take place when you start the upgraded version of Iguana for the first time. For example, suppose that your Iguana 3.3 installation defines two channels named SendingChannel1 and SendingChannel2, and that both of these channels have LLP Client destination components that send messages to port 10000. Also, suppose that a third channel, ReceivingChannel, has an LLP Listener source component that listens for messages on port 10000. When you upgrade this installation to use the latest version of Iguana, these channels are converted as follows:
This conversion happens automatically when you start the upgraded Iguana server. After the conversion, messages are routed in the same way as before: the transmitting channels are still able to send messages to the same destination. An advantage of the newer method is that messages are logged more cleanly. When a message is written to the logs, its original transmitting channel is clearly identified. This makes it easier to detect when a transmitting channel is experiencing problems.
|