Automic Workload Automation

 View Only
  • 1.  Port configuration

    Posted Feb 05, 2025 05:08 AM
    Hello Community,
    
    Taking into account, 
    JCP.PORTS= defines ports for internal communication only. It is not mandatory to configure such ports.
    If you do not define those ports they will bind to random ports. WS.PORT= defines the ports for incoming TLS communication.
    Agents and AWI will initiate the connection to the JCP using those ports! (not JCP.PORTS!) - If in the ucsrv.ini we put CP port 2217 and the WS ports PORT=2218-2221,
    we get the AS/400 to go through CP 2217 and the TLS through ports 2218 and 2221, the AWI in the ucconfig we will put port 2221. Is there anything else that needs to be adjusted in the system, or is this enough/correct?

    Thank you
    Regards


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


  • 2.  RE: Port configuration

    Broadcom Employee
    Posted Feb 06, 2025 06:22 AM

    @Santiago Fernandez

    Please make sure that those ports used for the JCPs (== WS.PORT) are not listed in any of the Non-TLS Agents ini-files as alternative ports/endpoints for connection to the AE. There might be some outdated entries from times where you were running multiple CPs.

    These pages might also be helpful:

    Michael



    ------------------------------
    Michael K. Dolinek

    Engineering Program Manager | Agile Operation Division
    Broadcom Software
    ------------------------------



  • 3.  RE: Port configuration

    Posted Feb 07, 2025 09:04 AM

    Thank you Michael



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