How to start or stop an Enterprise application that is deployed into a cluster using wsadmin scripting tool

http://www-01.ibm.com/support/docview.wss?uid=swg21293401


Problem(Abstract)
It is not possible to start or stop the application from cluster scope directly when using the wsadmin scriping tool.
To start or stop the application running in a cluster, the user must run wsadmin scriping start or stop commands for all the cluster members separately.
Resolving the problem
Here is an example to start or stop an Enterprise application in a cluster setup using the wsadmin scripting tool:
Connect to Deployment Manager:
/profile_install_root/bin>wsadmin.sh/bat

Identify the application manager MBean for the server where the application resides, and assign it to the appManager variable.

wsadmin> set appManager [$AdminControl queryNames
cell=mycell,node=mynode,type=ApplicationManager,process=member1,*]

This command returns the application manager MBean (output):
Example:
WebSphere:name=ApplicationManager,process=member2,platform=dynamicproxy,node=vik
ram2Node08,version=6.1.0.13,type=ApplicationManager,mbeanIdentifier=ApplicationManager,cell=vikram2Cell02,spec=1.0

To start the application:
wsadmin> $AdminControl invoke $appManager startApplication AppName

To stop the application:
wsadmin> $AdminControl invoke $appManager stopApplication AppName

Repeat the above two steps for all cluster members in a cluster by specifying right nodename and member names.









Example: /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/wsadmin.sh -lang jacl
Example :   set appManager [$AdminControl queryNames cell=wastest852Cell01,node=wastest852Node01,type=ApplicationManager,process=malisrv01,*]
Example:

[wasadmin@wastest852 bin]$ ./wsadmin.sh -lang jacl
WASX7209I: Connected to process "dmgr" on node wastest852CellManager01 using SOAP connector;  The type of process is: DeploymentManager
WASX7029I: For help, enter: "$Help help"
wsadmin>set appManager [$AdminControl queryNames cell=wastest852Cell01,node=wastest852Node01,type=ApplicationManager,process=malisrv01,*]
WebSphere:name=ApplicationManager,process=malisrv01,platform=proxy,node=wastest852Node01,version=8.5.5.1,type=ApplicationManager,mbeanIdentifier=ApplicationManager,cell=wastest852Cell01,spec=1.0
wsadmin>$AdminControl invoke $appManager startApplication NYS
wsadmin>

webservices.unify.faults in WAS v8.5

Websphere Application Server Network Deployment v8'den itibaren bu özellik default olarak true geliyor.

Bu nedenle true olarak set edildiğinde 

 javax.xml.ws.soap.SOAPFaultException: Internal Error

hata böyleyken . 

False olarak set edildiğnde hatayla ilgili daha fazla ayrıntıya giriyor ;

javax.xml.ws.soap.SOAPFaultException: An internal error occurred during JAX-WS marshalling. An object of type .....

webservices.unify.faults ;

Use the webservices.unify.faults property to disable SOAP Fault unification for JAX-WS and JAX-RPC. By default, the web service runtime environments (both JAX-WS and JAX-RPC) unify all faults generated by the runtime environment to a single type of fault containing a faultcodeof Server and a faultstring of Internal Error. The faults do not contain any additional information identifying the actual cause of the fault. The unification of faults results in a more secure system, preventing detailed information regarding why inbound message processing failed from being returned to message senders.

The default value for this property is true, which causes faults to be unified. If your applications require fault details, then you can set this property to false to disable fault unification, allowing detailed information to be returned in faults. Note that regardless of the property setting, checked exceptions defined in the WSDL and thrown by a service provider method implementation are not unified. Additionally, detailed information regarding the cause of the fault are logged if trace is enabled, regardless of the setting of this property.

This property and the associated behavior is new in Version 8 of the product.

http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/xrun_jvm.html?lang=en