Deploying PeopleSoft on Oracle Cloud Infrastructure...A Java-enabled Web server, which is an Oracle WebLogic server, is deployed on OCI Cloud Compute Service and is required to extend

Deploying PeopleSoft on Oracle Cloud Infrastructure O R A C L E W H I T E P A P E R | O C T O B E R 2 0 1 8

DEPLOYING PEOPLESOFT ON ORACLE CLOUD INFRASTRUCTURE

Disclaimer

The following is intended to outline our general product direction. It is intended for information purposes

only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code,

or functionality, and should not be relied upon in making purchasing decisions. The development,

release, and timing of any features or functionality described for Oracle’s products remains at the sole

discretion of Oracle.

0 | DEPLOYING PEOPLESOFT ON ORACLE CLOUD INFRASTRUCTURE

Table of Contents

Executive Overview 1

Introduction 2

Implementation Overview 2

Virtual Cloud Network 3

Compute 5

PeopleSoft WebLogic Server 7

PeopleSoft Application Server 7

PeopleSoft Application Tier Configuration 8

PeopleSoft WebLogic Tier Configuration 8

PeopleSoft Windows Server 8

Database 10

Oracle Cloud Infrastructure Load Balancer for PeopleSoft 10

Deploy Back End Set and HTTP Listeners 12

OCI Load Balancer Configuration for PeopleSoft 12

Establish Connection Between Tiers 14

Migrating PeopleSoft Database to Oracle Cloud Infrastructure Database Service 14

Choosing a Migration Method 14

Data Pump Conventional Export/Import 15

PeopleSoft DPK Application Tier Install on Oracle Cloud Infrastructure 16

Conclusion 17

References 18


Executive Overview

PeopleSoft applications customers want to maintain control of their own unique configuration of customizations and

data and with the help of Oracle Cloud Infrastructure or OCI, they can. OCI provides integrated network, block storage,

object storage, identity and access management, VPN connectivity, and a software-defined Virtual Cloud Network

(VCN) to provide PeopleSoft customers a complete end-to-end solution that will keep their customizations as is.

Utilizing Oracle Cloud Infrastructure, in conjunction with Viscosity’s complete Migration Services and Managed Cloud

solution, provides Oracle PeopleSoft customers a competitive edge as they make their move to the Oracle Cloud.

This paper illustrates how Oracle and Platinum Partner, Viscosity North America, developed a joint cookbook-approach

for provisioning a PeopleSoft application on Oracle Cloud Infrastructure configuration; including network, compute,

database, load balancing service, and storage. The second section of this paper describes the migration of an on-

premise PeopleSoft Database to the Oracle Cloud Infrastructure.


Introduction

Oracle Cloud Infrastructure (OCI), can be provisioned from https://cloud.oracle.com, under the Infrastructure tab. The

Services can be provisioned on-demand, by console or API, with ‘pay as you go’ consumption-based billing.

For on-premise systems, a business user or DBA would typically request compute, network, storage, and necessary HA

to be provisioned to support a new application. Similarly, with OCI, the Cloud Administrator would provision the

appropriate compute, block storage, object storage, load balancing, and network resources for the requestor. The

Oracle Cloud Infrastructure is built to emulate a complete on-premise datacenter, with all the security and isolation,

operational control and isolation management, as well as predictable performance.


In this document, the OCI infrastructure to be built out is used to host a PeopleSoft implementation.

Figure 1. Oracle Cloud Infrastructure main console page.

Implementation Overview

To ensure proper configuration of the PeopleSoft deployment on OCI, the following were considered.

• Deploy the PeopleSoft Application database in OCI Database Service • Deploy the PeopleSoft Mid/tier (App and Web tier) in OCI Compute Service • Deploy Windows server for File and Batch server deployment on OCI Compute Service • Establish a SQL*net connectivity between Mid-tier OCI Compute and OCI Database service • Provision OCI Block Volume for high performance storage for Mid-tier and Batch tier • Provision OCI Load Balancer services to automatically route traffic across Availability Domains for highly-

available and fault- tolerant PeopleSoft application.


