SAP Enterprise Portal Fundamentals Certification Questions Explanation

Question 1 Explanation: For SAP Enterprise Portal, the load-balancing solution should ensure session persistence, or “stickiness.” This means that all requests of a specific user in a single session are forwarded to the same server. Stickiness is achieved at initial logon, by linking to the IP address and local port of the load-balancing system. If one node fails, the other servers assume the tasks of the failed node without any pause in operation or loss of information.

Question 2 Explanation: Portal Content Directory (PCD) is a file system which stores roles and role components, and page-to-role relationships. It also stores deployable (PAR) and master iViews (written in Java) with their personalization data and derivations (Java iViews, External Services). The PCD stores a copy of the page catalog.

Question 3 Explanation: The portal server needs read/write access to its PCD file system.

Question 4 Explanation: Roles are maintained with the Role Editor in both SAP Enterprise Portal 5.0 and 6.0. The Role Editor is a Web-based tool for creating roles and hierarchies and for assigning content objects to roles. In EP 5.0, the Role Editor is a central tool which can be used to create and edit External Services, master iViews and work sets as well as roles. Other editors are available for the administration of pages and iViews. In EP 6.0, the Role Editor is embedded in the central administration environment for the development and administration of content: the Portal Content Studio. This administration environment can be used to call all editors for the creation and administration of content, including the Role Editor. Only roles can be created and edited in the Role Editor.

Question 5 Explanation: Authentication provides a way of verifying the user’s identity before he or she is granted access to the portal. Once the user has been authenticated, he or she is issued a SAP logon ticket that allows him or her to access all the applications, information and services in the Enterprise Portal using Single Sign-On. Since many of these applications may contain sensitive data, it is imperative that the user in question can be identified and this identity authenticated. The process of authentication is based on each user having a unique set of credentials for gaining access. For example, with user ID and password authentication, the authentication server compares a user’s authentication credentials with other user credentials stored in a data repository. If the credentials match, the user is granted access to the Enterprise Portal. Otherwise, the authentication fails and portal access is denied. The Enterprise Portal 5.0 offers the following integrated authentication mechanisms:· Authentication with User ID and Password· Authentication with X.509 digital certificates· Authentication using external mechanisms¡ Windows 2000 authentication¡ Authentication Against User Data in SAP R/3 System¡ External Web access management tools, such as Netegrity Site Minder¡ COM interface allowing you to use any kind of external authentication service Note that you must use one method of authentication for all users. The only exception is authentication with digital certificates. Digital certificates can be used as an additional method of authentication. This means that users that have a client certificate use it to logon while other users have to provide credentials using a different authentication mechanism.

Question 6 Explanation: The recommendation is that do not place more than fifty (50) objects in a single folder.

Question 7 Explanation: The Enterprise Portal Plug-In (WP-PI) enables the exchange of data between SAP Enterprise Portal and the mySAP.com components, for example SAP R/3 and SAP BW. It is a prerequisite to enable Drag & Relate and Single Sign-

Question 8 Explanation: The Page Builder assembles the pages that are displayed in the Enterprise Portal. It gets information about the navigation between pages and the layout of the pages from the roles assigned to a user. Information about which roles are assigned to which users is stored in the portal LDAP directory.

Question 9 Explanation: The operating system collector SAPOsCol is a stand-alone program that runs in the operating system background. It runs independently of SAP instances exactly once per monitored host. SAPOsCol collects data about operating system resources, including:• Usage of virtual and physical memory SAP Enterprise Portal Fundamentals Certification questions By Aravindaaravind_sapep@yahoo.com• CPU utilization• Utilization of physical disks and file systems• Resource usage of running processes• Process monitoring

Question 10 Explanation: User access to content is determined by Role definitions. A portal role is a collection of content. While portal content is developed to enable access to information relevant to the organization in which the portal is deployed, roles define the subset of content available to each functional role within the organization. Users are assigned to the role or roles that provide content relevant to them. A user has access to the content that has been assigned to all of his or her roles.

Question 11 Explanation:J2EE Engine cluster is a set of independent nodes that are addressed and managed as a single system. The cluster consists of two types of nodes: dispatchers and servers. The administrator of the system determines the number of dispatchers and servers in a cluster. Each dispatcher node is connected to all server nodes in the cluster and each server node maintains connections to all other cluster nodes. Clustering enables dynamic load balancing by distributing client requests among the server nodes in the cluster, thereby providing higher scalability and improved system performance

Question 12 Explanation: Users and passwords are defined in the directory server. To enable those users and passwords for portal logon, you must define a security configuration, using the portal tools. However, in order to do so, you need to log on to the portal. The first time you logon to the portal, you log on as a default, predefined user, called admin, using the default password, admin. After you have defined a security configuration, you may continue to log on as user admin, or you may log on with the user information defined in the directory server. The admin/admin logon provides you with access to the portal as a fully qualified super administrator. Note that administrator access is enabled via Microsoft Internet Explorer browsers only. There is no administrator access via Netscape browsers.

