If you have one or more Web service clients that run on the same consumer system, such as System A, and you want to configure them to consume one or more Web services which run on the same provider system, such as System B, you need to create a Web service physical destination on the consumer system.
You can configure a Web service client using this approach only if it already contains a Web service logical destination in its implementation. The logical destination is set by the developer of the client application at design time. It serves as a reference for the client to the set of Web services which it wants to consume. At the same time, the logical destination also points the client to any provider system in an abstract way. The exact details identifying the physical provider system to which the logical destination would actually point to depend on and are specified in the physical destination at runtime.
A Web service physical destination contains the following settings:
● The name of the logical destination available in the Web service client which has to be configured.
In this way, the physical destination is mapped to the logical destination, and hence to the clients which have a logical destination with that name. The settings (see below) you set in the physical destination are applied to all clients which have a logical destination with the specified name.
● The connection and authentication details of the physical provider system, such as the host name, port number, user name and password, and so on.
In this way, the physical destination enables the client to connect to the particular system which actually provides the Web services.
● The way in which the Web service client can discover the Web services on the provider system: by using a WSDL URL, WSIL, or by querying the Services Registry.
● Runtime configuration settings for the Web service client(s), such as authentication level.
Web service physical destination
When you have two or more Web service clients each having a logical destination with the same name, for example, HR, you can configure them at one go by creating a single physical destination with name HR. You can think of this physical destination as of a template which holds all the runtime settings needed by the clients with logical destination HR to consume the relevant Web services.