Transferring Resource Sets from a Server to Another Server

You can automatically duplicate resource sets customization from one server to another.

The standard process for migrating resources from a server to another is the following:

  • Migrate the P&O using the VPLMPosExport batch and the exportdatasetup option.

    For more information, see Installation and Setup: Configure: People & Organizations and Content: Persons, Organizations, and Collaborative Spaces: Importing and Exporting People, Organization, and Security Data: Running the VPLMPosExport Batch Tool.

  • Export the Data Setup resources in 3dxml format.
  • Import the .3dxml file to the new server using the CATRefImportAndDeployRscsets executable (see below).


Before you begin: You must have exported the P&O.
  1. In the Top Bar Search box , enter rscset: name_of_the_resource_set to search for the resource set you want to export.
    A list of resource sets displays.
  2. From the list, select the resource sets you want to export, and from the Share menu, select Export.
    The Export dialog box displays.
  3. Select the required options and click OK.
    The .3dxml file is exported.
  4. In a command window, enter the following command:

    <Installation directory>\win_b64\code\bin\CATSTART.exe
    -direnv myEnv -env IndexEnv
    -run "CATRefImportAndDeployRscsets -env VPM1 -server SERVER_URL
    -import_ticket IMPORT_TICKET
    [ -deploy_context DEPLOY_CONTEXT ]
    file1.3dxml"

    Where:

    Parameter Description
    myEnv

    Absolute path to your 3DEXPERIENCE platform environment file, which contains a set of runtime environment variables.

    For more information, see Installation and Setup: Install: 3DEXPERIENCE Platform: Installing 3DEXPERIENCE Platform Services for the First Time: Installing Services One-by-One: Native Apps: Configuring the Software: Configuring Environments: What Is an Environment?

    <Installation directory>

    Absolute path to the directory where the 3DEXPERIENCE platform was deployed.

    IndexEnv

    Valid file name without suffix.

    SERVER_URL

    URL of the server. For example: http://ve4al623dsy:10490/ematrix

    IMPORT_TICKET

    Ticket generated with a role granting 3D XML import rights. By default, it is typically Leader/VPLMProjectLeader.

    For more information about tickets, see Installation and Setup: Configure: People & Organizations and Content: Login Tickets: Managing Login Tickets.

    DEPLOY_CONTEXT

    Security context granting deployment rights. By default, it is typically Owner/VPLMProjectAdministrator.

    file1.3dxml

    Full file name of the 3DXML file to import. There can be several ones.

    Notes: The executable enables you to:
    • Perform an "import as ref" of the specified 3D XML files to repeatedly import the same 3D XML files.
    • Perform a "deploy" operation on the imported resource sets of these 3D XML files.

  5. Import the P&O.