IT34506: ALLOW CACHING OF REMOTE SERVER CONNECTIONS FOR FILE NODES

APAR status

• Closed as new function.

Error description

• When using the File Nodes with a remote SFTP, FTP or FTPS
  server a new connection is established for every operation.
  This can lead to an excessive performance penalty and an
  excessive use of resources on the remoter server.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of App Connect Enterprise version 11 or IBM
  Integration Bus version 10 using the File Nodes to connect to
  remote SFTP, FTPS or FTP servers.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  <span style="background-color:rgb(255, 255, 255)">When using the
  File Nodes with a remote SFTP, FTP or FTPS </span><span
  style="background-color:rgb(255, 255, 255)">server a new
  connection is established for every operation.    </span>
  <span style="background-color:rgb(255, 255, 255)">This can lead
  to an excessive performance penalty and an </span><span
  style="background-color:rgb(255, 255, 255)">excessive use of
  resources on the remoter server.     </span>
  

Problem conclusion

• This APAR introduces the ability to cache a remote server
  connection and re-use it for subsequent calls on the same
  thread. This behaviour can be enabled using the environment
  variable MQSI_FILENODES_CACHE_REMOTE_SERVICES. When set to any
  non-null value this causes connections to be cached. The
  environment variable must be set prior to starting the
  Integration Node or Server and therefore requires a restart to
  take effect. For example:
  
  <span style="background-color:rgb(255, 255,
  255)">MQSI_FILENODES_CACHE_REMOTE_SERVICES=1</span>
  
  By default cached connections will be invalidated after
  remaining idle for more than 5 minutes. The length of this idle
  timeout can be modified by setting the environment variable
  MQSI_FILENODES_REMOTE_SERVICE_TIMEOUT which takes a value in
  milliseconds. For example to set a default timeout of 10 minutes
  you would set:
  
  MQSI_FILENODES_REMOTE_SERVICE_TIMEOUT=600000
  
  When a connection becomes idle, by default the node will attempt
  to reopen the same connection when required. This can cause
  problems for some remote servers that require an entirely new
  connection to be established. If this is the case the
  environment variable
  MQSI_FILENODES_CACHE_REMOTE_SERVICES_DISPOSE_ON_EXPIRY may be
  set to force idle connections to be discarded and new
  connections to be established. For example:
  
  MQSI_FILENODES_CACHE_REMOTE_SERVICES_DISPOSE_ON_EXPIRY=1
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.23
  v11.0      11.0.0.12
  
  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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels