How to setup connector for P6

Modified on Fri, 22 Aug at 3:05 PM

TABLE OF CONTENTS

Introduction

This article will guide you through creating a connector for P6 and show you how to use different authentication methods.

Before setting up the connector, make sure you have the following:

Note: Each connector must have a unique combination of URL (to WebService/REST API).

These inputs are required

This option is used for SSO-enabled (Single SignOn) setups.
NO OTHER FIELDS NEED TO BE FILLED OUT HERE!

There are some additional settings you can do for P6 and they are shown with the red numbers and described below:

1	Use encryption	This setting is default unchecked, the setting should reflect what’s configured on the P6 server. Refer to your tenant admin for this setting.
2	Activity Retrieval Batch Size	Optional. Number of activities to retrieve per batch. The information icon gives this guideline: If your schedule has more than 50k activities, we highly recommend specifying a batch size. Use batch size like 10000.
3	Activity Write Batch Size	Number of activities to create/modify per batch. The default recommended setting is 500.
4	Include project level activity codes	Control if you need to retrieve Project specific Activity Codes. Default is false for a good reason: As each project will be allowed to have their own userfields (instead of the global set), turning this on will restrict reusability of configs from all schedules to one per schedule! If this is turned on the codeset id column will have values and if turned off then it would be blank.
5	Manage Custom Request Headers	This allows custom headers to be configured by adding Key-Value pairs in case this should be needed. The list of Key-Value pairs is edited when pressing the button. NOTE: Currently only Safran had a use case for this feature.

See red number (1) in previous screenshot.

If the executing component is "Desktop" then you will see this form:

Otherwise, you will see this form:

After creating the connector:

For Desktop Client execution:
- Open the IDE Desktop Client
- Navigate to the Connectors tab
- Click Test to verify connection
- Click Persist to fetch schedules and host fields from P6
For Autonomous Component execution:
- Test is done periodically via a background job, but it can be also done using desktop client.
- Alternatively: Go to Setup > Connectors in the web app, and open the newly created connector and click Persist to force retrieval of schedules and host fields from P6. After persisting, reload the page after a few minutes to verify the updated connector status.

Checkout this article to find out more about test & persist