TeamSite 8.2, Java vs Perl

Hi,

We're currently using TeamSite 6.7.2 SP1 and we're about to upgrade to 8.2. As this is a significant upgrade, I was taking a look through the ~1000 pages of documentation that was provided to me, and I saw more references to Java than I remember. So I'm wondering if it's still possible to develop for TeamSite without knowing Java?

We have a few DCTs, a couple of Perl PTs, and a few Perl-based workflows. Will I have to move any of that over to Java? I don't know Java, (nor do I want to know Java) so if developing for TeamSite 8.2 is going to require Java experience, I'd love to know in advance so I can ask my manager to assign this task to someone with the proper skillset.

Any advice/information you can provide would certainly help.

Cheers,
Matt

Find more posts tagged with

Comments

nipper

Your existing Perl will work. No issues there.

You can use Java, and some of the newer technologies will require Java (SitePublisher/LiveSite), but WFM, TST, etc all still happily run perl.

As to advice, I hope you have some help.

Are you replacing hardware ? Typically an upgrade like that would also include hardware/OS upgrade.

Note that the TeamSite install location has changed since 6. This is one of teh most significant issues I run into. If you are doing a new install, it will create a TeamSite folder under the path provided (/opt/iw-home). That can have huge ramifications on custom code. Of course the easy way to fix is with a symlink (on Linux).

matty_mouse

Thanks for your response, Andy.

Yes, we are replacing hardware. It's moving from an old Solaris box (I believe) to a RH/CentOS VM on much newer equipment.

As for help, I have a sysadmin to install the new version and get it running, but then I'm pretty much on my own to make all our old workflows, DCTs, PTS, etc work within the new system. So I'm sure it'll be a painful process. My biggest concern was that I'd need to work with Java. Since I won't, at least the pain should be bearable. :-)

Thanks again. Have a great day!

Adam Stoller

Just to make sure - you're planning on still registering all your users in /etc/passwd /etc/shadow or via some PAM module such that the users would still be able to physically login to the box (if allowed to do so)?

If so - then yes, Perl will still work.

If you are instead planning to use LDAP such that [most] all of the users are considerd "NonOS" - then no, Perl will not work in most of the places where you are probably using it and you would have to redo such customizations in Java / CSSDK.

Basically, any Perl code that is intended to run as the "logged in user" - will fail if that user is a "NonOS" user. Code being run by some local disk account (e.g.: "tsmaster" or such) will continue to work.

matty_mouse

That's how we're set up now, and AFAIK the plan is to continue that route. There are probably 20 or so users, (from an organization of ~4000), so LDAP isn't necessary. Thanks for mentioning that though; I'll be bringing this to my sysadmin's attention just in case!