Importing Settings from One Project to Another

In a hierarchical, multiple-project environment in which settings are stored in a database under different projects, administrators may need to import or export a given set of settings from the Adm folder of one project to another. This enables you to guarantee, for example, that users on different projects are using the same administered settings. The SettingsImport command allows you to take a snapshot of the reference settings on the server at a specific point and deploy them where necessary.

  1. Analyze your project hierarchy and identify both the project exporting its settings and the project importing the exported settings.

    The following illustration shows a typical project hierarchy:



    In this example, you are going to export settings from the Adm folder of ProjectC and import them into the Adm folder of ProjectB.

  2. Open a Command Prompt window.

  3. Go to the following directory:

    C:\Program Files\Dassault Systemes\B211\intel_a\code\bin

  4. Enter the following command to get help on the import command options:

    SettingsImport -h
    Parameter Description
    -server serverName:port/RootURI Name of server, port and rootURI
    -user username Administrator username in P&O database
    -pwd password Administrator password in P&O database
    -context Role.Organization.Project Security context at logon; the Role must be VPLMAdmin
    -project projectname Name of the project from which you export the settings
    -download Executes the export
    -exportdir userdirectory Name of the user-defined local folder to which you export the project settings; the folder must already exist
    -importfrom projectname Name of the project from which you import the settings
    -importfromdir userdirectory Name of the project into which you import the settings
    -no_overwrite Prevents overwriting settings files already present in the destination project
    -h Displays help

  5. Export your settings from ProjectC.

    You can export settings:

    • to the Adm folder in your local cache
    • or to a user-defined export folder.

    To export the settings to your local cache, run the following command:

    SettingsImport -server serverName:port/RootURI -user username -pwd password -context Role.Organization.Project -project projectname -download

    For example:

    SettingsImport -server ve4al54dsy:8090/ematrix -user VPMADM -pwd VPMADM -context VPLMAdmin.Admin.Default -project ProjectC -download

    To export the settings to a user-defined export folder, run the following command:

    SettingsImport -server serverName:port/RootURI -user username -pwd password -context Role.Organization.Project -exportdir userdirectory

    For example:

    SettingsImport -server ve4al54dsy:8090/ematrix -user VPMADM -pwd VPMADM -context VPLMAdmin.Admin.Default -exportdir E:\users\exportedsettings

  6. Import your settings into ProjectB from ProjectC.

    You can import settings:

    • exported to the local cache of the exporting project, into the Adm folder of your local project
    • from the user-defined export folder containing exported settings, into the Adm folder of your local project.

    To import the settings to your local cache, run the following command:

    SettingsImport -server serverName:port/RootURI -user username -pwd password -context Role.Organization.Project -importfrom projectname

    For example:

    SettingsImport -server ve4al54dsy:8090/ematrix -user VPMADM -pwd VPMADM -context VPLMAdmin.Admin.Default -importfrom ProjectC

    To import the settings from a user-defined export folder, run the following command:

    SettingsImport -server serverName:port/RootURI -user username -pwd password -context Role.Organization.Project -importfromdir userdirectory

    For example:

    SettingsImport -server ve4al54dsy:8090/ematrix -user VPMADM -pwd VPMADM -context VPLMAdmin.Admin.Default -importfromdir E:\users\exportedsettings