Prerequisites
● The portal is installed and configured.
● For creating systems based on connectors provided by SAP:
The application connector and its PAR file are installed to the Web application server and the PCD, respectively, and configured.
● For creating systems NOT based on connectors provided by SAP:
You have edited an existing PAR file, or written your own, to contain a portalapp.xml file where you define a non-SAP system to which you want to connect, and you have deployed it.
Procedure
...
...
1. From top-level navigation, choose System Administration ® System Configuration ® System Landscape.
2. In the Portal Catalog, right-click a folder in which to store the new system and choose either New From PAR ® System,or New ®System.
3. Follow the instructions for each screen of the wizard, as detailed in the table below and on the wizard interface. An asterisk indicates the mandatory fields in any screen.
Whether you create a new system from a PAR file or from a template, the SAP_ConnectionString is not supported for RFC iViews.
The template SAP system using connection string is not supported for RFC iViews.
System Landscape Wizard
Screen | From a PAR File | From a Template |
Portal Archive Selection | Select the PAR file on which to base the system, and click Next. The PAR files installed with the portal are: · com.sap.portal.httpconnectivity.urlsystem System created from this PAR provides authentication and user mapping information to URL iViews · com.sap.portal.systems. System created from this PAR represents an EP5 data source that has been migrated to EP6 · com.sap.portal.systems.EP5 System created from this PAR contains all the connectivity details needed to migrate an EP5 portal into EP6 · com.sap.portal.systems.jdbc · com.sap.portal.systems.sap · com.sap.portal.systems. ● com.sap.portal.unification50. | N/A |
Portal Component Selection | Select the component you want and click Next. The properties in each component provide the system with the necessary information for connecting to its back-end application. ● .httpconnectivity.urlsystem connects through url_system ● .systems.datasource connects through DataSource_System ● .systems.EP5 connects through: EP5_system ● .systems.jdbc connects through jdbc_system ● .systems.sap connects through: ¡ SAP_R3_ConnectionString – URL string ¡ SAP_R3_Dedicated – application server ¡ SAP_R3_LoadBalancing – message server ● .systems.webservices connects through webservice_system ● .unification50.template connects through unifier_system | N/A |
Template Selection | N/A | Select one of the templates installed with the portal and click Next. ● EP 5.0 System ● HTTP System ● JDBC System · SAP system using dedicated application server · SAP system using connection string · SAP system with load balancing · Web Service System The template name indicates the type of connection. |
General Properties | Enter the basic properties and click Next. The Back option is currently not available in this screen. To change your portal component selection, choose Cancel and restart the procedure. | |
System Name | Display name that appears in the Portal Catalog, title bars, and any form, dialog box, and window displaying a list of systems | |
System ID | The unique system identifier that will be registered in the PCD; may include any of the following characters: ● a-z ● A-Z ● 0-9 ● . _ - % ~ ( ) The ID must not exceed 100 characters. | |
System ID Prefix | If you want all your systems to follow a specific naming convention, add a uniform prefix to each system you create. | |
Master Language | Defines the language on which all translations are based | |
Description | Optional description intended for portal users; appears in the tooltip when you hover over the page name in the Portal Catalog and in search results | |
Summary Details | Review the options you selected for the new system. To make changes, choose Back until you return to the appropriate screen; otherwise, click Finish. | |
Next Step | Choose your next step and click OK. ● The system may need editing before it can connect properly to its back-end application. ● If you want to define the new system to be a template, in the System Landscape Editor set the Object is a Template property to Yes. | |
Result
You have created a system through which you can access a back-end application or an HTTP source, and retrieve its data. This system is now part of the portal system landscape and should appear in the System Landscape Overview iView.
No comments:
Post a Comment