Release Notes › Known Issues › Traffic Limits for Usage Data

Traffic Limits for Usage Data

In this release, CA RCM polls a CA Enterprise Log Manager instance in your environment for resource usage data, and presents that data when you review or certify access privileges. When CA RCM reports usage for a large time period, or when a large number of resources are tracked, polling CA Enterprise Log Manager generates a high volume of usage data. Traffic on the CA Enterprise Log Manager server increases, and the time interval for synchronizing usage data is lengthened.

Note: High traffic also impacts the time it takes to display detailed usage information when users click a usage icon during the access certification process or in the entity browser. In this case, a separate window opens in CA RCM, but the usage data make take significant time to load.

If synchronization takes too long or times out, try the following troubleshooting steps.

1. When you implement usage data in a universe, set the time periods for usage data to cover a shorter time frame. This will decrease the synchronization time. The values of the Time Period fields should not exceed the following default values:
   • Short: 7 days
   • Medium: 15 days
   • Long: 30 days

     Note: Configure CA Enterprise Log Manager to retain data for the maximum time period, as specified in the Long field.

2. If time periods are minimized, but timeouts persist, change the value of the following system property to suit the size of the CA RCM data universe and your operating environment:

   usage.import.logmanager.odbc.timeout.seconds

   Defines the waiting period for data queries from CA RCM to CA Enterprise Log Manager. Increase the value of this property to support a higher volume of queries. When the volume of traffic at the CA Enterprise Log Manager server is high, use values of an hour (3600 seconds) or more.

Note: For more information about implementing CA Enterprise Log Manager usage data in CA RCM, refer to the Portal User Guide.