| search-config-ext/ |
Code/search-app/search-config-ext.jar |
- Java module containing custom configuration files.
- All JAR files under the search-app directory will be copied to the
search-ear.ear/lib folder in the Search server Docker image.
|
| search-logic-ext/ |
Code/search-app/search-logic-ext.jar |
- Java module containing custom configuration files.
- All JAR files under the search-app directory will be copied to the
search-ear.ear/lib folder in the Search server Docker image.
|
|
Certs/search-app |
- This folder does not exist in the default HCL Commerce Build search package. The build and
deployment process is designed to support the use of the folder as an interface for your extensions.
- If you want to import your own certificates, you must implement HCL Commerce Build logic
to create this folder and to include your certificate JSON file into this folder within a custom
package. For more information, see Managing certificates manually.
|
|
DeployScripts/search-app |
- Similar to the Certs folder, the DeployScripts folder
does not exist in the default HCL Commerce Build search package. The build and deployment
process is designed to support the use of the folder as a potential extension point for you to
customize the deployment process.
- If you want to extend the default deployment process with your own custom code logic, you need
to implement HCL Commerce Build logic to create the folder and to place your custom shell
scripts within the folder. Your custom shell scripts within the folder must be named as
applyDeployScripts.sh
- The default logic to apply changes detects whether there are any
applyDeployScripts.sh scripts within the folder. If found, the scripts are run
to process any of your custom deployment logic. The default logic to apply changes is defined within
the /SETUP/bin/applyCustomization.sh file for reference.
|