Stop enabling the security of WAS Server without manually enter the password of the second option
Should be known as the easiest way to a
% PROFILE_HOME% \ bin \ stopServer.bat serverXyz-username Xyz-password Xyz
But the user name and password are all clear, and in some scenarios may not meet the
The second selection method is given now
set PROFILE_HOME = D: \ IBM \ WebSphere \ AppServer \ 6.1 \ profiles \ AppSrvSingle
cd% PROFILE_HOME% \ properties
To back up what files sas.client.props and soap.client.props
Because there are two ways to connect: SOAP and RMI, the default is the SOAP method
1. SOAP soap.client.props open the way to modify the file, about line 26
com.ibm.SOAP.loginUserid =
com.ibm.SOAP.loginPassword =
By default, the values are empty, populated with the current user and password are being used, such as are WebSphere
com.ibm.SOAP.loginUserid = WebSphere
com.ibm.SOAP.loginPassword = WebSphere
Then do
% PROFILE_HOME% \ bin \ PropFilePasswordEncoder.bat% PROFILE_HOME% \ properties \ soap.client.props com.ibm.SOAP.loginPassword-Backup
After successful implementation, will be the following tips
NOTE: all specified passwords already encoded in target file ==% PROFILE_HOME% \ properties \ soap.client.props
Or
NOTE: Backup file% PROFILE_HOME% \ properties \ soap.client.props.bak contains unencoded passwords
Open soap.client.props can see the password file is encrypted, as
com.ibm.SOAP.loginUserid = WebSphere
com.ibm.SOAP.loginPassword = {xor} CDo9DC83Oi06
Then stop the WAS Server directly using the following command to stop the WAS Server you can, do not need to enter a user name and password
% PROFILE_HOME% \ bin \ stopServer.bat server1
Or
% PROFILE_HOME% \ bin \ stopServer.bat server1-conntype SOAP
The default SOAP port is SOAP_CONNECTOR_ADDRESS port
2. RMI and SOAP methods to modify the way similar to open sas.client.props file, about line 90
com.ibm.CORBA.loginUserid =
com.ibm.CORBA.loginPassword =
By default, the values are empty, populated with the current user and password are being used, such as are WebSphere
com.ibm.CORBA.loginUserid = WebSphere
com.ibm.CORBA.loginPassword = WebSphere
Then do
% PROFILE_HOME% \ bin \ PropFilePasswordEncoder.bat% PROFILE_HOME% \ properties \ sas.client.props com.ibm.CORBA.loginPassword-Backup
After successful implementation, will be the following tips
NOTE: all specified passwords already encoded in target file ==% PROFILE_HOME% \ properties \ sas.client.props
Or
NOTE: Backup file% PROFILE_HOME% \ properties \ sas.client.props.bak contains unencoded passwords
Open soap.client.props can see the password file is encrypted, as
com.ibm.CORBA.loginUserid = WebSphere
com.ibm.CORBA.loginPassword = {xor} CDo9DC83Oi06
Note that RMI approach also need to change the following key
com.ibm.CORBA.loginSource = prompt
As
com.ibm.CORBA.loginSource = properties
Then stop the WAS Server directly using the following command to stop the WAS Server you can, do not need to enter a user name and password
% PROFILE_HOME% \ bin \ stopServer.bat server1-conntype RMI-port 2809
The default RMI port is BOOTSTRAP_ADDRESS port