Configuration target

Specify whether to configure the local client or the Business Connector proxy.

Configuration

Specify the name of the current group of settings for this client instance. This can be stored in the registry or as a file.

Manage

Open a menu with the following options:

• Open configuration file- Open a file containing configuration settings.

  Note
  Although you can use the Opencommand to view a saved configuration, Dynamics does not store the settings from the opened file to the registry. To save settings from a configuration file to the registry, you must use the Importcommand.

• Close configuration file- Close open configuration file.

• Save configuration as file- Save current configuration to a file. Use this command to store an offline copy of the settings you have been using.

• Import configuration from a file- Import a configuration to the registry that has been stored to a file. You can save imported configurations to the registry.

• Export configuration to a file- Export a configuration to a file when you want to copy it to a client on another computer.

• Export all configurations to a file- Export all configurations to a file when you want to copy all the configurations from one client instance to another computer.

• Create configuration- Create a new configuration using the Create configuration (form) (Server)dialog box. You can create a new configuration based on the currently-selected configuration, or the default configuration that shipped with Microsoft Dynamics AX.

• Delete configuration- Delete the current configuration.

• Rename configuration- Rename the current configuration.

General

Set startup options for a client here, including log directory location, company to open, commands to run on startup, and any messages to display.

Connection

Set the AOS instance to connect to, and connection options for that instance.

Developer

Set development options, including whether to allow debugging in the client or the Application Object Tree (AOT) layer to open by default. You can also enter a development license code to access the AOT at a customer location that does not have a development license.

Tracing

Specify traces to run to help monitor and tune Microsoft Dynamics AX performance.

Add

Open the Add Application Object Server instancedialog box to add an AOS to the list of available instances.

Edit

Edit an AOS instance.

Delete

Delete an AOS instance from the list of available instances.

Move up arrow

Click to move the selected instance higher in the list.

Move down arrow

Click to move the selected instance lower in the list.

Log directory

Specify an alternate directory for the log files generated when you make changes in the AOT.

Company

Specify the company that holds data for your application.

Command to run at application startup

Enter a SysStartupCmd method to run when this client application starts. Use SysStartupCmd commands with caution, because they not evaluated before being passed to the client. For details about SysStartupCmd methods, see Execute Startup Commands.

Configuration command to run at kernel startup

Enter a configuration command to run when this client kernel starts. Use configuration commands with caution, because they not evaluated before being passed to the client. For details about configuration commands, see Configuration commands (Client).

Startup message

Specify text to display in a message box when Microsoft Dynamics AX starts.

Server name

Name of computer running AOS.

Instance name

Name of AOS instance.

TCP/IP port

TCP/IP port that AOS instance communicates on.

Connect to printers on the server

Allow client to connect to printers on the AOS computer. Similar settings must be set on the AOS instance to enable this functionality.

Encrypt client to server communication

Encrypt all data sent between this client and the AOS.

Enable user breakpoints to debug code running in the Business Connector

For sessions owned by users for whom debug is enabled within Microsoft Dynamics AX, allow X++ code running in the Business Connector to be interrupted by breakpoints

Enable global breakpoints to debug code running in the Business Connector or client

For all users, allow X++ code running in the Business Connector or client to be interrupted by global breakpoints. To debug Business Connector, you must set both debug options. To debug the client, set only this option

Application object layer to open

Select the layer to open by default in the AOT.

Development license code

Enter your development license code for accessing the AOT.

Confirm license code

Retype your development license code.

RPC round trips to server

Trace all remote procedure call (RPC) round trips to the server that are triggered by this client.

X++ method calls

Trace all X++ methods that are invoked on the server and triggered by this client.

Number of nested calls:

Limit tracing to a specific number of nested method calls.

Function calls

Trace all function calls that are invoked on the server and triggered by this client.

SQL statements

Trace all Microsoft SQL Server statements that are triggered by this client.

Bind variables

Trace all columns that are used as input bind variables.

Row fetch

Trace all rows that are fetched using SQL Server triggered by this client.

Row fetch summary (count and time)

Count all rows that are fetched and record the time spent fetching.

Connect and disconnect

Trace each time the AOS is triggered by this client to connect to or disconnect from the database.

Transactions: TTSBegin, TTSCommit, TTSAbort

Trace all transactions that are triggered by this client and use the TTSBegin, TTSCommit, and TTSAbortstatements.

Enable method tracing to client desktop

Trace all X++ method calls made from this client and log them to the desktop on the client computer.