Working with the Repository

Download Error Page

Click the failed icon on the Download page to view the Download Error pop-up page. There are two types of error pop-up pages, one for standard errors and another for invalid password. The invalid password pop-up page only applies to password protected downloads.

This example illustrates the fields and controls on the Download Error page. You can find definitions for the fields and controls later on this page.

The download error message will indicate the error and direct the user to review the download log files. Error could be due to issues occurring during the download, such as network connection disruption (unable to reach MOS) or if there is no space available on the file server to save downloads.

Password Protected Subscription Password Error

When you subscribe to the a password protected download channel, the DownloadAssist file is downloaded from MOS to Cloud Manager. The DownloadAssist file contains the password required to download the packages.

This example illustrates a Download Error page displaying a password error.

This message will only appear if Cloud Manager is unable to retrieve the password due to an error in MOS. If this does occur, the user will need to request the password from Support and update it manually on this page.

If the issue is due to an expired password, user can do a unsubscribe to the channel and then re-subscribe to the channel. Any password changes will be updated in the DownloadAssist file that is posted in MOS. On re-subscribing to a channel, the new password should get automatically updated in Cloud Manager.

If a re-subscribing doesn't solve the problem, then there could be issues in Cloud Manager that is failing to retrieve and update the password automatically or an unforeseen issue in MOS which is not allowing the download of the DownloadAssist file. In such a scenario, the user is expected to get the password from support and update the same on the Download Error page.

Re-synchronizing Repository Data with Downloaded List

Sometimes even after subscribing to a channel, you may not able to see some of the downloaded patches in Repository > My Downloads page. The logs may show that the downloads are being skipped. This indicates a situation where the patches are already downloaded but their metadata is not synced with Cloud Manager. In such situations re-sync the downloaded patches metadata with Cloud Manager using the following steps.

1. Go to Repository > Download Subscriptions page and unsubscribe all channels that are currently subscribed.

2. Navigate to PeopleTools > Process Scheduler > Schedule Process Requests.

3. Enter a Run Control.

4. Run the process "ECL_REPODM".

5. After the process finishes, you should be able to see the missing patches in the Repository > My Downloads page.

Prerequisites

The administrator needs to define My Oracle Support credentials prior to subscribing channels using the Cloud Manager Repository. For this, perform the following:

1. Select the Cloud Manager Settings tile.

2. Edit the value in the User ID field and My Oracle Support password field in the My Oracle Support (MOS) Credentials section.

3. Click Save Settings to save the details. For details on the Cloud Manager settings, see Cloud Manager Settings Page.

Perform the following steps to subscribe to channels using the Cloud Manager Repository tile:

1. Click the Repository home page available on the Cloud Manager home page.

2. Select Download Subscriptions on the left panel. The Download Subscriptions page is displayed.

3. Click Unsubscribed.

4. To subscribe to the release channel, perform the following:

   1. Click the Related Actions button corresponding to the channel name.

   2. Select Subscribe action. If there are any new updates, then the system starts downloading the new updates.

Environment Variables Allowed in Custom Scripts

Custom scripts provide an ability to extend Cloud Manager's provisioning flow. During provisioning orchestration, Cloud Manager provides access to following environment variables inside the custom scripts. The environment variables allowed in custom scripts and their sample values are as follows:

PSFT_APP_APPDOM01_JOLT_LISTENER_PORT=9033

PSFT_INST_PS_CUST_HOME=/u01/app/oracle/product/pt/ps_cust_home

PSFT_ES_PORT=9200

PSFT_INFRA_AVAILDOMAINPRIMARY=evQs:US-ASHBURN-AD-1

PSFT_INFRA_COMPARTMENT_ID=ocid1.compartment.oc1..aaaaaaaaoxxxxxxxxxxxxxxxxxxxxxx7era

PSFT_CONNECT_ID=people

PSFT_APP_APPDOM01_PSPUBHND_DFLT_MAX_INSTANCES=1

