Page 1 of 6

1. Buy, Build or Reconfigure a Server

My Step Installation Guide Comment

Section

Decide how SAP strongly recommends a 64-bit server. See Note 996600 - "32 Bit platforms not recommended for productive NW2004s apps." The SDN Subscription
strong a box is intended as a Development system, though The limiting factor on a 32-bit system is memory since it can't address more than 4gb of physical memory.
you want or can On some hardware it can only use 3.5gb. Even if you're maxed out you're still swapping. I watch memory consumption with "Task Manager".
afford I have installed several Mini-SAPs, Test drives and Sneak Previews. My server for the last three years has been a home-built dual Athlon MP 2000+ with
2gb ram, a 200gb ATA boot drive and 4 x 36gb 10K rpm U320 SCSI drives. For the SDN Subscription I upgraded to 3gb and added 2 x 18gb SCSI drives.
You could start with a tower PC, max out the memory, add a PCI RAID Controller and put in more disks. The last NetWeaver 7.0 Service Pack 12 ABAP
Sneak Preview was configured down to use 1.2gb out of the box. I increased various startup parameters to their defaults to get it to use most of the 2gb I
had at the time. NetWeaver 7.0 Service Release 2 (SP9) ABAP+Java, the version that ships in the current SDN Subscription Kit uses 5.5gb out of the box,
probably because Java is such a hog. For me this means about half of what should be is in memory. Since I'm only one user, the response time is fine
when I stay in one area (ABAP vs. Java vs. Portal).
For less than SDN Subscription price over again you could build a very nice 64-bit server. Before I had my SDN Subscription system up and saw that it ran
fine in 3gb on 32-bit hardware I looked for the cheapest 64-bit server I could find. You can get a dual Xeon or Opteron motherboard for about $250. Look
for at least 8 memory slots and 6 SATA ports with hardware RAID 5. The slowest quad-core processors are down to close to $200. Higher speed ones
won't make a noticable difference and they're much more expensive. You could start with just one. DDR2-667 ECC Memory is about $600. for 8gb. You
could start with 4gb. 60gb SATA-300 disks are $55. each. You need four to six of them. An x64 Windows 2003 Standard just went for $255. on e-bay. I
have the rest of the parts lying around so I didn't look, but they're cheap.
If you plan to install a new Netweaver Service Release 3 central instance, be aware that according to OSS note 1108852 SAPinst for 32bit will not allow
such an install anymore (it simply doesnt show the <SAP Systems> options anymore). Netweaver 7.0 SR3 central instances can be installed under 64bit
OS only. If you still want to install on a 32bit OS, you need to install Netweaver 7.0 SR2 first and then upgrade to SR3.

3.1, 3.1.1 Running I ran the Prerequisite checker in standalone mode but it wasn't a big advantage. Next time I'll let SAPInst do it.
the Prerequisite I ran Quicksizer but didn't get anything useful because the load is so small. It uses two methods to estimate hardware requirements - Users and
Checker Throughput.
Active Users Result: CPU category: XS. SAPS: 100, Memory 1gb DB Disk cat: XS, DB Disk 3gb.
Throughput Result: CPU category: S, SAPS: 3100, Memory: 7gb, DB Disk cat. XS, DB Disk 2.5gb.

3.1.2 Requirements Read this section. Disk space is never the problem. Even if you have the minimum number of drives (4) you'll have plenty of space. The faster the drives
Checklist for a the better. RAID speeds things up also. It's easy and better to run SAPGUI on a different machine.
Central System

3.1.3 Requirements Not relevant

Checklist for a
Distributed System

Know where 2.5.1 Distribution of Read this section. Basis people say you need to protect your log files. SAP says to mirror them on two RAIDs. I think that's excessive. I put non-mirrored
everything will Components to logs on one RAID. I have a 200gb ATA boot drive. I made a RAID 5 "D:" Drive with three 36 gbs for the Kernel and the database, a RAID 0 "E:" with two 18
go Disks gbs for the database logs and a non-RAID "F:" with the fourth 36gb as a spare and to copy the DVDs onto. I did a disk-to-disk backup to the ATA Drive.
Eventually I'll copy it to my file server.

Gather the parts I use Newegg, Microcenter, PCs for Everyone, the MIT Flea Market (www.mitflea.com), craigslist and e-bay.

Build it Assemble the parts. Download the latest drivers. Flash the BIOS. Make BIOS settings. Make hardware RAID settings. Lower-level-format the disks if
necessary.

