PeopleSoft ElasticSearch 2.3.2

Oracle PeopleSoft have released Elastic Search which can be configured with PeopleSoft Search Framework with PeopleTools 8.55.11 and higher patch levels.

For ElasticSearch to deploy in your environment, You need to be on PeopleTools 8.55.11 or higher patch level. The Elasticsearch integration is supported for PeopleSoft 9.2 applications on PeopleSoft PeopleTools 8.55.11 or higher patch level ONLY.

PeopleTools 8.55.11 supports search engine Elasticsearch 2.3.2 with full integration with the PeopleSoft Search Framework.

With the release of ElasticSearch, Oracle Secure Enterprise Search will be supported for eighteen months, until April 30, 2018.

Elastic Search DPKs is available on e-delivery cloud and from the MOS under specific patchset number defined below

Patch No 24924150 ElasticSearch 2.3.2 DPK for Windows

Patch No 24924136 ElasticSearch 2.3.2 DPK for Linux.

I am working on collating more details on Elastic Search and will keep posting all details on the blog.

Watch this space.

  

Deploying PeopleTools Client on local desktop from the PeopleSoft Update Image installed on Windows VM

PeopleSoft latest image installed on the Virtual machine includes a client installer for setting up PeopleTools client tools such as Change Assistant, Configuration Manager, and Application Designer and an Oracle database client.

You can use the PeopleTools client( from tools_client folder) on the Virtual machine to install the standalone client on your local desktop on the network.

For standalone Tools Client installation on the local desktop, I assume that:

1. You have all required PeopleSoft DPKs in the DPK_INSTALL on the microsoft windows computer where you have install PeopleSoft Update Image.

2. You completed the setup of the PeopleSoft Image on the Virtual Machine and that has created the PI Home and Other required folders.

Once we get the confirmation on the above points,
Map you static IP which you have assigned to your image from your local desktop. For example if you static ip is \\116.121.23.41 then this IP should be accessible on the network and from your local desktop.
Once mapped the static ip, open windows power shell with administrater previliges and change the drive to the mapped drive. In my case it is as given below.

Navigate to tools_client and look for SetupPTClient.bat.

Execute SetupPTClient.bat with the option as below. SetupPTClient.bat is the interactive script that installs the PeopleSoft PeopleTools components including Oracle Client and Application Designer.

Once installed copy the tnsnames.ora from tools_client and copy it to C:\oracle\product\12.1.0\client_1\network\admin

PS V:\> .\SetupPTClient.bat -l

****** SetupPTClient started at 11:38:44.94 ******

This script will guide you through the deployment of PeopleTools Client components for your environment.

Is this deployment for a Update Manager Environment?
(A 'Y' will prompt you to setup a Target PeopleTools client deployment in
addition to the Source PeopleTools client.)
[Y/N]: N

Starting Tools Client Deployment!

Validating compatible Oracle DB Client for Source PeopleTools 8.55.07

Deploying Oracle DB Client for PTools Version - 8.55.07
Deploying Source PeopleTools 8.55.07 Client in C:\PT8.55.07_Client_ORA
Installing Change Assistant for PeopleTools 8.55.07 Client in C:\Program Files\PeopleSoft\Change Assistant The system cannot find the file specified.
'/s' is not recognized as an internal or external command, operable program or batch file.
Deployment of PeopleTools Client and installation of Change Assistant Complete.
Tools Client Deployment Ended.
"****** SetupPTClient ended at 11:53:39.72 ******"

Open pscfg.exe and configure the connect ID.
Open application designer from C:\PT8.55.07_Client_ORA\bin\client\winx86(from your local desktop) and login with your login credentials.

Process Scheduler starting Slow on Windows 2012 R2

We recently have upgraded to PeopleTools 8.55.05 and along with this we have upgraded our infrastructure also. For windows batch server, we have upgraded our infrastructure from windows 2008 R2 to Windows 2012 R2.

After installing new Tools version (PeopleTools 8.55.05) on windows 2012 R2 , we noticed performance issue while booting up the batch server. On windos 2012, each server process is taking approx 50-60 seconds to boot up and in turn the complete batch server is booting up in approximately 10 minutes. Before upgrade, we were on Tools 8.53 with windows 2008 and batch server boot up process was quite fast and as per the expectation.

As a part of our analysis we did a packet capture(using wireshark) and noticed a lot of NB (NetBios name resolution) and LLMNR (Link-Local Multicast Name Resolution) packets, which appeared to be slowing things down for the process scheduler processes.

For the box where the scheduler is booting up slow, we have noticed that prior to LDAP query there are series of DNS, NB and LLMNR queries to resolve the database name. However, on windows 2008 R2 , it just gets straight into the LDAP Query.

To force the scheduler process to directly go into the LDAP query, we have made the following changes:

  - Disabled "Link-Layer Topology Discovery Mapper I/O Driver" interface

  - Disabled "Link-Layer Topology Discovery Responder" interface

  - Disabled "Internet Protocol Version 6" interface

  - Disabled NetBIOS over TCP/IP

  - Disabled LLMNR by setting Local Computer Policy -> Computer Configuration -> Administrative Templates -> Network -> DNS Client -> Turn Off Multicast Name Resolution = Enabled

This has worked for us and we are able to boot up batch server fast on windows 2012 R2, however, having said this, we are still trying to understand why the process scheduler of Tools 8.55 is querying DNS, NB and LLMNR before LDAP query.

We are not sure if there is any change in the way process scheduler is going to communicate with underlying Operating System with PeopleTools 8.55.

If any of you have any idea on this, please let me know. I will happy to listen and discuss on the issue with you.

Clean Up DPK Deployed PeopleSoft environment

To remove the DPK deployed PeopleSoft environment follow the steps below

For Windows server we need to execute the command as below:

./psft-dpk-setup.ps1 -cleanup

For Linux based server or any other flavour of unix the command is:

./psft-dpk-setup.sh --cleanup


I have seen in my scenario where the above given Manual method of cleanup was failing and not clearing all the files on the server. This was happening due to the space in the folder or having some folders with large name.In one of the case, I have seen re-installation was failing because one folder was not cleared in the cleanup process and that folder was having a large directory name.In case if the automated method of cleaning is failing then an alternate way to 'cleanup' is to manually remove the existing installation:

