This step is compulsory. The server must be restarted for the security changes to take effect and to add additional required users. The server can be stopped using the stopServer.bat file in the profiles/AppSrv01/bin directory of the WebSphere Application Server installation. This is similar to starting the server described in Introduction.
Before restarting the application server (e.g. server1), it is necessary to make the registry and cryptography JAR files available to WebSphere Application Server. The registry JAR file contains classes necessary for the security configuration and the cryptography JAR file contains necessary configuration settings and data for password security.
The Registry.jar file is located in the lib directory of the SDEJ installation. Copy this file into the lib directory of the WebSphere Application Server installation.
The default CryptoConfig.jar file is located in the <SERVER_DIR>/project/properties directory of the Curam installation. Copy this file into the Java jre/lib/ext directory. If you require customizations to the Curam cryptographic configuration see the Curam Security Handbook for more information.
Now start the application server (e.g. server1) and open the Administrative Console to continue with the configuration steps. Since the security configuration is complete and the scripting changes have been made, it is now possible to use the SDEJ scripts to restart the WebSphere Application Server. See Starting and Stopping WebSphere Servers for more details on restarting the server.
The Administrative Console should now be opened to continue with the configuration. Now that global security is enabled, you will be required to login to the console with the username and password credentials set up previously.