DX Application Performance Management

  • Private Community
 View Only

  • 1.  Using EEM with APM 10 & Team Center Custom Attributes

    Broadcom Employee
    Posted Aug 25, 2015 02:15 AM

    Just a quick heads up that there appears to be a problem with EEM authorisation for the "admin" user to be able to add Custom attributes or Attribute nodes in APM Team Center

    Until a fix is available to workaround the problem please retain the "Local Users and Groups" realm in the realms.xml file as that enables the required authorisation after EEM authenticated login.

    APM Team Center

     

    Thank-you



  • 2.  Re: Using EEM with APM 10 & Team Center Custom Attributes

    Broadcom Employee
    Posted Aug 25, 2015 05:10 PM

    There are also some issues with Logout button not functioning properly for EEM authenticated/ authorized users. In this situation, logging into Webview and logging out the EEM based user will successfully log this user out of both Webview and ATC.



  • 3.  Re: Using EEM with APM 10 & Team Center Custom Attributes

    Broadcom Employee
    Posted Aug 25, 2015 06:15 PM

    Thanks Tom. I saw similar but thought I had a browser glitch



  • 4.  Re: Using EEM with APM 10 & Team Center Custom Attributes

    Broadcom Employee
    Posted Sep 08, 2015 06:39 PM

    I have also created a new KB for this problem with more advice on the workaround:

    In APM 10.0 using EEM authentication/authorization when login to Team Center as the "admin" user it is not possible to to add Custom attributes or Attribute nodes.



  • 5.  Re: Using EEM with APM 10 & Team Center Custom Attributes

    Posted Oct 15, 2015 04:29 PM

    Did this get fixed in APM 10.1?

     

    Thanx



  • 6.  Re: Using EEM with APM 10 & Team Center Custom Attributes

    Broadcom Employee
    Posted Oct 15, 2015 05:26 PM

    Hi Steve,

    It is not listed in the 10.1 Fixed Issues list (File Fixed-Issues_277862177.html inside bookshelf file GEN09091117E.zip under Download Center for APM 10.1).

    However I have checked the relevant internal Defect #376645 and it should definitely be fixed in 10.1

    Regards,

    Lynn