9.6. Defining External Applications

Engineering Knowledge Manager

Administration Guide | Chapter 9: Defining EKM Servers, Queues, and External Applications |

9.5. Creating and Editing Cluster Configurations in EKM |  | 9.6.1. Predefined External Applications
Prev |  | Next

## 9.6. Defining External Applications

`External Application` objects are used to represent applications that are external to EKM, and that can be run by EKM. External applications are stored as XML-formatted files in EKM and are always defined and associated with a particular `Queue`. Queues are used to specify different locations where applications are run.

Important: Any application that you define must be accessible on all compute hosts where the batch job may ultimately run. For example, if you define an application for a queue named TestQueue, and there are two execution nodes available to run jobs submitted to TestQueue, then both of these nodes need to be able to access the application that will be run.

When you select a queue in the file list window, any external applications associated with that queue are listed. In this way the queue object acts like a folder in the file list window, and that folder can contain external application files. For example, if there were an application named myApp.app.xml that was associated with a queue named `MyQueue1` under the `Master` server, the path to that application would be:

`/Administration/Servers/Master/MyQueue1/myApp.app.xml`

Important: All Queues and External Applications must be defined under `/Administration/Servers/Master`. Cache Servers cannot contain these definitions as they do not support running applications.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.