Install enterprise apps using scripting



Search Tips   |   Advanced Search


Use AdminApp or AdminApplication to install an application to the appserver runtime. We can install...

Command examples:

### Jython...
AdminApp.install('location_of_ear.ear','[-node nodeName -cell cellName -server serverName]')

### Jacl...
$AdminApp install "location_of_ear.ear" {-node nodeName -cell cellName -server serverName}

To get a list of supported options for an EAR file:

### Jython
print AdminApp.options()

### Jacl:
$AdminApp options

On a dmgr installation, verify the dmgr is running (

Start The wsadmin tool automatically wraps WAR and JAR files as an EAR file.

Install the application in batch mode on a cluster:

### Jython string
AdminApp.install('c:/MyStuff/application1.ear', '[-cluster cluster1]')

### Jython list
AdminApp.install('c:/MyStuff/application1.ear', ['-cluster', 'cluster1'])

### Jacl
$AdminApp install "c:/MyStuff/application1.ear" {-cluster cluster1}

Install the application using interactive mode.

### Jython...

### Jacl...
$AdminApp installInteractive "c:/MyStuff/application1.ear"

Synchronize nodes


What to do next

The steps in this task return a success message if the system successfully installs the application. When installing large applications, the command might return a success message before the system extracts each binary file. We cannot start the application until the system extracts all binary files. If we installed a large application, use the isAppReady and getDeployStatus commands for the AdminApp object to verify that the system extracted the binary files before starting the application.

The isAppReady command returns a value of true if the system is ready to start the application, or a value of false if the system is not ready to start the application.

For example, using Jython:

print AdminApp.isAppReady('application1')

Using Jacl:

$AdminApp isAppReady application1

If the system is not ready to start the application, the system might be expanding application binaries. Use the getDeployStatus command to display additional information about the binary file expansion status, as the following examples display:


print AdminApp.getDeployStatus('application1')
Using Jacl:

$AdminApp getDeployStatus application1


Related tasks

Starting servers using scripting
Install enterprise application files with the console
Automating application configurations using the scripting library
Use the AdminApp object for scripted administration



Application installation and uninstallation scripts
Commands for the AdminApp object
Options for the AdminApp object install, installInteractive, edit, editInteractive, update, and updateInteractive commands
Example: Obtaining option information for AdminApp object commands