OpenEdge Management explorer

Yahoo Archive
1
This was a bug with one of the installers.

You need to give each environment its own configuration for the 4GL
Clients.

You will find these files in the open edge / properties folder



Alternatively if it is a test environment, the latest media setup
routines should work correctly



Also as an aside, you can install PET on another machine and connect
remotely if required but OE Mange is now the Open Edge choice moving
forward.





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Techno Babbler
Sent: 06 January 2011 03:15
To: vantage
Subject: [Vantage] OpenEdge Management explorer





So I have a weird bug that I have not figured out and am Waiting for
Epicor
to get back to me on but I thought I would crowdsource here.

I have the OEManage application setup since I cannot use the PET on a
64bit
machine with the 64bit version of OpenEdge 10.2A on the machine.

I see 2 different things when I try to access the DBs to start them via
the
PET versus the OEManage tool.

If I look at the DB - DefaultConfiguration through the PET on another
server, then I see the normal 2 ODBCGroup and MfgSysGroups underneath
it.

However, if I go to the configuration.epicortrain.defaultconfiguration
page
in the OEManage tool, then I see 2 options in the Server Group
Properties
section at the bottom.
servergroup.epicortrain905.defaultconfiguration.odbcgroup and
servergroup.epicor905.defaultconfiguration.mfgsysgroup.

This is a problem because if I try to start Epicor905 it starts just
fine,
but if I try to start train, pilot, or test it gives me an error that
port
9400 is in use, but if I change the port in the mfgsysgroup, then it
changes
the port in the other 3 DBs as well.

Any idea why this would happen? I am going to uninstall and reinstall
the
OEManage tool, but not sure if that will actually have any effect on it.

This is a screen shot of the problem.

http://farm6.static.flickr.com/5003/5329178742_430e824a4d_o.png

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
2
So I have a weird bug that I have not figured out and am Waiting for Epicor
to get back to me on but I thought I would crowdsource here.

I have the OEManage application setup since I cannot use the PET on a 64bit
machine with the 64bit version of OpenEdge 10.2A on the machine.

I see 2 different things when I try to access the DBs to start them via the
PET versus the OEManage tool.


If I look at the DB - DefaultConfiguration through the PET on another
server, then I see the normal 2 ODBCGroup and MfgSysGroups underneath it.

However, if I go to the configuration.epicortrain.defaultconfiguration page
in the OEManage tool, then I see 2 options in the Server Group Properties
section at the bottom.
servergroup.epicortrain905.defaultconfiguration.odbcgroup and
servergroup.epicor905.defaultconfiguration.mfgsysgroup.

This is a problem because if I try to start Epicor905 it starts just fine,
but if I try to start train, pilot, or test it gives me an error that port
9400 is in use, but if I change the port in the mfgsysgroup, then it changes
the port in the other 3 DBs as well.

Any idea why this would happen? I am going to uninstall and reinstall the
OEManage tool, but not sure if that will actually have any effect on it.

This is a screen shot of the problem.

http://farm6.static.flickr.com/5003/5329178742_430e824a4d_o.png


[Non-text portions of this message have been removed]