Bootstrap files
Bootstrap files are XML files which WebSphere Commerce uses during instance creation to populate database tables with information, after the schema has been created. Once the data has been loaded, you can see the pre-loaded information in the appropriate database table. Bootstrap files can be used to retrieve information about specific data, such as calculation codes and pricing policies.
WebSphere Commerce uses the following bootstrap files:
- ACUserGroups_ locale.xml
- defaultAccessControlPolicies.xml
- defaultAccessControlPolicies_ locale.xml
- ubf_transformed.xml
- wcs.bootstrap.xml
wcs.bootstrap_adv.xml- wcs.bootstrap_adv_ locale.xml
- wcs.bootstrap_pro.xml
- wcs.bootstrap_pro_ locale.xml
- wcs.bootstrap_ locale.xml
- wcs.bootstrap_multi_ locale.xml
- wcs.keys.xml
- wcs.site.xml
- wcs.userreg.xml
These files are located under the WC_installdir/schema/xml directory.
In addition, WebSphere Commerce uses the following staging bootstrap files:
- wcs.staging.xml
- wcs.staging.keys.xml
These files are located under the WC_installdir/schema/db2 or WC_installdir/schema/oracle directories, depending on whether you use DB2 or Oracle as your database.
Existing bootstrap files from previous releases of WebSphere Commerce have been renamed to include "_base". For example, wcs.bootstrap_base.xml.
New bootstrap files have been componentized based on WebSphere Commerce features, and contains data for only the specified WebSphere Commerce feature. The following features use componentized WebSphere Commerce bootstrap files:
- Approvals
- Business tools
- Catalog
- Collaboration
- Contracts
- Coupons
- Development tools
- E-mail activities
- Fulfillment
- Inventory
- Members
- Messaging
- Negotiation
- Orders
- Order management
- Payment
- Personalization
- Portal and pervasive computing (PvC)
- Pricing
- Product Advisor
- Returns
- RFQ
- Rules
- Runtime
- Search
- Staging
- UBF
- UTF
New bootstrap files contain the component name within the file name. For example, wcs.bootstrap_catalog.xml.