i m using CA APM 9.5 when i m trace the transaction through CEM it show me unspecified user.
if any body face this problem please suggest what is the issue....
It is so because you must have defined your Domain application type to be "E-Commerce". If you wld have defined it "Enterprise" it would have shown you the user group \ new user.
Let me know if you need more clarifications.
It could be your session timeout is low , APM never sees the session identifier. See my tech note for more details (Below)
Untanglingthe Unspecified User Issue
ConsultingArchitect, Wily Professional Services
Table of Contents
Acommon problem is getting an “unspecified user” in CEM reports. This document reviewsthe unspecified user problem and some common ways to resolve this issue.
What is the Unspecified UserProblem?
The unspecified user message typically lookslike shown below:
While displaying login name or user group ina defect list, an unspecified user(s) appears instead of the actual user name.
Have an unspecified user has the followingdisadvantages:
An important note:There are various times when receiving an unspecified user message may be
the expected result.An example is an e-commerce website has no login process.
The following are typical causes ofunspecified user
How to Fix
Easy/Hard to Detect
Session Identifier Issues
Invalid or missing session identifier means CEM cannot differentiate user sessions and identify users. This also impacts the binding of the various transaction hierarchy elements.
-Correct text/case in session identifier.
- Add or use another session identifier.
- If no session cookie is available add a port number (Such as for NTLM Authentication and Service Desk without cookie templates)
Application Type Issues
Incorrect application type impacts the type of session identifier used. See session identifier for reasons why this is happening
-Choose correct application type (such as Siebel instead of general)
Authentication Type Issues
Authentication type impacts the type of session identifier used. See session identifier for reasons why this is happening
- Choose correct authentication type (such as NTLM instead of Basic)
If a defect happens in the login process, before the user is logged in, there will be no user identification
Turn off defect specifications’ before login or set expectations there will be no users for pre-login defects.
Session Timeout Issues
The user is at a remote location that needs a longer period of time for a session
Or session timeout is shorter than time needed to login/for a session.
Increase session timeout. (60 minutes by default).
You can also set the session timeout on the TESS in a file called tess-default.properties. It is under /etc/wily/cem/tess/tomcat/webapps/wily/WEB-INF/classes/ Here are the relevant lines: # when session info is aged out session.ageoutAfter_Mins=60
For the remote location issue:
Change it to a high value - say 1800 which is equal to 30 hours.
Remember to restart the TESS after you make this change.
Redirect to External URL
Users are authenticated are initially seen but an external redirect link is clicked.
Once clicked, you can see the transaction but lose the user to session information
Increase session timeout.
Use an internal link
This may be in the application/network realm and may not be possible to solve.
Thanks for Ahana Aman Tur, Joerg Mertin forfeedback on what to include in this document.
Thanksto Seth Hammerman, Clayton Johnson, Gautaum Malchandari, and Japeth Ko forpreviously providing notes on this topic on the Wily CEM mailing list.