New Release Available in October – Stay tuned!
HaloCAD for Autodesk Vault

Appendix

This section provides supplemental information.

Failover Mechanism for HaloENGINE GenNXT in HaloCAD for PLM

Server failover between two systems supports uninterrupted operation and service reliability in the event of a failure. The server failover configuration is active-standby, where the primary server is active, and the secondary server is standby.

HaloCAD for PLM supports connection failover between two HaloENGINE GenNXT instances. The failover mechanism provides the following benefits:

  1. High Availability: If the primary HaloENGINE GenNXT fails, the secondary HaloENGINE GenNXT takes over, reducing downtime and maintaining continuous operation.

    Example: Assume that your business process requires no downtime.

    As part of the business security policy, the administrator configures Fail-Safe Mode as Strict to block file uploads or downloads whenever an error occurs. If HaloENGINE GenNXT encounters an unexpected issue and fails to obtain label information, file uploads or downloads are prevented. In such cases, the HaloENGINE GenNXT failover mechanism handles the situation without affecting the end user. If the primary HaloENGINE GenNXT connection fails, HaloCAD detects the failure and immediately switches to the secondary HaloENGINE GenNXT to continue providing services.

    Once the primary HaloENGINE GenNXT is restored, it remains in standby while the secondary HaloENGINE GenNXT remains active. If the secondary HaloENGINE GenNXT fails, the primary HaloENGINE GenNXT takes over operations again.

    Common_Failover-01.png

    Failover Mechanism for HaloENGINE GenNXT in HaloCAD for PLM

  2. Redundancy: Provides redundancy by ensuring that another HaloENGINE GenNXT is always available to take over if the primary HaloENGINE GenNXT fails. This minimizes the possibility of a single point of failure.

  3. Data Integrity and Consistency: In the event of a failure, the failover mechanism helps ensure that data remains consistent and that file upload and download activities are not lost. This is crucial for systems that rely on high data security.

  Failover Mechanism Requirement 

  1. Network Infrastructure: Deploy the secondary HaloENGINE GenNXT on a separate network segment from the primary HaloENGINE GenNXT.

  2. Data Replication: Ensure that both HaloENGINE GenNXT use the same classification profiles and rules.

Third-Party Libraries

Third-party software/code is included or bundled with Secude's products according to its appropriate license. Secude conducts testing to make sure the third-party products are compatible with and perform as intended with Secude applications.

The third-party libraries and dependencies used by HaloCAD for Autodesk Vault are shown in the table below.

Library names

Versions

Source Code URLs

License Links

HTTP-Proxy-Servlet


https://github.com/mitre/HTTP-Proxy-Servlet

https://github.com/mitre/HTTP-Proxy-Servlet/blob/master/LICENSE.txt

httpmime

4.5.+

https://mvnrepository.com/artifact/org.apache.httpcomponents/httpmime

http://www.apache.org/licenses/LICENSE-2.0.txt

mail

1.6.2

https://mvnrepository.com/artifact/javax.mail/mail 

Common Development and Distribution License (CDDL) v1.0 https://glassfish.dev.java.net/public/CDDLv1.0.html

commons-io

2.+

https://mvnrepository.com/artifact/commons-io/commons-io

https://www.apache.org/licenses/LICENSE-2.0.txt

jakarta.servlet-api

5.0.0.0

https://mvnrepository.com/artifact/jakarta.servlet/jakarta.servlet-api/5.0.0

https://www.eclipse.org/legal/epl-2.0/

jna

5.8.0

https://mvnrepository.com/artifact/net.java.dev.jna/jna

http://www.apache.org/licenses/LICENSE-2.0.txt
http://www.gnu.org/licenses/licenses.html

jna-platform

5.8.0

https://mvnrepository.com/artifact/net.java.dev.jna/jna-platform

http://www.apache.org/licenses/LICENSE-2.0.txt
http://www.gnu.org/licenses/licenses.html

activation

1.2.0

https://mvnrepository.com/artifact/javax.activation/activation

https://glassfish.dev.java.net/public/CDDLv1.0.html

jaxws-api

2.3.1

https://mvnrepository.com/artifact/javax.xml.ws/jaxws-api

https://github.com/javaee/jax-ws-spec/blob/master/LICENSE.md

jaxws-ri

4.0.1

https://mvnrepository.com/artifact/com.sun.xml.ws/jaxws-ri/4.0.1

https://oss.oracle.com/licenses/CDDL+GPL-1.1

rt

2.3.0

https://mvnrepository.com/artifact/com.sun.xml.ws/rt

https://oss.oracle.com/licenses/CDDL+GPL-1.1

stax2-api

4.0.0

https://mvnrepository.com/artifact/org.codehaus.woodstox/stax2-api

http://www.opensource.org/licenses/bsd-license.php

MIP SDK

1.18.124

https://learn.microsoft.com/en-us/information-protection/develop/version-release-history

https://docs.microsoft.com/en-us/information-protection/develop/

MSAL

4.82.1

https://github.com/AzureAD/microsoft-authentication-library-for-dotnet

https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/blob/master/LICENSE

Spdlog

 1.15.3

 -

https://github.com/gabime/spdlog

Third-party libraries

Autodesk Vault Metadata Definitions

The table below lists the Autodesk Vault metadata available in the HaloENGINE GenNXT.

Autodesk Vault Metadata

Use

lifecycle_state

Derivation from the lifecycle of Autodesk Vault data. (For example, work-in-progress, review, and released)

file_type

Derivation from file type. File types of AutoCAD, Inventor, and MS Office native file types. (For example, dwg, ipt, and iam)

folder_name

Derivation from the folder name in the Autodesk Vault server. (For example, $/DESIGNS/INVENTOR FILES/Jet Engine Model/Workspace/Design Accelerator)

preexpression_custom_pre-expression

Derivation from custom pre-expression.

  1. Yes

  2. No

Autodesk Vault metadata

Uninstalling the HaloCAD for Autodesk Vault

Once you stop using the HaloCAD component, you can uninstall it. Uninstalling removes all files and registry settings that were added to your computer during initial installation.

 Method #1 

  1. Click Start menu > go to Control Panel > Programs > Programs and Features > Uninstall a Program > select HaloCAD for Autodesk Vault application from the list > right-click and select Uninstall option or double-click on the installer HaloCAD_Autodesk_Vault_Setup.exe file.

  2. Depending on your Windows security settings, you may get a security warning as "Do you want to allow the following program to make changes to this computer?". If you get this security warning, click the Yes button to confirm that you want to uninstall the HaloCAD component.

  3. The following confirmation message appears.

    Uninstall Message #1.png

    Uninstall Message #1

  4. Click Yes to confirm that you want to remove it from the computer.

    Uninstall Message #2.png

    Uninstall Message #2

    Result

    • The HaloCAD component is successfully uninstalled.

    • Click OK to close the dialog.

    • The uninstallation process is complete.

    • Alternative method: Open Command Prompt as Administrator, then run this command: HaloCAD_Autodesk_Vault_Setup.exe -uninstall


Last updated: