In the Configurations tab, expand your configuration.
Expand Database/Instance[n]/BPM Settings.
In the Connector file location field, enter the full path (including the file name) where you copied the connector files.
For example:
c:/oracle/bpm1111x/eppmjars/prm-bpm-connector-11.1.1.x-v1.0.jar or /home/oracle/bpm1111x/prm-bpm-connector-11.1.1.x-v1.0.jar
In the BPM library path field, enter the path of the directory where you copied all the 11g jars.
Note: If the above settings are incorrect or the BPM jar files are incomplete, you will be prompted with an error message when you try to configure the BPM. Verify that your settings and jar files are correct.
Right-click BPM Configuration, then select Configure to set options from the dialog box. If you receive an error message, check your values from the previous steps in this section.
To configure P6 to use BPM 11g, add the following settings:
Caution: Do not put a forward slash / at the end of the URL. For example, it should read only http://host:port, and not http://host:port/.
In the bpm.user field, enter the BPM 11g user with administrative access to BPM.
In the bpm.password field, enter the password for the user.
In the bpm.t3.url field, enter the T3 URL for your configuration. For example: t3://host:port/soa-infra
In the bpm.security.realm field, enter the name of the security realm used by BPM. This is jazn.com by default.
In the bpm.soap.url field, enter the URL for the SOAP services. Usually this URL takes the form of http://host:port.
In the bpm.workspace.url field, enter an address in the form of http://host:port that indicates where the BPM Workspace application is hosted.
In the bpm.partition field, enter the name of the SOA partition containing the BPM composite applications you would like to use in P6. The default partition name is default.
Click OK and save changes. When the configuration is complete, you will see a BPM properties have been configured message.
Restart the P6 application server.
Tips
To verify the sample workflow works:
Open the P6 Administrator application.
In the Configurations tab, expand your configuration.
Expand Web Services/Security/Authentication.
In the Mode field, select Username Token Profile.
Expand Web Services/Security/Authentication/Username Token Profile/Nonce and set Require Nonce to false.
Expand Web Services/Security/Authentication/Username Token Profile/Created and set Require Created to false.
Expand Web Services/Security/Authentication/SAML Token Profile and set Require Signed SAML Token to false.
Expand Web Services/Security/Message Protection:
Set Require Timestamp to false.
Set Require Digital Signatures for Incoming Messages to false.
Set Require Encryption for Incoming Messages to false.