Setting the Bootstrap Location if P6 Team Member is in a Different WebLogic Server from P6

Contents

If you will run the p6tm.ear file in the same WebLogic server as P6, skip this section and continue to Adding P6 Team Member to WebLogic.

If you will run the p6tm.ear file in a different WebLogic Server from P6, set the location of your P6 bootstrap file. When you set the bootstrap argument, you will set it for the home directory where you want your p6tm.ear file to connect.

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. If your bootstrap file has only one database, skip this step.

      If your bootstrap file contains more than one database, you need to add an argument clarifying which database you want to use. The line will look similar to the following:

      -Ddatabase.instance=db_id

      where db_id is the database instance you want to use (for example, -Ddatabase.instance=2).

      The whole line should look similar to the following (all one line):

      -Dprimavera.bootstrap.home=p6home -Ddatabase.instance=db_id

   3. Set the memory settings to maximize performance.
      • In Windows, the line should look similar to the following (all one line):

        -Dprimavera.bootstrap.home=p6home -Xms256m -Xmx512m

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

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

        -Dprimavera.bootstrap.home=p6home -Xms256m -Xmx512m

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

   4. Below the -Dprimavera line, enter the variable to connect to your config folder:
      • In Windows, the line should look similar to the following (all one line):

        -Dtmweb.home=tmweb_home\tmws

        where tmweb_home is the P6 Team Member Web home directory that was set during installation (for example, C:\P6EPPM_1\tmws).

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

        -Dtmweb.home=tmweb_home/tmws

        where tmweb_home is the P6 Team Member Web home directory that was set during installation (for example, /usr/P6EPPM_1/tmws).

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.