Question 13 Explanation: Load balancing is dividing the work of one computer among several computers so that more work gets done in the same amount of time and all users get served faster. You can implement a hardware or a software load balancing solution.

Question 14 Explanation: The role definition determines the navigation structure within the portal. The navigation structure consists of the top-level navigation bar, and the detailed navigation tree. The top-level navigation bar is a series of tabs in the title area of the portal header. A user navigates portal pages and services by clicking tabs in the top-level navigation bar.

Question 15 Explanation: When the user performs a Drag & Relate action in the front end, the client sends a HRNP (hyper relational navigation protocol) request to the Unification Server through HTTP. The Unification Server resolves the relationship between the drag source and the drop target, and queries the database and/or applications to determine the record set. Then it redirects the result set to the Portal Server and launches the screen which appears in the browser.

Question 16 Explanation: If you are using basic authentication, we strongly recommended that you set up the browser and portal Web server to communicate using Secure Sockets Layer (SSL).Otherwise users‘ credentials will be transmitted in clear text.

Question 17 Explanation: The SAP System has Release 4.0B or higher. SAP logon tickets are not supported in releases lower than 4.0B.

Question 18 Explanation: Reverse Proxy Filter enables the portal to do the following:• Check all HTTP requests coming to the portal platform.• Distinguish between the following HTTP requests to the portal: those coming from external sources, such as the Internet and outside the firewall of an enterprise, and those coming from internal sources, such as the intranet within the firewall.• Replace the scheme, host, and port number in an HTTP request.• Respond to more than one domain name using different proxy servers.

Question 19 Explanation: An iView is handled differently by Enterprise Portal depending on whether it is invoked from an Internet Explorer or Netscape browser. In Internet Explorer, each iView in a portal page is contained in an iFrame. Each iFrame is a distinct container, independent of the other containers. In Netscape, each iView is contained in an HTML table. When multiple iViews are displayed in a portal page in Netscape, you are actually viewing a single HTML page formatted into HTML tables.

Question 20 Explanation: Content Admin tab provides the tools for creating portal-related content, such as roles, iViews, pages, Web components.

Question 21 Explanation: Portal applications are configured according to the logger.xml configuration file. Various portal applications place information into different log files. SAP recommend that you set log levels in production environments to WARNING or ERROR.

Question 22 Explanation: SAP JCo is a middleware component that enables the development of SAP-compatible components and applications in Java. SAP JCo supports communication with the SAP server in both directions: inbound calls (Java calls ABAP) and outbound calls (ABAP calls Java). So, SAP JCo realizes communication between the ABAP and the J2EEenvironments that can be used in SAP Web AS.

Question 23 Explanation: You use the cryptographic tool SAPGENPSE to generate a key store in which you can store a certificate. You only need this key store for storing the root certificate of the portal Web server. It is therefore not necessary that you send the generated certificate request toyour CA.

Question 24 Explanation: The entire portal administration is performed using administration roles contained in the standard content of the portal. The administration roles contain all the functions possible for portal administration. The standard delivery of SAP Enterprise Portal 6.0 contains four administration roles, all of which subdivide the existing administration tasks into the following four groups:· Super Administration (containing all administration tasks)· Content Administration· System Administration· User Administration

Question 25 Explanation: You implement the Knowledge Management (KM) platform of the Enterprise Portal to enable unstructured content management, and sophisticated search and retrieval functionality over unstructured content in disparate information repositories. The knowledge management platform also provides collaboration functionality, such assending messages, annotating documents, and setting up discussion groups.

Question 26 Explanation:

Question 27 Explanation: The Enterprise Portal iView interface enables you to create and manage portal channels and iViews. When you open the interface, a list of iViews and channels is displayed, along with a set of tools that let you create and maintain channels and iViews. In this section, we describe the main functions of this interface. iView Editor screen: (1) Search Tool, (2) Toolbar, (3) Channel List, (4) iView List

Question 28 Explanation: The user management component of the Enterprise Portal is an extensive application programming interface (API) that allows iViews to read data from the corporate LDAP directory and to read and write data to the portal LDAP directory. It also provides Single Sign-On functions and Authentication of portal users against user repository.

Question 29 Explanation: Single Sign-On (SSO) is a key feature of the Enterprise Portal that eases user interaction with the many component systems available to the user in a portal environment. Once the user is authenticated to the enterprise portal, he or she can use the portal to access external applications. With SSO in the Enterprise Portal, the user can access different systems and applications without having to repeatedly enter his or her user information for authentication. The Enterprise Portal SSO mechanism is available in two variants depending on security requirements and the supported external applications:· SSO with SAP logon tickets· SSO with user ID and password Both variants eliminate the need for repeated logons to individual applications after the initial authentication at the enterprise portal. Whereas SSO with SAP logon tickets is based on a secure ticketing mechanism, SSO with user ID and password forwards the user’s logon data (user ID and password) to the systems that a user wants to call.

