Changing Profiles (without using GUI):

If the user has multiple profiles, the best way to reflect the changes directly:

1. Each profile has its own directory (with its own set of options)

Choose the profile that you want to change, cd into that directory

(eg

~/.pipeline/ConfigProfile_01)

Change options in appropriate configuration file (eg: executionConfig.xml)

2. ~/.pipeline/ directory always has the options of the profile currently in use (which is specified in configurationLoader.xml which just serves as a pointer)

3. Check configurationLoader.xml (for the profile being used currently)

Case 1: The profile that you changed is not the currently used profile

Action: You are all set -

Case 2: The profile that you changed is the currently used profile

Action: You would need to copy the changed option files (in this case: executionConfig.xml) into ~/.pipeline from (eg: ~/.pipeline/ConfigProfile_01)

--

Adding Configuration Options:

The following is the description of an option in serverConfiguration.xml -

--

For an option with a single value:

<option name="Hostname.Aliases" value="pipelinev3.loni.ucla.edu">

</option>


In this case, the option just has a name and value associated with it - So
to add new options with only a single value, one would just have an option
resource under 'options'
--

For an option with multiple choices:

  <option name="UserAccountManager" value="CURSUserAccountManager">

    <choices>

      <choice>

        <name>

          XMLUserAccountManager

        </name>

        <value>

          edu.ucla.loni.pipeline.security.XMLUserAccountManager

        </value>

      </choice>

      <choice>

        <name>

          CURSUserAccountManager

        </name>

        <value>

          edu.ucla.loni.pipeline.security.CURSUserAccountManager

        </value>

      </choice>

    </choices>

  </option>

The name {in eg: UserAccountManager} has two possible values - XMLUserAccountManager and CURSUserAccountManager - And each of those values
can have an actual value associated with them -

This level of indirection was needed to keep the names user-readable - To add
another value as a choice for UserAccountManager - one would just have to add
a choice resource with an appropriate name and value

The current value associated with UserAccountManager is an attribute of the
option -

--

-- JagadeeswaranRajendiran - 06 Jan 2006