Notice BTW for CQ OSLC to work with 3.0.1 CLM you need to upgrade CQ to at least 7.1.2.3 and not just 7.1.2 as stated in he documentation. If you dont do this the widgets will not work.

Hi All,

Just wanted to share some tips so that people might find them when they run into problems and search for them.

Running the JTS setup with LDAP getting the error "the user could not be created"

This error was in our case caused by the LDAP user we were logged in with to not be in the direct root of the AD. So if your ldap starts its search at users.company.com - this is where your admin user needs to be. not in say us.users.company.com

Problems logging in to a newly added application in your clm setup?

If you are adding for instance CCM to an upgrade of RQM (or any other combination) and you are using ldap for authentication then you will have a problem accessing the new applications setup url - you can simply not authenticate - this is because the new application is by default configured for tomcat where as your existing apps and jts uses ldap. To fix this you need to manually edit the web.xml of your new application to contain the ldap group mappings - compare this with your existing applications to find the correct values.

Integration with CQ
- here you need to run the repotools -migrateCmLinks
You also need to deploy the oscl package to your CQ schema and finally you need to remove the old friend from your app and add it with the new oslc path and redo all your project mappings.
You may also get an error when you access a dashboard that needs to be migrated - you can continue and ignore this error(this means you will no longer have CQ stuff on your dashboard) but you can manually add the widgets to each project.

Setting up datawarehouse:
All applications CCM, RM and JTS should use the same datawarehouse database. Using SQL server something interesting happens here - you need to specify a table space folder which you for some reason only need to do for the datawarehouse database and not for the applications. In this case the only thing I could get working was to create a folder in a random place on the database server and use this value so for instance D:\jazztablespace - remember to create the folder your self.
Notice that dw user is created if it does not exist. If you use LDAP you should use an existing user(a tech user not your admin) as dw user and notice that the user needs the JazzAdmins role and some kind of license.

Public uri's:

When you upgrade your server you get the option of changing the public uri - which you can actually not do because it would screw up all internal linkings between workitems. so for an existing application use the same URI. However for JTS and new applications its a good idea to create a dns forwarding the server where you install them so that you may move the applications later on. Say you install all applications on a single server but in future you want to move them seperately - to do that you need to use something like

jts.company.com/jts
ccm.company.com/ccm
myserver/jazz (in this case an upgraded rqm that can never be moved away from myserver)

Widgets and reports not deployed:

When you upgrade your server the new version of the server has a number of report templates available for reports and widgets in dahsboards. However these needs to be manually deployed to each project area - so you need to use the rtc eclipse client and go to the reports folder of your project area and right click ->deploy new templates. This is the case for both RTC and RQM though you would normally not use RTC clients for RQM.

Hi Kim,

I also want to thank you for these tips. I have run into these situations over the past 2 weeks. I saw them first when I was just trying to upgrade RTC v2.0.0.2 with iFix 6 to CLM v3.0.1. That setup was on a VMWare system and I actually got that to almost work. I downloaded and followed the CLM upgrade to v3.0.1 from v2 workshop. I think that the workshop is pretty good. However, it was describing steps for someone who was working with a WebSphere Application Server and the workshop lost me after I upgraded RTC and the instructions started describing how to remove the old RTC files using WAS. I am using Tomcat with SQL Server.

We were then given a new "physical" server. This new server has the specifications that are "recommended" by IBM. 2 "iCore 8" CPUs with 16GB of RAM and a large HD. I am installing CLM as JTS along with RTC, RQM, and RRC on this and I think we have a good system to do that. On this new server, I installed CLM v3.0.1 from scratch. Then I went thru all of the gyrations, head banging, and convulsions encountering the situations that you captured in your original post.

I love using RTC/RQM and up to now have only had to do upgrades to those products. The process for the upgrades in the v2.x version have gone smoothly. I understand that the CLM 3.0.1 is a totally new architecture. However, I do need to say that the documentation for the install process is not very good. For example, the issues involving the data warehouse are really a big pain point. I had to look at over a dozen topics about this issue in the forums to get it working. Fortunately, the Jazz forums are very helpful (this topic is an example). I am getting though all of this with the help of the forums and authors like you and others going through this experience.

Thanks again,

-Walter

Hi Kim,

I also want to thank you for these tips. I have run into these situations over the past 2 weeks. I saw them first when I was just trying to upgrade RTC v2.0.0.2 with iFix 6 to CLM v3.0.1. That setup was on a VMWare system and I actually got that to almost work. I downloaded and followed the CLM upgrade to v3.0.1 from v2 workshop. I think that the workshop is pretty good. However, it was describing steps for someone who was working with a WebSphere Application Server and the workshop lost me after I upgraded RTC and the instructions started describing how to remove the old RTC files using WAS. I am using Tomcat with SQL Server.

We were then given a new "physical" server. This new server has the specifications that are "recommended" by IBM. 2 "iCore 8" CPUs with 16GB of RAM and a large HD. I am installing CLM as JTS along with RTC, RQM, and RRC on this and I think we have a good system to do that. On this new server, I installed CLM v3.0.1 from scratch. Then I went thru all of the gyrations, head banging, and convulsions encountering the situations that you captured in your original post.

I love using RTC/RQM and up to now have only had to do upgrades to those products. The process for the upgrades in the v2.x version have gone smoothly. I understand that the CLM 3.0.1 is a totally new architecture. However, I do need to say that the documentation for the install process is not very good. For example, the issues involving the data warehouse are really a big pain point. I had to look at over a dozen topics about this issue in the forums to get it working. Fortunately, the Jazz forums are very helpful (this topic is an example). I am getting though all of this with the help of the forums and authors like you and others going through this experience.

Thanks again,

-Walter

Hi Ralph,

Thanks for the suggestion regarding documentation. I am more than willing to help out with documentation. Please understand that it was just an observation.

I do appreciate the forum having a lot of information that really is helpful. This particular topic has helped me get thru some installation "bumps" and I am now at the point where I have installed a new V3.0.1 Jazz Team Server. The "jts" part is all set up and seems to be OK.

I am now going thru the configuration of the "ccm" application. The issue I have right now is configuring the database for the "ccm" application. I followed the steps for setting up a database in the "Interactive Installation Guide" to create a new database named "ccm". When I go to configure the "ccm" application via the JTS setup web page I get the following error: "descriptor must not be null". This may be a problem with something I did and I am following up with our IT folks here about it.

I do have a sort of related question t this.

I am using "ccm" even though there is an existing database on the database server named "rtc", which was being used for RTC v2.x. I am wondering if I should have installed the "ccm" application with a root context of "/jazz" (used for v2.x) instead of "/ccm". This is described in the ""Interactive Upgrade Guide". I think I could uninstall the "ccm" application and reinstall it with the old root context. Maybe that would help.

Thanks,

-Walter