SAP Web application server and business server pages known as BSP functions are the core component of the SAP WAS development model.They have entry to the total performance of the SAP system; for example they will access BAPIs, make RFC calls, and access the database. They include the following set of parts:
- BSP pages. These are pages that comprise the structure of the presentation. These pages have code in both ABAP or JavaScript used to insert the appliance data. BSP pages could have dedicated occasion handlers and parameters. The system distinguishes between two types of pages: correct ages and web page fragments. Web page fragments include small items of data which might be supposed to be inserted in regular pages reminiscent of web page headers and footers.
- Navigation structure. It defines the navigation movement that is used to direct requests to Internet pages.
- MIME objects and themes. This group incorporates all of the static objects, particularly images, documents, and so forth, that belong to the BSP application. MIME objects are dealt with within the MIME Repository. A theme is a container for MIME objects which are used to customize the looks of the Internet application. Themes are based mostly on CSS (Cascade Type Sheets) and needs to be used to clearly separate the looks from the application and presentation logic. A theme is created as an independent object and subsequently may be assigned to a number of BSP applications.
- Software Class. This is a international ABAP class that encapsulates the business logic necessary for the BSP application. The Utility Class should present interfaces (for example by BAPI calls) to the features it defines. All of the components of the class (attributes, strategies, and so on) are directly accessible by the BSP application. The Software Class holds the enterprise core logic of the applying and therefore is the key element to assume about if you're migrating from earlier dynpro-primarily based applications. These functions ought to provide a way to make business capabilities available for use inside BSP applications.
The work center for creating BSP purposes is the Web Utility Builder.The primary interface of the web Utility Builder is the SAP Improvement Workbench, which has been enhanced to offer all the functionality obligatory for Web functions building. The Net Utility Builder is started with transaction SE80.
The display screen of the Net Application Builder has three areas. The large area within the proper side (showing a photograph in Figure eight-3) is the working area. This space will maintain the programmer’s editor and all of the attributes and configuration screens associated to each of the totally different elements which might be parts of the BSP application. The left side is split in two areas. The top left space allows the person to go to the totally different elements of the SAP growth system. The underside left shows a browser permitting entry to the thing hierarchy. The Repository Browser button will allow you to access the zone of the builder that contains the BSP objects.
A BSP Software Instance
An entire Web software is normally a lot more than a set of BSP pages. Application Class interfaces are essential to allow access to enterprise capabilities from BSP. Traditional SAP programming techniques and ideas are still legitimate and needs to be the core of any excessive-high quality Web application.
The first thing to note with this version of the Net Utility Builder (as against the previous ABAP Development Workbench) is that it's not doable to create a Improvement Class. This may occasionally come as a surprise to the skilled ABAP developer, however the idea has not disappeared: the previous Improvement Lessons are actually referred to as Packages. Packages are precisely the same thing; therefore, they act as containers for every type of object in the SAP Growth Workbench, including Dictionary Objects, ABAP Classes, and so on, but in addition to all that, there are now Internet Objects.
So, the first step of our instance will be to create a Package deal that can contain all the elements of the application. For that, choose the Bundle option within the object sort listing box in the prime left space and fill in the identify of the package deal that you want to create (on this case, I title it ZWEBAPPS). Press the Enter key and the system will verify if a package with the given title already exists in the system.
The next steps will create a BSP application. The process goes as follows:
As quickly as the BSP application is created, you need to fill it with pages. To do this, proper-click on on the entry for the BSP utility within the left-hand space and select the choice Create/Page .
This leads to the Create Page dialog field . Right here you'll have the option to tick the small check field in the bottom left if you want this page to be a web page fragment. The page whose identify is default.htm will doubtless be considered by the BSP processor as the default page of the appliance; that is the page that will doubtless be sent to the browser when the person doesn’t request any specific page.
After assigning the web page to a transport request, the Growth Workbench will open the text editor in the work space with a primary HTML template in it. You may now begin typing your individual code .As quickly as the typing is finished, it is time to save the page. Then, it's possible to test it by pushing the Check button. An Internet browser window ,exhibiting the HTML generated.
When accessing the page with a browser, it'll require the consumer to present a username and password. The SAP username and password used to create the appliance or any SAP person with administrative rights will be granted access. The URI within the server name house used to access the BSP software is often /bc/bsp/sap//. The Web page proven in does nothing fascinating; it is just a static HTML page and utilizing a SAP WAS for serving it's probably overkill. The greatest way to do extra fascinating things is by embedding programming code within the HTML code. Within the BSP page:
The first thing to note with this version of the Net Utility Builder (as against the previous ABAP Development Workbench) is that it's not doable to create a Improvement Class. This may occasionally come as a surprise to the skilled ABAP developer, however the idea has not disappeared: the previous Improvement Lessons are actually referred to as Packages. Packages are precisely the same thing; therefore, they act as containers for every type of object in the SAP Growth Workbench, including Dictionary Objects, ABAP Classes, and so on, but in addition to all that, there are now Internet Objects.
So, the first step of our instance will be to create a Package deal that can contain all the elements of the application. For that, choose the Bundle option within the object sort listing box in the prime left space and fill in the identify of the package deal that you want to create (on this case, I title it ZWEBAPPS). Press the Enter key and the system will verify if a package with the given title already exists in the system.
The next steps will create a BSP application. The process goes as follows:
- Proper-click on the newly created entry for the bundle (ZWEBAPPS).
- Choose the option Create/Internet Objects/BSP Software in the pull down menus.
- In the dialog field, select a reputation for the BSP utility (in our example, ZW1) and assign it to a transport request.
- As quickly as the BSP utility is created, a hierarchy will seem in the browser area of the Web Utility Builder. The entry for the BSP utility shall be beneath Net Objects/BSP Functions in the Repository Browser menu.
As quickly as the BSP application is created, you need to fill it with pages. To do this, proper-click on on the entry for the BSP utility within the left-hand space and select the choice Create/Page .
This leads to the Create Page dialog field . Right here you'll have the option to tick the small check field in the bottom left if you want this page to be a web page fragment. The page whose identify is default.htm will doubtless be considered by the BSP processor as the default page of the appliance; that is the page that will doubtless be sent to the browser when the person doesn’t request any specific page.
After assigning the web page to a transport request, the Growth Workbench will open the text editor in the work space with a primary HTML template in it. You may now begin typing your individual code .As quickly as the typing is finished, it is time to save the page. Then, it's possible to test it by pushing the Check button. An Internet browser window ,exhibiting the HTML generated.
When accessing the page with a browser, it'll require the consumer to present a username and password. The SAP username and password used to create the appliance or any SAP person with administrative rights will be granted access. The URI within the server name house used to access the BSP software is often /bc/bsp/sap/
default.htm. This would be the starting page of the application. It can present only hyperlinks to entry the opposite pages in the application. list.htm. This page reads the contents of desk ZWEBUSERS and presents them in a desk in HTML format. add_entry.htm. This page shows a kind for the person so as to add a model new entry to the desk and will course of the insertion of information when the person presses the submit button.
An XML/XSLT engine Purposeful SMTP plug-in Assist for the SOAP A graphical development device Enhanced event model Controls for developing WML functions for the Wi-fi Access Protocol (WAP)
Related posts
sap internet transaction architecture
SAP internet transaction application components
SAP authorization and client administration in mysap.com
Mysap web application server
SAP ABAP FILTER DEPENDENT BADI IMPLEMENTATION
BADI AND OTHER ENHANCEMENTS COMPARISON
SAP ABAP BADI PART ONE
No comments :
Post a Comment