It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787
×6,076
×5,819
×4,288
×3,952

question asked: Jul 16 '15, 2:03 a.m.
question was seen: 3,316 times
last updated: Jul 16 '15, 2:25 a.m.

Related questions

FAQ - How this Forum works

Any experience with the new DCC module and a good topology for it ?

0
long TRUONG (365●4●118●146) | asked Jul 16 '15, 2:03 a.m.
 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:
  • the DCC is working with Tomcat but IBM recommendation is to use only DCC/WAS in PROD
  • And IBM support confirmed that DCC/WAS should work with CLM/Tomcat, but the combination has never been tested to be officially supported (same for RRDI/WAS & CLM/Tomcat)

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.

  On standard one-server departmental topology https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/c_topology_ex_stand_clm_dept.html&scope=null

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.

  And we want to have the reporting modules (DCC & JRS) on separate JTS (as it is one of the choice for stand-alone DCC) so it is not interrupted by the appServer or apps going down.

Hence we would appreciate any input/advice/comments from your experience on our 2 desired topologies:

 Currently we have an (unused) RRDI/WAS server on Window platform, which we can use for the DCC/WAS server, hence if we can't buy anything with a new DCC/WAS Linux server, we rather reuse an existing Window server.

Unfamiliar with WAS so far, we also wonder:

  • Is there any scenario where a WAS on a separate host by itself would be required or recommended ?
  • Is there a central WAS console to configure all the separate WAS ?
What would be your vote (and why) for the switch back to Linux/WAS:
  • with CLM 5.0.2 & the external install of DCC/JRS, and an upgrade to 6.0 later
  • or with CLM 6.0 with DCC/JRS included.

One answer

Most liked answers|Newest answers ↑|Oldest answers

0
permanent link
Ralph Schoon (63.1k●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

Register or to post 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.