win_J

PUBLIC

Installation Guide

SAP CRM 5.0 SR2 Javaon Windows: OracleIncluding:

CRM Java Components (JCRMCRM Business Packages (BP-CRM)CRM Mapbox (MBX)NetWeaver Java Application Server (AS-Java)NetWeaver Development Infrastructure (DI)NetWeaver EP Core (EPC)NetWeaver Enterprise Portal (EP)Application Sharing Server (Optional Standalone Unit)

Target Audience

n System Administratorsn Technical Consultants

Document version: 1.0 12/04/2006

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The information containedherein may be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook, and PowerPoint areregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,iSeries, pSeries, xSeries, zSeries, System i, System i5, Systemp, System p5, System x, System z, System z9, z/OS, AFP,Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix,i5/OS, POWER, POWER5, POWER5+, OpenPower andPowerPC are trademarks or registered trademarks of IBMCorporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Readerare either trademarks or registered trademarks of AdobeSystems Incorporated in the United States and/or othercountries.

Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered

trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame,

WinFrame, VideoFrame, and MultiWin are trademarks orregistered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarksor registered trademarks of W3C, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of SunMicrosystems,

Inc., used under license for technology invented andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and services mentionedherein as well as their respective logos are trademarks or

registered trademarks of SAP AG in Germany and in severalother countries all over the world. All other productand service names mentioned are the trademarks of theirrespective companies. Data contained in this documentserves informational purposes only. National productspecifications may vary.

These materials are subject to change without notice.These materials are provided by SAP AG and its affiliatedcompanies (SAP Group) for informational purposesonly, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions withrespect to thematerials. The only warranties for SAP Groupproducts and services are those that are set forth in theexpress warranty statements accompanying such productsand services, if any. Nothing herein should be construed asconstituting an additional warranty.

This document was created using stylesheet 2006-06-15(V4.3) and XSLT processor SAXON 6.5.2 from Michael Kay(http://saxon.sf.net/), XSLT version 1.

DisclaimerSome components of this product are based on Java. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.

Any Java Source Code delivered with this product isonly to be used by SAPs Support Services and may not bemodified or altered in any way.

Legal Software Terms

Terms for Included Open Source SoftwareThis SAP software contains also the third party opensource software products listed below. Please note that forthese third party products the following special terms andconditions shall apply.

1. This software was developed using ANTLR.

2. gSOAP

2/210 PUBLIC 12/04/2006

Part of the software embedded in this product is gSOAPsoftware. Portions created by gSOAP are Copyright(C) 2001-2004 Robert A. van Engelen, Genivia inc. AllRights Reserved.THE SOFTWARE IN THIS PRODUCT WAS IN PARTPROVIDED BY GENIVIA INC AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUTNOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE ARE DISCLAIMED. INNO EVENT SHALL THE AUTHOR BE LIABLEFOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSEDAND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITYOF SUCH DAMAGE."

3. SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingNeurottstrasse 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive,non-transferrable, royalty-free license to usethe STLport.org C++ library (STLport) and itsdocumentation without fee.

B) By downloading, using, or copying STLport orany portion thereof Customer agrees to abideby the intellectual property laws, and to all ofthe terms and conditions of this Agreement.

C) The Customer may distribute binaries compiledwith STLport (whether original or modified)without any royalties or restrictions.

D) Customer shall maintain the followingcopyright and permissions notices on STLportsources and its documentation unchanged:Copyright 2001 SAP AG

E) The Customer may distribute original ormodified STLport sources, provided that:n The conditions indicated in the above

permissions notice are met;n The following copyright notices are retained

when present, and conditions provided inaccompanying permission notices are met:Coypright 1994 Hewlett-PackardCompanyCopyright 1996,97 Silicon GraphicsComputer Systems Inc.Copyright 1997 Moscow Center forSPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute andsell this software and its documentation forany purposes is hereby granted without fee,provided that the above copyright notice appearin all copies and that both that copyright noticeand this permission notice appear in supportingdocumentation. Hewlett-Packard Companymakes no representations about the suitabilityof this software for any purpose. It is providedas is without express or implied warranty.Permission to use, copy, modify, distribute andsell this software and its documentation for anypurpose is hereby granted without fee, providedthat the above copyright notice appear in allcopies and that both that copyright notice andthis permission notice appear in supportingdocumentation. Silicon Graphics makes norepresentations about the suitability of thissoftware for any purpose. It is provided as iswithout express or implied warranty.Permission to use, copy, modify, distribute andsell this software and its documentation forany purposes is hereby granted without fee,provided that the above copyright notice appearin all copies and that both that copyright noticeand this permission notice appear in supportingdocumentation. Moscow Center for SPARCmakes no representations about the suitabilityof this software for any purpose. It is providedas is without express or implied warranty.Boris Fomitchev makes no representationsabout the suitability of this software for anypurpose. This material is provided "as is", withabsolutely no warranty expressed or implied.Any use is at your own risk. Permission touse or copy this software for any purpose is

12/04/2006 PUBLIC 3/210

hereby granted without fee, provided the abovenotices are retained on all copies. Permissionto modify the code and to distribute modifiedcode is granted, provided the above noticesare retained, and a notice that the code wasmodified is included with the above copyrightnotice.Permission to use, copy, modify, distributeand sell this software and its documentationfor any purposes is hereby granted withoutfee, provided that the above copyright noticeappear in all copies and that both that copyrightnotice and this permission notice appear insupporting documentation. SAP makes norepresentations about the suitability of thissoftware for any purpose. It is provided with alimited warranty and liability as set forth in theLicense Agreement distributed with this copy.SAP offers this liability and warranty obligationsonly towards its customers and only referringto its modifications.

b) Support and MaintenanceSAP does not provide software maintenance for theSTLport. Software maintenance of the STLporttherefore shall be not included.All other services shall be charged according to therates for services quoted in the SAP List of Pricesand Conditions and shall be subject to a separatecontract.

c) Exclusion of warrantyAs the STLport is transferred to the Customer on aloan basis and free of charge, SAP cannot guaranteethat the STLport is error-free, without materialdefects or suitable for a specific application underthird-party rights. Technical data, sales brochures,advertising text and quality descriptions producedby SAP do not indicate any assurance of particularattributes.

d) Limited Liability

A) Irrespective of the legal reasons, SAP shall onlybe liable for damage, including unauthorizedoperation, if this (i) can be compensated underthe Product Liability Act or (ii) if caused due togross negligence or intent by SAP or (iii) if basedon the failure of a guaranteed attribute.

B) If SAP is liable for gross negligence or intentcaused by employees who are neither agents ormanagerial employees of SAP, the total liabilityfor such damage and a maximum limit on thescope of any such damage shall depend on

the extent to which its occurrence ought tohave anticipated by SAP when concluding thecontract, due to the circumstances known toit at that point in time representing a typicaltransfer of the software.

C) In the case of Art. 4.2 above, SAP shall notbe liable for indirect damage, consequentialdamage caused by a defect or lost profit.

D) SAP and the Customer agree that the typicalforeseeable extent of damage shall under nocircumstances exceed EUR 5,000.

E) The Customer shall take adequate measuresfor the protection of data and programs, inparticular by making backup copies at theminimum intervals recommended by SAP. SAPshall not be liable for the loss of data and itsrecovery, notwithstanding the other limitationsof the present Art. 4 if this loss could have beenavoided by observing this obligation.

F) The exclusion or the limitation of claims inaccordance with the present Art. 4 includesclaims against employees or agents of SAP.

4. Adobe Document ServicesAdobe, the Adobe logo, Acrobat, PostScript, and Readerare either registered trademarks or trademarks ofAdobe Systems Incorporated in the United States and/ or other countries. For information on Third Partysoftware delivered with Adobe document services andAdobe LiveCycle Designer, see SAP Note 854621.

5. Apache License, Version 2.0

a) Definitions:n "License" shall mean the terms and conditions

for use, reproduction, and distributionas defined by Sections 1 through 9 of thisdocument.

n "Licensor" shall mean the copyright owner orentity authorized by the copyright owner thatis granting the License.

n "Legal Entity" shall mean the union of theacting entity and all other entities that control,are controlled by, or are under commoncontrol with that entity. For the purposesof this definition, "control" means (i) thepower, direct or indirect, to cause the directionor management of such entity, whether bycontract or otherwise, or (ii) ownership offifty percent (50%) or more of the outstandingshares, or (iii) beneficial ownership of suchentity.

4/210 PUBLIC 12/04/2006

n "You" (or "Your") shall mean an individual orLegal Entity exercising permissions granted bythis License.

n "Source" form shall mean the preferred formfor making modifications, including but notlimited to software source code, documentationsource, and configuration files.

n "Object" form shall mean any form resultingfrom mechanical transformation or translationof a Source form, including but notlimited to compiled object code, generateddocumentation, and conversions to othermedia types.