Figure 2. This diagram illustrates a standard Cloud configuration in Oracle Cloud Infrastructure

This document was written in the context of PeopleSoft HCM Application version 9.2, PeopleTools Version 8.55.xx running on Oracle Database 12c Release 1, with Oracle Tuxedo® 12.1.3.0.0 (64-bit) and Oracle WebLogic Server™ 12.1.3.0.0.

Figure 3. This diagram describes the PeopleSoft Architecture deployment on Oracle Cloud Infrastructure (OCI).


Virtual Cloud Network A Virtual Cloud Network (VCN) is a customizable and private network in Oracle Cloud Infrastructure. As with traditional data center networks, the VCN provides complete control over the OCI network environment; which includes assigning your own private IP address space, creating subnets, route tables, and configuring stateful firewalls. A single tenant can have multiple VCNs, thereby providing grouping and isolation of related resources.

Figure 4. Virtual Cloud Network (VCN) enablement and configuration page.

A provisioned VCN automatically includes a default route table, default security list, and default set of DHCP options. In addition, administrators can define a private IP address range specified as 10.0.0.0/8, 172.16/12, or 192.168/16. The allowable VCN size range is /16 to /30.

NOTE: in this PeopleSoft use case, the “CREATE VIRTUAL CLOUD NETWORK PLUS REALTED RESOURCES” option was chosen. This option configures the essential network layout, such as subnets and route tables.


A fully completed VCN definition will yield an entry in the VCN Instance page.

Figure 5. After enablement of VCN, the following entry will be seen in Networking VCN page.

Compute The central service within OCI is the Compute Service. A Compute Service in OCI, is referred to as an Instance.

Key components of an Instance include:

• Virtual Cloud Network • Availability Domain • SSH Key Pairs • OS Image • Compute Shapes

Figure 6. On Compute Instances page, Compute Instances can be created. In this example, a Web Server Instance will be created.


Execute the “Launch Instance” link to create the Compute Instance; select the appropriate image, network, etc. In this example, Oracle Linux was selected and mapped back to a previously defined VCN.

Figure 7. This page illustrates the Web Server configuration details. Note, the Network entry specifies the earlier created VCN configuration.

When an Instance is provisioned, each Instance automatically receives both a public and private IP address. Connection from the on-premise network to OCI Compute Instances can be accomplished via ssh, using the public IP address.

After an Instance is created and started, administrators will need to add local storage for applications, etc. Block Volume Service volumes can be either 256 GB or 2 TB.


NOTE: to attach a volume to an instance, both the instance and volume must be within the same Availability Domain.

A block storage device can be dynamically expanded as needed for the storage capacity of an instance. This Block

volume can be deemed as a movable device; i.e., the volume can be detached from the instance and subsequently be

moved to a different instance, without the loss of data. This data persistence allows for easy migration of data between

instances and ensures that the data is safely stored, even when it is not connected to an instance. Any data will remain

intact until the volume is reformatted or deleted.

In the next sections, steps for creating the appropriate set of Compute Instances, using the steps listed above, to support

the PeopleSoft configuration will be reviewed.

PeopleSoft WebLogic Server

A Java-enabled Web server, which is an Oracle WebLogic server, is deployed on OCI Cloud Compute Service and is required to extend the PeopleSoft architecture to the internet and intranet. A collection of PeopleSoft Java servlets, designed to handle a wide range of PeopleSoft transactions, originating from the internet or an intranet, are deployed through PeopleSoft Internet Architecture on the web server.

Create OCI Linux Instance to deploy PeopleSoft WebLogic Server. Details on how to create and deploy a Linux Instance can be found at “Launching your first Instance” under the OCI documentation.

Figure 8. This page illustrates the Web Server configuration details. Note, the Network entry specifies the earlier created VCN configuration.


PeopleSoft Application Server

For the PeopleSoft on OCI project, another Linux compute instance was created to host the PeopleSoft Application Server. Once the Web Server is provisioned, provision and configure PeopleSoft Application server on OCI Linux server.

Figure 9. This page illustrates the Application Server configuration details.

PeopleSoft Application Tier Configuration

