Abstract: A messaging system for masking addresses from sending processes. The messaging system maintains a message service profile and a service-address profile. The messaging system accesses recipient data. Sending processes are able to send messages to the messaging system in a form such that each message has an message type and list of recipients. The messaging system is able to determine which of a set of sending services is to be used to send the message, based on the message-service profile. The service-address profile stores information about where in the structure of recipient data the appropriate address for the selected service is located. The addresses corresponding to the named recipients, for the services determined by the messaging system, can be retrieved by from recipient data. The message system can then provide the recipient address to the appropriate sending services to send the message.

Abstract: A Web services access management system which enables loosely coupled Web services can include a servlet configured to receive incoming request messages to access business logic and a mapping table associating different ones of the request messages with different business logic. Mapping logic can be disposed between the servlet and the business logic and configured to route at least part of the incoming request messages to selected ones of the business logic according to the mapping table. Finally, the system can include a response builder configured to build responses with data produced by the business logic responsive to processing incoming request messages routed by the mapping logic. In this regard, changes to the mapping logic can remain transparent to clients transmitting request messages and the business logic servicing the requests.

Abstract: A Web services access management system which enables loosely coupled Web services can include a servlet configured to receive incoming request messages to access business logic and a mapping table associating different ones of the request messages with different business logic. Mapping logic can be disposed between the servlet and the business logic and configured to route at least part of the incoming request messages to selected ones of the business logic according to the mapping table. Finally, the system can include a response builder configured to build responses with data produced by the business logic responsive to processing incoming request messages routed by the mapping logic. In this regard, changes to the mapping logic can remain transparent to clients transmitting request messages and the business logic servicing the requests.

Abstract: A messaging system for masking addresses from sending processes. The messaging system maintains a message service profile and a service-address profile. The messaging system accesses recipient data. Sending processes are able to send messages to the messaging system in a form such that each message has an message type and list of recipients. The messaging system is able to determine which of a set of sending services is to be used to send the message, based on the message-service profile. The service-address profile stores information about where in the structure of recipient data the appropriate address for the selected service is located. The addresses corresponding to the named recipients, for the services determined by the messaging system, can be retrieved by from recipient data. The message system can then provide the recipient address to the appropriate sending services to send the message.

Abstract: A system is provided to permit page definitions in the Java Server Pages standard (JSP pages) may be invoked in response to non-HTTP protocol requests. An adapter is created by a servlet in a web server. The adapter receives requests which may include non-HTTP requests. A composition service is provided that is usable for both HTTP and non-HTTP format requests. Within the composition service, the protocol of the request is evaluated. Where the request is an HTTP request, specified JSP files may be executed directly from the service. Where the request is a non-HTTP request, the composition service carries out steps to ensure that specified JSP files are executable. The composition service may generate a HTTP request to the web server to execute the specified JSP files.