Installation Guide

®
SAP NetWeaver
Portal Drive
Target Audience
„ System administrators
„ Technology consultants

Document version: 1.0 – July, 2007

 SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

© Copyright 2007 SAP AG. All rights reserved. NetWeaver, and other SAP products and services
mentioned herein as well as their respective logos are

No part of this publication may be reproduced or transmitted in any form trademarks or registered trademarks of SAP AG in

or for any purpose without the express permission of SAP AG. The Germany and in several other countries all over the world.

information contained herein may be changed without prior notice. All other product and service names mentioned are the
trademarks of their respective companies. Data contained

Some software products marketed by SAP AG and its distributors contain in this document serves informational purposes only.

proprietary software components of other software vendors. National product specifications may vary.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks These materials are subject to change without notice.

of Microsoft Corporation. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, only, without representation or warranty of any kind, and

AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, SAP Group shall not be liable for errors or omissions with

z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, respect to the materials. The only warranties for SAP

i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or Group products and services are those that are set forth in

registered trademarks of IBM Corporation. the express warranty statements accompanying such
products and services, if any. Nothing herein should be

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either construed as constituting an additional warranty.

trademarks or registered trademarks of Adobe Systems Incorporated in

the United States and/or other countries. SAP Library document classification: PUBLIC

Oracle is a registered trademark of Oracle Corporation.

Disclaimer
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Some components of this product are based on Java™.

Group. Any

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, code change in these components may cause unpredictable

VideoFrame, and MultiWin are trademarks or registered trademarks of and severe malfunctions and is therefore expressively

Citrix Systems, Inc. prohibited, as is any decompilation of these components.

HTML, XML, XHTML and W3C are trademarks or registered Any Java™ Source Code delivered with this product is

trademarks of W3C®, World Wide Web Consortium, Massachusetts only to be used by SAP’s Support Services and may not

Institute of Technology. be
modified or altered in any way.

Java is a registered trademark of Sun Microsystems, Inc.

Documentation in the SAP Service Marketplace
JavaScript is a registered trademark of Sun Microsystems, Inc., used You can find this documentation at the following address:
http://service.sap.com/installNW70
under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

Typographic Conventions Icons

Type Style Description Icon Meaning

Example Text Words or characters quoted Caution
from the screen. These include
field names, screen titles, Example
pushbuttons labels, menu Note
names, menu paths, and menu
options. Recommendation

Cross-references to other Syntax

documentation
Example text Emphasized words or phrases Additional icons are used in SAP Library
in body text, graphic titles, and documentation to help you identify different
table titles types of information at a glance. For more
EXAMPLE TEXT Technical names of system information, see Help on Help → General
objects. These include report Information Classes and Information Classes
names, program names, for Business Information Warehouse on the
transaction codes, table first page of any version of SAP Library.
names, and key concepts of a
programming language when
they are surrounded by body
text, for example, SELECT and
INCLUDE.
Example text Output on the screen. This
includes file and directory
names and their paths,
messages, names of variables
and parameters, source text,
and names of installation,
upgrade and database tools.
Example text Exact user entry. These are
words or characters that you
enter in the system exactly as
they appear in the
documentation.
<Example text> Variable user entry. Angle
brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in the
system.
EXAMPLE TEXT Keys on the keyboard, for
example, F2 or ENTER.
Installation Guide: SAP NetWeaver Portal Drive

Contents

1 Introduction .........................................................................................5
1.1 About this Document ............................................................................. 5
1.2 Before You Start ..................................................................................... 5
1.2.1 SAP Notes for the Installation ............................................................ 5
2 Preparation ..........................................................................................6
2.1 Client Requirements .............................................................................. 6
2.2 Downloading the Installer from the SAP Service Marketplace........... 6
2.3 Installation Server .................................................................................. 6
3 Simple Installation ..............................................................................7
3.1 First Steps............................................................................................... 8
4 Central Installation............................................................................12
4.1 Setting Up an Installation Server ........................................................ 13
4.2 User Installation ................................................................................... 14
4.3 Unattended Installation........................................................................ 15
5 Post Installation: Central Configuration .........................................16
5.1 Central Configuration File ................................................................... 17
5.1.1 General Settings .........................................................................................................18
5.1.2 Service Settings ..........................................................................................................25
5.2 update.xml File ..................................................................................... 27
5.3 admin.cfg File ....................................................................................... 28
6 Upgrade..............................................................................................29
7 Uninstallation ....................................................................................30
7.1 User Uninstallation............................................................................... 30
7.2 Unattended Uninstallation................................................................... 30

