Dear all,
if you have sophisticated Mapping you have sometimes to write your ouwn mapping service in java to supplement the XI-Standardmapping functionality. Developing your own java source is done
with an external Java-IDE like eclipse. You can test its functionality local and when it ist ok you pack it into an archive an use it as a seperated Step in XI-Mapping.
Even if you have testet on your local environemt your could got Error when runnen in XI. So now how to find out what's going wrong. The best way is to debugg the source code like debugging an abap in R/3. But how can one debug the java code while the interface is running? How can a break point be stoped?
Have anyone done debugging in XI with java code already? Is it possible? Any idea will be wellcome.
thanks in advance.
Ly-Na Phu
2 Answers
-
Former MemberPosted on Mar 19, 2004 at 01:23 PMLy-Na Phu,
I took the input message from XI and used Stylus Studio (from Sonic software) to debug the XSLT and the Java code used within the XSLT. Watch out however: XI Stylus Studio is somewhat limited on invoking underlying Java code (only static).
Good lucl. Guy Crets
Add comment
-
Former MemberPosted on Mar 19, 2004 at 02:49 PM
Hi!!!
I don't know if logging into the standard log is a solution for you.
You can check it at Exchange Infrastructure: Monitoring --> Integration Engine --> Monitoring --> Monitor for Processed XML Messages.
Here is a template:
public class YourMapping implements StreamTransformation {
(...)
private void logInfo(MappingTrace trace, String msg) {
if (trace != null)
trace.addInfo(msg);
}
private void logWarning(MappingTrace trace, String msg) {
if (trace != null)
trace.addWarning(msg);
}
(...)
public void execute(InputStream in, OutputStream out) {
(...)
MappingTrace trace = (MappingTrace) m_param.get(
StreamTransformationConstants.MAPPING_TRACE);
(...)
logInfo(trace, "Here is my info...");
(...)
logWarning(trace, "Here is my warning...");
(...)
}
}
Have a nice day,
Mariusz
Add comment
Add comment