buildSSE
- Karl Henselin
Each server-side extension will be 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.
Build workflow must contain SCM plugin operations to extract source code for specific extension followed by this operation. This operation will find package.json file in extracted source to generate zip file appropriately. Generated zip file is saved as project version artifact in FlexDeploy, which will be used during Deploy workflow execution.
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. |
Artifacts
This operation produces artifacts that will be stored in the artifacts repository.
Endpoint Selection
This operation will select all available endpoints associated to the Target. You can add any endpoint to Target as this operation does not depend on any external libraries or utilities.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.Â
- style