Integrating Content into the NWCE
Portal
Purpose
Using a portal, your business users can reach all types of enterprise information they need to complete their daily tasks, through a single point of access in a Web-based environment. This information includes SAPapplications, third-party applications, databases, data warehouses, desktop documents, and Web content and services. The portal makes it possible to search internal and external sources, and to access both structured and unstructured information from any geographical location throughout the organization.
The NWCE portal can function purely as a development or test environment for running composite applications, or it can function in a production environment by exposing its content to a remote portal.
This topic lists the steps you need to perform to integrate your applications, which include composite applications created in NWCE, as content objects into the portal platform.
Prerequisites
● You have fully configured the portal.
More
information:
Configuring the
Portal
● The applications you want to integrate as content in the portal have been modeled and developed. The applications must also be deployed in a way that the portal can access them.
More
information:
Developing and
Composing Applications and Generic Portal
Application Layer (GPAL) Repositories.
Process Flow
...
1. Configure connections to back-end systems.
To enable back-end connectivity to applications, such as composite views and processes, you can configure Remote Function Calls (RFCs) and Web services in the SAP NetWeaver Administrator (NWA). However, to set up back-end connectivity to BI composite and SAP transaction iViews, use instead the portal system landscape or portal APIs.
2. In the Portal Content Studio, do the following:
a. Create worksets and roles (see Roles and Worksets).
b. Create portal pages (see Portal Pages)
c.
Create iViews/pages
based on the deployed applications (see
Integrating
Applications into the Portal and Working with GPAL
Repositories).
d. Integrate the iViews and pages into the worksets and roles you created previously (see Adding Content Objects to Roles and Worksets).
e. Configure and test the content in the portal runtime.
Note that you can use alternative methods for creating portal content:
○
The Portal Content
Modeling tool in the Visual Composer environment allows you to create portal
content, including iViews, pages, worksets, and roles. For more information,
see
Modeling
Portal Content with Visual Composer.
○ The XML Content and Actions tool in the portal allows you to upload an XML script and automatically create semantic portal objects (and perform actions, such as assigning roles or deleting content). For more information, see XML Content and Actions.
3. Configure navigation parameters and settings (see Navigation).
4. Assign user permission settings to content (see Portal Permissions).
5. Assign users and groups to roles (see Assigning Roles to Users and Groups).
6.
(Optional) Set user
mapping (see
User Mapping and the
Portal).
7. (Optional) Transport your portal content to a test or production system (see Transport of Portal Objects).
Optionally, you can use the federated portal network capabilities to share content and applications running in the NWCE portal and integrate them into an existing remote portal running on SAP NetWeaver 7.0. For more information, see Running Content in a Remote Portal.
More Information
Logging On to / Off the Portal
Portal Administration Tasks by User Roles