Bug 1035296 - Governance wars are not distributable by default
Summary: Governance wars are not distributable by default
Keywords:
Status: MODIFIED
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: DT Governance
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: FUTURE
Assignee: Eric Wittmann
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-27 13:34 UTC by Stefan Bunciak
Modified: 2023-05-15 19:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The Governance WAR files are not distributable by default. To work around this, users must add the <programlisting><![CDATA[ <distributable/> ]]></programlisting> tag to all Design Time Governance web applications.
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OVERLORD-141 0 Major Closed Ensure all Overlord JARs are marked as 'distributable' in web.xml 2014-09-04 12:32:44 UTC

Description Stefan Bunciak 2013-11-27 13:34:45 UTC
Description of problem:

While configuring a clustered server consisting of 2 FSW standalone servers, I needed to manually add <distributable/> tag to all design time governance web applications (there is 5 of them). 

This should be either fixed or at least documented.

Version-Release number of selected component (if applicable):
* FSW ER6 (Beta)

How reproducible:

Comment 1 Eric Wittmann 2013-11-27 15:05:12 UTC
I'm sorry to say I don't know what this means (although it sounds easy to fix!).  Could you give me some additional context or a link to relevant documentation?

Also - what are the 5 web applications?  Here is a list off the top of my head:

s-ramp-server
s-ramp-ui
dtgov
dtgov-ui

Additionally we have:

rtgov-server
gadget-web
bpel-console
bpel-console-server

Comment 2 Stefan Bunciak 2013-11-28 11:53:30 UTC
(In reply to Eric Wittmann from comment #1)
> I'm sorry to say I don't know what this means (although it sounds easy to
> fix!).  Could you give me some additional context or a link to relevant
> documentation?
> 

https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.1/html-single/Development_Guide/index.html#Enable_Session_Replication_in_Your_Application

Basically, they do not have <distributable/> tag in web.xml. So yes, it's an easy fix :-)

> Also - what are the 5 web applications?  Here is a list off the top of my
> head:
> 
> s-ramp-server
> s-ramp-ui
> dtgov
> dtgov-ui
> 

Yes, we have web applications other than for design-time governance but my points of interest are dtgov&sramp. I did not inspect other wars so maybe this issue applies to others as well.

> Additionally we have:
> 
> rtgov-server
> gadget-web
> bpel-console
> bpel-console-server

Comment 3 Gary Brown 2014-06-18 15:49:46 UTC
Hi Stefan - when the wars are marked as distributable, do they still function correctly, with respect to SSO, across the clustered servers if a session migrates?

Comment 4 Stefan Bunciak 2014-06-20 12:17:52 UTC
Hi,

I was able to configure overlord sso to propagate authorization among the server nodes.

Steps I made: 
* set-up FSW server as described in https://bugzilla.redhat.com/show_bug.cgi?id=1035315
* add to the web subsystem of every standalone-ha.xml, under the "virtual-server" named 
"default-host":
     <sso cache-container="web" cache-name="sso" 
reauthenticate="false"/>
* put <distributable/> to web.xml, and
* <replication-config>
      <cache-name>web/sso</cache-name>
  </replication-config> to jboss-web.xml 
  in all governance wars.

Comment 5 JBoss JIRA Server 2014-09-04 12:31:56 UTC
Eric Wittmann <eric.wittmann> updated the status of jira OVERLORD-141 to Resolved

Comment 6 JBoss JIRA Server 2014-09-04 12:32:44 UTC
Eric Wittmann <eric.wittmann> updated the status of jira OVERLORD-141 to Closed

Comment 7 Eric Wittmann 2014-10-10 11:29:42 UTC
I *believe* this has been addressed for all WARs in community.


Note You need to log in before you can comment on or make changes to this bug.