4 July 2007
 1 Introduction

1 Introduction
1.1 About this Document
This documentation is located at the following address:
service.sap.com/installNW70 Æ 4 – Installation - Clients

Purpose
You can use the portal drive client to assign KM folders to Windows drive letters. This allows
you to work with documents in KM folders in the same way as documents on other Windows
drives.
This documentation describes how to install and deploy SAP NetWeaver Portal Drive Client
on Windows platforms.

Integration
You use the portal drive client to access documents stored in Knowledge Management
repositories. NetWeaver Enterprise Portal (EP) must be installed on the server.

Example
You want to assign room folders or Collaboration rooms to Windows drive letters so that you
can access room documents directly on Windows.

1.2 Before You Start

1.2.1 SAP Notes for the Installation
You must read the following SAP Notes before you start the installation. These SAP Notes
contain the most recent information on the installation, as well as corrections to the
installation documentation.
Make sure that you have the most up-to-date version of each SAP Note, which you can find
in the SAP Service Marketplace at the following Internet address:
service.sap.com/notes.
SAP Note Title Description
Number
911449 Portal Drive: Central note SECTION I: Download of Portal Drive
SECTION II: Portal Drive Versions
SECTION III: Portal Drive Versions:
major corrections / enhancements
SECTION IV: Portal Drive logs - where
to find on the client

July 2007 5
2 Preparation

2 Preparation
2.1 Client Requirements
Make sure that the client PCs meet the following minimum requirements:
• Windows NT/2000/XP
• Network connection
• 128 MB RAM
• 10 MB free disk space on the hard drive

2.2 Downloading the Installer from the SAP

Service Marketplace
Download the installer from the SAP Service Marketplace.
The installer is located at the following address: service.sap.com Æ Software Download Æ
Download Æ Support Packages and Patches Æ Entry by Application Group Æ SAP
NetWeaver Æ SAP NETWEAVER Æ SAP NETWEAVER 04 Æ Entry by Component Æ
Frontend Æ Portal Drive 4.4 Æ Windows Server on IA32 32bit.

2.3 Installation Server

You need a file server in your network to set up an installation server for the network
installation. It should have a Windows server version, such as Windows 2003 Server.
Decide which host you want to use as the installation server. The host that you select to be
the installation server must be available to all users at all times.

6 July 2007
 3 Simple Installation

3 Simple Installation
This procedure describes how to install the portal drive client on a single PC.

Prerequisite
You have administrator permissions on the PC in question.

Procedure
1. Download the installation file from the SAP Service Marketplace.
The installer is located at service.sap.com Æ Software Download Æ Download Æ
Support Packages and Patches Æ Entry by Application Group Æ SAP NetWeaver Æ
SAP NETWEAVER Æ SAP NETWEAVER 04 Æ Entry by Component Æ Frontend Æ
Portal Drive 4.4 Æ Windows Server on IA32 32bit.
2. Unzip the ZIP file.
The ZIP file contains the installation file, which is called xPortaldrive.exe.
3. To start the installation on your PC, double-click the xPortaldrive.exe file.
The SAP front-end installer starts.
Follow the instructions on the screen.
4. Once the installer has finished, restart the PC.

To complete the installation, you must restart the client PC.

July 2007 7
3 Simple Installation

3.1 First Steps

Once you have installed the portal drive client and restarted the host, the SAP NetWeaver
Portal Drive window appears.

The system tray of the task bar contains the icon (SAP NetWeaver Portal Drive).

8 July 2007
 3 Simple Installation

Connecting a Drive
To connect a drive, you must first create a service for it. This only needs to be done the first
time.
1. Choose Service Æ New.

2. Enter a name for the service, the server URL, and your user name.
To find out the server URL, proceed as follows:
a. In the portal, navigate to the folder that you want to connect.
b. Open the Details dialog box of the folder that you want to connect.
c. In the Details dialog box, choose Settings Æ Properties Æ Access Links.
d. Copy the WebDAV URL to your Windows clipboard, and paste it into the
Server URL field in the portal drive client.

