Deploy Plugins or Resources Without CV apps Packager

Using CV apps packager is the best solution to copy a single host installation from one host to another. If you only need to replicate core plugins or mashup plugins, you can also use the following procedures.

This page discusses:

Deploy Exalead CloudView Core Plugins to Another Host
Deploy Mashup Plugins to Another Host

Deploy Exalead CloudView Core Plugins to Another Host

You may want to deploy your custom core components only, packaged as CVplugins, to another host.

These components can be:

Connectors
Document Processors
Meta Processors
Prefix Handlers
Push API Filters
Query Processors
Security Sources

For more information, see Packaging Custom Components as Plugins in the Exalead CloudView Programmer's Guide.

Deploy Mashup Plugins to Another Host

You may also want to deploy your custom Mashup UI components, packaged as mashup plugins, to another host.

These components can be:

Widgets
Feeds
Feed Triggers
Mashup Triggers
Pre-Request Triggers
MEL Functions
Security Providers

Deploy All Mashup Plugins

You can generate a standalone .war file (embedding the 360 mashup configuration) as you want to deploy the Mashup UI outside of the Exalead CloudView environment, on another server.

For more information, see Generate WAR Files for Heavy Customization in the Exalead CloudView Mashup Programmer's Guide.

Deploy a Specific Mashup Plugin

You can use the plugin-cli.sh script located in <INSTALLDIR>/sdk/java-mashupui/project.

For example, to install a myplugin.zip file on the <DATADIR> located in mydatadir, for the default application on the mu0 mashup-ui service:

./plugin-cli.sh --cmd install --app-id default --data-dir /mydatadir/ --mashup-ui-service
mu0 myplugin.zip

Run this command on all the hosts on which you want to deploy the plugin.