Setting Up Campus Mobile Within Campus Solutions

Campus Mobile is a smartphone app that uses delivered Campus Solutions web services to provide data directly to the user's phone that will then be rendered by the Campus Mobile screens. To enable the web services that Campus Mobile requires, you will need to configure Integration Broker as well as the appropriate security for your web services. To enable building mapping (a feature accessed in Campus Mobile through the Class Section Details), you will need to populate the latitude and longitude for each building.

We assume that you have performed and validated all the basic Integration Broker setup. Refer to the Integration Broker for information on Integration Broker gateway setup and service configuration.

See PeopleTools PeopleSoft Integration Broker Administration, “Configuring PeopleSoft Integration Broker for Handling Services”

Service operations for the Campus Mobile are delivered with a status of Inactive to prevent the accidental transmission of data. In order to make use of these key elements of the Campus Mobile at the time of implementation, you need to set each of them to a status of Active.

To activate service operations:

1. Log into the PeopleSoft application in a browser.

2. Select select PeopleTools, then select Integration Broker, then select Integration Setup, then select Service Operations.

3. Select each of the service operations from the Campus Mobile Service Operations tables.

4. On the General page, select the Active check box in the Default Service Operation Version group.

5. Select the Handlers page and select the Active option from the drop-down list for the Status column.

6. Save the page.

7. Select the Routings tab, select the check box against the routing name, and click the Activate Selected Routings button.

Some service operations do not have routings generated by default so you will need to generate routings for them separately.

Follow these steps to generate routings for the User Registration Service:

1. Log into the PeopleSoft application in a browser.

2. Select select PeopleTools, then select Integration Broker, then select Integration Setup, then select Service Operations.

3. Search for SCC_USERREG_AUTHENTICATE Service Operation.

4. On the General page, select the Generate Any-to-Local check box.

5. Save the page.

Follow these steps to generate routings for the Enrollment Sync Service:

1. Log into the PeopleSoft application in a browser.

2. Select select PeopleTools, then select Integration Broker, then select Integration Setup, then select Service Operations.

3. Search for SSR_ENROLLMENT_SYNC Service Operation.

4. On the General page, select the Generate Local-to-Local check box.

5. Save the page.

Follow the same steps to Generate Any-to-Local routings for the following service operations:

• SCC_GET_CHECKLIST_R_POST

• SCC_GET_SERVICE_INDICATORS_R_G

• SFA_GET_STUDENT_AWARDS_R_POST

• SSF_GET_STUDENT_ACCOUNT_R_POST.

By default, only error messages appear on the Integration Broker Synchronous Service Monitor screen. During testing, it may be helpful to increase the logging detail of the web service messages in order to detect all messaging activity through the Integration Broker Synchronous Service Monitor screen. Increasing the log detail to “Header and Detail” will enable synchronous message header information and XML message content to appear in the Service Operations Monitor.

The following steps enable logging in greater detail of the web service messages for Campus Mobile:

1. Navigate to select PeopleTools, then select Integration Broker, then select Integration Setup, then select Service Operations.

2. Enter each of the service operation names from the list of service operations used in Campus Mobile, such as SSR_ADD_ENROLLMENT_R_POST.

3. Click Search.

4. Select the Routings tab.

5. On the Routing Definitions page, change Log Detail from No Logging to Header and Detail.

For more information, access the Configuring Routing Definitions page (select PeopleTools, then select PeopleSoft Integration Broker, then select Managing Service Operation Routing Definitions, then select Configuring Routing Definitions).

Users log into Campus Mobile using the same credentials that they use for Campus Self Service access through PIA. These credentials pass to PeopleTools using the Authentication and Authorization web services (Service operations SCC_USERREG_AUTH_GET and SCC_USERREG_AUTHORIZE_POST in the Campus Mobile Service Operations chart above).

The delivered authorization model is different for V3.1 (and earlier versions) and V4 as outlined below.

Campus Mobile V3.1 and earlier:

For Campus Mobile V3.1 and earlier, the permission list HCCPCSSA3000 determines whether a user is authorized to access the Campus Mobile features. The security role, CS Mobile Student, is delivered by default with the HCCPCSSA3000 permission list added to it. You have the flexibility to deploy security for Campus Mobile in the way that fits your institution’s requirements. Your options include:

• Assign the delivered CS Mobile Student role to students who need access to Campus Mobile.

• Assign the delivered HCCPCSSA3000 PL to a role that is (already) assigned to students who need access to Campus Mobile.

• Customize the Campus Mobile application to use a different permission list as described in the Campus Mobile Implementation Guide.

Campus Mobile V4:

Beginning with V4 of Campus Mobile, a more granular security model is delivered. Each Campus Mobile feature is assigned its own permission list that is checked to determine whether a user is authorized for access to that feature. With this security model, access to features can be readily controlled with security configuration. For example, with the delivered security roles, students that do not participate in Financial Aid can simply not have the CS Mobile Financial Aid role added to their user profile. Then they will not see the Financial Aid feature on their springboard.

The following table contains the delivered roles and permission lists. You may use these as delivered or deploy security in the way that meets your institution’s requirements. The Campus Mobile application can be configured to use different permission lists if needed, see the Campus Mobile Implementation Guide, section 3.3.2.3.

Campus Mobile makes extensive use of the LOV web services throughout the features of Campus Mobile. In order to limit the data that can be queried using the LOV service operations, there are delivered LOV configurations to enable web service access to the specific LOV data used in Campus Mobile. In the LOV setup all of the following use the ‘DEFAULT’ context except for the ‘SSC_SUBJECT_CLS’ noted with the (*) which uses the ‘CM’ context. This configuration is delivered as is provided here for informational purposes.

See Setting Up List of Values

In addition to feature-level access in Campus Mobile, users must be granted access to the web service operations that provide the data and business logic between Campus Mobile and Campus Solutions itself. A permission list must be defined that includes all of the necessary service operations to be deployed to users. That permission list must then be attached to a role assigned to Campus Mobile student users.

PeopleTools provides granular-level control to allow you to define relationships between permission lists and roles that best fit your institutional policies. You may want to encapsulate both feature-level access (see above) and web service-level access within a single permission list (such as HCCPCSSA3000), or you may want to define feature and web service access independently and pull them together within a single role. As long as users have access to both the Campus Mobile features and required service operations, Campus Mobile transactions will be available to them.

Follow these steps to add the permission list to each service operation listed in the Campus Mobile Service Operations table above:

1. Navigate to select PeopleTools, then select Integration Broker, then select Integration Setup, then select Service Operations Page.

2. Search each Service Operation Name listed in the Campus Mobile Service Operations tables.

3. On the General Tab, click the Service Operation Security link.

4. The Web Service Access page opens in a new window. On this page, select the appropriate permission list that you want to attach to this service operation.

5. Select Full Access from the Access drop-down list.

6. Click Save.

Access the Instructor Contact Information page (select Set Up SACR, then select Product Related, then select Campus Mobile, then select Instructor Contact Setup).

Image: Instructor Contact Setup page

This example illustrates the fields and controls on the Instructor Contact Setup page. You can find definitions for the fields and controls later on this page.

Campus Mobile includes the ability for a student to view information on instructors assigned to a class either in their Class Schedule or through Class Search. Details can include the contact information (address, phone number, email address, and photo) for instructors, if institutions have chosen to share those details.

See PeopleTools: Security Administration

The service operations that deliver the financial information are dependent on settings on the General Options page (select Set Up SACR, then select Common Definitions, then select Self Service, then select Student Financials, then select SF Institution Set). For your Institution Set, ensure that the Allow Use in Service check box is selected and you have entered a value in the Maximum Payments in Service field.

There are several areas of configuration needed to enable contributions along with the service operations described here. In the Campus Mobile Contributions feature, each institution that is configured for Involvement has a dynamic message associated with it that appears on the Contributions page. This message is set on the Involvement Setup page (select Set Up SACR, then select Common Definitions, then select Self Service, then select Involvement, then select Involvement). You can change the Message field and it will dynamically update in Campus Mobile. For more information about involvement setup, see Setting Up Self-Service Online Giving and Pledges.

In the Contributions feature, Make a Gift allows for direct integration with payment providers for credit card gifts. For this integration to work, you must configure the Hosted Payment Framework; see the ePayment Developer's Guide for instructions. Once the Hosted Payment merchant setup is complete, select the Hosted Payment to use with Contributions on the Business Unit CR component (select Set Up SACR, then select Product Related, then select Contributor Relations, then select Install Contributor Relations, then select Business Unit CR). For more information on CR business unit setup, see Defining and Securing PeopleSoft Contributor Relations Business Units and SetIDs.

Further, there is a required servlet that provides the integration between the Campus Mobile app and the third-party payment provider through the Hosted Payment Framework. See the Campus Mobile Implementation Guide posted to My Oracle Support, for instructions on configuring the servlet.

The service operations that deliver the Applications information are dependent on display settings for Application Status, Checklist Item Due Dates and Checklist Contacts.

See Setting Up Application Status and Checklist Options

For more information on customizing the features of Campus Mobile, please see the Campus Mobile Implementation Guide posted to My Oracle Support. There you will find details around branding the application with your institution's logo and colors as well as icons and labels. Further, you will find information on the potential for customizing or extending the Campus Mobile application.

Campus Mobile can be deployed to both Android (.apk) and iOS (.ipa) devices. Campus Mobile is built on the Oracle ADF Mobile framework. You will open the Campus Mobile application archive in Oracle Jdeveloper, apply your branding, sign the application for your Institution and deploy it to Apple and Android application files to be distributed to your students. The Campus Mobile Implementation Guide contains details on deploying and distributing the Campus Mobile Application.

See Campus Mobile Implementation Guide, posted to My Oracle Support.