Main

WSCandis is a caching and directory solution especially tailored for enterprise environments in which client applications rely on a layer of webservices that may be located on separate locations. In these environments applications are often deployed from one or more development servers to one or more production servers.

The Webservices Caching and Directory Service (wscandis) tries to address the following issues:

• The need of applications that act as webservices clients to have the webservice WSDL address hardcoded as part of the application code.
• The lack of a single directory of web services used by all applications
• Lack of a consistent naming scheme for all webservices (i.e. "com.uvi.general.resorts") regardless of their network location, implementation language and environment.
• An application's need to use a different webservice, or the same webservice but on different locations, based on whether the application is being executed on a development or production server.
• Performance hit on high demand applications due to having to continually instantiate and discard webservice stubs for each request.

WSCandis tries to solve these problems using a two-part approach: a webservice stub caching mechanism ( CachingEngine ) and the use of a central directory and lookup service ( DirectoryService )

The following diagram displays a general overview of how the elements of wscandis are interconnected. Media:wscandis_overview.jpg

See Also:

• UsingWSCandis

UML Diagrams

• Sequence Diagram 1: Requested webservice is not on the cache Media:wscandis_sd1.jpg
• Sequence Diagram 2: Requested webservice is already on the cache Media:wscandis_sd2.jpg
• Class Diagram 1: Client Media:wscandis_cd_client.jpg
• Class Diagram 2: Server Media:wscandis_cd_server.jpg