Installing Additional Apps

This section explains how to install additional apps.

By default, the compilation of the JPOs (Java Program Objects) compilation when running BuildDeploy3DSpace_CAS.bat/.sh is not activated. To activate it:

  • On Windows, set the variable set do_jpo_compilation to true in <install_path>\win_b64\code\command\BuildDeploy3DSpace_CAS.bat.
  • On Linux, set the variable do_jpo_compilation to true in <install_path>/scripts/BuildDeploy3DSpace_CAS.sh.

Or launch MQL:

On Windows: <3DSpaceInstallPath>\win_b64\code\bin: mql

On Linux: <3DSpaceInstallPath>/scripts: ./mql

  • MQL<1> set context user creator ;
  • MQL<2>compile prog * force ;

Then you will be prompted to enter the password for the creator user.

  1. Stop the running TomEE instance.

    On Windows, stop the corresponding services:

    • 3DEXPERIENCE R2022x 3DSpace TomEE+
    • 3DEXPERIENCE R2022x 3DSpaceNoCAS TomEE+.

    On Linux, run the appropriate script:

    • <3DSpaceInstallPath>/scripts/TomEENoCAS_Shutdown.sh -force (without CAS)
    • <3DSpaceInstallPath>/scripts/TomEECAS_Shutdown.sh -force (with CAS)

  2. Install the apps.

    On Windows, run the appropriate command:

    < AppName.Windows64\1> setup.exe –installerPath <Path to DS_Installer.Windows64\1>

    On Linux, run the appropriate command:

    <AppName.Linux64\1$./StartGUI.sh –installerPath <Path to DS_Installer.Linux64/1>

  3. Rebuild the war archives and redeploy them in the appropriate TomEE instance.

    On Windows, use the appropriate desktop shortcut (by right-clicking Run as administrator) , or run the appropriate script:

    • <3DSpaceInstallPath>\win_b64\code\command\BuildDeploy3DSpace_NoCAS.bat (without CAS)
    • <3DSpaceInstallPath>\win_b64\code\command\BuildDeploy3DSpace_CAS.bat (with CAS)

    On Linux, run the appropriate script:

    • <3DSpaceInstallPath>/scripts/BuildDeploy3DSpace_NoCAS.sh (without CAS)
    • <3DSpaceInstallPath>/scripts/BuildDeploy3DSpace_CAS.sh (with CAS)

  4. If you are using an external tomEE, you need to copy the respective .war files (<3DSpaceInstallPath>/distrib/3dspace.war, <3DSpaceInstallPath>/distrib_CAS/3dspace.war, <3DSpaceInstallPath>/distrib_NoCAS/internal.war) in the webapps folder of each tomEE instance (CAS / NoCAS) (<TomEECAS_install_path>/ <TomEENoCAS_install_path>).

    If you are running Windows server, use the templates of setenvCAS.bat / setenv.bat that are ready in <3DSpaceInstallPath>/win_b64/templates/. You can copy them in the “bin” folder of each tomEE instance.

    If you are running Linux server, mxEnvCAS.sh or mxEnv.sh scripts must be sourced at the beginning of each startup.sh script of TomEECAS / TomEENoCAS instance.

    For example,

    • for TomEECAS, you must add this line in the second position of <TomEECAS_install_path>/bin/startup.sh: . <3DSpaceInstallPath>/scripts/mxEnvCAS.sh

    • for TomEENoCAS, you must add this line in the second position of <TomEENoCAS_install_path>/bin/startup.sh: . <3DSpaceInstallPath>/scripts/mxEnv.sh