Borland Janeva .NET Interoperability with J2EE and CORBA Svetlin Nakov Software Development Consulta

1
Borland Janeva.NET Interoperability with J2EE
and CORBASvetlin NakovSoftware Development
Consultant Sofia University St. Kliment
Ohridski www.nakov.com
2
The Need to Integrate the Technologies

• CORBA in the Presentation layer
• Dont Pass Firewalls, Too Complex and High
  Maintenance
• but Code is closer to the native platform
  (better performance)
• J2EE in the Presentation and Data layers
• Resource Intensive, Too Complex and High
  Maintenance
• but Portability and Scalability across multiple
  platforms!
• .NET in the Business Rules and Data layers
• No Security, No Persistence, No EJB Analogue
• but Rich Front-End and Easier development
  environment!

3
The Chasm
.NET Thin Clients
? ? ? ?
J2EE and CORBA Middleware
.NET Thick Clients
4
Web Services as a Solution
.NET Thin Clients

• Additional infrastructures needed
• Interoperability is not seamless
• Security, Transactions, and Quality-
  of-Services may not be supported
• Poor Performance

J2EE and CORBA Middleware
.NET Thick Clients
5
Bridging as a Solution
.NET Thin Clients

• Additional infrastructures needed
• Changes may be required to middleware
• Security, Transactions, and Quality-
  of-Services may not be supported
• Poor Performance

J2EE and CORBA Middleware
.NET Thick Clients
6
The Janeva Solution
.NET Thin Clients
Janeva
Janeva
Janeva

• No additional infrastructures needed
• No changes required to back end
• Seamless interoperability
• J2EE and CORBA infrastructures are
• leveraged, including Qualities-of- Service
  features
• High Performance

J2EE and CORBA Middleware
.NET Thick Clients
7
Janeva Solution

• Janeva is VisiBroker for .NET
• Borlands implementation of CORBA infrastructure
  for .NET
• Adhering to (mature) standards on both the client
  and server
• .NET, J2EE, and CORBA
• Seamless interoperability between.NET and J2EE
  CORBA platforms
• Access to fully IIOP compliant J2EE servers
• Access to fully IIOP compliant CORBA ORB's
• Highly performing
• Leveraging efficiencies of IIOP vs. SOAP
• Enterprise Quality of Service (IIOP based)
• Load Balancing, Fault Tolerance, Transactions,
  Scalability

8
Janeva Solution

• Transactions
• Provide 2-Phase commits across applications
• Security
• Encryption, Authentication, and Authorization
• Stateful Services
• Object References
• Distributed Object Model
• Support for Complex Data Types
• Automated mapping between J2EE and CORBA
• Cross Language Support
• Microsoft Common Language Runtime (CLR)
• C, J, Visual Basic .NET, Visual C .NET
• Any CLR supported language

9
How Janeva Works

• Janeva compilers generate .NET stubs for mapping
  J2EE and CORBA types to .NET types
• The .NET C compiler compiles the generated
  stubs and include them in the compiled assembly
• Janeva runtime is embedded directly into the
  deployed application

10
Janeva Environment
EJB1
EJB2
Obj1
Obj2
C
Basic
C
C
Basic
JScript
J2EE Server
CORBA
Janeva Stubs
Janeva Stubs
ASP.NET Runtime
.NET Runtime
RMI-IIOP
IDL-IIOP
Janeva Runtime
Janeva Runtime
IIOP

• J2EE based compiler
• .Net Remoting stubs from Java RMI interfaces
• CORBA based compiler
• .Net Remoting stubs from IDL
• .NET Assemblies
• Packaged from generated stubs
• Stubs target Microsofts Common Type System (CTS)

11
Janeva Environment
J2EE Server Environment
Naming Service
C Client
Transaction Service
Ease-of-Use Layer
Assembly
Raw Stub Layer
EJB Container
.NET Runtime
Home Objects
IIOP
Janeva Runtime
Remote Objects

• Hiding the Complexities
• Ease-of-Use Abstraction (OO wrappers)
• Map J2EE and CORBA frameworks to .Net
• Tight integration with .NET based IDEs such as
  Visual Studio for .NET and C Builder

12
Janeva Connectivity Choices
13
Accessing J2EE from .NETwith Borland
JanevaDemo Svetlin NakovSoftware Development
Consultant Sofia University St. Kliment
Ohridski www.nakov.com
14
Borland JanevaQuestions?