Configuring the environment variable setting scripts
Before you can use the mass loading utilities, you might have to update some of the environment variables that are used by the utilities. The environment variables are set by the following scripts that are called by the mass loading utilities and other WebSphere Commerce utilities:
The massload utility
is deprecated for WebSphere Commerce Version 7 Feature Pack 6. The
Data Load utility is the recommended command-line loading utility.
If you are currently using the mass load utility, you are recommended
to switch to the Data Load utility to load your CSV and XML input
files into your target database. If your system contains scheduled
and automated processes that use massload, it is recommended that
you update these processes to use the Data Load utility. Other WebSphere
Commerce utilities that use the massload utility, such as the acpload
utility, continue to use the massload utility in WebSphere Commerce
Version 7 Feature Pack 6. If you have business reasons to continue
using the massload utility, you can continue to use this utility.
For more information about the Data Load utility, see Overview of the Data Load utility.
You can switch to the Data Load utility by using the TableObjectMediator
to
load your data when no business object mediator exists for the data
that you are loading. For more about the TableObjectMediator
formation,
see Data Load utility table-based mediator and builder.
About this task
- setenv script
-
- WC_installdir/bin/setenv.sh
- WC_installdir\bin\setenv.bat
- WCDE_installdir\bin\setenv.bat
- setenv.db2 script
-
- WC_installdir/bin/setdbenv.db2.sh
- WC_installdir\bin\setdbenv.db2.bat
- setenv.oracle script
-
- WC_installdir/bin/setdbenv.oracle.sh
- WC_installdir\bin\setdbenv.oracle.bat
To change the environment variable setting scripts: