配置使用P6(EPPM) 定時服務(Job Services)

Table of Contents

Configuring a Job Services Server Using p6services.jar

Configuring a Job Services Server Using p6jobservices.war

---

對於大中型部署，Oracle建議爲作業服務設置一個專用節點，並禁止作業服務在接受用戶流量的服務器上運行。

有關構成中型或大型部署的詳細信息，請參閱《The P6 EPPM Performance and Sizing Guide》。

以下說明假定已經配置了接受用戶流量的服務器。

 

Configuring a Job Services Server Using p6services.jar

Follow the guidelines below to configure the dedicated job services server using p6services.jar:

1. Copy the p6services.jar from the p6home directory where you installed P6 to a node that will use job services.
2. Ensure a supported JRE is in the system path. (See the Tested Configuration for supported JREs.)
3. Open a new command line or terminal window.
4. Navigate to the folder where p6services.jar was copied (for example, c:\jobservices).
5. Run the services application by entering java -Xms<MEMORY SIZE> –Xmx<MEMORY SIZE> –jar p6services.jar in the window. (See the P6 EPPM Performance and Sizing Guide for the correct value for the <MEMORY SIZE> setting for your environment. The settings in the example are the recommended values.)

   The line should look similar to the following:

   java -Xms4096m –Xmx4096m –jar p6services.jar

   If you are using Sun JDK, it should look similar to the following:

   java -server -Xms4096m –Xmx4096m –jar p6services.jar

6. If a BREBootStrap.xml file is in the USER_HOME, you can specify the location to the BREBootstrap.xml file by adding the following line:

   Note:

   • USER_HOME refers to your home directory. For example, in Windows it could be C:\Users\<USER_NAME> or C:\Documents and Settings\<USER_NAME>; in UNIX, it could be /home/<USER_NAME>.
   • If this is the first time you are launching p6services.jar, and a BREBootStrap.xml file does not exist in the USER_HOME, the database configuration wizard will launch. Skip to the next step.

   –Dprimavera.bootstrap.home= <BOOTSTRAP_LOCATION>

   The line should look similar to the following:

   java -Xms4096m –Xmx4096m –Dprimavera.bootstrap.home= <BOOTSTRAP_LOCATION> -jar p6services.jar

   where <BOOTSTRAP_LOCATION> is the location where the BREBootStrap.xml is located (for example, C:/USER_HOME).

7. If this is the first time you are launching p6services.jar, and a BREBootStrap.xml file does not exist in the <USER_HOME> directory (or <BOOTSTRAP_HOME> directory if the primavera.bootstrap.home is specified), the database configuration wizard will launch.

   Follow the steps in Changing Database Connection Settings for P6 .

   Create a new configuration when The Installer has detected... dialog box appears and give this new configuration a distinct name. For example, if you chose "P6 Users" for the configuration name for the server accepting user traffic, name the new configuration "P6 Job Services."

   Note: Create a new configuration for Job Services to ensure optimal database performance. Job Services could slow down performance if it is part of the same configuration.

8. In the Primavera P6 Administrator:
   1. Locate the Services/Enable All Services setting for the configuration created for the job services server (for example, P6 Job Services). Set the setting to true to enable all services.
   2. Locate the Services/Enable All Services setting for the configuration created for user traffic (for example, P6 Users). Set the setting to false to disable all services.

Configuring a Job Services Server Using p6jobservices.war

Note: These instructions assume that you have already installed and configured WebLogic Middleware and have deployed P6. These instructions provide single WebLogic node deployment steps, but you can target the application to a WebLogic cluster.

Follow the guidelines below to configure a dedicated job services server using p6jobservices.war:

1. Create a new directory in the P6 EPPM installation folder for p6jobservices.
2. Copy the following files from the p6home directory where you installed P6 to the new directory you created in the previous step:
   • p6jobservices.war
   • adminpv.cmd or adminpv.sh
   • dbconfigpv.cmd or dbconfigpv.sh
   • installp6keystore.bat or installp6keystore.sh
   • p6keystore.jks
   • lib folder and all files
