Integrating SAP Portal Content into Microsoft SharePoint Portal Server

Transcription

1 Applies to: SAP NetWeaver 04 SPS15, Portal Development Kit 0 for Microsoft.NET Microsoft Visual Studio.NET Summary Enabling the integration of portal content created with Portal Development Kit 0 for Microsoft.NET for SAP NetWeaver Portal, into 200 By: Tarnoruder, Anne, SAP NetWeaver Product Management Company: SAP Date: February 2006 Table of Contents Introduction...2 Terminology...2 Prerequisites...3 Creating an SAP Portal Application and Packaging it as a Web Part...3 Preparing a SharePoint Portal Server...3 Installing the SAP Portal Interoperability Web Part...3 Modifying the Web Configuration File...4 Creating a Folder for Web Part Files...4 Installing the Portal CSS Files...4 Integration...6 Installing the Web Part on a SharePoint Portal Server...6 Adding the Web Part to a SharePoint Page...6 Testing the Application...6 1

2 Introduction As another element of interoperability with Microsoft, SAP provides tools that enable the integration of portal content, created with Portal Development Kit 0 for Microsoft.NET for SAP NetWeaver Portal, into Microsoft SharePoint Portal Server 200 This capability is based on the new feature that allows packaging the SAP portal content in the format required by Microsoft SharePoint. This guide takes you through the sequence of steps required to perform this task. Terminology Term Description Portal Development Kit 0 for Microsoft.NET (PDK 0 for.net) A toolkit that enables development of SAP NetWeaver Portal content in the Microsoft.NET environment Portal Add-in 0 for Visual Studio 2003 The design-time environment of PDK 0 for.net Portal Runtime 0 for Microsoft.NET The runtime service of PDK 0 for.net 2003 A scalable portal server that connects people, teams, and knowledge across business processes. SAP NetWeaver Portal The front-end component for SAP NetWeaver the comprehensive integration and application platform that facilitates the alignment of people, information, and business processes across organizational and technical boundaries. SAP Portal Application A collection of ASP.NET custom controls created for SAP NetWeaver Portal using PDK for.net virtual server A virtual computer that resides on an HTTP server but appears to the user as a separate HTTP server. Each virtual server can have its own domain name and IP address. Web Part An ASP.NET custom control that can be installed on any site based on Windows SharePoint Services, and added to application pages. 2

3 Prerequisites Microsoft Visual Studio.NET 2003 installed on a development host Portal Add-in 0 for Visual Studio 2003 installed on a development host Portal Runtime 0 for Microsoft.NET installed and running on a For detailed installation instructions, see Installation, Upgrade and Configuration Guide PDK for.net. Creating an SAP Portal Application and Packaging it as a Web Part Log on to your development host. Open MS Visual Studio 2003 and from the Tools menu, select Options. In the Options dialog box, expand the SAP PDK folder. Set the Target property under Output Settings to Microsoft SharePoint and click OK. Restart Visual Studio. Design, develop and test a portal application project with PDK for.net, as usual. From the project menu, select Create PAR. From the project menu, select Create Web Part Package. The <par name>.par and <par name>.cab files are created in the output folder specified in the Project PAR properties. Preparing a SharePoint Portal Server Log on to a MS SharePoint Portal Server as a user with administrative permissions. Extract the contents of the supplied.zip file into a local folder of your choice. Installing the SAP Portal Interoperability Web Part Double-click the SAP Portal Interoperability WebPart.msi file to start the installation. In the SAP Portal Interoperability WebPart dialog box, select Specific virtual servers, enter the site name in the format Name>:<TCP Port No>, and click Next. In the next dialog box, click Yes to install the SAP Portal Interoperability WebPart.dll to the Global Assembly Cache. A message appears, indicating that the installation was completed successfully. 3

