Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin)
Use the wsadmin scripting AdminApp object for scripted administration
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:
- Install and uninstall applications
- List applications
- Edit applications or modules
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 the 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. We 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.
In a dmgr environment, configuration updates are available only if a scripting client is connected to a dmgr. When connected to a node agent or a managed application server, you will not be able to update the configuration because the configuration for these server processes are copies of the master configuration which resides in the dmgr. The copies are created on a node machine when a configuration synchronization occurs between the dmgr and the node agent. Make configuration changes to the server processes by connecting a scripting client to a dmgr. For this reason, to change a configuration, do not run a scripting client in local mode on a node machine. It is not a supported configuration.
To see a list of all available commands for the AdminApp object:
Procedure
- See the Commands for the AdminApp object topic.
- We can also use the Help command, for example:
### Jacl
$AdminApp help### Jython
print AdminApp.help()
Related
List applications using wsadmin.sh
Edit application configuration
Pattern matching using wsadmin.sh
Related
Commands for the AdminApp object using wsadmin.sh