3. Choose OK.

July 2007 9
3 Simple Installation

4. In the Drive dropdown list, choose a drive letter to use.

5. Choose Work Online.

The folder that you have connected is displayed in Windows Explorer.

Changing the Language

Proceed as follows to change the language:
a. Go to the Advanced tab page.
b. Choose a language.
The language change only takes effect once you restart the portal drive.

c. To close the portal drive, use the secondary mouse button to click the icon
(SAP NetWeaver Portal Drive) in the system tray of the task bar.
d. To restart the portal drive, choose Start Æ All Programs Æ SAP Frontend Æ
Portal Drive Æ Portal Drive Client from the Windows Start menu.

10 July 2007
 3 Simple Installation

Displaying Help
To display information on using the portal drive client, choose Help from the SAP NetWeaver
Portal Drive.

July 2007 11
4 Central Installation

4 Central Installation
This procedure describes how to install the portal drive client on a large number of PCs in
your company.
1. Set up an installation server in your network.
More information: Setting Up an Installation Server [Page 13]
2. Once you have set up an installation server, you can install the portal drive client as
follows:
• Users can install the portal drive client manually from the installation server.
More information: User Installation [Page 14]
• You can use a logon script to start an unattended installation on client hosts.
More information: Unattended Installation [Page 15]

12 July 2007
 4 Central Installation

4.1 Setting Up an Installation Server

Use
You have to set up an installation server for a central installation. The system copies all files
required for the installation on client hosts to a released folder on the installation server.

Prerequisites
To set up an installation server for the network installation, you need a file server in your
network. It should have a Windows server version, such as Windows 2003 Server.

Procedure
Carry out the following steps on the host that you want to use as the installation server:
1. Download the installation file from the SAP Service Marketplace.
The installer is located at service.sap.com Æ Software Download Æ Download Æ
Support Packages and Patches Æ Entry by Application Group Æ SAP NetWeaver Æ
SAP NETWEAVER Æ SAP NETWEAVER 04 Æ Entry by Component Æ Frontend Æ
Portal Drive 4.4 Æ Windows Server on IA32 32bit.
2. Unzip the ZIP file.
The ZIP file contains the xPortaldrive.exe installation file.
3. Create a temporary folder such as C:\Temp\PortalDrive.
4. Open a command prompt and extract the installer to the temporary folder using the
following command:
xPortalDrive.exe /extract=“<path_to_temporary_folder>“
Example:
xPortalDrive.exe /extract=“C:\Temp\PortalDrive“
5. To start the installation program for the installation server, go to the setup folder and
double-click the NwCreateInstServer.exe file.
Example:
C:\Temp\PortalDrive\setup\NwCreateInstServer.exe
6. Follow the instructions on the screen.
During the installation process, create a folder for the installation server (for example,
C:\PortalDriveInstServer) and release the folder in the network.
7. Once you have completed all steps, the SAPSetup Installation Server Administration Tool
opens.
For detailed information on the SAPSetup Installation Server Administration Tool, see
the following files in the Setup folder for the installation server:
• Installation Server Help.chm
• Workstation Installation Help.chm
You need a user account with administrator permissions on all client PCs to install
the portal drive client centrally. For more information, see the Installation Server
Help.chm file at Administering an Installation Server Æ Configuring Local Security
Handling.

July 2007 13
4 Central Installation

4.2 User Installation

Use
Once you have set up an installation server, users can start the installation process on client
hosts in the network themselves.

Procedure
1. Enter the following command line into the prompt on the user PC:
\\<name_of_the_installation_server>\PortalDriveInstServer\SapW
fcSetup.exe
2. Follow the instructions on the screen.
3. Once the installation process has finished, restart the client PC.

To complete the installation, you must restart the client PC.

14 July 2007
 4 Central Installation

4.3 Unattended Installation

Use
Once you have set up an installation server, you can start an unattended installation on all
client hosts using a logon script.

Procedure
Use one of the following command lines in your logon script:
• \\<name_of_the_installation_server>\PortalDriveInstServer\setu
p\NwSapSetup.exe /product="WFC" /noDLG
Only a progress bar appears on the screen of the host PC.
• \\<name_of_the_installation_server>\PortalDriveInstServer\setu
p\NwSapSetup.exe /product="WFC" /silent
The installation takes place completely in the background with no progress bar on the
host PC. Users are not informed when the installation is complete.

If the unattended installation variant is used, users are not asked to restart
their host. However, you must restart the client host to complete the
installation. You therefore have to make sure that all client hosts are restarted
following the installation.

July 2007 15
5 Post Installation: Central Configuration

5 Post Installation: Central Configuration

Use
You can use connection settings to centrally configure and update the assignment of KM
folders to drive letters and various options such as the cache size on client hosts.

Procedure
1. Create a central configuration file (for example, config.xml), and upload it to a Web
server.
More information: Central Configuration File [page 17]
2. Create the following two XML files so that the clients can read the central configuration
file when they start up:
File Description
update.xml You also store this file on a Web server.
You specify a date and the URL of the config.xml file in this
file.
More information: update.xml File [page 27]
admin.cfg You store this file on the client hosts in the portal drive installation
directory.
You specify the URL of the update.xml file here.
More information: admin.cfg File [page 28]

Result
At startup, the portal drive reads the admin.cfg file in the installation directory. It must
contain a URL for the update.xml file.
The portal drive now checks the date that you specified in the update.xml file. The portal
drive only downloads the central configuration file to the client PC again if the date element
has a new value in comparison with the last configuration update.

Configuration Files

update.xml config.xml

Web Server

admin.cfg

Client PC

16 July 2007
 5 Post Installation: Central Configuration

5.1 Central Configuration File

How to Use the Configuration File
The configuration file is an XML file (for example, config.xml). The first line in the file must
be <?xml version="1.0" ?> and the rest of the file is enclosed in a <wfc-config>
tag. Each attribute that needs to be set must be defined in its own <item> tag in the
configuration file.
For example, to set the cache size to 512MB and to start Windows Explorer upon connection,
a complete configuration file might appear as follows:
<?xml version="1.0" ?>
<wfc-config>
<item>
<name>CacheSize</name>
<value>512</value>
</item>
<item>
<name>StartExplorer</name>
<value>1</value>
</item>
</wfc-config>

Preventing a User from Overriding the Value

For some parameters, there may be a need to prevent a user from overriding values. This is
done on a per attribute basis by the presence of the <locked> tag in the configuration file.
For example, to set the cache size to 512MB and prevent the user from updating this value,
the configuration file would include a definition like the following:

<item>
<name>CacheSize</name>
<value>512</value>
<locked>1</locked>
</item>

Currently, locked fields are not reflected in the portal drive user interface. This
means that a user can override a value by changing its value on the screen;
however, if the value is declared as being locked, the system does not use
the change.

July 2007 17
5 Post Installation: Central Configuration

5.1.1 General Settings

The table below provides a list of attributes that can be configured centrally, and provides
details on the type of data, permitted values, and default values.

How to Read the Table:

● Name is how the item must be referenced in the configuration file.

● Description describes the use of the parameter.

● Type in registry indicates how this item is stored in the registry. This is either
DWORD for numbers, String for text values or Binary for dates and times. This is for
informational purposes only and cannot be changed.

● Applies to describes whether this parameter applies to all users (Computer) or just
the current user (User). This is for informational purposes only and cannot be
changed.

● Possible values describes which values are acceptable.

● Default value is the value that is used if no other value is specified.

18 July 2007
 5 Post Installation: Central Configuration

General Settings

Name Attributes
CacheSize Description: Size of the file cache
Type in registry: DWORD
Applies to: Computer
Possible values: Number, for example, 100
Default value: 32

ClearCacheUponDisconnect Description: Dictates whether or not the cache is cleared

when a drive is disconnected
Type in registry: DWORD
Applies to: User
Possible values: 0 (Disabled), 1 (Enabled)
Default value: 0

Permitted Servers Description: A list of permitted servers to which you can

connect. The names must be separated by semicolons. The
wildcard * can be used to specify a range of subdomains. For
example, *.sap.com would allow connectivity to
server1.sap.com and server2.sap.com.
Type in registry: String
Applies to: Computer
Possible values: String specifying the list of servers to connect
to
Default value: Empty; you can connect to all servers.

RestrictServiceEditing Description: Controls whether or not the user can edit the
server attributes for services, including creating, deleting and
modifying services. If this is enabled, the user can only set
service settings such as the sharing level, user
name/password, and auto-start options for predefined
services.
Type in registry: DWORD
Applies to: Computer
Possible values: 0 (Disabled), 1 (Enabled)
Default value: 0

July 2007 19
5 Post Installation: Central Configuration

UserName Description: the user name of the user. It is used for lock
identification
Type in registry: String
Applies to: User
Possible values: String for the user name
Default value: The user name that is used to establish the
connection

Language Description: Language for starting the portal drive

Type in registry: String
Applies to: User
Possible values: en-US (English), de (German), ja
(Japanese), fr (French), cs (Czech)
Default value: en-US

StartExplorer Description: Controls whether or not a Windows Explorer

window appears when a user connects
Type in registry: DWORD
Applies to: User
Possible values: 0 (Disabled), 1 (Enabled)
Default value: 1

DisableOffline Description: Controls whether or not the offline feature is

enabled
Type in registry: DWORD
Applies to: User
Possible values: 0 (Offline is turned ON), 1 (Offline is turned
OFF)
Default value: 0

ShowExtraTab Description: Controls whether or not the Advanced tab page is

displayed
Type in registry: DWORD
Applies to: User
Possible values: 0 (Disabled), 1 (Enabled)
Default value: 1

20 July 2007
 5 Post Installation: Central Configuration

ExtraOptions Description: Controls logging options on the Advanced tab

page
Type in registry: DWORD
Applies to: User
Possible values: A combination of values. Useful ones are: 1
(Log HTTP only), 3 (Log HTTP + Directory Listings), 9 (Log
HTTP + Monitor Messages), b (hex) (Log HTTP + Directory
Listings + Monitor Messages)
Default value: 9

AlwaysLockList Description: List of applications to which the automatic lock

upon opening feature applies
Type in registry: String
Applies to: User
Possible values: The name of the .exe processes, separated
by semicolons
Default value:
notepad;wordpad;winword;excel;winproj;powerpnt

NeverLockList Description: List of applications for which the auto lock upon
opening feature does not apply
Type in registry: String
Applies to: User
Possible values: The name of the .exe processes, separated
by semicolons
Default value:
explorer;wincmd32;totalcmd;outlook;cmd;ntvdm;
WINOA386;WINZIP32;WinRAR;winace;salamand;efcwl

UnlockByAppLockList Description: List of applications that are unlocked when the

application's process has terminated
Type in registry: String
Applies to: User
Possible values: The name of the .exe processes, separated
by semicolons
Default value: notepad;wordpad;photoed;uedit32

July 2007 21
5 Post Installation: Central Configuration

DefaultSharingLevel Description: Default sharing level for a new service.

Type in registry: DWORD
Applies to: User
Possible values: 0, 1, 2, 3 (None, Light, Medium, Heavy)
Default value: 2 (Medium)

SyncOnConnect Description: Controls whether or not a drive synchronizes

upon connecting
Type in registry: DWORD
Applies to: User
Possible values: 0, 1
Default value: 1

SyncOnDisconnect Description: Controls whether or not a drive synchronizes

upon disconnecting
Type in registry: DWORD
Applies to: User
Possible values: 0, 1
Default value: 0

DisplayOmitStoreMessages Description: When enabled, the system displays a message in

the status monitor indicating when an attempt to save a file
was quietly blocked by the portal drive. This is best used for
debugging purposes.
Type in registry: DWORD
Applies to: User
Possible values: 0 (Messages are not logged), 1 (Messages
are logged)
Default value: 0

MultipleConnections Description: The maximum number of simultaneous

connections that the portal drive can maintain to a server for
each service.
Type in registry: DWORD
Applies to: Computer
Possible values: Any number
Default value: 2

22 July 2007
 5 Post Installation: Central Configuration

TCPTimeout Description: The number of seconds portal drive waits for a

response from the server before it stops and retries the
request. The portal drive retries up to two times before failing
the request.
Type in registry: DWORD
Applies to: Computer
Possible values: Any number of seconds
Default value: 30

