System and method for communicating data

• US 6,940,870 B2
• Filed: 07/16/2001
• Issued: 09/06/2005
• Est. Priority Date: 12/30/1997
• Status: Expired due to Fees

• Current Assignee: Falk Integrated Technologies, Inc.
• Original Assignee: Falk Integrated Technologies, Inc.
• Inventors: Hamlin, James K.
• Primary Examiner(s): Pham, Chi
• Assistant Examiner(s): Boakye, Alexander O.
• Application Number:
  US09/906,222
• Publication Number:
  US 20010040897A1
• Time in Patent Office: 1,513 Days
• Field of Search: 370/466, 370/338, 370/397, 370/408, 370/410, 370/465, 370/467, 709/223, 709/230, 709/201, 714/800
• US Class Current: 370/466
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The present invention provides a system and method for communicating data between a source application process and one or more destination application processes. This system and method perform conversion and routing functions which require only a single conversion of all outbound transmissions regardless of the variety of destinations, and only a single conversion of all inbound transmissions regardless of the variety of sources. The functions also enable changes, additions, and deletions of sources and destinations of transmissions to be made without modification of a source or destination application process and without taking a source or destination application process off-line. The functions further enable this system and method to be implemented in virtually any enterprise architecture without requiring that each processing system of the architecture be custom built. These conversion and routing functions are performed by first receiving data to be transmitted in a source format from a source application. This data are then converted from the source format to a standard format. Next, one or more destinations are identified in a database using a transaction type corresponding to the data and/or the address of the source application. After identifying the one or more destinations, a copy of the data is transmitted to each and the data are then converted from the standard format to a destination format. Lastly, this converted data are passed to the destination process.

Claims

1. A method of communicating data from a source process to a destination process, the method comprising:

receiving the data in a source format from the source process;

converting the data from the source format to a standard format;

transmitting the data in the standard format to a destination address that is associated with the destination process;

receiving the data transmitted in the standard format at the destination address;

converting said data from the standard format to a destination format;

transmitting the data in the destination format to the destination process;

generating an acknowledgment of receipt of the data when the data is received at the destination process; and

notifying a user of an error upon an occurrence of at least one of a specified number of other transmission attempts and an absence of the acknowledgment of receipt within a given time period.

2. The method of claim 1, wherein the communication data is of a known data type.

3. The method of claim 1, further comprising:

determining the destination address based upon a source address associated with the source process after receiving the data in the source format from the source process.

4. A machine readable medium encoded with machine readable instructions for performing a method of communicating data of a known data type from a source process to a destination process, said method comprising:

receiving said data in a source format from said source process;

converting said data from said source format to a standard format;

determining a destination address that is associated with said destination process based upon at least one of said known data type and a source address that is associated with said source process;

transmitting said data in said standard format with said destination address;

receiving said data transmitted in said standard format at said destination address;

converting said data in said standard format to a destination format;

transmitting said data in said destination format to said destination process;

prior to said receiving of said data in said source format, defining at least one of said known data type, said source address, said source format, said standard format, said destination format, and a relationship between said destination address and said at least one of said known data type and said source address, wherein said relationship is defined by accepting user input that defines said relationship between said destination address and said at least one of said known data type and said source address;

said determining using said relationship in determining said destination address; and

said relationship relating said destination address to both said known data type and said source address.

5. The machine readable medium of claim 4, said method further comprising:

generating an acknowledgment of receipt of said data when said data transmitted in said destination format is received at said destination process; and

notifying a user of an error upon an occurrence of at least one of a specified number of other transmission attempts and an absence of said acknowledgment of receipt within a given time period.

6. The machine readable medium of claim 4, wherein each of said source format, said standard format, and said destination format are different.

7. The machine readable medium of claim 4, wherein:

said source format and said destination format are identical; and

said source format and said destination format are different from said standard format.

8. The machine readable medium of claim 4, wherein said defining comprises accepting user input that defines said source address of said source process.

9. The machine readable medium of claim 4, wherein said defining comprises accepting user input that defines said source format of said data.

10. The machine readable medium of claim 4, wherein said defining comprises accepting user input that defines said destination format of said data.

11. The machine readable medium of claim 4, wherein said converting of said data from said standard format to said destination format comprises selecting said destination format from a plurality of available destination formats based upon said known data type of said data.

12. The machine readable medium of claim 4, wherein said converting of said data from said standard format to said destination format comprises selecting said destination format from a plurality of available destination formats based upon said destination address transmitted with said data in said standard format.

13. A machine readable medium encoded with machine readable instructions for performing a method of communicating data of a known data type from a source process to a destination process, said method comprising:

receiving said data in a source format from said source process;

converting said data from said source format to a standard format;

determining a destination address that is associated with said destination process based upon at least one of said known data type and a source address that is associated with said source process;

transmitting said data in said standard format with said destination address;

receiving said data transmitted in said standard format at said destination address;

converting said data in said standard format to a destination format;

transmitting said data in said destination format to said destination process;

prior to said receiving of said data in said source format, defining at least one of said known data type, said source address, said source format, said standard format, said destination format, and a relationship between said destination address and said at least one of said known data type and said source address, wherein said relationship is defined by accepting user input that defines said relationship between said destination address and said at least one of said known data type and said source address;

said determining using said relationship in determining said destination address; and

said relationship relating said destination address to said source address without relating said destination address to said known data type.

14. A machine readable medium encoded with machine readable instructions for performing a method of communicating data of a known data type from a source process to a destination process, said method comprising:

receiving said data in a source format from said source process;

converting said data from said source format to a standard format;

determining a destination address that is associated with said destination process based upon at least one of said known data type and a source address that is associated with said source process;

transmitting said data in said standard format with said destination address;

receiving said data transmitted in said standard format at said destination address;

converting said data in said standard format to a destination format;

transmitting said data in said destination format to said destination process;

prior to said receiving of said data in said source format, defining at least one of said known data type, said source address, said source format, said standard format, said destination format, and a relationship between said destination address and said at least one of said known data type and said source address, wherein said relationship is defined by accepting user input that defines said relationship between said destination address and said at least one of said known data type and said source address;

said determining using said relationship in determining said destination address; and

said relationship relating said destination address to said known data type without relating said destination address to said source address.

15. A system for communicating data of a known data type from a source process to a destination process, the system comprising:

means for receiving said data in a source format from said source process;

means for converting said data from said source format to a standard format;

means for determining a destination address that is associated with said destination process based upon at least one of said known data type and a source address that is associated with said source process;

means for transmitting said data in said standard format with said destination address;

means for receiving said data transmitted in said standard format at said destination address;

means for converting said data in said standard format to a destination format;

means for transmitting said data in said destination format to said destination process;

means for generating an acknowledgment of receipt of said data when said data transmitted by said destination transmitter is received at said destination process; and

means for notifying a user of an error upon an occurrence of at least one of a specified number of other transmission attempts and an absence of said acknowledgment of receipt within a given time period.

16. The system of claim 15, wherein each of said source format, said standard format, and said destination format are different.

17. The system of claim 15, wherein:

said source format and said destination format are identical; and

said source format and said destination format are different from said standard format.

18. The system of claim 15, further comprising means for defining at least one of said known data type, said source address, said standard format, said destination format, and a relationship between said destination address and said at least one of said known data type and said source address prior to said data in said source format being received by said source receiver.

19. The system of claim 18, wherein said means for defining at least one of known data type accepts user input that defines said known data type of said data.

20. The system of claim 18, wherein said means for defining at least one of known data type accepts user input that defines said source address of said source process.

21. The system of claim 18, wherein said means for defining at least one of known data type accepts user input that defines said source format of said data.

22. The system of claim 18, wherein said means for defining at least one of known data type accepts user input that defines said standard format of said data.

23. The system of claim 18, wherein said means for defining at least one of known data type accepts user input that defines said destination format of said data.

24. The system of claim 18, wherein said wherein said means for defining at least one of known data type accepts user input that defines said relationship between said destination address and said at least one of said known data type and said source address.

25. The system of claim 18, wherein:

said addressing mechanism uses said relationship in determining said destination address; and

said relationship relates said destination address to both said known data type and said source address.

26. The system of claim 18, wherein:

said means for determining a destination address uses said relationship in determining said destination address; and

said relationship relates said destination address to said source address without relating said destination address to said known data type.

27. The system of claim 18, wherein:

said means for determining a destination address uses said relationship in determining said destination address; and

said relationship relates said destination address to said known data type without relating said destination address to said source address.

28. The system of claim 15, wherein said means for converting said data comprises means for selecting said destination format from a plurality of available destination formats based upon said known data type of said data.

29. The system of claim 15, wherein said means for converting said data comprises means for selecting said destination format from a plurality of available destination formats based upon said destination address transmitted with said data in said standard format.

30. A machine readable medium encoded with machine readable instructions for performing a method of communicating data of a known data type from a source process to a destination process, said method comprising:

receiving said data in a source format from said source process;

converting said data from said source format to a standard format;

determining a destination address that is associated with said destination process based upon at least one of said known data type and a source address that is associated with said source process;

transmitting said data in said standard format with said destination address;

receiving said data transmitted in said standard format at said destination address;

converting said data in said standard format to a destination format;

transmitting said data in said destination format to said destination process; and

prior to said receiving of said data in said source format, defining at least one of said known data type, said source address, said source format, said standard format, said destination format, and a relationship between said destination address and said at least one of said known data type and said source address,

wherein said determining uses said relationship in determining said destination address, and said relationship relates said destination address to both said known data type and said source address.

31. The machine readable medium of claim 30, said method further comprising:

when said data transmitted in said destination format is received at said destination process, generating an acknowledgment of receipt of said data; and

notifying a user of an error upon an occurrence of at least one of a specified number of other transmission attempts and an absence of said acknowledgment of receipt within a given time period.

32. The machine readable medium of claim 30, wherein each of said source format, said standard format, and said destination format are different.

33. The machine readable medium of claim 30, wherein:

said source format and said destination format are identical; and

said source format and said destination format are different from said standard format.

34. The machine readable medium of claim 30, wherein said defining comprises accepting user input that defines said known data type of said data.

35. The machine readable medium of claim 30, wherein said defining comprises accepting user input that defines said source address of said source process.

36. The machine readable medium of claim 30, wherein said defining comprises accepting user input that defines said source format of said data.

37. The machine readable medium claim 30, wherein said defining comprises accepting user input that defines said standard format of said data.

38. The machine readable medium claim 30, wherein said defining comprises accepting user input that defines said destination format of said data.

39. The machine readable medium of claim 30, wherein said converting of said data from said standard format to said destination format comprises selecting said destination format from a plurality of available destination formats based upon said known data type of said data.

40. The machine readable medium of claim 30, wherein said converting of said data from said standard format to said destination format comprises selecting said destination format from a plurality of available destination formats based upon said destination address transmitted with said data in said standard format.

41. A machine readable medium encoded with machine readable instructions for performing a method of communicating data of a known data type from a source process to a destination process, said method comprising:

receiving said data in a source format from said source process;

converting said data from said source format to a standard format;

determining a destination address that is associated with said destination process based upon at least one of said known data type and a source address that is associated with said source process;

transmitting said data in said standard format with said destination address;

receiving said data transmitted in said standard format at said destination address;

converting said data in said standard format to a destination format;

transmitting said data in said destination format to said destination process; and

prior to said receiving of said data in said source format, defining at least one of said known data type, said source address, said source format, said standard format, said destination format, and a relationship between said destination address and said at least one of said known data type and said source address,

wherein said determining uses said relationship in determining said destination address, and said relationship relates said destination address to said source address without relating said destination address to said known data type.

42. The machine readable medium of claim 41, said method further comprising:

generating an acknowledgment of receipt of said data when said data transmitted in said destination format is received at said destination process; and

notifying a user of an error upon an occurrence of at least one of a specified number of other transmission attempts and an absence of said acknowledgment of receipt within a given time period.

43. The machine readable medium of claim 41, wherein each of said source format, said standard format, and said destination format are different.

44. The machine readable medium of claim 41, wherein:

said source format and said destination format are identical; and

said source format and said destination format are different from said standard format.

45. The machine readable medium of claim 41, wherein said defining comprises accepting user input that defines said known data type of said data.

46. The machine readable medium of claim 41, wherein said defining comprises accepting user input that defines said source address of said source process.

47. The machine readable medium of claim 41, wherein said defining comprises accepting user input that defines said source format of said data.

48. The machine readable medium of claim 41, wherein said defining comprises accepting user input that defines said standard format of said data.

49. The machine readable medium of claim 41, wherein said defining comprises accepting user input that defines said destination format of said data.

50. The machine readable medium of claim 41, wherein said converting of said data from said standard format to said destination format comprises selecting said destination format from a plurality of available destination formats based upon said known data type of said data.

51. The machine readable medium of claim 41, wherein said converting of said data from said standard format to said destination format comprises selecting said destination format from a plurality of available destination formats based upon said destination address transmitted with said data in said standard format.

52. A machine readable medium encoded with machine readable instructions for performing a method of communicating data of a known data type from a source process to a destination process, said method comprising:

receiving said data in a source format from said source process;

converting said data from said source format to a standard format;

determining a destination address that is associated with said destination process based upon at least one of said known data type and a source address that is associated with said source process;

transmitting said data in said standard format with said destination address;

receiving said data transmitted in said standard format at said destination address;

converting said data in said standard format to a destination format;

transmitting said data in said destination format to said destination process; and

prior to said receiving of said data in said source format, defining at least one of said known data type, said source address, said source format, said standard format, said destination format, and a relationship between said destination address and said at least one of said known data type and said source address,

wherein said determining uses said relationship in determining said destination address, and said relationship relates said destination address to said known data type without relating said destination address to said source address.

53. The machine readable medium of claim 52, said method further comprising:

when said data transmitted in said destination format is received at said destination process, generating an acknowledgment of receipt of said data; and

notifying a user of an error upon an occurrence of at least one of a specified number of other transmission attempts and an absence of said acknowledgment of receipt within a given time period.

54. The machine readable medium of claim 52, wherein each of said source format, said standard format, and said destination format are different.

