FileNet P8 Workplace XT, Version 1.1.5       Application server:  WebLogic Application Server   Operating systems:  AIX, HP-UX, Linux, Linux on System z, Solaris

Setting up JAAS login information for authentication and memory settings for resource usage on WebLogic Server for UNIX

You can set up JAAS login information and configure memory settings for UNIX by editing WebLogic Server files.

Remember: In high availability clustered server configurations, for steps that require Java™ Virtual Machine (JVM) settings to be made make sure to make these changes for every node in the application server configuration.
To set up JAAS LOGIN information:
  1. Stop WebLogic Server, if it is running.
  2. Make a backup copy of the setDomainEnv.sh file.
  3. Do one of the following to edit the MEM_ARGS variable in the setDomainEnv file:
    • For all systems except those using JRockit Java:

      Find the MEM_ARGS variable and append the following to any existing settings:

      -XX:MaxPermSize=size m

      where size is the value, in MB, of the MaxPermSize. Refer to your application server vendor recommendation for a value for your configuration. For more information about performance tuning, see the IBM FileNet® P8 Performance Tuning Guide.

    • For systems using JRockit Java:

      Find the MEM_ARGS variable and append the following to any existing settings:

      -Xgc:gencon

    If the MEM_ARGS variable does not exist, add it to the setDomainEnv.sh file.

  4. If your application server uses the IBM® JVM, edit the JAVA_OPTIONS variable to improve performance.

    Modify the following line in the setDomainEnv file:

    JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES} -Dwlw.iterativeDev=${iterativeDevFlag} -Dwlw.testConsole=${testConsoleFlag} -Dwlw.logErrorsToConsole=

    ${logErrorsToConsoleFlag}" export JAVA_OPTIONS

    insert these entries (without a carriage return) before the export JAVA_OPTIONS line:

    -Dprogram.name=$PROGNAME -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5"

    Result:

    JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES} -Dwlw.iterativeDev=${iterativeDevFlag} -Dwlw.testConsole=${testConsoleFlag} -Dwlw.logErrorsToConsole=

    ${logErrorsToConsoleFlag} - Dprogram.name=$PROGNAME -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5" export JAVA_OPTIONS

  5. Configure JAAS login. Add one of the following right after the classpath entry for WebLogic Server.

    Enter the JAAS_LOGIN entry as a single line without line breaks. Do not copy and paste the text from this guide because hidden formatting can cause problems with the entry. Instead, type the entry into the script.

    Important: Your path might be slightly different depending on the version of your client installations, or whether you have chosen a custom path for installation. For example, if your Content Engine Client is at 4.0, this path might include a samples directory under the config directory. Verify the location of the file before you enter the path.
    Option Description
    AIX®
     # JAAS LOGIN configuration setting
    JAAS_LOGIN="${JAAS_LOGIN}" -Djava.security.auth.login.config= " install_path /IBM/FileNet/WebClient/CE_API/config/jaas.conf.WebLogic"
     JAAS_LOGIN="${JAAS_LOGIN}" -Dlogin.configuration.provider=
    com.ibm.security.auth.login.ConfigFile
    where install_path is the location where you installed Workplace XT. For example:
    "/opt/IBM/FileNet/WebClient/CE_API
    /config/jaas.conf.WebLogic"
    UNIX
    # JAAS LOGIN configuration setting
    JAAS_LOGIN="${JAAS_LOGIN}" -Djava.security.auth.login.config= "install_path /IBM/FileNet/WebClient/CE_API/config/jaas.conf.WebLogic"
    where install_path is the location where you installed Workplace XT. For example,
    "/opt/IBM/FileNet/WebClient/CE_API
    /config/jaas.conf.WebLogic" 
  6. Save and close the setDomainEnv.sh file.
  7. Make a backup copy of the application server startup script.
    • If you are using a WebLogic Server domain, modify startWebLogic.sh.
    • If you are not using a WebLogic Server domain, modify startWLS.sh.
  8. Use a text editor to open and edit the application server startup script.
  9. Add JAAS_LOGIN section as indicated in the examples below.
    ${JAVA_HOME}/bin/java ${JAVA_VM} -version
    if [ "${WLS_REDIRECT_LOG}" = "" ] ; 
    then
    echo "Starting WLS with line:"
    echo "${JAVA_HOME}/bin/java 
    ${JAVA_VM} 
    ${MEM_ARGS} ${JAVA_OPTIONS} 
    -Dweblogic.Name=${SERVER_
    NAME} -Djava.security.policy=
    ${WL_HOME}/server/lib
    /weblogic.policy 
    ${PROXY_SETTINGS} 
    ${SERVER_CLASS
    }"
    ${JAVA_HOME}/bin/java 
    ${JAVA_VM} ${MEM_ARGS} 
    ${JAVA_OPTIONS} ${JAAS_LOGIN} 
    -Dweblogic.Name=${SERVER_NAME} 
    -Djava.security.policy=
    ${WL_HOME}
    /server/lib/weblogic.policy 
    ${PROXY_SETTINGS} ${SERVER_
    CLASS}
     else
    echo "Redirecting output from 
    WLS window
     to ${WLS_REDIRECT_LOG}"
    ${JAVA_HOME}/bin/java 
    ${JAVA_VM} 
    ${MEM_ARGS} ${JAVA_OPTIONS} 
    ${JAAS_LOGIN} 
    -Dweblogic.Name=${SERVER_NAME} 
    -Djava.security.policy=
    ${WL_HOME}
    /server/lib/weblogic.policy 
    ${PROXY_SETTINGS} 
    ${SERVER_CLASS} 
    >"${WLS_REDIRECT_LOG}" 2>&1
    fi
  10. Save and close the application server startup script file.


Feedback

Last updated: March 2013
wxtip025.htm

© Copyright IBM Corporation 2013.
This information center is powered by Eclipse technology. (http://www.eclipse.org)