2. Install and Configure an Operating System with Non-NetWeaver Applications

My Step Installation Guide Comment

Section

Get Windows 3.1.2 Requirements You don't need to pay for Server 2003 Enterprise or Datacenter. 32-bit Standard supports two CPUs. 64-bit Standard supports four. I found a
Server 2003 Checklist for a Central Microsoft position paper in which they say they only count physical CPU chips, not cores. This means you can run "dual quads" on Standard. You
System certainly don't need the 25 User licenses you pay for with Enterprise.
32-bit Windows 2003 doesn't let you make a Virtual memory (paging) file bigger than 4gb. SAP says you need at least 11gb so you have to have one
on every drive. You can get around the limit by putting multiple files in multiple folders but you have to modify the registry by hand to accomplish it.
See Microsoft Article # 237740 |

Execute
Windows Setup It's probably better to start with a fresh install. You don't want junk that runs by itself and uses memory. I even disabled the motherboard sound in my
BIOS so it wouldn't install unnecessary drivers.
Run Windows Setup. Put Windows on a boot drive.
If you have to change it later, use "System -> "Computer Name" (tab). Don't even think of changing it after the NetWeaver install.
My Windows Server box has 4GB memory installed, with Windows 2003 32bit OS. I was having some memory-related issues; found OSS Note
110172 and Microsoft KB article 283037 which addresses the issue by adding the "/3gb" switch to boot.ini. That made the memory issues go away. If
that doesn't work for you, there's another Note 853696 which talks about rebasing your DLL's - looks messy - glad I didn't have to do that!

Enter Setup 2.6.4 Name of Instance Give it a short "Computer name" (less than 13 characters) without punctuation. SAP calls it a "Host name". A dash works but Basis people
parameters Host recommend against it. If you're going to swap out hardware soon give it a generic name like "sapserv1" rather than a hardwarish name like
"IntelP999" or you'll have to get all fresh keys.

Attach to your 3.3 Checking the Just for Domain installation (see below). I tried and eventually gave up. If you do one, you probably already have a file server that's the domain
Domain Windows Domain controller so you can put NetWeaver on a non-DC machine. Check your Domain controller System log to be sure the NW machine is trusted by the
Structure DC. I had to put mine back in "WORKGROUP", reboot and reattach it to the Domain. Even though I could get to files on the DC, it wasn't properly
connected. You probably have to turn Windows Firewall and any other one off to get any of this to work.

3.6 Performing a Domain Just for Domain installation. I couldn't get my local User into the Domain Admins group.
Installation Without Being
a Domain Administrator

5/9/2011
 Page 2 of 6

Get a Solution 2.6.13 SAP Solution You have a Host name. If you already know what your SID and Instance number will be you can ask for a key now. The Installation Guide instructions
Manager Key Manager key don't apply to SDN Subscriptions. Go to sdn.sap.com -> log yourself in if necessary -> "Subscriptions" (tab) -> "SAP NetWeaver, Development
early 3.9 Generating the SAP Subscription" -> Subscription Related Links" -> "SAP NetWeaver Installation Key Request". See Note 805390 - SAP Solution Manager is required for
Solution Manager Key SAP Software. The SDN Subscription folks host one for subscribers. It can take a day or two to get.

Make a powerful Log in as "administrator".

User Account Make a non-built-in local administrative account with a name that doesn't conflict with one that's already on the domain and put it into the local
"Administrators" group Or if that's too much work, just stay logged in as "administrator".

Update Microsoft recommends doing all your downloads to a non-server machine for safety. Then copy the files over to your server.
Windows Download and install Service Pack 2 if it's not already built in.
Run Windows Update as many times as you need to until it stops coming up with new patches.

Configure Disks 3.2 Checking the To get as far away from FAT as possible I converted my disks from MBR to GBT in "Disk Management" before I built the RAID arrays. GBT is new in
Windows File System SP1 or 2. My SCSI Controller doesn't have RAID 5 so I did my RAID in software using Windows "Disk Management".

Configure 3.4 Reducing the Size of Do it.

Windows the File Cache

Configure 3.1.2 Requirements Use "System" -> "Advanced" -> "Performance" -> "Settings" -> "Advanced" -> "Change".
Paging files Checklist for a Central 32-bit Windows 2003 doesn't let you make a Virtual memory (paging) file bigger than 4gb. SAP says you need at least 11gb so you have to have one
System on every drive. You can get around the limit by putting multiple files in multiple folders but you have to modify the registry by hand to accomplish it.
See Microsoft Article # 237740