- Locate the default.yaml file in /etc/Puppet/data on Linux platforms and in

C:\ProgramData\PuppetLabs\Puppet\etc\data on Microsoft Windows platforms.

- Change the ensure value in default.yaml from 'present' to 'absent'

- Change directory to this location /etc/puppet/manifests on Linux platforms and

C:\programdata\puppetlabs\puppet\etc\manifests on Microsoft Windows platform

And finally execute the command below

- Run puppet apply site.pp --debug –trace

This will remove the existing installation from the server.

Leave your comment on the topic.

PeopleSoft Customization yaml file

After deployment of DPK, I was trying to execute the psft_customizations.yaml using the non-root user i.e, the specific user which we normally use for installing the PeopleSoft Stack components. I was using user_name and group_name twice in the psft_customizations.yaml which was causing it to fail. That is for oracle_group and psft_group, I was using the same group profile and similarly for psft_user and oracle_user, I was using the same userid. Puppet don't allow you to give same group name(profile) and same user_name twice in the customization file. As a workaround for this issue, I have removed the user section from psft_customizations.yaml and ran it with default users i.e, psadm1, psadm2, psadm3 and Oracle. You can then give the permission to these users to execute as per your setup requirement or alternatively you can change the ownership of the installation done by these default users. You can only get these default users created on your system, if you have the super user access to the box where you are attempting to install DPK and PeopleSoft components.
As a solution to this,if you are intending to use one user name and user group for both PeopleSoft and Oracle installation then you can give that username and group name once at the top of the file psft_customizations.yaml and that should not be repeated for PeopleSoft and Oracle separately in the file.
For example: The section below should be in the top of the file with other content

psft_user_name: hr92ut

psft_group_name: psadmin_prd

Hope this will help you to resolve the user profile issue in psft_customizations.yaml file where you are intending to use the signle user to use for the entire installation using DPK, however if you face any issue, pls leave a comment or email me and I will respond at the earliest possible.

Giving Custom Name to the Image in Oracle Virtual Box

Users can give the custom name for the image running in Oracle Virtual Box. This can be achieved by the following defined method

1. When we import the ova file in the virtual box, at that time, double click the name for the importing image in the configuration column and change it to your cutomized name.

2. If you imported it with the default name, then in the later stage, when the image is powered off, right click in the virtual box and click setting. In the setting , change the name field and hit enter.

PeopleTools DPK Installation- Important Commands

Oracle PeopleSoft provide the commands which are available for PeopleSoft Deployment Package.

DPK provides the flexibility to install domains separately on different physical and logical machines.

Following DPK commands could be execute in Windows Powershell and Unix/Linux boxes

DPK provide the option to specify default option also as

domain_type (the default is all) : domain_type all

1. For App Server domain

--env_type midtier --domain_type appserver

2. For App Batch Domain (for App Server & Process Scheduler on on one machine)

--env_type midtier --domain_type appbatch

3. For PIA Domain

--env_type midtier --domain_type pia

4. For a Process Scheduler Domain

--env_type midtier --domain_type prcs

5. This command setups a fulltier (database and midtier) PeopleSoft environment using the DPK zips from the directory /opt/psft/dpks.

--dpk_src_dir /opt/psft/dpks

7. This command deploys just the PS_HOME. It does not setup any PeopleSoft environment. Just installs PS_HOME and none of the other 3rd party components.

--env_type midtier --deploy_only --deploy_type tools_home

Applying customizations for deployment ONLY through puppet failing with the error

After I created the psft_customizations.yaml and executed the command puppet apply site.pp --debug --trace under manifests, it was failing with the errors as below. I was intending to apply the deployment customization in the peoplesoft application and was looking to use the user profile for deployment as delivered default i.e, psadm1,psadm2,psadm3 and oracle2.

From the error message, I analysed that puppet script is unable to create the user profile folders in the home directory i.e,

/home/psadm1
/home/psadm2
/home/psadm3
/home/oracle2

Error: Could not set 'present' on ensure: No such file or directory - /home/psadm2/.profile at 59:/etc/puppet/modules/pt_profile/manifests/pt_system/users.pp
/usr/share/ruby/vendor_ruby/puppet/type/file.rb:812:in `initialize'
/usr/share/ruby/vendor_ruby/puppet/type/file.rb:812:in `open'

/usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:146:in `run'

/usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:92:in `execute'

/usr/bin/puppet:8:in `<main>'

Wrapped exception:

No such file or directory - /home/psadm2/.profile

/usr/s

Error: /Stage[main]/Pt_profile::Pt_system::Users/File[/home/psadm2/.profile]/ensure: change from absent to present failed: Could not set 'present' on ensure: No such file or directory - /home/psadm2/.profile at 59:/etc/puppet/modules/pt_profile/manifests/pt_system/users.pp

Notice: /Stage[main]/Pt_profile::Pt_system::Users/Exec[chage -d 0 psadm2]: Dependency File[/home/psadm2/.profile] has failures: true

Warning: /Stage[main]/Pt_profile::Pt_system::Users/Exec[chage -d 0 psadm2]: Skipping because of failed dependencies

Error: /Stage[main]/Pt_profile::Pt_system::Users/File[/home/psadm3/.profile]/ensure: change from absent to present failed: Could not set 'present' on ensure: No such file or directory - /home/psadm3/.profile at 59:/etc/puppet/modules/pt_profile/manifests/pt_system/users.pp

Notice: /Stage[main]/Pt_profile::Pt_system::Users/Exec[chage -d 0 psadm3]: Dependency File[/home/psadm3/.profile] has failures: true

Warning: /Stage[main]/Pt_profile::Pt_system::Users/Exec[chage -d 0 psadm3]: Skipping because of failed dependencies

Error: Could not set 'present' on ensure: No such file or directory - /home/oracle2/.profile at 59:/etc/puppet/modules/pt_profile/manifests/pt_system/users.pp

/usr/share/ruby/vendor_ruby/puppet/type/file.rb:812:in `initialize'

Error: Could not set 'present' on ensure: No such file or directory - /home/oracle2/.profile at 59:/etc/puppet/modules/pt_profile/manifests/pt_system/users.pp

