Dist with different Versions

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
3 posts • Page 1 of 1
a.bohne
Posts:3
Joined: Tue Apr 10, 2012 9:03 am

Dist with different Versions

Post by a.bohne »

In a distributed system I have a system with version 3.16 (system_99), the other system has version 3.8 (system_1). I did the entries in the config file like shown in the helpfile.
The systems seem connected but at the para of the 3.16-system I cannot see the 3.8-system. Surprisingly at the para of the 3.8-system I can see the 3.16-system.

3.8 config:
[general]
...
distributed = 1


3.16 config:
[general]
...
distributed = 1
mxProxy = "none"

[dist]
distPeer = "192.168.1.10" 1
mxProxy = "127.0.0.1 127.0.0.1 none"


What should I do that I Can see the 3.8-system at teh para of the 3.16-system? mxProxy-Manager is running. The log says: Connected to (SYS: 1 Dist -num 1 CONN: 1) @ XXXXXXXX (192.168.1.10)

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: Dist with different Versions

Post by leoknipp »

The dist connection possibly works when implementing the following solution in the project running 3.16:
-- Do a connect for the DPE _DistConnections.Dist.ManNums
If a connection is established this DPE is set by the Dist Manager. Every entry refers to the system number for a connected system.
-- The system number for a newly connected system is written to _DistManager.Command.RequestIdentification
If this DP element is set the identification is requested for the distributed system.

Best Regards
Leopold Knipp
Senior Support Specialist

a.bohne
Posts:3
Joined: Tue Apr 10, 2012 9:03 am

Re: Dist with different Versions

Post by a.bohne »

Thank you, with your solution the dist connection works fine

3 posts • Page 1 of 1