introduction to the abap trial version

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 1

How to Administrate the ABAP

Trial Version

Applies to:

SAP NetWeaver 7.0

Summary

This is the PDF version of a blogs series published in 2007 on the SDN. The series gives an introduction on how to work with and administrate the ABAP Trial Version. If you are interested in the comments and answers to the comments on the blogs, you should read the original blogs on SDN. Otherwise this PDF file gives you an easy opportunity to work your way through the whole series.

Authors: Manfred Lutz, and Thomas Weiss

Company: SAP AG

Created on: 28 January 2010

Author Bios

Manfred Lutz has been working at SAP since 1989. Initially, he worked in the Logistic Development Department, building what was to become the ancestor of the SAP R/3 system. He also designed the interface that enables communication between SAP and external systems. In 1993, he moved to the Certification Group where he worked as a Partner Manager in order to provide seamless integration between SAP R/3 and third-party products. In 2000, Manfred joined the Global e-Post Initiative at SAP as Product Manager and, for the last three years, has been involved in SAP NetWeaver Product Management. He is now responsible for the rollout of Web Dynpro for ABAP to internal application developers,

customers, and partners. Also he cares for the need of a new kind of Partner Program for the ISVs.

Thomas Weiss has a Ph.D. in analytic philosophy. He worked as a professional writer before joining, in 2001, the SAP NetWeaver product management training team where his responsibilities included the e-Learning strategy for ABAP. After becoming more involved in writing ABAP material himself, he is now a member of the SAP NetWeaver Application Server Solution Management. One of his main interests lies in rolling out ABAP topics both for experts and for beginners by writing blogs in SDN.

http://www.sdn.sap.com/irj/scn/nw-downloads

http://www.sdn.sap.com/irj/scn/weblogs

How to Administrate the ABAP Trial Version


© 2010 SAP AG 2

Table of Contents

Summary............................................................................................................................................................. 1

Author Bios ......................................................................................................................................................... 1

Table of Contents ............................................................................................................................................... 2

Download and Installation of the Trial Version ................................................................................................... 3

Starting and Stopping the Application Server ..................................................................................................... 7

Importing a Transport into SP11 ....................................................................................................................... 18

Database Manager and SQL Studio ................................................................................................................. 23

Related Content ................................................................................................................................................ 31

Copyright........................................................................................................................................................... 32



© 2010 SAP AG 3

Download and Installation of the Trial Version

This blog was posted by Manfred Lutz on 20 March, 2007, on SDN at ABAP → Application Server → Beginner.

If you are interested in the Trial Version and you like to download it, please check the system requirements first. If your PC does not meet the requirements the installation might fail or the performance will be very bad (which might reduce the fun to work with ABAP). The download consists of two rar-files SAPNW2004sABAPTrialSP11.part1.rar and SAPNW2004sABAPTrialSP11.part2.rar.

These two files should be downloaded into same directory. Since both of them are bigger than 1 GB the download might take some time.

To find out whether the downloads are complete you can check the file size (click on the file in the Explorer and choose 'Properties'): …part1.rar = 1.572.864.000 and …part2.rar = 1.189.536.491 If everything is alright so far you have to extract the files with an appropriate rar-tool (if there is none on your computer just google for 'rar tool download' and download and install it on your PC). Just click on the first one (…part1.rar) and after a little while your unpacked structure should look like:

The rar-tool creates a structure that you can see in the right side of the Explorer window. In the DOC directory you can find all HTML stuff related to the installer. The image is the installation itself. There are two database tools in the maxdbtools directory. And the SAPGUI directory contains a Compact SAP Logon 7.10 that you should use as User Interface. To start the ABAP server installation click on 'start.htm' and follow the dialog steps.

https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/cfc19866-0401-0010-35b2-dc8158247fb6#abap

https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/cfc19866-0401-0010-35b2-dc8158247fb6#abap



© 2010 SAP AG 4

Be sure to check the system requirements. It is also important that there are no remnants of an older Trial Version or Sneak Preview installation left on your PC.

The Installation can be started from the Installation page by clicking on the word 'Installer'.

