Creating Portal Content
Purpose
This IT process describes the steps you need to perform to generate content in the portal while implementing the Providing Uniform Content Access scenario variant.
Portal content refers to modular entities that interact at runtime to retrieve and display up-to-the-minute information to users in the portal interface. Users can also interact with content in the portal to perform their daily tasks. Portal content consists of iViews, pages, worksets, and roles.
An iView is the smallest unit of information that provides access to applications, reports, services, and information repositories. A page organizes the layout of iViews in the portal interface. A workset is a cluster of related pages and iViews that a user needs to complete a specific task. A role defines a user's responsibilities in the organization and contains the relevant worksets needed to accomplish it.
Portal content is available from a multitude of sources:
● Import ready-made role- or industry-specific business packages into your portal environment from the Portal Content Portfolio on SAP Developer Network to speed up your portal implementation.
● Develop custom-made iViews using content development kits, such as the Portal Development Kit (PDK) and then deploy them in the portal.
● Create iViews directly in the portal, using the iView Wizard, from iView templates shipped with the portal. iView templates provide an easy way to create content in a code-free environment.
The following portal administrator roles participate in this IT process:
● Content administrators
● System administrators
● Super administrators (may function as a substitute for the above administration roles)
Use of the Process
This process is part of the following IT scenarios:
IT Scenario |
Scenario Variant |
Prerequisites
● You have configured your portal (see Configuring the Portal).
● You have installed the usage type Developer Infrastructure (DI) if you intend to develop your own applications and content for the portal.
● You are logged on to the portal as an administrator. Each step in the workflow indicates the administrator role required to complete the step.
● You have the necessary portal permissions to work with the required portal objects.
Process Flow
1. Generate portal content:
a. The system administrator imports ready-made business packages from Portal Content Portfolio on SAP Developer Network at http://sdn.sap.com (optional).
b. Content developers develop custom-made content applications and deploy them in the portal (optional).
c. The content administrator creates iViews based on your own custom-made iView templates or those shipped with the portal.
2. The content administrator sets up content objects and role navigation structures:
a. Adjust imported business packages (optional).
b. Configure and test iViews in the portal.
c. Create portal pages with assigned page layouts and iViews.
d. Create worksets and roles.
e. Configure navigation settings that affect the runtime display of content.
3. The content and system administrators define portal runtime display settings for users, including portal themes, framework pages, portal desktops, and display rules.
Result
Portal content relevant to your business scenario is available in the portal. The content is now ready to be assigned to business users in your organization.
The next steps in implementing a running portal can be performed. See Maintaining the Portal.