Reading the Provisioning Server's etanotify log

book

Article ID: 130388

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal

Issue/Introduction



How can I read the Provisioning Server's etanotify log?

Environment

Release:
Component: IDSVA

Resolution

For troubleshoooting of problems it is recommended to have the Provisioning Server's Notification Log set to Level of DEBUG. This is configured within the Provisioning Manager under the System\Identity Manager Setup settings and is written to the etanotify log file on the Provisioning Server.

When reviewing the etanotify log the first column represents the date and the second column represents the time. The third colum is the thread ID (i.e. TID).

In the below example we see that there was a Modify of a Provisioning User originally performed on 4/2/2019 at 11:40:38 but that we are not sending it to the IM Server until 11:47:36 as the inbound notifications are not a real-time system. We can see that the modify was to change the Provisioning User's eTTitle value from Old_Title to New_Title and it was sent to the IM Environment called identityEnv which is hosted on IM_HOST on port 8080 and that the IM Server accepted the inbound notification successfully and that the notification was deleted from the Provisioning Repository's notify DSA.

20190402:114736:TID=001e54:I: Sending Notification: eTNotifyOpID=1be19222-336e-4936-9cd6-99c282bf7610
20190402:114736:TID=001e54:I:   Event: Modify_Global_User (eTGlobalUserName=testuser)
20190402:114736:TID=001e54:I:   SeqNo: 0000000001
20190402:114736:TID=001e54:D: Payload: 
20190402:114736:TID=001e54:D: <Request>
20190402:114736:TID=001e54:D:   <Id>1be19222-336e-4936-9cd6-99c282bf7610</Id>
20190402:114736:TID=001e54:D:   <ParentId></ParentId>
20190402:114736:TID=001e54:D:   <RootOperationID>ee96a7c5-ca78-45f9-93f4-8167e6c9ce04</RootOperationID>
20190402:114736:TID=001e54:D:   <StartDateTime>2019-04-02 11:40:38</StartDateTime>
20190402:114736:TID=001e54:D:   <EndDateTime>2019-04-02 11:40:38</EndDateTime>
20190402:114736:TID=001e54:D:   <ServerName>IMPS_HOST</ServerName>
20190402:114736:TID=001e54:D:   <DomainName>im</DomainName>
20190402:114736:TID=001e54:D:   <AdminUser>[email protected]</AdminUser>
20190402:114736:TID=001e54:D:   <Action>Modify_Global_User</Action>
20190402:114736:TID=001e54:D:   <ActionMsg>Modify Global User</ActionMsg>
20190402:114736:TID=001e54:D:   <ObjectClass>eTGlobalUser</ObjectClass>
20190402:114736:TID=001e54:D:   <FriendlyName>testuser</FriendlyName>
20190402:114736:TID=001e54:D:   <DN>eTGlobalUserName=testuser,eTGlobalUserContainerName=Global Users,eTNamespaceName=CommonObjects,d
20190402:114736:TID=001e54:D:+c=im</DN>
20190402:114736:TID=001e54:D:   <Attribute>
20190402:114736:TID=001e54:D:     <AttrName>eTTitle</AttrName>
20190402:114736:TID=001e54:D:     <ModOp>Replace</ModOp>
20190402:114736:TID=001e54:D:     <PreviousValue>Old_Title</PreviousValue>
20190402:114736:TID=001e54:D:     <Value>New_Title</Value>
20190402:114736:TID=001e54:D:   </Attribute>
20190402:114736:TID=001e54:D:   <Attribute>
20190402:114736:TID=001e54:D:     <AttrName>eTUseOperationID</AttrName>
20190402:114736:TID=001e54:D:     <ModOp>Replace</ModOp>
20190402:114736:TID=001e54:D:     <Value>ee96a7c5-ca78-45f9-93f4-8167e6c9ce04</Value>
20190402:114736:TID=001e54:D:   </Attribute>
20190402:114736:TID=001e54:D:   <Status>Success</Status>
20190402:114736:TID=001e54:D:   <Message>:ETA_S_0005&lt;MGU&gt;, Global User 'testuser' modified successfully</Message>
20190402:114736:TID=001e54:D: </Request>
20190402:114736:TID=001e54:D: Generating authentication code...
20190402:114736:TID=001e54:D: Sending Payload (975 bytes)...
20190402:114736:TID=001e54:D: Encrypting Payload...
20190402:114736:TID=001e54:D: Sending EncryptedPayload (1304 bytes)...
20190402:114736:TID=001e54:I: Try sending payload to http://IM_HOST:8080/iam/im/ETACALLBACK/?env=identityEnv
20190402:114742:TID=001e54:D: Received Response Payload: 
20190402:114742:TID=001e54:D: <eTExitReturn>
20190402:114742:TID=001e54:D:   <eTExitReturnCategory>SUCCESS</eTExitReturnCategory>
20190402:114742:TID=001e54:D:   <eTExitLogMsg>1982855a-ddceae43-3e07670e-69cdd1</eTExitLogMsg>
20190402:114742:TID=001e54:D:   <eTExitContinue>TRUE</eTExitContinue>
20190402:114742:TID=001e54:D:   <eTExitCustom></eTExitCustom>
20190402:114742:TID=001e54:D:   <eTPersistentFailure>FALSE</eTPersistentFailure>
20190402:114742:TID=001e54:D: </eTExitReturn>
20190402:114742:TID=001e54:I: SUCCESS: Payload sent successfully
20190402:114742:TID=001e54:D: Deleting notification.
20190402:114742:TID=001e54:D: Notification processed successfully: eTNotifyOpID=1be19222-336e-4936-9cd6-99c282bf7610,dc=verke01-S120
20190402:114742:TID=001e54:D:+38,dc=notify,dc=etadb
20190402:114742:TID=001e54:I: DONE: Notifications Processed: 1/1+