Example: Obtaining information about task options for the AdminApp install command

You can obtain information online about the AdminApp task options by using the AdminApp taskInfo method.

• Use the options method to see the requirements for an EAR file if you construct installation command lines. The taskInfo command provides detailed information for each task option with a default binding applied to the result.
• The options for the AdminApp install command can be complex if you specify various types of binding information, for example, Java Naming and Directory Interface (JNDI) name, data sources for enterprise bean modules, or virtual hosts for Web modules. An easy way to specify command line installation options is to use a feature of the installInteractive command that generates the options for you. After you install the application interactively once and specify all the updates that you need, look for message WASX7278I in the wsadmin output log. The default output log for wsadmin is wsadmin.traceout. You can cut and paste the data in this message into a script, and modify it. For example:

  WASX7278I: Generated command line: install c:/websphere/appserver/installableapps/jmsample.ear   {-BindJndiForEJBNonMessageBinding {{deplmtest.jar MailEJBObject deplmtest.jar,META-INF/ejb-jar.xml ejb/JMSampEJB1 }} -MapResRefToEJB {{deplmtest.jar MailEJBObject deplmtest.jar,META-INF/ejb-jar.xml mail/MailSession9 javax.mail.Session mail/DefaultMailSessionX } {"JavaMail Sample WebApp"  mtcomps.war,WEB-INF/web.xml mail/MailSession9 javax.mail.Session mail/DefaultMailSessionY }} -MapWebModToVH {{"JavaMail Sample WebApp" mtcomps.war,WEB-INF/web.xml newhost }} -nopreCompileJSPs -novalidateApp -installed.ear.destination c:/mylocation -distributeApp -nouseMetaDataFromBinary}