SOLA Setup and Verification

This section discusses the required setup and the verification to ensure that SOLA is configured properly.

Procedure:

  1. Access the URL Maintenance component (PeopleTools > Utilities > Administration > URLs).

  2. Enter SAD_APPL_ATCH in the Search by field:

    This is an example of searching for SAD_APPL_ATCH in the URL Maintenance component.

    Searching for SAD_APPL_ATCH
  3. Click the Search button.

  4. Verify whether a URL value (either a File Server or Database) has been supplied.

Procedure:

  1. Access the Roles component (PeopleTools > Security > Permissions & Roles > Roles).

  2. For New User Registration, see Campus Community’s New User Registration Framework documentation for setup instructions on how to add role name CS - NUR GateKeeper.

  3. For SOLA, complete the following steps:

    1. Add role name as Online Application Demo:

      This is an example of adding a role for SOLA in the Roles component.

      Adding a role for SOLA (Sample Online Application)
    2. Click the Add button.

    3. Add the description as Online Application Demo:

      This is an example of adding a description for the SOLA role on the General page.

      Adding description for the SOLA (Sample Online Application) role
    4. Add the permission list HCCPCSSA1190:

      This is an example of adding a permission list for the SOLA role on the Permission Lists page.

      Adding a permission list for the SOLA (Sample Online Application) role

Procedure:

  1. Access the User Profiles component (PeopleTools > Security > User Profiles).

  2. Add SCC_GUEST.

    This is example of adding the guest account in the User Profiles component.

    Adding the guest account
  3. On the General page, enter values as shown in the following graphic:

    Note: For password, choose a password of your choice.

    This example illustrates the values entered on the General page.

    General page
  4. On the ID page, enter values as shown in this graphic:

    This example illustrates the values entered on the ID page.

    ID page
  5. On the Roles page, enter values as shown in this graphic:

    This example illustrates the values entered on the Roles page.

    Roles page
  6. Save your changes.

Verify that minimal IB setup and service configuration is performed.

Verifying IB Gateway

Procedure:

  1. Access the Gateways component (PeopleTools > Integration Broker > Configuration > Gateways).

  2. Select that Integration Gateway ID for which the Local Gateway is set to Y.

  3. Verify that the URL is pointing to the correct gateway.

  4. Ensure that the gateway can be pinged by clicking the Ping Gateway button.

    You should see this page if the gateway is pinged successfully.

    PeopleSoft Integration Gateway page

Verifying IB Nodes

Procedure:

  1. Access the Nodes component (PeopleTools > Integration Broker > Integration Setup > Nodes).

  2. Click the Search button and scroll through the search results list looking for the Node Name where the Default Local Node is Y. There should be only one default local node.

  3. On the Connectors page, click the Ping Node button.

  4. Verify that the Gateway ID is pointing to the local gateway that you previously just pinged. If it is not, change the Gateway ID so that it is.

  5. When you click the Ping Node button, you should see Success in the message text.

Verifying that the Domain Status is Active

Procedure:

  1. Access the Domain Status page (PeopleTools > Integration Broker > Service Operations Monitor > Administration > Domain Status).

  2. Verify that the domain status is Active.

Verifying Service Configuration

Procedure:

  1. Access the Service Configuration page (PeopleTools > Integration Broker > Configuration > Service Configuration).

  2. Verify that a service configuration exists.

Note

Do not continue if any of the verification steps mentioned in this section “Step 4: Set Up Integration Broker (IB)” fail. Resolve the failed steps before continuing.

Procedure:

  1. Access the Services page (PeopleTools > Integration Broker > Integration Setup > Services).

  2. Generate Any to Local and Local to Local routings for the following six web service operations of the SAD_ADMISSIONS web service:

    • SAD_CREATEAPPL.v1

    • SAD_GETAPPL.v1

    • SAD_GETAPPLS.v1

    • SAD_GETATTACH.v1

    • SAD_SAVEAPPL.v1

    • SAD_SUBMITAPPL.v1

      This example illustrates the six service operations of SAD_ADMISSIONS service.

      The six service operations of SAD_ADMISSIONS service

To generate these routings and verify that the operation status is Active:

  1. For each operation, on the General page select both the Generate Any to Local check box and the Generate Local to Local check box.

  2. Make sure that the service operation is Active. If the status is not active, select the Active check box.

  3. Save your changes. When you save, the system updates the routing status to Exists for both routing actions:

    This example illustrates the fields and controls on the General page after save (1 of 2).

    General page after save (1 of 2)

    This example illustrates the fields and controls on the General page after save (2 of 2).

    General page after save (2 of 2)
  4. Click the Return to Service link.

  5. Repeat the steps 1 through 4 for the remaining operations.

