Provides the ability to stop a composite on the SOA server. This operation will handle all revisions for a given composite to ensure that the default revision doesn't change as revisions are stopped.
Environment/Instance Properties
...
Property Name | Property Code | Required | Description |
---|---|---|---|
SOA Composite Name |
| Yes | Name of composite that is being deployed. |
SOA Partition |
| Yes | Name of the partition to hold the composite on the server. |
Inputs
Input Name | Input Code | Required | Description |
---|---|---|---|
Composites File | FDSOA_INP_COMPOSITE_NAME_LIST | No | Comma separated list of composites to start. Optional can prefix a partition on the composite name, (<partition:>composite1, composite2) |
Composite Name List | FDSOA_INP_START_ALL_REVISIONS | No | Provide the option to leave all composites stopped, with the exception of the default revision (default value is False). |
Composite Revision |
| No | Provide the composite revision (see special considerations). |
Outputs
Output Name | Required | Description |
---|---|---|
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
This operation has two independent capabilities:
- stopping multiple composites/revisions
- utilizes "Composites Files" or "Composite Name List" inputs
- utilizes "Composites Files" or "Composite Name List" inputs
...
- if utilizing "Composite Files", 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
- if utilizing "Composite Files", there can be several variations of file name;
- either input provides a list of composite names that must use the following format: <partition:>composite1,composite2 (partition is optional)
- all non-default revisions will be stopped first and then the default revision will be stopped. This will hold the default revision and not allow SOA Suite to move it. If a composite is in two partitions, then specify the partition in the above format to direct the operation to the correct composite.
- stopping a single revision (this is the backwards compatibility capability)
- utilizes "Composite Revision" input to control what revision to stop