XMLP file definition - Compare report shows absent issue

There is a problem that occurs when inserting XMLP File Definitions by inserting an XMLP Report Defn and using the Related Definitions to insert the file definitions.

When you do this it seems to insert the files OK, but if you were to do a compare of your project at this point in time, the file definitions it inserted automatically show up as Absent in both the Source and Target.

What you then have to do is insert the file definition manually, not by using the Related Definition method and inserting files with the same names that were inserted originally.

You will now see under the Upgrade tab that the files you added manually actually appear twice in XMLP File Defn. 

Does PeopleSoft PIA Support property "cookie-http-only" in peopletools 8.49

As the Doc ID: 1071895.1  confirms that the "cookie-http-only" property supported from Weblogic 9.2 MP4. 

Does it mean that the same functionality supported from Peopletools 8.49 running on Weblogic 9.2 MP4 as well. 

No: Weblogic 9.2 MP$ support this  property "cookie-http-only" but peopletools 8.49 doesn't support this feature.

The property "cookie-http-only" is supported from peopletools 8.50 onwards.

Configuring FTP to SFTP on peopletools 8.49

As we know that the SFTP protocal is supported from Peopletools 8.50 only. we need to customize the delivered script to have the SFTP implemented for  peopletools 8.49


Script to be customized: <PS_HOME>\bin\ftpunx

You can get the parameter that is passed to this script and do some scripting to read the file and perform the SFTP file transfer using below command.

$SFTP_CMD -b $1 $USER@$SERVERNAME


Note: This above applies to PSUNX only. And for PSNT you may need to have the secure FTP clients installed and have the transfer initiated from the client.

Rest Next :-}

How to specify a non-default port number for FTP/SFTP/FTPS URL Definitions?

PeopleTools only supports URLs with following syntax:

PROTOCOL://HOSTNAME
PROTOCOL://USER:PASSWORD@HOSTNAME
PROTOCOL://USER:PASSWORD@HOSTNAME:PORT

Therefore if for example only sftp://hostname:portname is provided, the URL syntax validation thinks you are providing the User and Password without any Hostname, and gives an Invalid Parameter error.

Create instead a URL with a dummy (fake) username and password to workaround the above. The username provided and password will not actually be used, since the URL Properties would be used instead.

For example:
URL value: sftp://dummyuser:dummypassword@mysftpserver.com:1111

Above applies only from Peopletools Version 8.51 and later