Dollar Universe Manager for Microsoft Dynamics AX 2012 User Guide

Version: 6.7.21 Publication Date: 2016-11 Automic Software GmbH

ii | Copyright

Copyright Automic® and the Automic logo® are trademarks owned by Automic Software GmbH (Automic). All such trademarks can be used by permission only and are subject to the written license terms. This software/computer program is proprietary and confidential to Automic Software and is only available for access and use under approved written license terms. This software/computer program is further protected by copyright laws, international treaties and other domestic and international laws and any unauthorized access or use gives rise to civil and criminal penalties. Unauthorized copying or other reproduction of any form (in whole or in part), disassembly, decompilation, reverse engineering, modification, and development of any derivative works are all strictly prohibited, and any party or person engaging in such will be prosecuted by Automic Software. No liability is accepted for any changes, mistakes, printing or production errors. Reproduction in whole or in part without permission is prohibited. © Copyright Automic Software GmbH. All rights reserved. Other names may be trademarks of their respective holders.

Dollar Universe Manager for Microsoft Dynamics AX 2012 User Guide | iii

Contents 1 Release Notes ...................................................................................................................... 5 2 Introduction .......................................................................................................................... 6 2.1 Overview ......................................................................................................................... 6 2.2 Features .......................................................................................................................... 6 2.2.1 Job Submission ........................................................................................................ 6 2.2.2 Job Monitoring .......................................................................................................... 7 2.3 Technical Organization ................................................................................................... 7 2.3.1 Communication Mechanisms ................................................................................... 7 2.3.2 Microsoft Dynamics AX Batch Job ........................................................................... 7 2.3.3 Automatic Start-up of an AX Batch Job .................................................................... 8 2.4 Dollar Universe / Microsoft Dynamics AX Interface ........................................................ 9 2.5 Triggering and Monitoring Microsoft Dynamics AX Jobs ................................................ 9 3 Installation .......................................................................................................................... 12 3.1 Requirements ............................................................................................................... 12 3.2 Installing Dollar Universe Manager for Microsoft Dynamics AX ................................... 12 3.2.1 Directory structure .................................................................................................. 12 3.3 Upgrading Dollar Universe Manager for Microsoft Dynamics AX ................................ 12 4 Configuration ..................................................................................................................... 13 4.1 Users Configuration ...................................................................................................... 13 4.2 Automatic Start-up of a Batch Group ............................................................................ 13 4.2.1 Checking Automatic Batch Group Execution ......................................................... 14 4.2.2 Correcting the SysStartupCmdBatchRun Class ..................................................... 14 4.3 Administering the Manager for Microsoft Dynamics AX ............................................... 14 4.3.1 User License ........................................................................................................... 14 4.3.2 Start/Stop the Manager for Microsoft Dynamics AX ............................................... 15 4.4 Manager for Microsoft Dynamics AX Node Settings .................................................... 15 4.5 Manager for Microsoft Dynamics AX Logging .............................................................. 16 5 UniViewer Console ............................................................................................................ 17 5.1 Sample Uproc ............................................................................................................... 17 5.1.1 Sample Uproc’s Variables ...................................................................................... 17 5.1.2 Update the Uproc ................................................................................................... 18 5.1.3 AX Companies and Dollar Universe Management Units ....................................... 19 5.2 Managing AX Batch Jobs ............................................................................................. 19 5.2.1 Launching the Microsoft Dynamics AX Batch Job.................................................. 19 5.2.2 Monitoring the Microsoft Dynamics AX Batch Job ................................................. 19 6 Commands ......................................................................................................................... 22 6.1 Automatic Creation of Uprocs to Start AX Batch Jobs ................................................. 22 6.1.1 Extract the List of Batch Jobs ................................................................................. 22 6.1.2 Uproc Creator ......................................................................................................... 23 6.2 uxstrax Command......................................................................................................... 25

iv | Contents

7 Troubleshooting ................................................................................................................. 28 7.1 Troubleshooting Tool .................................................................................................... 29 8 About Automic Software, Community and Services ...................................................... 30 8.1 Automic Software Company ......................................................................................... 30 8.2 Automic Community...................................................................................................... 30 8.3 Download Center .......................................................................................................... 30 8.4 Technical Support ......................................................................................................... 31 8.5 Training and Services ................................................................................................... 31

Chapter 1 Release Notes | 5

1 Release Notes The following is the change history. Information on bug-fixes and known errors is available in the Dollar Universe Release Notes and by contacting Automic Technical Support. Date

Key Features

2014-11

Dollar Universe user guides change their look to integrate the Automic world.

2015-12

Correction of the variables types description in the Node Settings.

2016-11

New node setting, Uproc variable, and uxstrax command parameter to bypass the check of the number of running AOS.

6 | Chapter 2 Introduction

2 Introduction Welcome to the Dollar Universe Manager for Microsoft Dynamics AX 2012 User Guide! This guide addresses the needs of those who will install, configure and use the Dollar Universe Manager for Microsoft Dynamics AX 2012. It is assumed that the reader is familiar with Dollar Universe, UniViewer, Microsoft Dynamics AX 2012 and the .NET Business Connector technology. This guide details the installation, configuration, administration and use of Dollar Universe Manager for Microsoft Dynamics AX 2012.

2.1 Overview This guide describes the technical data and functions of Dollar Universe Manager for Microsoft Dynamics AX 2012. It details the installation, configuration, administration and utilization of Dollar Universe Manager for Microsoft Dynamics AX 2012. To provide coherent overall management of batch processing in the corporate information system, Dollar Universe Solutions proposes integration packages with most standard software solutions. These integration packages are meant to handle batch jobs delivered by all types of applications, whether in-house developments or standard software packages. For Microsoft® Dynamics AX 2012, primary objective of the Dollar Universe Manager for Microsoft Dynamics AX 2012 is to manage Dynamics AX batch operations from Dollar Universe: 

Scheduling AX jobs



Triggering AX jobs



Monitoring and control

The Dollar Universe Manager for Microsoft Dynamics AX 2012 manages AX jobs that have already been created in AX 2012.

2.2 Features The Dollar Universe Manager for Microsoft Dynamics AX provides the following features: 

Starts an AX Batch Job which is waiting to run.



Monitors the execution of the AX Batch Job and provides an overall status for tasks in the AX Batch Job.



Generates intermediate and final reports for tasks in the AX Batch Job. The Manager retrieves an infolog for each AX task. All reports are found in the job log of the Uproc which triggered the AX Batch Job.

A dedicated sample Uproc is delivered with the Dollar Universe Manager for AX. Users simply select the Axapta sample Uproc when creating a new Uproc which will trigger an AX Batch Job.

2.2.1 Job Submission The handling AX Batch Job execution in Dollar Universe is synchronous: the Dollar Universe Uproc waits for the AX Batch Job to complete.

Chapter 2 Introduction | 7