n "Work" shall mean the work of authorship,whether in Source or Object form, madeavailable under the License, as indicated by acopyright notice that is included in or attachedto the work (an example is provided in theAppendix below).

n "Derivative Works" shall mean any work,whether in Source or Object form, that isbased on (or derived from) the Work and forwhich the editorial revisions, annotations,elaborations, or other modifications represent,as a whole, an original work of authorship. Forthe purposes of this License, Derivative Worksshall not include works that remain separablefrom, or merely link (or bind by name) to theinterfaces of, the Work and Derivative Worksthereof.

n "Contribution" shall mean any work ofauthorship, including the original version ofthe Work and any modifications or additionsto that Work or Derivative Works thereof,that is intentionally submitted to Licensor forinclusion in the Work by the copyright owneror by an individual or Legal Entity authorizedto submit on behalf of the copyright owner.For the purposes of this definition, "submitted"means any form of electronic, verbal, or writtencommunication sent to the Licensor or itsrepresentatives, including but not limited tocommunication on electronic mailing lists,source code control systems, and issue trackingsystems that are managed by, or on behalfof, the Licensor for the purpose of discussingand improving the Work, but excludingcommunication that is conspicuously markedor otherwise designated in writing by thecopyright owner as "Not a Contribution."

n "Contributor" shall mean Licensor and anyindividual or Legal Entity on behalf of whom aContribution has been received by Licensor andsubsequently incorporated within the Work.

b) Grant of Copyright LicenseSubject to the terms and conditions of this License,each Contributor hereby grants to You a perpetual,worldwide, non-exclusive, no-charge, royalty-free,irrevocable copyright license to reproduce, prepareDerivative Works of, publicly display, publiclyperform, sublicense, and distribute the Work andsuch Derivative Works in Source or Object form.

c) Grant of Patent LicenseSubject to the terms and conditions of this License,each Contributor hereby grants to You a perpetual,worldwide, non-exclusive, no-charge, royalty-free,irrevocable (except as stated in this section) patentlicense to make, have made, use, offer to sell, sell,import, and otherwise transfer the Work, wheresuch license applies only to those patent claimslicensable by such Contributor that are necessarilyinfringed by their Contribution(s) alone or bycombination of their Contribution(s) with theWork to which such Contribution(s) was submitted.If You institute patent litigation against any entity(including a cross-claim or counterclaim in alawsuit) alleging that the Work or a Contributionincorporated within the Work constitutes direct orcontributory patent infringement, then any patentlicenses granted to You under this License for thatWork shall terminate as of the date such litigation isfiled.

d) RedistributionYou may reproduce and distribute copies of theWork or Derivative Works thereof in any medium,with or without modifications, and in Source orObject form, provided that You meet the followingconditions:

A) You must give any other recipients of the Workor Derivative Works a copy of this License; and

B) You must cause any modified files to carryprominent notices stating that You changedthe files; and

C) You must retain, in the Source form of anyDerivative Works that You distribute, allcopyright, patent, trademark, and attributionnotices from the Source form of the Work,excluding those notices that do not pertain toany part of the Derivative Works; and

12/04/2006 PUBLIC 5/210

D) If the Work includes a "NOTICE" text file as partof its distribution, then any Derivative Worksthat You distribute must include a readablecopy of the attribution notices contained withinsuch NOTICE file, excluding those notices thatdo not pertain to any part of the DerivativeWorks, in at least one of the following places:within a NOTICE text file distributed as partof the Derivative Works; within the Sourceform or documentation, if provided alongwith the Derivative Works; or, within a displaygenerated by the Derivative Works, if andwherever such third-party notices normallyappear. The contents of the NOTICE file arefor informational purposes only and do notmodify the License. You may add Your ownattribution notices within Derivative Works thatYou distribute, alongside or as an addendum tothe NOTICE text from the Work, provided thatsuch additional attribution notices cannot beconstrued as modifying the License.

You may add Your own copyright statement toYour modifications and may provide additionalor different license terms and conditions for use,reproduction, or distribution of Yourmodifications,or for any such Derivative Works as a whole,provided Your use, reproduction, and distributionof the Work otherwise complies with the conditionsstated in this License.

e) Submission of ContributionsUnless You explicitly state otherwise, anyContribution intentionally submitted for inclusionin the Work by You to the Licensor shall beunder the terms and conditions of this License,without any additional terms or conditions.Notwithstanding the above, nothing herein shallsupersede or modify the terms of any separatelicense agreement you may have executed withLicensor regarding such Contributions.

f) TrademarksThis License does not grant permission to usethe trade names, trademarks, service marks, orproduct names of the Licensor, except as requiredfor reasonable and customary use in describing theorigin of the Work and reproducing the content ofthe NOTICE file.

g) Disclaimer of WarrantyUnless required by applicable law or agreed to inwriting, Licensor provides the Work (and each

Contributor provides its Contributions) on an"AS IS" BASIS, WITHOUT WARRANTIES ORCONDITIONS OF ANY KIND, either expressor implied, including, without limitation,any warranties or conditions of TITLE,NON-INFRINGEMENT, MERCHANTABILITY,or FITNESS FOR A PARTICULAR PURPOSE.You are solely responsible for determining theappropriateness of using or redistributing the Workand assume any risks associated with Your exerciseof permissions under this License.

h) Limitation of LiabilityIn no event and under no legal theory, whether intort (including negligence), contract, or otherwise,unless required by applicable law (such as deliberateand grossly negligent acts) or agreed to in writing,shall any Contributor be liable to You for damages,including any direct, indirect, special, incidental,or consequential damages of any character arisingas a result of this License or out of the use orinability to use the Work (including but not limitedto damages for loss of goodwill, work stoppage,computer failure or malfunction, or any and allother commercial damages or losses), even if suchContributor has been advised of the possibility ofsuch damages.

i) Accepting Warranty or Additional LiabilityWhile redistributing the Work or Derivative Worksthereof, You may choose to offer, and charge a feefor, acceptance of support, warranty, indemnity, orother liability obligations and/or rights consistentwith this License. However, in accepting suchobligations, You may act only on Your own behalfand on Your sole responsibility, not on behalf ofany other Contributor, and only if You agree toindemnify, defend, and hold each Contributorharmless for any liability incurred by, or claimsasserted against, such Contributor by reason of youraccepting any such warranty or additional liability.

Documentation in the SAP ServiceMarketplaceYou can find this document at the following address:service.sap.com/instguides

6/210 PUBLIC 12/04/2006

Typographic ConventionsExample Description

< > Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, Enter your .

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address, for example, http://www.sap.com

/example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example n Words or characters quoted from the screen. These include field labels, screen titles,pushbutton labels, menu names, and menu options.

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, database table names, and key concepts of a programming languagewhen they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

12/04/2006 PUBLIC 7/210

Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. Youcan find the latest version on SAP Service Marketplace http://service.sap.com/instguides.

The following table provides an overview on the most important document changes:

Version Date Description

1.00 12/4/2006 Initial Version

8/210 PUBLIC 12/04/2006

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 151.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . 161.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 191.3 Information Available on SAP Service Marketplace . . . . . . . . . . 201.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 22

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 252.1 Basic System Variants . . . . . . . . . . . . . . . . . . . . . 252.2 How to Distribute Instances to Hosts . . . . . . . . . . . . . . . 262.3 System Configuration . . . . . . . . . . . . . . . . . . . . . 272.3.1 Distribution of Components to Disks . . . . . . . . . . . . . . . 282.3.2 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . 302.4 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . 332.5 Running Adobe Document Services on Non-Supported Platforms . . . . 392.6 Multiple Oracle Homes . . . . . . . . . . . . . . . . . . . . 392.7 Internet Pricing and Configurator . . . . . . . . . . . . . . . . 402.8 Application Sharing Server as an Optional Standalone Unit . . . . . . . 41

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 433.1 Hardware and Software Requirements . . . . . . . . . . . . . . . 433.1.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 443.1.2 Requirements Checklist for a Central System . . . . . . . . . . . . 453.1.3 Requirements Checklist for a Distributed System . . . . . . . . . . . 473.1.3.1 Requirements Checklist for the Central Services Instance . . . . . . . . 473.1.3.2 Requirements Checklist for the Database Instance . . . . . . . . . . 483.1.3.3 Requirements Checklist for the Central Instance . . . . . . . . . . . 493.1.3.4 Requirements Checklist for the Dialog Instance . . . . . . . . . . . 503.2 Checking the Windows File System . . . . . . . . . . . . . . . . 513.3 Checking the Windows Domain Structure . . . . . . . . . . . . . 513.4 Reducing the Size of the File Cache . . . . . . . . . . . . . . . . 523.5 Granting User Rights for the Installation . . . . . . . . . . . . . . 533.6 Performing a Domain Installation Without Being a Domain Administrator . 543.7 Preparing the SAP System Transport Host . . . . . . . . . . . . . 563.8 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 573.9 Installing the Java Development Kit . . . . . . . . . . . . . . . . 58

