16 March 2008

Part 2.1 - Enabling & Configuring Workflow

The optional (non-default) workflows can be activated by completing the following procedure:

  1. Verify that you have satisfied the following two requirements:

    • Install and license TeamSite (which now includes FormsPublisher)—Workflow email notifications use the presentation template compiler installed with FormsPublisher.
    • The permissions on the iw-home/tmp and the iw-home/tmp/cci directories must be readable and writable to all TeamSite users (the email notifications are temporarily placed in these directories while being created).

    And consider the following compatibility issues:

    • Install MetaTagger 3.6 or later (optional)—MetaTagger 3.5 and earlier are not supported. If you are integrating with MetaTagger, TeamSite must be installed before MetaTagger or the MetaTagger GUI will not work.
    • Install OpenDeploy 5.5.1 or later (optional)—You must have a base server on the TeamSite server.

  2. Open the iw‑home/local/config/wft/available_templates.cfg file (see available_templates.cfg).

  3. Add an entry for each new workflow.
    For example, to add the Author Submit Workflow workflow, add the following entry:

  4. <template_file name='Author Submit Workflow'
    <command name="submit"/>
    <role name="author"/>

    For your convenience, a file containing entries for each new workflow is provided. It is called available_templates.cfg.fragment and is located in the iw‑home/local/config/wft/solutions directory. You can copy any or all of the workflow entries from this file into your available_templates.cfg file.

  5. If you are replacing another workflow, you can deactivate it by any of these methods:

    • Delete the entry
    • Comment out the entry using <!-- -->
    • Add the attribute active=“no”

  6. Save and close the available_templates.cfg file.

  7. For each configurable workflow that you added to your available_templates.cfg file, edit the corresponding .cfg file to activate the desired functionality.
    The .cfg file contains question and answer pairings for each configurable option. For example, in the Email Notification section:

    # Should a email notification be sent if a deploy task fails? email_no_deploy=no

    Change the default from no to yes on any feature you want to activate. For a detailed description of the configurable features available in each workflow, refer to Configurable Workflow Settings.

  8. If you are using the Email Notification functionality:

    1. Ensure that your iw.cfg file contains entries for maildomain and mailserver in the [iwsend_mail] section.
      If it does not, add the appropriate entries. For example:
    2. Edit the solutions/email_map.cfg file to specify the mapping from user names to email addresses if adding @yourcompany.com to the username is not adequate.

  9. If you are using Metadata Capture functionality:

    1. Ensure that the metadata_capture_ui properties in the workflow-specific .cfg files have the desired setting for either MetaTagger or TeamSite Metadata
    2. Ensure that iw‑home/local/config/ contains datacapture.cfg and metadata‑rules.cfg files, and that these files contain the desired settings.
    3. Ensure the mt‑home/conf/metatagger.cfg file contains the desired entries. See MetaTagger Administration Guide “Configuring MetaTagger to Work with TeamSite” for integration instructions.
    4. Ensure that the category tag values in the metatagger.cfg file match corresponding item name values in the datacapture.cfg file.
    5. Optionally, test your metadata capture configuration from a custom menu item before you try it from a workflow.

  10. If you are using Deployment functionality:

    1. Copy the deployment configuration file (solutions/wft_opendeploy.xml) to the od‑home/conf directory.
    2. Edit solutions/wft_opendeploy.cfg file to specify the mapping from branch names to the corresponding destination nodes and paths.
      See Integrating with OpenDeploy for detailed information about these entries.

10. Ensure that yo have add appropriate TS groups and users in LDAP or AD. Then in TS, add all the groups and users. Then add the appropriate user to a group. Then assign roles to each added users.

No comments: