Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    2
  • Subscribers subscribers
    4
  • Views views
    170
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Running 2 Versions of Novell Messenger Side by Side

MigrationDeletedUser
We are attempting to run Messenger 2.2 (Production) and Messenger 3.0 (Development) Side by side, so that we can test the new version, without removing the test group's ability to talk to the users on our current production messenger server. I thought that creating a virtual app for 3.0 would be a good solution, as we have used virtualization to run applications side by side in the past.
This does not appear to work however. I have tried doing this with one version installed, and one virtualized, and with both virtualized, but the result is the same: Whatever version is run first becomes the functioning version. Attempting to run the second version just brings the other version up. It would seem that they are sharing some protocol..
Is there a solution for this? Has anyone had two versions of messenger running together?

Thanks
  • 0
    I'm guessing you couldn't have both running simultaneously unless you could configure the beta Messenger server to communicate on a different port but that's just a guess on mu part. Make sure the "Enable window class isolation" option is checked under "Settings
    |Process Configuration" in ZAV when you build the app.
  • 0 in reply to 
    You can run the two clients, connecting to two different servers, both on 8300.

    Thanks for the windows class isolation tip...forgot about this, and that's exactly what I needed.

    dholmesscsd;2341702 wrote:
    I'm guessing you couldn't have both running simultaneously unless you could configure the beta Messenger server to communicate on a different port but that's just a guess on mu part. Make sure the "Enable window class isolation" option is checked under "Settings
    |Process Configuration" in ZAV when you build the app.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.