12/04/2006 PUBLIC 9/210

3.10 Prerequisites for the Business Package for SAP CRM . . . . . . . . . . 593.11 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 603.12 Downloading Installation DVDs from SAP Service Marketplace (Optional) . 61

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . 634.1 Installing the Oracle Database Software . . . . . . . . . . . . . . 634.2 Setting Up Multiple Homes (Optional) . . . . . . . . . . . . . . 654.3 Installing an SAP System Using SAPinst . . . . . . . . . . . . . . 664.3.1 Running SAPinst on Windows . . . . . . . . . . . . . . . . . . 664.3.2 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . 724.3.3 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 734.3.4 Performing a Remote Installation with SAPinst (Optional) . . . . . . . 744.3.5 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . 754.3.6 Entries in the Services File Created by SAPinst . . . . . . . . . . . . 774.4 Installing the Business Packages for SAP CRM . . . . . . . . . . . . 774.5 Installing Application Sharing Server as an Optional Standalone Unit . . . 78

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . 815.1 Starting and Stopping the SAP System . . . . . . . . . . . . . . . 825.2 Logging On to the SAP System . . . . . . . . . . . . . . . . . 835.3 Logging on to the Portal . . . . . . . . . . . . . . . . . . . . 855.4 Installing the SAP License . . . . . . . . . . . . . . . . . . . 875.5 Configuring Remote Connection to SAP Support . . . . . . . . . . 885.6 Checking the Startup Type of the Oracle Listener Service . . . . . . . . 885.7 Configuring the Oracle Listener . . . . . . . . . . . . . . . . . 885.8 Improving the Performance of the Oracle Database . . . . . . . . . . 885.9 Applying the Latest Kernel and Support Packages . . . . . . . . . . . 885.10 Performing a Full Installation Backup . . . . . . . . . . . . . . . 905.11 Post-Installation Steps for Adobe Document Services . . . . . . . . . 915.11.1 Assigning Roles to Users ADSUSER and ADS_AGENT . . . . . . . . . 915.11.2 Installation Check and Quick Tests for Adobe Document Services . . . . 925.12 Performing Post-Installation Steps for Composite Application Framework Core

(CAF Core) . . . . . . . . . . . . . . . . . . . . . . . . 935.13 Activating Internet Pricing and Configurator . . . . . . . . . . . . 945.14 Checking the Availability of Back-End Systems for CRM Java Components . 955.14.1 Creating a Back-End User . . . . . . . . . . . . . . . . . . . 955.14.2 Checking the Connection to the ABAP System . . . . . . . . . . . 965.14.3 Configuring and Checking the TREX Service . . . . . . . . . . . . 985.14.4 Checking the selling via eBay Processes . . . . . . . . . . . . . . 985.15 Post-Installation Steps for Workforce Deployment Application and Calculation

Services . . . . . . . . . . . . . . . . . . . . . . . . . . 995.15.1 Implementing WFMCORE 200 Using Transaction SAINT . . . . . . . . 99

10/210 PUBLIC 12/04/2006

5.15.2 Configuring the XCM Administration Tool for WFD Application andCalculation Services . . . . . . . . . . . . . . . . . . . . . 100

5.15.3 Checking Workforce Deployment Calculation Services . . . . . . . . 1025.15.4 Checking the Installation of WFD Application Services and WFD Calculation

Services . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.16 Post-Installation Steps for the Business Packages for SAP CRM . . . . . . 1055.16.1 Creating Roles for the SAP CRM Business Packages . . . . . . . . . . 1055.16.2 Installation of the Info Center for the SAP CRM Business Package . . . . . 1055.16.2.1 Importing the CRM Info Center Configurations and Directory Structure . . 1065.16.2.2 Activating Manual Ordering of Folders for the sapcrm Repository . . . . 1075.16.2.3 Creating Indexes and Taxonomies for the sapcrmnews Repository . . . . 1075.16.2.4 Creating the Index for the sapcrm Repository . . . . . . . . . . . . 1095.16.2.5 Configuring the Personal Search . . . . . . . . . . . . . . . . . 1095.16.2.6 Increasing the Number of JCo Connections . . . . . . . . . . . . . 1105.17 Post-Installation Steps for MapBox . . . . . . . . . . . . . . . . 1105.17.1 Assigning User Groups for MapBox Users . . . . . . . . . . . . . 1115.17.2 Configuring an RFC Destination for MapBox . . . . . . . . . . . . 1125.17.3 Performing Initial Configuration for MapBox . . . . . . . . . . . . 1125.17.4 Executing the MapBox . . . . . . . . . . . . . . . . . . . . 1195.17.5 Performing the Smoke Test for MapBox . . . . . . . . . . . . . . 1205.17.6 Ensuring Optimal Block Size settings . . . . . . . . . . . . . . . 1235.17.7 Adapting Memory Settings for the J2EE Engine . . . . . . . . . . . 1235.18 Post-Installation Steps for Application Sharing Server . . . . . . . . . 1245.19 Ensuring User Security . . . . . . . . . . . . . . . . . . . . 1245.20 Running the Template Installer . . . . . . . . . . . . . . . . . 1285.21 Checking the SAP Java Documentation . . . . . . . . . . . . . . 1305.22 Using Extended Configuration Management (XCM) . . . . . . . . . 1315.23 Accessing Configuration Documentation in the SAP Solution Manager . . 139

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 1416.1 Installation of Multiple Components in One Database (Optional) . . . . . 1416.2 Integration of LDAP Directory Services (Optional) . . . . . . . . . . 1436.3 Setting Up the Active Directory Services (Optional) . . . . . . . . . . 1466.4 Preparing User Management for an External ABAP System . . . . . . . 1476.5 Configuring User Management to Use an LDAP Directory (Optional) . . . 1506.6 Usage Type-Specific Initial Technical Configuration . . . . . . . . . . 1506.6.1 Initial Technical Configuration for Application Server . . . . . . . . . 1516.6.1.1 Initial Technical Configuration for Adobe Document Services . . . . . . 1516.6.1.2 Initial Technical Configuration for Composite Application Framework Core 1526.6.1.3 Configuring the Connection for System Landscape Directory . . . . . . 1526.6.2 Initial Technical Configuration for the Portal . . . . . . . . . . . . 1526.7 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . 153

12/04/2006 PUBLIC 11/210

6.7.1 Running SAPinst to Delete an SAP System . . . . . . . . . . . . . 1546.7.2 Deleting the Oracle Database Software . . . . . . . . . . . . . . 1566.8 SAP System Security on Windows . . . . . . . . . . . . . . . . 1586.9 Automatic Creation of Accounts and Groups . . . . . . . . . . . . 1596.10 Manually Granting User Rights for the Installation . . . . . . . . . . 1616.11 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 1626.11.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 1626.11.2 Troubleshooting for Portal Installation . . . . . . . . . . . . . . 1636.11.3 Troubleshooting for the Business Package for SAP CRM . . . . . . . . 1646.11.3.1 Activating BI Templates Manually . . . . . . . . . . . . . . . . 1646.11.3.2 Troubleshooting when Importing PAR Files . . . . . . . . . . . . . 1656.11.3.3 Troubleshooting in SSO with SAP Logon Tickets . . . . . . . . . . . 1656.11.3.4 Dragging the Central Search onto the Portal Desktop . . . . . . . . . 168

Chapter 7 High Availability with Microsoft Cluster Service . . . . . . . . . 1697.1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 1707.1.1 SAP System Components in an MSCS Configuration . . . . . . . . . 1707.1.2 Enqueue Replication Server in an MSCS Configuration . . . . . . . . 1747.1.3 Distribution of Components to Disks for MSCS . . . . . . . . . . . 1757.1.4 Directories in an MSCS Configuration . . . . . . . . . . . . . . . 1787.1.5 IP Addresses in an MSCS Configuration . . . . . . . . . . . . . . 1797.1.6 Obtaining IP Addresses for MSCS . . . . . . . . . . . . . . . . . 1827.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 1847.2.1 Checking Hardware and Software Requirements for MSCS . . . . . . . 1857.2.2 Assigning Drive Letters for MSCS . . . . . . . . . . . . . . . . 1877.2.3 Mapping Host Names to IP Addresses for MSCS . . . . . . . . . . . 1877.2.4 Checking the Mapping of Host Names for MSCS . . . . . . . . . . . 1887.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . 1897.3.1 Moving MSCS Groups . . . . . . . . . . . . . . . . . . . . 1907.3.2 Rebooting During the Installation or Conversion for MSCS . . . . . . . 1907.3.3 Installing the Oracle Fail Safe Software . . . . . . . . . . . . . . . 1917.3.4 Installing the Central Services Instance (SCS) . . . . . . . . . . . . 1947.3.5 Configuring the First MSCS Node . . . . . . . . . . . . . . . . 1957.3.6 Installing the Database Instance . . . . . . . . . . . . . . . . . 1967.3.7 Configuring the Additional MSCS Node . . . . . . . . . . . . . . 1967.3.8 Additional Steps for the Oracle Fail Safe Configuration . . . . . . . . . 1987.3.9 Installing an Enqueue Replication Server . . . . . . . . . . . . . . 1997.3.10 Installing the Central Instance . . . . . . . . . . . . . . . . . 2007.3.11 Creating the Oracle Fail Safe Group . . . . . . . . . . . . . . . . 2017.3.12 Setting Up a Shared Database Directory in Oracle Home . . . . . . . . 2027.3.13 Adding the Oracle Database Resource to the Fail Safe Group . . . . . . . 2037.3.14 Installing the Dialog Instance . . . . . . . . . . . . . . . . . . 204