Patch the After Windows 2003 SP1 there's a security setting in the Registry you need to change to be able to see anything but the menus in HTMLHelp. See
Registry Note 857216 which refers to Microsoft KB article 896054. The answer in the end is to apply the attached registry patch in file saphelpfix.reg.
The Portal throws loads of errors if you run it in Explorer 7. There's a registry patch to improve the situation but when a Basis friend sent it to me my
Outlook blocked the attachment. There's another registry patch to keep Outlook from blocking registry patches but I haven't installed it yet.

Install Windows You can wait and do this while the NetWeaver Install is running or when there's some other lull in the action.
Apps. Download and install WinZip
Download and install Adobe Reader
Install the two MaxDB tools from Folder "Setups" on the MaxDB DVD.
Don't be tempted to install other crap. This is a dedicated server not a workstation.

Make an "Install" 3.5 Granting User Rights Make a local (not Domain) "Install" user and make it a member of the (local) "Administrators" group. In Local Policies, add it to the list for "Act as part
User account for the Installation of the operating system", "Adjust memory quotas for a process" and "Replace a process-level token". Otherwise SAPInst will stop and tell you to do it.
If you're in a Domain, make sure the corresponding Domain policies are "Not Applicable" so they don't override the local ones.

3.7 Preparing the SAP A "Central System" install takes care of this. Everything is on the same machine. SAPInst creates the whole directory hierarchy for you.
System Transport Host Check /usr/sap/trans at the end of the install to be sure it gives "Everyone" "Full Control".

Install and patch 3.8 Installing the SAP You can wait and do this while the NetWeaver Install is running or when there's some other lull in the action.
SAPGUIs Front-End Software You need a SAPGUI on the Server and on your regular (client) PC. Download the latest complete install and the latest patch. You don't need the
customization tools for a small installation. You can wait and do this while the NetWeaver Install is running. Don't use the server SAPGUI routinely.
Use a separate PC as a Client to conserve memory on the Server.

Download and 3.10 Installing the Java You need to install J2EE JDK which you download from Sun. SAP requires version 1.4.2. The latest 1.4.2 is 1.4.2.16. Don't be tempted to install Java
install Java Development Kit 6 which Sun will nag you forever to do. There's a specific version for 64 bit SAP. Click on this link
http://java.sun.com/j2se/1.4.2/SAPsite/download.html. You need to register for free then download.
While you're at Sun's site, get the JCE default Policy file. It's a little hard too find but it's there. You can click on this URL for JCE download
http://java.sun.com/j2se/1.4.2/download.html&nbsp;and scroll all the way down to section "Other downloads". Copy it to a convenient folder. You'll
have to point SAPInst to it later. It's a .ZIP file but you don't need to unzip it.
It is very helpfull to check sapnote 716604 for some version problems. At the moment (08.01.2009) versions 18 & 19 should not be used.
After the installation set the variables SAPINST_JRE_HOME and JAVA_HOME to the JDK installation.

Copy the 3.11 Preparing the Ignore SAP's recommendations in this section. SAPInst will prompt you for a folder to copy each DVD into during the install, but it's much easier and
NetWeaver Installation DVDs quicker to copy them all before you start. Make a folder for each DVD. Use the name of the DVD as the Folder name. Be sure there are no spaces in
DVDs to a local any Folder name anywhere that SAPInst might have to go. Another reason to do this is that unless you were a Basis person in a previous life or
drive you're omniscient you'll be doing the install more than once before you get it right. You won't have to recopy from the DVDs the second time.

3.12 Downloading Use the SDN Subscription DVDs.

Installation DVDs from
SAP Service
Marketplace (Optional)

3. Run the Installation

My Step Installation Guide Comment

Section

Choose 2.6 Basic SAP This Guide section is relevant except for the SLD part. It's easiest is to use "DEV" or at least something with something with a "D" in it as a SID. Don't use a
Names System Parameters reserved SID. There's no reason not to use "00" as an instance number if this is your only System.

Get a Solution 2.6.13 SAP Solution Do this now if you haven't already. You have a Host name. Once you decide on a SID and an Instance number you can ask for a key. The Installation
Manager Key Manager key Guide instructions don't apply to SDN Subscriptions. Go to sdn.sap.com -> log yourself in if necessary -> "Subscriptions" (tab) -> "SAP NetWeaver,
3.9 Generating the Development Subscription" -> Subscription Related Links" -> "SAP NetWeaver Installation Key Request". See Note 805390 - SAP Solution Manager is
SAP Solution required for SAP Software. The SDN Subscription folks host one for subscribers. It can take a day or two to get.
Manager Key

