DSM app packaging and caching

Hi,

As per the docs, the recommended way of packaging a DSM application is to have all the jar files in the WEB-INF/lib of vgn-ext-templating.war as well as custom-cda.war .

Question is , will this mean that we'll have 2 instances of the DSM cache (1 in each webapp) ? Is it better to have the jars in the .ear and reference the jars in the manifest of each of the webapp? This way the cache will be loaded by the application classloader and we'll have only 1 instance.

thanks,

Chinmay

Find more posts tagged with

Comments

Juan_Carlos_Ruiz_Cubo_(VILT)

You are right.

My recommendation is to have just 1 war for CDA or package all the CDA wars into 1 ear file.

The cache is per class loader so is very inefficient to have several class loaders.

Regards

Juan Carlos Ruiz Cubo

VILT
http://www.vilt-group.com/
Avenida de la Albufera 321, 3º 2ª
28031 Madrid
Tel: +34 913052553
Móvil: +34 696594065
Fax: +34913320833
Email: juancarlos.ruiz@vilt-group.com

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: miércoles, 27 de junio de 2012 15:35
To: eLink Recipient
Subject: DSM app packaging and caching

DSM app packaging and caching

Posted by chinmay_khandelwal@newyorklife.com (Khandelwal, Chinmay) On 06-27-2012 09:33

Hi,

As per the docs, the recommended way of packaging a DSM application is to have all the jar files in the WEB-INF/lib of vgn-ext-templating.war as well as custom-cda.war .

thanks,

Chinmay

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Juan_Carlos_Ruiz_Cubo_(VILT)

You are right.

My recommendation is to have just 1 war for CDA or package all the CDA wars into 1 ear file.

The cache is per class loader so is very inefficient to have several class loaders.

Regards

Juan Carlos Ruiz Cubo

VILT
http://www.vilt-group.com/
Avenida de la Albufera 321, 3º 2ª
28031 Madrid
Tel: +34 913052553
Móvil: +34 696594065
Fax: +34913320833
Email: juancarlos.ruiz@vilt-group.com

DSM app packaging and caching

Posted by chinmay_khandelwal@newyorklife.com (Khandelwal, Chinmay) On 06-27-2012 09:33

Hi,

As per the docs, the recommended way of packaging a DSM application is to have all the jar files in the WEB-INF/lib of vgn-ext-templating.war as well as custom-cda.war .

thanks,

Chinmay

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

eLink User

Hi Chinmay,

to answer your question: Yes.

And you are right, better to got only one instance of ObjectCache.

The way to get this might differ depending to your preferences. If you are using Tomcat as the Application Container for DSM I would prefer to merge the vgn-ext-templating.war and your stuff into only one DSM application. This is the easiest way to workaround. If you are using i.e. Jboss as Application Server you may want to deploy an EAR application with a shared "APP-INF" loader where you can place the CPS API libs so the ObjectCache class will be instantiated only one time for both WAR applications.

It becomes more complicated if you want utilize the FURL application too (which is using ObjectCache as well). For Tomcat there is no chance to share the CPS libs anymore, for Jboss there is: as mentioned above, simply add the FURL WAR to the CPS EAR.

-Uwe

Von: "eLink Entry: Discussion Group - Web Experience Management" <v7webcontentmanagement@elinkkc.opentext.com>
Antworten an: "MjY4ODkyMDAA@elinkkc.opentext.com" <MjY4ODkyMDAA@elinkkc.opentext.com>
Datum: Mittwoch, 27. Juni 2012 15:35
An: eLink Recipient <devnull@elinkkc.opentext.com>
Betreff: DSM app packaging and caching

eLink : DSM app packaging and cachingDSM app packaging and caching Posted by chinmay_khandelwal@newyorklife.com (Khandelwal, Chinmay) On 06-27-2012 09:33
Hi,As per the docs, the recommended way of packaging a DSM application is to have all the jar files in the WEB-INF/lib of vgn-ext-templating.war as well as custom-cda.war .Question is , will this mean that we'll have 2 instances of the DSM cache (1 in each webapp) ? Is it better to have the jars in the .ear and reference the jars in the manifest of each of the webapp? This way the cache will be loaded by the application classloader and we'll have only 1 instance.thanks,Chinmay[To post a comment, use the normal reply function]Forum: Discussion Group - Web Experience ManagementContent Server: Knowledge Center

Chinmay_Khandelwal

Thanks. I would prefer to have the 2 webapps packaged in the .ear and the jars loaded by the ear.

Can anyone from OpenText please comment on this?

thanks,

Chinmay

Uwe_Hollatz

Hi Chinmay,

sorry my update was not clear about the sender:

My Name is Uwe Hollatz, Customer Support Engineer at Open Text.

-Uwe