Be aware that the installation of an SAP system is typically a pretty complex task, with installing a database, starting it, filling it with a huge amount of data, configuring the network connection, starting the system and doing lots of configuration steps. Therefore the installation guide of a real SAP system consists literally of hundreds of pages for experienced administrators. All this is hidden in this trial version as good as possible but nevertheless it is done under the hood. So it might be a good idea to leave the installation alone and not to work heavily on the PC during the installation.



© 2010 SAP AG 5

This window shows you the real beginning of the installation process. The only information you have to provide during the installation is the target directory and you have to define the master password for the database. (the users of the ABAP trial server itself and their passwords are predefined).

The installation typically takes between half an hour and two hours dependent on your hardware. Therefore you have to be patient especially at 16% and 43%. Don’t worry if the installation seems to make no progress for a while at these points. As long as the hard disk is turning everything is ok. If you cancel the installation process manually you might leave the system in an indefinite state which may cause trouble with a new installation.

When the installation is finished the system will ask you how you to proceed. If you have already a SAP Logon on your PC you just can click on 'Next' which will start the Application Server and the SAP Management Console for monitoring purposes. If you don't have the SAP Logon yet on your PC, it would be a good idea to uncheck the check-boxes and install the GUI first. For that you have to go to the SAPNW2004sABAPTrialSP11 directory and open SAPGUI folder.

By double-clicking on 'SapGuiSetup.exe' you will start the installation of the Compact SAP Logon 7.10. In the dialog you are guided through some information pop-ups and finally you come to the window with the product selection. Just click on the 'Select all' that will check the check-box for you and then choose 'Next' and finish the installation.



© 2010 SAP AG 6

There will be a new icon for SAP Logon on your desktop now. After the installation of the SAP Logon a reboot might be required.

In the next edition of 'ABAP Trial Version for Newbies' it is shown how to start the Application Server and how to logon with the SAP GUI to the system.

There are two forums where you can post your questions and ask for help in case of trouble.

Trials, Previews & Other Downloads for general discussions about the trial versions (interesting projects you are doing with it, wishes for the future,…)

Web AS Preview Installation for concrete problems with the installation

https://www.sdn.sap.com/irj/sdn/forum?forumID=118&start=0

https://www.sdn.sap.com/irj/sdn/forum?forumID=88



© 2010 SAP AG 7

Starting and Stopping the Application Server

This Blog was posted by Manfred Lutz on 23 March, 2007, on SDN at ABAP → Application Server → Beginner.

In Part 1 of this blog series you successfully downloaded rar files from SDN, and you completed the installation process. At the end of the installation, you were asked whether you wanted to start the Application Server. In accordance with the governance described in the previous blog, it would be a good idea to install the SAP GUI first. The SAP GUI should be installed before you proceed with Part 2.

Now you are prepared to start the Application Server with the SAPMMC. SAPMMC is a SAP snap-in for the Microsoft Management Console (MMC). SAPMMC allows you to administer all the SAP systems running on a particular machine. To start the SAPMMC in Windows, choose Start -> Programs -> SAP -> Start SAP Management Console, or click the meter icon on your desktop at any time. For our ABAP Trial Version with the system ID 'NSP' the MMC will look like this:

The left pane shows a tree with the elements of the NSP system consisting of the database and the Application Server.

The Application Server also provides information about the current system operation. Clicking the question mark will take you to the documentation that explains in detail the layout and context menu of the SAP System Manager Snap-In.

To start the NSP system, choose the NSP icon, go to the context menu and choose 'Start' or simply click on the triangle in the tool bar. The database is started first, and after a short while, green lights will indicate that the NSP is running. To check if the server has started completely select the 'ABAP WP Table' node in the left pane, which displays the work processes, the work horses of an ABAP system. Details about the work processes will be covered in a later blog. For the moment we just use the display to see that everything has started.

If you want to start the system directly without the MMC you can also get to that point by choosing Start -> Programs -> SAP NetWeaver 2004 Trial Version -> NSP -> Start Application Server. This will not start SAPMMC, but it is easier, and if you are not interested in system information, it might be sufficient for your needs.

