SAP ENTERPRISE PORTAL PDF
SAP Enterprise Portal. Prepared By. Vamshi Krishna Katta. 2. Contents: 1. SAP EP. 2. SAP Net weaver. 3. Difference between , , , , 4. SAP Enterprise Portal offers more than the integration of data from vari- ous sources and manufacturers. It also facilitates interaction and collabo- ration among. SAP NetWeaver is an open technology platform that offers a comprehensive set of applications like SAP Process Integration (PI), Enterprise Portal, and.
|Language:||English, Spanish, Japanese|
|ePub File Size:||17.63 MB|
|PDF File Size:||11.24 MB|
|Distribution:||Free* [*Regsitration Required]|
SAP - SAP Enterprise Portal – System Administration. Suggested Audience. Skills Gained. Who Can Benefit. Prerequisites. Course Details. Course Content. An SAP Enterprise Portal implementation has many stages, and this book will help you every step of the way. E-book formats: EPUB, MOBI, PDF, online. For further information, please visit our website: wildlifeprotection.info Marty McCormick, Matt Stratford Content Integration with SAP NetWeaver Portal
The Portal Platform The Portal Platform includes those components and tools that are necessary to build a portal, including the following: iView technology, for creating and administering iViews.
You can either use standard iViews delivered by SAP or create your own iViews, either by programming them or by using the portal content creation tools. Unification technology includes services for resolving relations between business objects of back-end systems. User Role Management, for creating user roles that provide access to portal pages for the users or user groups. In addition, the possibility to reuse, supplement, and continually update SAP content offers great savings potential.
The Knowledge Management platform provides access to an organization's unstructured information documents. The information may reside in various repositories that can be connected to the portal by means of components called repository managers.
The Complete Guide to SAP NetWeaver Portal
First Name. Start date of account Validity. User Administration User Creation: To create user in portal. Then finally save it. Then save it. In Assigned Role. User ID. Then Go. We can see the assigned role of particular user.
Name of Role Eg: Select the Group and add it. Finally save it.
User ID and Password of Backend system. To unlock select the user. Copy the user data in notepad and save it. To export the users from Development and import it whether Quality or Production.
Then import the file to respective system. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample. SAP will not be held liable for any damages caused by using or misusing the information. SAP responsible or liable with respect to the content of this document. Changes made based on this information are not supported and can be overwritten during an upgrade. You agree that you will not hold.
Java system reports allow you to monitor the AS Java system and Java applications running on the system. You can track the per- formances of all AS Java instances, detect and analyze the causes of various problems in AS Java, and perform tuning for productive use with AS Java.
EE JCo monitoring: This allows you to monitor all the JCO connections in the system; for example, you can organize the metadata cache and change the settings for JCo traces. EE Locks: The locks tool in this work center allows you to create and release locks. EE Log viewer: This tool allows you to view all log and trace messages that are generated in the SAP system.
These log messages assist you in monitoring and troubleshooting problems. We discuss this in more detail in Chapter The configuration work center provides the following worksets: The tools are grouped under the following worksets: The various tools in this work center are grouped under the following worksets: As a result, the server does not need to be running for the Config Tool to work. The Config Tool connects directly to the database, which is where all completed configuration changes are stored.
SAP BASIS Related Interview Questions
For these changes to take effect, you must restart the server because the server reads all of the properties from the database during startup. The Config Tool can run in two modes, as discussed in the following subsections. In a UNIX environment, the file is named configtool. EE Connect to a database Connect to the default database and any other databases. You can effectively connect to multiple remote systems from one machine using the Config Tool. EE Configure the cluster, instances, and nodes This allows you to configure the whole cluster, as well as individual instances and nodes.
EE Add and remove server nodes Add additional server nodes to the same instance. Each server instance can have multiple server nodes.
When the server gets installed, by default it is installed with one server node. Adding more server nodes enables the server instance to handle higher loads and aids in load balancing the client requests. EE Log configuration Configure logging discussed in more detail in Chapter Console Config Tool The Console Config Tool provides a command-line interface for configuring the server parameters in offline mode.
The Console Config Tool can be invoked by double-clicking the batch file console- config.
This opens the Console Config Tool in the command line, as shown in Figure 2. A telnet client allows you to connect to the application server using the telnet protocol. Telnet requires the application server to be up and running for it to work. In addition, remote administration using telnet is not possible because SAP only allows connection to the local host with telnet. To start the telnet console, type the following command in the command line: For example, if the instance number is 01, the telnet port will be You can connect to the application server using the telnet protocol by invoking the telnet command.
By authen- ticating, you are logged in to one of the server processes. You can jump to another server by using the JUMP command.
The command LSC gives a list of all server processes in the instance. To view a list of all available commands, execute the MAN command.
This list is shown in Figure 2. To view the message syntax and message documentation of a com- mand, execute the following: It provides an environment on top of AS Java for running portal-based applications.
The request is processed in the server, which returns a response to the client. In this section, we will discuss these processing steps. This Java EE application defines the following two servlets: EE Gateway Handles requests for the portal home page.
When the request reaches the Java EE engine, it identifies that the request is for the Java EE application irj, which is the portal application. Every Java EE appli- cation has a web. The gateway and PRT dispatcher servlets are defined in the web.
The gateway servlet again reads the parameters defined in the web. It then redirects the request to the portal launcher PRT application if the applica- tion requires authentication, or it redirects to the application that enables anon- ymous requests if an anonymous login is required. The Java EE engine receives the redirection request and again reads the web.
Every portal component has an XML portalapp. The PRT reads the portalapp. If authentication is needed, then the runtime checks if the user is already authenticated by checking for a valid cookie or a valid user name and password.
After the user logs on successfully, a cookie is created on behalf of the user to identify the session for subsequent requests, and the request processing continues. The portal launcher component calls the desktop service of the portal to render the appropriate portal desktop for the user.
The irj application has a servlet named prt, which handles all of the requests coming to the PRT. PRT creates a root node called the portal node; all other components involved will be created as child nodes. The POM can become pretty complex for requests that involve multiple components. Called once for each component. The PRT traverses the tree from top to bottom, calling the method for each compo- nent.
Request event handlers This category of methods is called if there are request events for special nodes. These events are specific to your application and the events in your code. The PRT traverses the tree from bottom to top, calling the method for each component.
An alternative method is called for other modes. For example, if you are in help mode, then the method doHelp is called. The start and stop of AS Java can be done in various ways: Start the MC. In the console, navigate to the system that you want to start. Select the system. Right click, and choose Start from the context menu. MC then starts the SAP instance. Start the MMC. Right-click, and choose Start from the context menu.
To stop the SAP instance, follow similar steps as those previously mentioned, but choose Stop from the context menu instead. To start all instances running on the host, execute the following command: Database instance 2.
SCS instance 3. Java central instance To stop the SAP instances separately using the command line, follow this sequence: Java central instance 2. This brings a host of challenges that need to be anticipated. The network architecture of the SAP NetWeaver Portal landscape plays a large part in determining the security of the corporate portal.
There are various terms that you need to understand here: EE Firewall A firewall is a device or set of devices that protect a network from unauthorized access. Corporations normally have a firewall between their networks and the Internet to prevent direct access to their networks by outside users.
In a network, there are services that need to be exposed to external users e. However, exposing these servers to the Inter- net also means risking unauthorized access by malicious users.
To minimize this risk, servers are kept in a separate subnetwork so that even if these hosts are compromised, other business systems inside the network are safe. They are instead redirected by the intermedi- ate servers, thus adding an extra layer of security. There, the portal server has very limited access to the internal network, which is a high security zone.
Another firewall lies between the DMZ and the internal network, which makes any external access to the internal network very difficult.
All of the servers that contain sensitive data are part of the high security internal network. More complex network architecture is shown in Figure 2. We also discussed various administration and configuration tools and their usage.
The entire installa- tion process has been divided into preparation, installation, and post-installation steps. After the installation and post-installation sections, we will discuss some of the initial configuration needed for any SAP NetWeaver Portal implementation, including transport layer security configuration and user management configuration.
Each step is discussed in the following subsections. By default, outbound connections are not limited to rules and are therefore not restricted by the firewall. These settings apply to local policies. For domain policies that override local policies, other rules might apply. SAP recommends that you either secure network access to the SAP application servers with a real physical firewall or use a router access control list ACL.
Follow these steps on the Windows Server R2 for this configuration: Check the Windows file system. Make sure that you are using the Windows NTFS on the machine where you are installing the server by doing the following: Right-click the relevant disk. The system displays the type of file system in use. Check the Windows domain structure. If you are doing a domain installation, check that all SAP system hosts are mem- bers of a single Windows domain.
Ensure Windows Server performance. Make sure that High Performance is selected as the default power option by following these steps: The authorization required depends on whether you intend to perform a domain or local installation.
If necessary, ask the system administrator to grant the account the necessary authorization before you begin. The installation will abort if you attempt the installation with an account that does not have the required authorization. If you do not intend to use the directory structure of the system you are going to install but want to use either another new transport directory on a different host or an existing transport directory in your system landscape, you need to prepare that transport host as follows: EE If the directory structure already exists, you must set up its security to allow the new system to write to it.
EE If the directory does not yet exist, you must create the core directory structure and a share to export it for other computers as well as set the security on it.
Complete the following steps: EE If the transport directory already exists, grant Everyone the permission Full Control for the transport directory. If you download the installation media, note that the media might be split into several files. In this case, you have to reassemble the required files after the down- load. Follow these steps: Create a download directory on the host where you want to run SAPinst.
Identify all download objects that belong to one installation medium according to one or both of the following: EE Material number: All download objects that are part of an installation medium have the same material number and an individual sequence number: EE Title: Download the objects to the download directory.
This section describes how to run the installation tool SAPinst. These executables are deleted after SAPinst has stopped running. You can safely delete them after the installation has completed.
If these ports are already in use, SAPinst automatically searches for free port numbers. If the search fails, you see an error message, and SAPinst exits. If this happens—or if you want SAPinst to use specific ports—open a command prompt, and change to the required directory as follows: EE Make sure you have at least MB of free space in the installation directory for each installation option.
EE Check that your installation host meets the requirements for the installation options that you want to install. If you are installing a second or subsequent SAP system in an existing database, make sure that the database is up and run- ning before starting the installation.
Log on to the installation host using an account with the required user authori- zation to run SAPinst. Make the installation media available on the installation host. Start SAPinst from the installation media by double-clicking sapinst. In the Welcome screen, choose the required options, and click Next. If SAPinst prompts you to log off from your system, log off and log on again. SAPinst restarts automatically. Follow the instructions in the SAPinst screens, and enter the required parameters.
After you have entered all requested input parameters, SAPinst displays the Parameter Summary screen. This screen shows both the parameters that you entered and those that SAPinst set by default. If required, you can revise the parameters before starting the installation. To begin the installation, choose Start. SAPinst starts and displays the progress of the installation. It takes approximately 15 to 90 minutes before the deployment is completed and the portal is launched.
If you copied the installation media to your hard disk, you can delete these files when the installation has successfully completed. Make sure that the database is up and running before continuing, and then follow these steps: Open a command prompt, and execute the following command: The appli- cation server should be running before you continue with the following steps: Start a web browser, and open the following URL: To log on to the portal you just installed, make sure that the server is up and run- ning, and then follow these steps: Start a web browser, and open this URL: Log on with the administrator ID that was created during installation and the password that you provided as an installation parameter.
The license key is bound to the hardware key of the host where the message server is running. To install the license, first you need to get a license from SAP by going to http: The screen will show the current licenses installed with the validity dates as shown in Figure 3.
Portal Environment in Today’s Business
To install a new license, click the Install from File button. In the popup that appears, choose the file, and click Add. This should add the license to the system. You can use this protocol for communication between the database server and its client here, the AS.
In addition, the server authen- ticates itself to the client. There is a performance cost for SSL because the data has to be encrypted, which requires time and processing power. To use SSL, you need to do the following: Table 3.
In all cases, the user ID and password are encoded only when transported across the network. Make sure that you perform this procedure before the newly installed SAP system goes into production.
For the users discussed in the following subsections, take the precautions described in the relevant SAP security guide, which you can find on SAP Service Marketplace at http: After the installation, operating system users for SAP system, database, and host agent are available as listed in Table 3. Because SAP NetWeaver Portal is usually accessed by a large number of people, and many times the data transfer between the users and SAP NetWeaver Portal can be confi- dential, the security of the data while being transferred becomes very important.
Figure 3. Step 1: Three files are important: The DLL file and the configuration tool should be copied to the C: Log on by going to http: After saving, the SSL status should be green.
The screen will look like Figure 3. The screen should look like Figure 3. The new SSL access point should be set up as shown in Figure 3. Next, we discuss the steps required for the SNC configuration. You can execute the sapgenpse. You need to execute the following command to create the credentials: For example: To maintain the ACL, perform the following actions: After you log on, the user administration screen will look like Figure 3.
After logging on successfully, you will reach the Identity Management screen, as shown in Figure 3. The UME configuration page looks like Figure 3. EE User administration This feature provides the functionalities for creating, editing, and deleting users, groups, roles, and so on. It also supports import and export of users, roles, and groups. EE Security settings Settings such as password policy, password expiry policy, and others. EE Self-service scenarios If enabled, it allows users to register themselves and edit their data.
It defines which user store will be used for SAP NetWeaver Portal and is the repository where the information about users, groups, and roles is stored. The availability and connectiv- ity of a configured data source is a must for the AS Java to start. Many corporations already own an LDAP directory for storing the infor- mation about users, and it make sense to use the same user store as the data source for the UME. This way, the portal uses the same users and attributes as all of the other systems in the corporate network.
There are two options for using the LDAP directory as the user store: EE Option 1: The following data source configuration files are available for this scenario: Read-only service This option does not allow you to create or change the users and groups from the LDAP directory. The following configuration files are available for read-only service: Selecting the data source can be done either during or after the installation.
After installation, the data source can be changed, but after you have selected a data source other than the AS Java database, you cannot change the data source again. After selecting the data source, the next step is to edit the UME properties to configure it according to your needs.
However, changes done using the Config Tool take effect only after the server cluster has been restarted. Now we will discuss how the UME properties can be changed by using each mechanism: EE Expert mode in user management configuration page Using the export mode of user management configuration, you can make the UME changes that apply at the global level of the instance. To enter the export mode, first open the user management configuration, and then click Open Expert Mode button.
The screen shown in Figure 3. This opens the UME properties editor as shown in Figure 3. EE Change to edit mode, and double-click Propertysheet Properties.
EE Select the property that you want to change, and double-click to open the property in a new pop-up window. EE Save and restart the server. In this section, we will explore how to create and edit various systems in the system landscape of SAP NetWeaver Portal, test system connections, and create aliases for the systems. From this screen, you can edit or delete a system, and test a connection to ensure that the portal is able to connect to the defined system with the mentioned properties.
Go to the folder in which you want to create the system object. The system presents all of the predefined templates for creating the system see Figure 3. Select a template, and click Next. On the next screen, enter the system name, ID, and description, and click Next. On the next screen, define an alias, and click Next. You can define multiple aliases here if you want.
On the next screen, provide the connection and login details for the system that you want the portal to connect to, and then click Next. The system tries to connect to the chosen system.
Click Finish to close the sys- tem creation wizard. A system can be assigned multiple logical names, which are used in the applications. Although there can be any number of aliases assigned to a system, at least one alias must exist for every system. Each alias assigned to any system must be unique in the system, meaning that no two systems can share a common alias.
One important point to note about aliases is that they are not transported when the system object is transported, so when you transport your system to a new environment, you need to create system aliases in the new system manually.
In this section, we consider a scenario where you are integrating the UWL with the SAP backend, and discuss the necessary steps involved. EE You should have a portal system configured for the backend system to which you want to connect we discussed creating a system in Section 3. Also make sure an alias has been configured for the system. EE Single sign-on or user mapping should be set up for users. If you want to configure a new system, click on the New button; this will bring up the input form for creating the system Figure 3.
One of the most important parameters here is the Connector Type parameter; Figure 3. This will register the item types and give a success message after successful registration. This is where you will find all the configurations for the item types stored in XML files. Here you can upload new configurations as well as download and delete existing configurations. To upload a new configuration, go to the Upload New Configuration tab. Specify a configuration name for the new configuration, choose an XML file to upload, and click on the Upload button.
This uploads the new configuration. If you select a system from the dropdown, the configuration will only be valid for that particular system. You have now completed the basic UWL configuration.
By configuring the XML file, you can change many properties of the UWL, such as the order of columns, which columns are included, etc.
By default, the uwl. Select the uwl. This is shown in Figure 3. If you want to change the proper- ties of the default view, create a new XML file, name it based on your preference, and create the structure in the XML file as shown in Listing 3.
Your new XML file should look like Listing 3. Once your changes are done, your XML is ready to be uploaded.
ABAP Objects: Introduction to Programming SAP Applications (SAP Press)
You can upload this new XML file as described in Section 3. When you upload, choose the High priority option so that the configuration takes precedence over the standard configuration provided by SAP. The configuration for launching an item can be performed in two ways: We discuss these options next. To re-register the items, go to the UWL configuration page.
As shown in Figure 3. The new item launch configuration will now take effect for all users. We will see an example of such configuration here.
Let us assume that for a particular task type, we have created an application and have created a portal iView that should be launched when the item is launched in the UWL. To begin, create an XML file with the structure shown in Listing 3. We do this with the tag ItemTypeCriteria. As shown in Listing 3. This code is pro- vided in Listing 3.
The iView property has been set to the PCD path of the actual iView and an action name has been given. The configuration is now finished, and Listing 3. After clear- ing the cache, when you test again, you will be able to launch the iView for the configured task type.
As a result, there may be times when you want to create a custom UWL application that can more closely adhere to your look and feel requirements. You can find the weblog at this URL: It is important to note here that the UWL gives the ability to connect to multiple providers in order to get work items from different systems at the same time; all you need to do is configure a connector for each system.
This process is called transport. Before release 7. We also discus this topic in this section. In the next screen, provide the name and ID for the transport package; click Next, and then click Finish on the next screen. Now that the transport package has been created, you are presented with the options to choose from. Click Content to add content to the transport package, as shown in Figure 3.
Select the objects that you want to add to the transport package. This adds the objects to the transport package, as shown in Figure 3. After the content has been added, click Export to export the transport pack- age. The next screen shows the content of the transport package. From here, you can exclude objects or include objects that were earlier excluded. After final- izing the content, click Next. Name the export file. The name should end with. Click Next. The next screen shows the transport details and transport package details.
Click Export to start the export. After the export completes and the exported transport package file is saved on the server, you can download the EPA file by clicking the Download File link. After the export file has been downloaded, you can take this file and import it into another portal environment to transport the content of the transport pack- age into another portal system. To import a transport package, follow these steps: You can import a transport package by uploading the EPA file either from the client desktop or from the server.
He's Not That Complicated™ PDF, eBook by Sabrina Alexis & Eric Charles
This shows the objects in the transport package. Click Import to start the import. You will receive a message when the import has successfully finished. Until now, the ability to record the changes done to portal content in SAP NetWeaver Portal was an important but absent functional- ity. As a result, the transport of portal content was not very smooth.
With change recording, users can maintain, release, and transport a list of all their changes. Selecting the service brings all of the parameters for that service into the Extended Details pane. Select the property Pcd. This brings a pop-up for entering a custom value for that property see Figure 3. The change recording has now been activated.
Several other properties of the PCD Generic Layer are related to change recording and are worth mentioning: EE Pcd. Here you can add the locations that you want to be included in the change lists. Click Manage omitted prefixes to add the prefixes that you want to exclude from the change list recording.
After you have done this, the change recording is configured. The Change Organizer tool lists all of the change lists for the logged-in user; when you select a change list, it lists all of the objects included in the change list. This chapter began with a discussion of SAP NetWeaver Portal imple- mentation by outlining the preparation, installation, and post-installation steps. We will also see how single sign-on SSO is handled in such integration scenarios. One crucial challenge that you have to deal with during integra- tion is the authentication and single sign-on SSO of a user across systems.
When someone logs on to the portal and attempts to access an application that runs on some other system, he expects to be taken to that application seamlessly, without having to enter the user ID and password for that system again; this idea is known as single sign-on.
We will discuss these scenarios in the coming sections. It eases the pain of users who have to access multiple systems on a regular basis.
EE Logon ticket SSO based on a ticketing mechanism is where the source system issues a ticket, and the target system accepts and evaluates the ticket. If the ticket is valid, it lets the user in without asking for the user name and password. When the user is accessing the external system, the user name and password are sent to the system along with the request. If the user name and password are correct, the system lets the user in.
In any SAP NetWeaver Portal implementation in which you have to integrate external systems with the portal, the type of SSO mechanism that will be used is an important decision to make. There are important criteria that you need to consider when making this decision. The following are the possible SSO mechanisms: To take advantage of this scenario, your backend system must be able to accept logon tickets, and user IDs of the users should be the same in the portal as well as the backend systems.
In this scenario, a reference backend system is defined and the users are mapped in the portal with reference to this reference system. To enable this type of SSO, you need to configure SAP NetWeaver Portal to issue logon tickets, configure the portal for user mapping with logon tickets, configure the backend to accept logon tickets, and map users to the backend IDs. The following are the cases when you need this scenario: In this section, we discuss the major configuration steps involved in these scenarios.
Specifically, we will explain how to configure SAP NetWeaver Portal to act as a logon ticket-issuing system as well as a logon ticket-accepting system; how an SAP backend system can be configured to accept the logon tickets issued by SAP NetWeaver Portal which will be the case in most of the implementations ; and, finally, how to configure SSO using user mapping.
Based on the validity of this cookie, the user is authenticated to various other systems that accept logon tickets from SAP NetWeaver Portal. Logon tickets contain the user ID, but they do not contain the password.
It contains the following information: If SAP NetWeaver Portal works as the system that is accessed by the users first and is responsible for generating the logon ticket, the flow is as follows: The cookie is valid until the user either logs off or closes the browser. If the system finds the cookie valid, it lets the user in without asking for a password.If SAPinst prompts you to log off from your system, log off and log on again. J Agostinho O Junior. EE The additional costs for operating the solution are very small because Web Page Composer runs fully integrated with your existing portal infrastructure.
EE Easily componentizes and reuses Web Dynpro applications, which leads to a better design and architecture of the overall application. EE Portal framework The portal framework is a virtual environment that enables the portal as devel- opment and runtime environments.