12/210 PUBLIC 12/04/2006

7.4 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . 2057.4.1 Starting and Stopping the SAP System in an MSCS Configuration . . . . . 2057.4.2 Post-Installation Checks for Enqueue Replication Server . . . . . . . . 2067.4.2.1 Checking the Status of the Enqueue Replication Server with ENSMON . . . 2067.4.2.2 Monitoring the Lock Table During Failover with ENQT . . . . . . . . 207

12/04/2006 PUBLIC 13/210

14/210 PUBLIC 12/04/2006

1 Introduction

1 Introduction

This document explains how to install CRM 5.0 SR2 Java.SAP CRM 5.0 SR2 is based on SAP NetWeaver 2004s technology. For more information about

the technology provided by SAP CRM and SAP NetWeaver, see SAP Service Marketplace athttps://service.sap.com/crm and https://service.sap.com/netweaver.

Make sure you have read the documentation Master Guide mySAP Customer Relationship Management2005 before you start with this installation guide. The Master Guide is available on SAP ServiceMarketplace at https://service.sap.com/crm-inst mySAP CRM 5.0 .

You can install SAP CRMwith the following software unit(s) in a single installation run of SAPinst:

n

Only valid for: CRM Java Components (JCRM)

CRM Java ComponentsEnd of: CRM Java Components (JCRM)

n

Only valid for: MapBox (MBX)

CRM MapboxEnd of: MapBox (MBX)

Note

n You also install NetWeaver Application Server Java (AS Java) with the Java software units.n If you want to add additional software units or usage types to an existing SAP system, follow

SAP Note 883948.

Only valid for: Business Packages for CRM (BP-CRM)

You install CRM Business Packages (BP CRM) only using the Java Support Package Manager (JSPM)and not with SAPinst. Before you install CRM Business Packages, you must have installed NetWeaverApplication Server Java (AS Java), NetWeaver Enterprise Portal Core Components (EP Core) andNetWeaver Enterprise Portal (EP).End of: Business Packages for CRM (BP-CRM)

In addition to the CRM software units, you can install the following NetWeaver usage type(s)with SAPinst:

n

Only valid for: Development Infrastructure (DI)

NetWeaver Development Infrastructure (DI)End of: Development Infrastructure (DI)

12/04/2006 PUBLIC 15/210

1 Introduction1.1 New Features

n

Only valid for: EP Core (EPC)

NetWeaver EP Core (EPC)End of: EP Core (EPC)

n

Only valid for: Enterprise Portal (EP)

NetWeaver Enterprise Portal (EP)If you install usage type EP, note the following:l You must install NetWeaver Application Server Java (AS Java) and EP Core (EPC)l The Application Sharing Server is installed automatically with usage type EP. For production

use, we recommend that you install the server as an optional standalone unit on a dedicatedhost as described in this document.

End of: Enterprise Portal (EP)

For more information about the usage types of SAP NetWeaver and their interdependencies, see thedocument Master Guide SAP NetWeaver 2004s on SAP Service Marketplace [page 20]. For restrictions,see SAP Note 855534.

Constraints

You need to consider the following constraints before you start your installation:

n You can install your SAP system with Oracle 10.2 only.n You must only use the SAP installation tools according to the instructions and for the purposes

described in the SAP installation document. Improper use of the SAP installation tools can damagefiles and systems already installed.

n SAP system installations should only be performed by SAP Technical Consultants who arecertified for your operating system, your database, and the SAP system that you are installing.

n For downward-compatible releases of DB/OS platforms for SAP products, SAP plans to regularlyrelease the newest database (DB) and operating-system (OS) versions of SAP products. Thesereleases are downward-compatible with earlier SAP system releases.Note that for already shipped SAP components, we only support the installation for databaseversions proposed by the installation tool. Therefore, you must install a SAP component orperform a system copy using a downward-compatible database as follows:l Install the component with the old proposed database version.l Upgrade the old database version to the downward-compatible new version.

1.1 New Features

Here you can find the new features in this release.

16/210 PUBLIC 12/04/2006


SAP System Installation

Area Description

SAPinst As of SAP NetWeaver 2004s, SAPinst has the following new features:n You can check the prerequisites for your SAP system installation with the Prerequisite

Checker [page 44].n You can install a central system in one of two modes:l Typical Mode

If you choose Typical, your SAP system is installed with default settings. As aresult, you only have to respond to a small selection of prompts. If you want tochange any of the default settings, you can do so on the parameter summaryscreen at the end of the installation.

l Custom ModeIf you choose Custom, you must manually enter all installation parameters. Youcan change your values on the parameter summary screen at the end of theinstallation.

n You can uninstall an SAP system or an SAP component with the SAPinst serviceUninstall System / Standalone Engines / Optional Standalone Unit.

n You can install the Java Add-In for an existing ABAP system. This means that yourun SAPinst to execute the following:l Install the central services instance (SCS)l Add the Java database schema to the existing ABAP database instance.l Add the Java central instance with usage types to the existing ABAP central

instance.

NoteYou cannot install the Java Add-In for the dialog instance(s) of the existing ABAPsystem. Instead, you have to install an ABAP+Java dialog instance(s).

n You can change the default names of the Java users J2EE_ADMIN, J2EE_GUEST andSAPJSF during the input phase of the installation.

n You assign one Master Password to all users created by SAPinst. This password is usedfor all user accounts and for the secure store key phrase.

n SAPinst fills in most of the input parameter fields with default values.If required, you can change the default values on the Parameter Summary screen beforeyou start the actual installation.

Installation DVDs You start the installation from a single Installation Master DVD.

Usage type EP Core(EPC)

As of SAP NetWeaver 2004s SR2, usage type Enterprise Portal (EP) is now divided intotwo different usage types, EP Core (EPC) and Enterprise Portal (EP).n EP Core (EPC)

This usage type contains the core portal capabilities that were available in the formerusage type EP. This new usage type provides more flexibility when implementing aportal where the full enterprise portal capabilities, such as knowledge managementand collaboration, are not needed.

n Enterprise Portal (EP)This usage type includes Knowledge management, Collaboration, CAF-Core, VisualComposer, Web Dynpro extension, and .NET PDK, while EPC contains the portal,GP, and UWL.

Usage type EPC is a prerequisite for usage type EP. If you want to obtain the fullcapabilities of the former usage type EP, you need both EP Core and EP.

12/04/2006 PUBLIC 17/210


Area DescriptionThe configuration of EPC comprises only portal configuration steps.

NoteCurrently EPC is not supported as a standalone usage type. You must install bothEPC and EP usage types.

Integration ofInternet PricingConnector

The IPC (SAP AP IPC JAVA 7.00) has major architectural changes compared to CRMIPC 4.0. The IPC no longer exists as a separate server. Instead, the IPC functionality isnow delivered as part of SAP AP (Application Platform) and is processed on normalapplication servers.

SAP SolutionManager Key

You require a key to install your SAP system. You generate this key with your SAP SolutionManager [page 57].

High Availability You have the following options to install a high-availability system with MSCS:n You install one SAP system in one MSCS cluster.n You install one SAP system in two MSCS clusters.In both cases the following restrictions apply:n You must install the (A)SCS instance on two MSCS nodes in one MSCS cluster.n If your database supports the installation on several MSCS nodes, you can install the

database instance on more than two MSCS nodes in one MSCS cluster.

Oracle Database

Area Description

New features in Oracle 10g For the complete list of new features, see further documentation fromOracle, which you can find at:www.oracle.com/technology/products/database/oracle10g

See also:n www.oracle.com/technology/documentation/

database10g.html View Libraryn The documentation provided by Oracle on the RDBMS DVD

under :\NT\\DOC\index.htm

Operating Systems

Area Description

Support of OperatingSystems

See the Product Availability Matrix (PAM) on SAP Service Marketplace athttps://service.sap.com/platforms Product Availability Matrix.

18/210 PUBLIC 12/04/2006

1 Introduction1.2 SAP Notes for the Installation

Documentation

Area Description