Now it would be ok to log on to the system. To do this, start 'SAP Logon' (that is installed with the SAPGUI), click 'New Item' and double-click 'User Specified System' in the next dialog box. Enter the system parameters requested. The screenshot below shows the configuration for running an Application Server and SAP Logon on the same machine, which is our recommendation for the ABAP trial version. (If you prefer to install the GUI on another machine you have to make sure that the server PC is reachable via TCP/IP, has a valid IP address or DNS entry, that no firewall is blocking the GUI protocol etc.)

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/6113



© 2010 SAP AG 8

Click 'Finish' and a new entry for 'NSP' is displayed in the SAP Logon window.

Select 'NSP' and click 'Log On'. After a few seconds, the log-on screen appears.

The connection between your Application Server and SAP GUI is now up and running, - Congratulation!



© 2010 SAP AG 9

The following users have been created in your NSP system by default:

'BCUSER' for the standard user (e.g. development)

'DDIC' for administration

'SAP*' for license purposes

There is a temporary 30 day license on every NSP system after installation, which can be extended by 90 days again and again (and will be described in another blog).

Use the 'BCUSER', with the password 'minisap' (as can be seen on the last screenshot) and press 'Enter' or click the green icon at the beginning of tool bar. The entry screen should look like the screenshot below.

Pressing the 'Help' button will open a menu. The first entry is 'Application Help' which links directly to the SAP documentation for the subject you are currently working on. This is only available in the new ABAP Trial Version (SP11).

In the field that has the cursor, you can enter the so-called transaction code. This is a shortcut e.g. 'SE80' to start the development environment that takes you directly to the functionality you'd like to use.

Try it out and enjoy!



© 2010 SAP AG 10

This is the development environment (ABAP workbench) of the ABAP Application Server. Here you can find most of the tools for building business applications in ABAP. If you now open the 'Help' menu and select 'Application Help' a browser will appear and show you an overview of the functionality in the ABAP workbench.

When you have finished checking out the ABAP Trial Version, you can use the SAPMMC to stop the system. Select the NSP icon, go to the context menu and choose 'Stop' or just click the black rectangle in the tool bar, which will stop the Application Server but not the database.

Another way is to do this is: Click Start -> Programs -> SAP NetWeaver 2004 Trial Version -> NSP -> Stop Application Server. This will also stop the database.In one of the next parts of this blog, we'll show you how easy it is to write a simple program in ABAP.

There are two forums where you can post your questions and ask for help in case of trouble: Trials, Previews & Other Downloads for general discussions about the trial versions (interesting projects you are doing with it, wishes for the future, etc) Web AS Preview Installation for concrete problems with the installation

https://www.sdn.sap.com/irj/sdn/forum?forumID=118&start=0

https://www.sdn.sap.com/irj/sdn/forum?forumID=88



© 2010 SAP AG 11

Exporting Development Objects from SP8


The last part of this series was about the CTS (Change and Transport System), where you have got a brief overview of the transport mechanism on the ABAP Application Server. This blog explains what you have to do to get a package with your development objects out of a system. For our purposes, exporting a package means to get it out of the ABAP universe to the installation level.

Let's assume that you have created some programs or Web Dynpro components in the old (SP8) Trial Version and you want to upgrade the Trial Version to SP11. You use the transport system to save your programs and components and make them available in the new system.

You first need to set up the Transport System for the export.

On the installation level, the 'SAP' directory must be shared to the 'System' user. Open the MS Explorer, select the 'SAP' directory and choose 'Sharing and Security...' from the context menu. Select the 'Share this folder' option, and enter 'sapmnt' as the share name.

Choose 'Permissions'.

Add a new user 'SYSTEM' with full control.




© 2010 SAP AG 12

Choose 'Apply' and then 'OK'.

Now the changes on installation level are complete. To set up the transport environment, you need to start the Transport Managment System (Transaction STMS).

Choose 'System Overview' (red rectangle) and select 'CL5' from the table. Open the context menu, and choose 'Extras'. Then, choose 'Distribute and Activate Configuration'.



© 2010 SAP AG 13

Leave the distribution options as the default. Choose 'Enter'.

After you have successfully distributed the transport environment, there are two files in the 'bin' directory of the 'trans' tree on the installation level. These files are required by the RFC (Remote Function Call) to retrieve information about the receiver side.

