Deployer 10.7 | Deploying Assets from Source webMethods Runtimes | About Runtime-Based Deployment
 
About Runtime-Based Deployment
Deprecation Notice: Beginning with release version 10.5, runtime-based deployment is deprecated. Software AG recommends that you use the Asset Build Environment and repository-based deployment instead.
In runtime-based deployment, you deploy assets directly from webMethods source runtimes to target runtimes.
The following webMethods runtimes support runtime-based deployment:
*webMethods Brokers.
*Integration Servers, including hosts for Trading Networks Servers.
*My webMethods Server.
*Process Engine (BPM) runtimes (an Integration Server that hosts the webMethods Process Engine and executes business processes)
*Optimize runtimes (an Integration Server that hosts the Optimize Analytic Engine).
You can deploy user-created assets using Deployer. You cannot deploy system components that were installed by the Software AG Installer as part of a product installation. For example, you can deploy Integration Server packages that were created by users, but you cannot deploy Integration Server system packages that were installed, such as the WmPRT package (Process Engine). If you want such components on target servers, you must install them using the Software AG Installer. However, you can partially deploy system (Wm*) packages for some webMethods adapters, such as the adapter packages for WmAS400, WmSAP, WmJDBCAdapter, and WmMQAdapter. In partial deployment of system packages, configurations or artifacts that reside in the system packages on the source server can be deployed to the target server. To determine if system packages can be partially deployed for a particular product, refer to the product documentation.