4 Modifying the Web Configuration File Go to the home directory of your site, open the Web.config file, and modify the file as follows: To enable the use of the Session object, which is required to run Portal Runtime for.net, add the following tag to the system.web section: <pages enablesessionstate="true" enableviewstate="true" enableviewstatemac="true" validaterequest="false" /> If this tag already exists, modify its attributes accordingly. To enable redirection of requests for resources having the.ashx extension (.NET portal components) to Portal Runtime for.net, add the following tag to the httphandlers element under the system.web section. <add verb="*" path="*.ashx" type="sap.portal.interoperability.webpart.webpartwrapper, SAP.Portal.Interoperability.WebPart, Version=0.0.0, Culture=neutral, PublicKeyToken=50436dca5c7f7d23" /> To define attributes for the Interoperability Web Part, such as the location of the resource files, Portal Runtime for.net connectivity parameters, and the deployment folder, add the following appsettings element to the configuration section below the configsections element. <appsettings> <add key="pdkcss" value="/_wpresources/sap.portal.interoperability.webpart/ dca5c 7f7d23/UR" /> <add key="pdkserver" value="localhost" /> <add key="pdkport" value="8050" /> <add key="pdkdeploymentfolder" value="c:\spspcd" /> </appsettings> 4. Add the following tag to the <httpmodules> section: <add name="session" type="system.web.sessionstate.sessionstatemodule"/> 5. When finished, save the file, and restart IIS. Creating a Folder for Web Part Files Create a folder and name it C:\SPSPCD, as specified in the configuration setting. This folder will be used for storing the PAR files required to execute the Web Parts that you create with PDK for.net. Installing the Portal CSS Files On your SharePoint server, navigate to: %Program Files%\Common Files\Microsoft Shared\web server extensions\wpresources\sap.portal.interoperability.webpart\ dca 5c7f7d23\UR, and create the following subfolders: 4

5 \common \jslib \ur On your SAP NetWeaver Portal server, navigate to the <drive>:\usr\sap\..\..\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj \root\portalapps folder, for example, C:\usr\sap\P43\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\ro ot\portalapps folder. Copy the specified files to their respective destinations on your SharePoint server under the root folder %Program Files%\Common Files\Microsoft Shared\web server extensions\wpresources\sap.portal.interoperability.webpart\ dca 5c7f7d23\UR, as described in the following table: Source \com.sap.portal.design.urdesigndata\themes\portal\sap_trades how\common and all its subfolders com.sap.portal.design.portaldesigndata\themes\portal\sap_tra deshow Destination \common \ur \glbl\glbl_ie6.css \prtl_std\prtl_std_ie6.css \ur\ur_bdy_prtl_ie6.css \ur\ur_ie6.css \com.sap.portal.htmlb\jslib\popup_ie6.js \jslib \com.sap.portal.htmlb\jslib\sapurmapi_ie6.js \com.sap.portal.dotnet.framework\scripts\controls\dotnethand ler.js \jslib \com.sap.portal.dotnet.framework\scripts\controls\urmessageb undle_en.js 5

6 Integration Installing the Web Part on a SharePoint Portal Server Copy the PAR and CAB files you have created (<par name>.par and <par name>.cab) from the development host to the C:\SPSPCD folder on yout SharePoint server. Register the Web Part by opening a command prompt, and running the following command: C:\SPSPCD>stsadm -o addwppack -filename "<project name>.cab" -url "<your site URL>" -force Adding the Web Part to a SharePoint Page To enable the processing of requests with pdk in their path: 4. Navigate to the Windows SharePoint Services Central Administration page. Under Virtual Server Configuration, click Configure virtual server settings. Click your virtual server name. In the page that opens, under Virtual Server Management, click Define managed paths. In the Add a new path pane, enter pdk in the Path textbox, select Excluded path, and click OK. To add your Web Part to a page: Navigate to your site home page. Under Actions, click Edit Page. Click Modify Shared Page in the upper right corner. In the menu that opens, select Add Web Parts -> Browse. In the pane that opens, select the gallery that contains your Web Part. Select and drag your Web Part to the target zone on the page. Testing the Application Under Actions, click View Page. The Web Part you have added appears on the page. 6

7 Limitations In the 2003 environment, PDK 0 for.net supports limited functionality. The following features are not supported at runtime: SAP Portal Services: SAP.Portal.Services.UserManagement SAP.Portal.Services.Systems SAP.Portal.Services.OBN OBNAdapter component Server-side and client-side events When the Output Target option is set to MS Sharepoint 2003, the following features in the Visual Studio IDE are not accessible: SAP Toolbar SAP Menu bar Commands Deploy Publish Project Publish Page Create SDA View in Portal Debug Portal Style Designer Portal Page Designer The following Visual Studio IDE features do not function properly: Server Explorer SAP Portal Page project item SAP Portal System Template project item 7

8 Author Bio Anne Tarnoruder is an information developer for SAP NetWeaver Product Management in SAP Labs, Israel, where she is responsible for the developer s documentation of PDK for.net and Visual Composer. Prior to joining SAP in 2004, she held a number of positions in software development, team management, system architecture and technical communications in various high-tech companies. Anne holds an M.S. degree in Applied Mathematics. Disclaimer & Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. 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, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 8