The CA IAM CS framework reads the metadata provided for an endpoint type. The framework learns the data model from the metadata for the connector and configures how each object class and attribute are processed. Object classes and attributes which are mentioned in requests to a connector instance, for which there are no connectorMapTo* settings, are logged and discarded.
This allows the connector's implementation's coverage to be built incrementally, especially when porting an existing C++ connector to Java.
Some client applications, for example, the Provisioning Server, pass on some attributes to the CA IAM CS even though they are not relevant to CA IAM CS. You can configure the acceptedUnknownAttrIds property in connector.xml to list the names of attributes which are not relevant to the connector implementation, and are not logged when received. Also, the setting acceptedUnknownAttrIds in server_jcs.xml specifies attributes global to the whole CA IAM CS, rather than a specific connector.
A message is logged at the INFO level to jcs_daily.log for each object class, summarizing all its attributes which are mapped in metadata, for example:
INFO - class='eTDYNGroup': all mapped attributes=eTDYN-int-01;eTDYNMember [expensive];eTDYNGroupName;eTDYN-str-01
The syntax chosen for the list in the message lets you cut and paste into the list of requested attributes in JMeter search tests after qualifications in square brackets have been deleted. For example [expensive] in the preceding expression.
|
Copyright © 2013 CA.
All rights reserved.
|
|