Using wsadmin to deploy the generated .war file on WAS 6.1

You can also deploy the generated .war file at the command line using the wsadmin tool.

Note: These steps may need to be adjusted for alternate WAS configurations.
In the wsadmin tool, enter a command similar to the example below.

In this example, the enterprise application is named DiscoveryFramework. The module being added has the file name endeca-navigation-portlet.war and the display name endeca-navigation-portlet. This command is executed from the Liferay deploy output directory (that is, the directory containing the endeca-navigation-portlet.war file). In our example, this command is executed in /home/endeca/liferay/websphere-deploy/. .

[WAS]/AppServer/bin/wsadmin.sh -c "\$AdminApp update DiscoveryFramework modulefile {-operation addupdate -contents endeca-navigation-port¬
let.war -contextroot /endeca-navigation-portlet/ -contenturi endeca-navigation-portlet -usedefaultbindings}" –c "\$AdminConfig save"