| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Global cache at integration server level |
« View previous topic :: View next topic » |
| Author |
Message
|
| nelson |
 Posted: Tue Oct 06, 2015 9:58 am Post subject: Global cache at integration server level |
 |
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
Hi all,
Working on IIB 9... We want to enable global cache. We have a lot of integration servers. Is there a way to enable global cache only at EG level?
We want the global cache don't affect the rest of the integration servers.
The KC states this:
| Quote: |
| When the cache is enabled, the memory usage of integration servers that are hosting cache components is larger. If this memory usage is an issue, and you do not intend to use the cache, set the cache policy to disabled. |
|
|
| Back to top |
|
 |
| harish_td |
| Posted: Tue Oct 06, 2015 10:32 am Post subject: |
|
|
Master
Joined: 13 Feb 2006
Posts: 236
|
Enable the Catalog and the Container servers on only the Integration Servers you want (let's call it, GC-EG1).
All other integrations servers can connect to the cache components in GC-EG1 without needing to have any GC components defined on them.
You can't escape the memory usage of GC-EG1. What you can control is the minimum memory usage of this Integration server. So it starts with 2 GB memory and won't grow beyond 2 GB if there is not a lot of data that you are caching. |
|
| Back to top |
|
|
| NealM |
| Posted: Thu Oct 08, 2015 10:12 am Post subject: |
|
|
Master
Joined: 22 Feb 2011
Posts: 230
Location: NC or Utah (depends)
|
Other choices:
1. Buy eXtremeScale
2. Have a separate broker that does nothing but host global cache. In essence, your own mini XS. And no global cache components at all on your prod broker.
We have been doing option #2 for several months with great success for a shared and heavily used global cache. Our setup:
Two (for HA) global-cache-only brokers each with a shared global cache policy file, plus 4 EGs to support the 4 containers and 2 catalog servers that gc is happiest with. And Four services brokers that have gc policy = NONE and all EGs set with ContainerService and CatalogService disabled, but with connectionEndPoints = the connectionEndPoints string copied from one of the EGs from one of the global-cache-only brokers. |
|
| Back to top |
|
|
| nelson |
| Posted: Thu Oct 08, 2015 1:17 pm Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| Thanks a lot for your suggestions. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Thu Oct 08, 2015 3:59 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Enterprise level caching or Integration level caching - this will certainly give you an idea which option you have to go for
Broker - Global cache is more in to integration level caching, this is Xtreme Scale V8.5
Xtreme Scale (WXS) - i look this as Enterprise level caching -however its on the latest Version V8.6.0.8. (Catalog Monitoring, and feasibility to add more container servers on run time),
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
