on 02-09-2010 1:55 PM
Hi,
Where I can see the log files for ISA application?
I want to see the log to get an idea on the application flow. What I mean is when a button is clicked I want to know what are the actions, java classes are been called till the request is sent to backend.
Please help me.
Regards
MQ
Hi there,
If you go to the XCM and select theloggin option you will be able to create a log in the application for your specific actions.
Go to
Select => logging
Start the application
When you want to start logging click the start logging button.
This will log all your actions to a file that you can view/downlaod.
Regards
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I cannot see the "Start logging" button after login into http://server:port/b2b/admin and selecting logging.
I can see only ReLoad, Create Configuration, Show FIles, Delete and Edit Config buttons in Logging.
One more doubt is I had a text box in the screen and it contains "com.sap.isa". Does it mean only the files having this namespace will be written to the log file.
Regards
MQ
Hi MQ!
As I know, you can't see "logging" tab since it showed only for applications with names "b2b", "b2c", "isauseradm", "shopadmin", and these names are hardcoded.
If you want to see tab "logging" you should do these:
1) open file logging.jsp from DC crmtcweb~core
2) search line
String supportedApps[] = {"b2b", "b2c", "isauseradm", "shopadmin"};
(or something similar). Position of this line should be 24 or near
3) add name of your application in this list, e.g.:
String supportedApps[] = {"b2b", "b2c", "isauseradm", "shopadmin", "b2b_mod"};
where "b2b_mod" is the name of your app:
http://server:port/b2b_mod/b2b/init.do
4) save file, rebuild and deploy your app
P.S.: may be this issue resolved in latest SPs of CRM 5.0.
I hope Mark Foley will read this message.
Regards, Lev
If, in the b2b_mod application's web.xml file, you have changed the context-parameter application.name, then you might get into these types of issues.
<context-param>
<param-name>application.name</param-name>
<!-- please keep <param-value>b2b</param-value> together in one line without blanks for build.xml copy targets -->
<param-value>b2b</param-value>
<description>Name of the web application. This value must not be
changed. It is used in XCM configuration files and for CCMS reporting.</description>
</context-param>
It says, "This value must not be changed. It is used in XCM configuration files and for CCMS reporting."
Hi Easwar!
I've checked our web.xml file. Parameter "application.name" didn't changed. There may be some some confusings since we have two things called "application name".
For example:
http://server:50000/b2b_mod/b2b/init.do
http://server:50000/b2b_mod/admin/index.jsp
To eliminate confusings let's call "b2b", "admin" etc a "subapplications". Then we have our modified application B2B_MOD which contains a set of predefined subapplications (B2B, B2C, ADMIN, ISAUSERADM and some more). Now I can say that parameter from web.xml mentioned by you regarding to the supapplications and of course cannot be changed. But in my previous post I've talked about applications. Please have a look at the extended fragment from logging.jsp:
String currApplication = request.getContextPath().toLowerCase().substring(1);
String supportedApps[] = {"b2b", "b2c", "isauseradm", "shopadmin"};
for(int i = 0; i < supportedApps.length; i++) {
if(currApplication.equals(supportedApps<i>)) {
sessionLogSupported = new Boolean(true);
break;
}
}
There is a checking a name of application rather than subapplication.
Sorry if my english was not so good. I've tried to make my post clear for understanding
Regards, Lev
Check this note Note 1090753 - Creation of logs for WebChannel/E-Commerce applications
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.