Interwoven JBoss and Interwoven Servlet engine

spayal · June 17, 2011

TS72, Solaris

----------------------------------

When I see services on WIndows Server 2003, I see Interwoven JBoss and Interwoven Servlet engine services runing. Is not the JBoss used as Servlet engine ? If UI related services are provided by Servlet engine then whats JBoss used for ?

WHat kind of application server is Servlet engine ?

As per J2EE architecture, application container contains servlet and web server sends http request to application container which processes requst and sends response to web server. Thats what is happening when I send first request to TeamSite and TS servlet engine sends response back with UI. SO if servlet engine is responsible for UI, then when does JBoss come in picture ?

Same way what does AccessService do ? Access is provided by Apache web server. Or is it like when I send request to Apache, it rerdirects request to AccessService, which checks permissions for this user and then sends it to Servlet engine which displays according to the credentials of user ? So AccessService is to check permissions and role of the user and validate his credentials ?

Thanks

Rick Poulin · June 17, 2011

JBoss (iwjbossd) and Tomcat (iwservletd) only coexisted in version 7.0, when Autonomy was making that transition. If you still have both in 7.2, then I'd guess it's the result of an upgrade that didn't clean up after itself. In 7.2, the iwservletd should not be there.

With the move to JBoss came a more modular architecture, but otherwise the old iwservletd and the new iwjbossd serve the same purpose (running the various IWOV Java webapps).

As for the AccessService, it has very little to do with permissions (and neither does Apache). TeamSite permissions are controlled by TeamSite (the iw-cc webapp, the iwserver and the file system all play their part in it). The AccessService's role, as I understand it, is to provide connectivity between various modules, namely between TeamSite and OpenDeploy, between TeamSite and the WFM, and any other component that has to connect to these applications without actually being bundled with them (with the possible exception of web services)

spayal · June 17, 2011

Does it mean that, if I stop servlet engine service then TS UI functionality should not be affected ?

By the way, we are using TS7.1. Is iwservletd removed from TS7.1 ?

Thanks

Migrateduser · June 17, 2011

Why don't you just try it?

worries · June 17, 2011

There are lot of possibilities which may be reason
1)OD admin
2)different preview server
3)it is just there from intially

find the port on which it is running and can you post the jboss version if you are working on teamsite 7.0

spayal · June 19, 2011

I stopped interwoven servlet engine and jboss application server alternately and I found that when servlet engine service was not running TS UI was down. But when jboss application service was not running, TS UI was running fine. So it looks like jboss application service is redundant and not servlet engine.

Any ideas why is it like this ?

Again this is TS71 on WIn Server 2003
--------------------------------------------

There are lot of possibilities which may be reason
1)OD admin
2)different preview server
3)it is just there from intially

what do you mean by this ?

1) Is JBoss application service for OD admin ? - There is a separate OpenDeploy UI Admin service
2) what do you mean by different preview server ?
3) Both servlet engine service and jbosss application service read interwoven servlet engine and interwoven jboss application server. So I dont think any of the service was there before TS was installed.

Rick Poulin · June 21, 2011

I stopped interwoven servlet engine and jboss application server alternately and I found that when servlet engine service was not running TS UI was down. But when jboss application service was not running, TS UI was running fine. So it looks like jboss application service is redundant and not servlet engine.

This can only mean one of two things: either you're actually not running on 7.2 at all, or your upgrade from a previous version did not complete successfully.

Frederik · June 21, 2011

in your first post, you say 7.2, now you say 7.1

we ran 7.1 for a brief time, before switching to 7.2 (non-production phase). I remember indeed that 7.1 still used iwservletd for the main UI (ccpro etc), whereas iwjboss was running some other stuff (iwadmin, etc, IIRC).

Interwoven JBoss and Interwoven Servlet engine

Comments

Categories