Hitachi

JP1 Version 12 JP1/IT Desktop Management 2 Distribution Function Administration Guide


17.7 Debugging an AIT file

Once you created an AIT file, repeat syntax checks, execution, and debugging to finish a complete AIT file that can simulate user operations correctly. You do not need to compile AIT files.

Note that, depending on the JP1/IT Desktop Management 2 - Agent version, you must open the JP1/ITDM2 Automatic Installation Tool window as a user with Administrator permissions when debugging an AIT file for a program that requires Administrator permissions. This restriction applies to JP1/IT Desktop Management 2 - Agent for any of the following OSs: Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012, Windows 7, and Windows Server 2008 R2. If the program can be executed with non-Administrator user permissions, you can debug the AIT file with either type of permissions.

The following figure shows the flow of debugging an AIT file:

Figure 17‒30: Flow of debugging an AIT file

[Figure]

When you open an AIT file with the Automatic Installation Tool, the Build and Debug menus for debugging are enabled.

The Build menu allows you to detect syntax errors in the AIT file and to execute the active (currently opened) AIT file.

The Debug menu allows you to set breakpoints at which you can stop execution of the AIT file. You can use the Watch window to view and update variable values.

These facilities can be used only for the AIT files that have the extension .ais.

Notes on debugging

In the PACKAGE_INFO section, the installer name is specified in InstallerName with a relative path from the packaging directory. During debugging, in the MAIN section, you have to replace the relative path temporarily with the absolute path. After completion of debugging, you must set the original relative path. During syntax checks, however, you do not need to replace the relative path with the absolute path. The following gives an example of replacing the value of InstallerName with the absolute path.

Figure 17‒31: Example of replacing the value of InstallerName with the absolute path

[Figure]

Organization of this section