Hi experts,

we plan to sell our software together with OEM licences of
iAnywhere so we need to setup athenticated servers. I've
some technical questions about authentocated servers:

1.) Where is the authentication implemented, in the database file
or in the server installation?

2.) What are the consequences for the usage of iAnywhere
tools and software with a authenticated server? Can I use
ISQL, SC and so on with such a database without problems?
What about synchronisation, how to connect dbmlsrv and
dbmlsync to an authenticated server?

3.) I use PowerBuilder and Infomaker to maintain customer
databases. Is that possible with an autheticated database too?

4.) Are there other problems or drawbacks using authenticated
database which I haven't considered so far?

TIA

Chris Werner
f+s software gmbh

Chris

we use this now for a couple of years without problems. For additional
details check out the help files under "Running authenticated SQL
Anywhere applications"

1) It's in the database. You set the option in the database by script
and identify your software uppon connecting.

2) ISQL and SC don't need any authentication. I don't know what's with
synchronization.

3) Yes, when you use the developer edition of SQL Anywhere

4) To get it up and running ;-).

Regards
Arthur



Chris Werner wrote:

The server engine must be an authenticated version. So, technically it
is both.

The tools are self-authenticating - provided that the database has been
configured with the database_authentication option. Note that ISQL and
SC are not freely deployeable. Check you specific licensing if you plan
to deploy.

Yes. You can set the database authentication string in PB application
connections. IM requires you to set the InitString. Examples are in the
documentation.


Make sure that you configure the authenticate.sql if you are needing to
initialize new databases with an authenticated engine.

-chris



Arthur Hefti wrote: