Method, system and apparatus for establishing, monitoring, and managing connectivity for communication among heterogeneous systems

• US 20020010803A1
• Filed: 05/24/2001
• Published: 01/24/2002
• Est. Priority Date: 05/25/2000
• Status: Abandoned Application

• Current Assignee: Transact Tools Incorporated
• Original Assignee: Transact Tools Incorporated
• Inventors: Josse, David J., Oberstein, Brien M., Peacock, Robert L., Johnson, Samuel R.
• Application Number:
  US09/864,655
• Publication Number:
  US 20020010803A1
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/022 Multivendor or multi-standard integration
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0686 Additional information in the notification, e.g. enhancement of specific meta-data
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/0823 Errors, e.g. transmission errors
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A method, system and apparatus for establishing, monitoring and managing connectivity for communication among heterogeneous systems, such as in client-server networks having a plurality of systems, wherein the client-server network comprises a server for processing incoming events, an agent resident on at least one of the plurality of networks, and a monitor coupled to the agent, where the monitor handles and displays notifications and enables event handling. The agent remains in communication with the server to facilitate monitoring and error handling by one or more systems connected to the server. The server acts as a message router for forwarding events between one or more agents, and the server further stores events and event actions that flow through the system. Directory services facilitate querying and publishing to a repository or repositories of information to assist counter-parties in establishing connectivity directly with each other.

Claims

1. A method for event communication among networks having a plurality of systems, comprising:

receiving an event signal in a client, said event signal transmitted by an event-generating entity coupled thereto;

obtaining a pre-determined rule associated with said event; and

processing said event in accordance with said pre-determined rule.

2. The method of claim 1, further comprising transmitting said event to a server before said obtaining.

3. The method of claim 1, wherein said event is assigned a priority level in accordance with a pre-determined criterion.

4. The method of claim 3, wherein said processing is performed in accordance with said assigned priority level.

5. The method of claim 1, further comprising converting said event into a well-defined event.

6. The method of claim 5, wherein said event is divided into a plurality of workflow threads that are processed simultaneously.

7. The method of claim 1, further comprising receiving user instructions to configure said pre-determined rule.

8. The method of claim 7, wherein said user instructions are received from a web browser.

9. The method of claim 7, wherein said user instructions are received from a customized application.

10. The method of claim 9, wherein said customized application handles and displays said notifications.

11. The method of claim 7, further comprising accessing a directory service for accessing information and operational preferences for said client.

12. The method of claim 11, further comprising embedding state information into a persistent store on said client for said event.

13. The method of claim 12, further comprising providing a notification service, said notification service allowing access to a notification dispatcher for said transmitting of said notifications.

14. The method of claim 13, wherein said notification dispatcher provides access to at least one mechanism of notification, said notification provided as a result of said processing.

15. The method of claim 14, wherein said mechanism of notification is one of an electronic mail, paging, web browsing and instant messaging.

16. The method of claim 12, wherein said rule is provided as an executable script, said executable script actuating said processing of said well-defined event.

17. The method of claim 12, further comprising creating timers to control the duration of processing of said well-defined events.

18. The method of claim 1, further comprising accessing a directory service for accessing information and operational preferences for said client.

19. The method of claim 1, further comprising embedding state information into a persistent store on said client for said event.

20. The method of claim 1, further comprising providing a notification service, said notification service allowing access to a notification dispatcher for said transmitting of said notifications.

21. The method of claim 20, wherein said notification dispatcher provides access to at least one mechanism of notification, said notification provided as a result of said processing.

22. The method of claim 1, further comprising creating timers to control the duration of processing of said well-defined events.

23. The method of claim 1, wherein said rule is provided as an executable script, said executable script actuating said processing of said well-defined event.

24. The method of claim 2, further comprising transmitting notifications as a result of the processing.

25. The method of claim 2, further comprising:

receiving said event in said server from said client coupled thereto;

obtaining a predetermined rule associated with said event; and

processing said event in accordance with said predetermined rule.

26. The method of claim 25, further comprising transmitting notifications as a result of the processing.

27. The method of claim 25, wherein said rule is provided as an executable script.

28. The method of claim 27, wherein said executable script is stored in a repository associated with said server.

29. The method of claim 28, wherein said server is a distributed server.

30. The method of claim 29, further comprising synchronizing the result of processing said well-defined event within said server.

31. The method of claim 28, further comprising creating a workflow thread for said event.

32. The method of claim 31, wherein said workflow thread is acted upon during said processing in accordance with said executable script associated therewith.

33. The method of claim 27, wherein said executable script is configured to provide customized service during said processing.

34. The method of claim 33, wherein said customized service provides access to a repository that facilitates querying and publishing of information.

35. The method of claim 34, wherein said information assists said systems in managing connectivity therebetween.

36. The method of claim 33, wherein said customized service causes said executable script to embed state information into a persistent storage means for allowing said event to check state across more than one processing paths.

37. The method of claim 36, wherein said customized service further gives said executable script access to schedules to determine flow of processing of said event.

38. The method of claim 37, wherein said customized service further allows said executable script to write messages to an action log of the event and to a storage device.

39. The method of claim 38, wherein said customized service further allows said executable script to create timers to control duration of processing of said events.

40. The method of claim 39, wherein said customized service further allows said executable script access to a notification dispatcher, said notification dispatcher transmitting said notifications.

41. The method of claim 40, further comprising receiving acknowledgement of said dispatched notification.

42. The method of claim 37, wherein said scheduling is controlled by processing an event in a counter party agent.

43. The method of claim 33, wherein said customized service gives said executable script access to schedules to determine flow of processing of said well-defined events.

44. The method of claim 33, wherein said customized service allows said executable script to write messages to an action log of the well-defined event and to a storage device.

45. The method of claim 33, wherein said customized service allows said executable scripts to create timers to control duration of processing of said well-defined events.

46. The method of claim 33, wherein said customized service allows said executable scripts access to a notification dispatcher, said notification dispatcher transmitting said notifications.

47. The method of claim 46, further comprising receiving acknowledgement of said dispatched notification.

48. The method of claim 25, further comprising assigning a priority level to said well-defined event in accordance with a pre-determined criterion.

49. The method of claim 48, further comprising scheduling said well-defined event in accordance with said priority level.

50. The method of claim 49, wherein said processing is performed in accordance with said priority level.

51. The method of claim 1, further comprising assigning a priority level to said well-defined event in accordance with a pre-determined criterion.

52. The method of claim 51, further comprising scheduling said well-defined event in accordance with said priority level.

53. The method of claim 52, wherein said processing is performed in accordance with said priority level.

54. The method of claim 1, wherein an executable script is configured to provide customized service during said processing.

55. The method of claim 54, further comprising creating a workflow thread for said well-defined event.

56. The method of claim 55, wherein said workflow thread is acted upon during said processing in accordance with said executable script associated therewith.

57. The method of claim 1, wherein said rule is provided as an executable script.

58. The method of claim 57, wherein said customized service further allows said executable script access to a notification dispatcher, said notification dispatcher transmitting said notifications.

59. The method of claim 58, wherein said customized service causes said executable script to embed state information into a persistent storage means for allowing said event to check state across more than one processing paths.

60. The method of claim 59, wherein said customized service further gives said executable script access to schedules to determine flow of processing of said events.

61. The method of claim 60, wherein said customized service further allows said executable script to write messages to an action log of the event and to a storage device.

62. The method of claim 61, wherein said customized service further allows said executable script to create timers to control duration of processing of said events.

63. The method of claim 57, further comprising receiving acknowledgement of said dispatched notification.

64. The method of claim 57, wherein said notification is provided by one of an electronic mail, paging, web browsing and instant messaging.

65. A method for event communication among networks having a plurality of systems, comprising:

receiving an event at a server, wherein the event is forwarded to said server from a client coupled thereto;

obtaining event handling scripts from a storage device associated with the server; and

creating a workflow process for processing said event.

66. The method of claim 65, further comprising dispatching a notification based upon the processing of said event.

67. The method of claim 66, further comprising accessing a repository for querying and publishing information between at least two of said plurality of systems.

68. The method of claim 67, wherein said repository provides information for one of defining, handling and processing events in said systems.

69. The method of claim 68, wherein said repository provides information to assist in discovery of information on a potential counter-party.

70. The method of claim 67, further comprising listening for determining presence of events at the server.

71. The method of claim 70, wherein said server is a distributed server, the method further comprising synchronizing a result of processing said event received in said distributed server.

72. The method of claim 71, further comprising loading a handling script for processing the subsection of said event.

73. The method of claim 72, further comprising saving said event received at the server in said storage device, said storage device associated with the server.

74. The method of claim 72, further comprising dispatching said processed events by one of electronic mail, paging devices, web browsers and instant messaging.

75. The method of claim 74, further comprising dispatching notification of said processed event to the client.

76. The method of claim 72, wherein said event is processed in a workflow thread.

77. The method of claim 72, wherein storage device is a database.

78. A method for event communication among networks having a plurality of systems, comprising:

receiving an event at one of said plurality of networks;

retrieving an event handling script for processing said typed event; and

processing said event within said script engine in accordance with a predetermined handling script associated with said event.

79. The method of claim 78, further comprising sending a notification of said event to a server coupled to said client, said notification providing monitoring information for said one of said plurality of networks.

80. The method of claim 79, further comprising dispatching a notification in conformance with a predetermined dispatch policy.

81. The method of claim 80, further comprising converting said event into a well-defined event, wherein said well-defined event facilitates processing of said event in said one of said plurality of networks.

82. The method of claim 78, further comprising checking an event queue for availability of well-defined events, after said receiving.

83. The method of claim 82, further comprising saving said well-defined event to a repository.

84. The method of claim 80, wherein said notification is dispatched by one of electronic mail, paging devices, web browser and instant messaging.

85. A method for event communication among networks having a plurality of systems, comprising:

receiving an event at a first network in said plurality of networks;

processing said event at said first network in accordance with a predetermined handling script associated with said event; and

dispatching a notification in conformance with a predetermined dispatch policy.

86. The method of claim 85, further comprising sending a notification of said event to a server coupled to said client.

87. The method of claim 86, wherein said notification provides monitoring information regarding said first network.

88. A method for event communication among networks having a plurality of systems, comprising:

receiving an event at a first network in said plurality of networks;

transmitting said event to a second network in said plurality of networks;

processing said event at said second network in accordance with a predetermined handling script associated with said event; and

dispatching a notification in conformance with a predetermined dispatch policy.

89. The method of claim 88, wherein said handling script is received from said first network, said handling script customized for processing said event.

90. The method of claim 88, wherein said handling script is received from said second network, said handling script customized for processing said event.

91. A system for event communication among networks having a plurality of systems, comprising:

a server;

an agent resident on one of said plurality of networks, wherein said agent communicates with said server; and

a monitor coupled to said agent, wherein said monitor handles and displays notifications and enables event handling in said agent,

wherein said server further acts as a message router for forwarding events between one or more agents, said agent providing said server with connectivity information, said server further persisting events and event actions that flow through the system.

92. The system of claim 91, wherein said server further comprises:

a server event manager for continuously discovering an event entering said server;

a server workflow engine for processing said event received within the server;

a server workflow manager for controlling and overseeing the processing of said event by the workflow engine;

a server state manager for maintaining state of said event across said server; and

a notification dispatcher for transmitting information of said event through delivery means to one of a user and automated message receiver.

93. The system of claim 92, wherein said server workflow engine comprises:

at least one server workflow thread for allowing division of the workflow into a smaller task, wherein said task can be performed independently; and

a script engine for providing scripted processing of events and actions within said server workflow engine.

94. The system of claim 92, wherein said server further comprises an application program interface for communicating with various messaging protocols.

95. The system of claim 94, wherein said application program interface further allows interaction with client systems.

96. The system of claim 92, wherein said server further comprises a security manager for ensuring that information passed to the server is reliable.

97. The system of claim 96, wherein said server comprises a storage device for saving said event.

98. The system of claim 97, wherein said server comprises a repository for storing information to define, handle and process said event.

99. The system of claim 92, wherein said agent comprises:

an agent event manager for detecting an event entering said agent;

an agent workflow engine for processing event received within said agent;

an agent workflow manager for controlling and overseeing the processing of events by the workflow engine;

an agent state manager for maintaining state of the server across one or more events in the system; and

an agent notification dispatcher for transmitting said events to various delivery means for notifying users of the system.

100. The system of claim 99, wherein said agent further comprises an event application program interface for interfacing with external engines to receive events addressed to said agent.

101. The system of claim 100, wherein said agent further comprises a connection manager for managing connections to said agent.

102. The system of claim 99, wherein said agent workflow engine comprises:

at least one agent workflow thread for allowing division of the workflow into a smaller task, wherein said task can be performed independently; and

a script engine for providing scripted processing of events and actions within said agent workflow engine.

103. The system of claim 102, wherein said agent further comprises an application program interface for communicating with various messaging protocols.

104. The system of claim 103, wherein said application program interface further allows interaction with client systems.

105. The system of claim 99, wherein said monitor provides displays of notifications regarding said events.

106. The system of claim 91, wherein said agent comprises:

an agent event manager for continuously listening for events on a periodic basis;

an agent workflow engine for processing event received within the system;

an agent workflow manager for controlling and overseeing the processing of events by the workflow engine;

an agent state manager for maintaining state of the server across one or more events in the system; and

an agent notification dispatcher for transmitting said events to various delivery means for notifying users of the system.

107. The system of claim 106, wherein said agent further comprises an event application program interface for interfacing with external engines to receive events addressed to said agent.

108. The system of claim 107, wherein said agent further comprises a connection manager for managing connection to said agent.

109. The system of claim 108, wherein said agent workflow engine comprises:

at least one agent workflow thread for allowing division of the workflow into a smaller task, wherein said task can be performed independently; and

a script engine for providing scripted processing of events and actions within said agent workflow engine.

110. The system of claim 108, wherein said agent further comprises an application program interface for communicating with various messaging protocols.

111. The system of claim 110, wherein said application program interface further allows interaction with client systems.

112. The system of claim 91, wherein said monitor provides handles and displays notifications regarding said events.

113. The system of claim 112, wherein said monitor allows modification of customized rules for event handling.

114. The system of claim 113, wherein said monitor may be viewed from a standard web browser.

115. The system of claim 114, wherein said monitor may be viewed from a customized application.

116. A system for event communication among networks having a plurality of systems, comprising:

means for receiving an event signal in a client, said event signal transmitted by an event-generating entity coupled thereto;

means for obtaining a pre-determined rule associated with said event; and

means for processing said event in accordance with said predetermined rule.

117. The system of claim 116, further comprising means for transmitting said event to a server before said obtaining.

118. The system of claim 116, further comprising means for converting said event into a well-defined event.

119. The system of claim 116, further comprising means for receiving user instructions to configure said pre-determined rule.

120. The system of claim 119, further comprising means for accessing a directory service for accessing information and operational preferences for said client.

121. The system of claim 120, further comprising means for embedding state information into a persistent store on said client for said event.

122. The system of claim 121, further comprising means for providing a notification service, said notification service allowing access to a notification dispatcher for said transmitting of said notifications.

123. The system of claim 122, further comprising means for creating timers to control the duration of processing of said well-defined events.

124. The system of claim 116, further comprising means for accessing a directory service for accessing information and operational preferences for said client.

125. The system of claim 116, further comprising means for embedding state information into a persistent store on said client for said event.

126. The system of claim 116, further comprising means for providing a notification service, said notification service allowing access to a notification dispatcher for said transmitting of said notifications.

127. The system of claim 116, further comprising means for creating timers to control the duration of processing of said well-defined events.

128. The system of claim 116, further comprising means for transmitting notifications as a result of the processing.

129. The system of claim 117, further comprising:

means for receiving said event in said server from said client coupled thereto;

means for obtaining a pre-determined rule associated with said event; and

means for processing said event in accordance with said pre-determined rule.

130. The system of claim 129, further comprising means for transmitting notifications as a result of the processing.

131. The system of claim 130, further comprising an executable script configured to provide customized service during said processing.

132. The system of claim 131, wherein said customized service provides access to a repository that facilitates querying and publishing of information.

133. The system of claim 132, wherein said information assists said systems in establishing connectivity therebetween.

134. The system of claim 131, wherein said customized service causes said executable script to embed state information into a persistent storage means for allowing said event to check state across more than one processing paths.

135. The system of claim 131, wherein said customized service further gives said executable script access to schedules to determine flow of processing of said event.

136. The system of claim 131, wherein said customized service further allows said executable script access to a notification dispatcher, said notification dispatcher transmitting said notifications.

137. The system of claim 136, further comprising means for receiving acknowledgement of said dispatched notification.

138. The system of claim 131, further comprising means for assigning a priority level to said event in accordance with a pre-determined criterion.

139. The system of claim 138, further comprising means for scheduling said event in accordance with said priority level.

140. The system of claim 116, further comprising means for assigning a priority level to said event in accordance with a pre-determined criterion.

141. The system of claim 140, further comprising means for scheduling said well-defined event in accordance with said priority level.

142. A system for event communication among networks having a plurality of systems, comprising:

means for receiving an event at a server, wherein the event is forwarded to said server from a client coupled thereto;

means for obtaining event handling scripts from a storage device associated with the server; and

means for creating a workflow process for processing said event.

143. The system of claim 142, further comprising means for dispatching a notification based upon the processing of said event.

144. The system of claim 142, further comprising means for accessing a repository for querying and publishing information between at least two of said plurality of systems.

145. The system of claim 142, further comprising means for listening for determining presence of events at the server.

146. The system of claim 145, further comprising means for loading a handling script for processing a subsection of said event.

147. The system of claim 146, further comprising means for dispatching a notification for said processed events by one of electronic mail, paging devices, web browsers and instant messaging.

148. A system for event communication among networks having a plurality of systems, comprising:

means for receiving an event at one of said plurality of networks;

means for retrieving an event handling script for processing said typed event; and

means for processing said event within said script engine in accordance with a predetermined handling script associated with said event.

149. The system of claim 148, further comprising means for sending a notification of said event to a server coupled to said client, said notification providing monitoring information for said one of said plurality of networks.

150. The system of claim 149, further comprising means for dispatching a notification in conformance with a predetermined dispatch policy.

151. The system of claim 150, further comprising means for converting said event into a well-defined event, wherein said well-defined event facilitates processing of said event in said one of said plurality of networks.

152. The system of claim 150, further comprising means for saving said well-defined event to a repository.

153. A system for event communication among networks having a plurality of systems, comprising:

means for receiving an event at a first network in said plurality of networks;

means for processing said event at said first network in accordance with a predetermined handling script associated with said event; and

means for dispatching a notification in conformance with a predetermined dispatch policy.

154. The system of claim 153, further comprising means for sending a notification of said event to a server coupled to said client.

155. A system for event communication among networks having a plurality of systems, comprising:

means for receiving an event at a first network in said plurality of networks;

means for transmitting said event to a second network in said plurality of networks;

means for processing said event at said second network in accordance with a predetermined handling script associated with said event; and

means for dispatching a notification in conformance with a predetermined dispatch policy.

156. A system for event communication among networks having a plurality of systems, comprising:

a. a memory;

b. a processing unit disposed in communication with said memory unit, wherein said processing unit is configured for;

receiving an event signal in a client, said event signal transmitted by an event-generating entity coupled thereto;

obtaining a pre-determined rule associated with said event; and

processing said event in accordance with said pre-determined rule.

157. The system of claim 156, wherein said processing unit is further configured for transmitting said event to a server before said obtaining.

158. The system of claim 157, wherein said processing unit is further configured for converting said event into a well-defined event.

159. The system of claim 156, wherein said processing unit is further configured for receiving user instructions to configure said pre-determined rule.

160. The system of claim 156, wherein said processing unit is further configured for accessing a directory service for accessing information and operational preferences for said client.

161. The system of claim 160, wherein said processing unit is further configured for embedding state information into a persistent store on said client for said event.

162. The system of claim 161, wherein said processing unit is further configured for providing a notification service, said notification service allowing access to a notification dispatcher for said transmitting of said notifications.

163. The system of claim 162, wherein said processing unit is further configured for creating timers to control the duration of processing of said well-defined events.

164. The system of claim 156, wherein said processing unit is further configured for accessing a directory service for accessing information and operational preferences for said client.

165. The system of claim 156, wherein said processing unit is further configured for embedding state information into a persistent store on said client for said event.

166. The system of claim 156, wherein said processing unit is further configured for providing a notification service, said notification service allowing access to a notification dispatcher for said transmitting of said notifications.

167. The system of claim 156, wherein said processing unit is further configured for creating timers to control the duration of processing of said well-defined events.

168. The system of claim 157, wherein said processing unit is further configured for transmitting notifications as a result of the processing.

169. The system of claim 157, wherein said processing unit is further configured for:

receiving said event in said server from said client coupled thereto;

obtaining a pre-determined rule associated with said event; and

processing said event in accordance with said pre-determined rule.

170. The system of claim 169, wherein said processing unit is further configured for transmitting notifications as a result of the processing.

171. The system of claim 170, further comprising an executable script configured to provide customized service during said processing.

172. The system of claim 171, wherein said customized service provides access to a repository that facilitates querying and publishing of information.

173. The system of claim 172, wherein said information assists said systems in establishing connectivity therebetween.

174. The system of claim 172, wherein said customized service causes said executable script to embed state information into a persistent storage means for allowing said event to check state across more than one processing paths.

175. The system of claim 172, wherein said customized service further gives said executable script access to schedules to determine flow of processing of said event.

176. The system of claim 172, wherein said customized service further allows said executable script access to a notification dispatcher, said notification dispatcher transmitting said notifications.

177. The system of claim 176, wherein said processing unit is further configured means for receiving acknowledgement of said dispatched notification.

178. The system of claim 177, wherein said processing unit is further configured for assigning a priority level to said event in accordance with a pre-determined criterion.

179. The system of claim 178, wherein said processing unit is further configured for scheduling said event in accordance with said priority level.

180. The system of claim 157, wherein said processing unit is further configured for assigning a priority level to said well-defined event in accordance with a predetermined criterion.

181. The system of claim 180, wherein said processing unit is further configured for scheduling said well-defined event in accordance with said priority level.

182. A system for event communication among networks having a plurality of systems, comprising:

a. a memory;

b. a processing unit disposed in communication with said memory unit, wherein said processing unit is configured for;

receiving an event at a server, wherein the event is forwarded to said server from a client coupled thereto;

obtaining event handling scripts from a storage device associated with the server; and

creating a workflow process for processing said event.

183. The system of claim 182, wherein said processing unit is further configured for dispatching a notification based upon the processing of said event.

184. The system of claim 182, wherein said processing unit is further configured for accessing a repository for querying and publishing information between at least two of said plurality of systems.

