Creating a Batch Install Script

Use the Batch Tool wizard to create a batch script that you can subsequently use for installing Simcenter Amesim.

1. Launch the executable file called setup64.exe for Windows, or install.aol for Linux.Note You must ensure that the install.aol file has executable permission. Refer to Installing Simcenter Amesim Interactively. The Siemens installer opens.

2. Select Tools > Batch Tool.

3. Click Next.

4. The batch install script creation is a two-part process. In the first part, Part 1 of 2: Repository Setup Overview, you define the network paths to the repository (installation source). Click Next.

5. In the Siemens Install Program window, ensure that the Path to the installer executable field points to the executable file (either setup64.exe or install.aol) located in the uncompressed installation archive. Check the path and click Next.

6. In the Source Location window, the Path to the source field should be pre-populated. If it is not, you can type the search path or click the Search button and use the Source Browser to find the path to the source.

The source is the folder that contains:

The Simcenter Amesim archives (named Simcenter Amesim vN).

The metadata (_msidata).

7. Click Next.

8. In the second part of batch install script creation, Part 2 of 2: Client Batch Script Overview, you create the batch script that will run on the client machines. The script installs the software from the repository you defined in Part 1 of 2: Repository Setup Overview. Click Next.

9. In the Default Target Location window, specify the default target location where Simcenter Amesim is installed on the client machines. You can click Browse to search for the target location.

10. Click Next.

11. In the Platform Selection window, select your operating system (Windows or Linux), and click Next.

12. In the Product Selection window, select one or more products to install.

The window provides information about each product available for installation, the amount of available disk space at the target, and the amount of disk space the product requires. Note Some products may be dependent on one or more products and are check marked accordingly.

13. Click Next.

14. In the License Agreement Viewing Preference window, select if you want to prompt the License Agreement each time the batch script runs (Prompt when running), or if you want to agree to it now (Agree now).

15. Click Next.

If you chose Agree now, the License Agreement displays. If not, the Batch Script Options window opens.

16. Specify the optional script behavior during execution:

Verbose mode: Select if you want detailed progress during installation.

Verify installation: Select if you want to verify the files after installation.

Copy log file to location: Select if you want to copy the log file from the client to the specified location (client must have write access).

Run batch file as Administrator: Select if you want to run as admin (requires VBScript).

Participate in Digital Product Experience

17. Click Next.

18. In the Confirm and Save window, confirm the product selections, specify the file name and file type to save to, and click Save.

You get a confirmation window, stating that the batch script was created successfully.

19. Click Done to exit the Batch Tool.

The new batch install file is an executable script which contains the following metadata:

• source value — The full path to the repository or source of the installation media (DVD or installed tree).

• target value — The full path to the location where the media is to be installed.

• platform value — The platform that is to be installed.

• release name — The release name as specified on the source media.

• product name — The product(s) as specified on the source media.