To run Database Configuration after installation with a Cloud Connect database driver, complete the following steps:
- On the login screen, click Edit database configuration.
- On the Database Configuration wizard, select an alias from the list, or click Add to create a new alias. If you crete a new alias, enter a name in the Database Alias field.
- In the Driver Type list, select P6 Professional Cloud Connect.
Note: Select P6 Professional Cloud Connect only if you installed P6 Professional Cloud Connect in P6 EPPM to set up a remote method of access to connect to the EPPM Oracle database and the P6 APIs. P6 Professional Cloud Connect is not supported with SQL Server.
- In the Connection String field, enter the connection string to your database in the format
<database name>@http://<host name>:<port number>/p6cloudconnect.For example,
p6cloud@/http://p6server.nesbidcorp.com:1234/p6cloudconnectNote: Contact your P6 EPPM administrator to obtain the URL for P6 Professional Cloud Connect.
- In the Read Timeout field, enter the number of seconds to wait for a response to a query sent to the Cloud Connect database. Oracle recommends a value of 900.
- If P6 Professional Cloud Connect service uses SAML, select the Use SAML SSO option.
- If your organization allows the use of a local cache database, to improve performance with the P6 Professional Cloud Connect service, select the Enable Client-side Cache option.
- Click Test to test the database connection. If the connection is successful, click Save. If the connection is not successful, revise the database connection information you provided.
Tips
- The PrmBootStrapV2.xml file is used regardless of the driver type.
- If you create a new database alias for a module, the PrmBootStrapV2.xml file is updated to reflect the change. If multiple modules are installed on one client computer, changing the database alias for one module does not affect the other modules.
- If you change the database connection settings for a database alias and multiple modules share that alias to access the database, your changes affect all the modules that share the alias.