Java EE and .NET Interoperability: Integration Strategies, Patterns, and Best Practices

Index

[SYMBOL] [A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W] [X]

Mainsoft's Visual MainWin for Java EE

man-in-the-middle (security threat)

manageability

     in adapter strategy (messaging)

     of asynchronous communication

     of bridging strategy (messaging)

     Enterprise Service Bus

     in QoS (Quality of Service)

     in Web services messaging strategy

managed beans (MBeans)

managed code

managed environment (resource adapters)

management

     .NET Remoting

     agent-based architecture

     benefits of integration technologies

     best practices

     bridging solutions

     CORBA

     example scenario

     in .NET

     interoperability in

     ISO Network Management model

         accounting management

         configuration management

         fault management

         integration strategy comparison

         performance management

         security management

     in Java

     limitations of integration technologies

     Mono

     pitfalls

     platform unification strategy

         benefits of

         example of usage

         ISO Network Management model 2nd

         limitations of

         patterns

     proxy-based architecture

    of transactions [See transactions.]

     Web services management strategy

         commercial solutions

         ISO Network Management model

         WS-Management specification

         WSDM (Web Services Distributed Management)

Management of Web Services (MOWS)

Management Using Web Services (MUWS)

Manufacturing system [See .NET Manufacturing system (asynchronous Web services).]

Mbeans (managed beans)

MDBs (Message Driven Beans) 2nd

message alteration (security threat)

Message Inspector pattern

Message Oriented Middleware (MOM)

message replay (security threat)

Message Transmission Optimization Mechanism (MTOM)

     Web services best practices

messaging [See also JMS (Java Message Service).]

     adapter strategy

         benefits of

         example of usage

         limitations of

         patterns

         scope of

         solution

     bridging strategy

         benefits of

         best practices

         example of usage

         limitations of

         patterns

         Replenish Stock use case

         scope of

         solution

     Enterprise Service Bus

         benefits of

         data routing

         limitation of

         scope of

         solution

     fire-and-forget pattern

     in .NET 2nd

     in .NET Remoting

     in Java

     in Java EE

     Internet e-mail strategy

         benefits of

         example of usage

         limitations of

         scope of

         solution

     MIME versus DIME

     point-to-point pattern

     publish-subscribe pattern

     reliability of

     for transaction interoperability

     Web services messaging strategy

         benefits of

         examples of usage

         limitations of

         patterns

         Replenish Stock use case

         scope of

         solution

messaging platform, interoperability and

messaging technologies

meta-data (.NET security)

micro-tuning

Microsoft .NET Framework [See .NET Framework, basis for.]

Microsoft Intermediate Language (MSIL) 2nd

Microsoft Management Console (MMC)

Microsoft Message Queueing (MSMQ) 2nd

     reliability of

Microsoft Operations Manager (MOM)

migrating [See porting .NET applications to Java EE.]

MIME, DIME versus

MMC (Microsoft Management Console)

MOM (Message Oriented Middleware)

MOM (Microsoft Operations Manager)

monitors (Web services)

Mono framework 2nd

     benefits of

     limitations of

MOWS (Management of Web Services)

MSIL (Microsoft Intermediate Language) 2nd

MSMQ (Microsoft Message Queueing) 2nd

     reliability of

MTOM (Message Transmission Optimization Mechanism)

     Web services best practices

multithreading [See threading.]

MUWS (Management Using Web Services)