query about XPP 9.7 upgrade and WebServices

We have just upgraded to 9.7 and are experiencing some problems with out WebServices implementation.

As part of the 9.7 upgrade some changes to Perl have been listed in the Release Notes.
a. the location of Perl will be moved to a new location
b. Perl will be upgraded to v5.38

We are getting messages from WebServices that seem to indicate that the Perl location move is a problem.

For example, on our Web Server we run a program that has this callout to the WebServices API:


Progress(">Running BuildList command on XPP server");
$XPPDoc->userCommand($doc,'BuildList2.pl'," ws apply ftp-robot");

Note - we just pass the Perl program name of BuildList2.pl we do not name the program to process it - XPP works out that it is a Perl program.

The result message we get back from that userCommand call is:

PROBLEM:
From Webservices: 'perl' is not recognized as an internal or external command,
operable program or batch file.
: command=cmd /c perl D:\XPP\xz\xppws\BuildList2.pl \\appserv1\XPP_Data\alljobz/CLS_WebServices/GRP_ABCDEF/JOB_GHI ws apply ftp-robot


Can anyone advise how the change of Perl location on our XPP server has had an impact on those userCommand callouts?
Any other insight also gratefully received!

Thanks.

Paul

Paul Montgomery

emoji
  • It looks like we have got past the problem that generated the original message ...  perl was not being found.
    A reboot of our XPP server enabled the new PATHs to be found.

    I have a further query though - after the 9.7 install of Perl it looks like our @INC contains
    D:/XPP/xz/common/perl/site/lib
    D:/XPP/xz/common/perl/vendor/lib
    D:/XPP/xz/common/perl/lib

    However, we have a custom module for our WebServices located in D:/XPP/xz/xppws

    I'm wondering if anyone knows whether, prior to the 9.7 installation of Perl did the default @INC that XPP sets up used to include the xppws folder ?

    emoji
  • Hi Paul,

    The XPP 9.7 install doc notes if you have customized perl files you should migrate the customizations to the xz\common\perl folder.

    Screenshot of a document section titled 'Post-Upgrade Tasks' with a highlighted sentence: 'If you have customized Perl files, migrate the customizations to the xzcommonperl folder.'

    Hopefully that does the trick for you!

    emoji


    Generated Image Alt-Text
    [edited by: RWS Community AI at 3:41 PM (GMT 0) on 13 Jan 2025]
  • Thanks Sharon - it looks like we are now working OK.

    I had thought that that note had referred to just migrating any customizations that used to be under %XYV_EXECS%\perl to the new location of %XYV_EXECS%\common\perl
    That is how I read the note on page 32 of the Release Notes.

    However, having now moved our custom Module from %XYV_EXECS%\xppws to a location within %XYV_EXECS%\common\perl, as you suggested,  we are now processing things normally.

    Phew!

    emoji
  • Excellent, I'm so glad to hear that did the trick!

    I tend to be quite literal myself and I agree it could be read in 2 different ways...  If you have CUSTOMIZED Perl files versus If you HAVE customized Perl files -  emphasis matters. Slight smile

    emoji