Provides the ability to activate a composite(s) on the SOA server. This operation will handle all revisions for a given composite (the default revision will not be maintained). The default revision is always started, and other revisions can be controlled by an "Activate All Revisions" input.
Note that a composite is able to both receive and process requests if its mode is active and its state is on. This operation and the soaRetire operation function separately from soaStart and soaStop. For example, if a composite is both retired and on, it would have to be activated before it could receive new requests. Similarly, if it was retired and off, it the composite would have to be activated and turned on before it could to receive and process new requests.
Target Properties
...
Input Name | Input Code | Required | Description |
|---|---|---|---|
Composites File |
| No | File name (anywhere in temp directory) or absolute path to file with comma separated composite names. See Special Considerations section below for additional details. |
Composite Name List |
| No | Comma separated composite names, overrides Composite File Name input. Optionally, can prefix a partition on the composite name if there are more than one composite with the same name, (<partition:>composite1, composite2). See Special Considerations section below for additional details. |
Activate All Revisions |
| No | Check to activate all composite revisions. If false, then only default revision will be activated (default value is false). |
Composite Revision |
| No | Provide specific revision to activate. If set, then Activate All Revisions input will be ignored. See Special Considerations section below for additional details. |
Make Default Revision |
| No | If Composite Revision input is provided, that specific revision will be set as default. |
Continue on Not Found |
| No | If checked, error will not be thrown if composite is not found. Defaults to false. |
Artifacts
This operation doesn’t consume or produce any artifacts.
...
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
Special Considerations
The composite names that are used will be determined by first looking at the Composite Names input, then the Composite File Name input and lastly the SOA Composite project property (the first two inputs can provide multiple composite names). The Revision input should generally not be utilized with the Composite Names or Composite File Name inputs. The single revision input will be checked against each composite from the composite list and the specific revision may not be available on all composites, which will cause the operation to fail.
activating a single revision (this is the backwards compatibility capability)
utilizes "Composite Revision" and "Make Default Revision" inputs to control what revision to activate and whether it should be the default revision
activating multiple composites/revisions
utilizes "Composites File" or "Composite Name List" and "Activate All Revisions" inputs
if utilizing "Composite File", there can be several variations of file name.
just a file name, will look in the temp directory for the given file name
relative path, will only look for the relative path within the temp directory for the given file name
absolute path, will only look at the absolute path for the given file
either input (Composite File or Composite Name List) provides a list of composite names to activate that must use the following format: <partition:>composite1,composite2 (partition is optional)
the default revision is activated first and then all non-default revisions will be activate, if the "Activate All Revisions" input is checked. This operation will not maintain the default revision, Enterprise Manager executes in the same manner. If a composite is in two partitions, then specify the partition in the above format to direct the operation to the correct composite.