You can use the wsadmin tool and scripting to install an application into the run time.
On a single server installation, the server must be running before you install an application. See the Starting servers using scripting article for more information.
On a network deployment installation, the deployment manager must be running before you install an application. See the startManager command article for more information.
The application that you install must be an enterprise archive file (EAR), a Web archive (WAR) file, a servlet archive (SAR), or a Java archive (JAR) file. The archive file must end in .ear, .jar, .sar or .war for the wsadmin tool to be able to install it. The wsadmin tool uses these extensions to figure out the archive type. If the file is a WAR or JAR file, it will be automatically wrapped as an EAR file.
If you are installing an application that has the AdminApp useMetaDataFromBinary option specified, then you can only install this application on a WebSphere Application Server V6.x deployment target. This also applies to editing the application, using the AdminApp edit command, after you install it. If you use the V5.x wsadmin tool to install or edit an application on a WebSphere Application Server V6.x cell, only the steps available for the V5.x wsadmin tool will be shown.
Perform the following steps to install an application into the run time: