Extended support of the Application Entity Title on Unix and Windows systems

So far the sender was identified via the partner address. If the partner address of the initiator is changed from time to time, FTAM can have problems with the partner allocation and also with the recovery.

The Application Entity Title offers the option of implementing a sender verification which is independent of the partner address for FTAM as well. The sender verification of FTAM partners by means of the Application Entity Title can be specified via operation parameter settings.

Directory Form of the Application Entity Title

In addition to the numeric form there is a Directory Form (also known as transparent form) for Application Process Title and Application Entity Qualifier, respectively.

If an instance identification specified in a FTAM partner list entry does not correspond to the numeric form it is interpreted as Directory Form and the following applies:

• no blank at the beginning of a specification

• no blank at the beginning of a string that is attached to a numeric specification

Otherwise the Application Entity Title is rejected.

Specifications that contain a character which is neither a decimal number nor a dot will be sent and evaluated as ISO646 string in the Directory Form of the Application Entity Title.

The character string before the last occurrence of two sequential dots in the Directory Form is interpreted as Application Process Title.

The character string after the last occurrence of two sequential dots in the Directory Form is interpreted as Application Entity Qualifier. Exception: the identification ends with .. or ..#.

Examples

Specifications in the Directory Form are output in hexadecimal form as they would appear in the trace:

-id=1.3.5.6..# -id=9.3.4.5.2 -id=1.2.3.4.5.6.7..8.9	APT = 0x312e332e352e36 *) is rejected as only 0, 1 or 2 would be permitted at the first digit APT = 0x312e322e332e342e352e362e37 AEQ =0x382e39
-id=1.2.3.4.5.6.7.8.9.10.11 is rejected
-id=%ip139.28.87.55 -id=emil -id=1.3.5A "-id=1.3.5 A" "-id=Emil Huber" -id=Emil.Huber -id=Emil..Huber -id=Emil.. -id=Emil..#	APT = 0x2569703133392e32382e38372e3535 APT = 0x656d696c APT = 0x312e332e3541 is rejected APT = 0x456d696c204875626572 APT = 0x456d696c2e4875626572 APT =0x456d696c AEQ = 0x4875626572 APT = 0x456d696c *) APT = 0x456d696c *)

*)	These specifications are not suitable for a sender check via Application Entity Title if the partner is openFT. I.e., leading zeros, and strings ending with . or .. must be avoided in numeric specifications, and - with transparent format .. or ..# at the end must not exist.