Setting Up an OpenAccess SDK Service and Data Source for your IP
A client connects to your data source by connecting to an OpenAccess SDK Service that has been configured to access your data source through the IP code you are developing. The OpenAccess SDK installation sets up a service OpenAccessSDK810_NET and installs a template OpenAccess SDK 8.1 Service for .NET. It is recommended that you use the existing service OpenAccessSDK810_NET and create a data source entry under it instead of trying to create a new service.
You must configure the following Service and Data Source settings to load your IP code and to make it available when a connection is received by the OpenAccess SDK Server. See the OpenAccess SDK Administrator’s Guide for a detailed explanation of all the service and data source attributes that are used to configure an IP for the OpenAccess SDK SQL Engine.
• DataSourceIPType – DAMIP.
• DataSourceIPClass – name of the IP class that is implementing the oanet.sql.ip interface (for example damip.dll). The IP class must reside in the install_dir\ip\bin folder.
• DataSourceIPSchemaPath – full path of the directory containing the schema for your IP (for example C:\Program Files\DataDirect\oaserver81\ip\schema\yourip. The OpenAccess SDK SQL Engine stores the schema for the IP in the files contained in this directory.
• DataSourceLogonMethod – if you want your IP to authenticate based on user name and password passed in from the client, then you set this data source attribute to DBMSLogon(UID,PWD); otherwise, leave it set to Anonymous.
Refer to the OpenAccess SDK Administrator’s Guide for information about how to configure a new data source or to set up a new OpenAccess SDK service for your IP based on the provided .NET template. Initially, you should use the existing OpenAccessSDK810_NET service and add a data source for configuring your IP. Assuming you call this data source yourip, the OpenAccess SDK Client references the yourip data source entry within the OpenAccessSDK810_NET service.
Note: You must stop and restart the service for configuration changes to take effect and each time the IP class is recompiled.