PSFT_ULIMIT_CUSTOMIZATION=true

PSFT_PRCS_PRCSDOM01_MSTRSRV=Yes

PSFT_ADMIN_PWD=xxx

PSFT_INST_DB_LOCATION=/u01/app/oracle/product/db

PSFT_APP_APPDOM01_PSPUBHND_DFLT_MIN_INSTANCES=1

PSFT_INST_PS_APP_HOME=/u01/app/oracle/product/pt/ps_app_home

PSFT_INST_PS_CFG_HOME=/u01/app/oracle/product/sample09-fulltierlinux-1/ps_cfg_home

PSFT_ADB_CM_WALLET_LOCATION=xxx

PSFT_CUST_SCRIPT=TestPost.sh

PSFT_PRCS_PRCSDOM01_PSAESRV_MIN_INSTANCES=2

PSFT_WEB_WEBSERVER01_WEBSERVER_HTTP_PORT=8000

PSFT_APP_APPDOM01_JOLT_LISTENER_MAX_INSTANCES=3

PSFT_WEB_WEBSERVER01_AUTH_TOKEN_DOMAIN=.ft.vcnnet.oraclevcn.com

PSFT_APP_APPDOM01_JOLT_LISTENER_MIN_INSTANCES=3

PSFT_INFRA_TENANCY_ID=ocid1.tenancy.oc1..aaaaaaaayy35xxxxxxxxxxxxxxxxxxxxxxxma5a

PSFT_PI_IMAGE=17

PSFT_COBOL_TYPE=VisualCobol

PSFT_PRCS_DOMAINS=['PRCSDOM01']

PSFT_WEBLOGIC_ADMIN_USER=system

PSFT_INFRA_FAULT_DOMAIN=OCI Default

PSFT_PRCS_PRCSDOM01_APPLICATION_ENGINE=1

PSFT_ADB_WALLET_PASSWORD=xxx

PSFT_INFRA_PRIVATE_IP=10.1.10.124

PSFT_PRCS_PRCSDOM01_MAXAPIAWARE=1

PSFT_PSFT_BASE=/u01/app/oracle/product

PSFT_PRCS_PRCSDOM01_COBOL_SQL=1

PSFT_ACCESS_ID=SYSADM

PSFT_WEB_WEBSERVER01_PEOPLESOFT01_APPSERVER_CONNECTIONS=sample09-fulltierlinux-1.ft.vcnnet.oraclevcn.com:9033

PSFT_ES_INSTALL_DIRECTORY=/u01/app/oracle/product

PSFT_GW_ADMIN_USER=administrator

PSFT_SEARCH_PROXY_USER=people

PSFT_OS_USERS={'psft_search_user_name': 'esuser', 'psft_app_install_user_name': 'psadm3', 'remote_login_user': 'opc', 'psft_install_user_name': 'psadm1', 'psft_runtime_user_name': 'psadm2', 'oracle_user_name': 'oracle2'}

PSFT_INST_EYAML_PRIVATE_KEY=/u01/app/oracle/product/sample09-fulltierlinux-1/dpk/puppet/secure/keys/private_key.pkcs7.pem

PSFT_PRCS_PRCSDOM01_PSAESRV_MAX_INSTANCES=2

PSFT_WEBLOGIC_ADMIN_PWD=xxx

PSFT_KERNEL_CUSTOMIZATION=true

PSFT_PRE_PROVISION_CUST_SCRIPT=xxx

USER=root

PSFT_ACCESS_PWD=xxx

PSFT_OPR_ID=VP1

PSFT_INFRA_NSG_IDS=[]

PSFT_CLOUD_INIT_COMMANDS=echo "# testing01 " >> /etc/test.sh;

echo "# testing02 " >> /etc/test.sh;

PSFT_KERNEL_DATA=xxx

PSFT_IS_ADB_BASED_ENV=False

PSFT_SEARCH_ADMIN_USER=esadmin