SharingLevelRefreshTimeout Description: A list of the refresh timeouts (in seconds) for each
sharing level. The sharing levels are listed in the following
order: None, Light, Medium, Heavy.
Type in registry: DWORD
Applies to: Computer
Possible values: Comma-separated list of numbers.
Default value: 3600,900,300,60

SharingLevelAutoLocks Description: A list describing the auto lock behavior for each
sharing level. The sharing levels are listed in the following
order: None, Light, Medium, Heavy.
Type in registry: DWORD
Applies to: Computer
Possible values: Comma-separated list of 1 (yes) or 0 (no).
Default value: 0,1,1,1

SharingLevelCheckBeforeOpen Description: A list describing the check before open behavior

for each sharing level. The sharing levels are listed in the
following order: None, Light, Medium, Heavy.
Type in registry: DWORD
Applies to: Computer
Possible values: Comma-separated list of 1 (yes) or 0 (no).
Default value: 0,1,1,1

July 2007 23
5 Post Installation: Central Configuration

SharingLevelCachedListings Description: A list describing the initial folder listing behavior

for each sharing level. When this feature is enabled, the portal
drive displays the cached folder listing during the connection
process. If not, it waits until the directory list has been
retrieved from the server before displaying the folder list. The
sharing levels are listed in the following order: None, Light,
Medium, Heavy.
Type in registry: DWORD
Applies to: Computer
Possible values: Comma-separated list of 1 (yes) or 0 (no).
Default value: 1,1,0,0

ForceSearchTapeBackup Description: Windows search has an advanced option -

Search tape backup - that MUST be checked to enable users
to search network drives. This has been observed in Windows
SP2. As a workaround, the portal drive can automatically
enable this feature so the user can always search on a
network drive. This feature is enabled by default. This mass
configuration setting is used to change the default setting of
this feature.
Type in registry: DWORD
Applies to: Computer
Possible values: 0 (deselects the feature), 1 (selects the
feature), 2 (does nothing; leaves the feature as it was).
Default value: 1 (checked)

HelpPageURL Description: The URL to the portal drive help pages. This is
the URL for the Help button in the main portal drive window.
Type in registry: String
Applies to: User
Possible values: An HTTP/S URL
Default value:
http://help.sap.com/saphelp_nw04/helpdata/en/42/
C99B91341A6BADE10000000A1553F6/frameset.htm

RemoteDirectoryDelete Description: Controls the behavior for deleting folders. If it is

enabled, the portal drive only issues one delete request to the
server. If it is disabled, the portal drive issues a delete request
for each file and subfolder in the tree.
Type in registry: DWORD
Applies to: User
Possible values: 0 (disabled), 1 (enabled)
Default value: 1 (enabled)

24 July 2007
 5 Post Installation: Central Configuration

AskOnDisconnection Description: Controls the display of the dialog box that warns
you to ensure that all your files are closed before
disconnecting the drive.
Type in registry: DWORD
Applies to: User
Possible values: 0 (disabled), 1 (enabled)
Default value: 1 (enabled)

5.1.2 Service Settings

To define a service, use the format below for each service you want to define.
<item>
<type>service</type>
<name>Documents</name>
<hostname>myserver.mycompany.com</hostname>
<port>1234</port>
<secure>1</secure>
<server-directory>/irj/go/km/docs/documents</server-directory>
<drive-letter>k</drive-letter>
<sharing-level>3</sharing-level>
<auto-reconnect>1</auto-reconnect>
</item>

July 2007 25
5 Post Installation: Central Configuration

Service Settings

Name Attributes
type Description: Defines the item type
Possible values: Must be service

name Description: Name of the service

Possible values: Any string, for example,
Documents

hostname Description: Host name of the server, for example,

myserver.mycompany.com
Possible values: A string name representing the
host name

port Description: Port number for the connection on the

server
Possible values: The number of the port. If not
specified, this setting defaults to 80 or 443
depending on the value of secure.

secure Description: Determines whether or not HTTP or

HTTPS should be used
Possible values: 0 (use HTTP), 1 (use HTTPS)

server-directory Description: Server directory to mount

Possible values: A string representing a directory
path, for example
/irj/go/km/docs/documents

drive-letter Description: Drive letter to use for this service. This

