Re-submitting Failed Async Messages Automatically – PeopleSoft

Many a times Async messages have failed with errors – sometimes, it isn’t an “actual” error and goes away upon re-submitting. I agree that the best approach is to identify the root cause and get that resolved – however, it all depends on the scenario.

Here’s a quick code snippet to automate re-submission of failed messages. Looks like PeopleCode has had it all long, as part of the IntBroker class. šŸ™‚

You can use the following SQL to fetch the required values and pass it to a State record as part of an Application Engine process. The values from the State record can then be passed onto a PeopleCode step as listed below.

Subscription Contracts:

SELECT A.IBTRANSACTIONID, A.QUEUENAME, B.SEGMENTNO
FROM PSAPMSGSUBCON A, PSAPMSGPUBDATA B
WHERE     A.STATUSSTRING = 'ERROR'
AND A.IBPUBTRANSACTID = B.IBTRANSACTIONID
AND B.SEGMENTNO = 0
AND B.SUBSEGMENTNO = 1;

Publication Contracts:


SELECT A.IBTRANSACTIONID, A.QUEUENAME, B.SEGMENTNO
FROM PSAPMSGPUBCON A, PSAPMSGPUBDATA B
WHERE A.STATUSSTRING = 'ERROR'
AND A.IBPUBTRANSACTID = B.IBTRANSACTIONID
AND B.SEGMENTNO = 0
AND B.SUBSEGMENTNO = 1;

And pass the values to a PeopleCode step to re-submit either the Sub or Pub contracts:

Local string &sTransactionID, &sQueueName;
Local number &nSegmentNum;

&sTransactionID = <Transaction ID from the Do Select Action> ;
&sQueueName = <Queue Name from the Do Select Action>;
&nSegmentNum =<Segment Number from the Do Select Action>;

&resubStatus = %IntBroker.ReSubmit(&sTransactionID, &sQueueName, %IntBroker_SUB, &nSegmentNum);

Weā€™d have to replace %IntBroker_SUB with %IntBroker_PUB, for a Pub contract.

Please note : only messages with the following statuses can be re-submitted:

  • Cancelled
  • Edited
  • Error
  • Timeout

Hope this helps! šŸ™‚

Posted in Oracle, PeopleSoft, SQL | Tagged , , , , , | Leave a comment

Setting Up Kibana on FSCM PI 35 – PeopleTools 8.58.02

Hello Everyone!

Next up is setting up Kibana on FSCM PI 35.

ElasticSearch is installed out of the box for this PI, however Kibana isn’t.

Before we start installing Kibana, follow the steps provided in this post to reset the password for theĀ esadminĀ user. It is true that you can create a newĀ user and provide the requisite permissions – but, this approach saves you from having to deal with hassles around ElasticSearch configurations.

Once you’ve reset the password, ensure you’ve re-started ElasticSearch(also provided in the earlier post).

Now, let’s install Kibana. Login to Putty(installation instructions are available here).

  • Execute the following command(s)

[root@fscm92 bin]$ sudo -s su esadm1

  • Navigate to the ElasticSearch DPK Setup directory(this is based on FSCM PI 35)

[esadm1@fscm92 bin]$ cd /opt/oracle/psft/dpk/ES/setup

  • Execute the following command:

[esadm1@fscm92 setup]$ ./psft-dpk-setup.sh –install –install_base_dir /opt/oracle/psft/pt/ES

  • You’ll be prompted to enter values – if you’ve already installed ElasticSearch or Logstash, skip them

You’ve chosen to do a fresh installation of Elasticsearch, Logstash and Kibana.

Do you want to install Elasticsearch: (y/n): n

Do you want to install Logstash (Needed for PeopleSoft Health Centre): (y/n): n

Do you want to install Kibana: (y/n): y

Enter the server port for Kibana [ 5601 ] :

  • Enter the hostname along with http://

Enter the elasticsearch host[http(s)://hostname] : http://fscm92.ps.com

Enter the elasticsearch port [ 9200 ] :

Enter the password for esadmin : <enter your esadmin password here>
Re-enter the password for esadmin : <second time lucky>

  • You’ll see the following output from the installation script

Checking if Elasticsearch service is running…….

Elasticsearch service is running. Proceeding with the Kibana installation.

Extracting the new Kibana Binary …….
[OK]
Configuring Kibana ……
Kibana Keystore updated.
[OK]

Starting Kibana…..

Kibana installation is completed.
[esadm1@fscm92 setup]$

If you’ve reached this far, congratulations! šŸ™‚

Login to PeopleSoft using VP1Ā and update hostname and credentials in the following pages:

    • Navigate toĀ PeopleTools > Search Framework > Administration > Search InstanceĀ and update the password for theĀ esadminĀ user (the following screenshot is based on HCM PI 34)

SS-01

    • Navigate toĀ PeopleTools > Search Framework > Administration > Monitoring ServerĀ > Configure ServerĀ tab and update the password for theĀ esadminĀ username
      • You can either update it manually or run the script provided inĀ this post (the following screenshot is based on HCM PI 34)

SS-02

See if you’re able to access the Kibana home page from http://fscm92.ps.com:5601/

Hope this helps! Have fun! šŸ™‚

Posted in Oracle, PeopleSoft, SQL | Tagged , , , , , | Leave a comment

Resolving Issues with esadmin Password – PeopleTools 8.58

Hello Everyone!

I had been trying to get the password for esadminĀ reset on the HCM PI 34, but without much luck. This post from psadmin.io and lot of help from the Oracle Support forums came in very handy – I was able to reset the passwords using the PSCipher utility, however, I couldn’t get the change to take effect.

This all started when I tried accessing port 9200 on my HCM image – http://hcm92.ps.com:9200/

I got this error when attempting some random passwords(esadmin being the most likely) šŸ™‚

{“error”:{“root_cause”:[{“type”:”orcl_auth_plugin_exception”,”reason”:”Invalid user/password”}],”type”:”orcl_auth_plugin_exception”,”reason”:”Invalid user/password”},”status”:401}

Couple of Oracle Support notes provided steps to add a new user(say, esadmin1) and provide full access access to be the same as esadmin. I wanted to see if there was a workaround that we could use, to get this resolved. Here are the steps:

  • Login to the App Server using Putty
  • Execute the following command

[root@hcm92 piabin]$ sudo -s su psadm2

  • Navigate to the piabin directory on your Web Server (if you use PI 34 like me, it would be /home/psadm2/psft/pt/8.58/webserv/peoplesoft/piabin)

[psadm2@hcm92 piabin]$ cd /home/psadm2/psft/pt/8.58/webserv/peoplesoft/piabin

  • Next, execute the following command using the PSCipher Utility

[psadm2@hcm92 piabin]$ ./PSCipher.sh esadmin2web

  • where, esadmin2webĀ is the new password that you intend to use forĀ esadmin
  • Upon execution, your result would be something like this:

[psadm2@hcm92 piabin]$ ./PSCipher.sh esadmin2web
Encrypted text: {V2.1}lR4fYCnZEXWiK9x8dlGXKNLOPPTUtWPo

  • Note the content in bold, provided againstĀ Encrypted text
  • Navigate to ES_HOME/pt/elasticsearch7.0.0/plugins/orcl-security-plugin/config/properties on the App Server – it would be easier to access and edit the file via WinSCP or a text editor
    • The full path in my case was /opt/oracle/psft/pt/ES/pt/elasticsearch7.0.0/plugins/orcl-security-plugin/config/properties
  • Open the esusers.ymlĀ file available in this directorySS-01
  • Replace the password against esadmin in this file with the encrypted textĀ from the steps listed above(generated using the PSCipher utility)
  • Restart ElasticSearch
    • If a version of ElasticSearch is already running, execute the following command

[root@hcm92 bin]$ sudo -s su esadm1

[esadm1@hcm92 bin]$ ps -ef | grep elas

    • The first value available in the results would be theĀ process ID(pid)
    • Terminate it using the following command:

[esadm1@hcm92 bin]$ kill pid

  • Navigate to the ElasticSearch bin directory and issue the following command on HCM PI 34:

[esadm1@hcm92 bin]$ cd /opt/oracle/psft/pt/ES/pt/elasticsearch7.0.0/bin

[esadm1@hcm92 bin]$ nohup ./elasticsearch &

  • The last command(upon pressing Enter) will continue to run in the background and you can press the Enter key again to return to the prompt
  • If you’ve been successful until now, great job! šŸ™‚ – there are two more steps remaining
    • Navigate toĀ PeopleTools > Search Framework > Administration > Search InstanceĀ and update the password for theĀ esadmin user

SS-01

    • Navigate to PeopleTools > Search Framework > Administration > Monitoring Server > Configure Server tab and update the password for theĀ esadminĀ username
      • You can either update it manually or run the script provided in this post

SS-02

  • Access the ElasticSearch page on your browser (http://hcm92.ps.com:9200/)
    • Provide username asĀ esadminĀ and the new password(that you have reset)
    • You should be able to see something like this:

SS-03

  • Try doing a Global Search and it should work fine – in my case, it did not return any search results. I usually search for Kibana from the global search results – I presume that the search index file wasn’t created or was broken. This was resolved by running the PTSF_GENFEEDĀ process for run control PTPORTALREGISTRY_FULL.

Hope this helps!

Happy Reading! šŸ™‚

Posted in Oracle, PeopleSoft, Software, Virtualization | Tagged , , , , , , , | Leave a comment

Resolving “PTCDPK-50008: odcdeploy:Oracle client cloning failed” Error : PeopleTools 8.58

If you’ve had a PeopleTools client installed on your PC with an earlier VirtualBox installation, just deleting the PT8.xx.xx_Client_ORA and c:\oracle folders won’t suffice, as references to the earlier Oracle installations are set elsewhere. If you run the SetupPTClient.bat file, it’ll fail with the following error:

ODCDeploy.py ERROR : PTCDPK-50008: odcdeploy:Oracle client cloning failed

If you’ve setup VirtualBox installations like me, you can clean them up with the following steps:

Using the Registry Editor:

  • Ensure you have admin access to the PC
  • Use the run prompt(Windows Key + R) and typeĀ regedit
  • Once theĀ Registry EditorĀ window appears, navigate to the following key :Ā Computer > HKEY_LOCAL_MACHINE > SOFTWARE > Oracle > KEY_OraClient12Home2

SS-01

  • Right click on KEY_OraClient12Home2 and selectĀ Delete
  • When the following dialog appears, clickĀ Yes

SS-02

  • Exit Registry Editor

Removing the Oracle Inventory File:

  • Assuming your earlier PeopleTools client installation was in theĀ C drive, open this folder : C:\Program Files\Oracle\Inventory\ContentsXML
  • Here, you’d have three files listed:
    • comps.xml
    • inventory.xml
    • libs.xml
  • If you open up theĀ inventory.xml file, you’ll notice that it contains references to previous Oracle Client installations
  • Delete theĀ inventory.xmlĀ file from C:\Program Files\Oracle\Inventory\ContentsXML and start executing the SetupPTClient.batĀ again – this time, the installation will continue without any issues

Hope this helps!

Have fun! šŸ™‚

Posted in Oracle, PeopleSoft, Personal, SQL | Tagged , , , , , | Leave a comment

PeopleSoft 9.2 – PeopleTools 8.58 VirtualBox Installation – ElasticSearch

Link to the main post.

We’re almost there!

HCM PI 34 bundles ElasticSearch and Kibana. On Linux, both these directories are available under /opt/oracle/psft/pt/ES/pt.

Sasank’s posts provide a lot of detail about setting up ElasticSearch and Kibana, if they haven’t been started.

  • You can verify if ElasticSearch is up and running by logging into PeopleSoft and performing a global search

SS-32

  • You should be able to see search results as below

SS-33

  • You can also use the Diagnostics Utility to check if ElasticSearch is up and running – from PeopleTools > Search Framework > Utilities > Diagnostics

SS-34

  • Alternatively, you can follow instructions provided in Sasank’s post as well
  • If neither of these work, navigate to the ElasticSearchĀ bin folder and start up and instance of elasticsearch

[root@hcm92 bin]# cd /opt/oracle/psft/pt/ES/pt/elasticsearch7.0.0/bin

  • Against the prompt, switch to the esadm1 user, type nohup ./elasticsearch &Ā and press Enter

[root@hcm92 bin]# sudo -s su esadm1

[esadm1@hcm92 bin]# nohup ./elasticsearch &

  • After few seconds, press the Enter key to return to the command prompt
  • Execute the following commands to verify ElasticSearch is up and running
    • If there are errors, we’d have to troubleshoot – but if the file size does not grow any longer, check for a message that states that “colour was changed from red to yellow” to indicate the service’s status

[root@hcm92 bin]# cat nohup.out | tail -10

    • Execute the following command – you should be able to see a large output that indicates ElasticSearch is up and running

[root@hcm92 bin]# ps -ef | grep elas

If it is all good, return to global search and ensure you can see results.

Posted in Oracle, PeopleSoft, Software | Tagged , , , , | Leave a comment

PeopleSoft 9.2 – PeopleTools 8.58 : Error while Deploying Kibana Visualizations

I expected Kibana to work out of the box for HCM PI 34 – for some reason, I wasn’t able to get the dashboards and visualizations up and running.

If you’re receiving a blank page while accessing the dashboards in Kibana, look no further šŸ™‚

The error message that I received while trying to Deploy Visualizations was like this:

Integration Gateway – External System Contact Error

PTSF_ES_STATWRK.PTSF_ES_STAT_SAVE.FieldFormula Name:DeployVisualization PCPC:9793 Statement:109

Called from:PTSF_ES_STATWRK.PTSF_KIBANA_DEPLOY.FieldChange Statement:1

Integration Gateway was not able to contact the external system. The network location specified may be incorrect, or the site is permanently or temporarily down

SS-37

The first step is to check details provided in theĀ Configure ServerĀ tab (from PeopleTools > Search Framework > Administration > Monitoring Server) are correct – in my case, none of the fields from the screenshot below were populated.

SS-40

You can copy the values from PeopleTools > Search Framework > Administration > Search Instance > PTSF_DEFAULT. No problems if you don’t know the password forĀ esadmin (I believe it is setup as part of the bootstrap script) – you can provide some password temporarily and then, execute the following SQL script via SQL developer or Data Mover to sync the actual passwords(as a workaround).

 

UPDATE PS_PTSF_ES_STATDTL SET PTSF_ADMIN_PASSWD = (SELECT PTSF_ADMIN_PASSWD FROM PS_PTSF_SRCH_NODES);

You can now proceed with deploying the Visualizations and it’ll work like a charm!

Hope this helps! šŸ™‚

Posted in Code, Oracle, PeopleSoft, SQL | Tagged , , , , , | Leave a comment

PeopleSoft 9.2 – PeopleTools 8.58 VirtualBox Installation – Kibana

Link to the main post

I’ve seen a lot of posts where people have had Kibana up and running, out of the (virtual)box from HCM PI 34. I had issues getting the dashboards and visualizations to work. Many thanks to folks from Oracle who helped me resolve this issue.

  • The Kibana homepage can be accessed from here : http://hcm92.ps.com:5601/
  • You’d have to replaceĀ hcm92.ps.com with your hostname, whereas 5601 is the default port for Kibana
  • When you login to this URL for the first time, it would appear as below
    • Enter the username asĀ PS
    • Enter the appropriate password
    • Enter the Oracle database name – in this case HR92U034

SS-35

  • The dashboards are usually empty until you deploy them
  • For me, it looked like this – even with a completely fresh install

SS-35

  • Kibana was up and running, but of no avail. In case you get an error while accessing the Kibana URL, you can execute the following commands.

[root@hcm92 bin]#cd /opt/oracle/psft/pt/ES/pt/Kibana7.0.0/bin

[root@hcm92 bin]# nohup ./kibana &

  • The next steps were to deploy Kibana dashboards and visualizations
  • To do that, navigate toĀ PeopleTools > Search Framework > Administration > Monitoring Server > Monitoring VisualizationsĀ tab
    • Select all dashboards and click on Deploy Visualizations
    • If there were no errors deploying these visualizations, you’d get a message stating so
    • If you received errors, check this post

SS-36

  • Next, deploy dashboards fromĀ PeopleTools > Search Framework > Administration > Deploy Kibana Dashboards

SS-37

  • If all goes well, navigate to theĀ RecruitingĀ component and ensure you’re able to seeĀ visualizationsĀ as below

SS-38SS-39

That brings us to the end of these series of posts on setting up PeopleSoft 9.2 with PeopleTools 8.58.03. Feel free to add your questions and I’ll try to answer them as much as I can! šŸ™‚

Have fun! šŸ™‚

 

 

 

Posted in Oracle, PeopleSoft, Software | Tagged , , , , , , , , , , , | Leave a comment

PeopleSoft 9.2 – PeopleTools 8.58 VirtualBox Installation – SQL Developer & Putty

Link to the main post

If you’ve installed the Oracle Client successfully, you can get SQL Developer up and running in no time.

  • Click on SQL Developer from the Start menu

SS-26

  • Once you get the following window, click on theĀ New Connection button

SS-27

  • In the window that opens, provide the following details:
    • Connection Name of your choice – say, HR92U034 (does not have to be the same name as your database)
    • Username as SYSADM
    • Password to be the same as the one you had provided during the initial installation
    • Select the Save PasswordĀ checkbox
    • Change Connection Type to TNS
    • Select your database name from the Network Alias dropdown
      • If this doesn’t appear, ensure you’ve copied the tnsnames.ora file to the required directory

SS-28

    • Click on Save
    • Click on Test – ensure there are no errors
    • Click on Connect
    • The SQL editor would appear as below – run a SQL against a table to verify you’re able to run queriesSS-29

To access the Linux command prompt via Putty, download and install the application from here.

  • Click on Putty from the Start Menu
  • In the window that appears, provide your virtual machine’s IP address

SS-30

  • Click onĀ Open
  • When the prompt appears, provide the username asĀ rootĀ and the appropriate password

SS-31

That brings us to the end of setting up our environment – almost! The next post would deal with setting up ElasticSearch and Kibana.

Posted in Oracle, PeopleSoft, SQL | Tagged , , , , | Leave a comment

PeopleSoft 9.2 – PeopleTools 8.58 VirtualBox Installation – PeopleTools Installation

Link to the main post

So, if you’ve come this far, you should be able to access the PeopleSoft home page without any issues šŸ™‚

In this post, let us look at installing PeopleTools. First, you’d have to access the files required for the PeopleTools installation.

These are available on aĀ Samba Network Share. You can access them by providing your virtual machine’s IP address. In this case, the IP address is 192.168.1.116.

If you’re on an earlier version of Windows 10, you should be able to access the Samba share without any issues by accessing it via the run prompt:

SS-12

But with newer versions of Windows 10, you’re more likely to get the following prompt to enter your computer’s user name and password:

SS-11

Regardless of what you enter against the username and password fields, it is likely that you get the message “the user name or password is incorrect“. There are various options out there from “Turn On Network Discovery” to “Turning Off Password Authentication for Network Shares” and “Editing the Registry”. Unfortunately, none of them seem to work. If you know of a way to get it working, please leave a comment and I’ll include it in this post.

So, what can you do now to access the shares? There’s an alternative. You can access the files via WinSCP by connecting to the Linux server.

Download and install WinSCP from here. Once installed, access the application and follow the steps provided below:

  • Click on theĀ New SessionĀ button

SS-13

  • In the window that opens, click onĀ New Site, enter the Linux Host name, username asĀ root and password for theĀ root user : click on Login once done

SS-14

  • You’d get the following message – click onĀ Yes

SS-15

  • The right pane of your WinSCP window will now look like this

SS-16

  • PressĀ Ctrl + OĀ and paste this path /opt/oracle/psft/pt/tools_client
  • The directory and its contents would look like this

SS-17

  • You can copy these folders to your PC which is on the left pane of WinSCP, by dragging and dropping them into a folder of your choice(on your PC)
  • Open a new cmd session in Administrator mode and navigate to the tools_client folder

C:\Users\MANIKANDAN>cd tools_client

Your prompt should now look like this:

C:\Users\MANIKANDAN\tools_client>

  • Type SetupPTClient.batĀ and press enter
  • Once the batch script starts executing, you’ll start getting the following messages along with the Oracle Client installation – type N for the first prompt, if you’re setting it up on your PC. The rest is all automatic:

SS-19

If the installation goes through without any issues, your prompt would look like this

SS-20

So far so good! Now lets get the Application Designer and other 2-tier tools installed.

  • If installation completed without any issues, your PT client will be available against C:\PT8.58.03_Client_ORA
  • Open theĀ PS Configuration Manager [pscfg] from C:\PT8.58.03_Client_ORA\bin\client\winx86
  • It looks like this:SS-21
  • Double-click on the pscfg file
  • Provide the database name as configured, User ID as “PS” or as configured, connect ID asĀ people and the password that you had provided during the initial setup forĀ peopleSS-22
  • Click on the Client SetupĀ tab and select all options as displayed below, click onĀ ApplyĀ and then OK

SS-23

  • From yourĀ tools_clientĀ folder, now copy theĀ tnsnames.oraĀ file and paste it under theĀ networkĀ folder in yourĀ Oracle HomeĀ directory
    • In this case, from C:\Users\MANIKANDAN\tools_clientĀ to C:\oracle\product\12.1.0\client_1\network\admin or C:\oracle\product\12.1.0\client_2\network\admin
  • Access Application Designer from the Start Menu

SS-24

  • In the window that appears, database and username should be pre-populated – enter the password

SS-25

  • If this is the first time that you’re accessing Application Designer, it would take a while – it is worth the wait! šŸ˜‰
  • The App Designer window looks like this:

SS-26

That brings us to the end of this post. Let’s look at querying the database(using SQL developer) and setting up Putty in the next post.

 

 

Posted in Oracle, PeopleSoft, PeopleSoft HCM, Software | Tagged , , , , | 2 Comments

PeopleSoft 9.2 – PeopleTools 8.58 VirtualBox Installation – Creating the VM Shell File

Link to the main post

Once you’ve pressed the enter key from the Part-1, you’ll start seeing the following on the command prompt:

Starting the PeopleSoft Environment Setup Process:

Validating User Arguments: [ OK ]
Validating PeopleSoft Supported Platform: [ OK ]

Extracting the Zip File HCM-920-UPD-034-OVA_10of13.zip: [ OK ]
Extracting the Zip File HCM-920-UPD-034-OVA_11of13.zip: [ OK ]
Extracting the Zip File HCM-920-UPD-034-OVA_12of13.zip: [ OK ]
Extracting the Zip File HCM-920-UPD-034-OVA_13of13.zip: [ OK ]
Extracting the Zip File HCM-920-UPD-034-OVA_2of13.zip: [ OK ]
Extracting the Zip File HCM-920-UPD-034-OVA_3of13.zip: [ OK ]
Extracting the Zip File HCM-920-UPD-034-OVA_4of13.zip: [ OK ]
Extracting the Zip File HCM-920-UPD-034-OVA_5of13.zip: [ OK ]
Extracting the Zip File HCM-920-UPD-034-OVA_6of13.zip: [ OK ]
Extracting the Zip File HCM-920-UPD-034-OVA_7of13.zip: [ OK ]
Extracting the Zip File HCM-920-UPD-034-OVA_8of13.zip: [ OK ]
Extracting the Zip File HCM-920-UPD-034-OVA_9of13.zip: [ OK ]

Checking if the VirtualBox Software is Installed on the Windows Host: [ OK ]
Checking if the VirtualBox Default Machine Folder has Enough Free Spac[ OK ]

At this point in time, if your script fails stating that the VirtualBox Default Machine folder doesn’t have enough space, follow the steps provided below:

  1. Ensure you have at least 150 GB of free space in the drive of your choice(you should have started the installation on the same drive)
  2. OpenĀ VirtualBox, navigate to File > Preferences
  3. On theĀ GeneralĀ tab, you’d have an option to change/set the default machine folder – choose a folder within the drive in which you’ve started the installation

SS-04

Start running the .bat file again.

Checking if a PeopleSoft Appliance (OVA) is Available to Import: [ OK ]

Found a PeopleSoft VirtualBox appliance [VBOX_8.58.03_SHELL.ova]
in the DPK source folder [D:\DPK_INSTALL].
We can automate the process of importing this appliance
into the VirtualBox Manager on the Windows Host.

Do you want to import the OVA into the VirtualBox Manager? [Y|n]: Y

Checking if the PeopleSoft Appliance (OVA) is already imported: [ OK ]
Importing the PeopleSoft Appliance (OVA) into the VirtualBox Manager: [ OK ]

Choose optionĀ 2 – Bridged Network Adapter, if you’d like the PeopleSoft instance to be available on your mobile phone. Here are the instructions to access your instance on your phone.

The Network Adapter lets the VM be available either in a Sand-Box mode or
accessible to other hosts in the local network.

1. Host-Only Network Adapter
2. Bridged Network Adapter
Enter 1 or 2: 2

Getting the Bridged Network Adapter Name from the VirtualBox Manager: [ OK ]
Setting up Bridged Network Adapter for the VM: [ OK ]
Setting up the Shared Folder [D:\DPK_INSTALL] on the VM: [ OK ]

Starting the VirtualBox Manager on the Windows Host: [ OK ]
Starting the Imported PeopleSoft Appliance VM: [ OK ]

The PeopleSoft Appliance (OVA) is successfully imported into the VirtualBox
Manager and the new VM is started successfully. Please use the VM’s console
to continue with the PeopleSoft initializating process.

The PeopleSoft Environment Setup Process Ended.

D:\DPK_INSTALL\setup>

Post this, a new instance of VirtualBox would open to continue with the installation.

  • You should be able to see the following screen that prompts you to enter the password for theĀ rootĀ userĀ  – enter it twice and please note it down. You’ll require this once installation is completed:VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_09_53_08
  • Ā  The next question checks if you’d like to enable DHCP (go withĀ Y to avoid any manual configuration) – press enter and let the installation continue without any manual intervention
  • When prompted to enter the host name, enterĀ hcm92.ps.com

VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_09_53_52

VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_09_54_06

  • Enter theĀ PeopleSoft InstallationĀ type asĀ FRESH

VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_09_54_25

  • ChooseĀ Y for Multi Language support if rquired, else set it toĀ N

VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_09_54_37

  • You can either retain the default values for the database name or enter a database name of choice
  • Enter the password for the PeopleSoft database admin users
    • The password needs to satisfy complexity requirements : An uppercase character, a lowercase one, a number and a special character(like an hyphen – not all special characters are allowed in the password)
  • Enter theĀ PeopleSoft database ConnectĀ ID – default isĀ people

VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_09_54_49

  • Enter the password forĀ peopleĀ [alpha-numeric]
  • Enter the password for SYSADM [alpha-numeric]
  • Enter the password forĀ PS [alpha-numeric]
  • Enter the password for WebLogic Server Admin user – follow the complexity requirements displayed on the screen
  • Enter the password for the PeopleSoft WebProfileĀ user
  • The defaultĀ PeopleSoft Integration GatewayĀ user isĀ administrator – you can use the same or create a new one
  • Set the password for theĀ administratorĀ user

VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_09_54_58

  • EnterĀ Y if you’re happy with the passwords that you’ve provided:

VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_09_55_06

  • Installation continues without any manual intervention – took about 3-4 hours on my PC (best to leave it overnight for the installation to complete) šŸ™‚
  • VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_09_59_13VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_10_07_07VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_10_07_35
  • If all goes well, you’d get the following screen – prompting you to enter the username asĀ root and password that you had setup at the beginning of this postVirtualBox_VBOX_8.58.03_SHELL_12_06_2020_10_08_27
  • To identify the IP address associated with the image, typeĀ ifconfigĀ in the command prompt

VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_10_23_05

  • In this case, the IP address is the value available againstĀ theĀ inetĀ field
  • Note down this IP address as you’d be using this IP address to access the PeopleSoft image page
  • To access the PeopleSoft home page, you’d have to make the following changes:
    • In your Windows Host, access c:\Windows\System32\Drivers\etc\
    • Open the hostsĀ file from the files listed
    • Add an entry with theĀ IP AddressĀ andĀ host name (that you had provided during the installation) of your PUM image

SS-06

  • So, if your IP address is, say, 192.168.1.103 and host name is hcmi34.ps.com, theĀ hostsĀ file entry should look like:

192.168.1.103 hcmi34.ps.com

SS-07

  • In case your IP address changes during the installation, you’d have to update in the hosts file
  • In case, there are issues accessing the PeopleSoft home page, you’d have to edit it on the Linux Server as well
    • On the command prompt, enter cd ../
    • TypeĀ vi /etc/hosts
    • You can press the DeleteĀ key to change the IP address
    • Press theĀ I key to change the mode toĀ Insert
    • Enter the new IP address
    • Once all done, pressĀ EscĀ key+Ā :Ā +Ā wq +Ā Enter Key

VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_14_00_54VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_14_03_31VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_14_03_39VirtualBox_VBOX_8.58.03_SHELL_12_06_2020_14_03_47

  • Access the PeopleSoft home page using this URL : http://hcm92.ps.com:8000/ps/signon.html
  • You’d have to replaceĀ hcm92.ps.com with the host name that you had provided during the course of the installation
  • If all good, your home page would look like this – enter the username asĀ PS and password that you had provided during the setup

SS-08SS-09SS-10

So, that’s the end of this post – hope this helps! šŸ™‚

Lets move on to Part-3!

Posted in Oracle, PeopleSoft, PeopleSoft HCM, Software, Virtualization | Tagged , , , | 4 Comments