Pluggable Content Management Solution?

Greetings, I'm new to Content Managment and Interwoven and I have a couple of questions. I am currently in the process of refreshing a client's J2EE-based website. My client is considering using Content Management, but this decision will not be finalized until well into our re-design.

My main question is whether anyone has experience with creating a J2EE application that allows Interwoven to be "plugged in" at a later time? From the reading I've done so far, it appears that sites that leverage Interwoven are generally designed from the ground up around Interwoven Teamite.

Are we shooting ourselves in the foot by creating a J2EE solution and then trying to add Interwoven Teamsite at a later time or is it possible to craft a solution that will allow us to fully utilize Interwoven Teamsite at a later time?

Thanks for any help you can provide that will help me get a handle on this!

Josh H.

Find more posts tagged with

Comments

nipper

It is always easier to add it in the beginning

That being said, 90% of the implenentations I have done, was after the fact

Migrateduser

Hmmm, ok, that makes me feel a bit better.

Would you happen to know where, on this site or otherwise, I could look to find an example architecture diagram of how Interwoven would interact with an existing J2EE architecture? I'm having trouble visualizing where my J2EE app would end and Interwoven would pick up. I want to make sure our redesign takes this into account and we don't design ourselves out of using Interwoven in the future.

My concern is that we'll design our solution using standard J2EE technologies and then when it comes time to move to Interwoven, we'll have to start over from scratch (at least on the front end)

You'll have to forgive me for my ignorance, but this whole Content Management thing is new to me and I'm trying to get a grasp of how it works with Interwoven.

Thanks again!

Josh

nipper

I certainly hope you have a IW consultant coming in or an integrator. This is not really something you can expect to design correctly froma couple of architecture slides.

That being said, try searching the tech library, you may find some stuff to give you an idea how it will work.

Migrateduser

Hehe, no, we definitely would NOT try to implement a solution based off a few architecture diagrams. In fact, the actual IW implementation is outside the scope of my project.

My only goal is to try and identify how the current project can be implemented in the best possible way to support eventual migration to a CM environment. I am hoping to gain a better understanding of how and where the TeamSite system ties into a traditional J2EE application. If designing our current system using traditional J2EE technologies and patterns will mean that when we move to Teamsite, much of the web app will have to be re-written, then my recommendation would be to pull the Interwoven implentation forward and implement it at this time.

However, if Interwoven TeamSite integrates with a J2EE app in such a way that we can do our re-design now, and simply replace the front end with a TeamSite Content Managed solution, then I would proceed down that path.

Thanks for your advice, I'll continue searching the Library.

Josh

reddyl

TeamSite & J2EE integration points

- TeamSite & DataDeploy pushes data to a database and J2EE application can pull the data from database for rendering content to the users.
- TeamSite & OpenDeploy pushes xml data to the filesystem and J2EE can pull the xml files for rendering content to the users.
- TeamSite & OpenDeploy can generate either static pages or dynamic JSP pages that can be deployed to the J2EE application server.

TeamSite separates content and presentation using Forms Publisher tool. This allows content authors to add content without the knowledge of HTML, JSP, ASP, ...
- All the content is stored in the from of xml called the Data Capture Record (DCR).
- Content authors can add or modify the existing content using HTML forms called Data Capture Templets (DCT).
- Presentation Template (TPL) is combination of perl & the output format similar to JSP file containing HTML & JSP to generate static, dynamic content.

What are the best practices in J2EE application to separate content from the presentation logic?