blockcopy

Sunday, February 15, 2026

Check db2 client latency with db2 database

 Check db2 client latency with db2 database

If you wanted to check latency of db2 client hosted on Linux vs db2 database hosted on Mainframe , you will usually perform ping <db2 hosting host> from client server and that will give response time. 

However if you are not satisfied with response time and think it takes more time then it is probably because of multiple hops between db2 client server and db2 hosting database servers. Usually these servers gateway servers and configured in db2 catalog in nodes. 

How to test actual query response time.

Perform following steps from server where you have indirect/gateway server configured in db2 client catalog nodes.

  1. Open the DB2 Command Window: Click Start, navigate to IBM Db2, and select "DB2 Command Window Administrator"
  2. Create SQL File: Create a file named test.sql in a local directory (e.g., c:\temp\test.sql) containing your SQL statement (e.g., SELECT * FROM schema.table;).
  3. Run db2batch:
db2batch -d DBNAME -f "c:\temp\test.sql" -a dbid/password -i complete

This will give following response with query result.
* Prepare Time is:       0.032398 seconds
* Execute Time is:       0.028289 seconds
* Fetch Time is:         0.000837 seconds
* Elapsed Time is:       0.061525 seconds (complete)

Now perform above steps from server where you have configured db2 hostname in catalog nodes. Whatever complete time difference you observe will be latency.

Reconfigure nodes appropriately for performance improvement.  Comment on blog if you looking for additional information. 

PeopleSoft Journal upload template giving error

 PeopleSoft Journal upload template giving error 

Following warning gets generated while performing transaction through PeopleSoft upload spreadsheet which do not allow to upload the data.

Solution -

1. Check the connection details , select any two sheets of spreadsheet ->right click and select unhide . This will show connection settings.

2. If url is HTTP based then contact your security team to allow unsecured traffic and disable encryption. This situation is has worked most of the cases however you can take security considerations before changes.


Friday, January 23, 2026

