Both editions are used with authenticated SQL Anywhere applications, as defined here: http://dcx.sybase.com/index.html#sa160/en/dbadmin/running-s-4314706.html.
The 'Authenticated' edition is used when the authenticated application needs to pass the correct authentication string to the database in order of perform write operations. If the app does not do that, then the connection to the db is read-only. You obtain the authentication string by completing a form on our web site.
The 'OEM' edition is used when your application cannot pass an authentication string to the database, but requires write access. In this case, the connection has R/W permission and there's no need to pass an authentication string.
Which edition you are allowed to deploy depends on your SQL Anywhere contract. From a technical perspective, both editions are identical, with the exception of the authentication mechanism used when a db connection is established.
answered 08 Mar '13, 10:04
OEM edition: This is actually something a Partner needs to discuss with their
Sales Representative since the details may vary and has more to do with
contractual terms than software technology. But, for what it is worth, my
understanding is this.
There are many possible ways to embed the SQL Anywhere software so that it can only be used with the Var/OEM/Partner's application(s). Anyone can chose to do this for any one of many possible reasons but my understanding is something like this would be required of the OEM Edition sales agreement. In contrast the Authenticated Edition is just the main SW mechanism we provide for this purpose.
At least that is the outline as I understand it. Your sales representative can explain the finer details.
answered 11 Mar '13, 15:01
Nick Elson S...