185. The system of claim 182, wherein said processing unit is further configured for listening for determining presence of events at the server.

186. The system of claim 185, wherein said processing unit is further configured for loading a handling script for processing the subsection of said event.

187. The system of claim 186, wherein said processing unit is further configured for dispatching said processed events by one of electronic mail, paging devices, web browsers and instant messaging.

188. A system for event communication among networks having a plurality of systems, comprising:

a. a memory;

b. a processing unit disposed in communication with said memory unit, wherein said processing unit is configured for;

receiving an event at one of said plurality of networks;

retrieving an event handling script for processing said typed event; and

processing said event within said script engine in accordance with a predetermined handling script associated with said event.

189. The system of claim 188, wherein said processing unit is further configured for sending a notification of said event to a server coupled to said client, said notification providing monitoring information for said one of said plurality of networks.

190. The system of claim 189, wherein said processing unit is further configured for dispatching a notification in conformance with a predetermined dispatch policy.

191. The system of claim 190, wherein said processing unit is further configured for converting said event into a well-defined event, wherein said well-defined event facilitates processing of said event in said one of said plurality of networks.

192. The system of claim 191, wherein said processing unit is further configured for saving said well-defined event to a storage device.

193. A system for event communication among networks having a plurality of systems, comprising:

a. a memory;

b. a processing unit disposed in communication with said memory unit, wherein said processing unit is configured for;

receiving an event at a first network in said plurality of networks;

processing said event at said first network in accordance with a predetermined handling script associated with said event; and

dispatching a notification in conformance with a predetermined dispatch policy.

194. The system of claim 193, wherein said processing unit is further configured for sending a notification of said event to a server coupled to said client.

195. A system for event communication among networks having a plurality of systems, comprising:

a. a memory;

b. a processing unit disposed in communication with said memory unit, wherein said processing unit is configured for;

receiving an event at a first network in said plurality of networks;

transmitting said event to a second network in said plurality of networks;

processing said event at said second network in accordance with a predetermined handling script associated with said event; and

dispatching a notification in conformance with a predetermined dispatch policy.

196. A computer device comprising a computer readable medium having computer readable code means embodied therein for event communication among networks having a plurality of systems, said computer readable code means further comprising:

means for receiving an event signal in a client, said event signal transmitted by an event-generating entity coupled thereto;

means for obtaining a pre-determined rule associated with said event; and

means for processing said event in accordance with said pre-determined rule.

197. The computer readable code means of claim 196, further comprising means for transmitting said event to a server before said obtaining.

198. The computer readable code means of claim 196, further comprising means for converting said event into a well-defined event.

199. The computer readable code means of claim 196, further comprising means for receiving user instructions to configure said pre-determined rule.

200. The computer readable code means of claim 196, further comprising means for accessing a directory service for accessing information and operational preferences for said client.

201. The computer readable code means of claim 200, further comprising means for embedding state information into a persistent store on said client for said event.

202. The computer readable code means of claim 201, further comprising means for providing a notification service, said notification service allowing access to a notification dispatcher for said transmitting of said notifications.

203. The computer readable code means of claim 202, further comprising means for creating timers to control the duration of processing of said well-defined events.

204. The computer readable code means of claim 196, further comprising means for accessing a directory service for accessing information and operational preferences for said client.

205. The computer readable code means of claim 196, further comprising means for embedding state information into a persistent store on said client for said event.

206. The computer readable code means of claim 196, further comprising means for providing a notification service, said notification service allowing access to a notification dispatcher for said transmitting of said notifications.

207. The computer readable code means of claim 196, further comprising means for creating timers to control the duration of processing of said well-defined events.

208. The computer readable code means of claim 196, further comprising means for transmitting notifications as a result of the processing.

209. The computer readable code means of claim 197, further comprising:

means for receiving said event in said server from said client coupled thereto;

means for obtaining a predetermined rule associated with said event; and

means for processing said event in accordance with said predetermined rule.