PSFT_EM_AGENT=xxx

PSFT_INST_TOOLS_CLIENT_HOME=/u01/app/oracle/product/pt/tools_client

PSFT_ULIMIT_DATA=xxx

PSFT_PRCS_PRCSDOM01_PSDSTSRV_MAX_INSTANCES=2

PSFT_INFRA_VCN_ID=ocid1.vcn.oc1.iad.amaaaaaaxxxxxxxxxxxxxxxxxxxxxxxxxxxxxdaq

PSFT_OS_USER_GROUPS={'oracle_runtime_group_name': 'dba', 'oracle_install_group_name': 'oinstall', 'psft_app_install_group_name': 'appinst', 'psft_runtime_group_name': 'psft'}

PSFT_DB_TYPE=DEMO

PSFT_PRCS_PRCSDOM01_APPENG=Yes

PSFT_ES_CLUSTER_NAME=ESCL

SUDO_USER=opc

PSFT_ES_HOSTNAME=xxx

PSFT_INST_PUPPET_BASE_LOCATION=/u01/app/oracle/product/sample09-fulltierlinux-1/dpk/puppet

PSFT_APP_APPDOM01_PSSUBHND_DFLT_MIN_INSTANCES=1

SHLIB_PATH=:/home/opc/cloud/lnx_python/lib

PSFT_INST_DPK_LOCATION=/u01/app/oracle/product/sample09-fulltierlinux-1/dpk

PSFT_APP_APPDOM01_PSQRYSRV_MAX_INSTANCES=1

PSFT_CUSTOMER_DPK_FILE=xxx

PSFT_APP_APPDOM01_PSAPPSRV_MIN_INSTANCES=2

PSFT_CUSTOMIZATION=xxx

PSFT_PI_NUMBER=17

PSFT_WEBPROFILE_USER_PWD=xxx

PSFT_ES_PROXY_PASSWD=xxx

PSFT_APP_APPDOM01_PSBRKHND_DFLT_MIN_INSTANCES=1

PSFT_APP_APPDOM01_WORKSTATION_LISTENER_PORT=7000

PSFT_INST_PUPPET_PROD_LOCATION=/u01/app/oracle/product/sample09-fulltierlinux-1/dpk/puppet/production

PSFT_WEB_WEBSERVER01_WEBSERVER_HTTPS_PORT=8443

PSFT_PRCS_PRCSDOM01_SQR_REPORT=1

PSFT_SEARCH_PROVIDER=xxx

PSFT_DB_IS_ML=xxx

PSFT_PRCS_PRCSDOM01_OPTIMIZATION_ENGINE=1

PSFT_INFRA_PUBLIC_IP=129.80.206.203

PSFT_ELASTIC_SETUP=false

PSFT_INST_PT_LOCATION=/u01/app/oracle/product/pt

PSFT_ELASTIC_SEARCH=N

PSFT_APP_APPDOM01_PSSAMSRV_MIN_INSTANCES=1

PSFT_APP_TYPE=IH

PSFT_CUSTOM_INPUT=xxx

PSFT_INST_LOG_DIR=/home/opc/log/1715748988842831561/psft_activity_custom_post_provisioning_lnx_4_20240515_060212

PSFT_INST_EYAML_KEYS_DIR=/u01/app/oracle/product/sample09-fulltierlinux-1/dpk/puppet/secure/keys

PSFT_PRCS_PRCSDOM01_XML_PUBLISHER=1

PSFT_PIA_DOMAINS=['WEBSERVER01']

PSFT_COBOL_SETUP=false

PSFT_APP_APPDOM01_PSBRKHND_DFLT_MAX_INSTANCES=1

PSFT_INFRA_REGION=us-ashburn-1

PSFT_POST_PROVISION_CUST_SCRIPT=TestPost.sh

PSFT_CONNECT_PWD=xxx

PSFT_HOST_NAME=${envname}-${nodetype}${ostype}-${instno}

