Restarting WebSphere with Security Enabled

Stopping and restarting Websphere when security is enabled involves typing specific commands, including the WebSphere username and password, into a Command Prompt window (Windows) or terminal window (Linux).

  1. If necessary, open a Command Prompt window (Windows) or terminal window (Linux).

  2. Navigate to the <websphere_install_directory>\bin directory.

  3. Type one of the following commands on a single line to stop the WebSphere server, where user is the SIMULIA Execution Engine user’s name and password is the SIMULIA Execution Engine user’s password:

    • Windows: stopserver server1 -username <user> -password <password>

    • Linux: ./stopServer.sh server1 -username <user> -password <password>

    Note: If you fail to supply the user name and password when stopping the server, a dialog box may appear allowing you to specify these items.

    Important: If you have been using a desktop icon or Windows Start menu option to stop the server, it must be updated to specify the user ID and password. For more information, see Updating Windows Shortcuts for Security Authorization.

    A message appears when the server stop action is completed.

  4. After stopping WebSphere on Linux, you must log out (and preferably reboot your system) and log back in. This action is necessary so that the WebSphere server will recognize changes to the environment in /etc/profile made by the SIMULIA Execution Engine installer.

  5. Type one of the following commands to restart the WebSphere server (it is not necessary to specify the user name and password when starting the application server):

    • Windows: startserver server1

    • Linux: ./startServer.sh server1

    A message appears when the server start action is completed.

    Note: An error in configuring security (such as an incorrect ID or password) can cause the server to fail to start. Because the server also runs the Administrative Console, you will not be able to use the console to fix the configuration error. In this case, edit the security.xml file in the <websphere_install_directory>\AppServer\profiles\<profileName>\config\cells<computer name_NodeCell> directory, and fix the configuration parameters directly in that file. Once completed, you must restart the server. SIMULIA Execution Engine Security is now fully enabled.