Loading the Commerce+ database schema

You need to use a script to load the Commerce+ database schema.

Before you begin

Prepare an Oracle database for use with HCL Commerce.

About this task

This script completes the following tasks:
  • Creates the schema including tables, views, and stored procedures in the database.
  • Loads bootstrap data.
  • Creates two default users in the database.
    wcsadmin
    The site administrator.
    spiuser
    The internal user with the role "RemoteConfigurationReaders". This user is used for inter-component server API invocation only. The spiuser user is configured in the Store server, Search server and Customization (xC) server, and is used in the API invocation from those servers to the Transaction server. This user cannot be disabled. In the event that this user is disabled, the necessary component servers cannot connect to the Transaction server.

Procedure

Run the following command to create the Commerce+ database schema. 
./initdb_oracle_sample.sh staging|production dbName dbServer dbPort dbaUser dbaPassword dbUser dbPassword merchantKey wcsadminSalt wcsadminPassword spiuserSalt spiuserPassword sampleData|noSample [sslKeyFile sslKeyPassword]
The following example displays the command to create a staging database and include sample data for the sample Aurora store: 
./initdb_oracle_sample.sh staging orclpdb1 mydb.hcl.com 1521 system myunguessablepassword 
wcs wcs1 1a1a1a1a1a1a1a1a2b2b2b2b2b2b2b2b 3h8x876vd8g3 wcs1admin 7j2lhm2vjpoc QxV7uCk6RRiwvPVaa4wdD78jaHi2za8ssjneNMdu3vgqi 
sampleData /opt/java/openjdk/lib/security/cacerts changeit
type
The type of environment. Valid values are staging or production.
staging
Specify this value if you want to enable workspaces. The default workspace number is five. The script creates five Read and Write schemas in the database.
production
Specify this value if you do not want to enable workspaces and load a schema for production.
dbName
The name of the database that you created.
dbServer
The database server hostname.
dbPort
The database server port.
dbaUser
The database administrator username.
dbaPassword
The database administrator password.
dbUser
The database username. Ensure that you are not using the same username as the database administrator.
dbPassword
The database user password.
merchantKey
A plain text unencrypted merchant key.
  • A 32 hexadecimal character must be used. Characters can be one of 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, d, e, or f.
  • Must contain a minimum of one alphabetic character.
  • Must contain a minimum of one numeric character.
  • Must be in lowercase.
  • Cannot contain more than 4 identical consecutive characters.

    For example, 1a1a1a1a1a1a1a1a2b2b2b2b2b2b2b2b.

Important: You must specify your own merchant key and key encryption key values for the security of your Commerce+ installation. Do not use the default values contained within the provided sample configuration files and documentation examples.
wcsadminSalt
Specify a random string to use to encrypt the wcsadminPassword.
wcsadminPassword
This script creates a Site Administrator user named wcsadmin. Specify a password for wcsadmin. Use the username wcsadmin and this password to log in to the .
spiuserSalt
Specify a random string to use to encrypt the spiuserPassword.
spiuserPassword
This script creates an SPI user named spiuser. Contact your administrator who prepared the Docker images in your registry. Use the same plain text spiuserPassword that your administrator used when preparing the Docker images. For more information, see Configuring the spiuser password for Commerce+ Kubernetes Deployment.
This user is used for inter-component server API invocation only. The spiuser is configured in the Store server, Search server and Customization server, and is used in the API invocation from those servers to the Transaction server. This user cannot be disabled, otherwise the component servers cannot connect to the Transaction server.
withSample
Determine whether you want to load sample data for the sample store. Valid values are sampleData or noSample.
sampleData
Load sample data for the sample store. Specify this value if you want to view the sample store for learning purposes or to use the store as a validation point. At the end of the set up procedure, if you can view a functional store, then the environment installed correctly. If you specify sampleData, sample catalog data and images are loaded into your database.
noSample
Do not load any sample data. Specify this value when you will create your own store.
sslKeyFile
(Optional) If SSL support is configured on the database server, specify the path to the SSL key file. You might want to contact your database administrator to find out whether SSL support is configured.

Results

The Commerce+ schema is loaded into your database.