Please follow the installation guide to install and configure the following on the OCI Linux host from Oracle e-Delivery site.

• Install Oracle 12c Client software • Install PeopleTools 8.55 software • Install Oracle Tuxedo 12c Release 2 for PeopleSoft PeopleTools 8.55 with RP037 Patch installation.

PeopleSoft WebLogic tier (PIA) Configuration

The following PeopleSoft software needs to be installed on the Webtier.

• PeopleTools 8.55 for Web tier with PeopleSoft Internet Architecture • Oracle Fusion Middleware 12c (12.1.3.0.0) • WebLogic Server and Coherence.


PeopleSoft Windows Server

Figure 10. This page illustrates the Windows Server 2012 configuration details.

This section will list the details for the setup of PeopleSoft Windows File and Batch Server:

1. Launch an instance with the Oracle Windows image and basic shape.

2. In the Console, click Compute.

3. Click Launch Instance.

4. In the Launch Instance dialog, enter the following:

5. Name: Enter a name, for example: <your initials>_Instance.

6. Availability Domain: Select the first Availability Domain in the list (AD-1).

7. Image: Select Windows2012ServerR2-Standard.

8. Shape: Select one of the VM.Standard options.

9. The shape defines the number of CPUs and amount of memory allocated to the instance.

10. Virtual Cloud Network: Select the cloud network you created.

11. Subnet: Select the subnet created with your cloud network.

12. Private IP Address: Leave blank.

13. Assign public IP address: Leave checked.

14. Hostname: Leave blank. Hostname is not required. For more information about how hostname is used, see Validation and Generation of the Hostname.

15. Click Launch Instance.


The instance displayed in the Console is in a provisioning state. Expect provisioning to take several minutes before the status updates to running. Do not refresh the page. Once the instance is running, allow another few minutes for the operating system to boot before attempting to connect.

Once the Windows Instance is launched, RDP into the host machine and install the PeopleSoft client software. Follow the PeopleSoft Installation guidelines for PeopleTools 8.55.

Go to e-delivery.oracle.com and download the following on Windows.

• PeopleTools 8.55 software • Oracle Client software for 12c • Oracle Tuxedo software

Follow the PeopleTools installation guide for Oracle to install the above software on the newly provisioned windows machine. For details on installation, review the following link: http://docs.oracle.com/cd/E68526_01/psft/acrobat/PeopleTools_855_Installation_for_Oracle_122015.pdf.

Database

With OCI Database Service, customers can deploy Oracle databases on-demand, on a dedicated hardware platform, with in-depth security, and granular controls in a highly durable and available cloud environment. Also note, the database can be deployed on Exadata CS. In this use case, an Oracle 12.1.0.2 Database with CDB/PDB configuration was created on Bare Metal.

Figure 11. This page describes the OCI Database setup, which will be used to host the PeopleSoft database.


PeopleSoft Cloud Manager PeopleSoft Cloud Manager (CM) is a PeopleSoft application that runs on Oracle Cloud Infrastructure to help accelerate adoption as well as to optimize the benefits of running PeopleSoft on Cloud.

This section will reveal the key aspects and features of PeopleSoft CM.

PeopleSoft CM brings an unprecedented extent of automation to migrate your existing environment from on-premises and to rapidly clone and create new environments on the cloud tailored for specific functional use - such as development, customization, user acceptance testing, performance testing or production. PeopleSoft CM comes with a built in automated download manager and provides automated lifecycle operations such as PeopleTools only upgrade, PeopleTools update, setting up of selective adoption environments, and application change packages. Moreover, PeopleSoft CM continuously delivers enhancements to adopt new OCI features.

Note: This paper does not illustrate PeopleSoft Lift N’ Shift using Cloud Manager. It has been examined here for completeness

The following diagram illustrates the architecture for PeopleSoft Cloud Manager

Figure 12. Cloud Manager Architecture in on OCI


PeopleTools 8.57 Subscription

PeopleSoft Cloud Manager image 7 enables customers to be among the very first to get access to PeopleTools 8.57. Using a subscription to the PeopleTools maintenance channel within Cloud Manager, PeopleTools 8.57 will be automatically downloaded. When upgrading to the latest PeopleTools release, simply select the desired PeopleTools level and let Cloud Manager perform the update1

