Dynamic Apps Platform : webMethods BPM Process Development Help : Building and Uploading Processes : About Building and Uploading a Process : About Building and Uploading with the Command-Line Utility
About Building and Uploading with the Command-Line Utility
You can build and upload Designer processes with a command-line utility, available at Software AG_directory \Designer\util\buildUploadProcess.bat on Windows systems, and at Software AG_directory /Designer/util/buildUploadProcess.sh on UNIX-based systems.
Important:  
When you generate a process model with the command-line utility, the associated process model image and icon images are not generated with the model. As a result, any webMethods Monitor APIs that use the process or icon images will not perform as expected with the generated process.
When you run the utility, you must specify a configuration file based on the following XML-based configuration file template:
Software AG_directory \Designer\util\processConfig.xml for Windows, and
Software AG_directory /Designer/util/processConfig.xml for UNIX-based systems.
The processConfig.xml file contains all the information the command-line utility needs to build and upload one or more Designer processes. You can use it as a template to create your own configuration files.
The content of the processConfig.xml file is organized as follows:
Section
Description
<ProcessConfig>
Beginning element of the process configuration file.
<Processes>
Beginning element of the processes section.
<Process>
Defines a single process with elements for the process name, process project name, and process file path.
If you have more than one process to build and upload, you must create consecutive <Process> sections within the <Processes> section, one for each process.
One <Process> section is included in the configuration file by default. Copy and paste if you need more than one.
Important:  
Be sure to remove any unused sections before you run the utility.
< Integration Server >
Defines the Integration Server with elements for name, host, port, user ID, password, and SSL use.
If a process requires more than one Integration Server, you must create consecutive <Integration Server> sections within the <Process> section, one for each server.
Two <Integration Server> sections are included in the configuration file by default. Copy and paste if you need more.
Important:  
Be sure to remove any unused <Integration Server> sections before you run the utility.
<logDir>
Log directory file path.
Generated build reports are placed here. File names are appended with a time stamp in the format yyyyMMddHHmmss (for example, 20090503041804 would be 4:18 AM and 4 seconds on May 3, 2009).
Copyright © 2017 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback