Integration with Other Campus Solutions Components
AAWS interacts with the following Campus Solutions components:
User Account Manager
Constituent Transaction Manager
Admissions API
Student Financials Hosted Payment
This section discusses the application packages and classes for these components. If you want to customize AAWS, you may need to modify some of these classes and packages. For instance, if you want to integrate a non PeopleSoft user management system with AAWS, a new application class should be created that implements SCC_IDENTITY_MGR:INTFC:IIdentityManager. The application class must then be added to the table SCC_IDM_INST.
Image: AAWS Architecture
This diagram illustrates that AAWS architecture is composed of SOA UI, web services for user registration, authentication and admission applications, and the User Account Manager, Constituent Transaction Manager and Admissions API interfaces.
The user registration and authentication web service operations interact with User Account Manager to register and authenticate the end user. PeopleTools User Profile, by default, stores the user account information.
The User Account Manager component contains a number of sub-modules including the Campus Identity Manager and the User Manager. The following graphics show the core application packages and classes which support the User Account Manager:
Image: Campus Identity Manager
This image illustrates the Campus Identity Manager.
|
Class |
Description |
|---|---|
|
CampusIdentityManager |
Manages all aspects of Self Service Transactions interactions with any configured Identity management system or New User Registration module. Call getInstance() on this class to get access to a concrete IDM implementation. |
|
HANDLERS:UserRegistration |
Implements the User Registration Web Service, the register & authenticate operation. |
|
INTFC:IIdentityManager |
Represents the functionality available through any typical generic Identity Manager product. All access to IDM functions will occur through this interface whether from code level API calls or webservices. |
|
SAMPLE:PeopleSoftIDMImpl |
The peoplesoft default implementation of IIdentityManager. Performs all Identity Management tasks against the peoplesoft db. |
|
UTIL:IdentityException |
All exceptions generated from within the IdentityManager interface should extend this class. |
|
UTIL:ResultSet |
Represents a tabular data object that is the basis for many of the Identity Manager operations. |
Image: User Profile Manager
This image illustrates the User Profile Manager.
|
Class |
Description |
|---|---|
|
UserManager |
Main API for user manager. |
|
UserProfile |
A data object to store user profile information. |
|
TRANSACTION:UserRegTransaction |
This handles the posting activities for User Registration sourced data as directed by the Constituent Staging framework. Note: This is not the implementation currently used. |
|
UTIL:MessageHandler |
Handles any messages, warnings, errors generated during User Management. |
|
UTIL:UserManagementException |
All exceptions generated from within the UserManager interface should extend this class. |
Constituent Transaction Manager handles the admission application and applicant data that AAWS receives and sends to the user interface. When the user interface submits the application and applicant data, AAWS transmits this data to the Constituent Transaction Manager. The Constituent Transaction Manager stores this data in Campus Solutions staging tables.
Constituent Transaction Manager is composed of a number of application classes and PeopleTools components which support the staging and loading of constituent (applicant) and related transaction (application) data into staging tables.
The following graphics show the application packages and classes in the Constituent Transaction Manager component:
Image: Constituent Transaction Manager (1 of 4)
This image illustrates the Constituent Transaction Manager (1 of 4).
Image: Constituent Transaction Manager (2 of 4)
This image illustrates the Constituent Transaction Manager (2 of 4).
Image: Constituent Transaction Manager (3 of 4)
This image illustrates the Constituent Transaction Manager (3 of 4).
Image: Constituent Transaction Manager (4 of 4)
This image illustrates the Constituent Transaction Manager (4 of 4).
The Admissions Applications Programming Interface (API) moves the application data from the staging tables to the core Recruiting and Admissions tables.
The API supports the creation, modification, and submission of online admission applications. The API is an Object Oriented (OO) based application class hierarchy that represents the admission applications. The class hierarchy contains an Application Manager API that performs key functions with application data. The API also supports the calculation of Application Fees via integration to the Application Fee hosted payment processing.
The following graphics show the application packages and classes in the Admission Applications Manager component:
Image: Admission Applications Manager (1 of 3)
This image illustrates the Admission Applications Manager (1 of 3).
Image: Admission Applications Manager (2 of 3)
This image illustrates the Admission Applications Manager (2 of 3).
Image: Admission Applications Manager (3 of 3)
This image illustrates the Admission Applications Manager (3 of 3).
The Entity Registry feature enables academic institutions to create their own application data extensions (that is, you can add entirely new application child entities).