Execute 4.1.1 Running

SAPInst SAPinst on Windows Ignore everything having to do with subsequent installations, Clusters or remote installations, Java Add-in, "Application Sharing Server" and any System
variant except "Central System". You shouldn't need to edit any files or do any thing manually except starting the correct version of SAPInst. You should
have copied the "Installation Master" DVD to a Folder so you'll start it from the platform-specific folder there.

5/9/2011
 Page 3 of 6

Typical mode vs. Custom mode: I was hoping that "Typical" would do most of the work, but it makes bad assumptions so you still have to go back and
change its choices at the end. It didn't save me any time. I used "Custom" on my second try and it used all the same defaults. It just displays them one after
the other. Even though I told it to use the D: Drive for everything, "Typical" put the MaxDB data and logs on the C: Drive. It also it made the database and
log sizes too small. I did "ABAP+Java" because I want to be able to print from an ABAP Web Dynpro, which requires Adobe Document Services and
therefore a Java stack.
There are some things that come up as errors during the platform validation; some can be ignored. In my case, I installed on Windows Server 2003
Standard Edition R2, which SAPINST said was not a valid platform. I also installed as a Domain Installation in a real Windows domain, so some of the user
groups like "Power Users" were not present, which also caused SAPINST to think this was not a good OS. Final disclosure:- against recommendations, I
installed on my Domain Controller. I suspect that performance is the main reason that installing on a DC is not recommended. In my case, I'm the only user
in the domain, so I figured what's the harm........ Anyway, when these three errors were reported, I hit "Cancel" button to ignore them and everything
installed OK, and runs fine.

4.1.3 Using SAPinst Obvious

GUI

4.1.4 Interrupted SAPInst is better than the old installer. It remembers everything you did and will reliable pick up where you left off if you have to go back and change
Installation with something. It cannot, however correctly uninstall a blown partial installation. I had to go back and start from scratch.
SAPinst

4.1.7 Entries in the I've never seen a conflict.

Services File Created
by SAPinst

2.1 Basic System Only "Central System" is relevant.

Variants

2.2, 2.3 How to You're probably not distributing your system.

Distribute Instances
to Hosts

Usage Types I installed ABAP, Java, Enterprise Portal Core and Development Infrastructure.

Set 2.6.6 Master Passwords are set by SAPInst: There are a bunch of them. You can specify one master password in the beginning and it uses that as the default for the
Passwords Password others. It reminded me to use at least one digit. Make a list of all the Users SAPInst mentions. I should have done it and didn't. Most of these passwords
can stay - you aren't prompted to change them.

Specify a 2.6.23 Installation Read this section. Basis people say you need to protect your log files. SAP says to mirror them on two RAIDs. I think that's excessive. I put non-mirrored
Drive drive logs on one RAID. I used D: for everything except the Database logs.
2.6.24 MaxDB file
systems
2.5.1 Distribution of
Components to Disks

Specify a 2.6.2 Database ID I saw no reason for it to be different than the regular SID.
Database ID <DBSID>
2.6.25 Database ID

2.5.2 SAP Directories The basic part is relevant. SAPInst creates all the directories you need.

Enter more 2.5 System SAPInst is capable of creating all of the Operating system (vs. SAP) Users automatically. This means the User that executes SAPInst has to have strong
Parameters Configuration permissions. The normal way to accomplish this is to put them into the "Administrators" group. Unfortunately you can't add a Domain user to the local
machine's "Administrators" group and you can't add a local User to the Domain's "Administrators" group. A Local installation is easier because SAPInst can
create all the OS Users on the local machine automatically. A Domain installation means that some Users will be created on the Domain. I don't see a way
to have this happen except to follow SAP's procedure for creating the Users on the Domain by hand. You don't need a Domain installation unless you are
building a distributed System.
If you don't have another Windows server that's a Domain controller, "Local" is the only choice. I presume you use "Local" for a Laptop install. If you want to
have more than one physical server you need to have a Windows domain. The SAP Machine can't also be the domain controller. Your choice determines
who you log in as when you run SAPInst. For a Local installation you need to be a local Administrator (a member of the "Administrators" group). Logging
into a Domain account won't work even if it's in the "Administrators" group. I got into a Catch 22: I had to log into a local Account to answer questions until I
got to the "Local" vs. "Domain" choice. Then I had to switch to a Domain account. I eventually gave up and installed "Local".

