we did it

[Christoph Straßer]

Migrated our old productive WSM 10.1 SP2 / W2K3 - system yesterday to a new W2K8 R2 with WSM 11.0 HF3. (Have about 30 projects, some of them are pretty large.) Almost everything looks good so far. At least compared to the older versions. ;-)
We are looking forward to next week, when our authors / content editors start working with the new 11.0 - system. Personal feeling is good, but you never know whether users raise some (error-)conditions no one expected before...

[Manuel Schnitger (OpenText)]

Congratulations! We just had a Usergroup meeting in Mannheim/Germany
today and I also just heard very good results when users switched from
10.x to 11! Please let us know how you proceed!


On Jun 9, 11:08 am, Christoph Straßer <christoph.strasse...@gmail.com>
wrote:

[RedDot in Toronto]

Do you have time to outline any gotchas that you came up against while migrating?

[Jian Huang]

Congrats too.

Many of the 7.5 to 10.1 upgrade blocker still applies:

1.  reddot cannot be within rendertag
2.  container cannot be used pull in css or js by enabling "Insert placeholder for page in container" in the css/js template property
3.  if css/js is managed as content class and referenced via anchor in Management Server, this http://simplyreddot.blogspot.com/2011/12/managing-js-css-xml-as-content-classes.html
4.  RQL preexecution within template code

To 11
1.  If still using ASP RQL, change to new COM object in object connection string.

That's it.  All of them shouldn't even be a problem if best practices from 7.5 are followed.

-Jian

[Christoph Straßer]

In terms of how you build the project there are no changes between 10.x and 11.0 aside from RQL-COM-object that does not exist any more. (We did not used this in the past.) Our first projects startet with Version 5.6. We had to change some details when we migrated vom 9.0 to 10.0 about two and a half years ago.
Between 10.1 und 11.0 there was only one project (out of about 30) where we had to do a template-modification. (We used the old MSSOAP-COM object to call a webservice and replaced this with a custom rendertag which calls the webservice via C#/WCF-Code.)
We had a problem with large RQL-statements we send to the (new) RQL-webservice. .NET / WCF limits the messagesize per default to 8kb. We had the modify the web.config. This will be added to future revisions of the MS-documentation.
At the moment there is left one unresolved problem, that affects the publication via webservice from MS to DS. It seems like MS "forgets" to publish some content´s to the DS. The publishing-report and the MS-Logs say all contents have been published. When you look to the DS some of them are not there. We try to figur this out since last friday together with the OT-support.
Performance is - compared to the older versions - much improved. (The nightly publications of our large projects takes somewhere between 1/2 and 1/3 time compared to before. In most (but not all!) usecases a author runs through in his daily work the MS responses faster than before.)
We used a W2K3 Server before and stepped to a W2K8 R2 Server. Some changes within the Windows Server may affect you. (eg you have to configure your windows firewall to allow FTP-Transfer) It´s not a real problem. With some W2K8 Server - KnowHow you should be able to solve them.
I realy hope OT continues to improve the MS within the next months and years. They did much important work at the backend with 11.0 and should have paved the way for future versions. There is still much work to do. As an example the asset managers did not changed much since 2005 or 2006. (inconvenient UI, missing features like multi-upload for authors, only one subfolder-level, ....)
Just ask your questions to specific topics. I´ll try to answer them.

[Morgan Ritchings]

We had a similar experience with a v9 to v11 hf3 upgrade for a client. With a mix of publication setting amendments and the upgrade we were able to cut publication time from 12hours down to about 6 for a fullsite publication of approx 8gb of html and assets. SmartEdit responsiveness also "feels" better though this could be purely psychological. I have to credit OT for a solid release.

 - Morgan

[Morgan Ritchings]

Hi Christoph,

I think our client is hitting your same wcf message size limit with saving back huge content classes and text elements with a very large amount of content (either are not ideal but worked ok back in 10.1 sp2). Do you mind sharing which web.config you updated and the option that was added?

Many thanks,

 - Morgan

On Wednesday, 20 June 2012 22:24:22 UTC+10, Christoph Straßer wrote:

[Christoph Straßer]

Have a look at http://www.opentext-usergroup.org/doc/ext/Erste-Erfahrungen-mit-OTWSM11.pdf (pages 19, 20)

If this does not help: Please copy the error message into your response.

[Christoph Straßer]

Attached Screenshot of our modified web.config.

[SLC Webmaster]

This is good news to hear. Upgraded a few weeks ago to 11 HF 3 from 10.1 and waiting for the next few hot fixes to fix some bug tickets I have submitted. Users seem to be happy. Publication time was greatly reduced. There are some issues with publication since all assets are database stored and not locally on the OpenText (We do not own Asset Manager), but those bug fixes are submitted and I think publication times will be even faster with a HF.

On Saturday, June 9, 2012 5:08:00 AM UTC-4, Christoph Straßer wrote:

[Joel Kinzel]

Just curious what bugs you've found? We are getting ready to upgrade and any bugs would be good to know about going into the upgrade! 

[SLC Webmaster]

Joel,

 

Most of the bugs centered around me begining able to use the FCKeditor with Firefox. I try and use the tool as out of the box as possible and my upgrades usually go very well. (learned that way back in 1999!) I allow users to customize things like tables and graphics sometimes outside of CSS and need to use either the supplied RedDot Text editor or FCKeditor becuase of the easy end user interfaces. Most of the FCKeditor issues are the same as in version 10 if you are using that version. Here is a summary of my bug tickets for FCK. Jump Marks will set in content but not be found to link to.(You can set a jump mark target in the text and then link to it in the RAD editor if necessary) I use the Database to house my assets and there are issues with using FCK to link to files, the issues are fixed partically in a HF but it is only working for certain file types. (Images but not PDF files, weird but true) My workaround for users who want to use Firefox and FCK is to upload their files using the RADeditor (in Firefox) and then switch back to FCK. I only recommend this for seasoned editors who can understand the concept. I have all levels of users on the system. There are still limits on file size due to IIS (out of the box) on MS Server 2008 R2. I use MS SQL 2008 R2 as well.

 

If you use the database to house your assets and do not use the Asset Manager (we do not own it) and try and use the Folder jobs in SmartTree named Asset Manager Maintenance or Asset Control they do not work in version 11 with HF1-3. They work fine in version 10. The only work around I was offered until the HF comes out with be to Transfer Data Storage folder content into the local server. This is not an option as there is no way to un-convert it back to the database storage for ease of Exports and Imports.

 

One huge note with using the Database to store your assets is when your publication jobs run they will publish ALL assets even if they are not modified. This is in a bug ticket I have too. BUT!!!! even with all my assets publishing from the database storage my publication times are cut in HALF! I can't wait till the bug fix for the database storage publication to be fixed becuase I think the publication will be even faster.

 

I have not noticed anything major in the RedDot Text Editor if you are using that BUT if you want your users on multiple platforms. Letting them switch between IE and FireFox and highly customize things like table/images users will have to stick to one platform (IE or Firefox) or else some of the code will be wiped when the go back to the RedDot Text editor becuase of the way it codes things like Image right/left etc and Table colors.

 

I can explain anything else in detail if necessary I don't want to get to long winded.