210. The computer readable code means of claim 209, further comprising means for transmitting notifications as a result of the processing.

211. The computer readable code means of claim 210, further comprising an executable script configured to provide customized service during said processing.

212. The computer readable code means of claim 209, wherein said customized service provides access to a repository that facilitates querying and publishing of information.

213. The computer readable code means of claim 212, wherein said information assists said systems in establishing connectivity therebetween.

214. The computer readable code means of claim 213, wherein said customized service causes said executable script to embed state information into a persistent storage means for allowing said event to check state across more than one processing paths.

215. The computer readable code means of claim 213, wherein said customized service further gives said executable script access to schedules to determine flow of processing of said event.

216. The computer readable code means of claim 213, wherein said customized service further allows said executable script access to a notification dispatcher, said notification dispatcher transmitting said notifications.

217. The computer readable code means of claim 216, further comprising means for receiving acknowledgement of said dispatched notification.

218. The computer readable code means of claim 216, further comprising means for assigning a priority level to said event in accordance with a pre-determined criterion.

219. The computer readable code means of claim 218, further comprising means for scheduling said event in accordance with said priority level.

220. The computer readable code means of claim 196, further comprising means for assigning a priority level to said well-defined event in accordance with a predetermined criterion.

221. The computer readable code means of claim 220, further comprising means for scheduling said well-defined event in accordance with said priority level.

222. A computer device comprising a computer readable medium having computer readable code means embodied therein for event communication among networks having a plurality of systems, said computer readable code means further comprising:

means for receiving an event at a server, wherein the event is forwarded to said server from a client coupled thereto;

means for obtaining event handling scripts from a storage device associated with the server; and

means for creating a workflow process for processing said event.

223. The computer readable code means of claim 222, further comprising means for dispatching a notification based upon the processing of said event.

224. The computer readable code means of claim 223, further comprising means for accessing a repository for querying and publishing information between at least two of said plurality of systems.

225. The computer readable code means of claim 224, further comprising means for listening for determining presence of events at the server.

226. The computer readable code means of claim 225, further comprising means for loading a handling script for processing the subsection of said event.

227. The computer readable code means of claim 226, further comprising means for dispatching said processed events by one of electronic mail, paging devices, web browsers and instant messaging.

228. A computer device comprising a computer readable medium having computer readable code means embodied therein for event communication among networks having a plurality of systems, said computer readable code means further comprising:

means for receiving an event at one of said plurality of networks;

means for retrieving an event handling script for processing said typed event; and

means for processing said event within said script engine in accordance with a predetermined handling script associated with said event.

229. The computer readable code means of claim 228, further comprising means for sending a notification of said event to a server coupled to said client, said notification providing monitoring information for said one of said plurality of networks.

230. The computer readable code means of claim 229, further comprising means for dispatching a notification in conformance with a predetermined dispatch policy.

231. The computer readable code means of claim 230, further comprising means for converting said event in to a well-defined event, wherein said well-defined event facilitates processing of said event in said one of said plurality of networks.

232. The computer readable code means of claim 231, further comprising means for saving said well-defined event to a repository.

233. A computer device comprising a computer readable medium having computer readable code means embodied therein for event communication among networks having a plurality of systems, said computer readable code means further comprising:

means for receiving an event at a first network in said plurality of networks;

means for processing said event at said first network in accordance with a predetermined handling script associated with said event; and

means for dispatching a notification in conformance with a predetermined dispatch policy.

234. The computer readable code means of claim 233, further comprising means for sending a notification of said event to a server coupled to said client.

235. A computer device comprising a computer readable medium having computer readable code means embodied therein for event communication among networks having a plurality of systems, said computer readable code means further comprising:

means for receiving an event at a first network in said plurality of networks;

means for transmitting said event to a second network in said plurality of networks;

means for processing said event at said second network in accordance with a predetermined handling script associated with said event; and

means for dispatching a notification in conformance with a predetermined dispatch policy.