Home
Reference
Ant targets
A WebSphere Commerce instance can be created from the command line. The command-line utility uses Apache Ant to create the objects required. The targets are divided into several high-level groups that correspond to the environment that is to be configured.
Ant targets: Removing configuration targets
You can remove the WebSphere Commerce instance and the WebSphere Commerce Server using Ant targets.
RemoveCommerceServer
The RemoveCommerceServer target removes the WebSphere Application Server configurations from the WebSphere Commerce instance. The Ant target removes the data source, JDBC provider, virtual hosts, and uninstalls the enterprise application. Finally, the web server plug-in configuration file is regenerated.
RemoveJaasAuthData
RemoveJaasAuthData removes the JAAS authentication data used to store the database user ID and password. This JAAS authentication data object is used by the WebSphere Commerce data source.

Reference
- WebSphere Commerce API reference
  WebSphere Commerce exposes two main programming APIs. The first and newest API is a REST interface, and most new classes are exposed here. The legacy Java API also contains new classes not suitable for REST, and can be browsed in Javadoc format.
- Cross-reference of data beans, EJB beans, and tables
  Data beans are grouped into several component groups.
- Cross-reference of commands, tasks, and tables
  URL commands, controller commands, task commands, view commands and tables are related to each other.
- Cross reference: Commands to beans to database tables
  Use this information when you are customizing a command and you want to know which tables are affected. You should also use this topic if you are modifying a table and want to know which commands and beans are affected.
- API changes between WebSphere Commerce Version 7.0.0.9 and WebSphere Commerce Version 8.0.0.0
  If you are migrating version 7.0 of WebSphere Commerce, review the API changes between releases.
- WebSphere Commerce database schema
  The WebSphere Commerce database model was designed for data integrity and optimal performance. WebSphere Commerce provides several hundred tables that store WebSphere Commerce instance data. To maintain data integrity, and to ease maintenance referential integrity, constraints are widely used in the database model. Indexes are used carefully on tables to avoid over-indexing and to provide a good balance between data retrieval and data manipulation activities (insert and update). The business rules are implemented at the application level rather than by using database trigger. Triggers, however, are used to facilitate data staging and optimistic locking. A limited number of SQL-based database stored procedures are used for data intensive activities.
- Payments subsystem
  In WebSphere Commerce, payment processing uses the Payments subsystem.
- Dynamic caching
  In general, caching improves response time and reduces system load. Caching techniques are used to improve the performance of World Wide Web Internet applications. Most techniques cache static content (content that rarely changes) such as graphic and text files. However, many websites serve dynamic content, containing personalized information or data that changes more frequently. Caching dynamic content requires more sophisticated caching techniques, such as those provided by the WebSphere Application Server dynamic cache, a built-in service for caching and serving dynamic content.
- Data Load utility configuration file schema
  The Data Load utility contains several configuration files. You can use the configuration file schema to understand and customize the data load configuration files.
- WebSphere Commerce web services
  WebSphere Commerce provides many web services.
- Utilities
  Utilities help you to accomplish administrative or configuration tasks, for example, loading data, publishing a store.
- Shopping flow URLs
  WebSphere Commerce shopping flow URLs are organized by subsystem.
- Ant targets
  A WebSphere Commerce instance can be created from the command line. The command-line utility uses Apache Ant to create the objects required. The targets are divided into several high-level groups that correspond to the environment that is to be configured.
  - Ant targets: Creating and configuring targets
    You can create and configure, the database, the application server, the Web server, WebSphere Commerce, and workspaces using Ant targets.
  - Ant targets: Removing configuration targets
    You can remove the WebSphere Commerce instance and the WebSphere Commerce Server using Ant targets.
    - RemoveCommerceServer
      The RemoveCommerceServer target removes the WebSphere Application Server configurations from the WebSphere Commerce instance. The Ant target removes the data source, JDBC provider, virtual hosts, and uninstalls the enterprise application. Finally, the web server plug-in configuration file is regenerated.
      - RemoveJaasAuthData
        RemoveJaasAuthData removes the JAAS authentication data used to store the database user ID and password. This JAAS authentication data object is used by the WebSphere Commerce data source.
      - RemoveDataSourceV5
        RemoveDataSourceV5 removes the Commerce data source configurations.
      - RemoveJDBCProvider
        RemoveJDBCProvider removes the Commerce JDBC provider configurations.
      - RemoveVirtualHosts
        RemoveVirtualHosts removes the Commerce virtual host configurations.
      - UninstallEAR
        UninstallEAR uninstalls the Commerce EAR configurations.
      - RegeneratePlugin
        RegeneratePlugin regenerates the Web server plug-in configuration file (plugin-cfg.xml) for the Web server definition. This target regenerates the Web server plug-in configuration file when there is a change in the virtual host settings. This target must be run for any changes to the virtual host configurations.
    - RemoveHTTPService
      If you are using a local IBM HTTP Server, the instance creation creates a Windows service to start/stop the instance's IBM HTTP Server configuration. RemoveHTTPService removes the instance's IBM HTTP Server start/stop service.
    - RemoveInstance
      RemoveInstance removes the WebSphere Commerce instance configuration completely such as the site data, bootstrap data, schema, application, Web server configuration (IBM HTTP server only), and instance configuration files.
    - RemoveInstanceDir
      RemoveInstanceDir deletes the WebSphere Commerce instance configuration directory and its contents.
    - UnregisterInstance
      UnregisterInstance unregisters the WebSphere Commerce instance from the Configuration Manager. Once the instance is unregistered, the Configuration Manager is not aware of the existence of the instance.
  - Changing config_ant utility password properties file
    Add passwords to a properties file so that you can hide passwords from the command prompt when you run the config_ant utility.
- Glossary

Ant target: RemoveJaasAuthData

RemoveJaasAuthData removes the JAAS authentication data used to store the database user ID and password. This JAAS authentication data object is used by the WebSphere Commerce data source.

Called by

RemoveCommerceServer

Prerequisites

The Administrative server must be running to run the RemoveCommerceServer target and any subtargets.
The createInstance.properties file must exist for this Ant target to work. For information about generating the properties file, see Ant targets.

Required parameters

instance_name: The name of the WebSphere Commerce instance with which you are working (for example, demo).

Example

WC_installdir/bin/config_ant.sh -DinstanceName=instance_name RemoveJaasAuthData
WC_installdir/bin/config_ant.bat -DinstanceName=instance_name RemoveJaasAuthData