The following article is a compilation of logging options that exist for Embedded Entitlements Manager.
Embedded Entitlements Manager, also known by the acronyms EEM, EIAM, or ETEIAM, is a backend component that is used by multiple products to facilitate authentication. The component reads from either its own LDAP implementation, known as CA Directory, or can plug into a 3rd party LDAP Server, from which authentication and application permissions may be defined.
Various products which leverage EEM, including:
CA Service Catalog
CA Service Management - Service Desk Manager
CA Process Automation
CA IT Asset Manager/Asset Portfolio Manager
CA Workload Automation AE - Scheduler (AutoSys)
Not able to bind EEM to LDAP, userstore status shows up with Red (bind failed):
This article covers how to enable EEM logging/tracing when EEM is unable to connect with an LDAP external userstore
How to enable EEM server TRACE logging to diagnose EEM performance issues?:
Tracing for EEM performance concerns
The following logging may be used to trace the calls that a given product, such as Service Desk or Autosys may use to interact with EEM. There is usually an eiam.config file on the calling product side that needs to be configured, plus other config files, depending on the calling product.
How to enable logging to capture the calls sent to Embedded Entitlements Manager (EEM):
Used to diagnose EEM SDK calls that are made as part of the Service Desk integration.
Enable EEM SDK Debug Logging in AutoSys Web UI:
Used to diagnose EEM SDK calls that are made as part of the Autosys integration.
How to enable debug/tracing for AutoSys EEM integration:
Similar article also available to diagnose EEM SDK calls that are made as part of the Autosys integration.