perl migration to TS 8.0

We are migrating from ts 7.2.1 to 8.0 and i want to know what limitation/challenges would we face considering the fact all our workflows,form api code,customisations etc in 7.2.1 is done in perl ?

Wouldn't perl be supported for workflows/presentation logic etc in TS 8.

Thanks.

Vysh.

Find more posts tagged with

Comments

nipper

From a sandbox TS8

/opt/interwoven/TeamSite/iw-perl/bin/iwperl -v

This is perl, v5.8.2 built for i686-linux-multi

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using `man perl' or `perldoc perl'. If you have access to the
Internet, point your browser at http://www.perl.com/, the Perl Home Page.

/opt/interwoven/TeamSite/bin/iwpt_compile.ipl

Syntax: iwpt_compile.ipl -v | (Note: command-line options wrapped for readability)
-h |
-pt presentation_file
[-ofile outfile]
[-smartwrite]
[-manifest filename]
[-oprefix basename_prefix]
[-ocode filename.ipl]
[-umask umask (note: UNIX only)]
[tag-specific args (eg: -iw_pt-dcr filename)]
[-oenc output_encoding_name (default: -oenc UTF-8)]
[-osenc os_encoding_name (default: -osenc UTF-8)]

Notes:

o Extensive online HTML-based is available at:
http://support.interwoven.com/library/devel/tst/pt/
and http://<your_local_teamsite_machine>/iw/help/tst/pt/

o For a complete list of available output encodings, type:
iwpt_compile.ipl -h -oenc

o Common tag-specific flags:
-iw_pt-dcr <dcr>
-iw_pt-arg <arg>
-iw_pt-preview
-iw_include-location <dir>

Adam Stoller

To answer your question a bit less obscurely than @nipper - you generally shouldn't have any issues porting your Perl code from the earlier version of TeamSite as I doubt anything in the iwperl distribution has changed.

The only issues I could see is if any of the interfaces / CLTs that iwperl uses for interacting with TeamSite changed - which could, potentially, break some code; but I think that's a reasonably low probability. It doesn't mean you shouldn't do robust testing of the code in the 8.x environment, just that you are unlikely to run into any issues.