TIBCO Managed File Transfer Platform Server Remote Node Name Identification for Incoming Requests
book
Article ID: KB0078130
calendar_today
Updated On:
Products
Versions
TIBCO Managed File Transfer Platform Server for UNIX
8.0.0, 7.2.0
Description
Platform Server for Windows and Platform Server for Unix have slightly different logic for identifying the defined node for incoming requests. This article describes each approach.
Platform Server for Windows will perform the following logic to match an incoming request against the cfnode table to find the node that initiated the request in this order:
1. Check each cfnode entry for a match on the incoming IP Address
2. For cfnode entries defined with an IP Name, do a DNS Lookup to get the IP Address(es) associated with the IP Name and match the results against the incoming IP Address.
3. Issue Reverse DNS Lookup to find the IP Name associated with the incoming IP Address and check for a match on the IP Name in the Nodes table
Platform Server for Unix will perform the following logic to match an incoming request against the cfnode table to find the node that initiated the request.
Issue Reverse DNS Lookup to find the IP Name associated with the incoming IP Address
1. Check each cfnode entry for a match on the incoming IP Address
2. Check for match on the IP Name found in reverse DNS lookup
3. For cfnode entries defined with an IP Name, do a DNS Lookup to get the IP Address(es) associated with the IP Name and match the results against the incoming IP Address.
Note that in Platform Server for Windows and Platform Server for Unix version 8.0.0 and above, multiple IP addresses or multiple IP names are allowed on a node definition. The first is used for initiator requests. All are used on a responder to find a matching node definition.
Issue/Introduction
This article explains how TIBCO Managed File Transfer Platform Server for Windows and Unix identify the remote node name for incoming requests