Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

e*gate 3.6.2 -> e*gate 4.5.3

Status
Not open for further replies.

While

Programmer
Dec 8, 2003
2
GB
Hello,

Im currently working on a project to migrate from egate 3.6.2 (datagate) to egate 4.5.3.

Are there any tips/hints/lessons learnt that you could share pls.

Cheers,
Dean.
 
Be aware of JMS issues for 4.5.3 if this is on version 5 of unix. Contact Seebeyond for more info.

Also, when using JMS its best to set the expiry time of an event to Message Settings|MaxTimeToLive|value=2592000 secs(30 days). We have had issues where a subscriber component is shutdown and when restarted ignores the old events that were posted while the subscriber was down so watch out for that.

One last thing, when posting events to a queue if your using monk code, use (iq-initial-topic) instead of specific event names. Hopes this helps.
 
Non-java collaboration services can only have one subscription. I found this a bit of a pain with bidirectional Monk eWays.

Also empty the output buffer after iq-put - prevents empty data (ie (delimiters only) being published for your default event type.

Good luck!
 
Hi I want to implement e-gate in my company but I need programmers for that in Belgium, do you know anyone?

Cheers,

Tim b
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top