Replacing OnDemand Fat Client with Web browser based GUI

[bblunt]

    We've never used WEBi or Content Navigator.    We're in the process of upgrading a system to OnDemand 9.5 running on RedHat Linux 7.0.   The system has about a 1,000 users and we've been asked to build a web browser based GUI to replace the OnDemand 9.5 fat client for almost all the users.    Should we build our own browser based GUI connecting to ODWEK Java APIs or would Content Navigator be a good fit to completely replace the OnDemand 9.5 fat client for most users?  All the users would just be viewing data stored in Content Manager for OnDemand without any update access.   They would be viewing mostly line data documents, but there are some AFP documents.   If Content Navigator is a good fit for this purpose, does anyone know of any good documentation specific to using Content Navigator as a replacement for the OnDemand fat client?
    We have a home grown Java application that connects to another OnDemand 9.5 system through ODWEK Java APIs to get a small subset of data.   That system uses AFP2PDF to convert our AFP documents to PDFs for display on the client PC.

Thank You,
Brian Blunt

[Justin Derrick]

That's an analysis that only you can do.

If you have a tool, that's fine -- use it where it makes sense.  But Content Navigator is amazingly flexible, customizable, and expandable.  It would be my default answer in your situation.  You can probably give your customer much more value by starting with ICN, and developing custom components where they're required.

-JD.