EAServer 6.1 includes .NET client support, and enables IIOP/IIOPS communication between:
.NET C# clients and EAServer components
PowerBuilder® WinForm applications and EAServer
.NET and J2EE distributed objects
.NET client support includes data marshalling: data from multiple sources is collected, converted to a common format if necessary, and prepared to send over a network.
These components provide .NET client support:
NetCompiler Generates C# stubs and helper classes for EAServer components. To invoke NetCompiler, run:
%DJC_HOME%\bin\netcc.bat [class name] | [ejbjar-name] | [name.jar]
where:
Option |
Description |
---|---|
|
A class that is either an interface or serializable:
If the class name begins with “java” or if the class is a primitive, it is ignored. |
|
An EJB that is deployed in EAServer. NetCompiler generates C# stubs for both the home and remote interfaces. |
|
An EJB JAR that is deployed in EAServer. NetCompiler generates C# stubs for both the home and remote interfaces. |
.NET runtime assemblies Assembly files that provide runtime support to enable C# stubs to communicate with EAServer:
com.sybase.iiop.net.dll – for data marshalling, and for managing connections, SSL, and compression. The next two runtime assemblies depend on this one.
com.sybase.ejb.net.dll – enables invoking EJBs.
com.sybase.jms.net.dll – enables calling JMS.
The .NET runtime assemblies are located in %DJC_HOME%\lib.