Installing multiple 3DSpace instances in load balancer environment

When installing multiple 3DSpace instances in load balancer environment, 3DSpace instances can be duplicated in several hosts by this method. In all these multiple 3DSpace installations: the installation directory path, database details, file storage directory and all other installation inputs must be the same.

Note:
  • The TomEE port can be different for multiple instances.
  • In this service duplication method, 3DSpace uses embedded Java and embedded TomEE.

Before you begin: The ‘File storage directory’ used in 3DSpace installation must be shared between 3DSpace_host1 and 3DSpace_host2, and accessible in read/write/execute mode by both 3DSpace instances. Use a mounted path for the file storage directory.
  1. Install 3DSpace R2022x GA level in 3DSpace _host1, uncheck option ‘Configure and launch Full test Search indexing just after 3DSpace installation’.
  2. Install 3DSpace R2022x Hot Fix in server 3DSpace_host1.
  3. Copy 3DSpace installation from 3DSpace_host1 to 3DSpace_host2.
  4. Reconfigure 3DSpace installation in 3DSpace_host2, do not change any input value while reconfig.

    Reconfigure will:

    Windows : Create and start NoCAS_TomEE and CAS_TomEE services.

    Linux: Start NoCAS_TomEE and CAS_TomEE services.

    The first 3DSpace instance is available on 3DSpace_host1 and the second instance is available on 3DSpace_host2.

  5. Perform post install indexing activity ( baseline indexation, partial indexation, create a crontab entry ) in only one 3DSpace instance but not in both instances.