Automic Workload Automation

 View Only

  • 1.  TLS Gateway config. error

    Posted Mar 05, 2025 03:43 AM
    Hi everyone,
    We are setting up a TLS Gateway to communicate a non-TLS OS/400 port
    We have followed the installation manual, but we can only see it trying to communicate and after a few minutes it ends without result.
    The log I copied gives little information, but it seems to be searching for the IPs, although I do not see the server machine.


    20250225/082102.346 - U02000097 Connection with partner 'wss://10.254.169.70:2222/agent(/10.254.169.70:60804)' accepted.

    20250225/082102.424 -           U02002039 - 1        Successfully established connection with 'PCUC4001' (socket handle = '1158237757').

    20250225/082102.440 -           U00063013 - 1        FT '19517004': Connecting to '10.17.16.4' at port '2309'.

    20250225/082102.752 -           U02000060 - 1        Closing connection to Agent '0.0.0.0/0.0.0.0'.

    20250225/082102.752 -           U02000412 - 1        '0.0.0.0/0.0.0.0' ordered to close TLS connection with agent 'PCUC4001'.

    20250225/082102.752 - U02100051 Web socket connection 'PCUC4001 closed with status code 'No code present (1005)', reason '-'.\

    20250225/082102.768 - U02000327 Unexpected error on connection 'PCUC4001' (socket handle = '2'), reason '-'.

    20250225/082102.768 - U00045014 Exception 'java.nio.channels.ClosedChannelException: "null"' at 'org.eclipse.jetty.websocket.core.internal.WebSocketSessionState.onEof():169'.

    20250225/082102.768 - U02100051 Web socket connection 'PCUC4001 closed with status code 'No code present (1005)', reason '-'.\

    In the screenshot you can see what happened when triggering a JOBF in AS400.
    It remains connecting.... but does not do anything.

    I look forward to any help on this matter.
    Thanks in advance


    ------------------------------
    Santiago Fernández
    UC SOFTWARE
    santiago.fernandez@ucsoftware.es
    ------------------------------


  • 2.  RE: TLS Gateway config. error

    Posted Mar 06, 2025 07:55 AM
    Edited by Pothen Verghese Mar 07, 2025 07:22 AM

    Hi,

    There are two ways the Non-TLS agents can connect to AE. ( https://docs.automic.com/documentation/webhelp/english/AA/24.3/DOCU/24.3/Automic%20Automation%20Guides/Content/_Common/Security/Security_Hardening_AEFirewallPorts.htm - Refer the Agents and Proxy image) 

    a) Directly to a CP. TLS Gateway in this case is only involved in file transfers between TLS and Non-TLS agents.

    b) To the JCP via the TLS Gateway.

    The 2nd method is not very consistent and has problems when it comes to file transfer from Non-TLS agent to TLS-Agent. Try the first method and check.

    Regards

    Pothen