The Manager does not actually submit AX Batch Jobs to the AX Batch Job List, it simply triggers their execution. The AX Batch Job should be prepared and entered into the AX Batch Job List with the appropriate parameters independently of Dollar Universe. AX jobs scheduled and monitored by Dollar Universe must be saved in the Batch Job History. Check the Log Level status of each job: it should be set to the value corresponding to “Always save job in batch history”.

2.2.2 Job Monitoring Microsoft Dynamics AX Batch Job completion codes are: 

Retrieved from the BATCHJOB table,



Returned to the Dollar Universe Uproc that triggered the AX Batch Job.

The AX Uproc polls the AX Batch Job to check its progress. Polling output is returned to the AX Uproc job log. Once the AX Batch Job has completed, overall status and final reports (infolog) are also returned to the AX Uproc job log.

2.3 Technical Organization 2.3.1 Communication Mechanisms Communication between the Manager and Microsoft Dynamics AX is implemented via the following mechanisms: 

The .NET Business Connector provided by Microsoft Dynamics AX in the DLL Microsoft.Dynamics.BusinessConnector.dll is used to run queries against the AX database (whatever the database type), and execute static AX class methods. This component has to be installed and configured on the machine where Dollar Universe and the Manager for AX are running. The path to the file Microsoft.Dynamics.BusinessConnector.dll must be part of the %PATH% environment variable of Dollar Universe.



The AX client (ax32.exe) continues to perform batch execution for tasks that need to run on the client. If no AX task is targeted on AX client, the AX client is not required to be installed on the host running Dollar Universe and the Manager.

2.3.2 Microsoft Dynamics AX Batch Job Several variables are provided in the AX sample Uproc; the main one being the identifier of the target AX Batch Job. In Microsoft Dynamics AX, a Batch Job is a list of several tasks that run in batch mode. Tasks may be made dependent on other tasks in the same AX Batch Job to determine the overall task execution order in the AX Batch Job. AX Batch Jobs are managed from Main menu > Basic tab > Inquiries/Batch job. Each task is designed to run either on an Application Object Server (AOS) or on a client. In addition, it will be assigned to an AX Batch Group, which may in turn be associated to one or more AOS. 

For server-side tasks, the AX Batch Group determines the AOS on which the task will run.



For client-side tasks, the AX Batch Group triggers the execution of all “Ready” tasks. The execution of client-side tasks is supported in AX but is not recommended.

8 | Chapter 2 Introduction

When an AX Batch Job is started, Microsoft Dynamics AX executes all AOS tasks in the Batch Job and sets all clients task states to “Ready”. The client-side tasks can then be started manually in Main menu > Basic tab > Periodic/Batch/Processing. The completion status of a Batch Job is either Ended or Error.

2.3.3 Automatic Start-up of an AX Batch Job To start an AX Batch Job: 

If the job has no recurrence, the initial status of the AX job must be “Waiting”.



If it is scheduled for a future date and time, set its scheduled start date and time to current date and time.

2.3.3.1 Execution of AX Tasks on the AOS Tasks designed to run on the AOS (server-side tasks) are automatically executed by AX when the AX Batch Job starts.

2.3.3.2 Execution of AX Tasks on the Client Client-side tasks are launched by running an instance of the AX client program (ax32.exe) in the AX client Bin directory. The AX client program expects the name of the Batch Group to be started as an argument. Once the Batch Group has started, AX scans the Batch Group for tasks in the “Ready” status. To ensure that a Batch Group is started automatically by the AX client, the SysStartupCmdBatchRun class must be checked: the Group ID received as an argument must be passed to the BatchRun object. Refer to section "Automatic Start-up of a Batch Group" on page 13 to find out how to check the SysStartupCmdBatchRun class. The command line that manages the Microsoft Dynamics AX client is: :\axapta_client\Bin\ax32.exe [] -startupcmd=Batch_

Where: 

is the Drive where the Microsoft Dynamics AX client is located,



is the full path of the AX configuration file used to connect to Microsoft Dynamics AX,



is the name of the Batch Group to be started automatically.

Example 1: To start the Batch Group TEST using the myconfig configuration to connect with AX, enters the command: c:\axapta_client\Bin\ax32.exe c:\axapta_client\Bin\myconfig.axc startupcmd=Batch_TEST

-

Example 2: To start the Batch Group TEST using the default configuration to connect with AX, runs the command: c:\axapta_client\Bin\ax32.exe -startupcmd=Batch_TEST

The configuration file is optional. If not specified, the default configuration will be used.

Chapter 2 Introduction | 9

2.4 Dollar Universe / Microsoft Dynamics AX Interface The architecture can be broken down into six component parts: 

Dollar Universe: the job scheduling solution, designed to automate enterprise batch jobs, with comprehensive user interfaces to define and monitor jobs across the network, for all types of applications, for all types of operating systems.



The Dollar Universe Manager for Microsoft Dynamics AX: a set of commands which handle the submission and supervision of AX Batch Jobs.



AX Batch Jobs: a logical grouping of tasks (containing classes that run either on a client or on a server).



AX client program: the program that executes the tasks designed to run on the client.



AX Application Object Server (AOS): the middle tier where application objects, such as queries and classes, are executed, as well as the tasks designed to run on the server.



AX Database Server: Microsoft Dynamics AX database managed by an RDBMS (Oracle or Microsoft SQL Server).

Figure 1: Outline of interface with Microsoft Dynamics AX

2.5 Triggering and Monitoring Microsoft Dynamics AX Jobs This section covers the different actions implicit in the Batch job trigger program uxstrax. Refer to the section “uxstrax Command” on page 25 for its syntax and return codes. The Uproc sample delivered by the product is built upon the uxstrax command that executes the following steps: 1. Connects to Microsoft Dynamics AX Using the .NET connector, the uxstrax creates a connection to Microsoft Dynamics AX. If the connection is refused, the command exits with an error status. 2. Retrieves the list of client-side tasks in the Batch Job

10 | Chapter 2 Introduction