2.7 Multi-Language I made mine Unicode because I want to get used to writing Unicode compliant code, which runs on either kind of System.
and Unicode Support

2.9 Application Not relevant.

Sharing Server as an
Optional Standalone
Unit

Specify Data Make more and bigger Database and log files. I made six 8196mb Data files and two 6144mb Log files.
and Log files

JCE Policy Give it the JCE default Policy .ZIP file path.
File

Archives to Don't worry about SAPCRYPTO.CAR. Leave is unchecked.

Unpack

Let it run Do something else for a while. The first time through you'll probably have to respond to errors.
Mine ran all the way through on the third try.

4. Do the Post-Installation Steps

My Step Installation Comment

Guide Section

5/9/2011
 Page 4 of 6

Log in with 5.2 Logging On I couldn't wait to log in so I did before I did the Start and Stop test. There are two Users: SAP* and DDIC. You need to secure them. The Basis book tells how.
SAPGUI to the SAP It's much less important now that SAPInst uses the password you gave it rather than a default one like it used to. Make an account for yourself. I copied SAP*
System to make mine. It gives you SAP_ALL which you might as well have since it's your System to trash. Neither SAP* nor DDIC can make Customizing changes to
5.3 Logging on a Customer system so you'll need another Account pretty soon in any case. Log out again.
to the Portal Log into the J2EE Engine and the Portal as "J2EE Administrator". Save the URLs as Favorites. If you have Explorer 7 you'll get errors unless you patched
your registry.

Stop and Re-start 5.1 Starting and Read this section. Back in Windows, start SAPConsole with the new Icon SAPInst created. Stop the system with a right click. Your "Install" User can do it.
Stopping the The System will take a few minutes to die. In the meantime, read "5.2 Logging On to the SAP System" Log out of your "Install" user and log back in as
SAP System <sid>adm. I rebooted to see if it would use any less memory. It didn't. Then restart the System. It's one step on a "Central System". It will take a few minutes.
Java takes the longest.
Log into SAPGUI as yourself.

Check the I like to see how full the database is right away so I run "MaxDB" -> "Database Manager" before doing anything to fill it more. If you made a 50gb database it
Database will probably only be a quarter full. The MaxDB Users are "superdba" and "control".

Set the Time Use Transaction "SPRO" to change System Time zone to yours or to GMT if you're a purist. Set Users' Time zones as you create them. You have to do this
Zone in Client 001 even though it's a System-wide setting.

Installation Execute Transaction "SM28" (Installation Check). It didn't tell me anything.

Check

Generate the Execute Transaction SGEN (Load Generator) using the option "Generate All Objects...".
ABAP Load Select at least "Basis" and "ABAP". If you don't, you'll be sorry unless you have an incredibly fast Server. "SGEN" compiles ABAP Programs so you don't
have to wait for each one the first time you hit it, which is tedious. It runs in the background for many hours.
Check the size of the database again afterward. Take care of you log area. SGEN will increase the logs.

Apply for a one- If you might be getting new hardware within the next few weeks, wait on this step until after you install it. I changed disks and my Hardware Key changed
year License making the first license key useless.
There's tons of documentation that obscures what is really a painless process.
Execute Transaction "SLICENSE" to see your Hardware Key and Installation number. Go to sdn.sap.com -> log yourself in if necessary ->
"Subscriptions" (tab) -> "SAP NetWeaver, Development Subscription" -> Subscription Related Links" -> "License Key Generation". Do the next few steps
while you're waiting for the e-mail reply. It comes quickly.

Hook up the 5.5 Installing the Install the Help from the DVD to a hard disk using the instructions in the "EN" or "DE" folder. I like HTMLHelp (fka WinHelp) the best. Use Transaction "SR13"
Online SAP Online or "SPRO" (Customizing) to link the first two entries on the Help menu to the Documentation. Make a folder and call it something like "NW70_WinHelp". Move
Documentation Documentation the "EN" or "DE" folder the installer made under it. Entering something like "F:\NW70_WinHelp" in the "Path" field of "SR13" only works when you're on the
Server. Otherwise you have to make a share and enter something like \\Computer\Share\NW70_WinHelp. Allow "Everyone" to at least read it.
If you can see the menu hierarchy on the left but no text on the right, see "Patch the Registry" above.
You can also use the online help with "SR13".

5.6 Configuring I skipped this one.

Remote
Connection to
SAP Support

