发现一本ABAP开发好书,如果有影印版我一定要买!

下面内容摘自SDN的WIKI: Next Generation ABAP Development Book

Book Content

So what we ended up with was something amazingly close to the original table of contents. We adjusted it some to include some of the very good ideas that Rich had brought to the table during our work on the SDN Days session.

But more important than the technical topics covered, Rich and I really wanted to take our 20+ years of combined ABAP development experience from a customer’s standpoint and bottle it up in an easy to digest format.

The structure of this book reflects the workflow of a development project. The first half of the book focuses on creating the data and application logic layers and then service-enabling them. The second half of the book focuses on creating the user interface layers.

Chapter 1: Workbench Tools and Package Hierarchy
Before we begin our project, we will review some of the changes and enhancements to the ABAP Workbench. In this chapter, we will look at the new ABAP Editor, the Refactoring Assistant, the new development tools perspectives in transaction SE80, and the new debugger. Lastly, we will create the packages and package hierarchies for the project.

Chapter 2: Data Dictionary Objects
In this chapter, we will model the data relationships and build the corresponding Data Dictionary objects. We’ll study the tools for generating table maintenance, creating lock objects, and utilizing foreign keys. We’ll also explore the new technology of strings and binary strings within transparent tables.

Chapter 3: Data Persistence Layer
In this chapter, we’ll build the logic that controls the persistence of application data. We’ll start by generating persistent object classes for the underlying data dictionary tables created in Chapter 2. Then, we’ll build a set of business object classes to hide the inner technical details of the Persistent Objects. In addition to the new technology of Persistent Objects, we’ll show you how to use ZIP compression on large strings.

Chapter 4: Consuming a Web Service
Not all project data will originate from one centralized system. For example, in the sample application, some data will be stored in a legacy system and accessed remotely via Web Services. In this chapter, we will examine the process for generating a Web Service proxy object and integrating this proxy into the data persistence layer.

Chapter 5: Shared Memory Objects
After some analysis, it will become apparent that the sample application has some static data that will be accessed repeatedly. In this chapter, we will describe how you can provide the best performance by structuring the data access for this type of data into an ABAP Shared Memory Object.

Chapter 6: Model Class
In this chapter, we will begin to implement the core application logic, which is implemented as a Model Class. This same class will later be used as the business logic layer of all the UI technology examples. This chapter focuses primarily on object-oriented design patterns while introducing techniques for sending email and manipulating XML.

Chapter 7: ABAP and SAP NetWeaver Master Data Management
This is the first of our “What-If” chapters. Here, we look at an alternative approach to the project where our master data is modeled and stored in SAP NetWeaver Master Data Management (SAP NetWeaver MDM), instead of the local Data Dictionary. This chapter will focus on how we would alter the data persistence layer to read this data via the SAP NetWeaver MDM ABAP application programming interface (API) instead of directly from the local database.

Chapter 8: ABAP Unit
Before building any additional objects on top of the existing application logic, this is a good point in the project to unit test what has been completed. In this chapter, we’ll look at the built-in unit test tool, ABAP Unit, and examine how unit test classes can be integrated directly into the model class.

Chapter 9: Exposing a Model as a Web Service
Not all the logic from the sample model class will be exposed via a user interface. Instead, some of the data was designed to be exposed as a Web Service so that it can be accessible to external systems as well. In this chapter, we’ll examine the Inside-Out approach for generating Web Services.

Chapter 10: Exposing a Model as a Web Service Using SAP Net-Weaver Process Integration
This is the second of the two “What-If” chapters. In the previous chapter, we looked at the Inside-Out approach of generating Web Services via remote enabled function modules. In this chapter, we’ll look at the world of Enterprise Service Modeling. We’ll show you how the same logic could be modeled in SAP NetWeaver Process Integration (SAP NetWeaver PI) and then implemented as a server proxy in ABAP using the Outside-In approach.

Chapter 11: Classic Dynpro UI/ALV Object Model
In this chapter, we turn our attention to user interface logic. In the sample application requirements, there are a group of internal users who are full time SAP GUI users and who need powerful reporting tools. Therefore, we’ll learn how to build a classic Dynpro screen on top of the Model View Controller (MVC), which uses the ALV Object Model for its reporting output.

Chapter 12: Web Dynpro ABAP
Since most of the sample application’s users are not SAP GUI users, we’ll look at how you can build a Web Dynpro user interface for these users. This chapter will focus on real world Web Dynpro applications that contain multiple component usages, ALV integration, and table popins.

Chapter 13: Business Server Pages
The next user interface use case is for an Internet-facing application. This user interface needs to be highly customized and stateless for scalability. Therefore, in this chapter, we will use Business Server Pages (BSP) in order to show the flexibility they provide for highly customized style sheets and AJAX integration.

Chapter 14: Adobe Forms
Adobe Forms technology offers an interesting paper-like alternative user interface. In this chapter, we’ll look at each of the major types of Adobe Forms—print forms, online interactive forms, and offline interactive forms.

Chapter 15: SAP NetWeaver Portal
Although we have focused on ABAP as the primary development environment until now, it is also important to see how some of the SAP NetWeaver Portal technologies can be used with the best aspects of ABAP. In this chapter, we’ll explore how to wrap each of our user interface examples in iViews within the SAP NetWeaver Portal and how portal eventing can be used for cross iView communication. We’ll also look at how we can use SAP NetWeaver Visual Composer to build code-free applications that consume ABAP services.

Chapter 16: RSS Feed Using an ICF Service Node
In this chapter, we’ll examine how Internet Communication Framework (ICF) Service Nodes can be combined with XML processing in ABAP to produce interesting Web 2.0 type projects. As the final example of the book, we’ll implement an RSS Feed using these technologies.

Chapter 17: The Closing
In the final chapter we will look back on the completed project and re-view the most important points of what has been discussed.

4 Responses

Subscribe to comments with RSS.