Using Developer Tools

Mashup Builder includes several tools that can be useful to develop and debug your own search applications.

This task shows you how to:

Monitor the Developer Area status

  1. In Mashup Builder, click Application and select Developer area.
  2. Look at the Overview section.

    The tab displays a list flagging the various indicators status.

    Note: You can click Refresh to get up-to-date status views.

  3. From the Actions section, click Check global configuration to display the elements that are not configured as expected for production.

Develop and work on a non-packaged Mashup UI

Before you begin: To test your custom components (widgets, feeds, etc.) in a development environment like Eclipse, it is very useful to define a workshop Mashup UI. It allows you to test your components before deploying them on your Exalead CloudView instance.
  1. In Mashup Builder, click Application and select Developer area.
  2. In Mashup UI URL, enter the URL of your workshop Mashup UI.

Switch to Debug mode

  1. In Mashup Builder, click Application and select Developer area.
  2. In the Mashup UI section, select Mashup UI debug mode.

    Results:

    • The Messages panel displays that The Mashup UI is currently in debug mode.
    • On the Mashup UI, a Debug bar appears at the bottom of your search application pages.

Use the Mashup UI Debug tools

When the Development mode is on in the Mashup Builder, the Mashup UI displays a Debug bar at the bottom of your search application pages.



Context:

Click

to...

l18N

Highlight the internationalization elements.

1. Select the language for which you want to edit the internationalization.

2. Hover above highlighted elements to see and edit the text that can be translated.

Editing the text through the interface updates the MashupI18N.xml file, then, when I18N is reloaded it:

  • (For edits on a specific language only) creates an application_{lang}.properties file.
  • (For edits on ALL languages) edits the application.properties file.

See also Manage I18N for multiple applications.

Important: Do not modify the application.properties file directly!

Widgets

Highlight the various widgets used in the page. When you hover over one of them, you can see:

  • its name (as defined in the widget.xml files) and WUID
  • the path of its JSP file template
  • the feeds it uses

Templates

Highlight the various JSP components used in the page.

When you hover over one of them, you can see its full path. This saves time to find the JSP that must edited for a given component.

Timeline

Open a reporting screen if Reporting was enabled in the Mashup Builder in Application > Application Properties menu, and/or in Application > API Properties:

  • The mashup-ui-reporting collects data relative to task execution and to CPU activity on the Mashup UI. For example, when a user queries a page, the reporter retrieves data such as the execution and CPU time of pages, widgets and triggers.
  • The mashup-api-reporting reporter collects data relative to feeds, subfeeds and triggers execution. This reporter allows you to understand explicitly the feed execution process, with subfeeds and triggers and to identify possible problematic issues.