55. The machine readable medium of claim 52, wherein:

said source format and said destination format are identical; and

said source format and said destination format are different from said standard format.

56. The machine readable medium of claim 52, wherein said defining comprises accepting user input that defines said known data type of said data.

57. The machine readable medium of claim 52, wherein said defining comprises accepting user input that defines said source address of said source process.

58. The machine readable medium of claim 52, wherein said defining comprises accepting user input that defines said source format of said data.

59. The machine readable medium of claim 52, wherein said defining comprises accepting user input that defines said standard format of said data.

60. The machine readable medium of claim 52, wherein said defining comprises accepting user input that defines said destination format of said data.

61. The machine readable medium of claim 52, wherein said converting of said data from said standard format to said destination format comprises selecting said destination format from a plurality of available destination formats based upon said known data type of said data.

62. The machine readable medium of claim 52, wherein said converting of said data from said standard format to said destination format comprises selecting said destination format from a plurality of available destination formats based upon said destination address transmitted with said data in said standard format.

63. A system for communicating data of a known data type from a source process to a destination process, the system comprising:

means for receiving said data in a source format from said source process;

means for converting said data from said source format to a standard format;

means for determining a destination address that is associated with said destination process based upon at least one of said known data type and a source address that is associated with said source process;

means for transmitting said data in said standard format with said destination address;

means for receiving said data transmitted in said standard format at said destination address;

means for converting said data in said standard format to a destination format;

means for transmitting said data in said destination format to said destination process; and

means for defining at least one of said known data type, said source address, said standard format, said destination format, and a relationship between said destination address and said at least one of said known data type and said source address prior to said data in said source format being received by said source receiver.

64. The system of claim 63, further comprising:

means for generating an acknowledgment of receipt of said data when said data transmitted by said destination transmitter is received at said destination process; and

means for notifying a user of an error upon an occurrence of at least one of a specified number of other transmission attempts and an absence of said acknowledgment of receipt within a given time period.

65. The system of claim 63, wherein each of said source format, said standard format, and said destination format are different.

66. The system of claim 63, wherein:

said source format and said destination format are identical; and

said source format and said destination format are different from said standard format.

67. The system of claim 63, wherein said means for defining data accepts user input that defines said known data type of said data.

68. The system of claim 63, wherein said means for defining data accepts user input that defines said source address of said source process.

69. The system of claim 63, wherein said means for defining data accepts user input that defines said source format of said data.

70. The system of claim 63, wherein said means for defining data accepts user input that defines said standard format of said data.

71. The system of claim 63, wherein said means for defining data accepts user input that defines said destination format of said data.

72. The system of claim 63, wherein said means for defining data accepts user input that defines said relationship between said destination address and said at least one of said known data type and said source address.

73. The system of claim 63, wherein:

said means for determining said destination address uses said relationship in determining said destination address; and

said relationship relates said destination address to both said known data type and said source address.

74. The system of claim 63, wherein:

said means for determining said destination address uses said relationship in determining said destination address; and

said relationship relates said destination address to said source address without relating said destination address to said known data type.

75. The system of claim 63, wherein:

said means for determining said destination address uses said relationship in determining said destination address; and

said relationship relates said destination address to said known data type without relating said destination address to said source address.

76. The system of claim 63, wherein said means for converting comprises a selecting mechanism that selects said destination format from a plurality of available destination formats based upon said known data type of said data.

77. The system of claim 63, wherein said means for converting comprises a selecting mechanism that selects said destination format from a plurality of available destination formats based upon said destination address transmitted with said data in said standard format.

78. A machine readable medium encoded with machine readable instructions for performing a method of communicating data of a known data type from a source process to a destination process, said method comprising:

receiving the data in a source format from the source process;

converting the data from the source format to a standard format;

transmitting the data in the standard format to a destination address that is associated with the destination process;

receiving the data transmitted in the standard format at the destination address;

converting said data from the standard format to a destination format;

transmitting the data in the destination format to the destination process;

generating an acknowledgment of receipt of the data when the data is received at the destination process;

notifying a user of an error upon an occurrence of at least one of a specified number of other transmission attempts and an absence of the acknowledgment of receipt within a given time period;

identifying the data type of the transmitted data after receiving the data in the source format from the source process; and

determining the destination address based upon the identified data type of the transmitted data,

wherein the communicated data is of a known data type.

79. A machine readable medium encoded with machine readable instructions for performing a method of communicating data of a known data type from a source process to a destination process, said method comprising:

receiving the data in a source format from the source process;

converting the data from the source format to a standard format;

transmitting the data in the standard format to a destination address that is associated with the destination process;

receiving the data transmitted in the standard format at the destination address;

converting said data from the standard format to a destination format;

transmitting the data in the destination format to the destination process;

generating an acknowledgment of receipt of the data when the data is received at the destination process;

notifying a user of an error upon an occurrence of at least one of a specified number of other transmission attempts and an absence of the acknowledgment of receipt within a given time period;

identifying the data type of the transmitted data after receiving the data in the source format from the source process; and

determining the destination address based upon the identified data type of the transmitted data and a source address associated with the source process,

wherein the communicated data is of a known data type.

80. A machine readable medium encoded with machine readable instructions for performing a method of communicating data of a known data type from a source process to a destination process, said method comprising:

accepting user input that defines a relationship between a destination address that is associated with the destination process and at least one of the known data type and a source address that is associated with the source process;

receiving the data in a source format from the source process;

converting the data from the source format to a standard format;

determining the destination address based upon the defined relationship after receiving the data in the source format from the source process;

transmitting the data in the standard format to the destination address;

receiving the data transmitted in the standard format at the destination address;

converting the data in the standard format to a destination format; and

transmitting the data in the destination format to the destination process.

81. The machine readable medium of claim 80, said method further comprising:

defining the known data type, the source address, the source format, the standard format, and the destination format, prior to receiving the data in the source format.

82. The machine readable medium of claim 81, wherein the step of defining comprises accepting user input that defines the known data type, the source address, the source format, the standard format, and the destination format.

83. The machine readable medium of claim 80, wherein the step of converting the data from the standard format to the destination format comprises selecting the destination format from a plurality of available destination formats based solely upon the known data type.

84. The machine readable medium of claim 80, wherein:

the data is transmitted in the standard format with the destination address; and

the step of converting the data from the standard format to the destination format includes selecting the destination format from a plurality of available destination formats based upon the destination address transmitted with the data in the standard format.

85. A machine readable medium encoded with machine readable instructions for performing a method of communicating data from a source process to a destination, said method comprising:

receiving the data in a source format from the source process;

converting the data from the source format to a standard format;

transmitting the data in the standard format to a destination address that is associated with the destination process;

receiving the data transmitted in the standard format at the destination address;

converting said data from the standard format to a destination format;

transmitting the data in the destination format to the destination process;

generating an acknowledgment of receipt of the data when the data is received at the destination process; and

notifying a user of an error upon an occurrence of at least one of a specified number of other transmission attempts and an absence of the acknowledgment of receipt within a given time period.

86. The machine readable medium of claim 85, wherein the communication data is of a known data type.

87. The machine readable medium of claim 85, said method further comprising:

determining the destination address based upon a source address associated with the source process after receiving the data in the source format from the source process.

88. A method of communicating data of a known type from a source process to a destination process, the method comprising:

accepting input that defines a relationship between a destination address that is associated with the destination process and at least one of the known data type and a source address that is associated with the source process;

converting the data from the source format to a standard format; and

determining the destination address based upon the defined relationship.

89. The method of claim 88 further comprising:

generating an acknowledgment of receipt of the data when the data is received at the destination process, wherein the destination process is associated with the destination address.

90. The method of claim 88 further comprising:

receiving the data in the source format from the source process; and

prior to receiving the data in the source format, defining the known data type, the source address, the source format, and the standard format.

91. The method of claim 88, further comprising:

converting the data in the standard format to a destination format, wherein the step of converting the data from the standard format to the destination format comprises selecting the destination format from a plurality of available destination formats based solely upon the known data type.

92. The method of claim 88, further comprising:

converting the data in the standard format to a destination format, wherein the data is transmitted in the standard format with the destination address and the step of converting the data from the standard format to the destination format includes selecting the destination format from a plurality of available destination formats based upon the destination address transmitted with the data in the standard format.

93. The method of claim 88, further comprising:

creating a copy of the data in the standard format; and

transmitting the copy to the destination address and at least one different destination address.

94. The method of claim 88, further comprising:

identifying the destination process from a list in a configuration database.

95. The method of claim 88, further comprising:

converting the data in the standard format to a destination format; and

identifying the destination process as receiving data of the known data type from a list in a configuration database.

96. The method of claim 88, further comprising:

converting the data in the standard format to a destination format;

identifying the destination process as receiving data of the known data type from a list in a configuration database;

identifying at least one different destination process as receiving data of the known data type from a list in the configuration database; and

transmitting the standard format to the destination process and the at least one different destination process.

97. The method of claim 88, further comprising:

converting the data in the standard format to a destination format; and

identifying the destination process from a list in a configuration database, wherein the identification is performed by determining which destination processes listed in the database are indicated as receiving data of the source process.

98. The method of claim 88, further comprising:

converting the data in the standard format to a destination format; and

identifying the destination process as receiving data of the source process from a list in a configuration database;

identifying at least one different destination process as receiving data of the source process; and

transmitting the standard format to the destination process and the at least one different destination process.

99. The method of claim 88, further comprising:

creating at least one copy or the data in the standard format;

adding information identifying the destination process to the copy of the data in the standard format; and

transmitting the at least one copies to at least one different destination addresses associated with the destination process.

100. The method of claim 88 further comprising:

determining at least one different destination address by accessing a configuration database to determine if at least one different destination process associated to the at least one different destination address is receiving data of the source process.

101. The method of claim 88 wherein the standard format is a semantic that is a set of information that is associated with the data.

102. The method of claim 88 wherein the standard format is a semantic that is a set of information that is associated with the data and the semantic includes a label and a set of system-specific requirements for the piece of data.

103. A system for communicating data of a known data type from at least one of a plurality of outbound broker processes to at least one of a plurality of inbound broker processes, the system comprising:

a configuration database that contains a list of the plurality of inbound broker processes, wherein the configuration database is accessible to the plurality of outbound broker processes;

a source format associated to the at least one of the plurality of outbound broker processes, wherein the at least one of the plurality of outbound broker processes converts the data of the source format into a standard format and the at least one of the plurality of outbound broker processes has at least one source address;

a destination format associated to the at least one of a plurality of inbound broker processes, wherein the at least one of the plurality of inbound broker processes converts the data of the standard format into a destination format and the at least one of the plurality of inbound broker processes has at least one destination address; and

a relationship between the at least one destination addresses and the known data type, wherein the at least one destination addresses are determined based upon the defined relationship.

104. The system of claim 103 wherein the destination format is selected from a plurality of available destination formats based solely upon the known data type.

105. The system of claim 103, further comprising

a copy of the data in the standard format wherein the copy is transmitted to at least one of the destination addresses.

106. The system of claim 103, wherein the standard format data is transmitted to the at least one destination addresses.

107. The system of claim 103, further comprising:

at least one copy of the data in the standard format, wherein information related to the inbound broker process is added to the data of the at least one copy.

108. The system of claim 103, further comprising:

at least one copy of the data in the standard format, wherein information related to the inbound broker process is added to the data of the at least one copy and the at least one copy is transmitted to at least one destination address associated with the inbound broker process.

109. The system of claim 103 wherein the standard format is a semantic that is a set of information that is associated with the data.

110. The system of claim 103 wherein the standard format is a semantic that is a set of information that is associated with the data and the semantic includes a label and a set of system-specific requirements for the piece of data.

111. A system for communicating a first data from a source application process to one or more destination application processes running on at least one processing system in a communications network, the system comprising:

a source receiver operable to receive said first data in a source format from said source application process;

a source translator operable to convert said first data from said source format to a standard format;

an addressing process operable to determine a first destination that is associated with a first destination application based on a predefined routing relationship;

a first transmitter operable to transmit said first data in said standard format to said determined first destination;

a first destination receiver operable to receive said first data transmitted in said standard format at said first destination;

a first destination translator operable to convert said first data from said standard format to a first destination format;

a first destination transmitter operable to transmit said first data in said first destination format to said first destination application process; and

a system manager that, prior to said first data in said source format being received by said source receiver, defines a first transaction type corresponding to the content of said first data, and further defines transaction parameters for said first transaction type including said routing relationship specifying a first destination for said first data, by accepting user input entered into a user interface implemented separately from said source and first destination application processes.

112. The system of claim 111, wherein said addressing process is operable to identify said first transaction type corresponding to the content of said first data and to use said routing relationship for said first transaction type in determining said first destination.

113. The system of claim 112, wherein said determined first destination comprises a queue, wherein said queue is accessible by said destination receiver.

114. The system of claim 113, wherein said queue is located on the same processing system as said first transmitter.

115. The system of claim 113, wherein said queue is located on the same processing system as said first destination application.

116. The system of claim 112, wherein said first destination is identified as an IP address.

117. The system of claim 111, wherein said defined transaction parameters for said first transaction type further includes first destination formatting rules that dictate how said first data is converted between said standard format and said first destination format, said defined transaction parameters for said first transaction type further include source formatting rules that dictate how said first data is converted between said source format and said standard format, and said source translator is operable to use said source formatting rules in converting said first data from said source format to said standard format.

118. The system of claim 111, wherein said defined transaction parameters for said first transaction type further include source formatting rules that dictate how said first data is converted between said source format and said standard format.

119. The system of claim 118, wherein said source translator is operable to use said source formatting rules in converting said first data from said source format to said standard format.

120. The system of claim 119, wherein said source translator comprises a selecting application operable to:

identify said first transaction type corresponding to the content of said first data; and

select said source formatting rules from a plurality of available formatting rules based upon said identified first transaction type.

121. The system of claim 111, wherein said defined transaction parameters for said first transaction type further includes first destination formatting rules that dictate how said first data is converted between said standard format and said first destination format.

122. The system of claim 121, wherein said destination translator is operable to use said destination formatting rules in converting said first data from said standard format to said first destination format.

123. The system of claim 122, wherein said destination translator comprises a selecting application operable to:

identify said first transaction type corresponding to the content of said first data; and

select said first destination formatting rules from a plurality of available formatting rules based upon said identified first transaction type.

124. The system of claim 111, further comprising an acknowledgment generator operable to generate an acknowledgment of receipt of said first data based upon predefined receipt acknowledgment criteria.

125. The system of claim 124, wherein said defined transaction parameters for said first transaction type further include receipt acknowledgment criteria.

126. The system of claim 125, wherein said acknowledgment generator is operable to use said defined receipt acknowledgment criteria in generating an acknowledgment of receipt of said first data.

127. The system of claim 126, wherein said receipt acknowledgment criteria dictates that said acknowledgment generator generates an acknowledgment of receipt of said first data when said data transmitted by said destination transmitter is received at said first destination process.

128. The system of claim 111, further comprising an error notifier operable to notify a user of an error based upon predefined error notification criteria.

129. The system of claim 128, wherein said defined transaction parameters for said first transaction type further include error notification criteria.

130. The system of claim 129, wherein said error notifier is operable to use said defined error notification criteria in generating a notification of an error in transmitting said first data.

131. The system of claim 130, wherein said error notification criteria dictates that said error notifier generates an error notification upon an occurrence of a specified number of transmission attempts.

132. The system of claim 130, wherein said error notification criteria dictates that said error notifier generates an error notification upon an absence of an acknowledgment of receipt of said first data by said first destination application process within a given time period.

133. The system of claim 130, wherein said error notification criteria dictates that said error notifier generates an error notification if said first data received at said first destination receiver fails one or more integrity checks.

134. The system of claim 111, wherein said defined transaction parameters for said first transaction type further includes security parameters.

135. The system of claim 134, wherein said first transmitter is operable to encrypt said first data prior to transmission based on said defined security parameters.

136. The system of claim 135, wherein said first destination receiver further comprises a data decrypter operable to decrypt said first data received in an encrypted format.

137. The system of claim 111, wherein said first transmitter is operable to assign a serial number incrementally for each data transmission from said source application process to said first destination process for use in identifying a lost or failed data transmission to said first destination process.

138. The system of claim 111, wherein said first transmitter is operable to assemble said first data in said standard format into a transmission record associated with a communications protocol supported by said communications network prior to transmitting said first data to said first destination.

139. The system of claim 111, further comprising:

a second destination application process;

a second destination receiver;

a second destination translator; and

a second destination transmitter, wherein said system manager is operable to define a routing relationship that specifies a second destination for said first data.

140. The system of claim 139, wherein said addressing process is operable to determine a second destination that is associated with said second destination application process based on said routing relationship.

141. The system of claim 140, wherein said first transmitter is operable to transmit said first data in said standard format to said second destination.

142. The system of claim 141, wherein said second destination receiver is operable to receive said first data transmitted in said standard format at said second destination.

143. The system of claim 142, wherein said second destination translator is operable to convert said first data from said standard format to a second destination format.

144. The system of claim 143, wherein said second destination transmitter is operable to transmit said first data in said second destination format to said second destination application process.

145. The system of claim 144, wherein said system manager is operable to define second destination formatting rules that dictate how said first data is converted between said standard format and said second destination format.

146. The system of claim 145, wherein said second destination translator is operable to use said second destination formatting rules in converting said first data from said standard format to said second destination format.

147. The system of claim 141, wherein said first transmitter is operable to assign a serial number incrementally for each data transmission from said source application process to said second destination application process for use in identifying a lost or failed data transmission to said second destination application process.

148. The system of claim 141, wherein said first transmitter is operable to assemble said first data in said standard format into a transmission record associated with a communications protocol supported by said communications network prior to transmitting said first data to said second destination.

149. The system of claim 111, wherein said system manager is further operable to, by accepting user input entered into said user interface implemented separately from said source and destination application processes, define:

a second transaction type corresponding to the content of second data received from said source application process;

and second transaction parameters for said second transaction type including a routing relationship specifying a destination for said second data.

150. A system for communicating a first data from a source application process to one or more destination application processes running on at least one processing system in a communications network, the system comprising:

a source receiver operable to receive said first data in a source format from said source application process;

a source translator operable to convert said first data from said source format to a standard format;

an addressing process operable to determine a first destination that is associated with a first destination application based on a predefined routing relationship;

a first transmitter operable to transmit said first data in said standard format to said determined first destination;

a first destination receiver operable to receive said first data transmitted in said standard format at said first destination;

a first destination translator operable to convert said first data from said standard format to a first destination format;

a first destination transmitter operable to transmit said first data in said first destination format to said first destination application process; and

a system manager that, prior to said first data in said source format being received by said source receiver, defines a first transaction type associated with said source application process and further defining transaction parameters for said first transaction type, including said routing relationship specifying a first destination for said first data, by accepting user input entered into a user interface implemented separately from said source and first destination application processes.

151. The system of claim 150, wherein said addressing process is operable to identify said first transaction type corresponding to data received from said source application process and to use said routing relationship for said first transaction type in determining said first destination.

152. The system of claim 151, wherein said determined first destination receiver comprises a queue, wherein said queue is accessible by said destination receiver.

153. The system of claim 152, wherein said queue is located on the same processing system as said first transmitter.

154. The system of claim 152, wherein said queue is located on the same processing system as said first destination application.

155. The system of claim 151, wherein said first destination is identified as an IP address.

156. The system of claim 150, wherein said defined transaction parameters for said first transaction type further includes first destination formatting rules that dictate how said first data is converted between said standard format and said first destination format, said defined transaction parameters for said first transaction type further include source formatting rules that dictate how said first data is converted between said source format and said standard format, and said source translator is operable to use said source formatting rules in converting said first data from said source format to said standard format.

157. The system of claim 150, wherein said defined transaction parameters for said first transaction type further include source formatting rules that dictate how said first data is converted between said source format and said standard format.

158. The system of claim 157, wherein said source translator is operable to use said source formatting rules in converting said first data from said source format to said standard format.

159. The system of claim 158, wherein said source translator comprises a selecting application operable to:

identify said first transaction type corresponding to data received from said source application process; and

select said source formatting rules from a plurality of available formatting rules based upon said identified first transaction type.

160. The system of claim 150, wherein said defined transaction parameters for said first transaction type further include first destination formatting rules that dictate how said first data is converted between said standard format and said first destination format.

161. The system of claim 160, wherein said destination translator is operable to use said destination formatting rules in converting said first data from said standard format to said first destination format.

162. The system of claim 161, wherein said destination translator comprises a selecting application operable to:

identify said first transaction type corresponding to data received from said source application process; and

select said first destination formatting rules from a plurality of available formatting rules based upon said identified first transaction type.

163. The system of claim 150, further comprising an acknowledgment generator operable to generate an acknowledgment of receipt of said first data based upon predefined receipt acknowledgment criteria.

164. The system of claim 163, wherein said defined transaction parameters for said first transaction type further include receipt acknowledgment criteria.

165. The system of claim 164, wherein said acknowledgment generator is operable to use said defined receipt acknowledgment criteria in generating an acknowledgment of receipt of said first data.

166. The system of claim 165, wherein said receipt acknowledgment criteria dictates that said acknowledgment generator generate an acknowledgment of receipt of said first data when said data transmitted by said destination transmitter is received at said first destination process.

167. The system of claim 150, further comprising an error notifier operable to notify a user of an error based upon predefined error notification criteria.

168. The system of claim 167, wherein said defined transaction parameters for said first transaction type further include error notification criteria.

169. The system of claim 168, wherein said error notifier is operable to use said defined error notification criteria in generating a notification of an error in transmitting said first data.

170. The system of claim 169, wherein said error notification criteria dictates that said error notifier generate an error notification upon an occurrence of a specified number of transmission attempts.

171. The system of claim 169, wherein said error notification criteria dictates that said error notifier generate an error notification upon an absence of an acknowledgment of receipt of said first data by said first destination application process within a given time period.

172. The system of claim 169, wherein said error notification criteria dictates that said error notifier generate an error notification if said first data received at said first destination receiver fails one or more integrity checks.

173. The system of claim 150, wherein said defined transaction parameters for said first transaction type further include security parameters.

174. The system of claim 173, wherein said first transmitter is operable to encrypt said first data prior to transmission based on said defined security parameters.

175. The system of claim 174, wherein said first destination receiver further comprises a data decrypter operable to decrypt said first data received in an encrypted format.

176. The system of claim 150, wherein said first transmitter is operable to assign a serial number incrementally for each data transmission from said source application process to said first destination process for use in identifying a lost or failed data transmission to said first destination process.

177. The system of claim 150, wherein said first transmitter is operable to assemble said first data in said standard format into a transmission record associated with a communications protocol supported by said communications network prior to transmitting said first data to said first destination.

178. The system of claim 150, further comprising a second destination application process, a second destination receiver, a second destination translator, and a second destination transmitter, and wherein said system manager is operable to define a routing relationship that specifies a second destination for said first data.

179. The system of claim 178, wherein said addressing process is operable to determine a second destination that is associated with said second destination application process based on said routing relationship.

180. The system of claim 179, wherein said first transmitter is operable to transmit said first data in said standard format to said second destination.

181. The system of claim 180, wherein said second destination receiver is operable to receive said first data transmitted in said standard format at said second destination.

182. The system of claim 181, wherein said second destination translator is operable to convert said first data from said standard format to a second destination format.

183. The system of claim 182, wherein said second destination transmitter is operable to transmit said first data in said second destination format to said second destination application process.

184. The system of claim 183, wherein said system manager is operable to define second destination formatting rules that dictate how said first data is converted between said standard format and said second destination format.

185. The system of claim 184, wherein said second destination translator is operable to use said second destination formatting rules in converting said first data from said standard format to said second destination format.

186. The system of claim 180, wherein said first transmitter is operable to assign a serial number incrementally for each data transmission from said source application process to said second destination process for use in identifying a lost or failed data transmission to said second destination process.

187. The system of claim 180, wherein said first transmitter is operable to assemble said first data in said standard format into a transmission record associated with a communications protocol supported by said communications network prior to transmitting said first data to said second destination.

188. The system of claim 150 further comprising a second source application process and wherein said system manager is further operable to, by accepting user input entered into said user interface implemented separately from said source and destination application processes, define:

a second transaction type corresponding to second data received from said second source application process; and

second transaction parameters for said second transaction type including a routing relationship specifying a destination for said second data.

189. A method for communicating a first data from a source application process to one or more destination processes running on at least one processing system in a communications network, the method comprising:

receiving, at a source receiver, said first data in a source format from said source application process;

converting, at a source translator, said first data from said source format to a standard format;

determining, at an addressing process, a first destination that is associated with a first destination application based on a predefined routing relationship;

transmitting, at a first transmitter, said first data in said standard format to said determined first destination;

receiving, at a first destination receiver, said first data transmitted in said standard format at said first destination;

converting, at a first destination translator, said first data from said standard format to a first destination format;

transmitting, at a first destination transmitter, said first data in said first destination format to said first destination application process;

defining, at a system manager, prior to said first data in said source format being received by said source receiver, a first transaction type corresponding to the content of said first data; and

defining, at said system manager, transaction parameters for said first transaction type including said routing relationship specifying a first destination for said first data, by accepting user input entered into a user interface implemented separately from said source and first destination application processes.

190. The method of claim 189, further comprising:

identifying, at said addressing process, said first transaction type corresponding to the content of said first data; and

using said routing relationship for said first transaction type in determining said first destination.

191. The method of claim 190, wherein said determining said first destination comprises identifying a queue accessible by said destination receiver.

192. The method of claim 191, wherein said queue is located on the same processing system as said first transmitter.

193. The method of claim 191, wherein said queue is located on the same processing system as said first destination application.

194. The method of claim 190, further comprising identifying said first destination as an IP address.

195. The method of claim 189, wherein said defined transaction parameters for said first transaction type further includes first destination formatting rules that dictate how said first data is converted between said standard format and said first destination format, said defined transaction parameters for said first transaction type further include source formatting rules that dictate how said first data is converted between said source format and said standard format, and said source translator is operable to use said source formatting rules in converting said first data from said source format to said standard format.

196. The method of claim 189, wherein said defined transaction parameters for said first transaction type further include source formatting rules that dictate how said first data is converted between said source format and said standard format.

197. The method of claim 196, further comprising using, at said source translator, said source formatting rules to convert said first data from said source format to said standard format.

198. The method of claim 197, further comprising:

identifying, at a selecting application, said first transaction type corresponding to the content of said first data, wherein said source translator comprises said selecting application; and

selecting, at said selecting application, said source formatting rules from a plurality of available formatting rules based upon said identified first transaction type.

199. The method of claim 189, further comprising including, for said defined transaction parameters for said first transaction type, first destination formatting rules that dictate how said first data is converted between said standard format and said first destination format.

200. The method of claim 199, further comprising using, at said destination translator, said destination formatting rules in converting said first data from said standard format to said first destination format.

201. The method of claim 200, further comprising:

identifying, at a selecting application, said first transaction type corresponding to the content of said first data, wherein said destination translator comprises said selecting application; and

selecting, at said selecting application, said first destination formatting rules from a plurality of available formatting rules based upon said identified first transaction type.

202. The method of claim 189, further comprising generating, at an acknowledgment generator, an acknowledgment of receipt of said first data based upon predefined receipt acknowledgment criteria.

203. The method of claim 202, further comprising including, for said defined transaction parameters for said first transaction type, receipt acknowledgment criteria.

204. The method of claim 203, further comprising using, at said acknowledgment generator, said defined receipt acknowledgment criteria in generating an acknowledgment of receipt of said first data.

205. The method of claim 204, wherein said receipt acknowledgment criteria dictates that said acknowledgment generator generate an acknowledgment of receipt of said first data when said data transmitted by said destination transmitter is received at said first destination process.

206. The method of claim 189, further comprising notifying, through an error notifier, a user of an error based upon predefined error notification criteria.

207. The method of claim 206, further comprising including, for said defined transaction parameters for said first transaction type, error notification criteria.

