I have an application that requires a long initialization before being completely deployed to a Webserver (WebSphere 8.5 for our use case). This initialization takes several minutes even out to half an hour and that is completely normal. I have been using the wsadmin command line tool to upload the ear file and then issue start for the application. Since the start time is long, wsadmin receives a read time exception and closes before the completion of the application initialization. If at this moment I issue a wsadmin command to see the status of the application:
wsadmin.sh -host $HOST -port $PORT -user $USER -password $PASS -c '$AdminControl completeObjectName type=Application,name='$APP',*'
I will get an answer meaning the application is running (http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.base.doc%2Finfo%2Faes%2Fae%2Ftxml_appstate.html) The same answer I get when the initialization has been completed. So the question is how to determine the exact status of my application.
Thank you in advance.
P.S. I have already seen this post (How to get current application state from wsadmin console for WebSphere 7.0) but I am not sure how exactly I could follow the steps he is mentioning. Also I am running a single node and not a cluster. P.S.2. Also is it possible to increase the time out for the wsadmin tool in the first place so as to avoid the read time out?