3. In the new directory:
   1. Open adminpv.cmd or adminpv.sh in a text editor.
      • Change the PV_HOME environment variable to match the location of the new directory.
      • Change the JAVA_HOME environment variable to match the location of your JDK home directory.
      • Save changes and close the file.
   2. Open dbconfigpv.cmd or dbconfigpv.sh in a text editor.
      • Change the PV_HOME environment variable to match the location of the new directory.
      • Change the JAVA_HOME environment variable to match the location of your JDK home directory.
      • Save changes and close the file
   3. Open installp6keystore.bat or installp6keystore.sh in a text editor.
      • Change the JAVA_HOME environment variable to match the location of your JDK home directory.
      • Save changes and close the file
4. Copy the new directory to a WebLogic node where you will deploy p6jobservices.war.

   If the WebLogic Admin Server runs on a different physical node from your managed server, copy the directory to your admin server to deploy the application.

   If the PV_HOME or JAVA_HOME directory path is different from the path you modified earlier, you must update the files to reflect the actual location on the new node.

   Note: If you deploy p6jobservices.war to a cluster, the directory must be present on all nodes in the cluster.

5. If you are using external encryption, generate a new password file for reading p6keystore.jks using the following command:
   • Windows: installp6keystore.cmd -genpassfile
   • Unix: ./installp6keystore.sh -genpassfile

     Note: For more information on encryption keys for P6 EPPM, see: Oracle Support Document 2268703.1 External Storage Of Encryption Keys For P6 EPPM at https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=2268703.1

6. To create a BREBootStrap.xml file in the job services directory, execute dbconfigpv.cmd or dbconfigpv.sh.
7. In the Database Configuration Wizard:
   1. Select your database type, then click Next.
   2. Enter the required information for connecting to your database, then click Next.
   3. Select the option to create a new configuration for job services, then click Next.
   4. Click OK.
   5. Check that a BREBootStrap.xml file was created in the job services directory.

      Note: If you deploy p6jobservices.war to a cluster, you must create a BREBootStrap.xml file on all nodes of the cluster.

8. Create a new managed server in your WebLogic domain and set the following JVM parameters for the managed server:
   • -Xms<MEMORY SIZE> -Xmx<MEMORY SIZE>

     For example: -Xms4096m –Xmx4096m

     Note: See the P6 EPPM Performance and Sizing Guide for the correct value for the <MEMORY SIZE> setting for your environment. The settings in the example are the recommended values.

   • -Dprimavera.bootstrap.home=<BOOTSTRAP_LOCATION>

     Where <BOOTSTRAP_LOCATION> is the location of the BREBootStrap.xml file.

9. Deploy p6jobservices.war to the managed server.

   See the P6 EPPM WebLogic Configuration Guide.

10. Launch adminpv.cmd or adminpv.sh.
    1. Select the configuration used by job services.
    2. Expand Services and select General.
    3. Select the Enable All Services option.
    4. Select the configurations used by all other P6 EPPM web deployments and clear the Enable All Services option.
    5. Restart all the deployments you changed.

When upgrading your P6 EPPM environment perform the following steps:

1. Replace the following files in the job services directory with the upgraded files from your p6home directory:
   • p6jobservices.war
   • lib folder and all files
2. Launch adminpv.cmd or adminpv.sh.
   1. On the Configurations tab, right-click the job services configuration.
   2. Click Update to latest version.
   3. Click Save Changes.
3. To redeploy the updated p6jobservices.war to your WebLogic environment:
   1. Login to your WebLogic Administration Console.
   2. In the Change Center pane, click Lock & Edit.
   3. In the Domain Structure pane, click Deployments.
   4. In the Configuration tab on the Summary of Deployments page, click Update.
   5. Click Finish.