Hi,

I need a little help. Let's assume I'd like to encrypt one or more server binaries so people that don't know a password can't run WAS.
I'm trying to figure out what is the file/proces that initiates the WAS startup - in a way the httpd file starts apache server.
I know the startServer.sh starts JVM that spawns another JVM with server. But what are the key files (binaries) involved in the proces?  

Good afternoon,

Can you please provide a little more information?  Does more than one person have access to the WAS server?  If so, why not enable global security?

Hi !
There are various ways to start WebSphere Application Server. If you need to prevent someone from from doing this, you need to consider all these ways:

WebSphere Admin Console:
If you have global security enabled, one must provide username/password to get into the Admin console. If you don't have Global Security enabled, then anyone can get in and they will have all the rights

Command line:
/profiles//bin/startServer.sh can start WebSphere Application Server. It will ask for username/password if you don't have them in soap.client.properties.

wsadmin:
Same as command line, will ask for username/password if you don't have them in soap.client.properties.

Using Windows Service:
If Websphere Application Server has been configured to run as Windows Service, simply starting the Windows Service will start WebShere. Anyone who can get to the Server with Admin rights can start the service.  

Now, password in soap.client.properties can be encoded using PropFilePasswordEncoder.sh (or PropFilePasswordEncode.bat in Windows)

Good Luck
Karun