Each server-side extension will be it's its own project in FlexDeploy. We recommend that source code for each extension is stored in Source Control Systems like Git, Subversion in unique folder.
...
Your source code for extension may look like this. Parent folder structure does not matter as that is configurable in FlexDeploy project.
...
...
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
OCC Account |
| Yes | The Oracle CX |
Commerce account with all the required properties like URL, App Key etc. Account will be different for every OCC environment. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Server-Side Extension Name |
| Yes | The name of server-side extension for Oracle CX Commerce. Defaults to FlexDeploy project name. It is preferable to store extension source in a folder with name of the extension and use same for FlexDeploy project name. |
Inputs
Outputs
...
Artifacts
This operation produces artifacts that will be stored in the artifacts repository.
...
This operation will select all available endpoints associated to the environment/instanceTarget. You can add any endpoint to environment/instance Target as this operation does not depend on any external libraries or utilities.
...