The AX Batch Job ID is defined in the Uproc variable UAX_JOBID. A job can also be identified by its description defined in the Uproc variable UAX_JOBCAPTION if the Job ID is not provided. As two or more jobs in AX can share the same description, it is recommended to use the variable UAX_JOBID. If neither of these variables is defined, if no job with the identifier UAX_JOBID is found or if no job, or more than one job, is found with the caption UAX_JOBCAPTION the command exits in error. The command retrieves the identifiers (with their associated Batch Groups) of all the clientside tasks in the AX Batch Job. If there are any private client-side tasks in the AX Batch Job that cannot be executed by the current user, the command uxstrax exits in error. 3. Starts the AX Batch Job The status of the AX Batch Job is set to “Waiting” and the scheduled start date/time is overwritten with the current date and time. 4. Starts the associated Batch Groups For each AX Batch Group retrieved which is not associated to an AOS, the Microsoft Dynamics AX client (ax32.exe) is started in a new system process to which the Batch Group ID is passed as a command line argument. If the Microsoft Dynamics AX client fails to start, the command uxstrax exits in error. The access path to the Microsoft Dynamics AX client is held in the Dollar Universe Node Settings under the “Manager for Dynamics Axapta” category. It needs to be filled with the Full path of the ax32.exe program file. 5. Monitors the AX Batch Job The uxstrax command monitors the progression of the AX Batch Job and all its component tasks. The AX Batch Job is monitored until the AX Batch Job completes or the uxstrax command times out. The examination cycle (10 seconds by default) is defined by the Uproc variable UAX_JOBCTLCYCLE. If this variable is not defined, the default value in the Manager node settings is used: “Database polling cycle in seconds”. The maximum value of the examination window is defined by the Uproc variable UAX_JOBEXECTIMEOUT. If this variable is not defined, the default value is set in the Manager node settings: “Timeout for a Batch Job execution”. Cycles and timeout values are expressed in seconds. The Manager node settings are detailed in the section "Manager for Microsoft Dynamics AX Node Settings" on page 15. 6. Stops the Batch Groups If the AX client program was launched to run client-side tasks, it stops as soon as the Batch Job completes or the program times out. 7. Displays intermediate and final reports Intermediate reports are displayed in the Uproc job log by the uxstrax command. When polling is over, a final report is generated. For each AX task, the following information is displayed: - Completion status - Start date/time - End date/time - The user that created the task - The AX company - The record identifier of the task - The execution location (Client or Server)

Chapter 2 Introduction | 11

- Presence (or not) of the infolog generated by Microsoft Dynamics AX for the task - The class name Once the job has completed, the command retrieves any “infolog” information generated by the task. The infolog is displayed in the job log together with the basic information listed above. The Uproc variable UAX_JOBKEEPLOGERR determines if infolog data should be retrieved for aborted tasks. If this variable is not defined, the default value in the Manager node settings is used: "Recovers infolog at AX aborted jobs into job log". The Uproc variable UAX_JOBLEEPLOGOK determines if infolog data should be retrieved for completed tasks. If this variable is not defined, the default value in the Manager node settings is used: "Recovers infolog of AX ended jobs into job log". Infologs of all the AX tasks are accumulated in the Uproc job log. The data stored is in user readable ASCII format. 8. Handles timeout If the execution timeout is exceeded, the command uxstrax cancels the running batch job by setting its status to “Canceling”. The program then monitors that the job is properly canceled by Microsoft Dynamics AX. The time allowed for a job to be canceled is defined in the Uproc variable UAX_JOBSTOPTIMEOUT. If this variable is not defined, the default value in the Manager node settings is used: “Timeout for Batch Job cancellation”. If the cancelation of the job exceeds this timeout, the command uxstrax forces the status of the job to “Canceled” and exits in error. 9. End of processing: The command disconnects from Microsoft Dynamics AX.

12 | Chapter 3 Installation

3 Installation This chapter details the Dollar Universe Manager for Microsoft Dynamics AX installation, and upgrade.

3.1 Requirements For more information on supported operating systems and compatibility with other Dollar Universe products, refer to the "compatibility matrix" which can be found on the Customer Service website in the Content tab. The Manager accesses objects and databases tables via the Microsoft Dynamics AX Business Connector; it therefore needs access to the .NET Business Connector. This implies the installation of .NET 3.5 SP 1. If it is intended to manage client side tasks, the Microsoft Dynamics AX client is installed on the same machine as the Manager.

3.2 Installing Dollar Universe Manager for Microsoft Dynamics AX The Dollar Universe Manager for Microsoft Dynamics AX is automatically installed during Dollar Universe installation.

3.2.1 Directory structure The installation procedure creates a subdirectory called bin_axapta in the bin directory of the Dollar Universe Company. The Dollar Universe Manager for Microsoft Dynamics AX commands are copied to the bin_axapta subdirectory. The installation procedure inserts a Uproc sample (axapta_template_*.clint) into the bin/clints directory of the Dollar Universe Company.

3.3 Upgrading Dollar Universe Manager for Microsoft Dynamics AX The upgrade of Dollar Universe Manager for Microsoft Dynamics AX from Dollar Universe V5 to Dollar Universe V6 Manager for Microsoft Dynamics AX is described in the Dollar Universe Upgrade Guide. For minor releases, Dollar Universe v6 Manager for Microsoft Dynamics AX is upgraded once the Dollar Universe V6 upgrade has completed. In an update to version 6.1 and up, if the path to the Microsoft.Dynamics.BusinessConnectorNet.dll library is not present in the registry, you must define the node setting UNI_AX_DLL_PATH (refer to section "Manager for Microsoft Dynamics AX Node Settings" on page 15.

Chapter 4 Configuration | 13

4 Configuration This chapter describes the required configuration for Dollar Universe Manager for Microsoft Dynamics AX in Microsoft Dynamics AX and Dollar Universe.

4.1 Users Configuration The Dollar Universe submission account used for AX jobs must exist in Microsoft Dynamics AX. To launch a Microsoft Dynamics AX Batch job from a Dollar Universe AX Uproc: 

Create a submission account in the Dollar Universe objects corresponding to the user in Microsoft Dynamics AX under which Batch Jobs should be executed. Make sure you also select system user and fill in the credentials to create the corresponding user service. Please refer to the UniViewer User Guide for how to create a Dollar Universe submission account with a corresponding Windows service.



If you need to create a user in Microsoft Dynamics AX, contact your Microsoft Dynamics AX administrator.

The Dollar Universe Manager for Microsoft Dynamics AX needs access to the following database tables: 

Batch



BatchHistory



BatchJob



BatchJobHistory



BatchServerGroup



UserInfo



SysServerSessions



SysClientSessions

The AX User (associated with the Dollar Universe submission account) must have “Full Control” access rights on the Business Connector.

4.2 Automatic Start-up of a Batch Group The Microsoft Dynamics AX client can be instructed to execute certain actions when it starts using the –startupcmd parameter as shown below: ax32.exe –startupcmd=_

If equals “Batch”, then value is interpreted as the name of a Batch Group. If the Batch Group name is not passed correctly to the SysStartupCmdBatchRun class, the Batch Group will not start and its tasks, which should have been launched by the call of the Batch Group, will not run. The next sections explain how to determine if the parameter is passed correctly and how to correct the problem if it exists.

14 | Chapter 4 Configuration

4.2.1 Checking Automatic Batch Group Execution To check if the mechanism for automatically starting a Batch Group works: 

Open a DOS Window.



Change to the Microsoft Dynamics AX client Bin directory.



Start the Microsoft Dynamics AX client and request the execution of an existing Batch Group.

For example, for the batch group TEST: ax32.exe –startupcmd=Batch_TEST

When the AX client starts, a dialog box entitled Batch Processing displays. If the Batch Group name (i.e. TEST) does not appear, then the SysStartupCmdBatchRun class is not correctly defined (See the next paragraph). If the dialog box displays the name of the Batch Group, no changes are necessary.

4.2.2 Correcting the SysStartupCmdBatchRun Class To edit the SysStartupCmdBatchRun class, launch the Microsoft Dynamics AX client and open the Application Object Tree (AOT). In the AOT, select and expand the Class node. Scroll down the list until the SysStartupCmdBatchRun node is visible. To edit Class source code, select the node, open the context menu and click the Edit item. The class editor displays the X++ SysStartupCmdBatchRun Class source code. Check that the line: batchRun.parmGroupId(parm);

is present before calling the run() method. This instruction initializes the Class’s GroupId parameter. The value of parm was received during the initialization of the object, but not used. If this instruction is not present, add the line (and a comment) and compile the class again. Run the test procedure again to check that the modifications work.

4.3 Administering the Manager for Microsoft Dynamics AX 4.3.1 User License Use of the Dollar Universe Manager for Microsoft Dynamics AX is subject to license. The license key must be declared in the Dollar Universe licenses file. This file %UNI_DIR_ROOT%\data\u_fali01.txt is created by the installation procedure. The license can be entered: 

Via UniViewer Console: Administration mode > Nodes > Nodes, select the Dollar Universe V6 node that supports the Manager > Node Settings > License.



Or directly via a text editor.

This license is specific to the Dollar Universe node name on which the Manager for AX is located. The product code is DAX; product version is 6. Enter the valid license, with the following format: node product version expiration_date key

Example:

Chapter 4 Configuration | 15

DU6_node DOLLAR_UNIVERSE:DAX 6 20201231 0123456789ABCDEF

The license key is verified by the uxstrax command. If the license is incorrect, the AX Uproc will abort with an “Invalid license” error message. License keys can be obtained from the Customer Service website or through your sales contact.

4.3.2 Start/Stop the Manager for Microsoft Dynamics AX Dollar Universe Manager for Microsoft Dynamics AX does not have a dedicated process. It follows the Dollar Universe starting and stopping rules.

4.4 Manager for Microsoft Dynamics AX Node Settings The table below describes the Manager's variables. These variables can be defined in the Node Settings> Manager for Dynamics Axapta Dollar Universe V6 Node supporting the Manager: As for Dollar Universe, the Manager's variables are of Install (I), Static (S) or Dynamic (D) type. The Manager's variables related to Dollar Universe Installation cannot be modified. They are Install type. The other variables of Static or Dynamic type can be modified with UniViewer Console or with the unisetvar command. The change in static variables requires the Manager to be restarted for the changes to take effect. Dynamic variables are taken into account by the Manager without having to restart it. Variables needed by the Manager are defined in this category. Variables either contain default values or are common to all AX Uprocs. The table below contains the default values. Variable / Label

I/S/D Description

UNI_AX_DLL_PATH Full path of the library Microsoft.Dynamics.BusinessConnectorNet.dll

D

If UNI_AX_DLL_PATH is not set, the binaries extract the path from the registry key of the installed configuration. If the key is not defined, then the Axapta binaries (uxstrax, uxaxbatchjobretriever and uxaxtestconnect) exit with an error.

UNI_AX_AX32 Full path of the ax32.exe program file.

D

String containing a valid path to the ax32.exe program. For example: C:\AX_client\Bin\ax32.exe

UNI_AX_CTLCYCLE Database polling cycle in seconds.

D

Integer. Default value is 10 seconds.

UNI_AX_EXECTIMEOUT Timeout for a Batch Job execution.

D

Integer. Default value is 600 seconds.

UNI_AX_STOPTIMEOUT Timeout for a Batch Job cancellation.

D

Integer. Default value is 300 seconds.

UNI_AX_NETTIMEOUT Timeout for a connection attempt to Axapta.

D

Integer. Default value is 60 seconds.

UNI_AX_IGNOREHOLD Ignore withhold job status for Batch jobs.

D

String. Value must be “Yes” (“withhold” batch jobs are not launched and the command exits in error.) or “No” (Batch Jobs with the status “Withhold” are launched in the same way as any other job.). Default value is No.

UNI_AX_KEEPLOGERR Recovers infolog of AX aborted jobs into job log

D

String. Value must be “Yes” or “No”. Default value is No

UNI_AX_KEEPLOGOK Recovers infolog of AX ended jobs into job log

D

String. Value must be “Yes” or “No”. Default value is Yes.

16 | Chapter 4 Configuration

Variable / Label

I/S/D Description

UNI_AX_SEND_INFO Display messages inside Information Field of job runs

D

String. Value must be “Yes” or “No”. Default value is Yes.

UNI_AX_SENDMSG D Display messages inside execution history of the job

String. Value must be “Yes” or “No”. Default value is Yes.

UNI_AX_MONITORLEVEL Level of intermediate reports inside Uproc job logs.

D

1: No intermediate report 2: Job progress only 3: Full intermediate report Integer: 1, 2 or 3. Default value is 3.

UNI_AX_TRACE Level of debug traces inside Uproc job log

D

1: Normal 2: Detailed execution 3: Very detailed execution Integer: 1, 2 or 3. Default value is 1.

UNI_AX_BYPASSAOSCHECK Bypass the check of the number of running AOS

D

String. Value must be “Yes” or “No”. Default value is No. If the ByPassAOSCheck parameter value of the uxstrax command is correct, the UNI_AX_BYPASSAOSCHECK node setting value is ignored. If the ByPassAOSCheck parameter value of the uxstrax command is not correct, the UNI_AX_BYPASSAOSCHECK node setting value is used.

4.5 Manager for Microsoft Dynamics AX Logging The Dollar Universe Manager for Microsoft Dynamics AX generates traces to help administrator track and fix problems. You can active the trace mode of the manager by updating the Dollar Universe node setting > category Manager for Dynamics Axapta > Level of debug traces inside Uproc job log (UNI_AX_TRACE). The traces are recorded in the Uproc log file.

Chapter 5 UniViewer Console | 17

5 UniViewer Console This chapter describes UniViewer Console features used to create, submit, and monitor Microsoft Dynamics AX jobs. UniViewer allows Microsoft Dynamics AX jobs to be managed from within Dollar Universe. Standard UniViewer mechanisms and functions are used to execute and monitor Dynamics AX Batch Jobs: 

A Sample Uproc provides the basic integration between Microsoft Dynamics AX and other IT operations.



Dynamics AX Batch Jobs are launched using standard Dollar Universe scheduling functions.



Dynamics AX Batch Jobs are tracked using standard Dollar Universe job monitoring features (status, job logs).

To schedule an AX Batch Job in Dollar Universe, simply: 

Create a new Uproc from the Sample Uproc.



Set the appropriate variables values in the newly created Uproc.

The sample Uproc is built around the uxstrax executable which triggers the Batch Job whose ID or description was passed as a Uproc variable. The new Uproc can of course be adapted to change the number of variables, the execution script, commands used etc…

5.1 Sample Uproc The Dollar Universe Manager for Microsoft Dynamics AX inserts a sample Uproc at installation that can be used to implement batch operations in Microsoft Dynamics AX. To run a Microsoft Dynamics AX job from Dollar Universe: 

Open UniViewer Console > Design mode > Job Design > Uprocs



Create a new Uproc



In the General section of the Uproc definition, enter the Uproc name and then click on the From File button located next to the Type drop down menu.

In the displayed list, select axapta_template_win.clint and click on OK. The Uproc script is then imported and the variables are created. 

Update the Uproc variables to set the appropriate values for the desired AX job.

The sample can be simply customized by the operator to adjust the number of variables, to update the execution script or to update commands used in the execution … The Uproc sample uses the uxstrax command. Refer to the section “Triggering and Monitoring Microsoft Dynamics AX Jobs” on page 9 for the operation of the command.

5.1.1 Sample Uproc’s Variables The table below describes the sample Uproc variables:

18 | Chapter 5 UniViewer Console

Variable name

Description

Type/Format

UAX_JOBID

Identifier of the target AX Batch Job.

Integer

UAX_JOBCAPTION

Description of the target AX Batch Job (used only if UAX_JOBID is not set).

String. 100 characters max

UAX_JOBCONFIGPATH

Full path of the AX configuration file. Optional.

String

UAX_JOBCTLCYCLE

Cycle in seconds for polling the database. Optional.

Integer

UAX_JOBEXECTIMEOUT

Maximum time in seconds allowed for the AX Batch Job to execute. Optional.

Integer

UAX_JOBNETTIMEOUT

Maximum time in seconds allowed for connecting to AX. Optional.

Integer

UAX_JOBSTOPTIMEOUT

Maximum time in seconds allowed for canceling the AX Batch Job. Optional.

Integer

UAX_JOBIGNOREHOLD

Flag used to determine how to handle Batch Jobs with “Withhold” status. Optional.

String. Value must be “Yes” (or “Y”) or “No” (or “N”)

UAX_JOBKEEPLOGERR

Flag used to determine whether infologs for jobs in “Error” status are displayed in the Uproc job log. Optional.

String. Value must be “Yes” (or “Y”) or “No” (or “N”)

UAX_JOBKEEPLOGOK

Flag used to determine whether infologs for jobs in “Ended” status are displayed in the Uproc job log. Optional.

String. Value must be “Yes” (or “Y”) or “No” (or “N”)

UAX_JOBMONITORLEVEL

Level of intermediate reports displayed in the Uproc job log. Optional. 1: No intermediate report 2: Progress of the job only 3: Full intermediate report

Integer: 1, 2 or 3

UAX_JOBTRACE

Level of trace displayed in the Uproc job log. Optional. 1: Normal 2: Detailed execution 3: Very detailed execution

Integer: 1, 2 or 3

UXAX_BYPASSAOSCHECK

Set the ByPassAOSCheck parameter value of the uxstrax command. Optional If the value is correct, the UNI_AX_BYPASSAOSCHECK node setting is ignored.

String. Value must be “Yes” (or “Y”) or “No” (or “N”)

5.1.2 Update the Uproc Select the new Uproc and open it in update mode. In the Variables section, update for example the variable UAX_JOBID: replacing 0 with the identifier of the AX Batch Job. Another solution is to update the variable UAX_CAPTION instead: enter the description of the AX Batch Job. Save the Uproc. As multiple AX Batch Jobs can share the same description, use of the variable UAX_JOBID is recommended to identify the target Batch Job.

Chapter 5 UniViewer Console | 19

5.1.3 AX Companies and Dollar Universe Management Units Since AX Companies and Management Units in Dollar Universe are used to discriminate data, a good practice would be to create Management Units in Dollar Universe with the same names as the Companies in Microsoft Dynamics AX. The sample Uproc script contains the following line: REM set CMD=%CMD% AxComp=%S_CODUG%

Uncomment this line if you want to map the Dollar Universe Management Unit to the AX Company. If the line is left commented, the Manager for AX will connect to AX with the user’s default company.

5.2 Managing AX Batch Jobs If the Manager is properly configured and the corresponding Axapta job is waiting, the new Uproc is ready to be executed.

5.2.1 Launching the Microsoft Dynamics AX Batch Job To start a Microsoft Dynamics AX Batch Job, launch the corresponding Uproc: 

Via a Dollar Universe scheduled task. Default variable values can be changed during task definition.



Via the manual launch creation in the UniViewer Job Runs document. Default variable values can be changed during launch definition.

Make sure that the Calculator and Launcher engines are running. Check that the launch is created in the current area.

5.2.2 Monitoring the Microsoft Dynamics AX Batch Job Once the launch starting date-time has been reached, the Dollar Universe Launcher engine will select this job, check its prerequisite conditions and submit it for execution in Dollar Universe. In Dollar Universe version 6.0 or higher, UniViewer will display the progress in either a Job Run list or a Graphical view (Job Chain) if this is configured. The Job Run list can display a message in the information column with the following information: 

Overall progress of all tasks expressed as a percentage.

Once the Uproc has finished (Completed or Aborted status), a message will display the overall status of AX task executions. When processing has finished, the completed or aborted status is displayed and the following actions are available: 

Access to the job variable definition.



Display the Dollar Universe history trace.



Re-launch aborted jobs.



Purge the record from the Job Runs



Display the Uproc log with a report of all the execution steps performed by the Manager.

An example is shown below:

20 | Chapter 5 UniViewer Console

C00-SUPPORT-SITE DEBUT C00-SUPPORT-SITE WSPGM-CODNOEUD WIN-J0IBJETUTLK2 _!================================================ _!** $!** PROCEDURE .. : AXAPTA_EXAMPLE $!** VERSION .....: 000 $!** EXECUTION .. : 0000013 _!** _!** PROCESS DATE : 06/20/2012 _!** _!-----------------------------------------------$!** PARAMETERS. : None _!-----------------------------------------------_!** VARIABLES UAX_JOBID :5637144826 UAX_JOBCAPTION : UAX_JOBCONFIGPATH : UAX_JOBCTLCYCLE :10 UAX_JOBEXECTIMEOUT :3600 UAX_JOBNETTIMEOUT :3600 UAX_JOBSTOPTIMEOUT :3600 UAX_JOBIGNOREHOLD :Y UAX_JOBKEEPLOGERR :Y UAX_JOBKEEPLOGOK :Y UAX_JOBMONITORLEVEL :1 UAX_JOBTRACE :1 _!================================================ Pass Step : 00 "Starting Batch Job execution." c:\DUAS\AXA606_WIN-J0IBJETUTLK2\bin\uxstrax.exe JobId=5637144826 CtlCycle=10 StopTimeOut=3600 NetTimeOut=3600 ExecTimeOut=3600 IgnoreHold=Y KEEPLOGERR=Y KEEPLOGOK=Y MONITORLEVEL=1 Trace=1 6/20/2012 5:04:26 PM | ----------------------------------------------------------------6/20/2012 5:04:26 PM | Dollar Universe Manager for Microsoft Dynamics Ax v6.0.6/20/2012 5:04:26 PM | ----------------------------------------------------------------6/20/2012 5:04:26 PM | Trace level is set to 1 6/20/2012 5:04:26 PM | Execution time out is 3600 second(s). 6/20/2012 5:04:26 PM | Cancel time out is 3600 second(s). 6/20/2012 5:04:26 PM | Net time out is 3600 second(s). 6/20/2012 5:04:26 PM | Monitoring cycle is 10 second(s). 6/20/2012 5:04:26 PM | Jobs with status "Withhold" are ignored. 6/20/2012 5:04:26 PM | Send Info flag is set to: "Yes". 6/20/2012 5:04:26 PM | Send Msg flag is set to: "Yes". 6/20/2012 5:04:26 PM | Monitoring level is set to: 1. 6/20/2012 5:04:26 PM | Logs for completed jobs are saved. 6/20/2012 5:04:26 PM | Logs for unsuccessful jobs are saved. 6/20/2012 5:04:26 PM | Axapta client executable path: C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin\Ax32.exe. 6/20/2012 5:04:26 PM | Axapta configuration file is not defined. Using standard configuration... 6/20/2012 5:04:26 PM | Axapta company not found. Using Default value. 6/20/2012 5:04:26 PM | Connecting with Axapta without using configuration file... 6/20/2012 5:04:28 PM | Connected with AX. 6/20/2012 5:04:28 PM | Axapta batch job ID: 5637144826. 6/20/2012 5:04:28 PM | 6/20/2012 5:04:28 PM | Launching BatchJob: Report pre-processed data clean up (5637144826)... 6/20/2012 5:04:28 PM | There is no client task in the job. 6/20/2012 5:04:28 PM | Start date/time and status updated for the job 5637144826 in the BatchJob table. 6/20/2012 5:04:28 PM | 6/20/2012 5:04:28 PM | Axapta Batch Job successfully launched. [Job ID=5637144826] 6/20/2012 5:04:28 PM |

Chapter 5 UniViewer Console | 21

6/20/2012 5:04:48 PM | 6/20/2012 5:04:48 PM | Axapta job status: Ended. 6/20/2012 5:04:48 PM | ---------------------------------------------------------------- Final report ----------------------------------------------------------------Status | START | END | USER | COMP | RECID | LOCATION | INFO | CLASS NAME -----------+----------------------+----------------------+-------+------+-----------+----------+------+--------------------------------------Ended | 6/20/2012 5:04:39 PM | 6/20/2012 5:04:39 PM | Admin | dat | 5637144826 | Server | No | SrsReportRunRdpPreProcessController -----------+----------------------+----------------------+-------+------+-----------+----------+------+--------------------------------------#INFOLOG:class=SrsReportRunRdpPreProcessController:recid=5637144826:status=E nded:batch= -----------+----------------------+----------------------+-------+------+-----------+----------+------+--------------------------------------6/20/2012 5:04:48 PM | Disconnected from Axapta. 6/20/2012 5:04:48 PM | Axapta batch job execution successful. 6/20/2012 5:04:48 PM | End of script. AXAPTA_EXAMPLE: Execution is successful.



INFOLOGS: A line INFOLOG is added (in the Uproc job log) for each task executed in the job. #INFOLOG:class=:recid=:status=:batch=

Where: #INFOLOG is a keyword reserved for the parser. class= is a keyword reserved for the parser. recid= is a keyword reserved for the parser. status= is a keyword reserved for the parser. batch= is a keyword reserved for the parser. class_name is the name of the Microsoft Dynamics AX class that was executed. recid is the id of the AX Batch task. batch_status is the status of the AX Batch task. batch_group is the name of the Microsoft Dynamics AX Batch Group associated with the task. 

INFOLOGITEMS: An INFOLOGITEM is a line from in the infolog generated by AX. For each line (or item) of an infolog, a line named INFOLOGITEM is formatted and added to the AX Uproc job log. #INFOLOGITEM:::

Where: #INFOLOGITEM is a keyword reserved for the parser. class_name is the name of the Microsoft Dynamics AX class that was executed. recid is the id of the AX Batch task. line_text is one line of the infolog.

22 | Chapter 6 Commands

6 Commands This chapter describes the Dollar Universe commands used to create, and submit Microsoft Dynamics AX jobs. Refer to the Dollar Universe Commands Guide for more details about the commands general specifications.

6.1 Automatic Creation of Uprocs to Start AX Batch Jobs Two commands created by the installation procedure in the %UNI_DIR_ROOT%\bin\bin_axapta directory are designed to facilitate the creation of AX Uprocs. 

uxaxbatchjobretriever.exe: extracts information about AX jobs



uxaxuproccreator.bat: creates the corresponding Uprocs in Dollar Universe

6.1.1 Extract the List of Batch Jobs Open a DOS window and load Dollar Universe environment file unienv.bat. Change to the %UNI_DIR_ROOT%\bin\bin_axapta directory. uxaxbatchjobretriever.exe output= [status=] [caption=] [company=] [canceledby=] [createdby=] [recid=])

The command performs the following actions: 

Creates the output file in the %UNI_DIR_ROOT%\data directory



Connects to AX



Prepares the statement to retrieve the Batch Jobs according to the defined filter. If no filter is defined, all Batch Jobs are retrieved.

The command selects the records in the BatchJob table according to the values of parameters and writes them into the text file . If several filters are passed, the command uses the AND operator in order to retrieve AX jobs that match all the filters. Parameters are: Parameter

Format

Description

output

String

This parameter is mandatory. It specifies the name of the file to create. If the file exists, the command exists with an error.

status

Integer

This parameter specifies the status of the requested AX jobs. Enter 0 (Withold),1 (Waiting), 2 (Executing), 3 (Error), 4 (Ended), 8 (Canceled) to select jobs with a specific status.

Chapter 6 Commands | 23

caption

String (100 char. max)

Use this parameter to select AX jobs with a specific description . Wildcards (*) can be used as allowed in SQL statements run in X++, for example caption=*test*. Enclose caption text with “ (double quotes) characters if the caption contains space characters, for example: caption=”My first AX job”.

company

String (4 char. max)

Use this parameter to select AX jobs for a given AX company specified by . Wildcards (*) can be used as allowed in SQL statements run in X++, for example: company=ORS*.

canceledby

String (5 char. max).

