Ensure that you complete the following tasks before proceeding to populate the Elastic Path Commerce database:
- Ensure that you have created the Elastic Path Commerce database server. For more information see the Create Database Server documentation.
- Ensure that you have created the Apache ActiveMQ service. For more information see the Deploy ActiveMQ documentation.
How to Populate an Elastic Path Commerce Database
Running the CloudOps for Kubernetes Jenkins job
run-data-pop-tool will run the Elastic Path Data Population tool in a Docker container. Use this Jenkins job to perform one of the following tasks:
- Create and populate a new Elastic Path Commerce database
- Apply new changesets to an existing Elastic Path Commerce database
- Reset or re-create, an Elastic Path Commerce database
Parameters for the
run-data-pop-tool Jenkins Job
This job takes the following parameters:
The URL to your hosted copy of the
cloudops-for-kubernetes Git repository.
The branch of the
cloudops-for-kubernetes Git repository that you wish to use.
The Kubernetes namespace where the database server and related Kubernetes objects were created. Use the same value specified for
kubernetesNickname in the job you ran to create the database service. It was either the
The Jenkins job runs the
data-pop-tool docker container inside the same namespace.
The data-pop-tool command to run against the database. The two valid options are
update-db. For more information about the two options, see the Elastic Path Commerce Data Population Tool documentation.
The tag of the
data-pop-tool Docker image to use. The Docker image contains the data files that define the data to populate in the Elastic Path Commerce database. Selecting and specifying the correct image tag ensures that the correct data is populated in the Elastic Path Commerce database.
The name of the environment directory specifying the desired Elastic Path data to be populated in the database.
It is important to specify the correct value for this parameter, as it controls what data get loaded to the Elastic Path Commerce database. Often the Elastic Path Commerce development team can clarify the correct value for this parameter.
The value provided must be one of the environment directories in the deployment package from which the data-pop-tool Docker image was built. For more information about environment directories, see the Elastic Path Commerce Environment Directories.
The name of the Kubernetes cluster where the mysql database is located.
The Jenkins job checks to see if Kubernetes secrets exist for an Elastic Path schema and Elastic Path database user and password. If any of the values are missing, it generates new random values and stores them as secrets.