Environment Provisioning Status

Cloud Manager enables customers to view the current status of all VM instances and status of domains running in them.

The Provisioning Status page facilitates users to access provisioning details and error summary, if the provisioning failed.

Figure 13. Provisioning Status Page

Cloud Manager REST APIs

REST APIs in Cloud Manager allow customers and testers to automate their interaction with Cloud Manager, by-passing the Web User Interface.

Cloud Manager supports REST services in the following areas:

• Topology Management

• Template Management

• Environment Management

• Channel Management

• Lift and Shift Management

1 Cloud Manager supports the lift and shift of non-Unicode database.


Cloud Manager Self-Update

Cloud Manager self-update feature enables customers to update to a newer CM image. It also has the flexibility to auto-restore the latest backup stored in Oracle Cloud and reconcile any pending environments that are missing in the backup.

Figure 14. Manage Updates Page

Domain Customization

This feature enables users to define and configure web or app domains in topology or template definitions.

Database Cloud Service (DBCS) Support

Database Cloud Service feature allows users to select the database software edition and optionally enable RAC when deploying PeopleSoft database environments.

Environment Template Page

The Environment Template page enables users to define the number of domains and configure specific domain attributes.


Figure 15. Main Cloud Manager Page

Figure 16. Environment Template Page


File Server (FS) Decoupling

The FS Decoupling feature facilitates users to create a file server directly from CM User Interface, instead of bootstrap. The File Server page enables users to configure file server as repository for Cloud Manager.

Figure 17. File Server Page

Cloud Manager Settings Page

The Cloud Manager Settings page enables the administrator to change the system settings that are pre-populated based on the input provided during the Cloud Manager installation Bootstrap process.

Figure 18. The Cloud manager Settings fluid page


Various settings available in the Cloud Manager Settings page are:

• Oracle Cloud Service.

• My Oracle Support (MOS) Credentials.

• PeopleSoft Credentials for REST Services.

• Lift and Shift Container.

• COBOL License.

• Operating System Image.

You can also manage your VM size and PUM connection settings.

Repository

Cloud Manager Repository provides an easy way to automatically download and manage PeopleSoft Update Images (PIs), PeopleSoft Release Patchsets (PRPs), and PeopleTools releases and updates.

The Repository tile provides a page that enables the users to:

• Subscribe to Update Release Channels for latest PeopleSoft application updates.

• Manage downloaded PeopleSoft Images and PRPs.

Figure 19. The Repository Fluid Page


Topology

Topology defines the infrastructure layout that will be created on Oracle Cloud by Cloud Manager. This page enables the user to create topologies for PeopleSoft applications based on their requirements, as well as to edit, clone, or delete existing topology.

Figure 20. The Topology Fluid Page

Environment Templates

The environment template is a repeatable blueprint that is used to deploy PeopleSoft environments using Cloud Manager. This tile enables users to define environment templates, create new deployment templates, as well as edit, clone, or delete existing templates. It can also manage access restrictions to templates and deployed instances.

Figure 21.The Environment Template Page


The defining environment template feature delivered in Cloud Manager is a guided process that assists users when creating new templates in a simple four-step process:

• Entering general details

• Selecting topology

• Defining security

• Reviewing and submitting the details

Provision Environments

The Environments tile, which provides a page to define an environment with just a few clicks, enables users to manage PeopleSoft environments deployed on Oracle Cloud.

Specifically, users can:

• Check environment health on-demand

• Setup environment for Selective Adoption

• Apply a PeopleTools patch

• Manage environment attributes

• View logs

• Apply a template on running environments

Figure 22.The Environments Page – Card View


Lift and Shift

The Lift and Shift feature in Cloud Manager enables automated migration of on-premise PeopleSoft environments to Oracle Cloud. This page (shown below) provides a page that includes the lift utility and lifted containers, facilitates users viewing and accessing the lifted environments.

Figure 23.The Lift and Shift Landing Page

Using this feature users can:

• Run the lift process by downloading the lift utility for migrating on-premise environment to Oracle Cloud.

