Administer > Deploy > Overview: WCBD > Configure and run the server deployment process


Configure the server deployment settings


Overview

Configure the server deployment settings before running the server deployment script. These settings consist of important information like software installation paths and key information about your WebSphere Commerce server.

To save time when configuring a new server deployment package, you can provide the following assets...

...and include them on the build system in...

WCBD_INSTALL/deploy/server

These assets will be included in the new server deployment package, reducing the amount of configuration required.


Configure server deployment settings

  1. Rename files and set permissions...

    cd $WCBD_DEPLOY_SERVER
    cp wcbd-setenv.template setenv
    cp wcbd-deploy.private.properties.template deploy-target-env.private.properties
    cp wcbd-deploy.properties.template deploy-target-env.properties.
    chmod 755 setenv
    chmod 755 deploy-target-env.*

  2. Edit setenv and set...

  3. Edit...

    deploy-target-env.private.properties

    ...and set your values. Properties in this file will be encoded when the deployment process is executed.

  4. Edit...

    deploy-target-env.properties

    ...and configure the file according to the comments in the file. Although the file is lengthy, it is important that you read all the descriptions and set the properties accordingly.

    The following table describes the minimal list of server deployment configuration properties to be set and tips on finding the value

    Property name Tips
    connector.module.list
     
    ejb.module.list
     
    java.module.list
     
    existing.web.module.list It is generally not a standard practice to add a new Web module in a WCS customization project, as such this project will most likely be empty.
    new.web.module.list Can be skipped if new.web.module.list is empty.
    context.root.mapping.list
     
    wc.instance.name
     
    wc.home
     
    was.home
     
    was.host.list
     
    was.port The value of the SOAP_CONNECTOR_ADDRESS property in...

    WC_PROFILE/logs/portdef.props
    db.name The value of the dbName property in...

    WC_INSTALL/instances/instance/properties/createInstance.properties

    ...on the WCS server from which the WCS instance is created.

    db.schema.name The value of the schemaName property in...

    WC_INSTALL/instances/instance/properties/createInstance.properties

    ...on the WCS server from which the WCS instance is created.

    jdbc.url It is important to use the remote JDBC URL.
    jdbc.driver The value of the jdbcDriver property in...

    WC_INSTALL/instances/instance/properties/createInstance.properties

    ...on the WCS server from which the WCS instance is created.

    jdbc.driver.path
     
    datasource.jndi.name
     
    idresgen.customizer
     
    massload.customizer
     
    static.web.deploy.ant.file
     
    wc.server.sync.ant.file
     

  5. Optional: The server deployment process can be configured to send out e-mail notifications upon success or failure. In a build failure notification, the zipped log files are attached for convenience. This functionality can be enabled and configured as follows:

    1. Edit...

      deploy-target-env.properties

      ...and set the properties under the section...

      Properties for e-mail notification

    2. Edit...

      deploy-target-env.private.properties

      ...and set the following properties if the SMTP server requires authentication:

      • mail.user
      • mail.password


Previous topic: Set up the WCS configuration file synchronization Ant script


Next topic: Run the server deployment process


+

Search Tips   |   Advanced Search