Skip to end of metadata
Go to start of metadata

For additional information you may also visit the SDN page of Web Page Composer.

 This page focuses on SAP NetWeaver 7.0. We plan to add the new SAP NetWeaver 7.3 information soon.

Questions

General

What is Web Page Composer?
What are the content development tools provided for WPC?
What are the major steps in creating a website with Web Page Composer?
How does an end user navigate to WPC content?
Is there an additional license needed to download and use Web Page Composer?
How do I install WPC?
In what releases of the SAP NetWeaver Portal will WPC run?
What parts of KM and Portal technologies are used with WPC?
What roles are needed to use WPC?
What is a Web Resource Type?
What is a container?

Functionality

How does WPC integrate with the Portal Content Directory (PCD)?
Does WPC work with the light portal framework page?
Does WPC work with the standard portal framework page?
How does TREX search work with WPC?
What security is provided for WPC content?
How can I delegate authority to create WPC content to various departments in my company?
What Page Layouts are provided out of the box and how can I create my own Page Layouts?
Are portal style sheets used in WPC?
How can I create my own Web Forms?
Does WPC provide versioning?
Does WPC provide document workflow?

Content Integration

What about using standard HTML pages in WPC?
How does it integrate with other Web Content Management Systems?
Can I use Front Page or Dreamweaver or other WCM tools to create content?
Where does WPC store its content?
Can content come from other KM repositories?
How are document properties handled Can I use my own properties?
Can I separate specific content for my website versus content used across websites such as company logos, images, etc?
How can I use XML Forms Builder with WPC or is it replaced with the Web Forms?

Answers

What is Web Page Composer?

Web Page Composer (WPC) helps to bridge the gap between portal content and knowledge management. It is a new authoring tool for web content and web pages based on standard Knowledge Management and Portal functionality. WPC supports company-wide intranet, extranet or internet scenarios using portal and knowledge management capabilities of SAP NetWeaver. Additionally, WPC enables business users to create and publish web content and web pages in the portal. Finally, management of web sites may be delegated to the business users through WPC.

What are the content development tools provided for WPC?

Web Page Composer is delivered with the following tools:

  • Site Explorer:
    • Enable business users to manage web sites including web content, pages and navigation structures
  • XML Editor Framework:
    • Document definitions based on XML schemas
    • New document types can be added via configuration
    • Allows complete separation of content, layout and style
  • Page Editor:
    • Publishing and versioning on page level
    • Dynamic link management (for internal links)
    • Flexible and configurable page templates
    • Rule-based design - customizable rules define which content types can be added to which container
    • WYSIWYG editor with drag-and-drop support
    • In-place editing from the end-user perspective
    • Staging for pages

What are the major steps in creating a website with Web Page Composer?

The major steps are:

  • Create a website
  • Create web content
  • Create a Web Page
  • Create Navigation Nodes and assign pages
  • Connect the website to a Portal Role

How does an end user navigate to WPC content?

First the end users must have read permission to see the content.  This is done via ACLs in KM. The end user then is provided one or several roles which contain WPC sites with web pages which display in the detail navigation area of the portal.

Is there an additional license needed to download and use Web Page Composer?

No, the productive use of Web Page Composer is covered by the standard SAP NetWeaver or Business Suite license.

How do I install WPC?

WPC is an add-on to a particular SAP NetWeaver support package stack. The first generally available version is based on SPS13 and can be downloaded as a separate installation from the service marketplace. It is deployed as SCA file in the portal. You can download the package by accessing http://service.sap.com/swdc and searching for "Web Page Composer" under Downloads > Search for All Categories. For further details, refer to SAP Note 1080110.

In what releases of the SAP NetWeaver Portal will WPC run?

Web Page Composer runs on SAP NetWeaver 7.0 SPS13 and higher (usage type EP).

What parts of KM and Portal technologies are used with WPC?

WPC is built using both standard portal and KM technologies.  It uses a special KM repository to store the content for web pages and navigation structures although any content stored in KM can be used as content in a web page. In addition, there are new portal components which optimize the page building and rendering process for web content.

What roles are needed to use WPC?

The WPC_Editor role is the only one needed to create content in WPC.  Of course, other roles can be created and used for end users.  The Content Administrator role is required to connect the navigation structure (navigation.wpc) of a website to the role or workset in the PCD.  This connection is only done once per web site. All subsequent changes to the navigation are done in WPC by the Web Content Managers.

What is a Web Resource Type?

The Web resource type concept represents an enhancement to the existing resource type concept in that it supplies additional parameters in addition to the standard resource type definition. For example, a Web resource type is used to define which layout is used to display a resource of the type in question and to define parent-child relations between different web resource types. Some delivered Web Resource Types are: web link list, weblog comment, web navigation, simple_navigation, web page, web rss link list, web sponsored link, home_page, news_page, three_column_page, two_column_page, web article, web banner, web feature, web html file.

What is a container?

Containers are the content areas of a page. In the page editor, you can use Drag and Drop to pull content into the available containers. In addition, the container configuration allows you to define rules which MIME types or resource types can be used in a specific container.

How does WPC integrate with the Portal Content Directory (PCD)?

Some configuration steps have to be followed so that Web site owners can integrate iViews into Web pages.

Not all iViews are suitable for Web pages. Note the following limitations:

  •  Web Dynpro iViews are not supported.
  • When you add iViews to Web pages, you cannot set any parameters

