Making ODB Slick and Easy

Das Goravani goravanis at
Fri Sep 9 17:24:24 UTC 2022

Dear List,

When attempting to use the Omnis DataBridge at client sites, you are faced with a few tricky issues. I am wondering how you resolve these.

One is on the server: The ODB has a config.xml file. In it must be the PATH to your ODB Datafile(s). So this has to be edited for each site unless you force a certain location of the datafile, in a place where the path name is always the same exactly, in which case you could distribute one version of the xml file to all your users.

What do you do about this?

The other thing is that on the client’s machine you also have to deal with knowing the IP address of the server and the datafile’s name BEFORE you log on. So how do you deal with that?

The IP address and port can go into the Preference Property for same. Then they are there, and are used by Omnis, allowing you to write shorter addresses for example when you log on.

But you have to get that property into that slot so that it’s there.. and to that end you are, or are not, logged on..

It seems to me that you have to have a pre-log-on part of your program, which senses if ODB has been set up yet on the client machine, and allows for the user to enter the IP address, port, and datafile name(s), and because you are not logged on this data would have to be stored and accessed for example from Startup_task  $userinfo.. which is a place you can store anything and you don’t have to be logged on to access it.

Any input on how you handle these ODB issues is appreciated. 



More information about the omnisdev-en mailing list