Configuration Differences in OpenAccess SDK Manager

The organization of the nodes is different in the client/server and local configurations because the local configuration does not require the OpenAccess SDK Agent.

In a client/server configuration, you make changes, such as adding a data service or data source, in the OpenAccess SDK Manager. These changes are sent to the agent that the OpenAccess SDK Manager is connected to. The agent writes these to the configuration file, by default, install_dir/cfg/oadm.ini.

In the following figure, the OpenAccess SDK Management Console shows a new data source:

In this configuration, the OpenAccessSDK810_Agent node is at the top of the tree, below the Manager SDK node.

A local configuration does not use an OpenAccess SDK Agent. The OpenAccess SDK configuration file is the top node under which the data services are listed:

In this configuration, the configuration changes you make in the OpenAccess SDK Manager are automatically added to the configuration file, by default, installdir/cfg/oadm.ini.