ear deployment

[kalyan mohan]

Hi Friends
I am deploying the application ear many times in a day and it is time consuming to deploy each time.Can anyone please suggest if there is any script/automated process using which I can deploy very quickly and avoid restarting the server each time.

Thanks

[Paul Clapham]

Well, first of all you don't need to restart the server if you're just installing a new version of the EAR. But if you want something a little bit more automated than opening the web-based admin application and clicking, here's the install script I use:

set asn [$AdminControl queryNames type=ApplicationManager,process=server1,*]
$AdminControl invoke $asn stopApplication YourApplication
$AdminApp uninstall YourApplication
$AdminConfig save
$AdminApp install c:/websphere/appserver/installableapps/YourApplication.ear {-preCompileJSPs true}
$AdminConfig save
$AdminControl invoke $asn startApplication YourApplication

Put that in a file called (e.g.) install.script and open a command window on the server where Websphere is running. Change the current directory to Websphere's "bin" directory. (For me that would be
c:/websphere/appserver/bin but maybe something else for you.) Type this command:

wsadmin.bat < install.script

Note that you need to put the EAR file in a predetermined location on the server (I used the installableapps directory) and that location must be specified in the script.

[kalyan mohan]

Hi
Thanks for that...
Iam getting the following error when I try this ..any suggestions please

WASX7023E: Error creating "SOAP" connection to host "localhost"; exception infor
mation: com.ibm.websphere.management.exception.ConnectorNotAvailableException
WASX7213I: This scripting client is not connected to a server process; please re
fer to the log file C:\websphere\Dev\logs\wsadmin.traceout for additional informat
ion.
WASX7029I: For help, enter: "$Help help"
wsadmin>WASX7015E: Exception running command: "set asn [$AdminControl queryNames
type=ApplicationManager,process=server1,*]"; exception information:
com.ibm.ws.scripting.ScriptingException: AdminControl service not available

wsadmin>WASX7015E: Exception running command: "$AdminControl invoke $asn stopApp
lication myapp"; exception information:
com.ibm.bsf.BSFException: error while eval'ing Jacl expression: can't read "asn
": no such variable
wsadmin>WASX7015E: Exception running command: "$AdminApp uninstall WCG - Catalys
t 4.5"; exception information:
com.ibm.bsf.BSFException: error while eval'ing Jacl expression: can't find meth
od "uninstall" with 4 argument(s) for class "com.ibm.ws.scripting.AdminAppClient
"
wsadmin>WASX7015E: Exception running command: "$AdminConfig save"; exception inf
ormation:
com.ibm.ws.scripting.ScriptingException: WASX7070E: The configuration service i
s not available.

wsadmin>WASX7015E: Exception running command: "$AdminApp install C:/websphere/Dev/
installableApps/app.ear {-preCompileJSPs true}"; exception information:
com.ibm.ws.scripting.ScriptingException: WASX7206W: The application management
service is not running. Application management commands will not run.

wsadmin>WASX7015E: Exception running command: "$AdminConfig save"; exception inf
ormation:
com.ibm.ws.scripting.ScriptingException: WASX7070E: The configuration service i
s not available.

wsadmin>WASX7015E: Exception running command: "$AdminControl invoke $asn startAp
plication myapp"; exception information:
com.ibm.bsf.BSFException: error while eval'ing Jacl expression: can't read "asn
": no such variable

[Ryan Zezeski]

Looks like none of your servers are up when your calling wsadmin. Just a note, you will quickly learn that jacl script errors are cryptic and often times tell you nothing. It takes a while of working with them to understand the error messages.

[James Dsouza]

The problem should be with the \AppServer\profiles\AppSrv01\properties\wsadmin.properties. If you have changed the port information during creation of your profile that should be reflected in wsadmin.properties.

Application servers > server1 > Ports

Check the SOAP_CONNECTOR_ADDRESS port number this should be set to com.ibm.ws.scripting.port in wsadmin.properties

PS. this is wrt Websphere 6