Provides the ability to start a composite(s) 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 started. The default revision is always started , and other revisions can be controlled by an "Start All Revisions" input.
...
Input Name | Input Code | Required | Description |
---|---|---|---|
Composites File | FDSOA_INP_COMPOSITES_FILE | No | Complete pathPath, including file name, to file that contains the composites to start. See Special Considerations section below for additional details. |
Composite Name List | FDSOA_INP_COMPOSITE_NAME_LIST | No | Comma separated list of composites to start. Optional Optionally, can prefix a partition on the composite name if there are more than one composite with the same name, (<partition:>composite1, composite2) |
Start All Revisions | FDSOA_INP_START_ALL_REVISIONS | No | Provide Provides the option to leave all composites stopped, with the exception of the default revision (default value is False). |
Composite Revision |
| No | Provide specific revision to start (this is for backwards compatibility) |
Make Default Revision |
| No | Make the newly started composite the default (this is for backward compatibility) |
Outputs
Output Name | Required | Description |
---|---|---|
Artifacts
This operation doesn't consume or produce any artifacts.
...
- starting multiple composites/revisions
- utilizes "Composites Files" or "Composite Name List" and "Start All Revisions" 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 (Composite Files or Composite Name List) provides a list of composite names to start that must use the following format: <partition:>composite1,composite2 (partition is optional)
- the default revision is started first and then all non-default revisions will be started, if the "Start All Revisions" input is checked. This will hold maintain the default revision and not allow SOA Suite to move itthe default revision to another revision. If a composite is in two partitions, then specify the partition in the above format to direct the operation to the correct composite.
- utilizes "Composites Files" or "Composite Name List" and "Start All Revisions" inputs
- starting a single revision (this is the backwards compatibility capability)
- utilizes "Composite Revision" and "Make Default Revision" inputs to control what revision to start and whether it should be the default revision