Adding security arguments to the application server startup script (WebLogic Server only)

You must add several environment arguments Java™ Authentication and Authorization Service (JAAS) to the security arguments in the WebLogic Server startup script to enable users to connect to Content Platform Engine by using Administration Console for Content Platform Engine.

About this task

Important: If you are deploying Content Platform Engine in a highly available cluster, you must complete the following steps for each node in the cluster.

To add JAAS arguments to the WebLogic Server startup script:

1. Open the WebLogic Server startup script, startWebLogic.cmd or startWebLogic.sh. By default, the startup script is in the following directory (WL_HOME is the installation path for WebLogic Server):

   Operating system	Default location
   AIX®, HPUX, HPUXi, Linux, Linux for System z, Solaris	WL_HOME/user_projects/domains/domain_name/bin/startWebLogic.sh
   Windows	WL_HOME\user_projects\domains\domain_name\bin\startWebLogic.cmd

2. Add the environment arguments for JAAS to the startup script:
   • On AIX, HPUX, HPUXi, Linux, Linux for System z, and Solaris, the (default) Installation_directory is /opt/IBM/FileNet/ContentEngine:

     echo "${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} 
     -Djava.security.auth.login.config=Installation_directory 
     /config/samples/jaas.conf.WebLogic -Dweblogic.Name=${SERVER_NAME} 
     -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} 
     ${PROXY_SETTINGS} ${SERVER_CLASS}"
     
     
     ${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} 
     -Djava.security.auth.login.config=Installation_directory
     /config/samples/jaas.conf.WebLogic -Dweblogic.Name=${SERVER_NAME} 
     -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} 
     ${PROXY_SETTINGS} ${SERVER_CLASS}

   • On Windows, the (default) Installation_directory is C:\Program Files (x86)\ibm\FileNet\ContentEngine:

     echo Starting WLS with line:
     echo %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% 
     -Dweblogic.Name=%SERVER_NAME% 
     -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy 
     %JAVA_OPTIONS% %PROXY_SETTINGS% %SERVER_CLASS%
     	%JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% 
     -Djava.security.auth.login.config=Installation_directory
     \config\samples\jaas.conf.WebLogic 
     -Dweblogic.Name=%SERVER_NAME% 
     -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %JAVA_OPTIONS% 
     %PROXY_SETTINGS% %SERVER_CLASS%
     
     
     echo Redirecting output from WLS window to %WLS_REDIRECT_LOG%
     %JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% 
     -Djava.security.auth.login.config=Installation_directory
     \config\samples\jaas.conf.WebLogic 
     -Dweblogic.Name=%SERVER_NAME% 
     -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %JAVA_OPTIONS% 
     %PROXY_SETTINGS% %SERVER_CLASS%  >"%WLS_REDIRECT_LOG%" 2>&1 
     )

3. Save your changes to the startup script.
4. If you have a managed server environment, add the following lines to your startManagerServer.sh or startManagedServer.cmd file and save your changes to the file:

   For startManagerServer.sh:

   JAVA_OPTIONS="$SAVE_JAVA_OPTIONS 
    -Djava.security.auth.login.config=${WL_HOME}/config/samples/jaas.conf.WebLogic"
   export SAVE_JAVA_OPTIONS

   For startManagedServer.cmd:

   set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS% 
    -Djava.security.auth.login.config="WL_HOME\config\samples\jaas.conf.WebLogic"

5. Restart the application server and verify that the application server starts without errors.