Database Reference
In-Depth Information
◾
Views
: Views are responsible for only the layout of the application data. A view's life cycle
is determined by its corresponding controller, which also routes the view's calls and com-
municates with a model.
◾
Event Handler
: The event handler is part of the flow control, which determines the temporal
and logical flow of an application. Event handlers are executed at predefined times in a pre-
defined sequence during the life cycle of a BSP page. The event handler is implemented in
ABAP Objects and allows access to certain objects at the runtime.
◾
Navigation
: The navigation structure consists of the beginning and end of a request. This
makes it possible to change the flow control of a BSP application without changing any
code.
◾
Multipurpose Internet Mail Extensions (MIME) objects
: MIMEs are outcome of the original
Internet e-mail protocol that enabled exchange of a variety of data on the Internet. MIMEs
include audio, video, and image data, cascading style sheets (CSSs), and ASCII files.
Each new BSP application creates an identically named MIME directory that stores all the
application-specific MIME objects.
11.2 Java Custom Development
Java programming language is responsible for the success of J2EE. Though Sun developed the J2EE
specification, it is a cross vendor standard. In fact, this ensures that the software components can
be reused, and ERP systems from different vendors can integrate with each other easily. Support
from other vendors like IBM and Sun has ensured that J2EE continues to evolve and adopt to
meet the latest challenges and requirements of the market. The J2EE platform is suitable for a wide
range of distributed Web-enabled applications and Web-based applications.
SAP Java Development Infrastructure (JDI) and SAP NetWeaver Developer Studio (NWDS)
enable more efficient software development while addressing the challenges of global development
and delivery scenarios, namely, support for the entire life cycle of the software application, multi-
located distributed development by numerous teams, and customizations at partner and customer
sites.
A software application or product life cycle is spread across an extended period of time as it
includes the maintenance of the application involving periodic upgrades and releases. This leads
to the need for modularization, encapsulation, reusability, maintainability, and so on. Current
approach to address these requirements is to develop software in components that encapsu-
late functions accessible only via the predefined interfaces. Such an approach reduces coupling
between the software components rendering them easily maintainable because of their mutual
independence while also making them accessible via predefined interfaces. This dilemma is solved
by the SAP Component Model.
Similarly, during the development phase, when the development teams are spread across dif-
ferent locations, the software development effort is confronted with many problems related to
currency and correctness of versions, automatic synchronizations of code developed by different
teams at different locations at different times, and so on. These problems are related to the issues
of using libraries of different versions, preparing source files and runtime object consistently, and
simultaneously accessing and changing of files or objects at different locations. The complexi-
ties of the synchronization arise from the fact that these sources and objects are used in differ-
ent versions in the development and consolidation systems and again in different versions in the