Use this parameter to select AX jobs canceled by a given AX user specified by . Wildcards (*) can be used as allowed in SQL statements run in X++, for example: canceledby=ADM*.

createdby

String (5 char. max).

Use this parameter to select AX jobs created by an AX user specified by . Wildcards (*) can be used as allowed in SQL statements run in X++, for example: createdby=ADM*.

recid

Integer

Use this parameter to select a single AX job.

For example, to retrieve all the AX Batch Jobs created by the user Admin and write them to the output file uprocs.txt, perform the following command: uxaxbatchjobretriever.exe output=uprocs.txt CreatedBy=Admin

Example: Select all Batch Jobs whose description begins with "Test": uxaxbatchjobretriever.exe output=eca.txt caption="test*" Creating the file C:\DUAS\AXA606_WIN-J0IBJETUTLK2\data\eca.txt... File created. Connecting with Axapta... Connected with AX. Extracting Batch Job [5637146326]... Batch Jobs successfully retrieved.

The output file (C:\DUAS\AXA606_WIN-J0IBJETUTLK2\data\eca.txt) is: #======================================================================= # Dollar Universe Manager for Axapta Batch Job Retriever. #======================================================================= # # This file contains the Batch Job Ids and Descriptions extracted from AX. # You must fill the with the actual names you want to give for your AX Batch Jobs. # Executed statement: SELECT %1 WHERE %1.caption like 'test*' # #---------------------------------------------------------------------#UprocName Ver JobId JobDescription #--------------------------------------------------------------------- | 000 | 5637146326 | test #=======================================================================

