I am working with the BizTalk JDE adapter, and this is a very handy feature. A couple of times already I was just stuck, but examining the trace logs gave me the additional information I needed to troubleshoot my error. I do not have a lot of experience with tracing, so it took me a bit to catch on to exactly how it works.
The documentation is here. Here are my exact steps:
- Download and install the Windows Server 2003 Platform SDK (google it to find the version you need–I was developing on Windows Server 2003). All you really need is one file–tracelog.exe
- Copy tracelog.exe to your adapter installation directory. Mine was C:Program FilesMicrosoft BizTalk Adapters for Enterprise ApplicationsJ.D. Edwards EnterpriseOne(r)Bin
- Open a command prompt and go to that same directory. Run the command BTAJDEEnterpriseOneTrace.cmd -transmitter -start. This uses tracelog.exe to start a trace.
- Run whatever BizTalk-to-JDE process is giving you problems.
- From the command prompt again, run the command BTAJDEEnterpriseOneTrace.cmd -transmitter -stop to stop the trace.
- Run the command tracerpt C:rtlog.etl -o C:log.csv, where C:log.csv is where you want your report to go.
- This is now a CSV file containing much more information than what the adapter sends to the event log. I opened Excel and imported the data to make it more readable.
Hi, there
This is very nice post. Recently, I am studying BizTalk JDE adapter and then I found your blog. Have you encountered the error as below ?
E-JDE0036: Failed to start Java virtual machine. Missing or invalid JRE
Like you said, I was just stuck. Do you have any comments for this?
Thanks, Ark
It’s been a while, but yes, I think I did run into that problem. If I remember correctly, you have to configure the adapter with a path to the JRE. If you have Java installed on the machine, you will need to configure your path correctly.
Thanks for your comments. Finally, I have solved this problem due t0 64 bit OS. When I run on 32 bit OS. The error has been gone.