DISCOVERY SYSTEM CONNECTIVITY. Introduction HOW TO CREATE PORTAL IVIEWS BASED ON APPLICATIONS RUNNING ON A DS

Transcription

1 DISCOVERY SYSTEM CONNECTIVITY HOW TO CREATE PORTAL IVIEWS BASED ON APPLICATIONS RUNNING ON A DS Introduction Discovery System SAP Discovery system (DS) is a complete learning and testing environment designed to offer customers and partners the opportunity to test-drive and experience the power of enterprise SOA in a familiar landscape. While the Discovery system is a self contained environment, in some cases, the need to connect the DS with additional systems in the landscape is required. This document is part of a series of documents describing different aspects of the DS connectivity to the outside world. Use Case Description This document describes how to create portal iviews in a SAP Enterprise Portal and using a Web Dynpro application running on another SAP server. You can use the Discovery system either as the portal server or as the server providing the runtime for the remote WD application. This how to guide deals with real time connectivity between your DS and an external SAP Enterprise Portal. The DS will act as a service provider or backend offering services for consumption by an external client, i.e. a SAP enterprise portal. You will be guided through the process to integrate a Web Dynpro for Java (WD4J) application running on your DS into an existing, external SAP Enterprise Portal. Of course, the assignment between roles and servers can be exchanged so you utilize a WD application running on an existing server as an iview in the portal of the DS. As you do not have to develop a WD4J application, you will need less than one hour to complete the whole guide. You can easily adapt the example to use your other e.g. your own WD4J applications.

2 Page 2 Register an External System in the Enterprise Portal This chapter shows how to register a remote Web AS in the enterprise portal on the DS. This part is required to connect to the remote system on which the WD application runs. Register an external system in the enterprise portal Open the SAP Enterprise Portal, where the iview shall be created, in your web browser by entering the URL irj/portal e.g. :51000/irj/portal Logon as j2ee_admin with password sapides123 Navigate to System Administration System Configuration. Create a new folder via right-click on Portal Content New Folder Fill out the General Properties form of the Folder Wizard as shown. For the Folder ID Prefix please choose the domain of your organization, e.g. com.sap or org.example

3 Page 3 Close the wizard. Unfold the Portal Content folder. Add a new System via right-click on Systems (the folder you just created) New System (from template). The System Wizard opens. Choose the template SAP System using dedicated application server and click Next. Now provide the parameters of the remote system on which the WD runs. As System Name, use <SAP System>_<Type>, so already the name informs which system is referenced, e.g. iwdfvm2208_erp or iwdfvm2208_webas_j For System ID use the same as you did for System Name. For the System ID Prefix please choose the domain of your organization, e.g. com.sap or org.example Choose Next and Finish.

4 Page 4 Confirm to open the object by OK. Select Web Application Server from Property Category. Configure the Web Application Server. The host name and the protocol are mandatory. The description helps yourself. The path is not needed for the example. Save your settings. Choose User Management from Property Category. Configure the properties as shown. Save your settings. As you cannot select the system name but only a system alias in several portal settings (e.g. user mapping), create a new alias for the system: Select System Aliases from Display dropdown box.

5 Page 5 Type in an alias and press the Add button. Save your settings. To do the user mapping, go to User Administration Identity Management and search for your user. Click the correct entry. Select the User Mapping for System Access tab. Press Modify, choose the newly created system, and configure your user name and password for the target system. Save your settings. If you want to, you can do a connection test. For this, navigate to System Administration System Configuration and right click your system, choose Open and Connection Tests. Set the checkmark for SAP Web AS Connection and click Test. The highlighted pinging error is not important, but that HTTP/S succeeded. In case the connection test fails, open a command line on the portal server and execute telnet <host><domain><tld> <port> (watch the space between the server s FQDN and the port) manually, e.g. telnet iwdfvm2208.wdf.sap.corp As long as you do not receive an error here, the connection usually works.

6 Page 6 Creating the iview and Adding it to a Portal Role This chapter guides you through the creation of the iview for the remote WD application and how to add it to a portal role, so it can be accessed by users. Creating the iview Navigate to Content Administration Portal Content and right click the folder, in which you want to file the iview. Choose New iview Select iview template and click Next. Select SAP Web Dynpro iview and click Next. Now provide the parameters. For iview Name and iview ID choose some descriptive value, so others know the use and/or purpose of the iview already by the name. The name is also used as the title for the iview. For the iview ID Prefix please choose the domain of your organization, e.g. com.sap or org.example Choose Next and Finish.

7 Page 7 Select Web Dynpro for Java and click Next. Provide the alias name of the external system you added in chapter 1. In this example, we will use an existing WD4J application delivered with every DS the iview creation wizard application you re running just now so you do not have to create an application yourself. The Namespace is sap.com and the Appplication Name is new_iview/applic Click Next and Finish.

8 Page 8 Creating a portal role and adding the iview Navigate to Content Administration Portal Content and right click the folder, in which you want to file the portal role. Choose New Role Now provide the parameters. For Role Name and Role ID choose some descriptive value, so others know the use and/or purpose of the iview already by the name. For the iview ID Prefix please choose the domain of your organization, e.g. com.sap or org.example Choose Next and Finish. Open the Role for editing.

9 Page 9 Right click the iview you just created and select Add iview to Role Delta Link. Select Navigation as Property Category and set Entry Point to Yes. Save the role. Navigate to User Administration Identity Management, search for your user and select the row of your user. Then open the tab Assigned Roles and click Modify. In the area for Available Roles, search for the role you just created. Select its row and click Add. Click Save. Your user is now assigned to the portal role containing the iview, so you can access the iview from the top navigation. Now, log off and log in again.

10 Page 10 Now, in the top navigation the newly created role appears. Click on it and the iview will be shown in the main content area showing the WD4J application. You may right click in the content area and choose Properties to convince yourself the WD application really runs on a different server than the portal. Now, you may delete all created objects, beginning with the most depending one. First, delete the assignment of roles to users, then the role, then the iview and last, the system. Alternatively, you can modify the created objects in order to use your own WD application, show the iview in another role, or explore the possibilities in some other way.

11 Page 11 Copyright Copyright 2008 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic Server are trademarks of IBM Corporation in USA and/or other countries. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, R/3, mysap, mysap.com, xapps, xapp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.