WebSphere Commerce utilities
- acpextract
Extract the access control policy and access group information in the database to XML files. Use input filter XML files to specify the data to extract.
- acpload
Load XML files containing access control policies into the appropriate databases.
- acpnlsload
Load XML files containing the display names and descriptions, into the appropriate databases.
- acugload
Load XML files containing the user (access) group definitions into the appropriate databases.
- biEventFileGen
Alternative means to obtain the transformed Common Business Event XML file. Suitable for external systems if you choose to disable automatic transmission.
- buildstats
Update database statistics when you use LikeMinds.
- config_server
Start the Configuration Manager server. The Configuration Manager server must be started before starting the Configuration Manager client.
- dataload
Load data from a source file into a target database. Loading the file populates and updates the WebSphere Commerce database. You can also use the data load to delete data from a database.
- dataload
Run the data load inside the development environment when testing customizations or when debugging issues with the utility. This is less time-consuming than first deploying to a runtime environment, then running the utility for test purposes.
- Dbclean utility script
The Database Cleanup (dbclean) removes objects from the database.
- dtdgen
Create DTD and XSD files for use with the loading utilities based on the target database to which the data must conform. The DTD specifies structural elements and markup definitions that can be used within the XML data document and the DTD describes the tables and columns into which the massload utility imports data. For example, a DTD can list elements to be used in a document and specify the attributes that each element can take.
- Export Marketing Statistics
Export marketing statistics to an XML file.
- fileloader
Load managed files into a WebSphere Commerce database. Once the files are loaded into the database, the ScheduledContentManagedFileEARUpdate scheduled job copies the files from the database to the WebSphere Commerce EAR file.
- fileprop
Send new and changed files to the administration node of the federated WAS environment, which later pushes them into the managed nodes, which includes the production server. The staging server needs to be federated using the same deployment manager as the production server. Otherwise, the managed files will not be propagated into the production EAR because the deployment manager is not aware of the production node.
- idresgen
Generate identifiers for XML elements with their associated identifiers. The XML files must have identifiers because the XML files map directly to the target database schema.
- idresgen
Generate identifiers for XML elements with their associated identifiers. The XML files must have identifiers because the XML files map directly to the target database schema.
- Import Marketing Statistics
Import marketing statistics from a source XML file.
- massextract
The massextract utility uses a query against a database to extract selected subsets of data from the database into an XML document. The data to be extracted from the database is specified using an extraction-filter XML document. The function of the massextract utility is opposite that of the massload utility. Use the massextract utility to extract selective subsets of data from the WebSphere Commerce database in the form of XML files. You can extract data on products related to an upcoming holiday, for example, or you can extract information from a consolidated database for use with other systems.
- massload
Load an XML input file into a target database. Loading the XML file updates the WebSphere Commerce database. The massload utility allows column-level updates to a table. It also allows you to delete data from a database.Load an XML input file into a target database. Loading the XML file for populate and updates the WebSphere Commerce database. The massload utility allows column-level updates to a table. It also allows you to delete data from a database.
- MigrateEncryptedInfo
Change the merchant key and re-encrypt all encrypted data in the database. There are two ways to specify the values of the merchant key to this tool. The first way is to provide the old and new merchant keys through command line arguments. The second way is to retrieve the keys from calling out to the Key Locator Framework using the "-k" parameter.
- migratepaymentsdb
The Payments database tier migration script (migratepaymentsdb) collects database information to determine the version, release level, and database type. The script then runs the appropriate pre-migration steps. It updates the Payments Schema to the WebSphere Commerce Payments, v7.0 level. Based on the version and release, the script runs the Payments data migration command for the Payments Framework and IBM cassettes, and any installed third-party cassettes. The required tables for third-party cassette are copied to the migrated database, however, the cassette might not be fully functional until it is redeployed or reinstalled.
- publishstore
The publishstore script allows you to publish store archives from a command line.
- resetdb
The initial installation of WebSphere Commerce Developer contains pre-published starter stores using Apache Derby as the development database type. You can reset the database and workspace so that they do not contain any starter store resources. If you have enabled features, running the resetdb and resetstores scripts returns the Apache Derby database to the most recently applied fix pack level.
- resetstores
The Reset Stores (resetstores) utility resets the Stores Web module in the workspace to its bootstrap configuration; that is, it deletes all the published (and prepublished) store assets from the workspace.
- restoredefaults
Restoring the development environment to its default setup is accomplished by using a convenience command called restoreDefault.bat.
- setdbtype
After you install WebSphere Commerce Developer, the development environment is configured to use the Apache Derby database.To change the database type to DB2, Oracle, or back to Apache Derby, run the setdbtype command. Verify the database you are switching to, exists in the network. Changing development database types does not carry over any schema customizations or custom data to the new database.
- stagingcopy
Copy data from the production database to the production-ready data on a staging or authoring server. You cannot use this command if RFQs are on the production system.
- stagingprop
Copy data and managed files from the production-ready data to the production server. You cannot create or update RFQ objects on the staging server. The stagingprop utility uses the STAGLOG table to identify changed records in the production-ready data and update the corresponding tables in the production database.
- startWCToolkit
Start WebSphere Commerce Developer
- txttransform
Transform data between a character-delimited variable format and an XML format.
- updatedb
Post install steps
- wcim_ant
If migrating the WebSphere Commerce database using the command line, review this information to understand the parameters required for the migratedb command.
- wcs_encrypt
Encrypt sensitive information with a given merchant key. The value of the merchant key could be specified through command line arguments or retrieved from calling out to the Key Locator Framework using the "-k" parameter. If none of these parameters are specified, it will encrypt the sensitive data with the default merchant key.
- wcs_password
Encrypt user passwords to be stored in the WebSphere Commerce database.
- wcs_pmpasspwd
Generate encrypted passwords for WebSphere Commerce Payments.
- xmltransform
Change, aggregate, and remap the data in an XML document to alternative XML formats for use by other users or systems as needed.