Exalead Eclipse plugin is a tool to easily develop plugin for CloudView Mashup UI and Platform.
/!\ Please note that you need to have Eclipse Indigo 3.7 or higher to use this plugin /!\
Congratulations, the Exalead Eclipse development plugin is now ready to use!
To create a project:
Note: The Fetch libraries feature is not compatible with CloudView dev instances.
Select Window > Preferences > Exalead and click:
Note: To specify a Host, enter its name directly, do not precede it by http://
Set Window > Preferences > Exalead > CloudViewTM Mashup and click:
From the toolbar, use the Exalead Tools button to interact with your plugin.
From the toolbar, click the Exalead tools button and select CloudViewTM Mashup >
To package your plugin with classes and export it as a zip file on a selected path.
To package your plugin with classes that you want to export and deploy it automatically on the selected CloudView instance.
To list the deployed plugins for a selected CloudView instance.
You must then select the plugins you want to remove and click Finish.
To list the deployed plugins for a selected CloudView instance.
Then, you can retrieve plugins from the selected CloudView instance and deploy it on another one (locally or remotely).
To retrieve dependencies from a running CloudView instance, set classpath and javadoc locations.
To create a new Mashup-UI Eclipse project using a specific Mashup-UI SDK, previously defined in Window > Preferences > Exalead > CloudView Mashup, and link it to a CloudView instance.
When the Mashup-UI Eclipse project is created, you can right-click it in the Package Explorer panel, to access CloudView Mashup contextual options.
For example, to develop custom widgets, you can access the Widgets and the Tag libraries documentations.
You can also link your Mashup UI SDK to another CloudView instance using the Generate development configuration option.
From the toolbar, click the Exalead tools button and select CloudViewTM Core >
To package your plugin with classes and export it as a zip file on a selected path.
To package your plugin with classes that you want to export and deploy it automatically on the selected CloudView instance.
To list the deployed plugins for a selected CloudView instance.
You must then select the plugins you want to remove and click Finish.
To retrieve dependencies from a running CloudView instance, set classpath and javadoc locations.
CAUTION: The debugging functionality presented here applies to V6R2014.SP1 or higher.
The Eclipse Plugin allows you to debug the code of custom* connectors on-the-fly (* not included in the Administration Console Help > About > Built-in plugins list).
Once a custom connector contained in an Eclipse project is deployed on a CloudView instance, you no longer need to redeploy it each time you change its source code.
Activating the connector debugging functionality in Eclipse creates an RScan (RemoteScan) built-in connector in the Administration Console.
This new connector acts as an RScan client that sends scan orders to the RScan server. The RScan server sources are located in the datainteg-java-commons JAR file, and retrieved by the Eclipse plugin when you launch a Fetch libraries from instance action.
Each debug session has its own RScan server, running on the port specified in the debug configuration parameters.
In the end, when you launch any type of scan operation from the Administration Console, the order is sent to the RScan server which launches the scan of your source connector in Eclipse.
com.exalead.papi.connector.Myconnector