| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Can I use DB2 11.5 Community Edition for ACE 11 on AIX? |
« View previous topic :: View next topic » |
| Author |
Message
|
| t603 |
 Posted: Thu Nov 07, 2019 1:45 am Post subject: Can I use DB2 11.5 Community Edition for ACE 11 on AIX? |
 |
|
Voyager
Joined: 16 Oct 2012
Posts: 88
Location: Prague, the Czech Republic, Europe
|
Good morning,
we are using the latest IIB 10 with underlying DB10.5 on AIX now. We are going to upgrade to the latest ACE 11 on AIX soon. We are using DB2 10.? now as configuration database for IIB applications (message flows), so the database is used almost for reading (selects), few writes for old-fashioned implementations of message flows. The data are per hour re-cached to IIB. Total data storage used is far below 1 GB of data.
Now we are considering to switch from Standard or Advanced Edition (I do not know, which one we are using now) of DB2 to DB2 11.5 Community Edition, because our usage of DB2 does not make sense to pay for Standard or Advanced edition.
I have a question, if someone know any cons against usage of DB2 11.5 Community Edition together with ACE 11 on AIX? I know, that according the ACE 11 Detailed System Requirements (one can see on https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=9305DA803ED511E7BE8E09C6CE305F89&osPlatform=AIX#sw-3) there is no mention about DB2 11.5 and about DB2 any version Express-C or Community Edition. But I suppose, that 11.5 support will be added soon and according to the DB2 overview, there are no feature differencies among Editions (Community, Standard, Advanced).
So?
Thank You for Your answer in advance, Stepan |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Nov 07, 2019 6:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
One rather meta question I have is why keep configuration data in DB2 rather than as configuration (user policies, UDP and the like) within ACE? Is it perhaps that when this design was conceived, broker didn't have the facilities and now is a good time to review what function & value this database adds. Especially as you mention caching.
Moving to the direct point, with any kind of situation like this you need to ask what is the risk of using an unsupported configuration? If you're storing business or state data that's one class of risk; you're not. So the question becomes, what happens if there's a problem? Do the flows all crash or keep going using the cached data? Could you update the cache some other way in the event of a problem? How dynamic is this configuration? Could you keep using the same configuration for hours, days, weeks, months or years - how long would you have to resolve the problem? If it's hours, that's one thing. If it's years, that's another.
Could you mitigate the risk by providing dynamic, volatile configuration in another way (e.g. policies) and leave the database with the boilerplate? A completely made up example would be to provide discount percentages via a policy or UDP, and the accounting period dates in the database.
Bottom line - try it in test, see how stable it is, accept or mitigate the risk as you feel necessary.
Other opinions are equally valid.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
