Best Practices

3DEXPERIENCE on the Cloud

Native Apps Batch Installation

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved

Version 1.0 - 5/14/2018

Written by: Dominique Peronnaud

Validated by: Stephane Tronel
Edited by: Arati Desai

3DEXPERIENCE on Cloud R2018x FD02

Best Practices

Executive Summary
Every company wants to establish IT policies to ensure common and effective usage
of IT assets and above all want to protect their business and intellectual property.

Among these policies, a common practice is related to software deployment control

on employee’s computers. Users usually do not have sufficient privileges to install
the software by themselves and applications deployment is remotely controlled by
the IT Administrator.

This Best Practice is designed to help the IT Administrator to deploy 3DEXPERIENCE

on the Cloud Native Apps in compliance with the company IT policies.

3DS.COM © Dassault Systèmes

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

2
Best Practices

Contents
1. Introduction .................................................................................................................... 4
2. Downloading the Native Apps R2018x Media Files ........................................................ 5
3. Preparing the Deployment for New Installation (Admin IT Task) .................................... 7
3.1. Prerequisites .............................................................................................................. 7
3.2. Preparing the Template Installation ............................................................................ 8
3.3. Preparing the Automation of Installation in Batch Mode ............................................ 13
4. Deploying the Installation on Client Side ...................................................................... 15
4.1. Updating an Existing Installation ............................................................................... 15
4.2. New Installation ........................................................................................................ 16

3DS.COM © Dassault Systèmes

4.3. Opening an Elevated Command Prompt .................................................................. 17
5. Conclusion ................................................................................................................... 18
6. Document History ........................................................................................................ 19

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

3
Best Practices

1. Introduction
Whenever there is a Cloud 3DEXPERIENCE Platform update, the Client Native Apps
installations must be updated accordingly. Usually, this update is performed by the user
himself by launching 3DEXPERIENCE and from the Compass can request for an update for
the Apps. Only users with Windows Administrator rights are allowed to make updates.

Since R2018x FD02, the Native Apps client media installation files can be downloaded
directly from the 3DEXPERIENCE platform only by a platform Administrator. This
Administrator has the choice to download either the Full media files to perform a new
installation or the Delta media files which are suitable to update existing Native Apps
Client installations. Using these media files, the IT Administrator can perform Native Apps
installation update in batch mode on a remote client machine without the need of
launching 3DEXPERIENCE on every client machine.

During installation, run the Native Apps installer exe contained in these media files while
referencing a file which contains a list of components and roles to be installed. This file is

3DS.COM © Dassault Systèmes

called UserIntentions_CODE.xml. It is generated by the Native Apps installer and captures
the user options and roles selection when running the installation manually. This file is
located in the InstallData folder in the installation path.

For instance:

C:\Program Files\Dassault Systemes\B420\InstallData\UserIntentions_CODE.xml

In order to perform a new HotFix installation, the IT Administrator must select the
necessary list of components and roles to install and prepare for Template installation on a
machine. This task is explained in the next section. The UserIntentions_CODE.xml file
created during this installation will be referenced by the batch install.

For updating an existing Native Apps R2018x installation (from HotFix2 for instance) on a
client machine, you must refer to the UserIntentions_CODE.xml file which already exists
on the installation path.

Note: 3DLauncher and 3DDrive are not updated while updating the Native Apps using the
batch installation method. In case they both require an update; it must be performed by
the user when he is connected online on the 3DExperience Platform.

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

4
Best Practices

2. Downloading the Native Apps R2018x Media Files

1. Log in 3DEXPERIENCE as Platform Administrator and select Platform
Management>Members> Configure Apps Installation widget.

The following window appears.

3DS.COM © Dassault Systèmes

2. Download the Full: 3DEXPERIENCE R2018x HotFix 3 media file and un-zip it into a
shared folder. You should get the following views:

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

5
Best Practices

3. In Folder 1, you will find the StartUI.exe to be used for batch installation.

3DS.COM © Dassault Systèmes

4. Download the Delta 3DEXPERIENCE R2018x HotFix 3 media file and un-zip it into
a shared folder. You should get the following views.

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

6
Best Practices

5. In Folder 1, you will find the StartUI.exe that is used for Batch Installation.

3. Preparing the Deployment for New Installation (Admin IT

Task)

3DS.COM © Dassault Systèmes

Deployment is performed by a person with Windows Administrator rights on a machine
where the Template installation will be performed.

