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.