The output file is organized as follows: UprocName

Ver

JobId

JobDescription



000





The command creates a line in the output file for each AX Batch Job retrieved. The JobId and JobCaption are directly written by the command. The UprocName is initialized with and must be edited manually for each entry. The Uproc version number (Ver) is set to 000 by default. The edited list is then used to create the corresponding Uprocs in Dollar Universe.

6.1.2 Uproc Creator The script uxaxUprocCreator.bat creates Uprocs in the Production Area of the Dollar Universe Company from the modified output file created by uxaxbatchjobretriever or manually.

24 | Chapter 6 Commands

The file generated by the command uxaxbatchjobretriever must be updated manually: must be replaced by the actual name of the Dollar Universe Uproc. Be careful to respect the naming conventions of Dollar Universe Uprocs (the Uproc name can contain space characters). The Uproc version numbers are set to 000 by default because the Uprocs are created in Production Area. For example: #-----------------------------------------------------------------#UprocName Ver JobId JobDescription #-----------------------------------------------------------------UAX_TST01 000 5637144584 Created By Admin 1 UAX_TST02 000 5637145326 Created By Admin 2 UAX_TST03 000 5637145330 Created By Admin 3 UAX_TST04 000 5637145576 Created By Admin 4 UAX_TST05 000 5637146328 Created By Admin 5

Once the file has been updated with the actual Uproc names: 

Make sure the Dollar Universe Company is started.



Load the Dollar Universe Company environment (unienv.bat in the Dollar Universe Company root directory).



Launch the script uxaxUprocCreator.bat with the parameter . For example: uxaxUprocCreator.bat uprocs.txt

For each uncommented line, the script: 

Creates a new Uproc using the provided Axapta sample Uproc.



Removes the variable UAX_JOBID.



Adds the variable UAX_JOBID with the current line’s JobID value.

The Uprocs listed in the output file are created in Dollar Universe with the same variables as the sample Uproc script “axapta_template_win.clint”, with the exception of the variable UAX_JOBID. Example: uxaxUprocCreator.bat eca.txt -----------------------------------------------------------------------Dollar Universe Manager for MS Dynamics Ax Upgrade procedure -----------------------------------------------------------------------Creating Uprocs... Command : uxadd upr exp upr="ECA TEST " appl=U_ geninf fperiod=n label=" " memo=n nbper=0 upt=cl_int vupr=000 nopartage nointeractive geninf cl_int=c:\DU AS\AXA606_WIN-J0IBJETUTLK2\bin\clints\axapta_template_win.clint vupr=000 label=" test" Creation of Uproc successful. Adding the variable UAX_JOBID with the correct Job Id. Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBID vvalue=" 5637146326 " vtype="T" vformat="255" Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBCAPTION vtype=T vformat=100 vvalue=" " Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBCONFIGPATH vvalue=" " vtype="T" vformat="255" Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBCTLCYCLE vtype=Q valmin=1 valmax=60 vvalue=10 vformat="255"

Chapter 6 Commands | 25

Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBEXECTIMEOUT vtype=Q valmin=1 valmax=10000 vvalue=3600 vformat="255" Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBNETTIMEOUT vtype=Q valmin=1 valmax=10000 vvalue=3600 vformat="255" Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBSTOPTIMEOUT vtype=Q valmin=1 valmax=10000 vvalue=3600 vformat="255" Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBIGNOREHOLD vtype=T vformat=005 vvalue=Y Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBKEEPLOGERR vtype=T vformat=005 vvalue=Y Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBKEEPLOGOK vtype=T vformat=005 vvalue=Y Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBMONITORLEVEL vtype=Q valmin=1 valmax=3 vvalue=1 vformat="255" Command : uxupd upr exp upr="ECA TEST " vupr=000 nopartage launchvar add varname=UAX_JOBTRACE vtype=Q valmin=1 valmax=3 vvalue=1 vformat="255" Update of the uproc(s) variable(s) successful. Uprocs created in the Production Area of Dollar Universe. -----------------------------------------------------------------------Dollar Universe Manager for MS Dynamics Ax End of the Upgrade procedure.

6.2 uxstrax Command The sample Uproc script uses those Uproc variable values defined in the call of the uxstrax command. If no value is specified for optional parameters, the command uxstrax applies the default values defined in the Manager’s Node Settings. The syntax of the uxstrax command is as follows: uxstrax JobId= | JobDesc= [AxConfig=] [AxComp=] [CtlCycle=] [ExecTimeOut=] [StopTimeOut=] [NetTimeOut=] [IgnoreHold=] [KeepLogErr=] [KeepLogOK=] [MonitorLevel=] [Trace=] [ByPassAOSCheck=]

26 | Chapter 6 Commands

Where: Parameter

Description

JobId

Identifier of the target AX Batch Job. This parameter is not compatible with AxComp. This parameter is mandatory if AxComp is not used.

Description

Description of the target AX Batch Job This parameter is not compatible with JobId. This parameter is mandatory if JobId is not used.

ConfigPath

Full path to the AX configuration file used to connect with AX. This parameter is optional.

AXCompanyName

Name of the AX Company. This parameter is optional.

Cycle

Polling cycle (in seconds) used to periodically retrieve the AX Job status. This parameter is optional.

ExecTimeOut

Maximum time (in seconds) allowed for the AX job to complete. This parameter is optional.

StopTimeOut

