Setting Arguments in the WebLogic Administration Console for P6

Contents

Use these instructions if you will deploy P6 in a Managed or clustered server. To continue configuring WebLogic for P6, add the following arguments to your Managed or clustered server in the WebLogic Administration console:

1. Launch the WebLogic Administration Console.

   Note: You can open the Administration Console via a web browser using this address: http://serverIP:listenport/console. The default listenport is 7001.

2. In the Welcome window, log in using the user name and password you created when you created your WebLogic domain.
3. In the Change Center pane of the Administration Console, click Lock & Edit.
4. In the Domain Structure pane:
   1. Expand Environment.
   2. Click Servers.
5. In the Summary of Servers pane, in the Control tab, click the link for your managed server name.
6. In the Settings for <managed server name> pane, select the Server Start tab.
7. Locate the Arguments field and set the following:
   1. Set the Primavera bootstrap system property (it should be all one line with no space between "-" and "Dprimavera").
      • In Windows, the line should look similar to the following (all one line):

        -Dprimavera.bootstrap.home=p6home

        where p6home is the P6 home directory that was set during installation (for example, C:\P6EPPM_1\p6).

      • In UNIX, the line should look similar to the following (all one line):

        -Dprimavera.bootstrap.home=p6home

        where p6home is the P6 home directory that was set during installation (for example, /usr/P6EPPM_1/p6).

   2. (Optional) If you need WebLogic to process UTF-8 characters, add the following argument (as all one line) after the bootstrap property with one space between them:

      -Dweblogic.webservice.i18n.charset=utf-8

      • For example, in Windows:

        -Dprimavera.bootstrap.home=p6home -Dweblogic.webservice.i18n.charset=utf-8

      • For example, in Unix:

        -Dprimavera.bootstrap.home=p6home -Dweblogic.webservice.i18n.charset=utf-8

   3. For improved performance when starting the P6 domain in WebLogic, add the following JVM argument (as all one line) immediately after the previous argument with one space between them:

      -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory

      • For example, in Windows:

        -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory

      • For example, in Unix:

        -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory

        Note: Be sure to include a space before the -Djavax argument. Properties after the bootstrap can be in any order.

   4. (For Unix servers) If you don't have a graphical environment installed, you must set the server's JVM to bypass server-side rendering optimizations. If you don't add the argument, you may not be able to see graphics on pages, and the server logs will report NoClassDefFoundError errors.

      Add this JVM argument:

      -Djava.awt.headless=true

      For example, in Unix:

      -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -Djava.awt.headless=true

   5. If using the Sun JDK, set the Java Virtual Machine by entering the following flag at the beginning of the arguments you just added:

      -server

      • In Windows, the line should look similar to the following:

        -server -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory

      • In Unix, the line should look similar to the following:

        -server -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory

   6. If using the Sun JDK, increase the JVM MaxPermSize setting to avoid Out-of-Memory errors. The MaxPermSize setting should be set to at least 256m. Also, modify memory settings to maximize performance. To do this, add the following lines after the -Dprimavera line to set the NewSize, MaxNewSize, and SurvivorRatio and the total Initial (-Xms) and Maximum heap size (-Xmx).

      The complete line could look similar to the following if using the Sun JDK (all one line):

      • In Windows, the line should look similar to the following:

        -server -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -XX:MaxPermSize=256m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=8 -Xms2048m -Xmx2048m

      • In Unix, the line should look similar to the following:

        -server -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -XX:MaxPermSize=256m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=8 -Xms2048m -Xmx2048m

        Note: Be sure to include a space before the -XX: specification. Properties after the bootstrap can be in any order.

   7. (Optional) If using the Sun JDK and running Publication Services on a larger database, change the JVM parameters to increase the GC Time Ratio; add the following JVM setting (as all one line) immediately after the setting you just added:

      -XX:+UseParallelGC -XX:+UseParallelOldGC -XX:GCTimeRatio=19

      Notes:

      • Be sure to include a space before the -XX:+ specification. Properties after the bootstrap can be in any order.
      • R8.3 can run publication services through the P6 EPPM Extended Schema. See "Improved Reporting and Publication Services (R8.3)" in the new features guide, or "Configuring P6 for Reporting" and "Working with Publication Services for Reporting" in the Connecting BI Publisher to P6 guide for more information on Publication Services.
      • In Windows, the line should look similar to the following:

        -server -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -XX:MaxPermSize=256m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=8 -Xms2048m -Xmx2048m -XX:+UseParallelGC -XX:+UseParallelOldGC -XX:GCTimeRatio=19

      • In Unix, the line should look similar to the following:

        -server -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -XX:MaxPermSize=256m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=8 -Xms2048m -Xmx2048m -XX:+UseParallelGC -XX:+UseParallelOldGC -XX:GCTimeRatio=19

   8. (Optional) If you are having memory issues on the JVM, collect garbage logs by using the following parameter as all one line immediately after the previous line:

      -Xloggc:path to the log file

      • In Windows, the line should look similar to the following:

        -server -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -XX:MaxPermSize=256m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=8 -Xms2048m -Xmx2048m -XX:+UseParallelGC -XX:+UseParallelOldGC -XX:GCTimeRatio=19 -Xloggc:path to the log file

      • In Unix, the line should look similar to the following:

        -server -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -XX:MaxPermSize=256m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=8 -Xms2048m -Xmx2048m -XX:+UseParallelGC -XX:+UseParallelOldGC -XX:GCTimeRatio=19 -Xloggc:path to the log file

   9. If using the JRockit JDK, modify memory settings to maximize performance.

      Add the following lines after the -Dprimavera line to set the total Initial (-Xms) and maximum heap (-Xmx) size.

      The complete line would look similar to the following if using the JRockit JDK (all one line):

      • For Windows:

        -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -Xms2048m -Xmx2048m

      • For Unix:

        -Dprimavera.bootstrap.home=p6home -Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory -Xms2048m -Xmx2048m

8. Click Save.
9. In the Change Center pane, click Activate Changes.
10. Restart your managed server:
    1. In the Domain Structure pane:
       1. Expand Environment.
       2. Click Servers.
    2. In the Summary of Servers pane:
       1. Select the Control tab.
       2. Select the option for your managed server.
    3. Click Shutdown.
       1. Click the down arrow to the right of the Shutdown button.
       2. Click When work completes or Force Shutdown Now.
       3. In the Server Life Cycle Assistant pane, click Yes.
       4. Select the option for your managed server.
       5. Click Start.
    4. In the Server Life Cycle Assistant pane, click Yes.
    5. In the Summary of Servers pane, click the 'Start Refresh' icon in the middle of the pane to see when the State column says 'RUNNING.'
11. Repeat these steps for each managed server.

Tips

Once you have finished setting the arguments, you will use the following sections to deploy P6 and to start your managed or clustered server: Deploying P6 in WebLogic and Starting and Stopping Managed Servers.