Easysoft ODBC-ODBC Bridge

Can I run the OOB Server on UNIX without the inetd SuperServer?

Article:
00059
Last Reviewed:
28th October 2008
Revision:
2

Yes. By default the OOB Server for UNIX is installed as a service with entries in the /etc/services and /etc/inetd.conf files (inetd is informed of the configuration file changes)(OOB also supports xinetd). However, the OOB Server for UNIX will run standalone as well. To run the OOB Server standalone you need to either:

[1] use a different port address from the entry in /etc/services for
esoobserver. Edit
<install_path>/easysoft/oob/server/esoobserver.ini and change the
entry "Port = 8888" to specify a different port.

[2] comment out the esoobserver entries in /etc/services and
/etc/inetd.conf and send a SIGHUP to inetd.

Once you have done the above you start the server by changing directory to <install_path>/easysoft/oob/server and issuing the following command:

./esoobserver standalone

The server will start listening for connections on the Port specified in the esoobserver.ini file. You should really start the OOB Server as root or it will be unable to change to the LogonUser specified in the OOB client DSN. However, if you do not start the OOB Server as root then no logon authentication will be performed and all clients will run on the server as the user who started the OOB Server.

You can add a line to start the OOB Server standalone to one of your rc scripts to have the OOB Server start up every time the machine boots. The file you need to change depends on your Operating System so it is best to consult your system administrator. On RedHat for Linux a good place is /etc/rc.d/rc.local.

When the OOB server is started standalone it will by default fork a process to handle HTTP requests on port 8890 (this can be changed in the esoobserver.ini file). You can then use your browser to contact the OOB HTTP server using http://machine.domain:8890 and see connection statistics, configurable parameters and access control. If you want to change configurable parameters or access control via the HTTP interface you must define HTTPAdmin in the esoobserver.ini to an existing user on your machine and you will need to enter the password when viewing/making_changes on some protected pages. In this case the OOB Server must be running as root on some machines to verify the username/password.

Applies To

Knowledge Base Feedback

* Did this content help you?
* Please select one option based on your first choice:

(* Required Fields)


Oracle is a registered trademark of Oracle Corporation and/or its affiliates.