Beruflich Dokumente
Kultur Dokumente
Applies to:
SAP NetWeaver 04 SPS15, Portal Development Kit 2.0 for Microsoft .NET
Summary
Enabling the integration of portal content created with Portal Development Kit 2.0 for Microsoft .NET for SAP
NetWeaver Portal, into Microsoft SharePoint Portal Server 2003.
Company: SAP
Table of Contents
Introduction.......................................................................................................................................2
Terminology ..................................................................................................................................2
Prerequisites .................................................................................................................................3
Integration.........................................................................................................................................6
Introduction
As another element of interoperability with Microsoft, SAP provides tools that enable the integration of portal
content, created with Portal Development Kit 2.0 for Microsoft .NET for SAP NetWeaver Portal, into Microsoft
SharePoint Portal Server 2003. 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 2.0 for Microsoft .NET (PDK A toolkit that enables development of SAP
2.0 for .NET) NetWeaver Portal content in the Microsoft.NET
environment
Portal Add-in 2.0 for Visual Studio 2003 The design-time environment of PDK 2.0 for .NET
Portal Runtime 2.0 for Microsoft .NET The runtime service of PDK 2.0 for .NET
Microsoft SharePoint Portal Server 2003 A scalable portal server that connects people, teams,
and knowledge across business processes.
Prerequisites
For detailed installation instructions, see Installation, Upgrade and Configuration Guide PDK for .NET.
1. Double-click the SAP Portal Interoperability WebPart.msi file to start the installation.
2. In the SAP Portal Interoperability WebPart dialog box, select Specific virtual servers, enter the site
name in the format http://<Host Name>:<TCP Port No>, and click Next.
3. 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.
Go to the home directory of your site, open the Web.config file, and modify the file as follows:
1. 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.
2. 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=2.0.0.0, Culture=neutral,
PublicKeyToken=50436dca5c7f7d23" />
3. 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/2.0.0.0__50436dca5c
7f7d23/UR" />
<add key="PDKServer" value="localhost" />
<add key="PDKPort" value="8050" />
<add key="PDKDeploymentFolder" value="C:\SPSPCD" />
</appSettings>
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.
\common
\jslib
\ur
2. 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.
3. 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\2.0.0.0__50436dca
5c7f7d23\UR, as described in the following table:
Source Destination
\com.sap.portal.design.urdesigndata\themes\portal\sap_trades \common
how\common and all its subfolders
\ur
com.sap.portal.design.portaldesigndata\themes\portal\sap_tra
deshow
\glbl\glbl_ie6.css
\prtl_std\prtl_std_ie6.css
\ur\ur_bdy_prtl_ie6.css
\ur\ur_ie6.css
\jslib
\com.sap.portal.htmlb\jslib\popup_ie6.js
\com.sap.portal.htmlb\jslib\sapUrMapi_ie6.js
\jslib
\com.sap.portal.dotnet.framework\scripts\controls\dotNETHand
ler.js
\com.sap.portal.dotnet.framework\scripts\controls\urMessageB
undle_en.js
Integration
Installing the Web Part on a SharePoint Portal Server
1. 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.
2. 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
Under Actions, click View Page. The Web Part you have added appears on the page.
Limitations
In the Microsoft SharePoint Portal Server 2003 environment, PDK 2.0 for .NET supports limited functionality.
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
Server Explorer
SAP Portal Page project item
SAP Portal System Template project item
Author Bio
Anne Tarnoruder is an information developer for SAP NetWeaver Product Management in SAP
Labs, Israel, where she is responsible for the developers 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.
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.