Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
OIC Account |
| No | The OIC account with all the required properties like Base URI, Username and Password for connecting to an OIC Instance |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
OIC Account |
| No | The OIC account with all the required properties like Base URI, Username and Password for connecting to an OIC Instance. Typically, this will not be used because the value will come from the property |
Trading Partner List |
| No | CSV list of Trading Partner ids to include. Leave blank to include all non-project Trading Partners (and, depending on Project List, project Trading Partners as described below). Use |
Project List |
| No | CSV list of project ids whose Trading Partners should be included. Leave blank to include Trading Partners from all projects when that path is used. |
OIC Trading Partner Config Plan File |
| No | Optional input to specify a different Config Plan file name. If not specified, it defaults to |
If either is given, Config Plan entries for those listed are created.
If both are given, Config Plan entries for the listed of both lists are created (listed Trading Partners plus all Trading Partners in the listed projects).
Artifacts
This operation doesn’t consume or produce any artifacts.Endpoint Selection
This operation will select all available endpoints associated to the Target.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 plan is separate from the Trading Partner Identifier Plan (
TradingPartnerIdentifiersPlan.properties), which covers partner identifiers and control numbers. - Only fields that should change per environment should remain in the file. Delete lines you do not want to update.
- Transport Host identifiers (AS2 / AS4 / RosettaNet) and outbound agreement Hosts use UI format Type | Value (example: AS2 Identifier | FLEXAGONOIC_AS2). The Type and Value must exist on the target Host Profile at apply time.
- Config Plan apply runs after Trading Partner import. Transport updates that change a REST Send URI require the transport integrations to allow that update in OIC (integrations must not remain activated in a state that blocks URI update). Prefer a full undeploy/import/apply/deploy path.
- Hand-edited keys outside the generate allow-list for that transport/agreement type are ignored. Allowed plan keys that are missing on the OIC object cause apply to fail with a clear error.