For those of you considering and/or planning installation of MR3, be aware that (1) the Content Store structure changes and (2) the Framework Project files change (there is a new version of Framework Manager).Ã, I believe all these changes are not backwards compatible:Ã, If you use the new FWM it will not publish to the old Content Store.Ã, Ã, :o
That said, MR3 is supposed to fix a bunch of bugs, including my number one:Ã, Timeout and not being able to login again via SSO.Ã, Ã, 8)
Opher
thnks for the nice info.
Srik
Cognos almost never has forward compatibility, sometimes not even between different builds of the same version.
This is not new at all. I have been installing CRN since it's inception. An upgrade requires a complete backup of content store , removal of the directories and then a fresh installation. If you are using the default app server (Tomcat) any changes to the warproperties.xml, CQeconfig.xml and System.xml need re-added. You cannot in any situation publish an FM package from a prior version of FM to a new version of CRN.
The reasons are too many to get into but just know that it's application server related not application related. If you are using a 3rd party app server like WebSphere the changes are far fewer. Tomcat is wimpy and should only be used in environment support under 500 users. I have brought Tomcat to it's knees using JMeter on more that one occassion with just 100 concurrent users.
I have found that in FireFox 1.5 ReportNet html output cannot pagedown in MR3.
- carl s.