Big4Guy

You can find some of the key basics of the Web Dynpro Netweaver framework in my earlier post here. Today, lets have a look at the Phased Model framework functionality within the Web Dynpro framework. The phased model is a predetermined sequence of steps that need to be executed everytime there is a client request or response cycle. One important point to note here is that the phased model does not take care of component instantiation. It is only after all the components of the application have been instantiated that the phased model handles client requests or round trips during the lifecycle of the application.

Thus, there exists a one to one relationship between the phased model and the visible window. Each time a modal pop up window is displayed, it is processed using a new instance of the phased model. Some of the steps within the web dynpro programming phased model are discussed below:

1) First step is the receipt of an incoming request.

2) As a next step, the data from the incoming request is transferred to a client neutral location called the data container.

3) The 'doapplicationstatechange' step also known as the floating stage beacuse the creation of this step may vary depending upon the type of the incoming request.

4) The data in the request is validated against simple dictionary rules, however, if there are non validating actions, then the data request is sent as it is, without any validating steps in between.

5) Finally, as part of response rendering, an incoming request coming from an html client and after the post processing phase does not require any error messages, the user interface tree is passed on to the client. For non html requests, the UI data is rendered on to the screen without taking into account the fact that this might not be visible.

Related Posts

SAP EP Implementation Timelines
Meeting SAP Go-Live Deadline
SAP BW Implementation Guide
Business Process Definition for SAP Implementations

You can find the basics of SAP Netweaver XI Exchange Infrastructure here. As mentioned earlier, SAP NW XI is helpful in connecting different vendor systems SAP or Non SAP systems which have been implemented on different platforms such as ABAP, JAVA, .NET etc. The SAP Netweaver Xchange Infrastructure (XI) has many components. Lets have a brief look at the components of the SAP XI and how these are used in the XI Integration process:

1. At the outset, the user needs to define the SAP systems in the systems landscape in 'SLD'. Once this is completed, one needs to define the interfaces in the XI Integration Repository at the design stage. It is important to note that the data in these different systems may not be in the same format. This description of the data will need to be defined in the data mapping.

2. The components, interfaces and mappings are defined in the 'Integration Repository' during the configuration phase of SAP XI, which determines the integration processes in the system landscape called logical routing. This is stored in the XI Integration Directory.

3. The next step in the XI Integration process is to transfer application specific content. This can be achieved using XML Schema for transferring messages between sender and receiver. IDOCs, files etc are used to determine the data structure.

4. So how does the entire process of SAP NW XI Integration work once it is setup? When an inbound message is received at run time, the integration engine of the integration server checks the configuration of the integration directory. The configuration data defined earlier is used to determine the receiver of the message. In that sense, the integration server acts as the central point of communication and distribution of XML messages.

5. Lastly, SAP XI 3.0 works in conjunction with the SAP Web AS Server 6.40. SAP now uses JAVA as a standard and Java administration tools need to be used to manage the Integration Directory and Repository.

I will discuss another important topic of connecting different systems to SAP Netweaver XI tomorrow.

Related Posts

SAP Solution Manager Toolset
How to Implement SAP Netweaver - Part I
How to Implement SAP Netweaver - Part II
SAP Web Application Server AS Concepts and Basics