Skip to Content
author's profile photo Former Member
Former Member

Where to create and store static HTML content?

Hi,

We are rolling out EP 6.0.

One of our fundamental questions is where to create and store static HTML files and documents that will appear in the portal.

We've tried this approach:

1) Using Dreamweaver, we create and store HTML pages on our existing development web server. This is the same way we develop web content on our public and intranet site.

2) In our DEV portal, we create URL iViews that point to these HTML files.

The problem at this point is -- how do we move the HTML files from our development web server to our production web server AND more the portal files from the DEV portal to the QAS portal to the PROD portal?

What we've learned is that we need to move our HTML content from our development web server to our production web server AND THEN work in the DEV portal to create URL iViews that point to these HTML files. After testing and approvals, the next step would be to transport the content from the DEV portal to the QAS portal and then to the PROD portal. Since the URL iViews are always pointing to the production web server, they should stay intact through this process.

This approach isn't satisfactory to us since it involves two separate development and approval paths -- one for the web content on our web servers and the second for the portal on the portal machines.

We understand that another option is to create and store our static HTML content within the portal environment itself -- more specifically, on the CM box in the portal.

Our main questions are these:

1) What is the best approach to developing static HTML content in CM?

2) Can you use Dreamweaver?

3) What about style sheets? In early testing, we found that we could create HTML pages directly on the CM box using Dreamweaver. And when we created iViews pointing to those pages, they showed up -- but the external style sheets didn't work.

Any help or advice with this issue would be greatly appreciated!

How does everybody else handle this?

Thanks,

David

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Oct 28, 2004 at 07:33 AM

    I've heard someone mentioning that instead of using URL iviews to link to an external webserver, you create a system for the external webserver and make an iview which uses this system an points to a path on it (I think you can use SAP Connector iview for this, but it isn't very hard to make a new portal component which does this)

    Then for the quality system and production system, you only have a different definition of the same system.

    I haven't got too much details, but perhaps this way is worth chasing instead of CM

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 28, 2004 at 01:27 PM

    Hi,

    there are a lot of settings how you can implement your HTML content to the portal:

    - use KM for display

    - content inside a cm repository

    - content inside the filesystem

    - content from a webdav repository

    - create your content as a .war and deploy it as such

    - have the content inside a .par

    - external webserver outside WebAS at all

    For indexing, i.e. the navigation in the portal, it is quite tedious (and error prone) to have for each html page an URL iView.

    If you want to have a tight UI integration of the role/workset based navigation and your html index, you may want to preferably implement a navigation connector. The PDK (from SP6 on) already contains a navigation connector example that draws its index tree from an xml file. Such a navigation connector is realized as a .par.

    Most of the parts of that navigation connector could be reused for your case.

    A navigation connector can be role-sensitive also. The nodes that are provided by a navigation connector can be merged with those provided by the PCD (role/workset navigation). This is also realized in the PDK navigation connector.

    As a yet different solution for indexing content you can also use taxonomies in KM.

    There are still more possibilities, it depends heaviliy upon your specific needs/scenario.

    So these are just some ideas/suggestions.

    Regards,

    Armin

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.