SAP Notes You can now access SAP Notes directly in SAP Service Marketplace from yourPDF. Place the cursor on the SAP Note and double-click. Aseparate browser windows opens and the SAP Note is displayed.

Web Dispatcher Installation The installation of a Web Dispatcher is covered in a dedicated installationguide, available at https://service.sap.com/installnw2004s Installation -Standalone Engines & Clients Installation Guide - Web Dispatcher on

Application Sharing ServerInstallation

The installation of Application Sharing Server is part ofthe SAP NetWeaver Java installation guide, available at

https://service.sap.com/installnw2004s Installation - SAPNetWeaver 2004s Installation Documentation - SAP NetWeaver 2004s SR2 Java

Links in PDF files You can use the new links in the PDF files of the guides as follows:n Click on the section headings such as New Features to jump back to the

table of contents at the beginning of the guide.n Click on an internet link such as https://service.sap.com to jump to

the corresponding internet page.

1.2 SAP Notes for the Installation

Youmust read the following SAP Notes before you start the installation. These SAP Notes contain themost recent information on the installation, as well as corrections to the installation documentation.

Make sure that you have the up-to-date version of each SAP Note which you can find in the SAPService Marketplace at https://service.sap.com/notes.

Note

You can directly access the SAP Notes that are related to the SAP NetWeaver installation athttps://service.sap.com/sapnotesnw2004s.

SAP Notes for the Installation

SAP Note Number Title Description

852027 MapBox related notes This is a composite Note whichcollects together all Notes relating tothe installation of MapBox.

12/04/2006 PUBLIC 19/210

1 Introduction1.3 Information Available on SAP Service Marketplace

SAP Note Number Title Description

967123 SAP NetWeaver 2004s/Business Suite2005 SR2: Windows

Windows-specific information aboutthe SAP system installation andcorrections to this documentation.

NoteThis note also containsWindows-specific informationreferring to SAP CRM 5.0 SR2.

852008 Release Restrictions for SAPNetWeaver 2004s

Customer information on restrictionsconcerning the production use ofcertain functions.

737368 Hardware requirements of JavaDevelopment

Information on the hardwarerequirements for usage typeDevelopment Infrastructure (DI),which depends on the size of yourdevelopment team.

967121 SAP NetWeaver 2004s/ BusinessSuite 2005 SR2 based system: OracleWindows

Oracle-specific information aboutthe SAP system installation andcorrections to this documentation.

NoteThis note also containsOracle-specific information referringto SAP CRM 5.0 SR1 / SAP CRM 5.1.

828268 Oracle 10g : New functions Information about new Oraclefeatures released for the SAP system.

855498 Installation Prerequisite Checker SAP Software on UNIX, Windows andiSeries: Checking OS Dependencies

1.3 Information Available on SAP Service Marketplace

More information is available as follows on SAP Service Marketplace.

Documentation

Description Internet Address Title

Master Guide mySAPCRM Based on SAP CRM5.0

https://service.sap.com/crm-inst

mySAP CRM mySAP CRM 2005 CRM CrossComponent

Master Guide mySAP CustomerRelationship Managment 2005

Installation of SAPSolution Manager

https://service.sap.com

/solutionmanager Installation GuidesRelease

Installation Guide SAP SolutionManager on :

20/210 PUBLIC 12/04/2006

1 Introduction1.3 Information Available on SAP Service Marketplace

Description Internet Address Title

Configuration of SAPSolution Manager


/solutionmanager Installation GuidesRelease

Configuration Guide SAP SolutionManager

Upgrade to SAP CRM 5.0 https://service.sap.com/crm-instmySAP CRM mySAP CRM 2005 CRM CrossComponent

Upgrade Master Guide mySAPCRM 2005

Installation of SAPNetWeaver DeveloperWorkplace

https://service.sap.com/installNW2004s Installation Guide SAP NetWeaverDeveloper Workplace

Installation of SAPNetWeaver DeveloperStudio

https://service.sap.com/installNW2004s Installation Guide SAP NetWeaverDeveloper Studio

Installation of the SystemLandscapeDirectory (SLD)


/installNW2004s ConfigurationPost-Installation Guide SystemLandscape Directory of SAPNetWeaver 2004s

Installation of WebDispatcher


/installNW2004s Installation - StandaloneEngines & Clients

Installation Guide Web Dispatcheron for SAP NetWeaver2004s SR2

Front End installation https://service.sap.com/installNW2004s Front End Installation Guide (this guideis also available on the PresentationDVD)

Homogeneous andheterogeneous systemcopy for SAP systems basedon NetWeaver 2004s

https://service.sap.com/installNW2004s Homogeneous and Heterogeneous SystemCopy for SAP Systems based on SAPNetWeaver 2004s

SAP NetWeaver ProblemAnalysis Guide

https://help.sap.com/nw2004s SAPNetWeaver Library SAP NetWeaver by KeyCapability Solution Life Cycle Management by KeyCapability SAP NetWeaver Problem Analysis Guide(PAG)

SAP NetWeaver Problem AnalysisGuide (PAG)

General Quick Links

Description Internet Address

SAP Help Portal https://help.sap.com

SAP NetWeaver Library in SAPHelp Portal

https://help.sap.com/nw2004s

SAP Notes https://service.sap.com/notes

SAP Notes for SAP NetWeaver2004s installation

https://service.sap.com/sapnotesnw2004s

Released platforms and operatingsystems

https://service.sap.com/platforms

12/04/2006 PUBLIC 21/210

1 Introduction1.4 Naming Conventions

Description Internet Address

Unicode SAP systems and theiravailability

https://service.sap.com/unicode

System sizing (Quick Sizer tool) https://service.sap.com/sizing

High availability https://service.sap.com/ha

Security https://service.sap.com/security

NoteFor information on Windows operating system security, see:www.microsoft.com/security

Information on SAP SupportPackage Stacks

https://service.sap.com/sp-stacks

SAP Solution Manager https://service.sap.com/solutionmanager

1.4 Naming Conventions

In this documentation, the following naming conventions apply:

Terminology

n SAP system refers to SAP CRM 5.0 SR2.n Java system refers to SAP CRM 5.0 SR2 Java.

Variables

Variables Description

SAP system ID in uppercase letters

SAP system ID in lowercase letters

Database ID in uppercase letters

Database ID in lowercase letters

Name of the corresponding host

Installation directory for the SAP system

Directory on which a DVD is mounted

Operating system name within a path

Database schema ID

The following example shows how the variables are used:

22/210 PUBLIC 12/04/2006

1 Introduction1.4 Naming Conventions

Example

Log on as user adm and change to the directory \usr\sap\.If your SAP system ID is C11, log on as user c11adm and change to the directory\usr\sap\C11.

12/04/2006 PUBLIC 23/210

This page is intentionally left blank.

2 Planning

2 Planning

This section tells you how to plan the installation of your SAP system.

Only valid for: HA (MSCS)

If you want to perform a high-availability installation with Microsoft Cluster Service (MSCS),see High Availability with Microsoft Cluster Service [page 169].End of: HA (MSCS)

You have to complete the following planning activities:

1. You plan your SAP system landscape according to the Master Guide.In addition, we recommend that you read theTechnical Infrastructure Guide SAP NetWeaver 2004s,which is available on SAP Service Marketplace at: https://service.sap.com/installNW2004s.

2. You choose your basic system variants [page 25].3. You plan how to distribute the instances to hosts [page 26].4. You plan your system configuration [page 27].5. You identify basic SAP system parameters [page 33].6. If you want to use Adobe Document Services (ADS), you check what you have to do in case your platform is

not supported for ADS [page 39].7. You decide if you want to use Multiple Oracle Homes [page 39].8. You decide if you want to use Internet Pricing and Configurator [page 40].

9.Only valid for: Enterprise Portal (EP)

You decide if you want to install Application Sharing Server as a standalone unit on a dedicated host [page 41].End of: Enterprise Portal (EP)

The following planning activity is optional:

n Installation of Multiple Components in One Database (MCOD) [page 141]n Preparing User Management for an External ABAP System [page 147]

2.1 Basic System Variants

This chapter describes the basic system variants and shows how you can distribute SAP instanceswithin these variants.

Mandatory instances of a Java system are the central instance, the central services instance, andthe database instance.

12/04/2006 PUBLIC 25/210

2 Planning2.2 How to Distribute Instances to Hosts

Note

Optionally, you can install one or more dialog instances on a separate dialog instance host.

The following graphics show examples for the distribution of the SAP instances in a central system,where the mandatory instances are installed on one host, and a distributed system, where themandatory instances are installed on separate hosts.

Figure 1: Java System

More InformationOnly valid for: HA (MSCS)

For more information on how to distribute SAP instances in a high-availability SAP system, see SAPSystem Components in an MSCS Configuration [page 170].End of: HA (MSCS)

2.2 How to Distribute Instances to Hosts

The following provides information on how you can distribute the SAP instances for the different SAPsystem variants. You use SAPinst to install the SAP instances as a:

