Configure soap.client.props (When you have console secured)

Once you have secured the console each time you need stop a websphere server by command line, you will need an administrator user and password, configuring the service user in the soap.client.props file is the idea of this laboratory, this activities need to be done by windows administrators, you should know why.

The idea is that you can stop any java server without password

In order to it work, you must set properties in the soap.client.props file. 

Perform the following procedure:

1. Set the following properties in soap.client.props:
com.ibm.SOAP.securityEnabled=true
com.ibm.SOAP.loginUserid=<user_ID>
com.ibm.SOAP.loginPassword=<password>

2. Run one of the following commands to encrypt the password:
Windows:
PropFilePasswordEncoder.bat <path>\soap.client.props com.ibm.SOAP.loginPassword
UNIX or Linux:
<path>/PropFilePasswordEncoder.sh soap.client.props com.ibm.SOAP.loginPassword

in my case:
#cd /opt/IBM/WebSphere/AppServer8.5/profiles/Dmgr_Prod/properties
#cp soap.client.props soap.client.props.bk
#vi  soap.client.props
com.ibm.SOAP.securityEnabled=true
com.ibm.SOAP.loginUserid=wasadmin
com.ibm.SOAP.loginPassword=Wasadmin

SAVE the file
# ../bin/PropFilePasswordEncoder.sh soap.client.props com.ibm.SOAP.loginPassword

Now you can stop any websphere process using command line

NOTE:
As you can see, you no need to know what is the wasadmin password, only your Windows Administrator, this password should not expire because all user need to login to websphere will be authenticated by this user, that is the reason why it should not be used like infraestructure administrator.

Ahhh and copy  the configured soap.client.props to all yours managed nodes!!!!