SAP Enterprise Portal

SAP EP ADMINISTRATION

SAP EP Basics

Installation and Post Installation

Content Administration

Administration Activities

Portal Security

 SAP AG 2002
 Administration Activities

•Connecting to SAP Backend Systems

•Portal Backup and restore

•Transporting Portal Content

•Installing Support Packages

•Configuration of Systems landscape

 SAP AG 2002
 CONNECTING TO SAP SYSTEMS

 SAP AG 2002
 SAP AG 2002
 Connecting Using a Dedicated Application Server

Following are some of the properties required for connecting to the SAP backend system
using a dedicated application server:

• Application Host Host name or IP address of the application server

• Gateway Host Host name of the gateway server

• Gateway Service Service name or port number of the gateway server

• Logical System Name Concatenation of System ID + CLNT + Client number (for

example, XYZCLNT030)

• SAP Client Client number of the SAP backend system, such as 001

• SAP System ID Three-digit system ID, such as D11

• SAP System Number Instance number of the SAP backend system, such as 01

• Server Port Port number of application server: 32 + SAP System Number (for

example, 3201)

• System Type Type of SAP system, such as SAP_R3, SAP_BW, or SAP_CRM

 SAP AG 2002
 SAP AG 2002
 If the portal user is not the same as the SAP backend user, you must set up User
Mapping

1. Navigate to User Management | Identity Management in the top-

level menu of the portal. Enter the user you are going to use for
connecting to the backend system.
2. Click Go.
3. Select the checkbox next to the user. Click Modify, and navigate
to the User Mapping For System Access tab in the User Details
screen.
4. In the System Selection screen, select the system object created
in the previous steps and enter the user details such as Mapped
User ID and Mapped Password. These user credentials are passed
on to the backend system for validation, when the portal user tries
to access an iView that fetches data from the backend system.

 SAP AG 2002
 Now you can test the connection to the backend application:
1.      Select Connection Tests from the Display drop-down. Three types of system
connection tests are available, as shown next:
2.      Select the checkbox Connection Test For Connectors to test the connection
with the SAP R/3 backend system.
3.      Click Test.

 SAP AG 2002
 Portal Backup and Restore

A backup and restore is usually required to prepare for the following:

s
• Hardware or file system failure
• Damage due to viruses
• Issues during installation of software patches and upgrades
• Potential human mistakes, such as accidentally deleting some files or changing
configuration
• Loss of system or data due to theft

 SAP AG 2002
 Transporting Content

Transport Package
Exporting Transport Packages
Creating EPA Transport Packages

 SAP AG 2002
 SAP AG 2002
 SAP AG 2002
 Installing Support Packages Using Java Support Package Manager

Java Support Package Manager (JSPM) is a software deployment tool

that can be used for installing business packages, software components,
and SAP kernel binaries.
 
JSPM can be used for the following:
• Installing support package stacks and support packages for existing
software components
• Installing or upgrading business packages
• Updating SAP kernel binaries, Software Delivery Manager (SDM), and
Internet Graphics Service (IGS)
• Self-updating JSPM so that the latest version is used
• Deploying new SAP and non-SAP software components
• Installing additional usage types such as Enterprise Portal (EP) or
Process Integration (PI)

 SAP AG 2002
 Prerequisites for Installing SP Stacks and Support Packages

Back up the AS Java and Database Instance

Check Names of EXE and Profile Folders
Download Archives into the JSPM Inbox Directory
Increase the SDM Timeout
Check for Sufficient Free Space for the J2EE Engine
Deploy the Required JSPM Support Package Level

 SAP AG 2002
 SAP AG 2002
 SAP AG 2002
 SAP AG 2002
 SAP AG 2002
 SAP AG 2002
 Implementing Federated Portals

Content Federation
Portal Federation

Advantages of Federated Portal Network

Content Sharing Modes—Reusing Remote Content
Remote Role Assignment
Remote Delta Links
Remote Application Integration
Usage Scenarios for FPN

 SAP AG 2002
 SAP AG 2002
 SAP AG 2002
 Implementing External Facing Portals

Features of an External-Facing Portal

Implementing an External-Facing Portal

When implementing an external-facing portal, you should be focused on enabling
improved performance and easy-to-use features:
1. The user administrator sets up anonymous logon and self-registration scenarios if
required. Refer to the relevant chapters in this book for information on setting up these
scenarios.
2. The developer develops light content specifically for use in the external-facing portal.
Content created for the external-facing portal should be of static nature as much as
possible. Avoid using HTMLB, client-side eventing, out-of-the-box KM iViews, and
related links for pages and iViews.
3. The system administrator assigns that content to the users, groups, or roles.
4. The system administrator configures the navigation cache by changing the
appropriate J2EE parameter.
5. The developer creates or modifies the light framework page to suit the company
requirements for branding, look, and feel.
6. The content administrator customizes the light framework page by replacing the
standard navigation iViews with the custom-developed navigation iViews.
7. The system administrator customizes the styles using the Theme Editor.
8. The system administrator assigns the light framework page to the users, groups, or
URL alias for accessing light portal using desktop display rules. The users who use the
URL for light portal (http://<host>:<port>/irj/portal/light) will be assigned the light
framework page and the users who use the default portal URL will be assigned the
default portal desktop.

 SAP AG 2002