Automic Workload Automation

 View Only
  • 1.  Can't see the Web Service tab on both JOBS and CONN

    Posted Dec 30, 2019 12:45 PM
      |   view attached
    hello,

    I feel this question is weird but would like to ask for your help anyway.

    We are using a WebService object to send sms.

    Atm, we need to update some of the details and from some reason when we go to the WS job, we don't see the WebService tab.

    Same in the connection object.

    Attached you can see the objects – JOBS and CONN and screenshots of the objects as we see them.

     

    Is someone familiar with this issue?

     

    Many thanks,

    Ella

    Attachment(s)

    zip
    forbroadcom.zip   67 KB 1 version


  • 2.  RE: Can't see the Web Service tab on both JOBS and CONN

    Broadcom Employee
    Posted Jan 02, 2020 03:46 AM
    Hi,
    please check the permissions of your Automic user. Looks like it is missing read permissions to the client 0 store object UC_ECC_PLUGINS. Please refer to following page in documentation:
    https://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#AWA/AdministrationPerspective/AG_MinRequiredAuthorizations.htm#link3

    Regards, Markus


  • 3.  RE: Can't see the Web Service tab on both JOBS and CONN
    Best Answer

    Posted Jan 02, 2020 03:47 AM
    Hi.

    Missing tabs with RA agents are often caused by using the wrong RA agent version. There used to be (and probably still is) a "noweb" package of the RA agent available for download, which is for "classic​" installations using the Java client. And a "non-noweb" package with no particular suffix which is for installations using AWI. If you recently switched to a server that requires the use of AWI as the interface (12.x) you probably need to swap out or update your RA agent package. Also update the RA agent solution for good meassure.

    Hth,


  • 4.  RE: Can't see the Web Service tab on both JOBS and CONN

    Posted Jan 08, 2020 03:44 AM
    Sometimes just uninstalling and reinstalling the RA solution will fix this problem. Make sure you're using the most recent version of the RA Core agent too.