...
...
Meet with your campus PeopleSoft group
Libraries should meet with their campus PeopleSoft contacts to go over the various configuration options in the app engine.
User Identifiers
Every campus Student Information System (SIS) and HR System (for employee data) is set-up slightly differently in PeopleSoft. Although there is a great deal of standardization, especially around basic contact information (EmplID, name, email, address, etc.), some pieces of data, such as campus username and barcode, are not standardized across the CSU.
...
Note that this will not be necessary for most libraries. Campus username is not necessary for authentication for the vast majority of libraries, and at most campuses the PeopleSoft EmplID is the campus barcode number, and is already included in the basic export.
Testing with Alma
All campus Alma instances have been configured to pick-up the patron load file from your campus' PeolpeSoft dev/test FTP server location. Once your PeopleSoft group has configured the app engine on their dev/test PeopleSoft instance and produced a test file, you can go into Alma and run an import test.
...
Here’s the difference between the two: "The import mode is a one-time load, used to initially create new external users. It is intended to be used only when you have a file of users you know are new, such as during the migration process, when you want to load users from your legacy system into Alma. The synchronize mode is an ongoing load, used to update external users and add new ones."
Switching to production
On the PeopleSoft side, your PS group should know the steps for actually putting the app engine into production.
...
Change the last part of the 'UserName' from:
******dv
to:
******pd
...
That should be it. The public key and everything else should be the same.
Scheduling
The first time you run an import from production, you will be doing a full import of all users – just as most of you did during testing. After that, you'll want to set up a schedule for fully automated imports.
...