Any experience with the new DCC module and a good topology for it ?
![]()
We migrated from Linux/WAS to Windows/Tomcat when we upgraded from 3.x to 4.0.3. And now we are planning a quick migration of RTC/RRC 5.0.2 back to Linux/WAS while also contemplating bringing in the DCC (and JRS) due to issues with the Java ETL CCM WI job, which has never been completed successfully for more than a year, despite the fix to Java ETL since 5.0.1
We have ruled out implementing the DCC before the switch to Linux/WAS, as:
We'd like to have the DCC/JRS on a separate host with its own JTS and WAS, so the data collection to the DW would be independent of the ups and downs of the CLM appServer.
All apps and reporting modules are on same server with the same JTS and with WAS.
Yet on Distributed enterprise topology https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/c_topology_ex_dist_clm_dept.html&scope=null
Each app is with its WAS and on its own server, yet each shares the same JTS.
Hence we would appreciate any input/advice/comments from your experience on our 2 desired topologies:
What would be your vote (and why) for the switch back to Linux/WAS:
|
One answer
![]()
Ralph Schoon (63.3k●3●36●46)
| answered Jul 16 '15, 2:13 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Jul 16 '15, 2:25 a.m.
Please see this page and the subsequent ones: https://jazz.net/wiki/bin/view/Deployment/StandardTopologiesOverview
The DCC should be on a dedicated server: https://jazz.net/wiki/bin/view/Deployment/RecommendedALMDeploymentTopologies6 |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.