Add a colony in silent install mode

About this task

You can create colonies in silent install mode by creating an addColony.xml file that you can pass with the manageColony command. This file contains colony and database information that is required when you add a colony. In addition, you can specify multiple passwords and their effective dates, predefining passwords for a given pool months in advance. These passwords will change on the fly without a server restart. Adding colonies in silent install mode automates the process and limits manual interaction.

You can add colonies to your IBM® Sterling Selling and Fulfillment Foundation deployment as follows:

Procedure

  1. Create a silent addColony.xml file with a text editor. The file must contain the entries described in Parameters in the addColony.xml file.

    This table is followed by a sample addColony.xml file. After you edit the file, make note of its name and location (<path>), so that you can pass it with the manageColony command (see step 2).

  2. Enter the following command to add a colony:

    Windows: <INSTALL_DIR>\bin manageColony.cmd <path>\addColony.xml

    UNIX or Linux: <INSTALL_DIR>/bin ./manageColony.sh <path>/addColony.xml

    where <path> corresponds to the absolute path for addColony.xml.

  3. Repeat this command as necessary each time you want to create a colony, passing the XML file that is associated with each colony.
    Note: If deploying in multi-vendor mode, add and enable multiple vendors as follows. For example, to add an Oracle database vendor to your system:
    1. Copy the new dbdriver to <INSTALL_DIR>\dbjar\jdbc\Oracle\<DBJARFILENAME>.jar.
    2. Add the dbdriver path of Oracle to the DB_DRIVER parameter in <INSTALL_DIR>\properties\sandbox.cfg.

      For example: DB_DRIVERS=C\:\\Platform\\SI\\dbjar\\jdbc\\DB2\\db2cc4.jar;C\:\\Platform\\SI\\dbjar\\jdbc\\Oracle\\oracle.jar

    3. Modify sandbox.cfg and set multischema.multivendor.enabled=true.
    4. Run the install3rdParty utility and -targetJVM EVERY to add the new jar file to all classpath application servers and agents.
    5. Run the script <INSTALL_DIR>/bin/setupfiles.sh (for UNIX/Linux) or <INSTALL_DIR>\bin\setupfiles.cmd (for Windows).