LANSA Open for .NET
Tight, Fast, and Secure Access to IBM i Resources from .NET Applications
Unite Your .NET IBM i Applications
LANSA Open for .NET is a Visual Studio plugin designed to allow Windows developers to access IBM i (AS/400, iSeries) resources (including data and programs) directly within their .NET applications. It offers easy integration between IBM i and .NET.
- Extend IBM i data and resources to Windows rich client and web applications built in .NET.
- .NET developers have easy access to IBM i server functions including programs, spooled files, message queues and OS commands.
- Easy access to LANSA’s Business Rules Engine (including data definitions and validation rules) from .NET applications without having to write any code.
- Safely open up enterprise data on the IBM i without risking security or data integrity and completely eliminate the need for database synchronization.
- Faster and more secure than ODBC. All apps benefit from rigourous IBM i security checks, data validation and referential integrity checks.
- No knowledge of IBM i, DB2 or LANSA is needed.
Build IBM i Connected Windows Desktop Apps
Desktop applications written with C# or VB.NET, or potentially any Common Language Runtime (CLR) compliant language, can utilize the Repository Explorer and Data Model Editor to access native IBM i resources in real-time, like data areas, message queues, operating system commands, and more.
Â
Just about every non-LANSA application contains source code that validates data before it is inserted, updated, or deleted in the database. Even though these rules are critical to safeguarding the integrity of enterprise data, they are often duplicated in multiple programs. Not only is this a maintenance nightmare, but it can also introduce validation variations and application inconsistencies.
Â
In LANSA, business rules critical to enforcing data integrity are stored centrally in the LANSA Business Rules Engine rather than in the database or application. This locks down system-wide validations, calculations, and other business rules by delivering a completely independent Data Services Layer
that governs all database access.
Â
With LANSA’s Repository, these business rules, algorithms, and calculations reside centrally within the repository and are not duplicated and sprinkled across many programs.
Â
Since real business applications must integrate with a wide array of other systems inside and outside your enterprise, you can rely on the strength of LANSA’s integration capabilities, which stand well above other alternatives.
Build IBM i Connected ASP.NET Web Apps
Web applications written with ASP.NET, in potentially any Common Language Runtime (CLR) compliant language, can utilize the Repository Explorer and Data Model Editor to access native IBM i resources in real- time, like data areas, message queues, operating system commands, and more.
Â
Just about every non-LANSA application contains source code that validates data before it is inserted, updated, or deleted in the database. Even though these rules are critical to safeguarding the integrity of enterprise data, they are often duplicated in multiple programs. Not only is this a maintenance nightmare, but it can also introduce validation variations and application inconsistencies.
Â
In LANSA, business rules critical to enforcing data integrity are stored centrally in the LANSA’s Business Rules Engine rather than in the database or application. This locks down system-wide validations, calculations, and other business rules by delivering a completely independent Data Services Layer
that governs all database access.
Â
With LANSA’s Repository, these business rules, algorithms, and calculations reside centrally within the repository and are not duplicated and sprinkled across many programs.
Build IBM i Connected .NET Web Services
Reduce the cost of publishing web services from IBM i systems by implementing the web services on the Microsoft platform combined with LANSA Open for .NET to expose the functionality and data from the IBM i systems.
Â
Web services written in .NET, in potentially any Common Language Runtime (CLR) compliant language, can utilize the Repository Explorer and Data Model Editor to access native IBM i resources in real- time, like data areas, message queues, operating system commands, and more.
Â
Just about every non-LANSA application contains source code that validates data before it is inserted, updated, or deleted in the database. Even though these rules are critical to safeguarding the integrity of enterprise data, they are often duplicated in multiple programs. Not only is this a maintenance nightmare, but it can also introduce validation variations and application inconsistencies.
Â
In LANSA, business rules critical to enforcing data integrity are stored centrally in the LANSA Business Rules Engine rather than in the database or application.
Benefits of LANSA Open for .NET
Why Use LANSA Open for .NET? LANSA Open for .NET enables IT departments to safely open up their IBM i data and applications to a variety of internal and external .NET applications without risking security or data integrity to deliver a better customer experience to your employees.
.NET and IBM
i Collaboration
Break down application silos and achieve a single version of the truth by enabling .NET and IBM i to work collaboratively to share real-time data, automate business processes, and eliminate synchronization between Windows and IBM i platforms.
Controlled Access to IBM i Data from .NET
Faster Transfer of Data and Information
LANSA Open for .NET implements native record-level access to Db2 data over an encrypted, secure connection. Using native record-level access means .NET applications can quickly work with large volumes of Db2 data by taking advantage of IBM i’s powerful data processing capabilities.
Tighter IBM i Security from .NET
LANSA Open for .NET’s runtime DLL encrypts and compresses data during transmission between the client and the server, protecting sensitive data from being compromised as it is sent down the wire, using industry- standard DES or Twofish.
Easier Resource Management of Dev Teams
Reduce the challenges of managing siloed development teams and multi-platform projects by sharing resources between mixed .NET, RPG, and COBOL development environments by reusing the same enterprise business logic, validation rules, and calculations.
Getting Started Is Fast and Easy
LANSA Open for .NET is easy to use and implement for .NET developers. The class library is shipped with ready-to-run samples in both the C# and VB.NET languages. There is almost no learning curve for .NET developers. No knowledge of IBM i, DB2, or LANSA is needed.
LANSA Open for .NET Resources
Data Sheets
Videos
White Papers
Using .NET to Build Scalable Enterprise IBM i Apps
Mike Otey discusses developing real- world IBM
i applications using Microsoft .NET, integrating IBM i with other enterprise platforms like Microsoft SQL Server and SharePoint, requirements for delivering .NET applications connected to IBM i, and critical enterprise development issues for IBM i and .NET applications.