SHLVL=4

PYTHONPATH=/home/opc/cloud

PSFT_WEB_WEBSERVER01_SITE_NAMES=peoplesoft01

PSFT_DB_SERVICE_NAME=PSPDB

PSFT_APP_APPDOM01_PSAPPSRV_MAX_INSTANCES=2

PSFT_PRCS_PRCSDOM01_SQR_PROCESS=1

PSFT_APP_APPDOM01_PSSAMSRV_MAX_INSTANCES=1

PSFT_ES_DISCOVERY_HOST_NAME=127.0.0.1

PSFT_INFRA_HOST=sample09-fulltierlinux-1.ft.vcnnet.oraclevcn.com

PSFT_INFRA_HOST_OS=linux

LOGNAME=root

CV_ASSUME_DISTID=OL7

PSFT_APP_APPDOM01_PSSUBHND_DFLT_MAX_INSTANCES=1

PSFT_PRCS_PRCSDOM01_PSDSTSRV_MIN_INSTANCES=2

PATH=/home/opc/cloud/lnx_python/bin:/sbin:/bin:/usr/sbin:/usr/bin

PSFT_DB_NAME=PSPDB

PSFT_INFRA_SUBNET_ID=xxx

PSFT_APP_APPDOM01_PSQRYSRV_MIN_INSTANCES=1

PSFT_GW_ADMIN_USER_PWD=xxx

PSFT_INST_EYAML_PUBLIC_KEY=xxx

PSFT_ENV_TYPE=fulltier

PSFT_COBOL_VERSION=xxx

PSFT_DB_INSTANCE_TYPE=Compute

PSFT_APP_DOMAINS=['APPDOM01']

PSFT_DB_PORT=1522

PSFT_LOGSTASH=N

PSFT_OPR_PWD=xxx

PSFT_KIBANA_PORT=5601

How to Access Environment Variables in or from Custom Scripts

This section shows some examples of using the environment variables.

Example for Python:

crowdstrike_installer=os.environ.get('CS_BIN_PATH')+'/'+os.environ.get('CS_BINARY') 

Example for Shell: 

crowdstrike_installer="${CS_BIN_PATH}/{CS_BINARY}" 

Example for Batch:

set crowdstrike_installer=%CS_BIN_PATH%/%CS_BINARY%

Example for puppet script (Ruby script):

crowdstrike_installer=ENV["CS_BIN_PATH"]+"/"+ENV["CS_BINARY"]

Example for puppet script (puppet script):

$psft_site =  hiera('peoplesoft_site_name')

Sample Batch File

This sample batch file will print the PATH and PSFT_DB_NAME and store it in a file.

set file=C:\temp\script_batch.log

@echo off

@echo Starting the provisioning script > %file%

@echo The value for variable PATH is:  >> %file%

@echo %PATH% >> %file%

@echo The value for variable PSFT_DB_NAME is:  >> %file%

@echo %PSFT_DB_NAME% >> %file%

@echo Ending the provisioning script >> %file%

Sample Python Script

This sample python script will print the PATH and PSFT_DB_NAME and store it in a file.

import os, time

millis = int(round(time.time() * 1000))

file_name = '/tmp/post-provision_python_{}.log'.format(millis)

f = open(file_name, 'w+')

f.write('Starting post-provisioning script')

f.write('The variable PATH value is: {}\n'.format(str(os.environ.get('PATH'))))

f.write('The variable PSFT_DB_NAME value is: {}\n'.format(str(os.environ.get('PSFT_DB_NAME'))))

f.write('Ending post-provisioning script')

f.close()

Sample PowerShell Script

This sample PowerShell script reads and writes the environment variables PSFT_ACCESS_ID and PATH to a file.

$file="C:\script.log"

Add-Content $file "Starting the provisioning script"

Add-Content $file "The value for variable PATH is:"

Add-Content $file (Get-ChildItem Env:PATH).Value

