primarykvm.blogg.se - Openedge driver

Click OK to exit until no longer in the tool. If the test does not succeed, review your settings.ĩ. If the test succeeds, click on the OK button to complete the configuration.Ĩ.

Click on the Test Connect button to confirm that the details are correct.ħ. Note, you must use the service/port number and not the name.Ħ.

The Database Name on the selected server.

The Host Name and Port Number of the DBMS server.

Enter the following configuration details: Select the DataDirect/OpenEdge SQL or other appropriate Progress driver from the list. The Create New Data Source dialog displays, enabling you to add a new DSN.ģ. The ODBC Data Sources Administrator window displays. Select the Windows Control Panel | Administrative Tools | Data Sources (ODBC) option. It does not have a "stop a broker" option.The following assumes that Enterprise Architect is being used on a Windows platform.ġ. Proshut allows you stop the whole database or disconnect individual sessions. If that is running then the OE Explorer should work. If the admin server *is* running then type You might also find some evidence in the \OpenEdge\WRK folder (that is the default name for the work floder - it might have been changed.) Posting the extract of the 75 or so lines from the last (333) message might tell us. You could look at the dbname.lg (".lg" not ".log" as you typed above.) file and see if there is evidence one way or the other. That is more typical in a UNIX environment than Windows but it could be the case. This might be normal - it is possible that the application is "scripted" and not run using the admin server. If it is not then the OpenEdge Explorer tool will not function. This will tell you if the admin server is running or not.

This is a command line window that knows about the Progress tools and environment. Once you are on the db server you should be able to open a "proenv" window. You might be running the client on the same box as the server but it isn't obvious if you are or are not. The "broker rejects connection" message is a client side message. The admin server and OpenEdge Explorer run on the db server - not on the client. First of all make sure that you are logged in to the database server.