Configuring oXygen debugger with MarkLogic?

[feickertmd]

I have tried using oxygen debugger to work on my MarkLogic modules. I am new to ML, so I do not fully understand the relationship between the HTTP source and the XDBC source, but I followed what was done in the oxygen video tutorial. The video glossed over a lot of detail, and I sit still wondering how you actually set up a debug connection. To boot, the documentation explains very little.

Anyone who had worked with this setup, please let me know what I need ot do in terms of selecting a data source, setting up validation scenarios, etc. so that I can make use of this great integration!

[alex_jitianu]

Hello,

So you are trying to do what we call a Remote debugging which means intercepting an HTTP request on the server and debug it in Oxygen. In this type of scenario there are two AppServers involved:
1. The HTTP server that normally receives requests and executes XQuery
2. An XDBC server that Oxygen will use to send queries and to intercept and control the debugging. This server is the one to set when Configuring the MarkLogic connection in Oxygen.

An AppServer has a modules setting that controls where the XQuery modules are located. Another important setting is called root which is like a prefix for the modules. They both control where the modules are searched for and how the URI that identify the XQuery should look like. A good read on how a module is being identified is Rules for Resolving Import, Invoke, and Spawn Paths. It's also good to know the concepts of Library Modules and Main Modules in MarkLogic.

For the Remote debugging, both the HTTP and XDBC AppServers should have the same modules set.

In MarkLogic you can inspect the AppServers on port 8001 (for example: http://my.server.com:8001) and make sure they have the same modules and root configuration.

Best regards,
Alex