Interoperability Architecture

The areas of infrastructure that we need to understand interoperability around are:



1.    Networks (Protocols, DNS / Bind, Wireless)

2.    Directory (LDAP, AD, iplanet, NDS, edirectory)

3.    Security (Standards, Kerberos, Certificates, SSO, IRM, Identity, WS-Sec, Federation)


4.    File and Print (Windows, NFS, Novell, LU0, VSAM)

5.    Clients (Apple, Unix, Novell, Win 98, 3270, 5250, Mobile, Office, Browser)

6.    Platform (Virtual Servers, Windows, UNIX, LINUX, Zos, AS400, SUN OS)

Packaged Solutions

7.    Data (DB suppliers, Stored Procs, Data Access, Data Formats)

8.    CRM (SAP, Peoplesoft, Siebel, Great Plains, Reporting, BI)

9.    Messaging and Collaboration (IM, Lotus, Groupwise, Exchange 5.5, Exchange 2000, Portals, Fax)

Custom Solutions

10. Applications (VB, Delphi, COM, NET, Java / JSP, C++, Cobol, WS)

11. TPM’s (ES, MTS, OSI/TP, Tuxedo, J2EE, CICS, IMS)

12. Process (MSMQ, MQSERIES, Tibco RV, Biztalk, Websphere)

Management and Operations Process

13. Deployment and Management (SNMP, WMI, MOM, SMS, Tivoli, CA, HP)

Comments (3)

  1. Steve Cook says:

    Mike – Where does metadata live? Metadata can be about any of this.

  2. mike says:

    As you say metadata is about all of this and should exist in a repository, or more likley a federation of repositories.

  3. mike says:

    So for instance when you are trying to do something like capacity planning which exists for all these layers then you have metadata about that layer (Hardware or networks are the obvious ones). This will be held in a metadata epository for that layer.

    I dont really belive in one humongous repository for everything so the federation / relationships and vaildations between the repositories will be interesting.

Skip to main content