Adding P6 as a WebLogic Application

To add P6 as a WebLogic application:

Note: These steps assume that you have set the arguments in the WebLogic
Administration Console (see Setting Arguments for P6) and that the Admin Server
and Managed Servers are running (see Starting and Stopping the Admin Server
and Managed or Clustered Servers).
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
that 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, click Deployments.
5. In the Summary of Deployments pane, in the Control tab,
click Install.
6. In the Install Application Assistant pane:
a. Navigate to the P6 EPPM home directory.
b. Select the p6.ear file.
c. Click Next.
7. In the Install Application Assistant pane:
a. Select Install this deployment as an application.
b. Click Next.
8. In the Install Application Assistant pane:
 a. Click the server or cluster where you want to deploy the
application.
b. Click Next.
9. In the Install Application Assistant pane, click Next to accept the
default options.
10. Review the configuration settings you have chosen, then
click Finish to complete the installation.
11. In the Settings for P6 window, click Save.
12. Proceed to Starting the P6 Application in WebLogic.
Starting the P6 Application in WebLogic
To start the P6 application in WebLogic:
1. In the Change Center pane, click Activate Changes.
2. In the Domain Structure pane, click Deployments.
3. In the Summary of Deployments pane, select p6.
4. In the Summary of Deployments pane, in the Control tab:
a. Click the down arrow to the right of the Start button.
b. Click Servicing all requests.
5. In the Start Application Assistant pane, click Yes.
6. In the Summary of Deployments pane, view the link in
the State column of the row that contains 'p6.' Wait a few minutes, then
click Refresh.
The p6 State column should show Active.
7. Repeat the Deploying P6 in WebLogic process for the ‘p6help.war’
(optional, see notes below) and 'P6Tutorials.war' files.
Notes:
o Do not do this step for the ‘p6help.war’ file if you want to use
OTN for your help. The OTN link is the default link in the P6
Administrator application. OTN will have the most up-to-date
documentation for the P6 Help.
o When repeating the process for the P6 Help and Tutorials file
in Adding P6 as a WebLogic Application, navigate to the location of
the help and tutorials files as determined when you installed your P6
EPPM applications.
2. Verify that the State column for both files shows Active.
3. Logout of the Administration Console.
 4. Navigate to your P6 and verify the P6 login page displays in your
browser.
Example URL:
http://localhost:7001/p6
where localhost is your server's host name and 7001 is the default listen
port.
Note: The default context root is /p6, which is also the cookie path. If you
change the context root or use a fronting web server with a different
context root, you need to modify the cookie path used by P6 to match. See
the WebLogic documentation for more information on changing the cookie
path.
Tips
After you deploy P6, use the P6 EPPM Post Installation Administrator's Guide to do
the following:
 Make sure to review additional configuration steps using the P6
Administrator application in "Configuring a Setting for WebLogic on
Microsoft SQL Server 2005 Database" chapter.
 If you did not deploy the p6help.war and are using OTN instead, you
do not need to configure anything in the P6 Administrator application.
If you deploy the p6help.war file, a P6 Administrator application setting
must be populated to complete the P6 Help configuration. See information
about the Help Server URL setting in the P6 Administrator application.
 If you delete a p6.ear, p6help.war, or a P6Tutorials.war file from
WebLogic and then redeploy any of those files, check weblogic_home\
user_projects\domains\your_domain\config\ for a folder called
"fmwconfig." If the folder is there, delete it.
 If you do not use anything other than P6, see "Precompiling P6"
chapter.
Creating an XML File for Your Deployment Plan
Contents

To create an XML file for your deployment plan:

1. Open Notepad or other text editor.
2. Save the new file as P6R82DeploymentPlan.xml in your P6 home
directory (for example, C:\p6home in Windows or /usr/p6home in UNIX).
Note: You can save your XML file in another location, but saving it in your
P6 home directory will make it easier to find when you deploy it in
WebLogic.
3. Enter the following information into your
P6R82DeploymentPlan.xml file:
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-
plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan
http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-
plan.xsd" global-variables="false">
<application-name>p6</application-name>
<variable-definition>
<variable>
<name>SessionDescriptor_cookie_http_only</name>
<value>false</value>
</variable>
<variable>
<name>SessionDescriptor_cookie_path</name>
<value>/p6</value>
</variable>
</variable-definition>
<module-override>
<module-name>p6.ear</module-name>
<module-type>ear</module-type>
<module-descriptor external="false">
<root-element>weblogic-application</root-element>
<uri>META-INF/weblogic-application.xml</uri>
<variable-assignment>
<name>SessionDescriptor_cookie_http_only</name>
<xpath>/weblogic-application/session-descriptor/cookie-http-only</
xpath>
</variable-assignment>
</module-descriptor>
</module-override>
<module-override>
<module-name>p6.war</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>weblogic-web-app</root-element>
<uri>WEB-INF/weblogic.xml</uri>
<variable-assignment>
<name>SessionDescriptor_cookie_path</name>
<xpath>/weblogic-web-app/session-descriptor/cookie-path</xpath>
</variable-assignment>
</module-descriptor>
</module-override>
</deployment-plan>
4. Save the file and close it.
Adding Your Deployment Plan to Your P6 Deployment in WebLogic
Contents

To add your deployment plan to your p6.ear deployment:

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
that you created in 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, click Deployments.
5. In the Summary of Deployments pane:
 a. Select the p6 option.
b. Click Update.
6. In the Update Application Assistant pane, click Change Path in
the Deployment plan path field.
7. In the Update Application Assistant pane:
a. Navigate to the location where your deployment plan is in
your local file system and select the XML file you created (for
example, c:\p6home\P6R82DeploymentPlan.xml).
b. Click Next.
8. In the Update Application Assistant pane:
a. Choose Update this application in place with new deployment
plan changes. (A deployment plan must be specified for this option).
b. Click Next.
9. In the Update Application Assistant pane:
a. Review your choices.
b. Click Finish.
10. In the Change Center pane, click Activate Changes.
11. Verify that the State column for 'p6' shows Active.
12. Logout of the Administration Console.