Deployer 10.7 | Deploying Assets from Source webMethods Runtimes | Adding Assets to Broker, ProcessModel, My webMethods Server, or Optimize Deployment Sets
 
Adding Assets to Broker, ProcessModel, My webMethods Server, or Optimize Deployment Sets
 
Removing Process Models from a Deployment Set
Based on which product assets go into the deployment set, you should consider the following before adding assets to the set:
*Deployer cannot display more than 2500 assets at once, so it might not display all assets. Software AG recommends displaying smaller sets of assets and creating smaller deployment sets. When creating a deployment set with My webMethods Server assets, the Root folder aliases field in the MWS Server configuration (see Connecting to My webMethods Server) controls the Page assets that are displayed for each My webMethods Server. By default, this field is set to folder.public. If your Public Folders and its subfolders contain hundreds of pages, displaying these assets can take a long time. To deploy smaller sets of assets, change the Root folder aliases field to specify a folder that is deeper within the Public Folders hierarchy and create a deployment set for those assets.
*When deploying BPM process models, Deployer copies the generation receipt from the source environment to the target environment. Because the logical-to-physical server mapping might contain old data, the regeneration process connects to the previous logical server and cleans up the process-related assets there (for example, deleting associated triggers and services), in addition to creating the new assets on the new logical server. With no generation receipt, this mapping information is not available and the clean-up procedure cannot occur. If you deploy multiple versions of the same process model in a single deployment set and configure the deployment set to enable both processes on the target, the version that is deployed to the target last is the one that is enabled. Use webMethods Monitor to ensure that the proper version is enabled in the target environment.
*To add assets to Broker, ProcessModel, MWS, or Optimize deployment sets
1. In the Deployment Sets area, under the deployment set to which to add assets, click the Broker, ProcessModel, MWS, or Optimize folder. In the right-hand pane, Deployer lists the source servers of the type you selected.
2. In the right-hand pane, open the tree to show the assets on the source servers, then select the check box next to each asset to add to the deployment set. Keep in mind the following:
For...
Note
ProcessModel
The process models displayed are those that were "Built for execution" on the Integration Server.
MWS
The My webMethods Server folder is listed twice within its directory, as a container preceded by and as an asset preceded by . If you want to add a folder with all the assets it contains to the deployment set, select the folder where it appears next to the square icon. If you want to add individual assets in the folder without adding the folder itself, open the folder where it appears as a container and click the assets to add.
3. Click Save. Deployer shows the selected assets in the left-hand pane under the Broker, ProcessModel, MWS, Optimize, or Business Rules folder for the deployment set.