Index_N

N

/namespace switch, 238

namespaces, 59

naming proxy classes, 221

ndata namespace, 223

.NET. See also business tier; .NET Framework; .NET remoting; presentation tier

building applications based on, 27–29

components, 5, 18

components in the Business Tier, 12

components in the Presentation tier, 11

configuring the COM+ application on .NET platform, 318–319

Data tier resources for XBikes, 196

defining, 5

diagram of comparison to J2EE, 10

directory services, 34

features compared with J2EE, 45–46

fundamentals for J2EE developers, 18–35

fundamentals of J2EE for .NET developers, 35–44

goal of, 18

installing XBikes on, 317–335

installing XBikes on platform, 318

integrating in the Business tier, 235–260

integrating in the Presentation tier, 203–233

interoperability adapters and initialise method, 215–216

linking Presentation tier to the J2EE Business tier, 205

mapping data types, 62

mapping XSDs and classes in, 60

migrating to, 8

Presentation tier linked to J2EE Business tier, 11

shared databases, 113–114

unifying vision, 18

using WebSphere MQ Classes for, 146–147

vs. J2EE, 17, 18

vs. Java, 36

Web services adapter to address Data Access Logic resource in the .NET Framework Data tier, 199

Web services between the Web and Business tier, 295

.NET Framework

accessing EJB from, 77

accessing JMS Messages from clients, 148

accessing servers from Java, 75

and ADO.NET, 33

architecture, 159–161

architecture and XBikes implementations, 175

asynchronous interoperability adapter, 268

asynchronous interoperability with Java applications, 129

availability, 20

best practice design of application architecture, 160–161

Business and Data tiers with interoperability elements added, 197

business service fa ade in the Business tier, 243

CLR, 20

connecting to WebSphere MQ from, 146–147

creating asynchronous interoperability adapters, 268–269

creating Web services in, 95–96

cross language integration, 22

custom service interfaces for the business service fa ade, 252

data types definition based on an XML Schema, 238–241

distributed and multi-tiered architecture, 159

and EJB, 31

installation choices, 20

investigating, 19–27

and J2EE Application Architecture, 159–175

Java-side component with, 86

key features of, 19

linking types with Java, 78–79

mapping data types to Java data types, 78–79

message consumers, 266–267

resource interoperability adapters, 198–199

resource interoperability factories, 200

sending messages from Java Applications, 152

sending messages to Java Applications, 151–152

service interfaces, 194

service interfaces for the .NET Framework business service fa ade, 242

use case interoperability adapter factory, 195

use case interoperability adapters, 194–195

Web service client in, 98–99

XML configuration file, 196, 200

XMLSerializer in typed DataSets, 239

.NET Framework Business tier

adding to Data tier interoperability, 196–197

and J2EE Web tier with Ja.NET adapters, 297–298

services interfaces of, 194

.NET Framework Data tier

and J2EE Business tier with Ja.NET adapters, 298–299

service interfaces, 198

.NET Framework Presentation tier

adding interoperability to Business tier, 192–196

adding interoperability to Data tier, 196–200

adding to Business tier interoperability, 192–193

and Business tier with interoperability elements added, 193

.NET Framework Web service

between the Business and Data tiers, 328–329

Data Access Logic resource WS service interface in the .NET Framework Data tier, 191

encapsulating the .NET Framework business service fa ade, 241–242

.NET Framework Business tier, 186

.NET Remoting

advantages of, 67

channels, 68–69, 72

comparing to Web services, 108–110

configuration files, 72–73

configuring on Business tier, 323–324

described, 26–27

diagram of typical implementation, 70

hosting objects as ASP.NET components on IIS, 71

implementing, 69–73

.NET Framework Business tier, 194

.NET Framework Data Access Logic resource, 198

on the Presentation tier, 321–322

Remoting calls and DataSet object, 194

understanding, 68–69

using for connectivity, 67–72

vs. SOAP, 81

.NET Remoting adapter

Data Access Logic resource in the .NET Framework Data tier, 199

.NET WS service interface, 195

non-blocking asynchronous calls, 123–125

non-existent data types, 49–50