Install the one- 5.4 Installing the Save the attachment from the e-mail you were expecting (see above). Execute Transaction "SLICENSE" again. None of the obvious Toolbar buttons or Menu
year License SAP License selections do what you want, which is to install the new "Digitally signed key" from the text file from the e-mail. The trick is to click "New Licenses" button. The
"Installed Licenses" subscreen changes visibly. The "Install" button at the bottom of the subscreen changes invisibly and now does what you want.

Set up System 5.7 Performing You can do the next few steps in the Implementation Guide ("IMG", Transaction "SPRO") which takes you into the System Administration Assistant,
Administration Initial ABAP Transaction "SSAA". It has instructions on how to set it up. Be careful - some of the advice it gives you is obsolete in NW 7.0.
Assistant Configuration

Configure the 5.7 Performing A helpful Basis person described a simple setup that would be appropriate for an SDN Subscription. Having a Virtual second system with a Transport route
Transport Initial ABAP allows exports to happen so transport files (co-files and data-files) you can take with you are created. Execute Transaction "STMS". You only have one real
Management Configuration System so it becomes your Transport Domain Controller. If your SID is "DEV" your default name will be "DOMAIN_DEV". In "Overview: -> "Systems", create
System a Virtual Consolidation system using "SAP System" -> "Create" -> "Virtual System". You could instead create an "External System" which is the same thing
except that it has its own separate Transport directory. The Documentation says it's appropriate for putting Transports on removable media but they don't say
exactly how. I didn't think I needed two directories.
In "Overview: -> "Transport Routes", switch to "Change" and use "Configuration" -> "Standard Configuration" -> "Development and Production System" to
add the two Systems to the Route. It does things when you save.

Set up the 5.7.2.3 Before you can set up Operation Modes you have to set up Profiles (Default, Startup and Instance), which are misleadingly below Operation Modes it in Easy
Profiles Configuring work Access. Originally, you had to edit the profiles at the OS level, but they are now editable in Transaction "RZ10" which maintains versions and copies them
processes down. The instructions don't tell you enough about how the tool works. Transaction "RZ10" is an editor for files stored at the OS level. Unix has similar editors
for its parameter files. Unfortunately, SAPInst doesn't copy the first versions up into the database. You have to use do it explicitly. From then on it's top-down.
The "Import" button on the toolbar doesn't do what you need. You have to use "Utilities" -> "Import profiles" -> "Of active servers". My intention is to decrease
various parameters to lessen memory use, but I want to get past the full backup before I mess things up.

Set up an 5.7.2.2.1 Set up Set up an Operation mode like "Normal_operation" using Transaction "RZ04" -> "Operation mode" -> "Create". Then add an Instance with "Operation mode" -
Operation Mode Operation > "Maintain instances" -> " Operation mode view" -> Instance" -> "Create new instance". Use the defaults for everything.
Modes Set the daily schedule using Transaction "SM63". Select all the intervals and assign "Normal_operation" to them.

5.7.2.2.2 Set up You don't need Logon groups or do load distribution because it's just you.
Logon groups

5/9/2011
 Page 5 of 6

Make an 5.7.2.2.3 Set up Use your own Account unless you really want to get fancy.
Administrator Administrators
account

Schedule 5.7.2.2.4 The "Standard Jobs" button in Transaction "SM36" gave me a warning that some were already running. I checked and the Performance monitor Jobs were
background jobs Schedule already running, presumably having been set up by SAPInst. I didn't want to start any more Jobs yet as there won't be much activity like Dumps or Batch
background jobs inputs that would need to be cleaned up.
Report "INST_JOBS_STANDARD" sets up several standard Reorganization background jobs like deleting old Dumps. It might do the same thing as the
"Standard Jobs" button.

Install printer(s) 5.7.2.2.5 Install The easiest to set up is a Frontend printer, which you probably want even if you also set up SAP Printers. There'a a new, easier flavor, "Access method G"
a printer which doesn't require SAPLPD. See Note 821519. First you execute Report RSPO0075 to enable it. Then follow the directions in the "SAP Printing Guide" ->
"Defining an Output Device for Front-End Printing (SAP GUI for Windows)". You probably also want to set the Windows printer as your default and check
"Output Immediately" and "Delete After Output" in "System" -> "User Profile" -> "Own Data" in all your User accounts.

5.7.2.2.6 Windows doesn't support "Central Logging" which is the only part that needs configuration. The regular System log works out of the box.
Configure the
system log

Adjust Profile 5.7.2.3 Execute "Tools" -> "Administration" -> "Monitor" -> "System Monitoring" -> Transaction "SM50" (Process Overview) to see what's running by default. If
parameters Configuring work anything, you might want to cut down to three Dialogs and two Backgrounds to save memory. I left mine alone.
processes

Confirm 5.7.2.4 Installing SAP is only selling SDN Subscriptions in Germany and the USA. German and English are already installed by default. So you probably won't be installing
Languages languages and another language. In Transaction "I18N" I added "DE" (German) to the list of Languages to get rid of an inconsistency error between it and the Instance
performing profile. Then all I had to do was to activate German and English. I didn't notice anything different after I did the activation.
language
transport

5.7.2.5 I didn't configure ITS. It's a kluge and if I learn it a Client will force me to fix some broken garbage application. Viva Web Dynpro.
Activating and
configuring the
integrated
Internet
Transaction
Server (ITS)

System Change Use Transaction "SPRO" to check or set the System Change Option
Option

Enter an Address 5.7.2.6 I had already put a Company address in when I created my Account in Transaction "SU01".
Maintaining
address data

Upgrade 5.8 Applying the

NetWeaver Latest Kernel Download and read "SAP NetWeaver 7.0 Support Package Stack Guide — SPS14". SAP says over and over that you need Solution Manager to download
and Support Service Packs but your SDN Subscription ID bypasses the restriction. You can use Download Manager just like before Solution Manager existed. Even
Packages though I found a place in the documentation that says to use JSPM for the Kernel, ABAP and Java, it doesn't do ABAP. You still have to use SPAM/SAINT
for that. Some Basis people like to upgrade the Kernel manually by copying the file. JSPM worked fine for me.
Install Download Manager on a client PC rather than your server.
I downloaded an SPS09-to-SPS13 Upgrade the first time. SPS09 is the level you get when you install NW 7.0 SR2. Then when SPS14 came out I
downloaded just SPS13-to-SPS14. Navigate to the "service.sap.com" -> "Software Download" -> "Download" -> "Support Packages and Patches" -> "SAP
Support Package Stacks" -> "SP Stack Netweaver 7.0" -> "SP14". The download page takes you through three steps. First you select the from-to and which
Usages you want (e.g: ABAP, Java, Portal). I checked "Restrict according to Usage" so I could eliminate XI and Mobile. Then you tell it which OS and
database. In the third step, click "Save as File" to get it to make an XML file for JSPM to use. I de-selected the SAPGUI updates because I had already done
them separately. Click "Add to Download Basket". Execute Download Manager from the Start Menu. Download everything to a staging folder and then into
"\usr\sap\trans\EPS\in" on your server.
In each case (JSPM and SPAM/SAINT) you have to upgrade the tool first and then make a second pass to get everything else. I wasn't careful enough
in JSPM and didn't deselect everything else. It was smart enough skip everything except JSPM itself.
While I was upgrading the SPAM module, I got errors saying that the input SAR file had errors. Fix for this was to download the latest SAPCAR from Service
Marketplace and copy to the kernel directory (Irenamed the old one first, just in case!).
You have to unpack the ABAP part manually. Only the .CAR files are important. Sometimes the small files with no extension are missing.

2.4 Production The SDN Subscription License doesn't allow a "Production" System, but unlike on the "Test Drive" you do have a "Production Client" on your Development
Client System which is the one you log into. It starts as a copy of "000". Making it is one of the Post-installation steps.
Considerations

Copy Client "000" 5.9 Performing The hard part of this is the Profile change. The instructions don't tell you, but only non-default parameters are stored in the "RZ10" database Therefore you
the Client Copy have to add the "sapstar" parameter you need because it doesn't exist in the database version. There is a Search help, though. Each time you save, you get
a new version. When you "Activate" you copy the current database version down to the OS parameter file. The instructions also don't say which file the
"sapstar" parameter is in - it's in the "Instance" profile. They also don't tell you whether to do a "Stop" or a "Shutdown". I did a "Stop" and it worked.

5/9/2011
 Page 6 of 6

While I was editing the profile, I changed the default Client to "200" in the "Default" profile.
I found it interesting to look at all the parameters.

Back it Up 5.10 Performing The steps are wrong for Windows Server 2003. You back the registry up with the "Automated System Recovery Wizard".
a Full Installation
Backup

Create Start and How do you create Start and Stop Icons like you get in the "Sneak Preview"?
Stop Icons

Configure MMC You can add Snap-ins to the SAP Console. I couldn't get the MaxDB one to work that way. See "How-tos" page for the full instructions.