/usr/share/ruby/vendor_ruby/puppet/type/file.rb:812:in `initialize'

Error: /Stage[main]/Pt_profile::Pt_system::Users/File[/home/oracle2/.profile]/ensure: change from absent to present failed: Could not set 'present' on ensure: No such file or directory - /home/oracle2/.profile at 59:/etc/puppet/modules/pt_profile/manifests/pt_system/users.pp

Notice: /Stage[main]/Pt_profile::Pt_system::Users/Exec[chage -d 0 oracle2]: Dependency File[/home/oracle2/.profile] has failures: true

Warning: /Stage[main]/Pt_profile::Pt_system::Users/Exec[chage -d 0 oracle2]: Skipping because of failed dependencies

Warning: /Stage[main]/Pt_profile::Pt_tools_deployment/Notify[Applying pt_profile::pt_tools_deployment]: Skipping because of failed dependencies

Warning: /Stage[main]/Pt_setup::Tools_deployment/File[/home/fs91dev/ps_home8.55.05]: Skipping because of failed dependencies

Warning: /Stage[main]/Pt_profile::Pt_psft_environment/Pt_setup::User_environment[oracle2_environment]/File[oracle2_environment]: Skipping because of failed dependencies

Warning: /Stage[main]/Pt_profile::Pt_psft_environment/Pt_setup::User_environment[psadm2_environment]/File[psadm2_environment]: Skipping because of failed dependencies

Solution

As a solution to the issue, I have created the user profile folders manually in the home directory using the root linux user(note that I am installing PeopleSoft PeopleTools using the root user). 

mkdir psadm1 psadm2 psadm3 oracle2

drwxr-xr-x.  2 root      root           6 May 23 15:16 psadm1

drwxr-xr-x.  2 root      root           6 May 23 15:16 psadm2

drwxr-xr-x.  2 root      root           6 May 23 15:16 psadm3

drwxr-xr-x.  2 root      root           6 May 23 15:16 oracle2

Once done, I navigated to /etc/puppet/manifests and executed the command 

 puppet apply site.pp --debug --trace

This deployed the customized components in the server.

Ensure to change the permission and owner post deploying the tools and components.

You can also delete the user folders created above manually once the deployment is completed.

PSACCESSPROFILE Table in PT8.55

PSACCESSPROFILE 

In PT8.55 a new table PSACCESSPROFILE has been created with new longer fields. This new table PSACCESSPROFILE was replaced the table PSACCESSPRFL.

Structure/Column in PSACCESSPROFILE table

ColumnName

ENCRYPTED

STM_ACCESS_ID

STM_ACCESS_PART1

STM_ACCESS_PART2

STM_ACCESS_PSWD

STM_ENCRYPTION_VER

SYMBOLICID

VERSION

PeopleTools client installation When Running SetupPTClient.bat is failing with the error as The application has failed to start because"..

Attempt to install the client by running SetupPTClient.bat for PT 8.55.01 client is failing with the error as

"The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail"

Analyzing the issue revealed that this is happening because computer does not include the necessary Microsoft C++ runtime libraries which are required for installation of the client using the DPK.

As a solution for this

1. Uninstall all current all current Microsoft Visual C++ installations by going to Control Panel and with in the list of programs locate locate the Microsoft Visual C++ entries and uninstall all in a row.

2. Reinstall new Microsoft Visual C++ packages

You can get all the packages from the link below

https://www.microsoft.com/en-us/download/search.aspx?q=redistributable+package

Latest release date of the package

Visual C++ Redistributable Packages for Visual Studio 2013 is 30th Dec 2014.

You need to check all the packages available and click each of the following links in order to install all. Choose to Run the download to install each Microsoft Visual C++ Redistributable Package.

Microsoft Visual C++ 2005 Redistributable Package (x86): http://www.microsoft.com/en-us/download/details.aspx?id=3387
Microsoft Visual C++ 2005 Redistributable Package (x64): http://www.microsoft.com/en-us/download/details.aspx?id=21254
Microsoft Visual C++ 2008 Redistributable Package (x86): http://www.microsoft.com/en-us/download/details.aspx?id=29
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86): http://www.microsoft.com/en-us/download/details.aspx?id=5582
Microsoft Visual C++ 2008 Redistributable Package (x64): http://www.microsoft.com/en-us/download/details.aspx?id=15336
Microsoft Visual C++ 2008 SP1 Redistributable Package (x64): http://www.microsoft.com/en-us/download/details.aspx?id=2092
Microsoft Visual C++ 2010 Redistributable Package (x86): http://www.microsoft.com/en-us/download/details.aspx?id=5555
Microsoft Visual C++ 2010 SP1 Redistributable Package (x86): http://www.microsoft.com/en-us/download/details.aspx?id=8328
Microsoft Visual C++ 2010 Redistributable Package (x64): http://www.microsoft.com/en-us/download/details.aspx?id=14632
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64): http://www.microsoft.com/en-us/download/details.aspx?id=13523
Microsoft Visual C++ 2012 Redistributable Package (x86/x64/ARM): https://www.microsoft.com/en-us/download/details.aspx?id=30679
Microsoft Visual C++ 2013 Redistributable Package (x86/x64/ARM): https://www.microsoft.com/en-us/download/details.aspx?id=40784

Once every package has been downloaded and installed, restart Windows and run the cmd.exe as administrator and execute SetupPTClient.bat from the tools_client folder without any parameter.

How to Stop PeopleSoft image on Virtual Box

PeopleSoft Provided image on the Virtual Box can be stopped using many different options. These options can be used based on the strategy to administer the image.

First option is that you can go to the machine option and click on the ACPI shutdown. This will stop the services which are running on the virtual box and then shutdown the PeopleSoft Image.

One can also opt for the Machine >> Close and then select one from the three available options.

First Option in this case is -Save the Machine State- This will save the machine state as it and stop the image.

Second Option is - Send the Shutdown Signal- This will stop the services first and then shutdown the image. Similar to ACPI option as explained above.

and Third Option is - Power off the Machine- This is defined as the abrupt shutdown of the image. This option will stop the machine without stopping services which is as equivalent to KILL the running services.

Synchronize Target Metadata:Option in Change Assistant

Ever wonder what is Synchronize Target Metadata which come as a option while applying change package through Change Assistant.

Synchronize Target Metadata appear as a option in Apply Type in the Task Steps>>Settings section of the Change Assistant.

Once you applied the change package to target instance,Change Assistant can automatically update the source PeopleSoft Image(which is your PUM image) with the details of patches applied to target instance.This will help you when applying any other patches on target in future.

If your organisation have the strategy for PUM source and if you want to synchronize target metadata with source then select ‘Yes’ otherwise select ‘No’.

If you select ‘Yes’, source i.e. PeopleSoft Image(PUM Source image) should be up and remain accessible to Change Assistant until CA job is finished.This is required for details to update in the PUM Source image from the target environment.

Error in launching application Designer or Data Mover in two tier mode

When trying to log into 2-tier and launching Application Designer or DataMover, instead of the login screen, an error message comes up.  The error message says:

"Your security options are set improperly.  Please contact your system administrator."

The login screen never comes up.  It just keeps showing the above error every time when trying to launch the PeopleSoft Application from 2-tier.  This includes Application Designer, DataMover etc.


The issue could be resolved by doing the below steps:

1.  Launch Configuration Manager and in the Startup tab, re-type the ID/Password for the Connect ID.  Click "Apply" and "OK" and try to launch Application Designer.

2.  Launch Configuration Manager and in the Client Setup tab, reinstall the Workstation and try to log in again into Application Designer.

Data Mover Commands

Data Mover Commands

CHANGE_ACCESS_PASSWORD <symbolic_id> <newAccessPswd>

ENCRYPT_PASSWORD

ENCRYPT_PASSWORD <User_id>;
ENCRYPT_PASSWORD *;

IMPORT

IMPORT <table_name> As <new_tablename>;
IMPORT * AS <table_name> WHERE <condition>;
IMPORT *;

EXPORT

EXPORT <table_name> WHERE <condition>;
EXPORT *;

REPLACE_ALL

REPLACE_ALL <record_name>;
REPLACE_DATA *;

REPLACE_DATA

REPLACE_DATA <record_name>;
REPLACE_DATA *;

REPLACE_VIEW

REPLACE_VIEW <view_name>;
REPLACE_DATA *;

SET

SET LOG <log_file>;
SET OUTPUT <file_name>;
SET INPUT <file_name>;
SET IGNORE_ERRORS;
SET IGNORE_DUPS;
SET COMMIT;
SET UPDATE_DUPS;

PeopleTools Client Stand Alone Deployment on Windows: DPK Deployment

Steps to install the PeopleTools Client(stand alone): DPK Deployment.

Note that Stand Alone Deployment is majorly required for the PeopleTools Upgrade.


1. Copy the Zip file PEOPLETOOLS-WIN-8.55.05_4of4.zip for windows in the target windows server under DPK_INSTALL


2. Extract the content from the downloaded zip file which will create the another folder.

3. Run the command prompt as administrator and change the directory where you have extracted the PEOPLETOOLS-WIN-8.55.05_4of4.zip file.

4. Follow the steps as below

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\WINDOWS\system32>e:

E:\>cd PT85505

E:\PT85505>SetupPTClient.bat -t
****** SetupPTClient started at 14:58:27.05 ******


 Do you want to deploy PeopleTools client? [Y/N]: Y

 Please Select the Database Platform:
 1. Oracle
 2. DB2 for LUW
 3. Microsoft SQL Server
 4. DB2 for zOS

 Enter your choice [1-4] : 1

 Please specify the PSHOME for the PeopleTools Client [C:\PT8.55.05_Client_ORA]:



 Do you want to configure PeopleTools client? [Y/N]: N

 Please make your selection for the PeopleTools Client deployment:
 1. PeopleTools Full Upgrade
 2. PeopleTools Patch
 3. None of the above

 Enter your choice [1-3]: 1


 Do you want to install Change Assistant? [Y/N]: Y

 Please specify the directory to install Change Assistant [C:\Program Files\Peop
leSoft\Change Assistant]:


 Do you want to install Change Impact Analyzer? [Y/N]: N


 Do you want to install PeopleSoft Test Framework? [Y/N]: N


 Do you want to configure PeopleSoft Test Framework? [Y/N]: N

 Starting Tools Client Deployment!


 Deploying PeopleTools 8.55.05 Client in C:\PT8.55.05_Client_ORA

 Configuring PeopleTools 8.55.05 Client

 Installing Change Assistant for PeopleTools 8.55.05 Client in C:\Program Files\
PeopleSoft\Change Assistant

 Deployment of PeopleTools Client Complete.

 Please launch Change Assistant to configure and validate your Source and Target
 environment setup to perform Tools Upgrade

 Tools Client Deployment Ended.

"****** SetupPTClient ended at 15:05:38.17 ******"
"Please review C:\Local\Temp\PeopleSoft\PTClientDep
loy.log for additional information."

Cobol execution through Process Scheduler failing with the error

Test Cobol process through process scheduler was failing with the error as below

 Message:     Process 10568 is marked 'Initiated' or 'Processing' but can not detect status of PID
        Process Name: PTPDBTST
        Process Type: COBOL SQL

We have recompiled and re-linked Cobol many time but it keep giving us the error as above.

Issue: While compiling the cobols, the compiler was converting all cobol files for Unicode


[cam90dmo@csdev1 setup]$ ./pscbl.mak
Start of compilation in PS_HOME (/home/cam90dmo/pt/ps_home8.55.03)

/home/cam90dmo/pt/ps_home8.55.03/setup/pscbl_mf.mak : Convert all files for Unicode ....


 Conversion Summary for Source Codes in  :

     Source: /home/cam90dmo/pt/ps_home8.55.03/src/cbl/
     Target: /home/cam90dmo/pt/ps_home8.55.03/src/cblunicode/

Solution: 

While installing using DPK, I have defined unicode parameter as false in psft_customizations.yaml file still the installation of PeopleTools has generated the unicode.cfg file is in the %PS_HOME%\setup directory. The said file does not exists in a non-Unicode installation.

About the file itself, it contains only one section [unicode] and one line, unicode = 1. This file is subsequently sent to the Unix machine during the PeopleSoft Batch Transfer (pstrans.exe). In addition, this file impacts the compile process of the COBOL source files.

For a quick check, query the PSSTATUS table. If UNICODE_ENABLED=1, then this indicates a Unicode installation. If UNICODE_ENABLED=0, then it is NOT a Unicode installation.

For a UNIX/LINUX unicode installation, the Cobol compile process ( psrun.mak ) looks for the existence of this %PS_HOME%/setup/unicode.cfg file and if found calls on utilities to convert all the cobols to Unicode before compiling them.  If file not found, then ANSI is assumed and Cobols are compiled as ANSI. 

Since the file was there in PS_HOME/setup, I have removed the file and recompile and re-link the cobol. This time during re-compile it didn't create the cblunicode folder in the source.

Post doing the changes, restarted the process scheduler server and the cobol was successfully executing through the process scheduler. 

Weblogic TimeOut Parameters

Weblogic server is having few timeout parameters which users may need to check in case of any timeout issue in the application. Details of the weblogic time out parameters are as below

1. TimeoutSecs

This Parameter is defined in the weblogic.xml file located in the /webserv/PIA_DOMAIN/applications/peoplesoft/PORTAL.WAR/WEB-INF

TimeoutSecs is the session timeout for the webserver. However this timeout parameter is no longer in use by the PeopleSoft. Session Timeouts set in the Web Profiles override any HTTP session timeouts set on the webserver at runtime.


2. session-timeout

Parameter is defined in the web.xml and located in the directory
/webserv/PIA_DOMAIN/applications/peoplesoft/PORTAL.WAR/WEB-INF

Session Timeout is the parameter used by the webserver but PeopleSoft no longer uses session timeout on the webserver. Session timeouts set in the Web Profiles override any HTTP session timeouts set on the webserver at runtime.

3. Max Inactive Interval

Parameter display the value in http session details via the weblogic console.It defines number of seconds until session expires.

The value is measured in seconds and based on the following parameter settings:

A. Web Profile “Inactivity Logout” setting
B. Web Profile “HTTP Session Inactivity” setting
C. “Permission List” setting

GenMessageBox(200, 0, M): PS General SQL Routines: Missing or invalid version of SQL library libpsora64

Boot Attempt for application server and Batch Server on the RHEL7 was failing with the error as below

PSPPMSRV.32692 (0) [2016-05-02T15:01:15.608] - - - (0) PeopleTools Release 8.55.03 (Linux) starting. Tuxedo server is PPMGRP(91)/100
PSPPMSRV.32692 (0) [2016-05-02T15:01:15.609] - - - (3) Detected time zone is ACST
PSPPMSRV.32692 (0) [2016-05-02T15:01:15.751] - - - (0) Cache Directory being used: /home/fs91dmf/psft/pt/8.55/appserv/fin91dmo/CACHE/PSPPMSRV_100/
PSPPMSRV.32692 (0) [2016-05-02T15:01:15.760] - - - (1) GenMessageBox(200, 0, M): PS General SQL Routines: Missing or invalid version of SQL library libpsora64
PSPPMSRV.32692 (0) [2016-05-02T15:01:15.762] - - - (1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database FIN91DMO with user VP1.
PSPPMSRV.32692 (0) [2016-05-02T15:01:15.762] - - - (0) Server failed to start
PSADMIN.32658 (0) [2016-05-02T15:01:22.616] - - - (0) End boot attempt on domain

Further review of stderr file was showing the error which was pointing to the Oracle file libclntsh.so.11.1

dlopen in libpscompat failed for 'libpsora64.so': libclntsh.so.11.1: cannot open shared object file: No such file or directory
dlopen in libpscompat failed for 'libpsora64.so': libclntsh.so.11.1: cannot open shared object file: No such file or directory

Solution

Application server was not starting because of bad link.The application server is looking for a library that does not exist dlopen in libpscompat failed for 'libpsora64.so': libclntsh.so.11.1: cannot open shared object file: No such file or directory

As PeopleSoft now supports 64 bit Oracle for PeopleTools, the library libclntsh.so.11.1 need to link with the 64 bit lib directory.

I navigated to $Oracle_HOME/lib to check if the library are pointing to 64 bit lib directory. I found that soft link though exist in the lib directory pointing to 64 Bit lib directory but was actually broken as it was flashing in Red.

Note that softlink if broken will flash in Red colour in the linux directory structure.

I have unlinked the broken link: command as below
unlink libclntsh.so

Created the softlink again

ln -s libclntsh.so.12.1 libclntsh.so

Recreating the softlink fixed the issue







Post fixing the broken links to point to 64 bit library, both application server and batch server booted with success.

Process Scheduler Reports showing status as NOT POSTED

After the refresh of the PeopleSoft database with production backup, process scheduler reports were not posting to the report repository.

DSTAGNT_0428.LOG was showing the error as below.

PSJNI: Java exception thrown: javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: Untrusted Server Certificate Chain

PSDSTSRV.28584 (21) [2016-04-28T14:09:08.659 PostReport](3)     HTTP transfer error.
PSDSTSRV.28584 (21) [2016-04-28T14:09:08.659 PostReport](3)      Post Report Elapsed Time: 0.0200

The issue is caused by the digital certificates for the web server which were not loaded in the PeopleTools Security tables. Digital certificates can be loaded in PeopleSoft from the following navigation PeopleTools Security > Security Objects > Digital Certificates

As a solution to the issue, 

1. Export certificate from the browser padlock icon.
2. save certificate to the file.
3.  Navigate to PeopleTools > Security > Security Objects > Digital Certificates 
4. Click the + sign to add new record where Type = Root CA
5. Give the name for the certificate.It can be any name as per your convinence.
6. Open the saved certificated file in notepad and copy the entire text into the Detail field of the new Root CA. Ensure no carriage return at the end of the file.
7. Stop and restart the process scheduler server.


Solution helped in posting the reports successfully to the report repository.

PUM Image installation failing with Error:VirtualBox software is not installed on the Host

Attempt to install PUM image failing with the error. Executing the setup command on power shell ./psft-dpk-setup.ps1  is generating the error as below

VirtualBox software is not installed on the Host. This software is  required to automate the process of importing a PeopleSoft appliance.

The issue is caused by running the 32 bit version of the power shell. To resolve the issue we need to start the Windows PowerShell ONLY as administrator and should not attempt to start the x86 Windows PowerShell which is actually a 32-bit version.

psft_customizations file extension: Should be YAML only

After defining the psft_customizations.yaml and executing the command puppet apply site.pp --debug --trace, the puppet log was showing that psft_customizations.yaml is getting skipped in the process of deployment of environment stack. Log shown as below

ebug: hiera(): Cannot find datafile C:\ProgramData\PuppetLabs\puppet\etc\data/psft_customizations.yaml, skipping
Debug: hiera(): Looking for data source psft_unix_system
Debug: hiera(): Looking for data source psft_deployment
Debug: hiera(): Found peoplesoft_base in psft_deployment
Notice: Scope(Class[Pt_profile::Pt_tools_deployment]): JDK remove is true
Debug: hiera(): Looking up weblogic in YAML backend
Debug: hiera(): Looking for data source defaults
Debug: hiera(): Looking for data source psft_customizations
Debug: hiera(): Cannot find datafile C:\ProgramData\PuppetLabs\puppet\etc\data/psft_customizations.yaml, skipping

Further all the deployment customization as given in the psft_customizations.yaml also not considered in apply process. Finally the process failed with the error and didn't install weblogic, tuxedo and Oracle client.

Error: /Stage[main]/Pt_setup::Tools_deployment/Pt_deploy_weblogic[weblogic]/ensure: change from absent to present failed
: Weblogic installation copying failed: Execution of 'D:/dev/ps_home/pt85503/pt/wl20160427-1860-1izm0nwdir/pasteBinary.c
md -javaHome D:/dev/ps_home/pt85503/pt/jdk1.7.0_95 -archiveLoc D:/dev/ps_home/pt85503/pt/wl20160427-1860-1izm0nwdir/pt-w
eblogic-copy.jar -targetMWHomeLoc D:/dev/ps_home/pt85503/pt/bea -targetOracleHomeName OraWL1213Home  -executeSysPrereqs
false -silent true -logDirLoc D:/dev/ps_home/pt85503/pt/wl20160427-1860-1izm0nwdir' returned 4294967295: Log   File: "D:
\dev\ps_home\pt85503\pt\wl20160427-1860-1izm0nwdir\CLONE2016-04-27_14-59-10_1463859077.log".

Solution: It is due to the fact that when I was creating the psft_customizations.yaml on windows, I was saving the file as Yaml extension which eventually was getting saved as .txt extension. Yaml when saved with .txt extension will not be picked up by the puppet software for the deployment.
We need to save the file with double quotes in it so that it can be saved as file type of YAML ONLY i.e,

"psft_customizations.yaml". This will generate the file with the type as YAML. As given in the image embedded above.

After deploying midtier environment on windows attempt to apply customizations failing with the error:The term 'puppet' is not recognized as the name of a cmdlet, function

After creating the psft_customizations.yaml file, when I tried to run the puppet apply site.pp --debug --trace command on windows power shell. I received a message saying that the term "puppet" is not recognized when running this command.

PS C:\DPK_INSTALL\setup> cd ../..
PS C:\> cd C:\ProgramData\PuppetLabs\puppet\etc\manifests
PS C:\ProgramData\PuppetLabs\puppet\etc\manifests> puppet apply site.pp --debug --trace
puppet : The term 'puppet' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ puppet apply site.pp --debug --trace
+ ~~~~~~
    + CategoryInfo          : ObjectNotFound: (puppet:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException


It is due to the fact that the Puppet software is not included in the system's path. To set the Puppet environment, we need to run the command puppet_shell.bat:

PS C:\> cd '.\Program Files'
PS C:\Program Files> cd '.\Puppet Labs'
PS C:\Program Files\Puppet Labs> cd .\Puppet
PS C:\Program Files\Puppet Labs\Puppet> cd bin
PS C:\Program Files\Puppet Labs\Puppet\bin> ls

    Directory: C:\Program Files\Puppet Labs\Puppet\bin

Mode                LastWriteTime     Length Name
----                -------------     ------ ----
-a---        27/01/2015  11:49 AM       1243 environment.bat
-a---        27/01/2015  11:47 AM         91 facter.bat
-a---        27/01/2015  11:47 AM         94 facter_interactive.bat
-a---        27/01/2015  11:47 AM         91 hiera.bat
-a---        27/01/2015  11:47 AM         91 puppet.bat
-a---        27/01/2015  11:47 AM        104 puppet_interactive.bat
-a---        27/01/2015  11:47 AM         89 puppet_shell.bat
-a---        27/01/2015  11:47 AM        104 run_facter_interactive.bat
-a---        27/01/2015  11:47 AM        104 run_puppet_interactive.bat


Execute the command puppet_shell.bat on windows power shell.

This will set the Puppet software in system's path.

After executing the above command you need to restart the windows power shell with Administrator Option.
Open a Windows PowerShell window(with Administrater Option)
a. Select Start, and navigate to Windows PowerShell.
b. Right-click and select Run as Administrator.

And then re-execute the command puppet apply site.pp --debug --trace.

Error getting content - "Unable to get document" in PeopleSoft online application

Error getting content in the PeopleSoft application.When accessing any menu or component in the PeopleSoft, application is showing as   "Unable to get document" in the application browser. Though I was able to login successfully and navigate through the menus but when clicking on any menu/component, it was not retrieving data or publishing content on the page. 
Checked web server and application server logs but didn't see any details to target the issue.

Solution:
As the database was refreshed recently from the production backup, we checked the refresh log and found that issue was coming due to missing rows in PSCONTENT table after the refresh. Two rows which were missing in the table was for CONTNAME 'PT_HNAV_TEMPLATE' and 'PT_IFRAME_TEMPLATE'. We have imported two rows in the table from the backup and system started working as expected.

Details of Tuxedo Configuration Files.

The application server domain configuration use combination of the files which are generated on the Tuxedo application server. Details of the tuxedo configuration files are as below

1. PSAPPSRV.CFG: This file provide the parameter values for both variables in the Tuxedo configuration file psappsrv.ubx and application servers.
2. PSAPPSRV.VAL: Use as the Validation file.
3. PSAPPSRV.UBX: It is identified as the PeopleSoft Tuxedo template file which specify the layout for psappsrv.ubb and psappsrv.env.
4. PSAPPSRV.UBB: It is marked as Tuxedo native domain configuration source file.
5. PSAPPSRV.ENV: Application server environment file that defines additional environmental variables for server processes.
6. PSTUXCFG: It is compiled binary Tuxedo configuration file.

Oracle Support Delivery Cloud (OSDC)

Formerly named as Oracle E-delivery, Oracle software repository is now identified as

Oracle Support Delivery Cloud (OSDC)

Oracle now separated the application media and the People Tools media on Oracle support Delivery Cloud.

To clarify it more, if you are installing a new Application:

--You will need to search and locate the Application on OSDC(Oracle support Delivery Cloud)
 
--You will need to search and locate the PeopleTools on OSDC

--if you also use the Interaction Hub product (previously called Portal Solutions) you will also need to search for and locate that media as well.

Oracle has incorporated separate search functionality for the entire product line.

Timeout Parameters in a PeopleSoft

Timeout parameters in PeopleSoft Application stack which may need to adjust as per the organisational and business requirements.

PeopleSoft Application Server Timeout Parameters
[JOLT Listener] Client Cleanup Timeout
[JOLT Listener] Init Timeout
[Workstation Listener] Client Cleanup Timeout
[Work Listener] Init Timeout
Spawn Threshold
Service Timeout
Restart Period (PSBRKDSP_dflt, PSSUBDSP_dflt, PSPUBDSP_dflt)
TM_RESTARTSRV
TM_BOOTTIMEOUT
Tuxedo Sanity Scans and Blocking Timeouts

PeopleSoft Web profile Timeout Parameters
Inactivity Logout
Inactivity Warning
HTTP Session Inactivity (Public Users)
Disconnect Timeout (Jolt Settings)
HTTP Session Inactivity (Authenticated Users)
Send Timeout (Jolt Settings)
Receive Timeout (Jolt Settings)

Weblogic Server Timeout Parameters
Max Inactive Interval
session-timeout
TimeoutSecs 

How to clear PeopleSoft environment deployed through DPK

Navigate to DPK_INSTALL/setup/. Remove the environment using the -cleanup option for the PeopleSoft DPK setup script. Note that before removing the environment, set the ensure attribute to absent in default.yaml.

execute the command as below

sh psft-dpk-setup.sh --cleanup

Puupet can also be use to remove the deployed PeopleSoft Environment

To remove the environment manually on Linux:
1. Open the file /etc/puppet/data/defaults.yaml in a text editor
2. Change the value of the ensure attribute from present to absent.
3. Change directory to the /etc/puppet/manifests directory.
5. Run the following command:
puppet apply site.pp --debug --trace

Above will remove the deployed PeopleSoft environment in the linux server. Sometime I have faced the issue where running the  sh psft-dpk-setup.sh --cleanup script failed with the error.

In that case I have removed the following folders manually from the linux server


psadm1
psadm2
psadm3
oracle2
dpk
pt
db

After that executed the cleanup script again and it went to success

sh psft-dpk-setup.sh --cleanup

Cleaning up PeopleSoft Environment from the VM:

Cleaning up PeopleSoft Process Scheduler Domain:           [  OK  ]
Cleaning up PeopleSoft OS Users Environment:               [  OK  ]
Undeploying PeopleTools Components:                        [  OK  ]
Cleaning up System Settings:                               [  OK  ]
Removing Hiera-Eyaml Puppet Backend Encryption Keys:       [  OK  ]

Removing the Shared Folder from the VM:                    [  OK  ]

The cleanup of PeopleSoft environment is successful.

psft_deployment.yaml: Create customize file for installing PeopleSoft Binaries in the customized location

If you want to install the PeopleSoft in the default location then you can run the command

puppet apply site.pp --debug -trace

However, if you are looking to change the location/drive for your PeopleSoft and related component installation then you need to customize the psft_deployment.yaml file.
To override the default location, copy the entire section(section which details about installation location) from the psft_deployment.yaml file into the psft_customizations.yaml file and modify the values as needed.Ensure that the file begins with three dashes ---

Excerpt from ps_customizations.yaml file

---
peoplesoft_base: /opt/oracle/psft

dpk_location: /opt/oracle/psft/dpk
archive_location:     "%{hiera('dpk_location')}/archives"
pt_location:          "%{hiera('peoplesoft_base')}/pt"
db_location:          "%{hiera('peoplesoft_base')}/db"
db_platform: ORACLE
setup_ohs:            false

unicode_db:           false

ps_home_location:       "/opt/oracle/psft/ps_home8.55.03"
inventory_location:     "/opt/oracle/oraInventory"
oracle_client_location: "/opt/oracle/12.1.0.2"
jdk_location:           "/opt/jdk1.7.0_95"
weblogic_location:      "/opt/bea"
tuxedo_location:        "/opt/bea/tuxedo"
ohs_location:           "/opt/bea/ohs"

Change the unicode_db from true to false if it is non-unicode DB.

Save the above changes in ps_customizations.yaml and run the command puppet apply site.pp --debug -trace

PeopleSoft PeopleTools 8.55.03 Installation on Bare Metal(nativeOS) RHEL 7 through DPK

I am installing PeopleTools 8.55.03 on Bare Metal(nativeOS) Red Hat Enterprise Linux 7 using DPK and consolidating all my experience and information gained so far with new Tools 8.55.03 installation on the RHEL 7 Server. This is first post in the series and I will keep updating it with latest issues and solution for Tools 8.55 installation process.

In the first post, I will detail the process to install required Linux Packages, Puppet and DPK on RHEL 7.

1. Required Linux Packages

yum install gcc* libxslt* augeas* -y
yum install rubygem* ruby-2.0.0.598-25.el7_1.i686
yum install openssl-libs-1.0.1e-51.el7_2.4.i686
yum install libdb-5.3.21-19.el7.i686
yum instal libffi-3.0.13-16.el7.i686
yum install gdbm-1.10-8.el7.i686
yum install ncurses-libs-5.9-13.20130511.el7.i686
yum install ncurses-libs-5.9-13.20130511.el7.i686
yum install readline-6.2-9.el7.i686
yum install openssl-libs-1.0.1e-51.el7_2.4.i686

2. Create the folder DPK_INSTALL in your linux server. I have created the folder as /home/DPK_INSTALL

3. Copy PeopleTool 8.55.03 binaries in DPK_INSTALL folder.

4. Navigate to DPK_INSTALL folder.

5. unzip the first zip file named as  PEOPLETOOLS-LNX-8.55.03_1of4.zip in the DPK_INSTALL folder. command  >> unzip PEOPLETOOLS-LNX-8.55.03_1of4.zip

6. now to deploy all on the server with deploy_only option. Deploy all option will deploy the software required for the mid-tier components which includes Oracle Tuxedo, Oracle Weblogic and Oracle Database client. It will also install the PS_HOME directory on the designated server. Note that this option will not set the mid tier domains.

7. Command to execute. After executing the command below on the linux server, the process will go in a flow as detailed in the steps below

Steps below will install puppet, extract DPK and create the Hiera yaml file with user input.

sh psft-dpk-setup.sh --env_type midtier --deploy_only --deploy_type all


Starting the PeopleSoft Environment Setup Process:
Extracting the Zip File PEOPLETOOLS-LNX-8.55.03_1of4.zip:  [  OK  ]
Extracting the Zip File PEOPLETOOLS-LNX-8.55.03_2of4.zip:  [  OK  ]
Extracting the Zip File PEOPLETOOLS-LNX-8.55.03_3of4.zip:  [  OK  ]
Extracting the Zip File PEOPLETOOLS-LNX-8.55.03_4of4.zip:  [  OK  ]
Extracting the Zip File PT85503.zip:                       [  OK  ]

Verifying if Puppet Software is Installed on the Host:

Puppet Software is not installed on the Host. If this Host is
used to setup a PeopleSoft environment, Puppet Software should
be Installed.

Do you want to proceed with the Puppet Installation? [Y|n]: Y

Installing Puppet Software on the Host:                    [  OK  ]

Preparing the VMware VM for PeopleSoft Environment:


The VM is running on a VMware Hypervisor. We need to determine if the
VM is running on a VMware Player/VMware Workstation or a VMware Server
Hypervisor.

1.  The VM is running on a VMware Player/Workstation
2.  The VM is running on a VMware Server
q.  Abort the initialization process.
Enter 1,2 or q(uit): 2

The base directory is used to extract the PeopleSoft DPKs as well as for
deploying PeopleSoft Components. This directory should be accessible on the
VM, must have write permission and should have enough free space.

Please Enter the PeopleSoft Base Directory [/opt/oracle/psft]: /home/<PS_HOME>
Are you happy with your answer? [y|n|q]: y

Checking if PeopleSoft Base has Enough Free Space:         [  OK  ]

Checking if Default User Home Directory /home is Writable: [  OK  ]

Validating the DPKs in the VM:
Validating the PeopleSoft Application DPK:                 [  OK  ]
Validating the PeopleSoft PeopleTools DPK:                 [  OK  ]
Validating the PeopleSoft PeopleTools Client DPK:          [  OK  ]
Validating the Manifest Information in DPKs:               [  OK  ]

Extracting the DPK Archives in the VM:
Extracting the PeopleSoft PeopleTools DPK Archives:        [  OK  ]

Setting up Puppet on the VM:
Generating Hiera-Eyaml Puppet Backend Encryption Keys:     [WARNING]

Unable to generate EYAML backend encryption keys. Passwords will not be
encrypted and will be stored in clear text in the YAML files.

Do you still want to continue with the initialization process? [Y|n]: Y
Copying PeopleSoft Puppet Modules:                         [  OK  ]
Updating the Puppet Hiera YAML Files:                      [  OK  ]
Updating the Role in Puppet Site File for the VM:          [  OK  ]
Applying Linux Customizations to Puppet Hiera YAML Files:  [  OK  ]

Enter the database platform [ORACLE]:

Are you happy with your answers? [y|n]: y

Updating the Puppet Hiera YAML Files with User Input:      [  OK  ]

The bootstrap script is ready to deploy and configure the PeopleSoft
environment using the default configuration defined in the Puppet
YAML files. You can proceed by answering 'y' at the following prompt.
And if you want to customize the environment by overriding the default
settings, you can answer 'n'. If you answer 'n', you should follow the
instructions in the Installation Guide for creating a customizations
YAML file and running Puppet apply command directly to continue with
the setup of the PeopleSoft environment.

Do you want to continue with the default initialization process? [y|n]: n

You have decided not to continue with the default initialization process.
Any customizations to the PeopleSoft environment should be done in the YAML
files located in /etc/puppet/data directory. After making the necessary
customizations, run 'puppet apply site.pp' command from /etc/puppet/manifests
directory to continue with the setup of the PeopleSoft environment.

Stop at the step above and after this step customize the yaml file to meet the organisation specific requirement for installation and deployment of the application. If answered with Y at this step then installation and deployment will continue with default setup as given by Oracle.

In the next post on Tools 8.55 installation, we will see the other steps required for installing and configuring application with Tools 8.55.

PeopleSoft Process Stuck in Posting

Recently I have faced the issue where the process stuck in posting for couple of days. Though in the backend I can see the process is actually posted. This confirms the fact that the status is not get updated correctly post the batch server posted the report.

Reason: This presumably happened due to abnormal shutdown of the Batch Server.

Solution: I have  checked three tables named as below and found that DISTSTATUS is not updated in PSPRCSRQST and PSPRCSQUE. PS_CDM_LIST was having the DISTSTATUS updated correctly.

PS_CDM_LIST
PSPRCSRQST
PSPRCSQUE


SELECT CONTENTID, PRCSINSTANCE, DISTSTATUS, RQSTDTTM FROM PS_CDM_LIST WHERE PRCSINSTANCE ='3451281' ;

select PRCSINSTANCE, RUNSTATUS, DISTSTATUS from PSPRCSRQST where DISTSTATUS='7' and PRCSINSTANCE = '3451281' ;

select PRCSINSTANCE, RUNSTATUS, DISTSTATUS from PSPRCSQUE where DISTSTATUS='7' and PRCSINSTANCE = '3451281' ;


Updated the distribution status correctly in PSPRCSRQST and PSPRCSQUE which helped me to resolve the issue.