How to Deploy PeopleSoft Cloud Manager 17 on OCI for Environment Cloning [ka83]

Unlocking Agility: PeopleSoft Cloud Manager 17 Deployment on OCI for Environment Cloning

As enterprises increasingly migrate their critical applications to the cloud, the need for robust, automated, and scalable management tools becomes paramount. Oracle's PeopleSoft, a cornerstone for many organizations' HR, finance, and supply chain operations, is no exception. Oracle Cloud Infrastructure (OCI) provides a powerful, secure, and cost-effective platform for running PeopleSoft, and at the heart of managing PeopleSoft on OCI lies PeopleSoft Cloud Manager (PCM). This article delves into the intricacies of deploying PeopleSoft Cloud Manager 17 on OCI, with a specific focus on leveraging its capabilities for efficient environment cloning – a game-changer for development, testing, and training initiatives.

Overview

PeopleSoft Cloud Manager (PCM) is Oracle's specialized automation tool designed to simplify the deployment, management, and lifecycle of PeopleSoft environments on Oracle Cloud Infrastructure. Version 17 brings enhanced features, improved performance, and greater integration with OCI services, making it an indispensable tool for PeopleSoft administrators. Its core value proposition lies in its ability to provision new environments rapidly, apply patches and updates with minimal downtime, and, critically, clone existing environments with remarkable ease and consistency. This capability drastically reduces the time and effort traditionally associated with creating new development, testing, or training instances, accelerating project timelines and improving resource utilization.

The traditional process of cloning a PeopleSoft environment involves a laborious sequence of database backups and restores, application server and web server configurations, file system synchronization, and extensive post-clone cleanup. This manual effort is prone to errors, time-consuming, and often requires specialized DBA and PeopleSoft administration skills. PCM on OCI automates this entire workflow, leveraging OCI's native services like Compute, Object Storage, Networking, and Database Cloud Service (DBCS) to deliver a streamlined, repeatable, and reliable cloning mechanism. It transforms what was once a multi-day ordeal into a process that can be initiated and completed within hours, or even minutes, depending on the environment size and complexity.

Prerequisites

Before embarking on the deployment of PeopleSoft Cloud Manager 17 and subsequent environment cloning, several prerequisites must be meticulously addressed on Oracle Cloud Infrastructure. A well-prepared OCI tenancy is crucial for a smooth and successful deployment.

1. OCI Account and Permissions (IAM Policies)

You need an active OCI tenancy with administrator privileges or a user group granted the necessary IAM policies. Cloud Manager requires broad permissions to manage various OCI resources.

# Example IAM Policy for a group named 'TechNews-PCM-Admins'
# Replace 'ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs' with your actual Cloud Manager compartment OCID

allow group TechNews-PCM-Admins to manage instance-family in compartment ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs
allow group TechNews-PCM-Admins to manage volume-family in compartment ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs
allow group TechNews-PCM-Admins to manage virtual-network-family in compartment ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs
allow group TechNews-PCM-Admins to manage database-family in compartment ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs
allow group TechNews-PCM-Admins to manage object-family in compartment ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs
allow group TechNews-PCM-Admins to manage audit-events in compartment ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs
allow group TechNews-PCM-Admins to manage key-family in compartment ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs
allow group TechNews-PCM-Admins to manage functions-family in compartment ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs
allow group TechNews-PCM-Admins to use tag-namespaces in compartment ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs
allow group TechNews-PCM-Admins to read users in tenancy
allow group TechNews-PCM-Admins to read groups in tenancy
allow group TechNews-PCM-Admins to inspect compartments in tenancy

2. Virtual Cloud Network (VCN) Setup

A properly configured VCN with subnets, security lists (or Network Security Groups - NSGs), and route tables is essential. It's recommended to have separate subnets for application and database tiers for better security and organization.

• VCN: TechNews-PCM-VCN (e.g., CIDR: 10.0.0.0/16)
• Cloud Manager Subnet: TechNews-PCM-AppSubnet (e.g., CIDR: 10.0.1.0/24) - for the PCM instance itself.
• PeopleSoft Application Subnet: TechNews-PSFT-AppSubnet (e.g., CIDR: 10.0.2.0/24) - for future PeopleSoft application servers.
• PeopleSoft Database Subnet: TechNews-PSFT-DBSunet (e.g., CIDR: 10.0.3.0/24) - for future PeopleSoft database instances.
• Internet Gateway: For outbound internet access (e.g., for downloading patches, updates).
• Service Gateway: For private access to OCI services like Object Storage and Autonomous Database.
• NAT Gateway: For instances in private subnets to initiate connections to the internet.

Ensure security lists or NSGs allow:

• SSH (port 22) from your administrative IPs.
• HTTPS (port 443) to the Cloud Manager instance.
• Inbound/outbound traffic between application and database subnets (e.g., Oracle Net port 1521, PeopleSoft application server ports 8000/8443, web server ports 80/443).

3. SSH Key Pair Generation

An SSH key pair (public and private) is required to access the Cloud Manager instance and subsequent PeopleSoft environments. The public key will be uploaded to OCI, and the private key will be used for SSH access.

ssh-keygen -t rsa -b 2048 -f ~/.ssh/tech-news-cm-ssh-key
# This creates tech-news-cm-ssh-key (private) and tech-news-cm-ssh-key.pub (public)

4. OCI CLI Installation and Configuration

While PCM deployment is typically via the OCI console, having the OCI CLI configured is invaluable for managing other OCI resources, troubleshooting, and scripting. Ensure your CLI is configured with the correct tenancy OCID, user OCID, fingerprint, and region.

# Install OCI CLI (example for Linux)
bash -c "$(curl -L https://raw.githubusercontent.com/oracle/oci-cli/master/scripts/install/install.sh)"

# Configure OCI CLI
oci setup config
# Follow prompts for User OCID, Tenancy OCID, Region (e.g., us-ashburn-1), API key pair path

5. Object Storage Bucket for PCM Installer

Cloud Manager requires an Object Storage bucket to store its installer files and to act as a staging area for PeopleSoft images and PUM (PeopleSoft Update Manager) updates.

oci os bucket create \
    --compartment-id ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs \
    --name peoplesoft-cm-installers-us-ashburn-1 \
    --namespace your_object_storage_namespace \
    --public-access-type NoPublicAccess

Note: your_object_storage_namespace can be found in the OCI Console under Object Storage -> Bucket Details.

6. PeopleSoft Cloud Manager Image from Marketplace

The Cloud Manager instance is deployed from an image available in the OCI Marketplace. Ensure you have subscribed to the "PeopleSoft Cloud Manager" listing.

7. Database Cloud Service (DBCS) Configuration (Optional but Recommended)

While PCM can provision new databases, having an existing DBCS instance or understanding its setup is beneficial. For cloning, PCM will often create new databases or PDBs within existing DBCS instances. Ensure you have appropriate database versions and editions available (e.g., Oracle 19c Enterprise Edition).

Step-by-step Implementation

1. Deploying PeopleSoft Cloud Manager 17 from OCI Marketplace

The initial step is to deploy the Cloud Manager instance itself. This is done via the OCI Console.

1. Navigate to Marketplace -> All Applications.
2. Search for "PeopleSoft Cloud Manager". Select the latest version (e.g., "PeopleSoft Cloud Manager 17").
3. Click Launch Stack.
4. Stack Information: Provide a name (e.g., TechNews-PCM-17) and select the compartment (e.g., ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs).
5. Configure Variables:
   • Cloud Manager Instance Shape: A VM.Standard2.4 or VM.Standard.E3.Flex (with 4 OCPUs, 64GB RAM) is a good starting point.
   • VCN and Subnet: Select your pre-configured TechNews-PCM-VCN and TechNews-PCM-AppSubnet.
   • SSH Public Key: Paste the content of your tech-news-cm-ssh-key.pub file.
   • Object Storage Bucket Name: Enter peoplesoft-cm-installers-us-ashburn-1.
   • Cloud Manager Admin Password: Set a strong password.
   • Cloud Manager Hostname: Provide a hostname like pscm17.
6. Review and click Create. The Resource Manager stack will provision the Cloud Manager instance, install necessary software, and configure it. This process can take 30-60 minutes.

2. Initial Configuration of Cloud Manager

Once the Cloud Manager instance is running, access its web interface. You can find the public IP address of the instance in the OCI Console.

# Example to get public IP via OCI CLI
oci compute instance list \
    --compartment-id ocid1.compartment.oc1..aaaaaaaaabcdefghijklmnopqrs \
    --display-name pscm17 \
    --query "data[0].\"vnic-attachments\"[0].vnics[0].\"public-ip\"" \
    --raw-output
# Expected output: 129.150.112.205 (example IP)

Access the PCM UI via https://<Public_IP_or_DNS>/psft/cm/ (e.g., https://129.150.112.205/psft/cm/). Log in with user psadm and the password you set during deployment.

• OCI Credentials Setup: Cloud Manager needs to know how to interact with your OCI tenancy.
  1. Go to Cloud Manager Settings -> OCI Credentials.
  2. Add a new OCI User. Use an OCI user that belongs to the TechNews-PCM-Admins group. You'll need the User OCID, Tenancy OCID, Fingerprint of the API key, and the API Key itself (the private key file content).
• OCI Identity Integration: Configure Cloud Manager to use OCI IAM for user authentication.
  1. Go to Cloud Manager Settings -> OCI Identity.
  2. Enable OCI Identity and configure the necessary parameters (Identity Domain URL, Client ID, Client Secret). This allows you to log into PCM using your OCI IAM credentials.
• Define OCI Regions and Compartments:
  1. Navigate to Cloud Manager Settings -> OCI Regions and add the regions you intend to manage (e.g., us-ashburn-1).
  2. Under OCI Compartments, add the compartments where your PeopleSoft environments will reside (e.g., TechNews-Dev, TechNews-Prod).
• Define Network Topologies:
  1. Go to Cloud Manager Settings -> Network Topologies.
  2. Create a new topology, linking your VCNs and subnets (e.g., TechNews-PCM-VCN, TechNews-PSFT-AppSubnet, TechNews-PSFT-DBSunet). This tells PCM where to deploy new environments.

3. Preparing the Source Environment for Cloning

Before you can clone an environment, it must be "managed" by Cloud Manager. This typically involves registering an existing PeopleSoft environment or deploying a new one using PCM. For cloning, you need an "image" of the source environment.

• Registering an Existing Environment: If you have an existing PeopleSoft environment on OCI that wasn't deployed by PCM, you can register it. This involves providing SSH access, database details, and application server/web server information to PCM.
• Creating an Environment Image: Once an environment is managed, PCM can create an "environment image" or a "PUM Image" (for applying updates). For cloning, we'll create a full environment image.
  1. In Cloud Manager UI, go to Environments. Select your source environment (e.g., HCM92-DEV-US-ASHBURN-1).
  2. Click Actions -> Create Environment Image.
  3. Provide a name (e.g., HCM92-DEV-BaseImage-20231027) and description.
  4. PCM will perform a series of steps:
     • Take a snapshot of the database (if using DBCS, it leverages OCI's block volume snapshots or RMAN backups).
     • Create custom images of the application and web server compute instances.
     • Store metadata in Object Storage.
     This process can take several hours depending on the database size and number of application/web servers. Monitor the activity log in PCM.

4. The Cloning Process

With a successfully created environment image, you are ready to clone.

1. In Cloud Manager UI, go to Environments.
2. Click Create Environment.
3. Deployment Type: Select Clone from Environment Image.
4. Environment Image: Select the image you created in the previous step (e.g., HCM92-DEV-BaseImage-20231027).
5. Environment Details:
   • Environment Name: Provide a unique name for the new cloned environment (e.g., HCM92-TEST-US-ASHBURN-1).
   • Description: A brief description.
   • Compartment: Select the target compartment (e.g., TechNews-Dev).
   • OCI Region: Select the region (e.g., us-ashburn-1).
   • Network Topology: Select the appropriate network topology (e.g., TechNews-PCM-VCN-Topology).
6. Database Configuration:
   • Database Option: You can choose to create a new Oracle Database Cloud Service (DBCS) instance, create a new Pluggable Database (PDB) within an existing DBCS, or use an existing PDB. For a full clone, creating a new DBCS or PDB is common.
   • If creating a new DBCS: Specify shape (e.g., VM.Standard.E3.Flex - 2 OCPU), storage, database name (e.g., HCMTDB), PDB name (e.g., HCMTDBPDB), admin passwords, etc.
   • If creating a new PDB: Select the existing DBCS instance and provide a new PDB name.

   PCM will handle the database restoration from the image's backup.

7. Application and Web Server Configuration:
   • Application Server Count/Shape: Specify the number of application servers and their compute shapes (e.g., VM.Standard.E3.Flex - 1 OCPU).
   • Web Server Count/Shape: Specify the number of web servers and their compute shapes.
   • Load Balancer: Choose to provision a new OCI Load Balancer if desired.
   • SSH Public Key: Provide the same SSH public key used for PCM.
8. Review and Deploy: Review all configurations. Click Deploy.

PCM will now orchestrate the cloning. This involves:

• Provisioning new Compute instances for application and web servers.
• Provisioning a new DBCS instance or PDB.
• Restoring the database from the environment image's backup.
• Configuring the PeopleSoft application servers (domains, configuration files).
• Configuring the PeopleSoft web servers (web profiles, deployed war files).
• Updating configuration files with new IP addresses, hostnames, and database connection strings.
• Performing post-clone cleanup and setup (e.g., cache clearing, security file updates).

Monitor the progress in the Cloud Manager activity log. Upon successful completion, you will have a fully functional, cloned PeopleSoft environment ready for use.

5. Post-Cloning Steps

After a successful clone, some application-specific and network-level configurations might be necessary.

• Verification:
  • Access the new environment's login page via the provided URL (from PCM environment details).
  • Log in and verify core functionality.
  • Check application server and web server logs for errors.
• Network Adjustments: If using a load balancer, verify its backend sets are healthy. Adjust security lists/NSGs if specific external access is required.
• Application-level Configurations:
  • Update integration broker nodes to point to correct endpoints.
  • Clear application server and web server caches.
  • Update any hardcoded URLs or server names within PeopleSoft configuration if not handled by PCM.
  • Review and adjust scheduled processes and batch jobs to prevent unintended execution in the new environment.
• Backup Strategy: Implement a robust backup strategy for the new environment, leveraging OCI's native backup capabilities for DBCS and block volumes.

Security Considerations

Security is paramount when deploying and managing PeopleSoft environments on OCI. Adhere to the principle of least privilege and implement a defense-in-depth strategy.

• IAM Policies: Ensure IAM policies grant only the necessary permissions to Cloud Manager and administrative users. Regularly review and audit these policies.
• Network Security:
  • Use Network Security Groups (NSGs) or Security Lists to restrict network traffic to the absolute minimum required ports and IP ranges.
  • Isolate database subnets from application subnets and both from public access where possible.
  • Use a private subnet for the Cloud Manager instance if it doesn't require direct public internet access, using a NAT Gateway for outbound connectivity.
  • Implement WAF (Web Application Firewall) services like OCI WAF for public-facing PeopleSoft web servers.
• Data Encryption: All data at rest (OCI Block Volumes, Object Storage, Database) and in transit (SSL/TLS for web traffic, TDE for database) should be encrypted. OCI encrypts data at rest by default.
• SSH Key Management: Protect your SSH private keys. Use an SSH agent and restrict access to these keys. Consider using OCI Bastion Service for secure SSH access without exposing instances directly.
• Regular Patching: Keep Cloud Manager, the underlying OS (Oracle Linux), and PeopleSoft environments regularly patched with the latest security updates.
• Audit and Logging: Enable OCI Audit logs and integrate them with OCI Logging Analytics or a SIEM solution for continuous monitoring of activities.
• Secrets Management: Utilize OCI Vault to securely store sensitive credentials (e.g., database passwords, API keys) instead of hardcoding them.

Best Practices

• Compartment Strategy: Organize your OCI resources into logical compartments (e.g., Dev, Test, Prod, Shared Services) to enforce access control and manage billing effectively.
• Tagging: Implement a consistent tagging strategy (e.g., Project, Environment, Owner) for all OCI resources provisioned by PCM to aid in cost management, automation, and resource identification.
• Automation First: Leverage Cloud Manager's automation capabilities for all lifecycle management tasks – deployments, patching, cloning, and decommissioning. Avoid manual interventions where possible to ensure consistency.
• Cost Management: Monitor OCI costs closely. Utilize Cloud Manager's ability to easily tear down environments when not in use (e.g., development/test environments overnight or weekends) to optimize spend. Consider smaller compute shapes for non-production environments.
• Backup and Recovery: Establish and regularly test a comprehensive backup and disaster recovery strategy for all PeopleSoft environments, including the Cloud Manager instance itself. Leverage OCI's native backup features for DBCS and Object Storage.
• Monitoring and Alerting: Implement OCI Monitoring and Alarms for critical metrics (CPU, memory, disk I/O, network traffic) on all PeopleSoft components. Integrate with notification services (e.g., OCI Notifications, PagerDuty).
• Version Control for Configurations: While PCM manages much of the configuration, store any custom scripts, configuration templates, or environment-specific parameters in a version control system.
• Leverage OCI Load Balancer: Always deploy a load balancer for web servers in production and critical non-production environments to ensure high availability and efficient traffic distribution.

FAQ

1. Can PeopleSoft Cloud Manager clone environments across different OCI regions?

   Yes, PeopleSoft Cloud Manager 17 supports cross-region cloning. When creating an environment image, you can specify the target region, and PCM will handle the replication of database backups and compute images to the chosen region's Object Storage and Image services, enabling a seamless cross-region deployment.

2. What happens to the data in the cloned environment? Is it a full copy?

   A full clone using PeopleSoft Cloud Manager creates an exact replica of the source environment's database and file systems at the time the environment image was created. This means all application data, configurations, and customizations present in the source are copied to the new cloned environment. It is a complete, point-in-time copy.

3. Can I customize the compute shapes or database options for the cloned environment?

   Absolutely. During the cloning wizard in Cloud Manager, you have the flexibility to specify different compute shapes (OCPUs, memory) for the application and web servers, and also choose various database options (e.g., create a new DBCS, use an existing PDB, different database shapes or storage configurations) for the target environment, independent of the source environment's specifications. This allows for right-sizing your cloned environments based on their specific use cases (e.g., smaller for development, larger for performance testing).

Conclusion

The deployment of PeopleSoft Cloud Manager 17 on OCI, particularly for environment cloning, represents a significant leap forward in managing complex PeopleSoft landscapes. By automating what were once arduous, error-prone manual tasks, organizations can achieve unprecedented agility, accelerate their development cycles, and significantly reduce operational overhead. The ability to provision identical copies of production or development environments on demand empowers teams to innovate faster, test more thoroughly, and train more effectively, all while leveraging the robust, scalable, and secure foundation of Oracle Cloud Infrastructure. Embracing PCM 17 is not just about moving PeopleSoft to the cloud; it's about transforming how PeopleSoft is managed, making it a truly cloud-native application experience.