| |
| |
|
| |
PB
to ASP.Net Migration Architecture Overview |
| |
|
| |
|
| |
|
| |
User
Interface Components |
| |
For Web applications, PM.Net framework uses MVC architecture and PowerMigrator.Net front-end tool will generate ASP.Net UI components automatically extracting it from the original PowerBuilder application. This increases reusability, maintainability, and extensibility. This also helps to encapsulate dependencies between forms and the logic associated with navigating between them. |
| |
|
| |
User
Interface Process Components |
| |
Complex
user interfaces often require many highly complex forms.
To increase reusability, maintainability, and extensibility,
you can create a separate user interface process (UIP)
component to encapsulate dependencies between forms and
the logic associated with navigating between them. You
can apply the same concept to the dependencies, validation,
and navigation between components of a single form. These
UIP components are typically custom components that are
based on design patterns.
The interaction between UI and UIP components often follows
the Model-View-Controller or Presentation-Abstraction-Controller.
|
| |
|
| |
Business: |
| |
The business layer implements the business functionality of the application. The domain layer is typically composed of a number of components implemented using PowerMigrator tool, process and methodology to convert PowerBuilder NVO's to equivalent VB.Net components, which will be augmented with PM.Net framework. This will be deployed on the core Microsoft® .NET platform for scalable distributed component solutions and optionally with Microsoft BizTalk® Server for workflow orchestration. |
| |
|
| |
Data: |
| |
The
data layer provides access to external systems such as
databases. The primary .NET technology involved at this
layer is ADO.NET.
1. In memory structure is nothing but the datawindow buffer
and related logic has been migrated to data set which
is an integral part of ADO.Net
2. Data access logic, data update logic like insert, update
and delete logic is an integral part of the datawindow.
This logic will be extracted and implemented in .NET using
Data Adapter, which is again an integral part of ADO.Net.
3. Conventional PowerBuilder application use to connect
to the database using typically either using Native or
ODBC driver, which will be migrated to data connection
object in ADO.Net.We will also take care to use .Net XML
as a part of our migration, which will enable the migrated
VB.Net component to server as Web service component. |
| |
|
| |
|
|
|
|
|
