Invoking the Command Line in a Client/Server Configuration

When invoking the OpenAccess SDK Management Command Line, you must choose whether you want the tool to connect to a local OpenAccess SDK Agent (an Agent service running on the same machine as the tool) or a remote OpenAccess SDK Agent (an Agent service running on another machine). If you have not connected to an OpenAccess SDK Agent, the OpenAccess SDK Management Command Line will return the following message when you issue a command:

You can invoke the OpenAccess SDK Management Command Line and connect to a local or remote Agent after you invoke the tool or invoke the tool as shown in the following examples:

Example A: Connecting to a Local or Remote OpenAccess SDK Agent After Invoking the Command Line

This example invokes the tool without specifying whether it will connect to a local or remote Agent. You must now explicitly connect to a local or remote OpenAccess SDK Agent using the ActivateLocalConfig or ActivateRemoteConfig commands described in OpenAccess SDK Manager Commands before you can enter any other commands.

Example B: Connecting to a Local OpenAccess SDK Agent When Invoking the Command Line

This example connects the tool to a local OpenAccess SDK Agent. The administrator will be prompted for the user ID and password for the OpenAccess SDK administrator. The administrator can now enter any OpenAccess SDK Manager command described in OpenAccess SDK Manager Commands.

Example C: Connecting to a Remote OpenAccess SDK Agent When Invoking the Tool

This example connects the tool to a remote Agent. The administrator will be prompted for the host name and port of the remote server. Then, the administrator will be prompted for the user ID and password for the OpenAccess SDK administrator. The administrator can now enter any OpenAccess SDK Manager command described in OpenAccess SDK Manager Commands.