208. The method of claim 207, further comprising using, at said error notifier, said defined error notification criteria in generating a notification of an error in transmitting said first data.

209. The method of claim 208, wherein said error notification criteria dictates that said error notifier generate an error notification upon an occurrence of a specified number of transmission attempts.

210. The method of claim 208, wherein said error notification criteria dictates that said error notifier generate an error notification upon an absence of an acknowledgment of receipt of said first data by said first destination application process within a given time period.

211. The method of claim 208, wherein said error notification criteria dictates that said error notifier generate an error notification if said first data received at said first destination receiver fails one or more integrity checks.

212. The method of claim 189, further comprising including, for said defined transaction parameters for said first transaction type, security parameters.

213. The method of claim 212, further comprising encrypting, at said data transmitter, said first data prior to transmission based on said defined security parameters.

214. The method of claim 212, further comprising decrypting, at a data decrypter, said first data received in an encrypted format, wherein said first destination receiver comprises said data decrypter.

215. The method of claim 189, further comprising assigning, at said first transmitter, a serial number incrementally for each data transmission from said source application process to said first destination process for use in identifying a lost or failed data transmission to said first destination process.

216. The method of claim 189, further comprising assembling, at said first transmitter, said first data in said standard format into a transmission record associated with a communications protocol supported by said communications network prior to said transmitting said first data to said first destination.

217. The method of claim 189, further comprising:

providing a second destination application process;

providing a second destination receiver;

providing a second destination translator; and

providing a second destination transmitter, wherein said system manager defines a routing relationship that specifies a second destination for said first data.

218. The method of claim 217, further comprising determining, at said addressing process, a second destination that is associated with said second destination application process based on said routing relationship.

219. The method of claim 218, further comprising transmitting, at said first transmitter, said first data in said standard format to said second destination.

220. The method of claim 219, further comprising receiving, at said second destination receiver, said first data transmitted in said standard format at said second destination.

221. The method of claim 220, further comprising converting, at said second destination translator, said first data from said standard format to a second destination format.

222. The method of claim 221, further comprising transmitting, at said second destination transmitter, said first data in said second destination format to said second destination application process.

223. The method of claim 222, further comprising defining, at said system manager, second destination formatting rules that dictate how said first data is converted between said standard format and said second destination format.

224. The method of claim 223, further comprising using, at said second destination translator, said second destination formatting rules in converting said first data from said standard format to said second destination format.

225. The method of claim 219, further comprising assigning, at said first transmitter, a serial number incrementally for each data transmission from said source application process to said second destination process for use in identifying a lost or failed data transmission to said second destination process.

226. The method of claim 219, further comprising assembling, at said first transmitter, said first data in said standard format into a transmission record associated with a communications protocol supported by said communications network prior to transmitting said first data to said second destination.

227. The method of claim 189, further comprising defining, at said system manager, a second transaction type corresponding to the content of second data received from said source application process, and second transaction parameters for said second transaction type including a routing relationship specifying a destination for said second data, by accepting user input entered into said user interface implemented separately from said source and destination application processes.

228. A method for communicating first data from a source application process to one or more destination processes running on at least one processing method in a communications network, the method comprising:

receiving, at a source receiver, said first data in a source format from a source application process;

converting, at a source translator, said first data from said source format to a standard format;

determining, at an addressing process, a first destination that is associated with a first destination application based on a predefined routing relationship;

transmitting, at a first transmitter, said first data in said standard format to said determined first destination;

receiving, at a first destination receiver, said first data transmitted in said standard format at said first destination;

converting, at a first destination translator, said first data from said standard format to a first destination format;

transmitting, at a first destination transmitter, said first data in said first destination format to said first destination application process;

defining, at a system manager, prior to said first data in said source format being received by said source receiver, a first transaction type corresponding to data received from said source application process; and

defining, at said system manager, transaction parameters for said first transaction type, including said routing relationship specifying a first destination for said first data, by accepting user input entered into a user interface implemented separately from said source and first destination application processes.

229. The method of claim 228, further comprising:

identifying, at said addressing process, said first transaction type corresponding to data received from said source application process; and

using said routing relationship for said first transaction type in determining said first destination.

230. The method of claim 229, wherein said determined first destination comprises a queue accessible by said destination receiver.

231. The method of claim 230, wherein said queue is located on the same processing method as said first transmitter.

232. The method of claim 230, wherein said queue is located on the same processing method as said first destination application.

233. The method of claim 229, further comprising identifying said first destination as an IP address.

234. The method of claim 228, wherein said defined transaction parameters for said first transaction type further includes first destination formatting rules that dictate how said first data is converted between said standard format and said first destination format, said defined transaction parameters for said first transaction type further include source formatting rules that dictate how said first data is converted between said source format and said standard format, and said source translator is operable to use said source formatting rules in converting said first data from said source format to said standard format.

235. The method of claim 228, wherein said defined transaction parameters for said first transaction type further include source formatting rules that dictate how said first data is converted between said source format and said standard format.

236. The method of claim 235, further comprising using, at said source translator, said source formatting rules in converting said first data from said source format to said standard format.

237. The method of claim 236, further comprising:

identifying, at a selecting application, said first transaction type corresponding to data received from said source application process, wherein said source translator comprises said selecting application; and

selecting said source formatting rules from a plurality of available formatting rules based upon said identified first transaction type.

238. The method of claim 228, wherein said defined transaction parameters for said first transaction type further include first destination formatting rules that dictate how said first data is converted between said standard format and said first destination format.

239. The method of claim 238, further comprising using, at said destination translator, said destination formatting rules in converting said first data from said standard format to said first destination format.

240. The method of claim 239, further comprising:

identify, at a selecting application, said first transaction type corresponding to data received from said source application process, wherein said destination translator comprises said selecting application; and

selecting said first destination formatting rules from a plurality of available formatting rules based upon said identified first transaction type.

241. The method of claim 228, further comprising generating, at an acknowledgment generator, an acknowledgment of receipt of said first data based upon predefined receipt acknowledgment criteria.

242. The method of claim 241, wherein said defined transaction parameters for said first transaction type further include receipt acknowledgment criteria.

243. The method of claim 242, further comprising using, at said acknowledgment generator, said defined receipt acknowledgment criteria in generating an acknowledgment of receipt of said first data.

244. The method of claim 243, wherein said receipt acknowledgment criteria dictates that said acknowledgment generator generate an acknowledgment of receipt of said first data when said data transmitted by said destination transmitter is received at said first destination process.

245. The method of claim 228, further comprising notifying, through an error notifier, a user of an error based upon predefined error notification criteria.

246. The method of claim 245, wherein said defined transaction parameters for said first transaction type further include error notification criteria.

247. The method of claim 246, further comprising using, at said error notifier, said defined error notification criteria in generating a notification of an error in transmitting said first data.

248. The method of claim 247, wherein said error notification criteria dictates that said error notifier generate an error notification upon an occurrence of a specified number of transmission attempts.

250. The method of claim 247, wherein said error notification criteria dictates that said error notifier generates an error notification if said first data received at said first destination receiver fails one or more integrity checks.

