Provides the ability to retire a composite on the SOA server. This operation will handle all revisions for a given composite (the default revision will not be maintained). Operation only available on plugin version 5.1.0.2.x and greater.
Environment/Instance Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
SOA Server Host |
| Yes | Host name of the SOA managed server. |
SOA Server Port |
| Yes | Port number of the SOA managed server. |
Weblogic Admin User |
| Yes | Admin user name for WebLogic server. |
Weblogic Admin Password |
| Yes |
|
Oracle SOA Home |
| Yes | Oracle SOA Home, indicates where SOA Suite is installed. |
Project 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 | 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 | FDSOA_INP_START_ALL_REVISIONS | No | Comma separated composite names, overrides Composite File Name input (default value is false). See Special Considerations section below for additional details. |
Composite Revision |
| No | Provide specific revision to stop, otherwise all revisions will be retired. See Special Considerations section below for additional details. |
Outputs
Output Name | Description |
---|---|
Artifacts
This operation doesn’t consume or produce any artifacts.
Endpoint Selection
This operation will select all available endpoints associated to the environment/instance.
Endpoint Execution
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 and shouldn't be utilized together. If Composite Revision input is set, the Composite Files and Composite Name List inputs will be ignored :
- retiring a single revision (this is the backwards compatibility capability)
- utilizes "Composite Revision" input to control what revision to stop
- retiring multiple composites/revisions
- utilizes "Composites File" or "Composite Name List" 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
- if utilizing "Composite File", there can be several variations of file name;
- either input (Composite File or Composite Name List) provides a list of composite names to retire that must use the following format: <partition:>composite1,composite2 (partition is optional)
- all non-default revisions will be retired first and then the default revision will be retired. 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.
- utilizes "Composites File" or "Composite Name List" inputs