ERROR: Jolt client (ip address X.X.X.X) does not have proper application password. PeopleSoftTargetConnector - The appserver may be down. Check Appserver URL or Domain Password. (158

    ERROR: Jolt client (ip address X.X.X.X) does not have proper application password

Ping local node from Integration Gateway properties or directly from Integration Broker -> nodes.

Error observed in tuxlog file of PeopleSoft application server logs.

ERROR: Jolt client (ip address X.X.X.X) does not have proper application password. PeopleSoftTargetConnector - The appserver may be down.  Check Appserver URL or Domain Password. (158 

Even though configuration.properties domain password matching with app server domain password this error is occurring. 

Solutions --->

1. Remove and update domain password from psappsrv.cfg of app server domain and reconfigure App server domain. Test the local node

If still did not work

2. Remove domain password from Integration Gateway properties application server node details. Also remove it from psappsrv.cfg of app server domain and reconfigure App server domain. Test the local node.


2nd option fixed issue for me.



Sunday, March 9, 2025

PeopleTools 8.51 error while copying project through application designer- check copy options (62,30)

 PeopleTools 8.51 error while copying project through application designer

Definition Name RECNAME.FIELDNAME.FieldFormula not copied, check copy options (62,30)

While copying application designer projects to other database, if you receive an error like this:

Definition Name RECNAME.FIELDNAME.FieldFormula not copied, check copy options (62,30)

It means that you did not selected the language type Common  in your project copy options. This can happen if in the copy dialog, the user selects options and then selects a specific language (e.g. English).


Note this setting can continue to apply to a project even if another person is performing the copy. Behind the scenes this setting is stored in the PeopleTools table,PSPROJECTSEC

If it still did not work then select "Select All' If you are using multilingual database

Wednesday, January 17, 2024

Change Assistant unable to connect target database

Change Assistant unable to connect target database

While configuring change assistant with target database it is failing to query database and does not show any error message.

PeopleTools 8.60


Resolution 

Make sure you have updated tnsnames.ora with target database details in Oracle 19c client present in db folder of dpk and in oracle client. 


Monday, December 12, 2022

CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS, BECAUSE OF: bea.jolt.ApplicationException: TPESVCFAIL - application level service failure

After hitting PeopleSoft login page in browser getting following message

CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS, BECAUSE OF: bea.jolt.ApplicationException: TPESVCFAIL - application level service failure

-->

App Server logs does show following message

PSAPPSRV.7524 (4) [XX GetCertificate] - - - (1) (NET.502): PTWEBSERVER@HOSTNAME is an Invalid User ID, or you typed the wrong password.  User ID and Password are required and case-sensitive.  Make sure you're typing in the correct upper and lower case.  

Based on these issue is with PTWEBSERVER User .

1. User account PTWEBSERVER is locked, and if it is then unlock the PTWEBSERVER account :

UPDATE PSOPRDEFN SET ACCTLOCK=0 WHERE OPRID=’PTWEBSERVER’;

2. User password is not matching with encrypted value.
Navigate to 
$PS_CFG_HOME/webserv/<DOMAIN_NAME>/peoplesoft/applications/peoplesoft /PORTAL.war/WEB-INF/psftdocs/<DOMAIN_NAME>/configuration.properties

Look for parameter WebPassword

If you know existing password then use pscipher utility to check encrypted value of it and see if it matches with above WebPassword value. If not then reset it.

on command prompt type follow to get encrypted value
>pscipher password

Tuesday, September 6, 2022

Error in document delete process (262,2031)

 Elastic Search Indexing Application Engine process failure Error in document delete process (262,2031)

Search Indexing Process failure with following errors -

Message Log-

Error in document delete process (262,2031)

.log File -

Process XXX ABENDED at Step PTSF_GENFEED.INDXDATA.Step01 (PeopleCode) -- RC = 24 (108,524)

Process %s ABENDED at Step %s.%s.%s (Action %s) -- RC = %s

.Trc File-

Direct Transfer Parameters: URL= http://HOSTNAME/_bulk Handle Count=50 Process Instance = XXX SBO Name = INDEX NAME Max Error = 100 

Solution ---->

PeopleTools ->Search Framework ->Administration ->Search Options

Update Attachment handlers from default 50 to 20


Tuesday, June 21, 2022

ApplySession::apply failed: oracle.glcm.opatch.common.api.install.HomeOperationsException: A failure occurred while processing patch

 Weblogic 14.1.1 patch failure with following error -

UtilSession failed: ApplySession failed in system modification phase... 'ApplySession::apply failed: oracle.glcm.opatch.common.api.install.HomeOperationsException: A failure occurred while processing patch: 33791665'

Log file location: X\bea\cfgtoollogs\opatch\opatch20X_09-X-04AM_1.log

OPatch failed with error code = 73

Solution ->

Apply patch with -invPtrLoc

D:\33791665>D:\X\bea\OPatch\opatch apply -invPtrLoc D:\X\bea\inventory

Thursday, July 8, 2021

Unable to get PeopleSoft landing page after sign in due to error CPCServletService::DoService -> nPcmReturn=24: Failed to start the Java Virtual Machine.

Unable to get PeopleSoft landing page after sign in due to error CPCServletService::DoService -> nPcmReturn=24: Failed to start the Java Virtual Machine.

If you get following set of errors even after application services bounce then please try this solution.

Error:

PSAPPSRV.29571 (13) [2021-07-08T06:41:20.869 XXX@172.IP (IE 11.0; WIN10) ICScript] OYwwgOA89L98oA 3980798699840058369 XXXX(1) Could not load the JavaVM library jvm
PSAPPSRV.29571 (13) [2021-07-08T06:41:21.161 XXX@172.IP (IE 11.0; WIN10) ICScript] OYwwgOA89L98oA 3980798699840058369 PEOPLE1 (1) CPCServletService::DoService -> nPcmReturn=24: Failed to start the Java Virtual Machine. (2,766) PT_SECURITY.iScript.OnExecute  Name:getSIDHTML  PCPC:199  Statement:6
Called from:PT_FAV.AddToFav.OnExecute  Name:getSIDHTML  Statement:32
Called from:PT_FAV.AddToFav.OnExecute  Name:setHTML  Statement:120
Called from:PT_FAV.AddToFav.OnExecute  Name:AddToFav  Statement:23
Called from:PT_POPUP.Popup.OnExecute  Name:Popup  Statement:15
Called from:PT_BRANDING.IframeHeader.OnExecute  Name:setAddToFavPopupHTML  Statement:101
Called from:PT_BRANDING.IframeHeader.OnExecute  Name:SetAddFav  Statement:98

Solution ->

First check the what JAVA_HOME is set. Make sure JAVA_HOME directory exists.

Check PATH, LIBPATH and Shell profile ( of Linux server) and make sure jdk path is accurate.

Update correct JDK path , exit from your id and login back and rev-verify if environment variables are pointing to correct JAVA_HOME path.

Shutdown App services , configure App Server, clear cache and bring up services.

This should fix the issue.

Wednesday, May 5, 2021

Integration Gateway Message Unmarshalling: Could not Parse the XML message String. (158,10415)

Integration Gateway Message Unmarshalling: Could not Parse the XML message String. (158,10415) 

You will notice following error while pinging / testing node from Integration Gateway or Node definition. If you see following error in Logs then this solution will work. 

errorLog.html :
com.peoplesoft.pt.common.XmlException: [Parsing error] msg: Fatal Error: at file null line: 2 column: 359 message: An invalid XML character (Unicode: 0xb) was found in the CDATA section. 

Solution: 
Simply remove special characters from password and try again. It will work.

Wednesday, February 24, 2021

Unable to open opatch lsinventory due to error is not accessible. Please set appropriate JAVA_HOME and run again.

  Error :
    Unable to open opatch lsinventory due to error <JDK> is not accessible.
    Please set appropriate JAVA_HOME and run again.
     
  Solution:
      This error occurs when listing Weblogic Patches.
      This error occurs because of invalid path of JAVA_HOME.
      TO fix this change JAVA_HOME path in hidden file .globalEnv.properties present at $ORACLE_HOME/oui
     
      JAVA_HOME=<Latest JAVA_HOME Path>
   JAVA_HOME_1_8=<Latest JAVA_HOME Path>

Monday, December 14, 2020

Weblogic Server error OPatch failed with error code 255

Weblogic Server error OPatch failed with error code 255 If you get following error when attempting to list patches using opatch then try this solution. Note that I faced this error for Weblogic Server 12.2.1.3 after executing opatch lsinventory command. OPatch failed with error code 255 Solution: Most likely issue is due to JAVA and JRE path. If you are using Linux then export following two path and try again running opatch. export JAVA_HOME= export ORACLE_HOME= Please let me know if this helps you.

Monday, May 18, 2020

DeleteService failed - The specified service has been marked for deletion. (0x43

DeleteService failed - Error while deleting application server NT service


If you get following error while deleting PeopleSoft Application service then


DeleteService failed - The specified service has been marked for deletion. (0x43


Just sign-out or log off user session and connect to server again. The service will go away.



Tuesday, April 28, 2020

Windows Installer error during PeopleTools 8.57 installation on Windows and Linux Server through DPK

Error during PeopleTools 8.57 installation on Windows and Linux Server through DPK

Following error occurs sometimes when you are installing PeopleTools using DPK.


This error occurs during Puppet installation. It is because we have space in directory names where we have extracted DPK first zip file. E.g. d:\install dpk\setup.bat it should be d:\install_dpk\setup.bat
Hope this helps.

PeopleTools 8.57 installation on Windows Server through DPK

PeopleTools 8.57 installation on Linux Server through DPK

PeopleTools 8.57 has to be installed through DPK. Except PeopleTools everything else you can install manually in classic way. Following step will guide in details for PeopleTools 8.57 installation on Windows Server through DPK.

1. Extract first zip file of the linux DPK setup files inside DPK_INSTALL folder
 
2.Before you proceed for PeopleTools installation you will need to install Puppet software through admin user. If you wanted to installed PeopleTools through admin access then you don't need to install Puppet separately. Use following command if you wanted to install only Puppet using root user. Here we are proceeding to install puppet with PeopleTools installation.
 
3. Open the Windows Command prompt with admin rights. Change directory to DPK_INSTALL/setup
D:/DPK_INSTALL/setup>psft-dpk-setup.bat --env_type midtier --deploy_only --deploy_type tools_home

Starting the PeopleSoft Environment Setup Process:
 
Validating User Arguments:                                            [  OK  ]
Validating PeopleSoft Supported Platform:                             [  OK  ]
 
Extracting the Zip File PEOPLETOOLS-WIN-8.57.03_2of4.zip:             [  OK  ]
Extracting the Zip File PEOPLETOOLS-WIN-8.57.03_3of4.zip:             [  OK  ]
Extracting the Zip File PEOPLETOOLS-WIN-8.57.03_4of4.zip:             [  OK  ]
 
 
Verifying if Puppet Software is installed:
 
Puppet 5.3.5 is not installed on the Windows Host. If PeopleSoft
environment needs to be set up on this host, Puppet 5.3.5
must be installed.
 
Do you want to proceed with the Puppet 5.3.5 Installation? [Y|n]: y
Installing Puppet Software on the Windows Host:                       [  OK  ]
Installing eYAML Hiera Backend on the Windows Host:                   [  OK  ]
 
Preparing the Windows 2012ServerR2 VM for PeopleSoft Environment:
 
Checking if PeopleSoft DPKs are Present:                              [  OK  ]
 
The base folder is used to extract the PeopleSoft DPKs. It is also
used to deploy the PeopleSoft components. This folder should be
accessible on the Windows VM, must have write permission and should
have enough free space.
Enter the PeopleSoft Base Folder: D:/PS/PT857Base
Are you happy with your answer? [Y|n|q]: y
 
Checking if the Base Folder has Enough Free Space:
The PeopleSoft base folder [D:/PS/PT857Base] has only
X GB of disk space available. Please ensure it has at least
25 GB of free space for midtier.
 
 
 
Validating the PeopleSoft DPKs in the Windows VM:
Validating the PeopleSoft PeopleTools Server DPK:                     [  OK  ]
Validating the PeopleSoft PeopleTools Client DPK:                     [  OK  ]
 
Validating the Manifest Information in PeopleSoft DPKs:               [  OK  ]
 
Extracting the PeopleSoft DPK Archives in the Windows VM:
Extracting the PeopleSoft PeopleTools Server DPK Archives:            [  OK  ]
 
Setting up Puppet on the Windows VM:
Generating eYAML Hiera Backend Encryption Keys:                       [  OK  ]
Updating the Puppet Hiera YAML Files in the Windows VM:               [  OK  ]
Updating the Role in Puppet Site File for the Windows VM:             [  OK  ]
 
Enter the PeopleSoft database platform [ORACLE]: ORACLE
Is the PeopleSoft database unicode? [Y|n]: Y
 
Are you happy with your answers? [y|n]: y
Encrypting the Passwords in the User Data:
Updating the Puppet Hiera YAML Files with User Data:                  [  OK  ]
 
The bootstrap script is ready to deploy and configure the PeopleSoft
environment using the default configuration defined in the Puppet
Hiera YAML files. You can proceed by answering 'y' at the following
prompt. And, if you want to customize the environment by overriding
the default configuration, you can answer 'n'. If you answer 'n', you
should follow the instructions in the PeopleSoft Installation Guide
for creating the customization Hiera YAML file and running the 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 PeopleSoft environment
setup process. Any customizations to the PeopleSoft environment should be
done in the Hiera YAML file 'psft_customizations.yaml' and place it under
[D:/PS/PT857Base\dpk\puppet\production\data] folder. After making the
necessary customizations, run the following commands to continue with the
setup of PeopleSoft environment.
 
1. cd /d D:/PS/PT857Base\dpk\puppet\production\manifests
2. "C:\Program Files\Puppet Labs\Puppet\bin\puppet.bat" apply --confdir=D:/PS/PT857Base\dpk\puppet site.pp --debug --trace --detailed-exitcodes --logde
st /some_valid_path/to/log/psft_dpk_setup.log
 
Exiting the PeopleSoft environment setup process.
 The PeopleSoft Environment Setup Process Ended.
 

4.  Created following psft_customizations.yaml file and placed in data folder
 
---

ps_home:

db_type: "%{hiera('db_platform')}"

unicode_db: "%{hiera('unicode_db')}"

location: "D:/PSHOME"
 
5. Run the following command and PeopleTools 8.57 with patch will get installed.
 cd /d D:/PS/PT857Base\dpk\puppet\production\manifests
"C:\Program Files\Puppet Labs\Puppet\bin\puppet.bat" apply --confdir=D:/PS/PT857Base\dpk\puppet site.pp --debug --trace --detailed-exitcodes --logde
st d:/psft_dpk_setup.log
 
6. Next step is to configure the pscfg and attempt to connect target database through Application Designer.
 
 

Friday, March 20, 2020

Steps to deinstall Oracle Tuxedo 12.2.2

                                               Steps to deinstall Oracle Tuxedo 12.2.2
  1. Identify Oracle Home of Tuxedo. Once identified navigate to following path
Oracle Tuxedo Home \ oui \ bin and run setup.exe as admin.
If you are unable get installation wizard due to Java  then run command prompt as admin.
setup Java Home as
JAVA_HOME=D:\java1.8
Now navigate and run \ oui \ bin and run setup.exe from command line.


2.  Once Installation Wizard opens click on Deinstall Products and select OracleTuxedoHome from list and click Remove. It will show details of uninstallation , click yes.

3. Once Deinstall click ok and then cancel from main installation wizard. You will see Tuxedo uninstalled.

Tuesday, August 20, 2019

Steps to install of Oracle Tuxedo 12c version 12.2.2 patch in Linux Server

Steps to install of Oracle Tuxedo 12c version 12.2.2 patch in Linux Server

  1. Tuxedo 12.2.X onwards releases are supported by opatch so there are not many changes while installing Oracle Tuxedo base version but you will have to use opatch while applying Tuxedo rolling patches.
  2. Set Environment variables

Export JAVA_HOME=/opt/JDK1.8

EXPORT ORACLE_HOME=/opt/tuxedo


3. Create Oracle initialization file as oraInst.loc
This file contains the Oracle home path. Check sample file in Oracle documents for reference.

4. Run following command
Navigate to patch folder
>$ORACLE_HOME/OPatch/opatch apply 2951XXXX.zip -invPtrLoc /opt/oraInst.loc

Picked up _JAVA_OPTIONS: -Djava.security.egd=file:/dev/./urandom

Invoking OPatch 11.2.0.1.2



Oracle Interim Patch Installer version 11.2.0.1.2

Copyright (c) 2010, Oracle Corporation. All rights reserved.



 

Oracle Home : /opt/tuxedo

Central Inventory : /opt/tuxedo

from : /opt/oraInst.loc

OPatch version : 11.2.0.1.2

OUI version : 12.2.0.1.0

OUI location : /opt/tuxedo/oui

Log file location : /opt/tuxedo/cfgtoollogs/opatch/opatch2019-.log


.
.

OPatch will rollback the subset patches and apply the given patch.



Running prerequisite checks...



OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.



Backing up files and inventory (not for auto-rollback) for the Oracle Home

Backing up files affected by the patch '29513310' for restore. This might take a while...

Backing up files affected by the patch '29513310' for restore. This might take a while...

ApplySession rolling back interim patch '29513310' from OH '/opt/tuxedo'

..

 OPatch Session completed with warnings.



OPatch completed with warnings.

5. Check version of tuxedo using tmadmin -v

Monday, August 19, 2019

PeopleTools 8.57 installation on Linux Server through DPK

      PeopleTools 8.57 installation on Linux Server through DPK

PeopleTools 8.57 has to be installed through DPK. Except PeopleTools everything else you can install manually in classic way. Following step will guide in details for PeopleTools 8.57 installation on Linux Server through DPK.

  1. Extract first zip file of the linux DPK setup files inside DPK_INSTALL folder




DPK_INSTALL]$



    2. Before you proceed for PeopleTools installation you will need to install Puppet software through root user. If you wanted to installed PeopleTools through root access then you don't need to install Puppet separately. Use following command if you wanted to install only Puppet using root user.

Use this command if you do not want to update the system configuration variables on your host.
setup> ./psft-dpk-setup.sh --prereq.

User this command if you want to change ulimit and kernel values as per installation guide. This will also install puppet. This is optional.
setup>./psft-dpk-setup.sh --prereq --syscfg

 Puppet gets installed in /opt/puppetlabs

        3.   Open a terminal window using non root user and change directory to DPK_INSTALL/setup

      [setup]$ ./psft-dpk-setup.sh --env_type midtier --deploy_only --deploy_type tools_home

      You are running DPK setup without root/administrator access.
      Before proceeding, please ensure that the necessary prerequisites
      have been met, as described in the PeopleSoft installation documentation.

      Would you like to proceed with the setup as a non-root user? [y/n]: y

       
      Starting the PeopleSoft Environment Setup Process:

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

      Extracting the Zip File PEOPLETOOLS-LNX-8.57.05_4of4.zip: [ OK ]
      Extracting the Zip File PEOPLETOOLS-LNX-8.57.05_3of4.zip: [ OK ]
      Extracting the Zip File PEOPLETOOLS-LNX-8.57.05_2of4.zip: [ OK ]

       
      Verifying if Puppet Software is installed: [ OK ]
      Verifying if eYAML Hiera Backend is Installed: [ OK ]

      Preparing the Redhat Linux VM for PeopleSoft Environment:

      Checking if PeopleSoft DPKs are Present: [ OK ]

      The base directory is used to extract the PeopleSoft DPKs. It is also
      used to deploy the PeopleSoft components. This directory should be
      accessible on the Linux VM, must have write permission and should
      have enough free space.
      Enter the PeopleSoft Base Directory: /opt/PT857Base
      Are you happy with your answer? [Y|n|q]: y

      Checking if the Base Directory has Enough Free Space:
      The PeopleSoft base directory [/opt/PT857Base] has only
      xxxGB of disk space available. Please ensure it has at least
      25 GB of free space for midtier.

      Validating the PeopleSoft DPKs in the Linux VM:
      Validating the PeopleSoft PeopleTools Server DPK: [ OK ]
      Validating the PeopleSoft PeopleTools Client DPK: [ OK ]

      Validating the Manifest Information in PeopleSoft DPKs: [ OK ]

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

      Setting up Puppet on the Linux VM:
      Generating eYAML Hiera Backend Encryption Keys: [ OK ]
      Updating the Puppet Hiera YAML Files in the Linux VM: [ OK ]
      Updating the Role in Puppet Site File for the Linux VM: [ OK ]

      Enter the PeopleSoft database platform [ORACLE]: ORACLE
      Is the PeopleSoft database unicode? [Y|n]: Y

      Are you happy with your answers? [y|n]: Y
      Encrypting the Passwords in the User Data:
      Updating the Puppet Hiera YAML Files with User Data: [ OK ]

      The bootstrap script is ready to deploy and configure the PeopleSoft
      environment using the default configuration defined in the Puppet
      Hiera YAML files. You can proceed by answering 'y' at the following
      prompt. And, if you want to customize the environment by overriding
      the default configuration, you can answer 'n'. If you answer 'n', you
      should follow the instructions in the PeopleSoft Installation Guide
      for creating the customization Hiera YAML file and running the 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 PeopleSoft environment
      setup process. Any customizations to the PeopleSoft environment should be
      done in the Hiera YAML file 'psft_customizations.yaml' and place it under
      [/opt/PT857Base/dpk/puppet/production/data] directory. After making the
      necessary customizations, run the following commands to continue with the
      setup of PeopleSoft environment.

      1. cd /opt/PT857Base/dpk/puppet/production/manifests
      2. /opt/puppetlabs/bin/puppet apply --confdir=/opt/PT857Base/dpk/puppet site.pp --debug --trace --detailed-exitcodes --logdest /some_valid_path/to/log/psft_dpk_setup.log

      Exiting the PeopleSoft environment setup process.

      The PeopleSoft Environment Setup Process Ended.df

          4.  Created following psft_customizations.yaml file and placed in data folder






              ---

              ps_home:

              db_type: "%{hiera('db_platform')}"

              unicode_db: "%{hiera('unicode_db')}"

              location: "/opt/PSHOME"

                    5. Run the following command and PeopleTools 8.57 with patch will get installed.


                        cd /opt/PT857Base/dpk/puppet/production/manifests



                        [manifests]$ /opt/puppetlabs/bin/puppet apply --confdir=/opt/PT857Base/dpk/puppet site.pp --debug --trace --detailed-exitcodes --logdest /opt/tmp/psft.log


                        6. Next step is to create environment file psft_env.sh. Sample file is present in installation doc. You can include given variable in non root user profile file as well. Also call psconfig.sh from same profile file.