AX Server Configuration (form) [AX 2012]

AX Server Configuration (form) [AX 2012]

Click System administration > Setup > System > Server configuration.

Use this form to set up an AOS instance as a batch server or a load-balancing server. You can also use the form to change performance settings and cache limits for all AOS instances, or cache limits for a single AOS instance.

A batch server is an Application Object Server (AOS) instance that processes batch jobs. The first AOS to be set up is automatically designated as a batch server. You can designate additional servers, and you can specify when each server is available. Use multiple batch servers to increase throughput and reduce the time that is required to run batches.

A load-balancing server is an AOS instance that balances the load of client connections to Microsoft Dynamics AX. An AOS instance set to be a load-balancing server does not host any client sessions. Instead, it regulates the load among other AOS instances.

The following tables provide descriptions for the controls in this form.

Tabs 

Tab	Description
Batch server schedule	View or change when the selected AOS instance is available for running batch jobs.
Batch server groups	Specify which batch groups can be run on the selected batch server.
Performance Optimization	Specify performance and cache limit settings for all AOS instances, or cache limit settings for a single AOS instance.

Fields

Field	Description
AOS instance name	The name of the AOS instance, in the format InstanceName@ServerName.
Is batch server	Select this check box to set the AOS instance to be used as a batch server.
Load balancer	Select this check box to set the AOS instance to be used as a dedicated load balancing server. When this option is selected, the AOS instance will not host any client sessions. Instead, it regulates the load among other AOS instances.
Max concurrent sessions	The number of total threads for batch tasks or client sessions that can run at the same time on this server.
Cluster name	The name of the load balancing cluster that the selected AOS instance belongs to.
Maximum batch threads	The number of threads for batch tasks that can run on the selected server at the specified time.
Start time	The time when the batch server becomes available to run batch jobs.
End time	The time when the batch server is no longer available to run batch jobs.
Selected groups	The batch groups that can run on this batch server.
Remaining groups	The available batch groups that are not assigned to this batch server.
Error on invalid field access	Determines system behavior when SELECT statements access fields that have not been explicitly selected. If the value of this field is set to 0, no error is generated. If the value of this field is set to 1, an error is generated.
Error on exceeding maximum number of tables in join	Determines the behavior when the number of joins in a table exceeds the maximum number of joins allowed. If the value is set to 1, an error will be generated. If the value is set to 0, a warning will be generated.
Maximum number of tables in join	The maximum number of tables allowed in a JOIN statement. Note If this limit is exceeded, a message is displayed, but application logic continues to run.
Client record cache factor	The value used to determine the relationship between the number of elements in the record cache stored on the server and the number of elements stored in the Windows client record cache. For example, if the cache limit for the Framework table group is 2000 and the cache factor is 20, then 2000 elements can be saved in the record cache on the server, but only 100 (2000 divided by 20) elements can be saved in the record cache on the client.
Entire table cache size	Size beyond which the table cache will be flushed to disk.
Global Object Cache elements	Number of elements that can be stored in the Global Object Cache.
Record cache elements for Framework table group	Number of elements that can be stored in the record cache for the Framework table group.
Record cache elements for Parameter table group	Number of elements that can be stored in the record cache for the Parameter table group.
Record cache elements for Reference Table group	Number of elements that can be stored in the record cache for the Reference table group.
Record cache elements for Group table group	Number of elements that can be stored in the record cache for the Group table group.
Record cache elements for Main table group	Number of elements that can be stored in the record cache for the Main table group.
Record cache elements for Miscellaneous table group	Number of elements that can be stored in the record cache for the Miscellaneous table group.
Record cache elements for Transaction table group	Number of elements that can be stored in the record cache for the Transaction table group.
Record cache elements for Transaction Header table group	Number of elements that can be stored in the record cache for the Transaction Header table group.
Record cache elements for Transaction Line table group	Number of elements that can be stored in the record cache for the Transaction Line table group.
Record cache elements for Worksheet table group	Number of elements that can be stored in the record cache for the Worksheet table group.
Record cache elements for Worksheet Header table group	Number of elements that can be stored in the record cache for the Worksheet Header table group.
Record cache elements for Worksheet Line table group	Number of elements that can be stored in the record cache for the Worksheet Line table group.

 

Setting

Manage batch execution AX 2012

Manage batch execution AX 2012

The final step in implementing a batch job is to manage the execution process. Before a batch job can be executed on an AOS instance, you must configure the AOS instance as a batch server and set up the batch groups that tell the system which AOS instance should execute the job.
In addition to these initial configuration tasks, you’ll likely need to manage the batch tasks and jobs: checking status, reviewing history, and sometimes canceling a batch job. You’ll probably also need to debug a batch task at some point.

The following sections describe how to configure an AOS instance as a batch server and set up batch groups, and the next 2 posts will describe manage batch jobs and debug a batch task.

Configure the batch server

You can configure an AOS instance to be a batch server, including specifying when the batch server is available for processing and how many tasks it can run, by using the Server Configuration form.
The Server Configuration form is located at System Administration > Setup > System > Server Configuration.
Note that the first AOS instance is automatically designated as a batch server, but you can configure additional AOS instances manually as batch servers.

Tip Use multiple batch servers to enable parallel processing and increase processing throughput.

1. In the Server Configuration form, select a server in the left pane.
2. Select the Is Batch Server check box to enable batch processing on the server, as shown in Figure below.

3. On the Batch Server Schedule FastTab, click Add to enter a new schedule. Enter the maximum number of batch tasks that can be run on the AOS instance at one time. The server continues to pick up tasks from the queue until it reaches its maximum.
4. Enter a starting time in Start Time and an ending time in End Time to specify the time window in which the server processes batch jobs. Press Ctrl+N to enter an additional time window.

Tip It’s a good idea to exclude a server from batch processing when it is busy processing regular transactions. You can set server schedules so that each AOS instance is available for user traffic during the day and batch traffic overnight. Keep in mind that if the server
is running a task when its batch processing availability ends, the task continues running to completion. However, the server doesn’t pick up any more tasks from the queue.

Create a batch group

A batch group is a logical categorization of batch tasks that lets a user (typically a system administrator) determine which AOS instance runs the batch task. This section describes how to create a batch group so that it can be assigned to a specific server for execution. The first step is to create batch groups by using the Batch Group form at System Administration > Setup > Batch Group.

To create a batch group, press Ctrl+N in the Batch Group form, and then type a name and description for the batch group. The Batch Group form is shown in below

Note By default, the system contains an empty batch group that can’t be removed. This is a default batch group for tasks that are not explicitly assigned to a group. 

After you create batch groups, assign each group to a server as follows:
1. In the Server Configuration form (shown in Figure below), click the Batch Server Groups FastTab.
The Selected Groups list shows the batch groups specified to run on the selected server.
2. In the Remaining Groups list, select a group, and then click the left arrow button to add this group to run on the selected server.

Note  you can assign each group to a server using Batch Servers in Batch Group form

Imparted from Inside Dynamics AX 2012 Book