Use the AdminApp object to manage applications.
This object communicates with the runtime application management object in the product to make application inquires and changes, for example:
Because applications are part of configuration data, any changes that you make to an application are kept in the configuration session, similar to other configuration data. Be sure to save your application changes so that the data transfers from the configuration session to the master repository.
With the application already installed, the AdminApp object can update application metadata, map virtual hosts to web modules, and map servers to modules. You must perform any other changes, such as specifying a library for the application to use or setting session management configuration properties, using the AdminConfig object.
You can run the commands for the AdminApp object in local mode. If a server is running, it is not recommended that you run the scripting client in local mode because any configuration changes that are made in local mode will not be reflected in the running server configuration and vice versa. If you save a conflicting configuration, you could corrupt the configuration.
To see a list of all available commands for the AdminApp object: