Adding effectivity date parameters for database shard configuration

You can add the effectivity date and password parameters for a database shard. Using the effectivity dates, you can restrict the use of database shard configuration within a set of specified date ranges.

About this task

Along with the effectivity dates, you can define the corresponding passwords that will take effect for database shard configurations. You can define the <Name> <Value> pair for effectivity date and password parameter for database shard configuration in the following way:

Procedure

  1. In the Name column add effective.1 and from the Value column select the date and time from the drop-down window (for example, 2009-07-16T15:00:00).

    If you only select the effective date without selecting the timestamp, the system defaults the timestamp to the current timestamp.

  2. Similarly, in the Name column add password.1 and in the Value column add the required value (for example, mypassword).

    In this case, the password mypassword defined in the password.1 parameter will become effective on July 16th 2009 at 3PM as defined in the effective.1 parameter.

    The effective.n and password.n parameter names are case sensitive. Also, if the current database password is invalid as per the effective date, then database connection is established using previous valid password.

    You can define multiple number of effective date and password parameters for a given database shard configuration as shown in the figure below:

    Figure 1. Effectivity date and password parameters
    Manage DB Shard Connection window displaying a Shard Parameter List

    In Figure 1, the example attributes effective.1 and effective.2 contain arbitrary numbers that do not represent a sequence. Sterling Selling and Fulfillment Foundation does not enforce the use of any number or sequence in these attributes. However, the date that you enter for an associated value is tied to the password for that attribute. For example, in Figure 1, password.2 (associated with effective.2) takes effect on Thursday, February 28, and password.1 (associated with effective.1) takes effect on Thursday, November 29.

  3. After adding colonies, you must either use the synchronize feature in the System Administration Console or enter the manageColony command.