You need to prepare your typical 3DEXPERIENCE Native Apps installation as Template.
This installation must contain all the Native Apps Roles ordered and deployed on your
Cloud Tenant(s). This installation will be suitable for any member including, the members
you have already invited on your tenant(s) or ones whom you will invite in the future, or
even the members you don’t intend to grant all the Native Apps Roles. For this step, you
need to perform a local installation from the Full media files while selecting all the Roles
you have ordered.

Note: Template installations by selecting the MES Roles is illustrated in the sections
below.

3.1. Prerequisites
For the 3DEXPERIENCE R2018x HotFix3 batch mode installation, it is mandatory to have
.NET 4.6.2 as the minimum level. This .NET level must be installed on every client machine
that needs to be updated, prior to the installation task.

The official .NET 4.6.2 software can be downloaded from the link below:

https://www.microsoft.com/en-us/download/details.aspx?id=53344

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

7
Best Practices

3.2. Preparing the Template Installation

1. Go into

<shared_folder_New_Installation>\HF_NativeApps_3DEXP_OIF.Full.Windows64\1

2. Run setup.exe with administrator privileges, right click on setup.exe and, select Run
as administrator.
3. Click Next.

3DS.COM © Dassault Systèmes

4. Choose the installation folder. If there is no prior installation on the machine, the n
the default installation path is suggested. You can choose any other installation
path but the folder must be empty.

5. If there is already a R2018x installation on this machine, it will appear in the list.
You must choose another folder for this task. Then click Next.

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

8
Best Practices

The R2018x HotFix2 installation takes place in the default installation path. It is
recommended that you update this installation to HotFix3 rather than creating
another one.

6. In the example below, we choose to create a new installation in the

3DS.COM © Dassault Systèmes

E:\B420_HF3_TEMPLATE path and click Next.

7. Then enter a specific Identifier for this new installation and click Next. This
identifier will be captured in the UserIntentions_CODE.xml.

Choose B420_HF3 _TEMPLATE as an identifier.

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

9
Best Practices

8. Select the Roles to install and click Next. Here, select the MES Role.

3DS.COM © Dassault Systèmes

9. Depending on the Roles you have selected, following panel for Install all
additional content is displayed. Selecting MES Role only, here is the list of
Additional Content:

Should you select other Roles, the list of additional content could be that large:

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

10
Best Practices

3DS.COM © Dassault Systèmes

10. Whether you choose to Install additional content or not, click Next irrespective of
your selection. Depending on the Roles you have selected, the panel below is
displayed.
11. Select No Legacy Connector and click Next.

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

11
Best Practices

Installation starts with copying files to the installation folder.

…and Installing

3DS.COM © Dassault Systèmes

12. When the installation is complete. Click Close.

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

12
Best Practices

The UserIntentions_CODE.xml file is generated in the following folder:

E:\B420_HF3_TEMPLATE\InstallData

3.3. Preparing the Automation of Installation in Batch Mode

During the initial part of the installation process, the UserIntentions_CODE.xml file is
created. Reuse this file to perform a new installation on other client machines using the
batch mode deployment.

3DS.COM © Dassault Systèmes

Copy the UserIntentions_CODE.xml file located in the installation folder into the
<shared_folder_New_installation> folder so that it can be referenced from other
machines.

Create a LaunchNewInstall.bat file referencing to the UserIntentions_CODE.xml file. This

referenced file will be used for new installation. Note that Full media file must be used for
new installation.

For Instance:

echo on
rem ###
rem ### Mandatory option “--silent %USER_INTENTIONS%” to define the
UserIntentions_CODE.xml file
rem ### Mandatory option “--var TARGET_PATH” to define the installation path
rem ### Optional option “--var DSYRegIdent” to define specific Identifier for this installation
rem ###
echo "-------------------------------------------"
echo "-- 3DEXPERIENCE Native Apps Installation --"
echo "-------------------------------------------"

echo "Start new installation in batch mode..."

set MEDIA=\\<shared_folder_new_installation>\HF_NativeApps_3DEXP_OIF.Full.Windows64
set USER_INTENTIONS=%MEDIA%\UserIntentions_CODE.xml
set TARGET_PATH=C:\Program Files\Dassault Systemes\B420
set IDENT=B420_HF3

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

13
Best Practices

rem go in first folder of media

pushd %MEDIA%\1

StartTUI.exe --var TARGET_PATH="%TARGET_PATH%" --var DSYRegIdent=%IDENT% --silent

"%USER_INTENTIONS%"

echo "Installation End."

pause

Create a LaunchUpdateInstall.bat file referencing to the UserIntentions_CODE.xml file

which is located in the existing installation path on the clients machine. This
LaunchUpdateInstall.bat file will be used for updating the existing installation.