• Perform the shift process to provision the migrated environment from Oracle Cloud. The shift process can be done by means of a guided process. The tasks are to:

o Define target database details

o Define custom attributes as per lifted environment

o Review and submit the details

Selective Adoption

Cloud Manager enables customers to take advantage of Selective Adoption by:

• Quickly creating PUM environments in Oracle Cloud.

• Automating configuration of target databases in the PUM source.

With this feature, users can:

• Deploy PUM images quickly

• Deploy and configure Change Assistant on the Windows Client

Update source environment with PRP and patches

21 | DEPLO

YING

PEOPLESO

FT ON

OR

ACLE C

LOU

D IN

FRASTR

UC

TUR

E

• D

efine new target databases and upload to the PU

M Source

• Launch PU

M U

pdate Manager

• C

reate and apply change packages using Com

mand Line Interface

Cloud M

anager Logs

Cloud M

anager enables customers to view

different types of logs which contain useful inform

ation for analyzing any environm

ent related issues or failures that may occur in the system

.

Different log types available are:

• Python logs

• Environm

ent Action logs

• D

ownload M

anager logs

• App Server D

omain logs

• Process Scheduler D

omain logs

• Puppet logs in provisioned VM

s

Backing Up and R

estoring in Cloud M

anager

The Cloud M

anager instance provides a comm

and line utility. Users can backup C

loud Manage on to O

racle Cloud Storage

and the restore process allows you to restore the backups.

OC

I Load Balancer for PeopleSoft The O

racle Cloud Infrastructure Load Balancing Service, provides autom

ated traffic distribution from one entry point to

multiple servers, reachable from

your Virtual Cloud N

etwork (VC

N).

A load balancer improves resource utilization, facilitates scaling, and helps ensure high availability. It can configure

multiple load balancing policies and application-specific health checks to ensure that the load balancer directs traffic only

to healthy instances. The load balancer can reduce the maintenance w

indow, by draining traffic from

an unhealthy application server before rem

oving it from service for m

aintenance.

The Load Balancing Service enables creation of a public or private load balancer within the VC

N. A public load balancer

has a public IP address that is accessible from the internet. A private load balancer has an IP address from

the hosting subnet, w

hich is visible only within your VC

N. M

ultiple listeners can be configured for an IP address to load balance transport Layer 4 and Layer 7 (TC

P and HTTP) traffic. Both public and private load balancers can route data traffic to

any backend server that is reachable from the VC

N.

In this PeopleSoft use case, a Load Balancing instance for the Public Subnet was created. Follow

the Oracle C

loud Infrastructure docum

entation to configure Oracle C

loud Load balancer for this PeopleSoft deployment.


Deploy Backend Sets and HTTP Listeners

The first step in the Load Balancing Instance provisioning, is the setup of Backend Sets. A Backed Set, is a logical container that holds information about the application cluster. Within the backend set, the following can be performed:

• Dynamically add or remove a backend (cluster node identifiable via an internal IP address and an application server port);

• Select a load-balancing policy that defines ingress traffic distribution policy to the cluster; • Configure a health check, so that the load balancer actively checks the health of your application before

forwarding the internet traffic.

Figure 24. Create backend sets.

An HTTP Listener Instance, is a container that specifies how the load balancer should handle the internet traffic. In the listener configuration page, specify the protocol, SSL termination at the load balancer tier, and the port that the load balancer uses to handle the internet traffic; in addition, associate a backend set to the listener. This allows forwarding of ingress internet traffic to the application cluster.

Figure 25. Create and configure HTTP Listeners

Once the Load Balancing is setup and enabled, there will be an entry in the Load Balancer Instance page.


Figure 26. Load Balancing Instance for the PeopleSoft Public Subnet.

Destinations Source: Cloud Manager and File Server

Source: Mid-tier Source: Database

Source: PeopleSoft Windows Client

Source: Full-tier Source: Elasticsearch

Cloud Manager and File Server

• NFS (ports 2049, 111, 892, and 32803)

• SSH (port 22)

NFS (ports 2049, 111, 892, and 32803)

