Conventions
Variables
- businessmodel
- The name of the business model with which you are working (for example, consumer direct or B2B direct, extended sites, supply chain, or demand chain).
- cell_name
- The name of the WebSphere Application Server cell. Cells are arbitrary, logical groupings of one or more nodes in a WebSphere Application Server distributed network that are managed together by a WebSphere Network Deployment Manager. In this definition, a node is a single occurrence of WebSphere Application Server and the applications that run inside the occurrence of WebSphere Application Server.
- db_password
- The password for the database user.
- dba_password
- The password for the database administrator. Use dba_password if table and database locks require administrator privileges (for example if WebSphere Commerce is configured as an authoring server, or WebSphere Commerce Developer is configured to use an authoring server database).
- db_schema
- The database user ID (schema owner). This value should be the same value for db for development_db.
- db_user
- The database user.
- development_db
- The name of the WebSphere Commerce development database.
- drive
- The letter representing the drive on which you installed the product or component being discussed (for example, C:).
- host_name
- The fully qualified host name of the WebSphere Commerce Server (for example, wcserver.mydomain.ibm.com is fully qualified).
- instance
- The name of the WCS instance with which you are working (for example, demo).
- locale
- A language and country specific code. By default, WebSphere Commerce supports the following locales:
- en_US
- United States English
- fr_FR
- French
- de_DE
- German
- it_IT
- Italian
- es_ES
- Spanish
- pt_BR
- Brazilian Portuguese
- zh_CN
- Simplified Chinese
- zh_TW
- Traditional Chinese
- ko_KR
- Korean
- ja_JP
- Japanese
- pl_PL
- Polish
- ro_RO
- Romanian
- ru_RU
- Russian
- Management_Center_component
- The name of the Management Center tool or area with which to work. The values are catalog, marketing, promotion, foundation, and shell.
- node_name
- The short (unqualified) host name of the WebSphere Commerce node (for example, wcserver). A WebSphere Commerce node is a node in the topology that contains the WebSphere Commerce Server.
- profile_name
- The name of the WebSphere Application Server profile that is created for the WCS instance.
- storedir
- The name of the directory in which store-specific assets are located, as defined in the DIRECTORY column of the STORE table.
- storeId
- The store entity ID as defined in the STORE_ID column of the STORE table.
- target_db
- The name of the database used by the target WebSphere Commerce Server.
- WAS_instance
- The name of the WebSphere Application Server with which the WCS instance is associated.
- WC_enterprise_application
- WC_instance. For example, given the instance demo, the value of WC_enterprise_application is WC_demo.
- WC_EAR
- WC_instance.ear. For example, given the instance demo, the value of WC_EAR is WC_demo.ear.
Path variables
- Ant_installdir
- The installation directory for Apache Ant.
- DB2_installdir
- Installation path for DB2 Universal Database. These are the default installation paths:
- /usr/opt/db2_09_05
- /opt/IBM/db2/V9.5
- /opt/IBM/db2/V9.5
- C:\Program Files\IBM\SQLLIB
- IHS_HOME
- Installation directory for IBM HTTP Server. These are the defaults for IBM HTTP Server, version 7.0:
- /usr/IBMIHS/
- /opt/IBMIHS
- /opt/IBMIHS
- C:\Program Files\IBM HTTP Server
- LC_profiledir
- Path for the WebSphere Application Server profile for Lotus Connections. A profile is the set of files that define the runtime environment. These are the default profile paths:
- WAS_HOME/profiles/profile_name
The Profiles and Blogs applications can be deployed to different WebSphere Application Servers as part of a Lotus Connections installation. Because of this possibility, LC_profiledir may also have different values for Profiles and Blogs.
- MVCPortlet_installdir
- Installation directory for the WebSphere Commerce portlets:
- WCDE_INSTALL/portal/MVCPortlet/MVCPortlet.war
- WC_INSTALL/portal/MVCPortlet/MVCPortlet.war
- Oracle_installdir
- Installation path for the Oracle database.
- RAD_installdir
- Installation directory for Rational Application Developer. These are the default installation directories:
- /opt/IBM/Rational/SDP/7.0
- C:\Program Files\IBM\Rational\SDP\7.0
- refapphome
- Installation path for reference application. The default installation path is...
WC_INSTALL/refapps/ref-app-name...where ref-app-name is the name of the reference application.
- SC_installdir
- Installation path for Sales Center. The default installation path for Sales Center is:
C:\Program Files\IBM\WebSphere\SalesCenter70
- StaticHTMLAssets_tempDir
- Temporary directory where you extracted the Static HTML Assets package.
- TestAssets_tempDir
- Temporary directory where you extracted the Test Assets package.
- UPDI_tempdir
- Temporary directory where you have saved the WebSphere Commerce Update Installer download package.
- UPDI_installdir
- Installation directory of the WebSphere Commerce Update Installer. This installer is used to install fix packs and APARs.
- WAS_HOME
- Installation path for WebSphere Application Server. These are the default installation paths:
- /usr/IBM/WebSphere/AppServer
- /opt/IBM/WebSphere/AppServer
- /opt/IBM/WebSphere/AppServer
- C:\Program Files\IBM\WebSphere\AppServer
- WAS_userdir
- Path for all the data used by WebSphere Application Server that can be modified or must be configured by the user. The default path is...
/QIBM/UserData/WebSphere/AppServer/V7/edition...where edition is either ND or BASE.
- WCBD_INSTALL
- The installation directory for the WebSphere Commerce Build and Deployment tool. These are the default installation paths:
- WC_INSTALL\wcbd
- WCDE_INSTALL\wcbd
- WCBD_DEPLOY
- The common directory to store the server deployment package installations.
- WCBD_DEPLOY_SERVER
- The installation directory for the server deployment package created by the build process.
- WCBD_deploy_toolkit_common_dir
- The common directory to store the toolkit deployment package installations.
- WCBD_deploy_toolkit_dir
- The installation directory for the toolkit deployment package created by the build process.
- WC_EAR
- Path for the WebSphere Commerce Enterprise Archive.
These are the default paths:
- WC_PROFILE/installedApps/ cell_name/WC_instance.ear/
- WC_PROFILE/installedApps/cell_name/WC_instance.ear/
- workspace_dir/WC
XML files in WC_EAR/xml should not be updated directly. See XML configuration directory for more information about working with the files in this directory.
- WC_INSTALL
- Installation path for WebSphere Commerce. These are the default installation paths for WebSphere Commerce:
- /usr/IBM/WebSphere/CommerceServer70
- /opt/IBM/WebSphere/CommerceServer70
- /opt/IBM/WebSphere/CommerceServer70
- C:\Program Files\IBM\WebSphere\CommerceServer70
- WC_PROFILE
- Path for the WebSphere Application Server profile for WebSphere Commerce. A profile is the set of files that define the runtime environment. These are the default profile paths:
- WAS_HOME/profiles/profile_name
- WCDE_INSTALL
- Installation directory for the WebSphere Commerce development environment. The default installation directory depends on the edition of WebSphere Commerce Developer:
- C:\WCToolkitExpress70
- C:\WCToolkitPro70
- C:\WCToolkitEE70
- WC_USER
- Directory for all the data used by WebSphere Commerce that can be modified or must be configured by the user. The default path is...
/QIBM/UserData/CommerceServer70
- WP_installdir
- Installation directory for WebSphere Portal:
- /usr/IBM/WebSphere/PortalServer
- /opt/IBM/WebSphere/PortalServer
- /opt/IBM/WebSphere/PortalServer
- C:\Program Files\IBM\WebSphere\PortalServer
- workspace_dir
- WebSphere Commerce workspace directory. The default is...
WCDE_INSTALL\workspace