Using Asset Manager with CLM 3.x
Hi everybody,
I am a little bit confused about Asset Manager usage with CLM 3.x applications. There's a possible to use OSLC linking between CLM artifacts,etc... but while trying to configure Asset Manager I am only allowed to configure RTC 2.x server. But I like to use it with RTC 3.x, I couldn't find a way to achieve that? A little help might be good. Kind regards |
10 answers
Yes... you can link to CLM 3.x from RAM.
RAM uses RTC internally to drive its life cycle (based on work items). ... this internal RTC is 2.x.... RAM ships with a 2.0.0.2 RTC server, or you can connect to an existing one .... but this use is for the internal operation of the RAM server - not to be confused with OSLC linking ... A RAM server can link assets to CM, RM, QM and Arhitectual Mgt. artifacts. |
|
I got it :)
Then I need to configure my packeaged RTC installation. After that can use my CLM 3.x with RAM. Thank you very much. I'd appreciate it :) |
I'm not sure what this means?
Then I need to configure my packeaged RTC installation. After that If you are talking about the RTC installation that RAM installs, then no you cannot use CLM with that RAM. IF you are talking about a different RTC (one that 3.0) then yes you can use that other RTC. -- Rich Kulp Rational Asset Manager developer |
|
One of my customer is using CLM 3.x solution and they also like to use Rational Asste Manager.
Before deploying the application on their environment I am trying to configure and see everything is working well in my environment. So I installed and configured CLM 3.x to my local pc and now I am trying to configure Rational Asset Manager 7.5.1 At the first page of the configuration RAM asks me if I am going to install the packaged version of RTC 2.x or I will use my own RTC 2.x. There's no choice about RTC 3.x So I choose the packaged version of RTC which is coming with RAM installation. According to your message if I configure my RAM instance with RTC 2.x I cannot use it with CLM, then how should I configure my RAM installation? |
|
Those are two different RTCs that are being talked about.
On the Configuration page that is the RTC that RAM needs to maintain its own workflows. That must be an RTC 2.0. To participate in CLM the RTC being talked about is an entirely different RTC from the internal one that RAM uses. The CLM RTC must be a 3.0 RTC (and is physically a different RTC than RAM's internal RTC). In CLM this other RTC is not referenced on the configuration page. It is instead referenced on the Community's Connections tab as a foreign Jazz server. -- Rich Kulp Rational Asset Manager developer |
Those are two different RTCs that are being talked about. That's OK. Internatl RTC 2.x is installed and workflows are stored in that.
That's OK too. I have setup CLM 3.0.1.2 installation with RTC.
So I need to go into Cross-Server Communication and mark my RTC 3.x server as a Non-jazz server and configure the integration between CLM and RAM server. It asks Oauth access URL,Oauth authentication URL etc. I don't know what to write into those fields. And there's no proper documentation about RTC 3.x integration. |
So I need to go into Cross-Server Communication and mark my RTC 3.x First RTC is Jazz, RTC would be a Jazz server friend, not a Non-jazz server friend, Second the documentation is in the RAM docs starting at: http://publib.boulder.ibm.com/infocenter/ramhelp/v7r5m1/index.jsp?topic=%2Fcom.ibm.ram.doc%2Ftopics%2Fc_integrate_jazz_overview.html -- Rich Kulp Rational Asset Manager developer |
|
Ok, the problem solved. RAM Cross Server communication recognized my RTC server as Change and Configuration Management. Last time I tired to add my RTC 3.x server the OSLC Domain dropdown box was disabled and didn't show anything for some reason but it is working now.
That's why I was asking if I should use non-Jazz server. I thought may be RTC's jazz Team Server(JTS) has some difference. Thank you for your help. I appreciate it :) |
Last time I tired to add my RTC 3.x server the OSLC Domain dropdown box was disabled and didn't show anything for some reason Whenever the root services URL is changed, that combo box is disabled while we fetch the root services document and determine what type of server it is. Usually, this only takes a couple seconds, but maybe your RTC server was slow before and that's why it stayed disabled. |
|
I noticed a problem in the CCM logs. There was a problem with my RTC test enviroment during the whole time. A simple restart would have solved my problem :)
|
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.