Running the instance creation command

Create your WebSphere Commerce instance silently by using Ant targets.

Before you begin

Prepare the createInstance.properties file by using the Configuration Manager. The Configuration Manager wizard validates all entries to ensure that the Ant target does not encounter errors when using the createInstance.properties file. For more information, see Preparing the createInstance.properties file
For IBM i OS operating systemYou must start the Configuration Manager server, then restart it before you continue. This prerequisite step is necessary because the Configuration Manager server prepares some files under WAS_userdir/instances/ that are needed by the instance creation process. You can skip this step if the Configuration Manager server has already been restarted.
  1. Starting the server
  2. Stopping the server

Procedure

  1. Windows Log in as a user in the Administrators group.
  2. AIXLinux Log in as the non-root user.
  3. For IBM i OS operating system Log on to your IBM i system as a user with SECOFR class authority.
  4. Windows Open a Command window.
  5. AIXLinux Open a command shell.
  6. For IBM i OS operating system Start a QSH session.
  7. Navigate to the WC_installdir/bin directory.
  8. Run the following command:
    • Windowsconfig_ant.bat -DinstanceName=instance_name [-DpasswordFile=passwordFile]
    • For IBM i OS operating systemAIXLinux./config_ant.sh -DinstanceName=instance_name [-DpasswordFile=passwordFile]
    Where:
    instanceName

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

    passwordFile
    Optional: The full path to the password properties file. The properties file can contain encrypted passwords that might be required when running the utility. For example, you can store encrypted database administrator (dbaPassword) or database user (dbUserPassword) passwords. Passwords that are entered on the command line take precedence over the passwords that are in the password file. For more information, see Changing config_ant utility password properties file.
  9. Consider changing the default WebSphere Application Server isolation level.
    Important: By default most WebSphere Commerce code runs database queries at specified isolation levels that are within safe tolerances for those individual queries. You can ensure optimal performance of your site by setting the default isolation level for WebSphere Application Server to Cursor Stability. For more information about how to set the default level of isolation for WebSphere Application Server, see Changing the default isolation level for non-CMP applications and describing how to do so using a new custom property webSphereDefaultIsolationLevel.

What to do next

Verify instance creation.