is a required field.
Possible values: Any letter from D-Z. If the chosen
letter is not available or if no letter is specified, the
first letter available is used.
sharing-level Description: Sharing level to use for this service
Possible values: 0 (None), 1 (Low), 2 (Medium), 3
(High)
Default value: 2 (Medium)

26 July 2007
 5 Post Installation: Central Configuration

auto-reconnect Description: Controls whether or not the service is

connected automatically on startup
Possible values: 0 (No), 1 (Yes)
Default value: 0 (No)

5.2 update.xml File

Create an XML file with the name update.xml in accordance with the example below:
<?xml version="1.0" ?>
<wfc-update>
<config-update>
<date>31.12.2007</date>
<location>http://myserver:1234/mydirectory/config071231.xml</l
ocation>
</config-update>
</wfc-update>

Elements of the update.xml file

Element Description
<date> You can enter any character string here.
The portal drive saves this value when it downloads a
configuration file. The portal drive only downloads the
config.xml file again if the update.xml file contains a new
value.
<location> Enter the URL to the central configuration file (config.xml) on a
Web server.
Make sure that all users can access this URL.

Upload the update.xml file to a Web server.

July 2007 27
5 Post Installation: Central Configuration

5.3 admin.cfg File

Create an XML file with the name admin.cfg in accordance with the following example:
<?xml version="1.0" ?>
<wfc-config>
<item>
<name>AutoupdateURL</name>
<value>http://<Server Host>:<Port>/<Path>/update.xml</value>
</item>
</wfc-config>

Elements of the admin.cfg File

Element Description
<name> Must be AutoupdateURL.
<value> Enter the URL to the update.xml file on a Web server.

Deploy the admin.cfg file on the client hosts. This file must be located in the same directory
as the PortalDrive.exe file (by default, this is located at C:\Program
Files\SAP\PortalDrive).

28 July 2007
 6 Upgrade

6 Upgrade
Use
You can update your installation server when a new version of the portal drive client becomes
available. The subsequent upgrade of the client is the same as for a new installation.

Procedure
1. Create a temporary folder on the server, for example C:\Temp\PortalDrive_Update.
2. Extract the installer to the temporary folder using the following command:
xPortalDrive.exe /extract=“<path_to_temporary_folder>“
Example:
xPortalDrive.exe /extract=“C:\Temp\PortalDrive_Update“
3. To update the installation server, execute the following command:
C:\<path_to_temporary_folder>\setup\NwUpdateInstServer.exe
/dest="C:\PortalDriveInstServer\setup"
Example:
C:\Temp\PortalDrive_Update\setup\NwUpdateInstServer.exe
/dest="C:\PortalDriveInstServer\setup"
4. Once you have set up an installation server, users can start the installation or update
on client hosts in the network themselves or you can use a logon script to start an
unattended update on all client hosts.
Use the same commands as for the initial installation for the update.
More information: User Installation [Page 14] or Unattended Installation [Page 15]

July 2007 29
7 Uninstallation

7 Uninstallation

7.1 User Uninstallation

Use
Users can uninstall the portal drive client from their client hosts whenever they want.

Procedure
1. Before uninstalling, you have to exit portal drive.

a. Right-click on the (SAP NetWeaver Portal Drive) icon in the system tray.
b. Select Exit.
2. In the Windows Control Panel, choose Add/Remove Programs.
c. Scroll down to Portal Drive and select the Add/Remove button.
d. Restart your computer to complete the process.

You must restart the client host to complete the uninstallation.

7.2 Unattended Uninstallation

Use
You can use a logon script to start the uninstallation process on all client hosts.

Procedure
Use one of the following command lines in your logon script:
• \\<name_of_the_installation_server>\PortalDriveInstServer\setu
p\NwSapSetup.exe /product="WFC" /noDLG /uninstall
Only a progress bar appears on the screen of the client PC.
• \\<name_of_the_installation_server>\PortalDriveInstServer\setu
p\NwSapSetup.exe /product="WFC" /silent /uninstall
The uninstallation takes place completely in the background and users are not
informed about the progress. Note that users are not informed when the installation is
complete.

In the case of an unattended uninstallation, users are not prompted to restart

their hosts. However, you must restart your host to complete the
uninstallation. You must therefore make sure that all client hosts are restarted
following the uninstallation.

30 July 2007