Location discovery provides runtime mapping between location codes, or node names, and network addresses. This is called location discovery.
Location discovery in done two ways:
static discovery using configuration information.
dynamic discovery using service discovery.
Configuration can be used to define the mapping between a node name and a network address. Configuring this mapping is allowed at any time, but it is only required if service discovery cannot be used for location discovery. An example of when this would be necessary is if a remote node is across a wide area network where service discovery is not allowed. This is called static discovery.
If configuration information is not provided for a location name, service discovery is used to perform location discovery. This has the advantage that no configuration for remote nodes has to be done on the local node - it is all discovered at runtime. This is called dynamic discovery.
![[Warning]](images/warning.png) | |
When a network address is discovered with both static and dynamic discovery, the configured static discovery information is used. |
Location discovery is performed in the following cases:
A create of an object in a partition with a remote active node.
A method or field is set on a remote object.
When an object is associated with a partition whose active node is remote, a location discovery request is done by node name, to locate the network information associated with the node name.
When an operation is dispatched on a remote object, a location discovery request is done by location code, to locate the network information associated with a location code.
Location code information is cached on the local node once it has been discovered.