Creating or Revising Tool Suites

You can create tool suites for a development area.

Required access roles:

  • App-specific: Defect Engineer
  • Baseline: Administrator, Owner, or Leader

  1. To create a tool suite:

    1. View the list of tool suites. See Design Tool Suites Page.
    2. Click Create .

    To revise an existing tool suite:

    1. Open the required tool suite. See Opening a Tool Suite.
    2. In the navigation pane, click Revisions.
    3. Click Revise .

  2. Enter these details:

    When creating a tool suite, these fields are blank. When revising a tool suite, the values for the existing suite show in all fields except Revision.

    Field NameDescription
    NameEnter a name for the tool suite.

    You cannot change the name when revising a suite.

    RevisionEnter a revision level for the design tool suite.

    If the tool suite type is DesignSync, the revision value must match the version number of the installed DesignSync system, such as 3DEXPERIENCE R2015x.

    DescriptionEnter descriptive text about the purpose of the tool suite.
    Tool Suite TypeSelect DesignSync or Other.

    A development needs at least one tool suite with the DesignSync type defined, and every development assignment must have a tool suite that includes a DesignSync type.

    If you select Other type, enter text to describe the tool suite in the box below the label.

    You cannot change the tool suite type when revising a tool suite.

    PlatformFrom the list, select the platform that the tools in the suite run on:
    • All
    • UNIX
    • Windows

    The list might include specific versions of operating systems, such as solaris_a64 and solaris_b64.

    Install PathEnter the path name to the tools on the platform.

    You must enter a path for a DesignSync type. You can use environment variables in your path.

    For DesignSync type tool suites, this value sets SYNC_DIR for the development areas that use this tool suite.

    ScriptEnter the path to scripts that run before the tool is started to set the environment for this tool suite. The value can include environment variables. For UNIX, you must use a bourne shell script (.sh). For Windows, you must use a DOS batch file (.BAT).

    See the Enterprise DesignSync Administration guide for more information about defining a script.

    Program GroupIf you selected All or Windows for the platform, enter the Program Group for this tool suite. You can enter a relative path.
    Starting DirectoryThe relative path to the development area directory to set as the current working directory (cwd) for the tool when it starts. The starting directory for a specific design tool can override this starting directory. Users can specify a different starting directory when they connect to their development area.

  3. Click Done.

If you revised a tool suite from the Tool Suites category for a development, the new suite is not connected to any DesignSync Server or development. However, if you revised the suite from the Tool Suites category for a server, it is connected to that DesignSync Server.

If you created this suite from the Tool Suites page for a DesignSync Server, the new suite is connected to that server AND to the organization that the server is connected to.

A DesignSync Server without any tool suites automatically uses all the tool suites connected to its organization. If you create a tool suite for a DesignSync server like this, the new suite is connected to the organization and not to the DesignSync server (because the server uses all of the suites connected to the organization).