WebLogic guidelines
Follow the guidelines in this section when deploying IBM® EMM products on WebLogic.
All versions of WebLogic, all IBM® EMM products
*
IBM® EMM products customize the JVM used by WebLogic. You may need to create a WebLogic instance dedicated to IBM® EMM products if you encounter JVM-related errors.
*
Verify that the SDK selected for the WebLogic domain you are using is the Sun SDK by looking in the startup script (startWebLogic.cmd) for the JAVA_VENDOR variable. It should be set to: JAVA_VENDOR=Sun . If it is set to JAVA_VENDOR=BEA , JRockit has been selected. JRockit is not supported. To change the selected SDK, refer to the WebLogic documentation.
*
Deploy the IBM® EMM products as web application modules.
*
On UNIX™ systems, you must start WebLogic from the console to allow correct rendering of graphical charts. The console is usually the machine on which the server is running. In some cases, however, the web application server is set up differently.
If a console is not accessible or does not exist, you can emulate a console using Exceed. You must configure Exceed so that your local Xserver process connects to the UNIX™ machine in root window or single window mode. If you start the web application server using Exceed, you must keep Exceed running in the background to allow the web application server to continue running. Please contact IBM® Technical Support for detailed instructions if you encounter problems with chart rendering.
Connecting to the UNIX™ machine via telnet or SSH always causes problems rendering charts.
*
If you are configuring WebLogic to use the IIS plug-in, review the WebLogic documentation.
*
If deploying in a production environment, set the JVM memory heap size parameters to 1024 by adding the following line to the setDomainEnv script: Set MEM_ARGS=-Xms1024m -Xmx1024m -XX:MaxPermSize=256m
Copyright IBM Corporation 2013. All Rights Reserved.