Configuring the Data Extract utility environment settings
You must create an environment configuration file that specifies your environment
settings so that the Data Extract utility can extract data objects from your WebSphere Commerce
database.
Procedure
-
Go to the following directory, which contains the sample configuration files for extracting
data:
- WC_installdir/samples/DataExtract
- WC_installdir\samples\DataExtract
- WCDE_installdir\samples\DataExtract
- Create a backup of the wc-dataextract-env.xml environment configuration files in the directory for the object that you want to extract. The sample environment configuration file is configured for a default IBM WebSphere Commerce Developer environment that uses an Apache Derby database. If your environment settings are different, you must change the configured values in these files to match your environment.
- Open the environment configuration file (wc-dataextract-env.xml) for editing and configure the settings for your environment.
-
Change the values of the business context attributes inside the
<_config:BusinessContext>
element to match your store settings:- storeIdentifier
- The identifying name of the store that owns the object data, for example, Aurora.
- langId
- The language ID for the language of the data, for example, -1 for English.
-
Change the values of the database configuration attributes inside the
<_config:Database>
element to match your database settings:<_config:Database type="derby" name="..\..\db\mall" />
<_config:Database type="db2" name="database name" user="user" password="encrypted password" server="server" port="50000" schema="schema name" />
<_config:Database type="Oracle" name="database name" user="user" password="encrypted password" port="1521" schema="schema name" driverType="thin" />
<_config:Database type="os400" name="database name" user="user" password="encrypted password" server="server" remoteDB="true" driverType="toolbox" />
- type
-
- derby
- db2
- oracle
- os400
- name
- The name of the database
- user
- The database user ID.
- If you are using an Oracle database, the user you specify should be identical to the schema. If you specify an invalid schema in the settings, the user is used as the database schema if the user is different and valid. The utility displays a warning, which explains that a change occurred and then the utility continues to run.
- If you use DB2 and you specify an invalid schema, an error message displays. This message indicates that a valid schema is required before the utility runs.
- password
- The database password is necessary to connect to the database. For security purposes, the password is always encrypted. If the password field is empty, you are prompted to enter the password on the command line when you run the utility.
- server
- The name of the server the database is on. The server name can be the IP address or the fully qualified DNS name of the server the database is on.
- port
- The port to connect to the database.
- remoteDB
- Indicates whether the database is remote.
- If your system uses DB2 for IBM i with a remote iSeries database, set the value
for this parameter to be
"true"
.
- If your system uses DB2 for IBM i with a remote iSeries database, set the value
for this parameter to be
- driverType
- Optional: The database driver type.
The default value for the
driverType
isthin
. Another possible option for thedriverType
isoci8
, which is the oracle thick driver.The supported values for the
driverType
are2
and4
.If you are configuring your development environment to use DB2 for IBM i, set the value for this parameter to be
"toolbox"
. - schema
- The name of the database schema.
-
Encrypt the password of the database user:
- Enter the following command:
- ./wcs_encrypt.sh db_password
- wcs_encrypt.bat db_password
- Use the encrypted password next to ASCII encrypted string as the
value for the
password
attribute inside the<_config:Database>
element.
- Enter the following command:
- Save and close the configuration file.