For new user registration also you must perform the same steps:

  1. Access the Services page (PeopleTools > Integration Broker > Integration Setup > Services).

  2. Generate Any to Local and Local to Local routings for the following two web service operations of the SCC_USERREG web service:

    • SCC_USERREG_AUTHENTICATE.v1

    • SCC_USERREG_CREATEACCT.v1

      This example illustrates the two service operations of SCC_USERREG service.

      The two service operations of SCC_USERREG service
  3. Repeat the preceding steps for generating routings and ensuring that the status is Active.

Procedure:

  1. Access the Nodes component (PeopleTools > Integration Broker > Integration Setup > Nodes).

  2. Search for the ANONYMOUS node name.

  3. On the Node Definitions page, change the Default User ID to SCC_GUEST.

    This example illustrates the fields and controls on the Node Definitions page.

    Node Definitions page
  4. On the WS Security page, change the Authentication Token Type to Username Token.

    This example illustrates the fields and controls on the WS Security page.

    WS (Web Services) Security page
  5. Save your changes.

Procedure:

  1. Access the Provide Web Service Wizard (PeopleTools > Integration Broker > Web services > Provide Web Service).

  2. Ensure all the operations for the SAD_ADMISSIONS and SCC_USERREG web services are published.

    Search for SAD_ADMISSIONS service name:

    This example illustrates the fields and controls on the Select Services page.

    Select Services page
  3. Click the Select All button and click the Next button.

  4. On the Select Service Operations page, click the Select All button and click the Next button.

    This example illustrates the fields and controls on the Select Service Operations page.

    Select Service Operations page
  5. On the View WSDL page, click the Next button.

    This example illustrates the fields and controls on the View WSDL page.

    View WSDL (Web Service Definition Language) page
  6. On the Specify Publishing Options page, click the Finish button.

    This example illustrates the fields and controls on the Specify Publishing Options page.

    Specify Publishing Options page
  7. Repeat the steps for the SCC_USERREG web service.

Procedure:

  1. Access the HCM Interface Registry page (Set Up Common Objects > System Administration > HCM Registry > Service Registry).

    This example illustrates the fields and controls on the HCM Interface Registry page.

    HCM (Human Capital Management) Interface Registry page
  2. Click the Refresh Cache button.

    Note: The message Processing displays and remains on the page. There is no other message displayed.

Procedure:

  1. Access the New User Registration Context component (Set Up SACR > System Administration > Utilities > New User Registration > New User Registration Context).

  2. Click the Add a New Value tab.

  3. Add the DEFAULT_CONTEXT New User Registration Context as shown in this graphic:

    This is an example of the New User Registration Context for SOLA.

    New User Registration Context for SOLA (Sample Online Application)
  4. Select the Default check box.

  5. In the Node Name field, you must select a node marked as Default Local Node = Y.

  6. Save your changes.

Procedure:

  1. Sign into Campus Solutions using your institution's master user ID and password.

    This is an example of signing into CS.

    Signing into Campus Solutions
  2. Access the New User Registration Tester page (Set Up SACR > System Administration > Utilities > Sample User Interfaces > New User Registration Tester).

    This is an example of the New User Registration Tester page with sign-in fields.

    New User Registration Tester page with sign-in fields
  3. Select the Need a User ID? Yes/No check box.

  4. Fill out the New User Registration Tester page as shown in this figure:

    This is an example of the New User Registration Tester page with the filled out user registration fields.

    New User Registration Tester page with the filled out user registration fields

    Note: For the password field, choose a password of our own.

  5. Click the Create User button. On clicking this button, the system transfers you to Sample Online Application home page:

    This example illustrates the fields and controls on the blank Application Home page.

    Blank Online Application Home page
  6. Fill out the Create A New Application section. Select values for:

    • Institution.

    • Academic Career.  

    • Admit Term.

    • Academic Program.

    • Academic Plan.

    • Admit Type.

      This is an example of the Home page with the values for creating a new application.

      Home page with the values for creating a new application
  7. Click the Create Application button.

  8. Change the value for the Gender field to Female.

  9. Save your changes. When you save, a message should be displayed indicating that the application was successfully saved:

    This is an example of the message indicating that application has been saved.

    Message indicating that application has been saved
  10. Click OK and sign out.

  11. Sign back in using the newly created ID (that is, JSmith):

    This is an example of signing into CS using the ID created through New User Registration tester page.

    Signing into Campus Solutions using the ID created through New User Registration tester page
  12. Access the Sample Online Application component (Set Up SACR > System Administration > Utilities > Sample User Interfaces > Sample Online Application).

    This is an example of the Home page with the saved application.

    Home page with the saved application
  13. Click the Edit button.

  14. You should be able to see the application you started and the previously saved Gender change.

    This is an example of the Basic Information page with the saved value.

    Basic Information page with the saved value
  15. If you have made it this far, then the database is configured correctly for AAWS, SOLA, and New User Registration. If not, then verify that the preceding setup steps have been performed correctly.