Deploy customized WebSphere Commerce database assets

If you customize or change the WebSphere Commerce database, we must package and deploy the changed assets. Deploying the database assets can involve various schema changes and access control policies. In addition, if you have many changed assets, use the WebSphere Commerce loading utilities to load those changes.

1. Deploying schema changes
   Schema changes involve adding or altering tables in the target WebSphere Commerce database. These actions are typically stored in SQL files. Each database vendor provides a means for running SQL files.

2. Deploying schema and data changes with WCBD
   We can use WCBD to deploy schema and data changes in sql, xml, dataload, acug, acp, and acpnls files.

3. Deploying access control policies
   Access control is crucial to any business, and is especially important if you plan to customize access control policies. Ensure that we are familiar with WebSphere Commerce access control. An access control policy authorizes a group of users to perform a set of actions on a set of resources within WebSphere Commerce. Unless authorized through one or more access control policies, users have no access to any functions of the system.

Related tasks
Packaging custom database assets
Deploying custom database assets