n Central system on a single hostYou run SAPinst and install all instances on one host.

n Distributed system on several hosts

26/210 PUBLIC 12/04/2006

2 Planning2.3 System Configuration

You perform the following steps:1. You specify or create a shared transport directory.2. You run SAPinst and install the:l Central services instance (SCS) on the global hostl Database instance on the database hostl Central instance on the central instance hostl Dialog instance(s), if required, on the dialog instance host(s)

The following figure shows how to distribute your instances to several hosts:

Figure 2: Distribution of Instances in a Java System

2.3 System Configuration

You need to consider the following aspects:

n You and your hardware partner plan the distribution of your SAP system instances within the basic system variants[page 25].

n You and your hardware partner work out a high-performance configuration based on sizinginformation that reflects the system workload, such as:l The set of applications to be deployedl How intensively the applications are to be usedl The number of users

n You decide whether to perform a domain or local installation:

12/04/2006 PUBLIC 27/210


l Local installationYou need to be Local Administrator of the machine involved. In a local installation, allWindows account and user information is stored locally on one host and is not visible to anyother hosts in the system.If the SAP system is to run on a singlemachine, you can perform a local installation.

Caution

If you install a distributed system as a local installation, this can lead to authorization problemsfor the operating system users adm and SAPService, as well as to problemswith the transport directory, which is usually shared by several SAP systems. Therefore, SAPdoes not support a local installation for a distributed system and recommends you to install adistributed system as a domain installation.If you still want to perform a local installation for a distributed system, make sure that:uYou use the same password for the adm or the SAPService user on all

hosts.The password for the adm and SAPService user can differ.

uYou use the same master password on all hosts.uAll hosts belong to the same Windows work group.

l Domain installationYou need to be Domain Administrator of the domain involved, and all machines in the systemmust belong to the same domain. In a domain installation, the user information is storedcentrally on the domain controller and is accessible to all hosts in the system.If the system is to be distributed across more than one machine, SAP strongly recommendsyou to perform a domain installation to avoid authorization and support problems.

Caution

If for any reason, you are not granted domain administrators rights, you can perform theinstallation as a domain user who is a member of the local administrators group. However, thedomain administrator has to prepare the system appropriately for you.For more information, see Performing a Domain Installation without being a Domain Administrator [page 54].

For more information on user rights for a local or domain installation, see: Granting User Rights forthe Installation [page 53].

2.3.1 Distribution of Components to Disks

When you install the SAP system, the installation tools prompt you to enter drive letters for the maincomponents of the system. This gives you the opportunity to distribute components to disks in thesystem as you wish. The way in which you do this significantly affects system throughput and data

28/210 PUBLIC 12/04/2006


security, and must therefore be carefully planned. The best distribution depends on your specificenvironment and must take into consideration factors such as the size of the components involved,security requirements and the expected workload.

When you work out the assignment of components to disks, you first need to get an overview of themain components and their corresponding directories. Then, on the basis of sample configurationsand the recommendations provided in this documentation, you can decide which assignment is bestfor your particular system.

SAP systems are normally installed on RAID arrays that ensure data redundancy. Thisdocumentation therefore focuses on RAID subsystems and drives.

Minimal Configuration

The following illustrates a disk configuration for a small test or demo system. As security andperformance play a less crucial role in this type of system, many different configurations are feasible.The following shows one of the possible options.

Caution

Use the illustrated configuration exclusively for test or demo systems with a final database size of lessthan 10 GB. It is unsuitable for production systems because it only minimally satisfies security andperformance requirements.

Figure 3:

12/04/2006 PUBLIC 29/210


Distribution of Directories to Disks

Disk Directories

Disk 1 \ORACLE\\102\ORACLE\\sapreorg

\ORACLE\\origlogA

\ORACLE\\origlogB

\ORACLE\\sapdata1

\ORACLE\\sapdata2

Disk 2 \ORACLE\\mirrlogA\ORACLE\\mirrlogB

\ORACLE\\saptrace

\ORACLE\\sapbackup

\ORACLE\\sapcheck

\ORACLE\\sapdata3

\ORACLE\\sapdata4

Disk 3 \ORACLE\\saparch

Comments

n The configuration ensures that no data can be lost, but the process for recovering a damageddatabase is complicated and time-consuming.

n The redo logs and database files are located on the same disks. This means that a single disk failurecan result in the loss of both the redo logs and database data.

n The I/O-intensive redo logs are on the same disk volumes as the data files. This can impedeperformance.

n An equally good alternative would be to simply place all components on a single RAID 5 array.

2.3.2 SAP Directories

This section describes the SAP directories that SAPinst creates during the installation.The base directories required for the SAP system are:

n \usr\sapThis directory is created on the:l Global host and shared with the name sapmnt

On global hosts, the \usr\sap directory contains general SAP software, global and local(instance-specific) data.For this, the following directories are created in usr\sap\\SYS:uglobal (contains globally shared data)uprofile (contains the profiles of all instances)uexe (contains executable kernel programs)

30/210 PUBLIC 12/04/2006


All instances of an SAP system access this directory on the global host using the UniversalNaming Convention (UNC) path.

l Local host and shared with the name saploc.On local hosts, the \usr\sap directory contains copies of the SAP software and local(instance-specific) data.The executables on the local host are replicated from those on the global host each time thelocal instance is started.

Note

Since SAP traces for the instance are created in \usr\sap, make sure there is sufficient spaceavailable in this directory. Changes in SAP profiles can also affect the disk space.

n \usr\sap\transThis directory contains SAP software for the transport of objects between SAP systems and iscreated on the transport host, which is normally the SAPGLOBALHOST.If you do not want to have it created on the global host you can specify another host during theinstallation. For more information, see Preparing the SAP System Transport Host [page 56].

Directory Structure

The global host has the SAP\\SYS directory structure. The global data (binaries) is stored inthe global directories on the global host and physically exists only once for each SAP system. Otherapplication servers access the global data using the UNC path \\\sapmnt. The SAPprograms access their instance-specific data with the UNC path \\\saploc. If theUNC path points to a local directory, the local path (and not the UNC path) is used to access thedirectory.

In a distributed system, the parameters SAPGLOBALHOST and SAPLOCALHOST have the same values onthe global host.

Every time an instance starts, the SAP copy program sapcpe compares the binaries in the-directory on the global host and the binaries in the exe-directory on the applicationserver. If the binaries in the exe directory are elder than those in the -directory, sapcpereplaces them with the newer version of the global host.

The following figures show how the physical directory \usr\sap is shared on the global host in acentral and in a distributed system. In both cases, the UNC paths are used as follows:

n \\\sapmnt to access global directoriesn \\\saploc to access local instance-specific data

12/04/2006 PUBLIC 31/210


Figure 4: Directory Structure on the Global Host in a Central Java System

Figure 5: Directory Structure in a Distributed Java System

32/210 PUBLIC 12/04/2006

2 Planning2.4 Basic SAP System Parameters


Figure 6: Directory Structure in a High-Availability Java System

End of: HA (MSCS)

2.4 Basic SAP System Parameters

The tables below list the basic system parameters that you need to determine before installing yourSAP system. For all other SAP system parameters, use the F1 help in the SAPinst dialogs.

Note

In the column Enter Your Values, you write down the values that you plan to use, for example,the Message Port Number.

12/04/2006 PUBLIC 33/210


SAP System ID and Database ID

Parameters Description Enter Your Values

SAP System ID

The SAP System ID identifies the whole SAPsystem.

CautionChoose your SAP system ID carefully. You cannot changethe SAP system ID after the installation.

Make sure that your SAP system ID:n Is unique throughout your organizationn Consists of exactly three alphanumeric charactersn Contains only uppercase lettersn Has a letter for the first charactern Does not include any of the following, which are reserved

IDs:ADD ALL AND ANY ASC COM DBA END EPS FOR GID IBM

INT KEY LOG MON NIX NOT OFF OMS RAW ROW SAP SET

SGA SHG SID SQL SYS TMP UID USR VAR

...

Database ID The identifies the database instance.The database ID can be different from the SAPsystem ID.

...

SAP System Instances, Hosts and Ports


Instance Number Instance Number:Technical identifier for internal processes, consisting of atwo-digit number from 00 to 97.The instance number must be unique on a host. That is, ifmore than one SAP instance is running on the same host, theseinstances must be assigned different numbers.If you want to install an additional application serverinstance, you must use exactly the same instance number as theexisting primary application server instance.To find out this number, look under the SAP directory:\usr\sap\\J on the host of the primaryapplication server instance.The value is the number assigned to the primary applicationserver instance.

CautionDo not use 43, 60, 89 for the instance number because:

n 43 is used by MSCSn 60 is used by iSCSIn 89 is used by Windows Terminal Server

...

34/210 PUBLIC 12/04/2006



Name of InstanceHost

