21B Monthly Release 1 : Deployment Debug Log

The final (public) feature released in Oracle Intelligent Advisor 21B Release 1 that we are going to look at is something for administrators. For some time now, those involved in interview deployments that have a degree of complexity have been leveraging external tools to find ideas for tracing what is going on with deployments and interview execution. Enter the Deployment Debug Log!

The 21B Monthly Release 1 reveals that now we have some internal tools to be able to get valuable feedback about our interview once it is deployed. We should take into account that this functionality is not designed to be left running for ages – it has a maximum of 12 hours per activation. The content of the log can be accessed by a new administrative page in the Oracle Intelligent Advisor Hub, for review offline. So here is the walkthrough of how to enable and take advantage of the new feature.

After navigating to the Deployment you want to activate this for, click the little hamburger menu on the right hand side, and select the new “View Debug Log” (View Action Log has been there for a while). You will find yourself here:

Deployment Debug Log - Activation

As you can see, the history section is empty. In due course, this will show the different instances of data that represent your interview executions.

As mentioned above, there is a time limit to the logging, and one should consider that the information is potentially sensitive since it contains any values provided by the end user.

Deployment Debug Log - Icon

Once you save those changes you will notice the new icon on the deployment summary page, shown above, to remind you of the debug log activation status. Now you just wait until the project is used. So the project I used is shown below. It includes an extension or two.

The session includes the option to download the complete log, which is a Zip file containing different files for each interaction. This is available from the Summary page shown below:

Deployment Debug Log - Review

The file looks a little like this example, with each screen shown:

The files use a quite familiar structure, in XML presenting the session data. An example is shown below, based on the example I used above.

Deployment Debug Log - Output

Since this feature is likely to generate a certain volume of data in these files, you will not be able to switch this feature on if the debug log is “full”. The online documentation tells us that you will have to delete some logs or use the Delete All button to remove them all.

Richard Napier

Author: Richard Napier

After 8 years in case management and ERP software roles, Richard Napier joined Siebel Systems in 1999 and took up the role of managing the nascent Siebel University in Southern Europe. He subsequently was Director of Business Development and Education for InFact Group (now part of Business & Decisions) for 8 years. He now runs Intelligent Advisor IT Consulting OÜ. Owner of intelligent-advisor.com, he also is Co-Founder of the Siebel Hub.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Intelligent Advisor IT Consulting Serving Customers Worldwide
Hide picture