The tree should look like this. Now the setup of transport system is complete.

In our example, we assume that there is a development object 'Z_MY_QUIZ' in an old Trial Version (SP8) that you need to migrate to the new Trial Version (SP11), since you can have only one ABAP Trial Version on your PC. This object is a copy of the 'WDT_QUIZ' Web Dynpro ABAP component in the Trial Version.

To export an object, it must belong to a package.

How to create a package is shown in the previous blog in this series. The package for migration in this blog is 'Z_MY_PACKAGE'.

Let's assume that the object you want to migrate is created as a local object. (new users do not normally concern themselves with packages and workbench orders.)




© 2010 SAP AG 14

You first need to reassign the object to a package. Go to the ABAP workbench (SE80) and select the component you want to reassign.

This would be the right way to reassign the object, but be careful: there is a bug in the current version. Mime objects will not be written to the export. For that you need to copy the component to a new object that is related to a package.

Choose ENTER.

The system prompts you with the workbench request to create the package. This request will comprise all the objects from the package, and will be the basis of the transport.

Choose ENTER.

SAVE.

There may be another dialog step - confirm this in the same way.



© 2010 SAP AG 15

Now the package Z_MY_PACKAGE which contains all the objects in the Web Dynpro Component/Application Z_MY_QUIZ is linked to the workbench order NSPK900044. In the following steps, this order and the related tasks will be released.

Open the transport organizer (transaction SE09). You will find the virtual system 'CL5' as the destination of our transport.

Select the correction (NSPK900045) for our workbench order, and click the truck icon in the menu bar. This releases the correction. A released correction cannot be changed. To release a workbench order, all the related corrections must be released first. After releasing the correction, an OK icon appears right to the correction.

You process the workbench order in the same way. Place the cursor on the workbench order and click the truck icon in the menu bar. This starts the physical transport.



© 2010 SAP AG 16

To find out when the transport is finished, you will have to refresh a couple of times.

Now the transport is complete. On the level of the installation, there is data written to two files.

The 'cofiles' directory contains the header information in a file beginning with 'K' followed by the workbench order number and ended with the system ID.



© 2010 SAP AG 17

The transport data can be found in the 'data' directory beginning with 'R' followed by the workbench order number and ended with the system ID.

These two files can be copied to the corresponding directories in any other SAP system in order to be imported. This will be the topic of the next blog.



© 2010 SAP AG 18

Importing a Transport into SP11


In SP11 (SP = Service Pack) the transport system is preconfigured. That means you no longer have to distribute the transport environment with the transaction 'STMS'. The only thing that you have to do is to share the SAP folder on the installation level. This was described at the beginning of the previous blog.

The two files for the RFC communication in the 'bin' directory are there - This was done as part of the pre-configuration.

The output of the export from the last blog must be copied to the corresponding directory in the new installation. The 'cofiles' directory is for the header of the transport (beginning with 'K'), the 'data' directory is for the data of the transport (beginning with 'R').

Now we come to the actual import. Start the Transport Management System (transaction 'STMS') and click the truck icon in the menu bar.

This is the Import Overview.



© 2010 SAP AG 19

Select the NSP queue with double-click.

Open the context menu of 'Extras' and choose 'Other Requests >> Add'. A dialog box prompts you to specify a transport request.

Click the input help icon.



© 2010 SAP AG 20

Select the request you'd like to import and choose 'Enter'.

Choose 'Enter'.

Choose 'Yes'

Select the transport request and click the small truck icon in the menu bar.



© 2010 SAP AG 21

Enter '000' as the Target Client and leave the rest unchanged. Choose 'Enter'.

Click 'Yes'.



© 2010 SAP AG 22

The import is now running. Click the 'Refresh' button in the menu bar to find out when the import is finished.

Start the ABAP workbench and have a look for the migrated component 'Z_MY_QUIZ' from the package 'Z_MY_PACKAGE'.

Activate the new component. To make the new component run you have to create a Web Dynpro Application for it. Select the new component, open the context menu and choose 'Create' >> 'Web Dynpro Application'. Now you can run the migrated object. Open the 'Web Dynpro Applications' folder, select 'Z_MY_QUIZ', open the context menu and choose 'Test'.



© 2010 SAP AG 23

Database Manager and SQL Studio


In this blog it is explained how to do the very first steps with the tools of the MaxDB that are shipped with the ABAP Trial Version download.

In the download of the ABAP Trial Version there are two tools, one for database administration (Database Manager) and the other one for having a look at the tables and the execution of SQL statements (SQL Studio) on tables of interest. Both tools have a GUI as well as a CLI (Command Line Interface) - in this blog only the GUI is used. The database itself (MaxDB) is installed during the installation of the ABAP Trial Version. The tools however must be installed manually. You can find them in the directory 'maxdbtools' of the tree structure of the download

.

After installing the tools you will find two new icons on your desktop.

Double-click on the Database Manager icon to start this tool.



© 2010 SAP AG 24

The Database Manager comes up with its entry screen.

At first you have to select the database you'd like to administrate.

Click on the 'Add' button.



© 2010 SAP AG 25

The system will give you an overview of the databases that are on the selected machine (your PC). In my case, there is only the NSP database from my ABAP Trial Version. Select the database of your choice and press the 'OK' button.

Now the selected object will appear in the upper right window. Click on the Connection icon (red) to get connected to the database.



© 2010 SAP AG 26

You have to enter the name of the database manager user for this database and his password. The user is set by the ABAP Trial Version installation to 'control'. The password is the one you entered during the installation process for the database. Press OK.

Since in my case the NSP database is not running, there are red balls at the database icons. Click on the online-icon (highlighted in red) in the menu bar to start the database. If the database is running, there will be a process 'kernel.exe' in the processes list of the task manager of your PC. In addition to that, a service 'MAXDB: NSP' will be started.



© 2010 SAP AG 27

Now it's done - the database is up and running and we are connected with the Database Manager tool to it. The entry screen gives you an overview about the database size and the sessions that currently running.

Yet you can have a closer look at the different items. For example, click on the 'Information' button on the left menu, a submenu will appear, and then select 'Data Area'.

Here you can see the physical locations where the data is stored. If more storage is needed you can add another volume (Configuration).

Since with the new ABAP Trial Version SP12 the online documentation for the Database Manager is not available, you can get the information from here.

http://aiokeh.wdf.sap.corp:1080/SAPIKS2/contentShow.sap?IWB_INDUSTRY=SAP_BW&RELEASE=700&_CLASS=IWB_EXTHLP&_LOIO=7AEA493905E6D07DE10000000A114084&TMP_IWB_TASK=DISPLAY&_HIDETREE=yes&_SLOIO=D1802CFC454211D189710000E8322D00&LANGUAGE=EN&_SEQNUM=0&_SCLASS=IWB_STRUCT



© 2010 SAP AG 28

Click on the 'Tools' button in the menu bar and select 'SQL Studio' or just double-click on the 'SQL Studio' icon on your desktop. The SQL Studio will be started. Be sure that the database is running, if you come by way of the desktop item.

Click on the key button on the left side of the button bar.

Enter the server name where your MaxDB is running,

Database = 'NSP',

User = 'SAPNSP',

Password is the one you entered during the installation of the ABAP Trial Version for the database.

Press 'OK' button.



© 2010 SAP AG 29

This is the entry screen of the SQL Studio.

If you like to see for example which tables are in the ABAP Trial Version, just click on 'Tables' and scroll down. For example, searching for the structure of the SFLIGHT table that is well known from our demos, enter 'SFLIGHT' into the field below button bar and open up the tree beyond 'Tables (SFLIGHT)'.

Here you can see all elements of table SFLIGHT.



© 2010 SAP AG 30

If you are eager to know what is inside the table, just go back to the dialog window and enter the open SQL statement 'select * from sflight'.



© 2010 SAP AG 31

Related Content

For more information, visit the ABAP homepage.

ABAP Trial Version

Blogs On SDN

https://www.sdn.sap.com/irj/sdn/abap

http://www.sdn.sap.com/irj/scn/nw-downloads

http://www.sdn.sap.com/irj/scn/weblogs



© 2010 SAP AG 32

Copyright

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

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 or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

introduction to the abap trial version

Documents