To move data between applications, Primavera Gateway needs to know where to get and send information. Set this up by adding application deployment connections by specifying an Endpoint URL for each application.
For P6 Cloud service, contact Oracle Support to:
- add one or more P6 deployments
- copy an existing P6 deployment
For on-premises installations, add or edit a P6 deployment connection as follows:
- Enter the Primavera Gateway URL in the format:
http://<host name>:<port>/gateway
Where, <host name> and <port> should match those of your Primavera Gateway domain.
- Sign in to Primavera Gateway with administration credentials.
- In the sidebar, select Configuration.
- Select the Deployments tab.
- Select Add... or Edit....
The Deployment wizard displays.
- In the General step, select P6 from the Select Application Provider list, and name the deployment.
Note: Select Next on each screen to advance to the next step.
- In the Deployment step, set up P6 connectivity from Gateway:
- P6 Webservices authentication type: Select the authentication type as SAML2.0 Token or UserName Token.
- User Name: Enter the name of a P6 administrator with access to projects in P6 EPPM.
- Password: If you chose UserName Token authentication, enter the case-sensitive password of the P6 administrator.
Endpoint: Enter the URL to connect with P6 Web Services in the format, http:<host name>:<port>/p6ws/services/SyncServiceV1
- P6 Database Instance ID: Enter the database instance ID associated with the P6 application.
- SAML 2.0 Token File: If you chose SAML2.0 Token authentication, then browse or enter the location of the downloaded SAML 2.0 token XML file used by P6 Web Services for authentication.
- Enable Encryption: Select this option if you want to enable encryption when using P6 web services.
- Keystore File: Enter or Browse... to the keystore file.
For more details on how to generate a keystore file and keystore password, see Enabling Encryption Between Gateway and P6 Web Services.
- Keystore Password: Enter the password for the keystore file.
- Certificate Alias: Enter the certificate alias used for authentication.
- Keystore File: Enter or Browse... to the keystore file.
- P6 Currency: Enter the base currency for the P6 deployment.
- (Optional) If you choose to synchronize P6 events on the web using the delivered P6 Event provider, enter the following information in the Event Provider step:
- (On-premises only) In the JMS Connection Factory field, enter the local JNDI name from the Connection Factory object created in Configuring Gateway for P6 Event Notification for On-Premises. The connection factory contains a set of configuration parameters to connect with the P6 event provider.
- In the JMS Queue field, enter the local JNDI name of the JMS Queue used to send and receive messages on P6 events from the destination setup created in Configuring Gateway for P6 Event Notification for On-Premises.
- Select Test Connection to ensure connectivity with P6 is established.
- Select Save.
Tips
- You can also edit a deployment and select Save in any step to exit the wizard.