nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Calling a Servlet from PT

Bill Klish

TeamSite 6.1 SP1
Windows 2003, Solaris 2.8

I am not sure if this should be in this forum or the developer forum but here goes:

I have written a simple Java Servlet that returns back some information that I want to embed in the output created from a Presentation Template. The servlet was built and added to the customer_src toolkit and deployed. I can access the servlet just by entering the url into a browser.

I have tried to call the same servlet within a presentation template and it gives me a login screen inside of the presentation template output. This leads me to believe that there is an authentication problem with whatever user is running iwpt_compile.ipl and my logged in user credentials. This is how I am accessing the URL:

use LWP: Smiley Frustrated

imple;
my $output = get 'http://myserver/iw-cc/myservlet?param1=value1';

Is there something that needs to be configued to allow anyone access to this servlet, or a way to configure the user running iwpt_compile.ipl to have access to this?

Find more posts tagged with

Comments

Johnny

You are definitely chosing the wrong technolodgy.
Why are you trying to use a servlet for this?..

PT generation is done on the server side, so you are trying to invoke that URL from with in the server via a PERL browser/agent - there is no relationship at all to the specific browser that contains the session string on the client machine.

If you really need to do this in Java (and not in PERL which is what the PT generation is based on) then your PT needs to make a system call to ex,ecute a standalone Java app (not servlet).
If the reason is to take advantage of CS SDK, then you're going to have even more authentication hurdles.

You seem way off target here.

John Cuiuli

Bill Klish

We aren't as far off as you are making it.

This is a very simple servlet that used to be a standalone Java application. We had invoked it as a standalone app in the past, but was just pretty much experimenting to try it out as a servlet. This app does not need anything from the CS SDK.

Unfortunately, Perl is not up to the task here. We need to use Java for this, and I was simply experimenting. I was hoping to avoid making system calls, relying on a path to a JRE to execute the code, and had hoped to contain it within the Content Center app.

Simple answer: I will keep it as a Java application.

Adam Stoller

Unfortunately, Perl is not up to the task here. We need to use Java for this ...

Just curious (i.e., not saying you're wrong [yet ;-)]) - but can you expand on the above and explain in a bit more detail why Perl couldn't be used / why Java had to be used?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com