ESP Workload Automation

 View Only
  • 1.  FTP Set Up on New Agent Can't Load JARS

    Posted Sep 29, 2020 10:24 AM
    I am setting up to migrate from DE 11.3 to 12.2

    As part of this I am setting up new agents to be on the latest agent build level.

    Workload Automation Agent for:
    Linux x86_64 64-bit
    Version 12.0.00.00-6181

    But, FTP, SFTP job fails to run.

    1. Initially Plugin-not found
    2. Reviewed agentparam.txt on current working agent
    3. Can't find a command to run to add the agentparam.txt settings.
      1. https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-system-agent/12-0/configuring/set-up-and-run-ftp-workload/ftp-client-and-ftp-server.html 
      2. For a silent installation, add the following settings for the FTP client in the installer properties file:
        FTP_PLUGIN=1 FTP_NO_SERVER=true
      3. What is the installer properties file called and how to run it.
        1. Would be good to have links to notes in these sections.
      4. I added FTP settings from previous Agent where it was working
    4. Now runs, but fails "Cannot Load Jars"
      1. The JARS are there, but cannot be loaded
      2. Error: Could not find or load main class ext.jackson-databind.jar:.opt.CA.WA_Agent.jars.ext.commons-cli.jar:.opt.CA.WA_Agent.jars.ext.xmlsec.jar:.opt.CA.WA_Agent.jars.ext.xml-apis.jar:.opt.CA.WA_Agent.jars.ext.xercesImpl.jar:.opt.CA.WA_Agent.jars.ext.xalan.jar:.opt.CA.WA_Agent.jars.ext.wss4j.jar:.opt.CA.WA_Agent.jars.ext.wsdl4j.jar:.opt.CA.WA_Agent.jars.ext.slf4j-jcl.jar:.opt.CA.WA_Agent.jars.ext.slf4j-api.jar:.opt.CA.WA_Agent.jars.ext.serializer.jar:.opt.CA.WA_Agent.jars.ext.resolver.jar:.opt.CA.WA_Agent.jars.ext.qname.jar:.opt.CA.WA_Agent.jars.ext.opensaml.jar:.opt.CA.WA_Agent.jars.ext.json-smart.jar:.opt.CA.WA_Agent.jars.ext.json-path.jar:.opt.CA.WA_Agent.jars.ext.jaxrpc.jar:.opt.CA.WA_Agent.jars.ext.httpmime.jar:.opt.CA.WA_Agent.jars.ext.httpcore.jar:.opt.CA.WA_Agent.jars.ext.httpclient-cache.jar:.opt.CA.WA_Agent.jars.ext.httpclient.jar:.opt.CA.WA_Agent.jars.ext.commons-logging.jar:.opt.CA.WA_Agent.jars.ext.commons-lang3.jar:.opt.CA.WA_Agent.jars.ext.commons-discovery.jar:.opt.CA.WA_Agent.jars.ext.commons-collections4.jar:.opt.CA.WA_Agent.jars.e
    5. Why won't it load the JARs?


  • 2.  RE: FTP Set Up on New Agent Can't Load JARS

    Broadcom Employee
    Posted Sep 30, 2020 09:06 AM
    Hi,
    If you have already installed the agent then just add the 'plugin.start_internal_<n>=ftp' in agentparm.txt, see this link for R12.
    The installer properties file name can be anything, you just have to put the -f switch after setup,  e.g setup.bin -f <file>
    If you are getting errors on jars, then most likely install didn't complete or there was an error.   There will be an install log in install directory with name starting like this '

    CA_WA_Agent_12.0.....'.  Check that for any errors.
    Also, check if the missing jars are present in jars directory.

    HTH,
    Nitin Pande




    ------------------------------
    Support
    Broadcom
    Toronto
    ------------------------------



  • 3.  RE: FTP Set Up on New Agent Can't Load JARS

    Posted Oct 01, 2020 12:58 PM
    Hi Nitin,

    Thank you so much for your response, yes I'm in a crunch here.

    The install looks good, the log did not show any errors.
    I added the FTP properties as per my current agent.

    Plug-in Start Up
    plugins.start_internal_1=runner
    plugins.start_internal_2=router
    plugins.start_internal_3=filemon
    plugins.start_internal_4=objmon
    plugins.start_internal_5=filebrowser
    plugins.start_internal_6=database
    plugins.start_internal_7=appservices
    plugins.start_internal_8=dataservices
    plugins.start_internal_9=ftp


    #
    # FTP specific properties
    #
    ftp.noserver=true
    #ftp.serverport=21

    ftp.client.ssl=true
    ftp.client.ssl.truststore=/opt/CA/WA_Agent/cacerts
    ftp.client.ssl.truststore.password=XXXXXXXXXXXXXX
    #ftp.client.ssl.start_with_ssl_session=true
    ftp.download.owner=<The Owner>
    ftp.passive=true
    ftp.scp.debug.enable=true
    ftp.client.ssl.accept_new_ca=true


    # Jars classpath with full path
    oscomponent.classpath=/opt/CA/WA_Agent/jars/*.jar:/opt/CA/WA_Agent/jars/ext/*


    Error Output:

    Output of messages for workload object UPLOAD/PR_TEST_PYTHON.4/MAIN
    Start date Thu Oct 1 13:24:04 2020
    ----------------------------------------------------------------
    Error: Could not find or load main class ext.jackson-databind.jar:.opt.CA.WA_Agent.jars.ext.commons-cli.jar:.opt.CA.WA_Agent.jars.ext.xmlsec.jar:.opt.CA.WA_Agent.jars.ext.xml-apis.jar:.opt.CA.WA_Agent.jars.ext.xercesImpl.jar:.opt.CA.WA_Agent.jars.ext.xalan.jar:.opt.CA.WA_Agent.jars.ext.wss4j.jar:.opt.CA.WA_Agent.jars.ext.wsdl4j.jar:.opt.CA.WA_Agent.jars.ext.slf4j-jcl.jar:.opt.CA.WA_Agent.jars.ext.slf4j-api.jar:.opt.CA.WA_Agent.jars.ext.serializer.jar:.opt.CA.WA_Agent.jars.ext.resolver.jar:.opt.CA.WA_Agent.jars.ext.qname.jar:.opt.CA.WA_Agent.jars.ext.opensaml.jar:.opt.CA.WA_Agent.jars.ext.json-smart.jar:.opt.CA.WA_Agent.jars.ext.json-path.jar:.opt.CA.WA_Agent.jars.ext.jaxrpc.jar:.opt.CA.WA_Agent.jars.ext.httpmime.jar:.opt.CA.WA_Agent.jars.ext.httpcore.jar:.opt.CA.WA_Agent.jars.ext.httpclient-cache.jar:.opt.CA.WA_Agent.jars.ext.httpclient.jar:.opt.CA.WA_Agent.jars.ext.commons-logging.jar:.opt.CA.WA_Agent.jars.ext.commons-lang3.jar:.opt.CA.WA_Agent.jars.ext.commons-discovery.jar:.opt.CA.WA_Agent.jars.ext.commons-collections4.jar:.opt.CA.WA_Agent.jars.e
    @
    ---------------- The end of the file ----------------


    Questions:
    1. Not sure why I get the "@" at the end of all output now
    2. agent_properties.log   In this log I see three class.path entries

    This path named "java.class.path" has the jars it needs

    java.class.path=.:/opt/CA/WA_Agent/jars/agent.jar:/opt/CA/WA_Agent/jars/appservices.jar:/opt/CA/WA_Agent/jars/commonsvc_log.jar:/opt/CA/WA_Agent/jars/commonsvc_transport.jar:/opt/CA/WA_Agent/jars/commonsvc_utility.jar:/opt/CA/WA_Agent/jars/commonsvc_webservice.jar:/opt/CA/WA_Agent/jars/database.jar:/opt/CA/WA_Agent/jars/dataservices.jar:/opt/CA/WA_Agent/jars/hadoop.jar:/opt/CA/WA_Agent/jars/informatica.jar:/opt/CA/WA_Agent/jars/installer.jar:/opt/CA/WA_Agent/jars/itpam.jar:/opt/CA/WA_Agent/jars/js.jar:/opt/CA/WA_Agent/jars/microfocus.jar:/opt/CA/WA_Agent/jars/oa.jar:/opt/CA/WA_Agent/jars/proxy.jar:/opt/CA/WA_Agent/jars/proxyjs.jar:/opt/CA/WA_Agent/jars/ps.jar:/opt/CA/WA_Agent/jars/sap.jar:/opt/CA/WA_Agent/jars/snmpagent.jar:/opt/CA/WA_Agent/jars/sql.jar:/opt/CA/WA_Agent/jars/webservice.jar:/opt/CA/WA_Agent/jars/ext/accessors-smart.jar:/opt/CA/WA_Agent/jars/ext/asm.jar:/opt/CA/WA_Agent/jars/ext/axis.jar:/opt/CA/WA_Agent/jars/ext/bcprov-ext-jdk15on.jar:/opt/CA/WA_Agent/jars/ext/castor-core.jar:/opt/CA/WA_Agent/jars/ext/castor-xml.jar:/opt/CA/WA_Agent/jars/ext/castor-xml-schema.jar:/opt/CA/WA_Agent/jars/ext/commons-cli.jar:/opt/CA/WA_Agent/jars/ext/commons-codec.jar:/opt/CA/WA_Agent/jars/ext/commons-collections4.jar:/opt/CA/WA_Agent/jars/ext/commons-discovery.jar:/opt/CA/WA_Agent/jars/ext/commons-lang3.jar:/opt/CA/WA_Agent/jars/ext/commons-logging.jar:/opt/CA/WA_Agent/jars/ext/httpclient-cache.jar:/opt/CA/WA_Agent/jars/ext/httpclient.jar:/opt/CA/WA_Agent/jars/ext/httpcore.jar:/opt/CA/WA_Agent/jars/ext/httpmime.jar:/opt/CA/WA_Agent/jars/ext/jackson-annotations.jar:/opt/CA/WA_Agent/jars/ext/jackson-core.jar:/opt/CA/WA_Agent/jars/ext/jackson-databind.jar:/opt/CA/WA_Agent/jars/ext/jaxrpc.jar:/opt/CA/WA_Agent/jars/ext/json-path.jar:/opt/CA/WA_Agent/jars/ext/json-smart.jar:/opt/CA/WA_Agent/jars/ext/mail.jar:/opt/CA/WA_Agent/jars/ext/ojdbc8.jar:/opt/CA/WA_Agent/jars/ext/opensaml.jar:/opt/CA/WA_Agent/jars/ext/qname.jar:/opt/CA/WA_Agent/jars/ext/resolver.jar:/opt/CA/WA_Agent/jars/ext/security:/opt/CA/WA_Agent/jars/ext/serializer.jar:/opt/CA/WA_Agent/jars/ext/sinetfactory.jar:/opt/CA/WA_Agent/jars/ext/slf4j-api.jar:/opt/CA/WA_Agent/jars/ext/slf4j-jcl.jar:/opt/CA/WA_Agent/jars/ext/wsdl4j.jar:/opt/CA/WA_Agent/jars/ext/wss4j.jar:/opt/CA/WA_Agent/jars/ext/xalan.jar:/opt/CA/WA_Agent/jars/ext/xercesImpl.jar:/opt/CA/WA_Agent/jars/ext/xml-apis.jar:/opt/CA/WA_Agent/jars/ext/xmlsec.jar:


    This path does not have them
    java.library.path=/opt/CA/WA_Agent/jre/lib/amd64/compressedrefs:/opt/CA/WA_Agent/jre/lib/amd64:/opt/CA/WA_Agent:/opt/CA/WA_Agent/jre/lib/amd64/server:/opt/CA/WA_Agent/jre/lib/amd64::/usr/lib64:/usr/lib


    sun.boot.class.path=/opt/CA/WA_Agent/jre/lib/amd64/compressedrefs/jclSC180/vm.jar:/opt/CA/WA_Agent/jre/lib/se-service.jar:/opt/CA/WA_Agent/jre/lib/rt.jar:/opt/CA/WA_Agent/jre/lib/resources.jar:/opt/CA/WA_Agent/jre/lib/jsse.jar:/opt/CA/WA_Agent/jre/lib/charsets.jar:/opt/CA/WA_Agent/jre/lib/jce.jar


    Which path is the SFTP Job type leveraging?


    It's like it using the wrong CLASSPATH or something?



  • 4.  RE: FTP Set Up on New Agent Can't Load JARS

    Posted Oct 01, 2020 03:20 PM
    Edited by David Lock Oct 01, 2020 03:21 PM