NFS (ports 2049, 111, 892, and 32803)

• NFS (ports 2049, 111, 892, and 32803)

• PIA HTTP (port 8000)

• PIA HTTPS (port 8443)

NFS (ports 2049, 111, 892, and 32803)

NFS (ports 2049, 111, 892, and 32803)

Mid-tier SSH (port 22) • Jolt (port 9033)



NA • PIA HTTP (port 8000)


NA NA

Database SSH (port 22) Database ports (1521)

NA NA NA NA

PeopleSoft Windows client

• Winrm (ports 5985 and 5986)

• CIFS (ports 137, 138, 139, and 445)

NA NA NA NA NA

Full-tier SSH (port 22) NA NA • NFS (ports 2049, 111, 892, and 32803)



NA • PIA HTTP (port 8000)


Elasticsearch SSH (port 22) Elasticsearch HTTP (port 9200)

NA NA Elasticsearch (port 9200)

NA


OCI Load Balancer Configuration for PeopleSoft

When you create a listener, update VCN's security list to allow traffic to that listener.

The subnets where the load balancer resides, must allow traffic to be accepted by the listener. To enable the traffic to get to the listener, update the load balancer subnet's security list.

To update the security list to allow the listener to accept traffic:

1. Go to your VCN details page. 2. Click Security Lists.

• A list of the security lists in the cloud network is displayed. 3. Click the LB Security List. The details are displayed. 4. Click Edit All Rules. 5. Under Allow Rules for Ingress, click Add Rule. 6. Enter the following ingress rule:

§ Source CIDR: Enter 0.0.0.0/0 § IP Protocol: Select TCP § Destination Port Range: Enter 80 (the listener port).

7. Click Save Security List Rules.

Figure 28. Load Balancing Instance for the PeopleSoft Public Subnet and Sign on PeopleSoft Page

Figure 29. Signed into PeopleSoft Page on Oracle Cloud Infrastructure


Establish Connection between Tiers

This section will cover the connection details on session connectivity between the Mid-Tier/App Server and the Database Server - updating the Security List for the DB System. Oracle Database Service on OCI, supports access to the database on the standard Oracle Net Listener port (1521). Add the Oracle Net Listener port (1521) into the Security List for the DB System as shown in the Figure below.

The 'Source Port Range'= ALL and 'Destination Port Range'=1521.

1. Review the list of ports in Opening Ports on the DB System and for every port you open in iptables, update the security list used for the DB System, or create a new security list.

• Port 1521 for the Oracle default listener is included in iptables, but should also be added to the security list.

• Port 1521 needs to be allowed both from the Windows host and the Application server host to be able to access the database service.

2. Open To update an existing security list

3. In the Console, click Database and locate the DB System in the list.

4. The DB System's Subnet name and click its Virtual Cloud Network.

5. Locate the subnet in the list, and then click its security list under Security Lists. 6. Click Edit All Rules and add an ingress rule with source CIDR=0.0.0.0/0, protocol=TCP, and port=1521

7. Ready the Database Details for Connection

Establishment Username : <any user created>

Password: The database admin password that was specified while creating the

instance Hostname: Public IP address of the database

Port: 1521 after adding to the Security List.

Service Name: The concatenated Database Unique Name and Host Domain Name. It can be obtained by viewing detailed information of a database instance.

Migrating PeopleSoft Database to OCI Cloud Database Service The database migration can be executed using a number of different methods and tools. The method that applies to a given migration scenario, depends on several factors; including the version, character set, and platform endian format of the source and target databases.

In this section, a description on how to migrate an on-premise PeopleSoft Database to an OCI Database Service is provided, using the Datapump Export and Import method.

In this use case, the Database service is using HCM 9.2 Database with People tools 8.55 on Oracle Multitenant database 12c Release 1 (12.1.0.2).


Choosing a Migration Method

Not all migration methods apply to all migration scenarios. Many of the migration methods apply only if specific characteristics of the source and destination databases match or are compatible. Moreover, additional factors can affect which method is chosen for migration, from the methods that are technically applicable to your migration scenario.

Some of the characteristics and factors to consider when choosing a migration method are:

