Running the PeopleSoft Update Image (PUM) Container Image

To run the container image:

Extract the image zip file, referred to here as FILENAME.zip, in a convenient directory.
Enter this commands to load a single container image:
```
podman load -i ./image/FILENAME.tgz
```
Use this command to load all three images:
```
find ./image -name "*.tgz" -exec bash -c 'podman load -i "{}" &' \;
```
Use this command to list all images:
```
podman images -a
```
Open ./in/pum/psft_customizations.yaml for editing and add the FQDN for the Linux host computer to this parameter:
```
pia_host_name: "<Host Machine FQDN>"
```

Open ./compose.yaml for editing and specify the following values:

Parameter	Value
ORACLE_PWD	Enter the password for the Oracle database SYS user. Use the same password to update admin_pwd in ./in/pum/install.rsp.
hostname	Enter the mid-tier container hostname. This hostname is critical for PeopleTools domain creation processes. The hostname must not contain underscores (_) and should be distinct from the host machine's FQDN. For example, if your container host computer's FQDN is server.example.one.oraclevcn.com then set the container hostname as midtier.oraclevcn.com. This will set the PeopleTools Auth Token Domain to .oraclevcn.com. The PIA URL will be http://server.example.one.oraclevcn.com:8000.
volume	Remove the comment character (#) in front of /path/to/nfs_share. Update it to /path/to/nfs_share:/out/nfs:rw.
Resource limit	Add CPU and memory resource limits for each container. Leave some resources for host. `deploy: resources: limits: cpus: '4' memory: 16g`
services/midtier/environment	To run on Windows, remove the comment character (#) in front of: `contaner=windows`

If you do not want to run the OSK container at this time, remove the search section from compose.yaml.
View and update the ./in/pum/install.rsp file with the appropriate values for your environment.
The values in the install.rsp response file will be used for the installation.
Enter this command to run the container:
```
podman-compose -f compose.yaml up -d
```
Note:
Remove ./in/pum/install.rsp once the midtier container is up and running.
Check the logs with these commands.
The -f option means follow log output. The -n option outputs container names rather than IDs.
```
podman logs -fn database
podman logs -fn midtier
podman logs -fn osk
```
Enter CTRL+C to exit the log.
The container is up and running when it shows the following message in the container logs:
```
============================
PUM IS READY TO USE!
============================
```
Use these commands to log in as one of the delivered Linux users. For other commands see Working with PeopleSoft Containers.
- Database — podman exec -ti database bash
- Mid-tier — podman exec -ti midtier bash
- Linux psadm1 user — podman exec --user psadm1 -ti midtier bash
- Linux psadm2 user — podman exec --user psadm2 -ti midtier bash
- Linux psadm3 user — podman exec --user psadm3 -ti midtier bash
- OSK — podman exec -ti osk bash
Stop the services using Podman Compose.
```
podman-compose -f compose.yaml down
```