Fill the Flights 5.7.2.7 Execute Transaction "BC_DATA_GEN" to fill the Flight database. If you use Transaction "SM36" to create a Job for Report "BC_DATA_GEN" with one of the
database Configuring standard Variants you can have it create a bigger database.
business SDN Subscription doesn't include any Business applications except for the Flight database.
applications

Download and The NW 7.0 Sneak Preview has some of these already installed. I found where to get them and how to install them on a Forum post:
import "Web https://www.sdn.sap.com/irj/sdn/message?messageID=2768833. Unzip the downloaded file or copy from the CD. Put files K*.<SID> (the small ones) into
Dynpro for \usr\sap\trans\cofiles and R*.<SID> into usr\sap\trans\data. If you want the "Original system" of the imported Objects to be your Subscription system (e.g:
ABAP" and/or DEV) so you can edit them directly rather than copying them first, change the extensions of each pair of files files to your SID. You can change the type of
other book Transport your CTS thinks they are ("Transport of Copies", "Relocations" or "Release to Consolidation System") by editing the CO-file. Be careful to overwrite
examples. what you want to change so as not to mess up the offsets. I don'y know of a "Co-files Editor" that breaks them into fields for editing. You could write one and
Copy from CD post it on SDN.
and Import "Next Execute Transaction "STMS" -> Import Overview" (Icon) -> "<SID>" (single-click) -> "Display import queue" (Icon) -> "Extras" -> "Other Requests" -> "Add".
Generation Select the current system (e.g: DEV) and the Request(s) you want.
ABAP Click "Import Request" (Icon).
Development"
and/or other book
examples

Activate Internet
Communication ABAP Web Dynpros use these services to communicate with the Application server. They are turned off by default for security reasons. See OSS Note
Framework 1088717 (Active services for Web Dynpro ABAP in transaction SICF). They tell you to activate some and not others. Why not activate them all since it's not a
Services Production system?
Remember to activate new WDAs if you import them. Are they automatically active if you create them locally?

Get yourself a Go to http://service.sap.com -> "SAP Support Portal" -> "Keys & Requests" -> "SSCR Keys" and read the documentation. Then hit ""Register Developer". It
Developer Key already knows everything except your User ID. "SSCR" means "SAP Software Change Registration" The Quick link is http://service.sap.com/sscr.

Get yourself a A Namespace is your own prefix instead of a "Z" or a "Y" to use on almost any Workbench Object you create (e.g: Classes, Reports, Tables, Domains). Since
Development it is unique worldwide like a URL you can transport your Objects into any SAP System without fear of clobbering something that's already there. SAP has
Namespace reserved Namespaces for its own use for add-on products like "Legacy System Migration Workbench". The prefix starts and ends with a forward slash. It
must be five to ten characters long including the slashes. In the newer Notes SAP says you should use your company name or some derivation of it. In older
Notes SAP says you can also use a product name. I want to bundle up all my reusable Objects like my message handler helper Class so I applied for
"/DBP/" (Developer's Boilerplate), and it was accepted. Go to http://sdn.sap.com -> "Subscriptions" -> "Software Subscriptions FAQ" (left side navigation) ->
"Can I apply for a Namespace...? " Read the Notes and the documentation on what a Namespace does for you and how to apply for a Namespace and install
the keys.
It's a bit of exttra work do develop in a Namespace. See "How-tos" page.

Get an account Register for ESA (...irj/sdn/esareg). You have to be logged in as your "S..." User ID, not your "P...". This doesn't work yet.
on ES Workplace

Explore Web Enter through the "Explore Enterprise Services" (page) -> "Test Drive" -> Pick a System & Log in-> Execute Transaction "WSADMIN" -> Choose a Web
Services Service -> "Web Service Home Page" -> "Document style" -> "Save as... ....wsdl" To try it out: -> "Web Service Home Page" -> "Document style" -> "Test".
http://erp.esworkplace.sap.com/sap/bc/gui/sap/its/webgui?~okcode=wsadmi

Adobe Document 2.8 Running Several Notes warn you about ADS not having a 64-bit version, but make no suggestions. The PAM is much more sensible about it. If you hunt you'll
Services Adobe eventually find where SAP says ADS will run as a 32-bit application on certain a 64-bit environments like Windows 2003 on x64. Adobe Document Server
Document doesn't run native on 64-bit Windows (Note 925741).
Services on Non The ALV Component for ABAP Web Dynpro prints through ADS so you need it.
-Supported
Platforms

5/9/2011