Upload Content and Actions 

Purpose

By means of an XML-based script, you can automate and simplify the creation of semantic portal objects (for example: iViews, pages, roles, worksets, systems etc.) and perform actions (for example: role assignment and content deletion) in the portal. A parser interprets the XML in the uploaded file and generates content and performs actions directly in the Portal Content Directory (PCD) based on this XML.

This is useful for automated mass content creation, bypassing the need to invoke various content wizards and editors. Advanced users can use their knowledge of the capabilities and limitations of the tool to expand its uses to other possibilities, such as performing batch operations and making pinpoint modifications within a large content base.

For detailed documentation, refer to the Uploading Content and Actions to the Portal with XML How-To Guide, located at service.sap.com/nw-howtoguides ® Portal, KM and Collaboration ® Portal.

This guide describes the elements and attributes required to code a semantically correct XML file for defining portal objects and actions that are currently available. The guide also includes code samples and how to upload an XML script.

 

Integration

You upload an XML script to the portal using the Content and Action Upload tool. By default, it assigned to the standard System Administration role, under Transport ® Upload Content & Actions.

This feature, formerly known as the Generic Creator, was previously available in the PortalAnywhere development environment as a SAPinternal tool. It now officially supported from within the portal user interface.

The implementation uses SAP-provided handlers for semantic portal objects and actions. For example; the PageHandler, PackageHandler, and RoleHandler.

Prior to uploading an XML file in the portal, the portal content and action definition needs to be coded into semantically correct XML that can be parsed and executed by the portal. Coding the XML is possible in a number of ways, including the use of scripts that can transform a Microsoft Excel format or a text format to XML. Such services are not supplied by SAP.

Uploaded XML files are able to irreversibly execute any number of actions in the portal, including the overwriting and deletion of existing content. Uploading an incorrect XML file may cause permanent damage to the portal. It is highly recommended to perform test runs initially on a non-production portal installation.

Due to the potential harmful effects of this tool it is recommended to remove access to it for all portal administrators, except for those who are authorized and trained to use it.

 

Features

The architecture of this XML-based implementation is based on the following:

·        An engine that is able to parse XML and execute actions, while providing clear and detailed reports to indicate successes and failures of each stage. The engine is modular, thus allowing it to be extended for custom semantic object types.

·        A set of handlers, each one dealing with a different semantic object or action.

·        A tool in the portal allowing administrators to upload an XML script.

 

Constraints

·        The portal’s transport (import/export) mechanism should be used instead to physically move content existing in a portal to another portal. The transport mechanism also provides additional functionalities, such as multi-language support. See Transport of Portal Objects.

·        The portal does not provide a means to extract existing content in the portal in its current state to XML.

·        For information, on transporting and creating permissions using XML script, see Transporting Permissions.

·        The portal does not offer an editor that enables you to view, edit, or validate the syntax and well-formedness of the XML in a file before it is uploaded.