251. The method of claim 228, wherein said defined transaction parameters for said first transaction type further include security parameters.

252. The method of claim 251, further comprising encrypting, at said data transmitter, said first data prior to transmission based on said defined security parameters.

253. The method of claim 252, further comprising decrypting, at a data decrypter, said first data received in an encrypted format, wherein said first destination receiver further comprises said data decrypter.

254. The method of claim 228, further comprising assigning, at said first transmitter, a serial number incrementally for each data transmission from said source application process to said first destination process for use in identifying a lost or failed data transmission to said first destination process.

255. The method of claim 228, further comprising assembling, at said first transmitter, said first data in said standard format into a transmission record associated with a communications protocol supported by said communications network prior to said transmitting said first data to said first destination.

256. The method of claim 228, further comprising:

providing a second destination application process;

providing a second destination receiver;

providing a second destination translator; and

providing a second destination transmitter, wherein said system manager is operable to define a routing relationship that specifies a second destination for said for said first data.

257. The method of claim 256, further comprising determining, at said addressing process, a second destination that is associated with said second destination application process based on said routing relationship.

258. The method of claim 257, further comprising transmitting, at said first transmitter, said first data in said standard format to said second destination.

259. The method of claim 258, further comprising receiving, at said second destination receiver, said first data transmitted in said standard format at said second destination.

260. The method of claim 259, further comprising converting, at said second destination translator, said first data from said standard format to a second destination format.

261. The method of claim 260, further comprising transmitting, at said second destination transmitter, said first data in said second destination format to said second destination application process.

262. The method of claim 261, further comprising defining, at said system manager, second destination formatting rules that dictate how said first data is converted between said standard format and said second destination format.

263. The method of claim 262, further comprising using, at said second destination translator, use said second destination formatting rules in converting said first data from said standard format to said second destination format.

264. The method of claim 258, further comprising assigning, at said first transmitter, a serial number incrementally for each data transmission from said source application process to said second destination process for use in identifying a lost or failed data transmission to said second destination process.

265. The method of claim 258, further comprising assembling, at said first transmitter, said first data in said standard format into a transmission record associated with a communications protocol supported by said communications network prior to transmitting said first data to said second destination.

266. The method of claim 228, further comprising providing a second source application process, wherein said system manager is further operable to, by accepting user input entered into said user interface implemented separately from said source and destination application processes, define:

a second transaction type corresponding to second data received from said second source application process; and

second transaction parameters for said second transaction type including a routing relationship specifying a destination for said second data.

249. The method of claim wherein said error notification criteria dictates that said error notifier generates an error notification upon an absence of an acknowledgment of receipt of said first data by said first destination application process within a given time period.

267. A system for communicating a first data from a source application process to one or more destination processes running on at least one processing system in a communications network, the system comprising:

a source receiver operable to receive said first data in a source format from said source application process;

a source translator operable to convert said first data from said source format to a standard format;

an addressing process operable to determine a first destination that is associated with a first destination application based on a predefined routing relationship;

a first transmitter operable to transmit said first data in said standard format to said determined first destination;

a first destination receiver operable to receive said first data transmitted in said standard format at said first destination;

a first destination translator operable to convert said first data from said standard format to a first destination format;

a first destination transmitter operable to transmit said first data in said first destination format to said first destination application process; and

a system manager that, prior to said first data in said source format being received by said source receiver, defines a first transaction type corresponding to the content of said first data and said source application process, and further defines transaction parameters for said first transaction type including said routing relationship specifying a first destination for said first data, by accepting user input entered into a user interface implemented separately from said source and first destination application processes.

268. A method for communicating a first data from a source application process to one or more destination processes running on at least one processing system in a communications network, the method comprising:

providing a source receiver operable to receive said first data in a source format from said source application process;

providing a source translator operable to convert said first data from said source format to a standard format;

providing addressing process operable to determine a first destination that is associated with a first destination application based on a predefined routing relationship;

providing a first transmitter operable to transmit said first data in said standard format to said determined first destination;

providing a first destination receiver operable to receive said first data transmitted in said standard format at said first destination;

providing a first destination translator operable to convert said first data from said standard format to a first destination format;

providing a first destination transmitter operable to transmit said first data in said first destination format to said first destination application process; and

providing a system manager that, prior to said first data in said source format being received by said source receiver, defines a first transaction type corresponding to the content of said first data and to data received from said source application process and further defines transaction parameters for said first transaction type, including said routing relationship specifying a first destination for said first data, by accepting user input entered into a user interface implemented separately from said source and first destination application processes.

269. A management system for setting up a communications network, wherein said management system is operable to:

add a first application process to said communications network;

add a second application process to said communications network;

establish an information broker on one processing system, wherein said information broker is operable to obtain data from said first application process in a first format, said information broker is operable provide said data to said second application process in a second format, and said first and second formats are different;

define a transaction type for said data; and

define transaction parameters for said transaction type that determines where said data is provided in said communications network.

270. The management system of claim 269, wherein said transaction parameters determine that said data is provided to at least said second application process.

271. The management system of claim 269, wherein said first format is a semantic format.

272. The management system of claim 269, wherein said second format is a semantic format.

273. The management system of claim 269, wherein said information broker is further operable to determine said first format as being a generic format or a semantic format.

274. The management system of claim 269, further operable to define a group of semantic formats for use in said communications network.

275. The management system of claim 274, further operable to define said group of semantic formats by an automated process.

276. The management system of claim 274, further operable to define said group of semantic formats through the use of user input entered into a user interface.

277. The management system of claim 274, further operable to determine, by an automated process, whether all of said semantic formats of said group have been defined in said communications network.

278. The management system of claim 269, further operable to define said transaction parameters through the use of user input entered into a user interface.

279. The management system of claim 269, further operable to define said transaction parameters by an automated process.

280. The management system of claim 269, further operable to modify said transaction parameters for said data.

281. The management system of claim 269, wherein said information broker is further operable to convert said data obtained in said first format into a standard format.

282. The management system of claim 281, wherein said information broker is further operable to convert said data in said standard format into said second format.

283. The management system of claim 282, further operable to define said standard format.

284. The management system of claim 269, further operable to add said first and second application processes to said communications network through the use of user input entered into a user interface.

285. The management system of claim 269, further operable to add said first and second application processes to said communications network by an automated process.

286. The management system of claim 269, further operable to modify said transaction parameters.

287. The management system of claim 269, further operable to:

add a third application process to said communications network that provides a second data;

define a second transaction type for said second data;

define second transaction parameters for said second transaction type that determines where said data is provided in said communications network.

288. The management system of claim 287, further operable to:

add a fourth application process to said communications system; and

establish a second information broker, wherein said second information broker is operable to obtain said second data from said third application process in a third format, said information broker is operable to provide said data to said fourth application process in a fourth format, and said third and fourth formats are different.

289. The management system of claim 287, further operable to:

add a fourth application process to said communications system, wherein said information broker is further operable to obtain said second data from said third application process in a third format, said information broker is further operable to provide said data to said fourth application process in a fourth format, and said third and fourth formats are different.

290. The management system of claim 269, further operable to enable said information broker to perform at least one format conversion function on said data in said first format.