Instance Host:Host name of the specific instance.To find out the host name, open a command prompt and enterhostname.For more information about the allowed host name length andcharacters, see SAP Note 849423.

...

Messaging ServicePort Caution

Make sure that all messaging service port numbers on the samehost are unique.

Port number of the SAP Messaging Service:If you do not specify a value, the default port number is used.The messaging service port number must be unique for the SAPsystem on all hosts.The Java messaging service is configured in the SCS instanceprofile.The Java messaging service port uses the parameterrdisp/msserv_internal with default value 39, where is the instance number of the SCS messaging service instance.For more information, see SAP Note 821875.

...

Master Password


Master Password This password is used for all user accounts SAPinst creates andfor the secure store key phrase. The length has to be 8 to 14characters.Depending on your installation scenario there might be morerestrictions.

CautionIf you do not create the operating system users manually,SAPinst creates them with the common master password (seeOperating System Users). In this case, make sure that themaster password meets the requirements of your operatingsystem and of your database.

...

12/04/2006 PUBLIC 35/210


Operating System User


Operating SystemUsers

SAPinst creates the adm and SAPService usersin the domain specified. Make sure that you have domainadministrator rights before you start the installation. If not,you have to create these users manually before starting theinstallation. For more information, see Granting User Rights for theInstallation [page 53].

...

User Management Engine (UME)

Parameter Description Enter Your Values

UME Configuration You are prompted for how to configure the UME during theinput phase of the installation.You can choose between the following options:n Use Java database (default).

If you choose this option, administrators can manage usersand groups with the UME Web admin tool and SAP NetWeaverAdministrator only.For LDAP, use this configuration for the installation andchange the configuration to LDAP after the installation.

n Use an external ABAP system.If you choose this option, administrators can manage userswith the transaction SU01 on the external ABAP system,and, depending on the permissions of the communicationuser, also with the UME Web admin tool and SAP NetWeaverAdministrator.You must have created the required users manually on theexternal ABAP system.For more information, see Preparing User Management for anExternal ABAP System [page 147].

...

Using the Java Database:

Java AdministratorUser

SAPinst sets the user name Administrator and the masterpassword by default.If required, you can choose another user name and passwordaccording to your requirements.

...

Java Guest User SAPinst sets the user name Guest and the master password bydefault.The Guest user is for employees who do not belong to acompany or who have registered as company users withpending approval. Guest users belong to the default groupAuthenticated Users and have read access only.

..

Using an External ABAP System Parameters for the ABAP Connection:

36/210 PUBLIC 12/04/2006



Application ServerNumber

This is the instance number on the application server ofthe central ABAP system to which you want to connect theApplication Server Java.To find out the number on the host of the primaryapplication server instance, look under the SAP directoryusr/sap//DVEBMGS. The value is the numberassigned to the SAP system.

...

Application ServerHost

This is the host name of the relevant application server instance.To find out the host name, enter hostname at the commandprompt of the host running the primary application serverinstance.

...

Communication User This is the name and password of the existing ABAPcommunication user. You must have created this usermanually on the external ABAP system.

...

Using an External ABAP System Parameters for the Application Server Java Connection:

Administrator User This is the name and password of the administrator user thatyou created on the external ABAP system.

...

Administrator Role The role SAP_J2EE_ADMIN must exist on the external ABAPsystem.

...

Guest User This is the name and password of the guest user that youcreated on the external ABAP system.The guest user is for employees who do not belong to acompany or who have registered as company users withpending approval. Guest users belong to the default groupAuthenticated Users and have read access only.

..

Guest Role The role SAP_J2EE_GUEST must exist on the external ABAPsystem.

...

Internet Communication Manager (ICM) User Management


Password of webadm The administration user webadm is created to use the webadministration interface for Internet Communication Manager(ICM) and Web Dispatcher.SAPinst sets the master password by default. If required, youcan choose another password.

...

12/04/2006 PUBLIC 37/210


Solution Manager Key


SAP Solution Managerkey

To install your SAP system, you need to generate a SAP SolutionManager key [page 57], which the installation requires to continue.For more information, see SAP Note 805390.

...

Parameters for SAPDATA Drives


Installation drive Base directory for the SAPsystem. Do not add assubdirectory because the systemadds this directory automatically.

ExampleIf you enter D:, the system addsthe directory D:\usr\sap\SAPSID.

NoteIf you install a subsequent SAPsystem, the saploc share alreadyexists and you cannot select theinstallation drive. SAPinst usesthe installation drive where thesaploc share points to.

...

Oracle parameters n Oracle homen SAPDATA drivesn Drives for redolog and archives

(oraarch)

...

Parameters Relevant for the Database


Code page The code page that is used by your database (Unicode orNon-Unicode).

...

38/210 PUBLIC 12/04/2006

2 Planning2.5 Running Adobe Document Services on Non-Supported Platforms


Database schemata,Passwords

The Java database schema is namedSAPDB.Default name is SAPSR3DB.

...

Oracle Listener Name,Oracle Listener Port

n If you install the database instance on a host where noother Oracle database is installed, you normally do nothave to change the default values for Listener Nameand Listener Port.

n If you install the database instance on a host wherealready another Oracle database is installed you havethe following options:l If you install it in the same Oracle home, you use the

default values for Listener Name and Listener Port.l If you install it in a different Oracle home, you

specify an unused Listener Name and Listener Portfor the new Oracle Listener.

n All dialog instances of an SAP systemmust use the sameListener Port than the database instance.

...

2.5 Running Adobe Document Services on Non-SupportedPlatforms

Adobe document services (ADS) are currently not supported to run natively on all platformssupported by SAP systems based on SAP NetWeaver, in particular on 64-bit platforms.

ProcedureTo use ADS in SAP landscapes on non-supported platforms, install an additional standalone ASJava on a platform supported by ADS.

For more information, see SAP Note 925741.

2.6 Multiple Oracle Homes

Oracle allows to install multiple Oracle Homes on one host.


Note

MSCS only:Multiple Oracle Homes for different database instances are not supported in an MSCS

configuration.

End of: HA (MSCS)

Note the following about multiple Oracle Homes:

12/04/2006 PUBLIC 39/210

2 Planning2.7 Internet Pricing and Configurator

n Multiple Oracle Homes are necessary, if you install different Oracle versions for two or moredatabases on the same host.

n If you use multiple Oracle Homes you must use different port numbers for each listener.n If you install the same Oracle database version on one host for different database instances, you

can use:l Multiple Oracle Homes

With multiple Oracle Homes you can administer your databases independently. For example, ifyou want to install a patch set, you do not have to install them on both databases.

l One Oracle Home for two databasesYou have to install the database software only once.

Note

In case you later want to use two multiple homes instead of one, you either have to perform anew database instance installation or upgrade your database.

Before you install your Oracle database software, you need to decide whether you want to set upmultiple Oracle Homes as this influences the installation procedure. For more information, seeSetting Up Multiple Oracle Homes [page 65].

2.7 Internet Pricing and Configurator

Internet Pricing and Configurator (IPC) is delivered as part of SAP AP (Application Platform) andprocessed on normal application servers.

SAP IPC is required for CRM Mobile Application Components that are part of software unit CRMJava Components (JCRM). For more information, see the documentation Master Guide mySAP CRM2005 on SAP Service Marketplace at https://service.sap.com/crm-inst.

PrerequisitesThe IPC (SAP AP IPC JAVA 7.00) requires the Virtual Machine Container (VMC) as runtimeenvironment. The VMC is part of SAP Basis 7.00.

IntegrationNo separate IPC installation steps are necessary. No separate host or separate Java runtimeenvironment is necessary. IPC functionality is processed on each application server. The IPC doesnot support any special methods to support high availability or load balancing. By running on eachapplication server, SAP standard load balancing or high-availability mechanisms apply.

You need to enable the VMC after the installation of your SAP system. For more information, seeActivating Internet Pricing and Configurator [page 94].

40/210 PUBLIC 12/04/2006

2 Planning2.8 Application Sharing Server as an Optional Standalone Unit

Only valid for: Enterprise Portal (EP)

2.8 Application Sharing Server as an Optional Standalone Unit

Application Sharing Server for real-time collaboration provides data streaming services that enableapplication sharing capabilities provided by SAP NetWeaver collaboration. The server handles theflow of data between portal users collaborating through the real-time application sharing feature.

Application Sharing Server lets users share their Windows desktop or individual applicationswith other portal users in real time. Remote users can interact directly with the shared desktop orapplication as if they were sitting at the host machine.

The server is installed automatically with usage type Enterprise Portal (EP) on the portal host. Ina cluster environment, the load generated by the Application Sharing Server is replicated to allinstances of the cluster. This generates load on all dialog instance hosts.

Note

You can only use Application Sharing Server with SAP NetWeaver systems with usage type EP.

Planning

For test or demo purposes, you can run the Application Sharing Server on the portal machine.

