Hello,
if I export a .Net-iView (for integrating an external application) in EP5 and
import it afterwards into the PDE (ep60sp2), I can see the channel and iView name
correctly migrated to a folder (below Portal Content/Migrated Content/EP 5.0/iViews)
but trying to view the iView always leads to the error message:
' .Net iViews werden nicht unterstützt'
What does this mean? The feature list of EP6SP2 states that URL .NET iViews can be
migrated.
Thanks for hints in advance.
Best Regards,
Rüdiger
This means what it says.
.Net iviews are not support by EP60.
BR, Oliver
Hi Oliver,
sorry for being imprecisely in my question. I intended to ask:
What is the functional replacement of EP5 URL-.NET-iViews in EP6?
Because of the fact, that the migration fails for this type of our iViews,
we have to implement them newly by the corresponding means of EP6.
Are URL-iViews to be used for the integration of an external (HTTP/S)
application?
Best Regards,
RÃÆ’¼diger
PS: May be the abovementioned error depends on our iViews, but if this result
is common, this feature should be dropped from your feature list.
Hi Ashley,
our current point of view is to re-create them
manually(!) based on com.sap.appintegrator->Generic.
In order to provide necessary URL parameters, we
added a system template, created systems derived
from it and defined aliases for them.
These systems (resp. aliases) are then used in the appintegrator-wizard.
Best regards,
Rüdiger
According to EP6 documentation I have seen (some presentations pulled from this site even), you are quite correct that .NET iViews are not NATIVELY supported for EP6 as they were in EP5. Just think about it for a moment....this is largely because EP5 was IIS-focused where EP6 is not. The approach suggested in the above noted documentation says that .Net iViews are supported via the .NET connector. So basically, .Net iViews can be thought of as just another "information source" hanging off the portal (ok, "integrated" if you prefer verus "hanging off"...haha). It's nothing "magical" really. Just think of them kinda, sorta as non-native web services. Hope this helps.
Christopher Solomon
Add a comment