For instance:

echo on

3DS.COM © Dassault Systèmes

rem ### Mandatory option “--silent %LOCAL_INSTAL%” to define
UserIntentions_CODE.xml file
rem ###
echo "-------------------------------------------"
echo "-- 3DEXPERIENCE Native Apps Installation --"
echo "-------------------------------------------"

echo "Start update installation in batch mode..."

set
MEDIA=\\<shared_folder_update_installation>\HF_NativeApps_3DEXP_OIF.Windows64
set TARGET_PATH=C:\Program Files\Dassault Systemes\B420
set LOCAL_INSTAL=%TARGET_PATH%\InstallData\UserIntentions_CODE.xml

rem - go in first folder of media

pushd %MEDIA%\1

StartTUI.exe --silent "%LOCAL_INSTAL%"

echo "Installation End."

pause

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

14
Best Practices

4. Deploying the Installation on Client Side

Now that the Template installation is ready, the administrator must deploy the Native
Apps on every machine. If an existing installation already exists, it is recommended to
update it with the new HotFix level by running the update an existing installation
procedure documented in section 4.1 below. If not, apply the new installation procedure
documented in section 4.2.

4.1. Updating an Existing Installation

For updating existing installation on the client machine (session opened without
administrator right necessarily),

1. LaunchUpdateInstall.bat file, set the <TARGET_PATH> with the local R2018x

HotFix2 (or HotFix1) installation path (if different from default) you want to
update.

3DS.COM © Dassault Systèmes

2. Open an elevated command prompt with administrator right.
3. Run the LaunchUpdateInstall.bat file with call command.

For instance:

call
O:\MEDIA\HF_NativeApps_3DEXP_OIF.HF3.Windows64\LaunchUpdateInstall.bat

The installation update begins in the batch mode.

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

15
Best Practices

The view in <TARGET_PATH>InstallData is updated as shown below:

3DS.COM © Dassault Systèmes

From the 3DEXPERIENCE platform user point of view, before this batch update,
you could see HotFix2 in the Compass.

Once the local installation is updated, you will see HotFix3 in the Compass.

4.2. New Installation

For new installation on the client machine (session opened without administrator right
necessarily):

1. In the LaunchNewInstall.bat file, set the <TARGET_PATH> for the new installation.
You can choose a path different from the default installation path.

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

16
Best Practices

In our example, we have set it to E:\B420_HF3_LOCAL folder with

B420_HF3_LOCAL identifier.

2. Open an elevated command prompt (with administrator right).

3. Run the LaunchNewInstall.bat file with call command.

For instance,

call
O:\MEDIA\HF_NativeApps_3DEXP_OIF.Full_HF3.Windows64\LaunchNewInstall.
bat

The new installation is performed in batch mode.

3DS.COM © Dassault Systèmes

From 3DEXPERIENCE platform user point of view, you will see HotFix3 in the Compass.
Notice that the chosen Identifier is reflected in the displayed label.

4.3. Opening an Elevated Command Prompt

1. Click the Start button.
2. In the search box, type cmd and then press Ctrl+Shift+Enter. If done properly, the
User Account Control window will appear.
3. Click Yes to run the Windows Command Prompt as an administrator.

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

17
Best Practices

5. Conclusion
With such a methodology, an IT Administrator can automate 3DEXPERIENCE Native Apps
deployment on every targeted computer where all the installations are strictly the same.
Support and maintenance also becomes easier and cheaper.

This methodology applies to both a new installation and also for an update.

3DS.COM © Dassault Systèmes

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

18
Best Practices

6. Document History
Document
Revision Date Revised By Changes/Notes

1 Dominique
05/14/2018 Original
Peronnaud

3DS.COM © Dassault Systèmes

Our 3DEXPERIENCE® platform powers our brand applications, serving 12 industries, and provides a rich
portfolio of industry solution experiences.
Dassault Systèmes, the 3DEXPERIENCE® Company, provides business and people with virtual universes
to imagine sustainable innovations. Its world-leading solutions transform the way products are designed,
produced, and supported. Dassault Systèmes’ collaborative solutions foster social innovation, expanding
possibilities for the virtual world to improve the real world. The group brings value to over 210,000
customers of all sizes in all industries in more than 140 countries. For more information, visit
www.3ds.com.

Confidential Information. © [2018] Dassault Systèmes. All Rights reserved.

This document is intended for internal use only and is provided for information purpose. Any other use without the written prior authorization from
Dassault Systèmes is strictly prohibited, except as may be permitted by law.

19