10 docs tagged with "extension"

You can extend the Deploy plugin for JBoss Enterprise Application Platform (EAP) 6 and JBoss Application Server (AS)/WildFly 7.1+ using the Deploy plugin API type system and Jython.

The Deploy GlassFish plugin is designed to be extended through the Deploy plugin API type system and Jython. The plugin wraps the GlassFish command-line interface (CLI) with a Jython runtime environment, so that extenders can interact with GlassFish and Deploy from the script. The Jython script is executed on the Deploy Server and has full access to the following Deploy objects:

You can extend the IBM WebSphere Application Server (WAS) plugin through Deploy's plugin API type system and using custom, user-defined Python scripts.

You can extend the IBM WebSphere MQ (WMQ) plugin using the Deploy plugin API type system. And because the WMQ plugin is built on top of the Generic plugin, you can also add support for new types using Generic plugin patterns.

You can extend the JBoss Application Server plugin using the Deploy plugin API type system. And because the JBoss plugin is built on the Deploy Generic plugin, you can also add support for new types using the Generic plugin patterns.

You can extend the Deploy Oracle WebLogic (WLS) plugin using the Deploy plugin API type system and by using custom WebLogic Scripting Tool (WLST) Python scripts.

The Apache Tomcat plugin for Deploy is designed to be extended through Deploy's plugin API type system. For more information about this plugin, see Apache Tomcat plugin.

Implementing custom input/output formats

After you synchronize plugins on a Deploy satellite, the satellite must be restarted. For more information, see Synchronize plugins with a satellite server.

If you add, remove, or update a Deploy plugin or extension, you must synchronize Deploy with satellite servers before performing a deployment.