Examples: Using CfAlias

You can configure the parameters in the CfAlias.cfg file according to your end goal.

A daily report named report.doc is received by TIBCO MFT Platform Server running on a UNIX server everyday from a remote TIBCO MFT Platform Server user named JohnDoe. The user sends a new report each day and the report.doc sent on the previous day is replaced with the new report file. The UNIX administrator wants to prevent the existing report.doc from being replaced without involving JohnDoe.

To solve this, the administrator can simply set up two CfAlias groupings in the CfAlias.cfg file as follows: 

USERID=JohnDoe,
NODE=DEFAULT,
TYPE=RECEIVE,
FILE=/home/JohnDoe/DailyReports/report.%GDATE.doc,
ALIAS=report.doc
*
USERID=JohnDoe,
NODE=DEFAULT,
ALLOW=NO
With the settings configured in the first CfAlias grouping set, when JohnDoe sends in his daily report, it is put in the following directory with a new file name each day based on the current date:

/home/JohnDoe/DailyReports/report.%GDATE.doc

For example, if the date is July 18, 2009, the file can be created as report.090718.doc. JohnDoe has no knowledge of where or how his report is stored. Also, note the TYPE=RECEIVE setting, this is because a receive transfer on the responder is a send transfer from the initiator. Finally, the second CfAlias grouping restricts JohnDoe from having any other access to any file that is not report.doc.