Migrate from AIM-h to 3DVis OnPrem viewer

This section is intended for client currently using AIM-h to stream 3D models in an on-premises environment with AIMHybrid authentication and plan to migrate to the OnPrem 3DVis Viewer for 3D model streaming after upgrading to release 6.0 or later.

Note: This section is applicable only to AIM-h client using 3D on cloud. Clients who are using Windows or Azure authentication are not required to follow the below steps as they are already using OnPrem 3DVis Viewer for 3D model streaming.

To migrate AIM-h to OnPrem 3DVis Viewer you must follow these steps:

1. Install and deploy AIM 6.0 version or latest.

2. Deploy 3DVis OnPrem viewer. To deploy, refer Configure 3DVis OnPrem for more information.

3. Configure the authentication

   1. If you are using PCM integration or LaaS configuration then follow the instructions provided in these topics:

      • Integrate APCM with AIM

      • Configure LaaS

   2. If you are not using PCM integration or LaaS configuration then user can use the windows authentication. By default, deployment will be done with Windows authentication. Administrators need to enable to the windows authentication and disable the anonymous authentication in IIS Web site.

      

4. Log into import server machine.

5. Locate the EIWM files which has physical file reference and remove from staging area and place those files outside staging area.

   Note: Do not delete the tag reference EIWM files.

6. Open import controller and register database. Add the package with required details along with the 3D Model drop folder location in import package, refer Import Controller Tool for more information.

   

7. Process the deleted EIWM files using import server.

8. Collect all physical RVM and ZGL files. Store the files in staging area along with .vnet file. .vnet file contains context/subcontext of 3D model and Class ID.

   This Context/Sub context must be from the EIWM files of AIM-h Models.

   3. If all the existing AIM-h files are with same sub context then user can maintain single folder.vnet file for all files placed in that folder. Folder.vnet contains as below:
      

      <Object>

      <Context>

      <ID>SampleModelSub-Context</ID>

      </Context>

      <ClassID>3D MODEL</ClassID>

      </Object>
      Ex:
      

   
   

   4. If the existing AIM-h files are maintained with different contexts for each 3D file then user should maintain the [ModelName].vnet file for respective model.
      

      <Object>
      <ID>File ID </ID>
      <ClassID>3D MODEL<</ClassID>
      <Context>
      <ID>VPD</ID>
      </Context>

      </Object>

   Ex:
   
   

9. Process the physical files in import controller

10. Log into the Dashboard, search for processed files and open it.

    Note: If the 3D Models are not loading in UI then clear the cache and reload the page.