Are there any limitations on JOBFs running on TLS GW in parallel?
search cancel

Are there any limitations on JOBFs running on TLS GW in parallel?

book

Article ID: 271124

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation Automic SaaS

Issue/Introduction

Is there anything that details performance of the TLS Gateway and how many filetransfers can run in parallel?  For example, if thousands of JOBF's run a day between 12.3 and 21.0 or v24 agents, will that be a problem?

Environment

Release : 21.0, 24.x

Resolution

Theoretically there are no limitations on the number of filetransfers that can be run through a TLS GW; any limitations will be dependent upon the amount of resources (CPU, memory, etc...) as TLS/AES encryptions is CPU intensive.  Because of this, our recommendation is to test thoroughly before using the TLS GW (100 FT at a time, 1000, 10000 if needed, etc...) to see if there's any problems and enough resources dedicated to the TLS GW, which will gather what it needs from java, so the VM needs to have resources and java needs to be able to use those resources.

The TLS Gateway is meant as a stop gap while upgrading 12.3 agents to 21.0 and then as a way to run filetransfer between the 21.0 non-TLS agents and the 21.0 or 24.x TLS agents, which should not include too many agents in most environments (AS/400, z/OS, BS2000, etc...)