APAR status
Closed as program error.
Error description
From fixpack 11.0.0.13 the following properties are available to control FileNodes behaviour in the server.conf.yaml file but these are not documented: allowReadOnlyInputFiles true/false default=false When set to true this will allow files to be processed by the FileInput node if the file has filesystem permissions set to read-only for the ACE user. The parent directory must still be writeable. disableLocking true/false default=false When set to true prevents the File Nodes from obtaining operating system level locks on files before processing them. This can be helpful to allow files to be processed on filesystems that do not support POSIC file locking semantics. Note that file locking is used to prevent multiple Integration Servers or Integration Nodes from reading the same input file when processing from the same directory. Therefore if disableLocking is set to true the user must ensure that only a single Integration Server reads from the specified input directory. avoidWriteLockCheck true/false default=false When set to true bypasses the write lock check on an input file before it is processed by the FileInput node. For network filesystems that cache file attributes between calls this can prevent the accumulation of zero length input file in the input directory. maxDirectoryDepth int default = 50 The maximum depth of directory structure a FileINput Node will traverse below the input directorym as described here: https:// www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools .mft.bipmsgs.doc/ay_bip3.htm rootDirectory string default='' Allows a base directory to be set such that relative paths set in the FileINput Node's directory property will be constructed relative to this abse path. As described here: https://www.ibm. com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.bip msgs.doc/ay_bip3.htm allowFileSystemRoot true/false default=false When set to true will allow teh FileInput node to read and delete processed fiels from the root directory of the operating system. As described here: https://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ib m.etools.mft.bipmsgs.doc/ay_bip3.htm maxRecordLength int default=104857600 The maximum size of record that will be read by the FileInput or FileRead nodes. In the case where the Record Detection property is set to "Whole File" this is the maximum length of file that may be processed. As described here: https://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ib m.etools.mft.doc/au55470_.htm
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM App Connect Enterprise 11 or 12 using the File nodes. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: <span style="background-color:rgb(255, 255, 255)">From fixpack 11.0.0.13 the following properties are available to </span><span style="background-color:rgb(255, 255, 255)">control FileNodes behaviour in the server.conf.yaml file but </span><span style="background-color:rgb(255, 255, 255)">these are not documented: </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">allowReadOnlyInputFiles true/false default=false </span><span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">When set to true this will allow files to be processed by the </span><span style="background-color:rgb(255, 255, 255)">FileInput node if the file has filesystem permissions set to </span><span style="background-color:rgb(255, 255, 255)">read-only for the ACE user. The parent directory must still be </span><span style="background-color:rgb(255, 255, 255)">writeable. </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">disableLocking true/false default=false </span> <span style="background-color:rgb(255, 255, 255)">When set to true prevents the File Nodes from obtaining </span><span style="background-color:rgb(255, 255, 255)">operating system level locks on files before processing them. </span><span style="background-color:rgb(255, 255, 255)">This can be helpful to allow files to be processed on </span><span style="background-color:rgb(255, 255, 255)">filesystems that do not support POSIX file locking semantics. </span> <span style="background-color:rgb(255, 255, 255)">Note that file locking is used to prevent multiple Integration </span><span style="background-color:rgb(255, 255, 255)">Servers or Integration Nodes from reading the same input file </span><span style="background-color:rgb(255, 255, 255)">when processing from the same directory. Therefore if </span><span style="background-color:rgb(255, 255, 255)">disableLocking is set to true the user must ensure that only a </span><span style="background-color:rgb(255, 255, 255)">single Integration Server reads from the specified input </span><span style="background-color:rgb(255, 255, 255)">directory. </span> <span style="background-color:rgb(255, 255, 255)"> </span><span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">avoidWriteLockCheck true/false default=false </span> <span style="background-color:rgb(255, 255, 255)">When set to true bypasses the write lock check on an input file </span><span style="background-color:rgb(255, 255, 255)">before it is processed by the FileInput node. For network </span><span style="background-color:rgb(255, 255, 255)">filesystems that cache file attributes between calls this can </span><span style="background-color:rgb(255, 255, 255)">prevent the accumulation of zero length input file in the input </span><span style="background-color:rgb(255, 255, 255)">directory. </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">maxDirectoryDepth int default = 50 </span> <span style="background-color:rgb(255, 255, 255)">The maximum depth of directory structure a FileINput Node will </span><span style="background-color:rgb(255, 255, 255)">traverse below the input directorym as described here: https://</span>www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/ com.ibm.etools<span style="background-color:rgb(255, 255, 255)">.mft.bipmsgs.doc/ay_bip3.htm </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">rootDirectory string default='' </span> <span style="background-color:rgb(255, 255, 255)">Allows a base directory to be set such that relative paths set </span><span style="background-color:rgb(255, 255, 255)">in the FileINput Node's directory property will be constructed </span><span style="background-color:rgb(255, 255, 255)">relative to this abse path. As described here: </span>https://www.ibm<span style="background-color:rgb(255, 255, 255)">.</span><span style="background-color:rgb(255, 255, 255)">com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mf t.bip</span><span style="background-color:rgb(255, 255, 255)">msgs.doc/ay_bip3.htm </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">allowFileSystemRoot true/false default=false </span> <span style="background-color:rgb(255, 255, 255)">When set to true will allow teh FileInput node to read and </span><span style="background-color:rgb(255, 255, 255)">delete processed fiels from the root directory of the operating </span><span style="background-color:rgb(255, 255, 255)">system. As described here: </span> https://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ib< span style="background-color:rgb(255, 255, 255)">m.etools.mft.bipmsgs.doc/ay_bip3.htm </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">maxRecordLength int default=104857600 </span> <span style="background-color:rgb(255, 255, 255)">The maximum size of record that will be read by the FileInput or </span><span style="background-color:rgb(255, 255, 255)">FileRead nodes. In the case where the Record Detection property </span><span style="background-color:rgb(255, 255, 255)">is set to "Whole File" this is the maximum length of file that </span><span style="background-color:rgb(255, 255, 255)">may be processed. As described here: </span> https://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ib< span style="background-color:rgb(255, 255, 255)">m.etools.mft.doc/au55470_.htm </span>
Problem conclusion
The Knowledge Center has been updated to include description of these Resource Manager parameters. The sample server.conf.yaml files have also been updated with these properties. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v11.0 11.0.0.17 v12.0 12.0.4.0 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT37222
Reported component name
APP CONNECT ENT
Reported component ID
5724J0550
Reported release
B00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-06-11
Closed date
2022-03-02
Last modified date
2022-03-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
APP CONNECT ENT
Fixed component ID
5724J0550
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]
Document Information
Modified date:
10 March 2022