Sample configuration
The tool can build applications for all four server types: the Transaction server, Store server, Search server, and Customization server. An example shows how you can build your own extensions using the .
These examples are for reference only, intended as a starting point to help you to set up your own build environment.
Building for the Transaction server (ts
)
To configure the build properties for a Transaction server package, build-buildtype-ts.properties, consider the following relevant configurations that you need to complete. The values in the following name-value pairs are the folders in your workspace. These properties determine which assets to package.
ejb.module.list=WebSphereCommerceServerExtensionsData
java.module.list=WebSphereCommerceServerExtensionsLogic
web.module.list=CommerceAccelerator
ear.dir.includes=lib/**,properties/**,xml/**
Build process takes these folders from the workspace | Packages to these folders in the output ZIP file | Description |
---|---|---|
WC | Code/ts-app/ | EAR project |
WC/lib | Code/ts-app/lib/ |
|
WC/properties | Code/ts-app/properties/ |
|
WC/xml | Code/ts-app/xml/ |
|
WebSphereCommerceServerExtensionsData | Code/ts-app/ejb/WebSphereCommerceServerExtensionsData.jar |
|
WebSphereCommerceServerExtensionsLogic | Code/ts-app/WebSphereCommerceServerExtensionsLogic.jar |
|
CommerceAccelerator | Code/ts-app/CommerceAccelerator.war |
|
You need to define logic to determine where to pull the certificates. | Certs/ts-app |
|
You need to define logic to determine where this folder exists in your workspace. | DeployScripts/ts-app |
|
DeployScripts/ts-app/custConfiguration.sh |
|
|
DeployScripts/ts-app/applyDeployScripts.sh |
|
|
DeployScripts/ts-app/*** |
|
Building for the Search server (search
)
To configure the build properties for a Search server package, build-buildtype-search.properties, consider the following relevant configurations that you need to complete. The values in the following name-value pairs are the folders in your workspace.
java.module.list=search-config-ext, search-logic-ext
Build process takes these folders from the workspace | Packages to these folders in the output ZIP file | Description |
---|---|---|
search-config-ext/ | Code/search-app/search-config-ext.jar |
|
search-logic-ext/ | Code/search-app/search-logic-ext.jar |
|
You need to define logic to determine where to pull the certificates. | Certs/search-app |
|
You need to define logic to determine where this folder exists in your workspace. | DeployScripts/search-app |
|
DeployScripts/search-app/custConfiguration.sh |
|
|
DeployScripts/search-app/applyDeployScripts.sh |
|
|
DeployScripts/search-app/*** |
|
Remote stores (crs
)
To configure the build properties for a Store server package, build-buildtype-crs.properties, consider the following relevant configurations that you need to complete. The values in the following name-value pairs are the folders in your workspace.
web.module.list=crs-web
java.module.list=crs-extensions-logic
This project is used to customize java code for the crs-web store.
Build process takes these folders from the workspace | Packages to these folders in the output ZIP file | Description |
---|---|---|
crs-web/ | Code/crs-app/crs-web.war:/ |
|
crs-web/src/ | Code/crs-app/crs-web.war:/WEB-INF/classes/ |
|
crs-web/WebContent/ | Code/crs-app/crs-web.war:/ | Web content files for the web module. |
crs-web/WebContent/META-INF/ | Code/crs-app/crs-web.war:/META-INF/ | Meta info files. |
crs-web/WebContent/WEB-INF/ | Code/crs-app/crs-web.war:/WEB-INF/ | Web Info files. |
crs-extensions-logic | Code/crs-app/lib/crs-extensions-logic.jar | Create a java utility project in the Store server to hold java customization code (Such as a JSTL tag library, ServletFilter, Listener or Spring MVC). The project can also hold custom resources in a manner similar to the Transaction server and Search server. |
You need to define logic to determine where to pull the certificates. | Certs/crs-app |
|
You need to define logic to determine where this folder exists in your workspace. | DeployScripts/crs-app |
|
DeployScripts/crs-app/custConfiguration.sh |
|
|
DeployScripts/crs-app/applyDeployScripts.sh |
|
|
DeployScripts/crs-app/*** |
|
Commerce UE (xc
)
To configure the build properties for a Customization server package, build-buildtype-xc.properties, consider the following relevant configurations that you need to complete. The values in the following name-value pairs are the folders in your workspace.
- web.module.list=commerceue-app
- web.src.dir=src/main/java
- web.resource.dir=src/main/resources
Build process takes these folders from the workspace | Packages to these folders in the output ZIP file | Description |
---|---|---|
commerceue-ear/src/main/application/ | Code/xc-app/ |
|
commerceue-ear/src/main/application/lib | Code/xc-app/lib | Java libraries for the EAR |
commerceue-ear/src/main/application/META-INF/ | Code/xc-app/META-INF/ | Meta info for the EAR |
commerceue-app/src/main/java/ | Code/xc-app/commerceue-app.war:/WEB-INF/classes |
|
commerceue-app/src/main/resources/ | Code/xc-app/commerceue-app.war:/WEB-INF/classes | Java resource file directory, especially property files |
commerceue-app/WebContent/ | Code/xc-app/commerceue-app.war:/ | Web content |
commerceue-app/WebContent/WEB-INF/ | Code/xc-app/commerceue-app.war:/WEB-INF/ | WEB-INF directory |
commerceue-app/WebContent/swagger/ | Code/xc-app/commerceue-app.war:/swagger/ | Swagger web app files |
commerceue-app/WebContent/META-INF | Code/xc-app/commerceue-app.war:/META-INF/ | Web meta information directory |
You need to define logic to determine where to pull the certificates. | Certs/xc-app |
|
You need to define logic to determine where this folder exists in your workspace. | DeployScripts/xc-app |
|
DeployScripts/xc-app/custConfiguration.sh |
|
|
DeployScripts/xc-app/applyDeployScripts.sh |
|
|
DeployScripts/xc-app/*** |
|
Building data
For data, you do not need to specify the assets to be built. You only need to put your data files into related directories (sql, xml, dataload, acug, acp, acpnls). For the details of file structures, see HCL Commerce Build tool repository structure.