Where to Begin
Step 1: Decide on a server to host P6 EPPM Web Services
You will need to choose and configure an Application/Web Server and then deploy P6 EPPM Web Services into the Application Server. For information about which Application/Web Server P6 EPPM Web Services supports, refer to the P6 EPPM Web Services Administration Guide.
Step 2: Decide on an authentication method
The next step is to determine how client service requestors should establish and authenticate their credentials with the server. P6 EPPM Web Services supports three choices:
- Authentication using UsernameToken Profile
- Authentication using SAML
- Authentication using HTTP Cookies (on-premises only)
See the P6 EPPM Web Services Configuration Guide for your server for more information about how to configure the Application/Web Server.
Step 3: Decide on a client technology
The next step is to decide on the client technology that you will be using with P6 EPPM Web Services from the many client technologies that are available that can utilize P6 EPPM Web Services interfaces. BPM, BPEL, and .NET are examples of technologies that can utilize P6 EPPM Web Services interfaces.
P6 EPPM Web Services has been tested with Java client technologies.
Step 4: Use P6 EPPM Web Services to interact with P6 EPPM
Depending on the decision you made on step 2, use either of the following steps to use P6 EPPM Web Services:
If your server is configured to use a UsernameToken for authentication, follow these steps:
- Write client code to send and receive P6 EPPM Web Services messages, supplying valid authentication information based upon the authentication method you chose in step two.
- Call P6 EPPM Web Services operations as required by your program.