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.