Depending on your integration strategy, you may have to augment management components that are not available with an integration solution. Table 15-2 lists individual ISO management characteristics across different technologies and integration strategies.
Table 15-2. ISO Management Characteristics Across Interoperability Strategies
| Bridging Solution | CORBA-based Bridging | Web services | Mono | Platform Unification |
---|
Fault Management | No Integrated solution | No integrated solution | Integrated through WSDM/MOWS | No integrated solution | Integrated through Java EE |
Configuration Management | No integrated solution | No integrated solution | Integrated through WSDM/MOWS | No integration between Mono and native deployment | Java EE deployment model |
Accounting Management | No integrated solution | No integrated solution | Integrated through WSDM/MOWS | No integrated solution | Supports solutions running on Java EE |
Performance Management | Network component and marshaling impacts performance | CORBA impacts performance | SOAP/HTTP impacts performance, Integrated through WSDM/MOWS | Inferior to .NET and Java [VOGELS] | Near Java EE performance, Java EE metering |
Security Management | Limited integration context to Java | Propagation of .NET security WS-Trust EE, no integrated user management | WS-Security, WS Federation, Cryptographic support | Cross platform ASP.NET Security, | Java EE Security model, Java EE user management |
When to use | Fine-grained interoperability | Fine-grained interoperability | SOA Environments | Platform migration key issue | Performance key issue |
| Intra-firewall applications | Intra-firewall applications | Loosely coupled business architecture | .NET environment key issue | Deployment on Java EE |
| | | | | Development Productivity key issue |
| Binary application interoperability | Binary application interoperability | B2B integration | | Contain interoperability issues at development time |