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; } } }

cant call jsp without virtualizing

SendelbachDavid

Hello,
I'm new to the forum and I'm an intern at my place of work. We are having a strange issue when we try to modify a metadata file. We have a module replicant (in the forms > new form entry > 2nd page) that contains a dropdown list that gets populated by a jsp when the module_replicant is added. When making the call to the jsp, if the site hasn't been virtualized first, the call to the jsp results in a 404 error. If the site is virtualized first, the jsp works just fine and the drop-down list gets populated correctly. The http link to the jsp is identical in both situations.

I get the same 404 error when trying to call the jsp directly (by copying the link into my browser). I admit I am new to this, but I've been struggling with this for a few days now and I can't figure it out. Any thoughts would be appreciated.

Thanks

Find more posts tagged with

Comments

ISCBorisB

Hello,
I'm new to the forum and I'm an intern at my place of work. We are having a strange issue when we try to modify a metadata file. We have a module replicant (in the forms > new form entry > 2nd page) that contains a dropdown list that gets populated by a jsp when the module_replicant is added. When making the call to the jsp, if the site hasn't been virtualized first, the call to the jsp results in a 404 error. If the site is virtualized first, the jsp works just fine and the drop-down list gets populated correctly. The http link to the jsp is identical in both situations.

I get the same 404 error when trying to call the jsp directly (by copying the link into my browser). I admit I am new to this, but I've been struggling with this for a few days now and I can't figure it out. Any thoughts would be appreciated.

Thanks

Within TS internal http requests go through TeamSite's web Daemon (iwwebd Module)

Daemon redirects all http requests to either servletd for the TS Store access or to
iwproxy to access Customer's Web Service/App. Proxy Server (iwproxy) "maps" your URL
to a desired one according to Virtualization rules set by your TS Administrators.

The process is transparent to the user, the end result though is that the URL
actually used to render your response may be completely different than the original one.

You may want to take a look at TS Administration Guide to see how to configure proxy Server,
set mapping rules etc...

(Topic_35563)Actuate_BIRT_Professional_11SP3_DynamicallyAddScriptedDataSetColumnsInActuateDataObject.datadesign

SendelbachDavid

(this is the original poster, I had my username changed for obvious reasons)

Thanks for the quick reply. I looked at the Admin guide and it said the proxy server configurations are in iw.cfg.
After looking in that file, I found this piece of code:

[iwproxy_preconnect_remap]
_regex=/default/main/.*/WORKAREA/[^/]+/(home/)(.*)=http://................/$1$2
_regex=(^/iw-mount/default/main/.*/WORKAREA/[^/]+/).[^\?]*/((content|images|scripts|includes|pdf|authorware|flash|docs|powerpoint|zip|html)/.*)=$1$2
_regex=(^/iw-mount/default/main/(.*)/(((WORKAREA|EDITION)/[^/]+)|STAGING)/(.*\.html)((\?.*)?))$=$1

I'm kind of a noob so this is probably wrong, but if I were to add jsp to this list would that maybe work? This remap sends the request to port 81

ISCBorisB

...but if I were to add jsp to this list would that maybe work? This remap sends the request to port 81

What exactly is the problem you are trying to solve?

From little you've described before, it sounds like you need your JSP rendered in the context
of the actual application for which it's intended. If that's indeed the case you'll need
virtualization regardless of any other things you do.

Further, you've noted that "...If the site is virtualized first, the jsp works just fine...".
To me, it indicates that the virtualization rules are already set and set correctly.
Why would you want to modify rules by "...add[ing] jsp to this list"?

SendelbachDavid

I've atached a few screenshots to clarify. "this is under the new for entry tab" in teamsite. The issue is we want to have the drop down list populated by the jsp without clicking the "virtualize" file first. Judging by your first response and by what I read in the Admin manual, I thought making a change to the proxy settings would help.

It seems like the request is getting routed to the servlet engine when it should be getting routed to the Content Web Server (port 81).

Like I said, I'm very new to this. Hopefully the screnshots I attached can be helpful.

MenWithCars.zip

SendelbachDavid

I thought I should clarify more. We have a virtualization file in our workarea that when clicked displays a copy of our entire site. In order for that dropdown list to be populated correctly by the jsp, we currently have to click that virtualization file in the workarea.

If we don't click it, the connection to the jsp file (whose whole purpose is to populate the list) can't be made, resulting in the error message in the 1st pic I attached.

If we do click it, the jsp can be found and everything works correctly.

In both situations, the link that we pass via:

IWDatacapture.callServer(ineturl.toString() + "/MD_BASE/CEMCategory.jsp",params,true);

is the same. (where ineturl.toString() + "/MD_BASE/CEMCategory.jsp is the link I'm talking about)

ISCBorisB

Removed

ISCBorisB

we have to click that virtualization file [...] and everything works correctly

All this is custom and peculiar to your Web Application. We have no way of knowing how your Site
is configured, how it's virtualized and what this particular JSP does. You'll have to dig way deeper
to see what Application / Environment changes are made upon virtualization jsp run and how you can
automate it

SendelbachDavid

yeah, thats what I was afraid of.