Recommendation

For production use, we recommend that you install the server as an optional standalone unit on adedicated host. To do this, you perform a separate installation as described in this documentation.By removing Application Sharing Server traffic from the portal host, you reduce the networking andJ2EE Engine demands on that machine, which improves the overall performance of the portal.

When you install usage type EP, the Application Sharing Server is installed automatically. If you donot intend to use the Application Sharing Server, you can disable it. For more information, seePost-Installation Tasks for Application Sharing Server [page 124].

You can install Application Sharing Server on a dedicated host before or after installing the usagetype EP. However, you can only complete the post-installation steps after you have installed usagetype EP.

Preparation

Prepare the Application Sharing Server installation host for an AS Java central system installation:

1. Check hardware and software requirements [page 43].2. Check the Windows file system [page 51].3. Install the Java Development Kit [page 58].4. Prepare the installation DVDs [page 60].

12/04/2006 PUBLIC 41/210

2 Planning2.8 Application Sharing Server as an Optional Standalone Unit

Installation

1. Install the Oracle database software [page 63].2. Run SAPinst to install Application Sharing Server as an optional standalone unit [page 78].

Post-Installation

Perform the post-installation steps for an AS Java central system installation on the ApplicationSharing Server installation host:

1. Start and stop the Application Sharing Server system [page 82].2. Check the SAP Java documentation [page 130].3. Apply the latest kernel and support packages [page 88].4. Perform post-installation steps for Adobe Document Services [page 91].5. Perform post-installation steps for Application Sharing Server [page 124].6. Ensure the security of Java standalone users stored in the database [page 124].

End of: Enterprise Portal (EP)

42/210 PUBLIC 12/04/2006

3 Preparation

3 Preparation

You have to complete the following preparations:

1. You check the hardware and software requirements [page 43].2. You check the Windows file system [page 51].3. You check the Windows domain structure [page 51].4. If required, you reduce the size of the file cache [page 52].5. If required, you grant user rights for the installation [page 53].6. If required, you perform a domain installation without being a domain administrator [page 54].7. If required, you prepare the SAP system transport host [page 56].8. You generate the SAP Solution Manager Key [page 57].9. You install the Java Development Kit [page 58].

10.Only valid for: Business Packages for CRM (BP-CRM)

You check the prerequisites for the installing the business package for SAP CRM [page 59].End of: Business Packages for CRM (BP-CRM)

11. You prepare the installation DVDs [page 60].12. If required, you download the installation DVDs from SAP Service Marketplace [page 61].

The following preparation activity is optional:Preparing user management for an external ABAP system [page 147].

3.1 Hardware and Software Requirements

You check the hardware and software requirements for your operating system (OS) and the SAPinstances using the Prerequisite Checker tool. The Prerequisite Checker provides information aboutthe requirements that you need to meet before you start the installation. For example, it checks therequirements for the different installation services.

Note

n The values that are checked by the Prerequisite Checker apply to the installation of developmentsystems or quality assurance systems.

n For the most recent updates to the Prerequisite Checker, always check SAP Note 855498.

You can run the Prerequisite Checker as follows:

12/04/2006 PUBLIC 43/210

3 Preparation3.1 Hardware and Software Requirements

n Standalone (optional):To check the hardware and software requirements of the host on which you want to later installan SAP system, you can run the Prerequisite Checker standalone [page 44].

n Integrated in SAPinst (mandatory):SAPinst automatically runs the Prerequisite Checker when you install your SAP system.

We also recommend that you consult the requirements checklists tables, which provide values for theinstallation of development systems or quality assurance systems. Depending on the amount ofdata involved, the requirements might change. In addition, consider the following information:

n To get precise sizing values for production systems, you have to do one of the following:l You use the SAP Quick Sizer tool that is available on SAP Service Marketplace at

https://service.sap.com/sizing. You enter information about your planned system andthe tool calculates the requirements.For more information, see Planning your System Landscape in the Master Guide SAP NetWeaver 2004s,which is available on SAP Service Marketplace [page 20].

l You contact your hardware vendor, who can analyze the load and calculate suitable hardwaresizing.

n For supported operating system and Java (JDK/JRE) releases, see the Product Availability Matrix onSAP Service Marketplace at https://service.sap.com/pam.

n Contact your OS vendor for the latest OS patches.n Make sure that the host name meets the requirements listed in SAP Notes 611361 and 849423.

Process Flow

1. If required, you run the Prerequisite Checker standalone [page 44] to check the hardware and softwarerequirements.

Caution

If you do not fully meet the requirements, you might experience problems when working withthe SAP system.

2. In addition, we recommend that you check the hardware and software requirements checklistsfor the following system variants:n Central System [page 45]n Distributed System [page 47]

3.1.1 Running the Prerequisite Checker in Standalone Mode(Optional)

Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check thehardware and software requirements for your operating system (OS) and the SAP instances.

44/210 PUBLIC 12/04/2006


Recommendation

We recommend that you use both the Prerequisite Checker and the requirements tables for reference.

Note

When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks thehardware and software requirements in the background.

Procedure1. You start SAPinst [page 66].2. On the Welcome screen, choose Additional Software Lifecycle Tasks Additional Preparation

Tasks Prerequisites Check .3. Enter the required parameters when prompted in the SAPinst dialogs.

Note

For more information about each parameter, position the cursor on the parameter field andchoose F1 in SAPinst.

When you have finished, the Start Execution screen appears summarizing all parameters you haveentered. To change a parameter, choose Back and enter a new value.

4. To start the Prerequisite Checker choose Start.

ResultAfter the check has successfully completed, the Prerequisite Check Results screen appears displayingthe results found.

If required, you can also check the results in file prerequisite_checker_results.html, which youcan find in the installation directory.

3.1.2 Requirements Checklist for a Central System

If you want to install a central system, where all instances reside on one host, this host must meetthe following requirements:

12/04/2006 PUBLIC 45/210


Requirement Type Requirement

Hardware n Suitable backup systemn Minimum disk space:l Database Software:

1 GB (x86, AMD64)2 GB (IA64)

l SAP system files (not including paging file):5 GB (x86, AMD64)8 GB (IA64)

l SAP database files (not including paging file):2 GB

l Up to 2 GB for each usage type or software unit you want to install.l 4.3 GB of temporary disk space for every required installation DVD

that you have to copy to a local hard diskTo check disk space:1. Choose Start Programs Administrative Tools Computer Management

Disk Management.2. Select the local drive.3. Choose Properties.

n Minimum RAM:1.5 GBTo check RAM, in the Windows Explorer choose Help About Windows.

n Paging File Size: 1 times RAM plus 8 GBTo check paging file size:1. Right-click My Computer and choose Properties.2. Choose Advanced Performance Settings .3. If required, in section Virtual Memory, choose Change.

Software n Oracle 10g database server softwaren Current Oracle patch set and hot fix, if available.

NoteFor more information on the current patch set, see SAP Note 871735.

n English international version of one of the following:l Windows Server 2003 Standard Editionl Windows Server 2003 Enterprise Editionl Windows Server 2003 Datacenter Edition

NoteWe strongly recommend you to use the 64-bit version of the WindowsServer 2003 editions.

To check your Windows version:1. Choose Start All Programs Accessories Command Prompt .2. Enter the command winver.

n Make sure that the required fonts or code pages are installed.n A suitable Windows Resource Kit is strongly recommended.

46/210 PUBLIC 12/04/2006


3.1.3 Requirements Checklist for a Distributed System

The following sections provide information about the hardware and software requirements in adistributed system, where the following SAP instances can reside on different hosts:

n Central services instance [page 47]n Database instance [page 48]n Central instance [page 49]n Dialog instance [page 50]

Note

n The listed values only apply for development systems or quality assurance systems.n If you install multiple SAP instances on one host, you need to add up the requirements.

3.1.3.1 Requirements Checklist for the Central ServicesInstance

The central services instance (SCS) host must meet the following requirements:


Hardware n Suitable backup systemn Minimum disk space:l Central Services Instance (SCS) (not including paging file):

5 GB (x86, AMD64)8 GB (IA64)

l 4.3 GB of temporary disk space for every required installation DVD thatyou have to copy to a local hard disk.

To check disk space:1. Choose Start All Programs Administrative Tools Computer Management

Disk Management.2. Right-click the local drive and choose Properties.

n Minimum RAM: 0.5 GBTo check RAM, in the Windows Explorer choose Help About Windows.

n Paging File Size:1 times RAM plus 8 GBTo check paging file size:1. Right-click My Computer and choose Properties.2. Choose Advanced Performance Settings .3. If required, in section Virtual Memory, choose Change.

Software n English international version of one of the following:l Windows Server 2003 Standard Editionl Windows Server 2003 Enterprise Editionl Windows Server 2003 Datacenter EditionTo check the Windows version:

12/04/2006 PUBLIC 47/210

win_J

Documents

Transcript of win_J