Setting Credentials for Automation
The Update Settings component contains three pages:
Settings
Notifications
Subscription
Automation requires the proper credentials. MOS credentials are necessary to download the PRPs from My Oracle Support (MOS) and must be entered by the customer. The Image and REST services credentials are auto-updated during DPK installation, these credentials can be added or modified as necessary. The REST credentials will be used by the Download Manager to communicate the status of PRPs downloads.
Note that PAU uses OAuth 2.0 for authentication.
Note: PAU needs access to https://updates.oracle.com to download DPKs and PRPs.
Note: When using VirtualBox to install a PUM environment, a proxy configuration is required for the downloads depending on the customer network settings and the VirtualBox network configuration.
Use the Settings page to review and enter credentials.
This example illustrates the fields and controls on the Settings page for MOS Credentials. You can find definitions for the fields and controls later on this page.
These MOS credentials are used to connect to MOS, while downloading PRPs from MOS. When the page is saved, the system will validate connectivity to MOS using the credentials, encrypt the credentials and save to the database.
Field or Control |
Description |
|---|---|
User ID |
Enter the user ID for your My Oracle Support account. |
Password |
Enter the password for your My Oracle Support account. |
This example illustrates the fields and controls on the Image Credentials section. You can find definitions for the fields and controls later on this page.
Initially these credentials are provided from the DPK when the PUM environment is deployed, then through the Automated Configuration Manager (ACM).
These credentials need to be updated if they are changed in the PUM source. All credentials are encrypted before storing in the database.
Field or Control |
Description |
|---|---|
DB User ID |
Database User ID. |
DB Password |
Database password. |
Connect ID |
Connect Id for the database. |
Connect Password |
Connect ID password. |
Access ID |
Access Id for the database. |
Access Password |
Access ID password |
DB Admin ID |
Database Administrator ID. |
DB Admin Password |
Database Administrator ID password. |
This example illustrates the fields and controls on the REST Service Credentials. You can find definitions for the fields and controls later on this page.
Initially these credentials are provided from the DPK when the PUM environment is deployed, then through the Automated Configuration Manager (ACM).
These credentials need to be updated if the REST Service credentials are changed in the PUM source.
REST Services are used by the Download Manager that downloads PRPs to communicate status of downloads. The user ID must have permission list PTPT4300.
This example illustrates the fields and controls on the PUM Source Settings. You can find definitions for the fields and controls later on this page.
Use the PUM Source Settings to enable the upload of customization projects and enable object merge.
|
Field or Control |
Description |
|---|---|
|
Enable Customization |
Enables the upload of customizations to the PUM Source. Note that you can set up customization repository from Change Assistant as well. |
|
Enable Merge |
Enables object merge for PeopleCode, SQL and XSLT objects in your Customization Repository. When object merge is enabled in the PUM source, the upload Customization fetches the object merge data in the Customization project (Peoplecode, SQL and XSLT) and schedules version update Application Engine to set the appropriate object version to the mergable objects uploaded. Note that you can enable object merge from Change Assistant as well. |
|
Enable test |
Enables the upload to test repository. |
|
Mergeable Objects |
Shows a list of mergeable objects. |
Use the Notifications page to set up preferences for notifications.
This example illustrates the fields and controls on the Navigations page. You can find definitions for the fields and controls later on this page.
Field or Control |
Description |
|---|---|
Distribution ID Type |
Select User or Role. |
Distribution ID |
Enter the User ID or role name. |
On Initiation |
Select Yes to be notified when an automated update job is initiated. |
On Success |
Select Yes to be notified when an automated update job runs to success. |
On Failure |
Select Yes to be notified when an automated update job fails. |
Email Notification |
Select to send email notifications. Note: For details, see Email Details |
If Email Notification is selected, enter the SMTP details:
This example illustrates the fields and controls on the Email details section. You can find definitions for the fields and controls later on this page.
Field or Control |
Description |
|---|---|
Server Name |
Enter the SMTP mail server from which you receive the error or completion messages. |
Port Number |
Enter the port from which you want to access the email. |
Connection Security |
Select the connection security. SSL/TLS type connection |
User Name |
Enter the user name to log in to the SMTP server. |
Password |
Enter password for SMTP user name. |
Email To |
Enter the email address. |
Email CC |
Enter the email address. |
On Initiation |
Select Yes to send an email when an automated update job is initiated. |
On Success |
Select Yes to send an email when an automated update job runs to success. |
ON Failure |
Select Yes to send an email when an automated update job fails. |
Email Details
The email notification for tasks, such as, Download PRPs from MOS or Apply PRPs to PUM Source, contains all relevant details.
|
Task |
Details |
|---|---|
|
Download PRPs from MOS or Apply PRP to PUM Source |
Displays the:
When user runs Download and Apply PRP in one PAU job, it sends two emails with list of PRPs downloaded and PRPs applied. |
|
Define Change Package/ Create Package |
Displays the:
|
|
Apply Change Package |
Displays the success or failure status and link to the Job Monitor page. |
This example illustrates the fields and controls on the PRP Details page.
The subscriptions page displays the default channel information corresponding to the deployed PeopleSoft Image.
This example illustrates the fields and controls on the Subscriptions page.
