Migrated EP5 BW iViews get 500 response

[] [] [] [] [] [] [] [] [] []

Symptom

Migrated BW iViews from EP5 content, which set the property ‘Cache Level’ to ‘User’, get 500 response status during runtime.
Other terms

EP5 content, migrated content, BW iView, 500 response, Cache Level
Reason and Prerequisites

Prerequisites:
Migrated BW iViews from EP5 content that run on portals later than EP5, and their property ‘Cache Level’ is set to ‘User’.
Reasons:
When the property ‘Cache Level’ is set to ‘User’, The AppIntegrator is running the iView using a different component called ContentFetcher, and the request generated is sent to the BW which doesn’t know how to handle it.
Solution

The property ‘Cache Level’ should be set to ‘None’ in those iViews that get 500 response status.
The configuration can be done via the property Editor of the iView by the content administrator.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment