Let's say the following is being returned when attempting to start a WebSphere deployment manager or application server. Notice in this example that /opt/WebSphere/AppServer85/java_1.8_64/bin/java is listed.

ADMU0111E: Program exiting with error:
           com.ibm.ws.process.exception.InvalidExecutableException: PROC0004E:
           Executable: [/opt/WebSphere/AppServer85/java_1.8_64/bin/java]
           does not appear to be a valid executable.  Process could not be
           created.

The managesdk.bat (Windows) or managesdk.sh (Linux) command with the -listEnabledProfileAll option can be used to list the version of Java being used by the nodes and application servers for each profile. Notice in this example that Server001 is using 1.8_64 whereas Node01 is using 1.8_64_bundled.

AVOID TROUBLE

If you are prompted for a username and password, refer to username password and the soap.client.props sas.client.props ipc.client.props files.

~]# ${WAS_INSTALL_ROOT}/bin/managesdk.sh -listEnabledProfileAll

CWSDK1004I: Profile Profile01 : 1.8_64_bundled
CWSDK1006I: PROFILE_COMMAND_SDK = 1.8_64_bundled 
CWSDK1008I: Node Node01 SDK name: 1.8_64_bundled
CWSDK1009I: Server Server01 SDK name: 1.8_64

• The managesdk.bat (Windows) or managesdk.sh (Linux) command with the -enableProfile and -sdkname options can be used to updated the version of Java SDK being used by the profile. You will probably also want to use the -setNewProfileDefault option for new profiles.
• Refer to this article to update the version of Java SDK being used by a deployment manager.
• Refer to this article to update the version of Java SDK being used by a node.