Maximum time (in seconds) allowed for the AX job to stop when the AX job is canceled by the Manager. This parameter is optional.

NetTimeOut

Maximum time (in seconds) allowed for connecting to AX. This parameter is optional.

IgnoreHoldJobsFlag Used to determine how to handle Batch Jobs with “Withhold” status. Value must be “Yes” (or “Y”) or “No” (or “N”). This parameter is optional. KeepLogErrFlag

Used to determine whether infologs for jobs in “Error” status are displayed in the Uproc job log. This parameter is optional.

KeepLogOKFlag

Used to specify whether infologs for jobs in “Ended” status are displayed in the Uproc job log. This parameter is optional.

MonitorLevel

level of intermediate reports displayed in the Uproc job log. This parameter is optional. Enter: 1: no intermediate report 2: progress of the job only 3: full intermediate report

TraceLevel

Level of trace displayed in the Uproc job log. This parameter is optional. Enter: 1: Normal 2: Detailed execution 3: Very detailed execution

ByPassAOSCheck

Bypass the check of the number of running AOS. Value must be “Yes” (or “Y”) or “No” (or “N”). This parameter is optional. If the value is correct, the UNI_AX_BYPASSAOSCHECK node setting is ignored.

Return Codes: The uxstrax return codes are:

Chapter 6 Commands | 27

Return code

Description

0

Normal successful completion

1

An error occurred during the execution of the AX job.

2

The AX job was not launched.

3

Invalid configuration file

4

Invalid command line arguments

11

AX client pathname invalid

12

AX client could not be launched.

21

Error logging into AX

31

Invalid Batch Job ID

32

AOS validation error

41

Missing DLL

42

License of the Manager invalid

43

License file not found

Figure 2: uxstrax return code table

This return code is verified in the Uproc script. The Uproc ends with the appropriate completion status: 0 indicating success; anything other than zero meaning that the execution ended in error.

28 | Chapter 7 Troubleshooting

7 Troubleshooting This chapter gives information to resolve possible problems. Issue

Displayed message

Possible reason

Solution

The execution of the commands uxaxtestconnect.e xe, uxaxbatchjobretrie ver.exe or uxaxUprocCreator .bat fails.

Windows displays a dialog box to warn the user that the command cannot be executed and must be closed.

The path to the DLL Microsoff.Dynamics.BusinessCon nectorNet.dll is not present in the registry or in the UNI_AX_DLL_PATH of Dollar Universe.

Add the path to the Microsoff.Dynamics.BusinessCon nectorNet.dll. Reload the environment. Launch the command again.

Log on to AX failed.

(AX_Logon) error (LogonFailedExc eption): Connection with the Application Object Server could not be established.

The AOS is not running.

Check the status of the Dynamics Object Server in the Services window.

Log on to AX failed.

(AX_Logon) error (LogonFailedExc eption): You are not a recognized user of Microsoft Dynamics AX.

The Dollar Universe user is not associated correctly with an AX user.

Contact your system administrator for help.

Log on to AX failed and no additional information is displayed in the Uproc job log

(AX_Logon) error:

Not enough rights to use the Business Connector.

Give the permission “Full Control” on the security key Business Connector.

Impossible to update a record in the Batch table

Error updating the job in the BatchJob Table: Cannot edit a record in Batch transactions (Batch). The corresponding AOS validation failed.

Not enough permission for launching the job.

Check the access on the Batch and BatchJob tables.

Chapter 7 Troubleshooting | 29

Issue

Displayed message

Possible reason

A warning appears indicating that no AOS is running for executing a task whereas the task is executed.

(getServerStatus) Insufficient permissions for error executing viewing online AOS. statement on the SysServerSessio ns table: An unspecified runtime engine error has occurred. Error code: %d.

Solution Give the permission “View” on the security key Administration – Daily.

7.1 Troubleshooting Tool The command uxaxtestconnect, located in the %UNI_DIR_ROOT%\bin\bin_axapta directory, can be used for troubleshooting purposes. First, load the Dollar Universe environment unienv.bat. uxaxtestconnect.exe [user=] [password=] [company=] [config=] [help]

The command tests the connection to AX through the .NET Business Connector. Called without arguments, the command connects to AX with the current Windows user, then disconnects from AX. Called with the parameter , the command displays its usage. The command can also connect to AX using another account: in that case uxaxtestconnect.exe must be called with the parameters and . The AX Company or the configuration file can also be chosen by using the optional parameters and . Example: uxaxtestconnect ==================================== UAX_TestConnect ==================================== Axapta session created. No configuration file found... Using default configuration... No company name found... Using default value... Connecting to AX with the current user... Connected to AX. Disconnecting from AX ... Disconnected from AX.

30 | Chapter 8 About Automic Software, Community and Services

8 About Automic Software, Community and Services This topic introduces the Automic Software company and how to leverage the full potential of our solutions to you. You can also obtain Automic documentation online from docs.automic.com.

8.1 Automic Software Company Automic Software is dedicated to business automation. Automic is the world's most comprehensive platform in automating businesses. Founded 1985, Automic pioneered the largest, independent, globally deployed automation platform which powers the enterprise, application and infrastructure. Now, as the consumerization of IT accelerates, Automic is re-imagining how organizations integrate next generation service models such as Cloud, DevOps and Big Data. Today, our software automates tens of millions of operations a day for over 2,000 customers worldwide. We challenge conventional thinking, enabling our customers to be faster, smarter, in control. Automic – the standard in business automation. Find out more at our website www.automic.com .

8.2 Automic Community Want to connect with other Automic users to compare notes or learn how others are tackling problems that you’re running into? Talk with other users from around the world to learn how they optimize their business automation with Automic. Interact with the Automic Team to get ONE Automation Platform tips and tricks straight from the source. Join the Automic Community and become an Automic Insider and be among the first to get news about new products and events, even before they are generally announced!

8.3 Download Center Make sure that you are using our products to their fullest potential. The Download Center is the place where you find product downloads, documentation and information on new releases and hot-fixes about your Automic solution. It’s all in one place: from service hotfixes, release notes, and all guides. You will also find patch descriptions, known bugs or workarounds.

Chapter 8 About Automic Software, Community and Services | 31

8.4 Technical Support We have a support team you can trust. Our team of professionals is ready to support you, anytime and anywhere. Three support centers located in Europe, the United States, and Asia Pacific build the core of the Automic support organization. Our Technical Support Team makes sure that your closest Automic experts are never more than a few hours flight away, no matter on which continent your subsidiaries and data centers are located. Automic Software is designed to provide global connectivity for international companies. You are employing Automic software on a global scale and therefore you can expect global service.

8.5 Training and Services Do you want to learn even more about Automic solutions? We offer a range of training options on how to get the most out of your Automic solution. Depending on your location, either open training sessions at an Automic Software Service Center, or personalized training sessions at your company's site suits best. Visit the training site and get detailed information about currently offered courses.