On-premises database version • Database Service database version • On-premises host operating system and version • On-premises database character set • Quantity of data, including indexes • Data types used in the on-premises database • Storage for data staging • Acceptable length of system outage • Network bandwidth

To determine which migration methods are applicable to your migration scenario, gather the information listed above. In this paper, the on-premise database characteristics include the following:

• Oracle Database 12c Release 1 version 12.1.0.2 • Multitenant container database (CDB) • Endian format (byte ordering) of the on-premises database’s host platform is little endian • The OCI Database Service uses the Linux platform, which is little endian. • The on-premise database character set and the OCI Database Service character set is Unicode. • Some migration methods require that the source and target databases use compatible database character sets.

Data Pump Conventional Export/Import

With the Data Pump utility, you can migrate an on-premises source PeopleSoft database, tablespace, schema, or table, to the OCI Database Service database, regardless of the endian format or database character set of the on-premise database.

The following tasks outline the steps to execute the PeopleSoft database migration to OCI database:

1. On the on-premise database host, invoke Data Pump Export and export the on-premise database. Use a secure copy utility to transfer the dump file to the Database Service compute node. On the Database Service compute node, invoke Data Pump Import and import the data into the database. After verifying that the data has been imported successfully, you can delete the dump file.

In this paper, an entire PeopleSoft SYSADM schema mode export and import and the on-premises database is on a Linux host.

2. On the on-premises database host, invoke Data Pump Export to export the PeopleSoft Schema.

3. On the on-premises database host, create an operating system directory to use for the on-premises database export files.


$ mkdir /u01/app/oracle/admin/psft psft/dpdump/for Hhcmpsft_cloud

4. On the on-premises database host, invoke SQL*Plus and log in to the on-premise database as the SYSTEM user.

Create a directory object in the on-premise database, to reference the operating system directory.

SQL> CREATE DIRECTORY dp_forHCMPSFT_cloud AS '/u01/app/oracle/admin/psft/dpdump/for_hcmpsftcloud';

Exit from SQL*Plus.

5. From the on-premise database host, invoke Data Pump Export as the SYSTEM user or another user with the DATAPUMP_EXP_FULL_DATABASE role and export the on-premise schemas. Provide the password for the user when prompted.

$ expdp system SCHEMA=SYSADM DIRECTORY=dp_for_hcmpsftcloud

6. Use a secure copy utility to transfer the dump file to the Database Service compute node.

7. The dump file is copied to the /u01 directory. Choose the appropriate location based on the size of the file that will be transferred.

8. On the Database Service compute node, create a directory for the dump file.

$ mkdir /u01/app/oracle/admin/PSFT/dpdump/from_onprem_hcmpsft

9. Before using the scp command to copy the export dump file, ensure the SSH private key, that provides access to the Database Service compute node, is available on your on-premises host.

10. On the on-premises database host, use the SCP utility to transfer the dump file to the Database Service compute node.

$ scp –i private_key_file \ /u01/app/oracle/admin/psft/dpdump/for_hcmpsftcloud/hcmpsftexport.dmp \

oracle@IP_address_DBaaS_VM:/u01/app/oracle/admin/PSFT/dpdump/from_onprem_hcmpsft

11. On the Database Service compute node, invoke Data Pump Import and import the data into the database.

12. With the Database Service compute node, invoke SQL*Plus and log in to the database as the SYSTEM user.

$ sqlplus system

Enter password: <enter the password for the SYSTEM user>

13. Create a directory object in the Database Service database.

SQL> CREATE DIRECTORY dp_from_onprem_hcmpsft AS

'/u01/app/oracle/admin/PSFT/dpdump/from_onpremhcmpsft';

Exit from SQL*Plus.

14. On the Database Service compute node, invoke Data Pump Import and connect to the database. Import the data into the database.

$ impdp system SCHEMAS=SYSAMD DIRECTORY=dp_from_onprem_hcmpsft

15. After verifying that the data has been imported successfully, you can delete the "hcmpsftexport.dmp" file. At this step, the PeopleSoft HCM database has been imported to OCI Database service.


PeopleSoft DPK Application Tier Install on Oracle Cloud Infrastructure With the release of PeopleTools 8.55, Oracle introduced the concept of DPK i.e. Deployment Kits. The PeopleSoft

(PS) architecture is comprised of different layers, i.e. Database Server, Application Server, Web Server, and Process Scheduler. When deploying a PS environment, first install the Database Server, as well as create and configure the App server, Web server, and Process Scheduler. This process also involves installation of software e.g., Database Software, PeopleTools, Application, Tuxedo, Web Server Software, etc. All of these activities take time and must be done in a particular order for everything to work correctly.

Deployment Kits (DPKs), available for download from Oracle Support, consists of utilities that are used to deploy the

PeopleSoft environment automatically. DPKs consist of scripts and configuration files, that can be used to automate the installation of necessary software, needed for deployment of PS environments. Post installation of software, the DPK can be used to deploy PeopleSoft in full- tier, mid-tier, deploy tools client only, install software only, install app domain only, install pia domain only, etc. In addition, the DPKs give the flexibility to choose what part of PS installation and system configuration you want to automate.

There are 2 main types of DPK files – PeopleTools DPK and Application DPK

• PeopleTools DPK – These files are available to download for the PeopleTools patch, and can be used to deploy all tiers of PS architecture except PS database. If you already have PS database, then use PeopleTools DPK to quickly scale and add an app server, web server or process scheduler. Another option is to install just the software and PeopleSoft Homes.

• Application DPK – Application DPK files are available to download as PS Image files. These image files

were previously available for deployment in Virtual machine management software, such as Virtual Box. Application DPKs can be used to deploy a fully functional PS application, including Database. Once downloaded, DPK files automate the setup of the PS environment using Puppet and Hiera. Puppet is open source software which allows automation and Hiera is used for configuration. Using the default configuration provided with Hiera files, Puppet is used to deploy the PS environment.

In this paper, the PeopleSoft DPK method of installing on OCI Compute Service has been depicted.


Conclusion

This document illustrated a cookbook-approach for provisioning a PeopleSoft application on Oracle Cloud Infrastructure

configuration; including network, compute, Database and storage, as well as the migration of an on-premise PeopleSoft

Database to OCI. Customers can run their existing PeopleSoft's Technology stack in the cloud without any changes. By

deploying PeopleSoft Infrastructure to Oracle Cloud Infrastructure customers can achieve greater business agility, while

lowering cost and risk.


References

PeopleSoft Installation on Oracle guide http://docs.oracle.com/cd/E68526_01/psft/acrobat/PeopleTools_855_Installation_for_Oracle_122015.pdf

PeopleSoft Deployment Package Installation: http://docs.oracle.com/cd/E71636_01/psft/acrobat/PeopleSoftPeopleTools855DeploymentPackagesInstallation OCI Loadbalancing Service Load Balancing in OCI example

Oracle Software Delivery Cloud https://edelivery.oracle.com/

PeopleSoft Enterprise: License Codes http://www.oracle.com/us/support/licensecodes/peoplesoft-enterprise/index.html

Oracle Cloud Infrastructure Getting Started Guide https://docs.cloud.oracle.com/iaas/pdf/gsg/OCI_Getting_Started.pdf Oracle Cloud Infrastructure User Guide https://docs.cloud.oracle.com/iaas/pdf/ug/OCI_User_Guide.pdf


C O N N E C T W I T H U S

blogs.oracle.com/oracle

facebook.com/oracle

twitter.com/oracle

oracle.com

viscosityna.com

Oracle Corporation, World Headquarters Worldwide Inquiries 500 Oracle Parkway Phone: +1.650.506.7000 Redwood Shores, CA 94065, USA Fax: +1.650.506.7200

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0617

PeopleSoft Deployment on Oracle Cloud Infrastructure October 2018 Author: Pat Bangalore, Oracle Master Principal Architect, Nitin Vengurlekar, CTO Viscosity North America

Documents

Deploying PeopleSoft on Oracle Cloud Infrastructure...A Java-enabled Web server, which is an Oracle WebLogic server, is deployed on OCI Cloud Compute Service and is required to extend