Add-Content $file "The value for variable PSFT_ACCESS_ID is:"

Add-Content $file (Get-ChildItem Env:PSFT_ACCESS_ID).Value

Add-Content $file "Ending the provisioning script"

Sample Shell Script

This sample shell script will print the PATH and PSFT_DB_NAME and store it in a file.

now=$(date +%d%m%Y%H%M%S)
file=/tmp/prov_$now.log

echo "Starting the provisioning script" > $file

echo "The value for variable PATH is: " >> $file

echo $PATH >> $file

echo "The value for variable PSFT_DB_NAME is: " >> $file

echo $PSFT_DB_NAME >> $file

echo "Ending the provisioning script" >> $file

Creating Custom DPK

You must create the custom DPK file by following directory structure and file structure similar to PeopleSoft DPK format. It must be in zip file format (for example, customerDPK.zip).

This example illustrates the custom DPK structure.

During the deployment of custom DPK, Cloud Manager overwrites the existing instance archives, YAML files, and puppet scripts. Since use cases such as clone, restore, add node, PeopleTools Patch, and PeopleTools Update use the existing puppet script present in the environment, you must ensure that the modifications using custom scripts do not interfere with the existing logic.

The Puppet process starts from the site.pp file (current customerDPK.zip/puppet/production/manifests/site.pp) in the custom DPK. Therefore, it is important to update the correct puppet role details in the site.pp file. The following sample script invokes the pt_ws_site puppet role, by using the puppet role script (customerDPK.zip/puppet/production/modules/pt_role/manifests/pt_ws_site.pp) file.

node default {
  include  ::pt_role::pt_ws_site
}

The puppet role script can be used for implementing different puppet profiles in sequence. You can write custom implementations using any combination of the following options:

• Puppet profiles (customeredDPK.zip/puppet/production/modules/pt_profile/manifests/pt_pia_site.pp)

• Puppet custom providers (customerDPK.zip/puppet/production/modules/pt_config/lib/puppet/pt_config/lib/puppet/provider/pt_webserver_pia_site/weblogic_site.rb)

• Custom types (customerDPK.zip/puppet/production/modules/pt_config/lib/puppet/pt_config/lib/puppet/type/pt_webserver_pia_site.rb)

You can pack the binary files and installer.exe in a tgz file in the archive directory (for example: customerDPK.zip/archives/pt-customer-11.0.18.tgz). Puppet custom script can be used for deploying the binaries. Use the Puppet Customizations field to provide new custom values in the psft_customizations.yaml. See Configuring DB Systems Settings.

Cloud Manager usually keeps all the dpk-specific files in a hostname based directory (for example: /u01/app/oracle/product/usernameft07-fulltierlinux-1/dpk). To update any values hiera.yaml file in CustomDPK, use factor global variables (%{::hostname}) for resolving the hostname. This example illustrates a sample hiera.yaml file:

:backends:
  - eyaml
  - yaml
 
:hierarchy:
  - defaults
  - psft_customizations
  - psft_unix_system
  - psft_deployment
  - psft_configuration
  - psft_patches
 
:yaml:
  :datadir: /u01/app/oracle/product/%{::hostname}/dpk/puppet/production/data
 
:eyaml:
  :datadir:   /u01/app/oracle/product/%{::hostname}/dpk/puppet/production/data
  :extension: 'yaml'
 
  :pkcs7_private_key: /u01/app/oracle/product/%{::hostname}/dpk/puppet/secure/keys/private_key.pkcs7.pem
  :pkcs7_public_key:  /u01/app/oracle/product/%{::hostname}/dpk/puppet/secure/keys/public_key.pkcs7.pem

Custom DPK is applied to the environment as part of the final tasks in provisioning use case. If the use case fails, you can retry the failed steps from Environment > Details > Provision Task Status. If a custom DPK file (Custom Puppet Script) is sourced from a Git repository or object storage, the latest file is pulled from the repository during provisioning.