Set up the Assistant

Setting up the Assistant touches four systems: your identity provider, PeopleSoft, a server for the Assistant service, and your LLM provider. These pages take you through them in order, and end with a user asking the Assistant a question and getting an answer from live PeopleSoft data.

Steps

1. Connect sign-in. Register the chat page, the Assistant service, and PeopleSoft with your identity provider, and set PeopleSoft up to accept its tokens.

2. Build the first application service, which returns the signed-in user’s absence balances.

3. Run the Assistant service in a container behind nginx, with its tool catalog.

4. Add the chat page to PeopleSoft, with a tile on homepages and the NavBar.

5. Test and go live, starting with a pilot group.

Who does what

Step	Done by
Connect sign-in	Your identity provider’s administrator, with a PeopleSoft security administrator
Build the first application service	A PeopleSoft developer
Run the Assistant service	Your operations team
Add the chat page	A PeopleSoft developer, with a portal administrator for the tile
Test and go live	The project team, with test users in each role

What you need

• PeopleTools 8.59 or later, with access to Application Designer, and your usual way of migrating definitions to production.
• An identity provider that PeopleSoft trusts for OAuth 2.0 access tokens, and that supports token exchange. If PeopleSoft already uses it for single sign-on, users won’t have to sign in again to use the Assistant.
• An LLM API that supports tool calling and streaming, with credentials for the service.
• A Linux server with Podman, close to PeopleSoft, with a DNS name and a TLS certificate for the service.
• Network access from browsers to the service over HTTPS, and from the service to the PeopleSoft web server, your identity provider, and the LLM API.

Names these pages use

Name	What it is
hr.example.com	The PeopleSoft web server
assistant.example.com	The Assistant service
login.example.com	The identity provider
api://aipeoplesoft-assistant	The Assistant service’s identifier in the provider
api://peoplesoft-hr	PeopleSoft’s identifier in the provider
ZZ_ASSISTANT_HR	The first application service
ZZ_AI_ASSISTANT	The chat page’s Fluid component
aipeoplesoft-assistant:1.0	The Assistant service’s container image

Replace them with your own as you go.

Start in a development environment

Set everything up against a development PeopleSoft database first, with test users in each role, and a separate registration in your identity provider. Move to production once the go-live tests pass.