Does WPC work with the light portal framework page?

WPC is designed to run in the light portal framework page (LFP) to enable an optimized, web-like behaviour (e.g. optmized caching, browser navigation). Most of the iViews such as KM Navigation iViews will automatically load the required libraries (e.g. HTMLB) even within the LFP. However, you can also use the standard portal framework page if some portal content does not support the LFP..

Does WPC work with the standard portal framework page?

WPC is also designed to run in the standard portal framework page but you will lose some of the capabilities provided by the light portal framework (see online documentation).

How does TREX search work with WPC?

TREX is used to index the content in WPC just as any other KM repository. The difference with WPC is that when an item in the search results is selected, the item is displayed in the context of the web page in which it is used. A special TREX parameter is used to index and return the WPC search results.

What security is provided for WPC content?

Security is provided by the standard KM and portal security concept (ACLs, security zones). Access to portal pages and iViews is determined by the user's role just like any other portal application.

How can I delegate authority to create WPC content to various departments in my company?

WPC allows sub-sites to be developed under a website. This capability permits the website administrator to delegate site development to a specific group or department. For example, under an HR website, there can be sub-sites for Benefits, Policies, etc. which are developed and controlled by a particular group.

What Page Layouts are provided out of the box and how can I create my own Page Layouts?

Yes. SAP delivers five page layouts with WPC: Home Page, News Page, One Column Page, Two Column Page and Three Column Page.  These are JSP pages.  You can create you own JSP pages in the NetWeaver Developer Studio by copying these pages or creating your own from scratch.  Once the new layout is completed, additoinal WPC configuration needs to be completed (see online documentation).

Are portal style sheets used in WPC?

No. SAP delivers additional style sheets for web forms and for web page composer content. Currently, WPC does not use stylesheets managed by the portal theme editor, and instead WPC has its own stylesheets located in the /etc/wpceditor/css repository.  Web forms use a combination of XSL transformations (stored as XSL files in /etc/wpceditor/styles) which reference the corresponding style classes and IDs of the WPC stylesheets to render the web forms at runtime. It's strongly recommended not to change the default styles and transformations delivered by SAP but to create custom stylesheets and transformations (or work on copies of the original ones).

How can I create my own Web Forms?

Web Forms are developed in xml by defining the standard elements and properties that should be part of the web form (see online documentation). SAP provides some out of the box forms such as an Article, Banner, Link List etc.  You can copy and modify these xml files and perform the configuration needed in KM to make them available to your WPC editors.

Does WPC provide versioning?

Yes, versioning can be turned on for web content and pages. You set versioning by accessing the details for content or a web page and then going to Settings>Versioning>Enable Versioning.

Does WPC provide document workflow?

The first release of WPC does not include the KM document approval process at this time but is planned for the second major release of WPC.

What about using standard HTML pages in WPC?

Standard HTML pages can be utilized in WPC out of the box. To use HTML in WPC, you  either upload the HTML file or use an existing HTML file which is stored in one of the connected repositories.

How does it integrate with other Web Content Management Systems?

HTML pages from other Web Content Management Systems (WCM) can be uploaded into a WPC Folder or connected via repository manager and used on Web Pages.  However, style sheets and templates used in the WCM are not automatically accessed by WPC. These must be uploaded and configured in KM.  KM supports relative links in HTML documents so it may be necessary include any dependent files in the same folder as the HTML document.

Can I use Front Page or Dreamweaver or other WCM tools to create content?

Yes, however the style sheets that are used with these products must be incorporated into KM to display HTML pages as designed.

Where does WPC store its content?

The Web content repository (ID: /Web_Content) repository is the central storage location for Web content. One creates all Web sites in the /Web Content/Sites folder. One can also create shared content that is used throughout the company in the /Web Content/Cross-Site Content folder. This might include the company logo or other objects that need to be used in a uniform manner on all Web sites.

Can content come from other KM repositories?

Yes. Content may be used from other repositories if content authors can access other repository content.  Typically Global and Site Entry Points are used to access other KM repositories in WPC.

How are document properties handled?  Can I use my own properties?

Document properties are handled as they are in standard KM.  You can create your own properties in the Property Metadata Service in KM Configuration and then use them on WPC content (documents, forms, HTML pages etc.). Currently, the validation of allowed values is not supported for web forms (planned for upcoming version). Furthermore, also the use of dependent properties is not supported by XML forms and WPC in the current version.

Can I separate specific content for my website versus content used across websites such as company logos, images, etc?

Yes, a cross-site content area is provided in the WPC repository.  This enables you to upload logos etc that can be accessed by any website developer.  KM permissions can also be used to limit the access to certain cross-site folders. In addition, you may also use a separate repository for specific content types (e.g. an image library) which allows you to control specific services or caching options independent of the standard web content repository.

How can I use XML Forms Builder with WPC or is it replaced with the Web Forms?

The XML Form builder can be used to create forms for user input such as news items. This is standard KM functionality. The iViews in which these forms are displayed can be used in any WPC web page. To maximize the benefit of WPC, it is recommended to use Web Forms when applicable for your scenario.

  • No labels

2 Comments

  1. Hi,

    Is there any oncoming support of Web Dynpro iViews within WPC,
    This limitation is astonishing these days with the ubiquity of WD!

    Thanks.
    Best regards,
    Guillaume

  2. Unknown User (wqokgqy)

    Hi,

    Which version of WPC supports workflow?

    Regards,

    Raj