Question 30 Explanation: Channels, used to organize iViews into logical groups, are also assigned to roles. While every iView must be assigned to a channel, not every iView is associated with a page. A user has access to the iViews displayed on the pages in his or her portal. When personalizing portal pages, the user will also have access to the iViews in the channels assigned to his or her roles.

Question 31 Explanation: There is a permissions concept for portal objects in SAP Enterprise Portal 6.0. It is valid for all objects of the Portal Content Directory that can be maintained with a special editor (Permission Editor) in the portal. Portal permissions mainly define the access rights of portal administrators to portal objects in the Portal Catalog. The access permissions are implemented with the Access Control List (ACL) method.

Question 32 Explanation: In a load balanced landscape with multiple portal server installations the lock server is the portal component that enables the components of the middleware layer to work concurrently with the persistence layer, notably with the Portal Content Directory (PCD) and the database server. The middleware layer is installed as clients that access the persistence layer and the shared resources. Each middleware client must not interfere with other clients accessing and modifying the same resources, therefore there is the need to implement a concurrent control mechanism. The control mechanism is a synchronization process over TCP/IP at port 3299. Through the port, the lock server identifies the specific process request coming from each middleware client. It then allows access to the shared resources and the persistence layer. By so doing, each portal works with a consistent view of the shared resources. Portals communicating with the lock server become the lock clients.

Question 33 Explanation: Web Dynpro is a browser-based, device-independent technology which provides a runtime and a development environment for professional business Web applications. Web Dynpro delivers a declarative meta-model to minimize the need to write programming code. From this abstract definition, Web Dynpro generates code to create a ready-to-run Web application.

Question 34 Explanation: The Enterprise Portal includes two user management master iViews that you can modify to suit your company’s requirements and integrate in the portal. These are:· Self registration master iView: Allows users, for example, external users that do not exist in the corporate LDAP directory, to register themselves as portal users.· Change password master iView: Allows users to change their password and optionally other user data.

Question 35 Explanation: For the portal cluster:· To guarantee proper portal functionality, external load-balancing solutions must always implement stickiness, using either a source-IP or cookie-based distribution policy.· All machines in a portal cluster are covered by a license installed on any of them. However, for high availability purposes, you should install a license on at least two portal machines, although a license on each machine is recommended. In this case, if the machine with the single license is stopped for more than an hour (the period of time during which the license is cached), portal operation will not be interrupted

Question 36 Explanation: My Pages tab contains the default Welcome page plus the pages assigned to all of the roles to which the logged on user is assigned. My Pages display iViews, small applications designed to retrieve information from various information resources.

Question 37 Explanation:

If you have a mixed system landscape including both SAP and non-SAP systems, we recommend that you use a corporate LDAP directory as a primary store for central user data। Also use this option if you have a large number of users in your system landscape। In the above figure, a system running CUA is used to administer user data from several SAPABAP systems centrally। The user data from the CUA is synchronized with a corporate LDAP directory। The UMEs of any standalone J2EE Engines are configured to use the corporate LDAP directory as data source। Third-party systems can also access user data on the LDAP directory।

Question 38 Explanation: The Unification Server enables your Portal for Drag & Relate (hyper relational navigation)। This means that you can relate business data across applications and/or databases for which you have installed a unifier on your Unification Server। Moreover the Unification Server provides functions to display data from the installed database unifiers।

Question 39 Explanation: To enable high load and avoid errors when running SAP Enterprise Portal with an Oracle database, increase the maximum number of processes and sessions in the database।

Make sure no one is currently using the database, as you must restart the database server. To change the number of processes on an Oracle database server:

1. From the Oracle program group in the Windows Start menu, go to Database Administration >DBAStudio, and log on to your Oracle database using DBA Studio as user SYSDBA.

2. Open the Database branch and choose: Instances > Database.

3. Choose All Initialization Parameters.

4. Scroll down the list of parameters to the processes property and increase its value (e.g. 150).

5. Verify the increase with your DBA.

6. Scroll down to the sessions property and increase its value to 1.2 multiplied by the number of processes.

7. Choose OK and then Apply. You are prompted to restart the database server.

8. Restart the IIS and the Oracle server.

Question 40 Explanation: When Single Sign-On with user ID and password is used, the user ID and password are transmitted in plain text using HTTP POST. We strongly recommend that you protect the connections to the SAP System using HTTPS or SNC to prevent the user ID and password being eaves dropped by an external party.