Академический Документы
Профессиональный Документы
Культура Документы
This document provides you an overview how to install/configure etc. MiniSAP WAS 610.
Table of contents
Introduction
Overview of process
Starting Installation
After Installation
Logon to SAP
Imports
Starting SE80
Setting up TMS
NLS Problem
Saposcol
New users
Kernel Change
Licensing
Enlarging Database
LSMW
Work Process
ST03
Trouble shooting
Hints
Exceptions
Appendices
Related documents
Introduction
MiniSAP 610 is a SAP Web Application Server 610 with only basis level without application
modules. It’s ideal for ABAPers and Basis consultants to get familiar with the WAS environment.
Overview of process
System requirements:
h) 256MB RAM
Starting Installation
5. Logon to Windows 2000 with administrator rights.
7. Start <CD Drive>\setup.bat or choose the Start Installation button on the right.
8. Choose 'Open' within the File Download Window popup.
11. Enter the target drive for SAP DB database software (Default: C:\).
After Installation
16. After successfully installation you can find a ‘Start SAP WA1’ shortcut on your desktop.
There is the same shortcut in your start menu Start Menu\Programs\Mini SAP Web
AS.
17. Double-click the Start SAP WA1 icon to start the database and the SAP System.
18. Stopping:
Cancel and close the Start SAP WA1 window with CTRL-C. (This only stops the SAP System
but not the database.)
Logon to SAP
21. Add to your SAPGUI the following entry
24. After you logged on you already have some favorites…in german:-)
25. In the menu you can see only the Tools part available, there is no menu for Application
modules.
30. After starting the SAP DB Database Manager (Start -> Programs -> SAP DB -> Database
Manager) for the firrst time, you have to register your database. To do this, choose File ->
Register in the Menu, specify the entry for the server where your database is running, mark the
database WA1, press the 'Register' button, and enter the username and password of the Database
Manager Operator (User name = 'control', Password = 'control'). Close the registration window.
Now you can perform all administrative tasks with the SAP DB Database Manager for Web
Application Server Demo Version.
Imports
31. It’s recommended that setup TMS now and import corrections package now, before
creating own transport request. See chapter Setting up TMS and Importing correction and
examples.
Note: This document describes the step in order I did … so it wasn’t the best order:-(
Starting SE80
32. If you start se80, the default.html BSP application is coming up.
Setting up HTML help
33. Copy Data CD\Htmlhelp to your local drive. E.g. C:\MiniWAS\Htmlhelp
34. In SAP start transaction SR13.
35. Press enter for information message ‘Caution: The table is cross-client’.
39. In the ‘Prompt for Workbench request’ pop-up press the ‘Create button’.
44. It didn’t work for me… I’ve mistyped the location. But now it’s OK.
Setting up TMS
45. Logon as DDIC.
48. For pop-up ‘Start deletion of CTS tables? Make a backup of the system beforehand’ choose
Yes.
49. For pop-up ‘Start deletion New initialization of CTS required’ choose Yes.
50. It takes a few minutes. You will get the following log:
Changing profile
53. You will get a nice log with full of error messages….
54. Go back to the selection screen and select profile WA1_D00 Instance.
56. Change the value of rdisp/wp_no_btc from 0 to 1. This is the number of the background
processes.
57. Press the copy button than go back to the selection screen.
59. For the pop-up ‘Incorrect parameter values detected. Display values?’ No.
67. Start transaction sm50 to check the work processes. As you can see there is a background
job (BGD).
68. Execute program RDDNEWPP (transaction SE38), which schedules the background job
RDDIMPDP within the WA1 system.
73. Enter description for the Transport Domain and save it.
75. ‘Transport profile TPPARAM contains entries for system WA1’ Cancel.
76. Go to System Overview.
84. In change mode follow the menu path Configuration -> Standard configuration -> Single
system.
87. In the system Overview SAP system-> Create -> Virtual System
88. In the system overview SAP System->Check-> … Perform all the 3 kind of check. All of
them should be OK.
89. You may have to refresh it several times because of the time-out problems.
90. In the initial screen of TMS all the error message is disappeared now.
Transport on OS level
91. To export or import transport requests, use the transport program tp as follows:
92. Open a DOS-box and change to the WA1 directory (C:\MINIWAS, for example).
93. Run the command file dbenv.cmd to set the environment variables for the database
connection.
98. sm50, sm04, st11, st02, st04, db12, db02, sm12, sm13 are fine.
102.
110. Create an entry with MIME type: image/gif Name extension: *.gif
I’ve started report RSCPINST, but I couldn’t activate the codepage, since parameters
install/codepage/db/non_transp and install/codepage/db/transp were not set. In rz11 the value was
‘sapparam.c: Don't use’…so I didn’t use….
During next startup there was no such message anymore…I’ve checked TCPDB, and a new entry
was created for 1100.
Saposcol
In st06 when I tried to check the parameters, all of them was zero, the saposcol wasn’t running.
I’ve tried started manually, but in windows level it terminated. I’ve downloaded the latest 620
version ‘COLL 20.77 02/05/06 620’, I’ve overwritten the old one (after rename it) and started
manually. It seems that it works fine now. In windows level it wasn’t registered as a service.
Since Saposcol doesn’t start automatically, I’ve modified runWA1.cmd like this:
REM =====================================================
REM =====================================================
set DBMS_TYPE=ada
set PATH=%PATH%;C:\sapdb\programs\bin;C:\sapdb\programs\sap;C:\sapdb\programs\pgm
REM =====================================================
REM =====================================================
cmd /c strdbsWA1.cmd
REM =====================================================
REM =====================================================
start /B saposcol -l
REM =====================================================
[C:\DOCUME~1\INOTAIP\LOCALS~1\Temp\dev_coll.tmp]
******************************************************************************
******************************************************************************
New users
New user can be created in SU01. Just copy BCUSER to a new one. A developer key is valid for
BCUSER, but for new user use 29671482393151224771. Somehow it didn’t work for me….
Kernel Change
Based on OSS note 502999 WAS 610 is able to run with Kernel 610. I wasn’t sure about which
version to download: Unicode/non-unicode. In OSS 544623 and 548016 it’s described how to
convert database to Unicode, so I decided not to convert to Unicode.
After I’ve downloaded the WAS 620 Non-unicode NT/I386 kernel and unpacked them my WAS
didn’t start.
C *** ERROR => Get of the precompiler version failed : sqlcode=-888 (Could not load libpcr
(7.3.1-.))
[dbslada.c 4837]
B ***LOG BY2=> sql error -888 performing CON [dbsh#2 @ 962] [dbsh 0962 ]
B ***LOG BY0=> Could not load libpcr (7.3.1-.) [dbsh#2 @ 962] [dbsh 0962 ]
B ***LOG BY2=> sql error -888 performing CON [dblink#1 @ 419] [dblink 0419 ]
B ***LOG BY0=> Could not load libpcr (7.3.1-.) [dblink#1 @ 419] [dblink 0419 ]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 8534]
I’ve found OSS 557227, which describes how to import/register Precompiler Runtime for SAP
DB.
5. For me it was :
C:\>dbmcli dbm_getpath indepprogpath
OK
C:\sapdb\programs
11. The system was very slow, it compiled at the first logon/transaction starts.
SICK error
I’ve reseted the old kernel, but then I’ve got the “Invalid load format”, probable now it had format
for 6.20.
It was strange that the old kernel used the old db library…
Finally I’ve decided to try again after checking OSS Note 5470, 185745 and 162991.
rsts/ccc/cachesize = 1000000
to
rsts/ccc/cachesize = 6000000
After changing this parameter “Reorganized Buffer” message didn’t appear anymore. I’ve tried to
avoid “Invalid load format” message with SGEN generation, but it was so slow…I gave it up….
1. Unpack ‘MiniWas_Correction01.zip’
4. Unpack ‘Example_Transport.zip’.
7. Logon as DDIC.
8. Start transaction STMS.
11. You might have to refresh it several times if you get a connection error.
14. WA1K900002
15. Yes.
17. B20K8A0H5B
18. Yes.
Finally I did it on OS level with tp command. I had problems that I already had a request with
name WA1K900002…I’ve renamed the request on OS level.
2EEPU164 "You cannot specify the component 'TABLE_LINE' for""a generic line type in the current
statement. allo"
C:\MiniWAS\trans\bin>dbenv.cmd
C:\MiniWAS\trans\bin>REM =====================================================
C:\MiniWAS\trans\bin>REM =====================================================
C:\MiniWAS\trans\bin>set DBMS_TYPE=ada
C:\MiniWAS\trans\bin>set
PATH=C:\sapdb\programs\bin;C:\sapdb\programs\pgm;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem
;C:\PROGRA~1\IBM\CLIENT~1;C:\PROGRA~1\IBM\CLIENT~1\Shared;C:\PROGRA~1\IBM\CLIENT~1\Emulator;C:\PRO
GRA~1\Symantec\pcAnywhere\;C:\PROGRA~1\SAP\FrontEnd\Controls\;;C:\MiniWAS;C:\sapdb\programs\bin;C:
\sapdb\programs\pgm;C:\sapdb\programs\sap;C:\sapdb\programs\bin;C:\sapdb\programs\sap;C:\sapdb\pro
grams\pgm@
WA1 buffer:
TASK |PROJECT |P|CMD I |DD Im |Activ |MainI |MC Ac |ADO I |VersF |XPRA
|Gener |UMODE|TAGS
--------------------+--------------------+-+------+------+------+------+------+------+------+-----
-+------+-----+----
B20K8A0H5B | | |1 |6 |6 |1 | | |127 |
|115 | |
meaning:
Everything OK
meaning:
Everything OK
WA1 buffer:
TASK |PROJECT |P|CMD I |DD Im |Activ |MainI |MC Ac |ADO I |VersF |XPRA
|Gener |UMODE|TAGS
--------------------+--------------------+-+------+------+------+------+------+------+------+-----
-+------+-----+----
B20K8A0H5B | | |1 |6 |6 |1 | | |127 |
|115 | |
WA1K900077 | | |1 | | |1 | | |2 |
|2 | |
meaning:
Everything OK
C:\MiniWAS\trans\bin>tp pf=TP_DOMAIN_WA1.PFL import B20K8A0H5B WA1
meaning:
C:\MiniWAS\trans\bin>
I’ve changed back the name and import it (on os level) and it was fine:
I’ve checked the version of one of the imported object…it showed the import date:
I’ve checked the requests ans I’ve seen request WA1K900002 was completely overwritten…so I
recommend to do this import before creating any request.
Licensing
You can extend your license with requesting a new license key. To install the license key:
22. Enter the license key. You can see here your Hardware Key.
23. If you send this key to SAP they will send you a license key immediately.
I don’t know why, but on SAP level I always got an error message, so I couldn’t install it….so
I’ve tried on OS level, and it worked.
C:\MiniWAS>saplicense -show
system-nr: INITIAL_SYSTEM_IDX
system-nr: INITIAL_SYSTEM_IDX
*** license useable ***
C:\MiniWAS>saplicense -get>
C:\MiniWAS>saplicense -install
SYSTEM-NR =
INSTALLATION NO = DEMOSYSTEM
LICENSE_KEY 1...5....0....5....0...4
LICENSE_KEY = CYEKCGJDFDBIALSLOM7AYBMT
C:\MiniWAS>saplicense -show
system-nr: INITIAL_SYSTEM_IDX
system-nr: INITIAL_SYSTEM_IDX
system-nr: INITIAL_SYSTEM_IDX
I still couldn’t register a new user as a developer, but I had to register BCUSER with Developer
key ‘29671482393151224771’.
Enlarging Database
After the kernel change my db was almost full, so I’ve added another data file. You have the
possibility to add two additional data file.
4. You can change the size, location and the type of the new datafile.
5. Press enter.
2. Unpack the file in the trans directory. It will create one file in the data, one file in the cofile
dir.
6. Create an LSMW>CMD file in the bin dir with the following content:
import
file = 'c:\MiniWAS\trans\data\R000652.B5T'
including 'R3TRTABU'
including 'R3TRTDAT'
8. Reset the buffer using the following command in the command field:
/$SYNC
You can start LSMW with transaction code LSMW. You will got the following Welcome message
first time:
Work Process
I’ve activated the ENQ and the UPD process, since they don’t need too much memory resource.
At startup they need about 6M each, but later the memory usage was about 600K for each of them.
At least I haven’t got any short dump at startup at least….in SICK the SPO process is still
missing….
The only problem that I’ve got an error message in the development trace files, that there are too
many process.
I’ve tried to activate SPO process, too. SICK was fine that time, but there were errors in the spool
process development trace, so I’ve deactivated it.
Tuning, Profile changes
I’ve changed PHYS_MEM from 64 to 128. The system paged more than before, so I changed
back it.
I’ve changed DIR_HOME = from ‘.’ To ‘.\work’ and created this dir…..the traces were created to
this dir….but the system halted after startup. In the dev_disp:
*** DP_FATAL_ERROR => Gateway could not be started - I better exit now
ST03
In the Miniwas dir there are many stat file, but I cannot see them in ST03, I’ve got the following
pop-up and a MESSAGE_TYPE_UNKNOWN abap short dump. I think it’s a programming error,
but I couldn’t find any relevant OSS note.
Trouble shooting
Not known.
Hints
a) Do the correction request import before creating any new request.
Exceptions
None
Appendices
None
c) Parameters: PHYS_MEM value seems too low (64MB), but increasing this value would cause
performance problem…
d) New client: Normally it’s recommended not too touch client 000. Since it’s a demo system
and I don’t want to enlarge the db, I will use client 000.
f) Unicode: How can I activate Unicode? => It would need extra resource (CPU, memory,
dbspace)
g) ZTTA/DEFTITLE: normally this parameter defines the title of the logon screen…it didn’t
work for me.
h) Dev key????
j) How can I maintain HTTP users? -> Theoretically SICF, but I couldn’t find the entry for
BCUSER.
m) SQL-studio connection?
s) Installing HTTPS?
v)
Related documents
OSS Notes:
OSS Note 502999 Installing a 6.20 kernel into a system with 6.010 Web AS
Links: