Native Apps installation

Discover the 3DEXPERIENCE platform with the 3DEXPERIENCE Launcher

ADMIN OR MEMBER
FIRST STEPS TO THE
3DEXPERIENCE PLATFORM

NATIVE APPS
INSTALLATION

The actions described in the native apps installation have to be performed as a Windows System Administrator. Please ensure that you have the admin rights or that you contacted your system administrator to prepare your computer to connect to the 3DEXPERIENCE platform.

Install the 3DEXPERIENCE Launcher

A Native Apps installation tool is required with 3DEXPERIENCE platform R2016x: The 3DEXPERIENCE Launcher.

1. A pop up window to download 3DEXPERIENCE Launcher installer will appear after clicking your rich app from the IFWE Compass if the 3DEXPERIENCE Launcher is not already installed on your computer.

2. After downloading it, you will need to run the 3DEXPERIENCE Launcher msi installer.

3. At the end of the installation the service will start and an icon will appear in the system tray.

 

If the icon doesn't appear, check the 3DEXPERIENCE Launcher troubleshooting.

 

 

 

Refresh your browser page before starting the Native Apps Installation process (type F5 on your keyboard).

Network Configuration Check

 

 

To run correctly, the 3DEXPERIENCE Launcher needs to be able to talk to other 3DEXPERIENCE Platform services locally on the machine. A wrong network proxy server setup can interfere if inaccurately configured. Please make sure or ensure with your IT network administrator that, if you have a proxy, it is accurately setup to authorize local communications (See troubleshooting section for more information).

Rich Apps Installation


Before you begin, to save space on your computer and secure the next installation steps, you may uninstall 3DEXPERIENCE R2016x rich client application code from your computer. For uninstall information please refers to troubleshooting installation section.

After the 3DEXPERIENCE Launcher installation completion, the Native Apps installation process will start while clicking on any Native Apps icon.

If you have issues, please check application launch and use.

Troubleshooting

A- The 3DEXPERIENCE Launcher was not installed


Check if you see this icon in the Windows system tray:
If you don't see it, this means that the 3DEXPERIENCE Launcher was not installed. Check that you have run the 3DEXPERIENCE Launcher msi installer after having downloaded it.

B- The 3DEXPERIENCE Launcher installation failed 

 

 

If the 3DEXPERIENCE Launcher installation process failed, open a Service Request to Dassault Systèmes Support with msi traces attached. To capture msi traces, please refer to QA00000035710.

 

MSI file installation failure:

MSI file type is used to install the 3DEXPERIENCE  Launcher.

This file may encounter installation failure and file corruption. So trace of the MSI installation needs to be generated for analysis.

 

Trace setup:

Inside a command window (cmd), type the following sentence:

msiexec /i "the_directory_where_you_have_downloaded_the_msi>\3DExperienceLauncher.msi" /L*v c:\temp\installlog.txt

 

Change the highlighted sentence by your own directory

Then get the traces generated inside c:\temp\installlog.txt


What is a MSI file?

Files that contain the .msi file extension store installer files for the Microsoft Windows operating system. 
When a user installs a Microsoft application onto his computer, the software uses a Windows Installer package to install the software onto their hard drive. The MSI file is what tells the computer which files to install and where to install the files on the user's system. 


The MSI file format is actually structured like a miniature database that is laid out in a structured storage file. 

 

 

 

C- The 3DEXPERIENCE Launcher is not running

To check if 3DEXPERIENCE Launcher is running, right click on the 3DEXPERIENCE Launcher icon in the Windows system tray and select About

 

 

There will be a balloon saying if 3DEXPERIENCE Launcher is running or not. 

If it is not running, you have to open a command prompt and launch services.msc. Then start 3DEXPERIENCE Launcher service.

D- Firewall or anti-virus software may be blocking the 3DEXPERIENCE Launcher

Right click 3DEXPERIENCE Launcher icon in the Windows system tray and click “About”. You will see the port number being used.

Check that your firewall/antivirus doesn't block the port number.

 

E- The proxy may be blocking the 3DEXPERIENCE Launcher

3DEXPERIENCE Launcher is installed and running. When user selects an app, there is a popup window to install the 3DEXPERIENCE Launcher. When user clicks to continue, after a few seconds, the same popup appears.
The issue might be on customer’s proxy configuration. The customer’s proxy configuration does redirect all requests to the proxy even if it’s bound to loopback addresses (127.0.0.1 / ::1 ). There is a workaround by adding an exception “dslauncher.3ds.com” on browser setting. A permanent fix consists to configure the user's proxy server correctly.

In Google Chrome

1. Go in Chrome Settings, in the Network paragraph click on Change proxy settings.

2. In Connections tab click on LAN settings button

3. In the Local Area Network Settings, Check Use a proxy server for your LAN and Bypass proxy server for local addresses. Then click on Advanced button.

4. In the Proxy Settings windows, add in the Exceptions field the address “dslauncher.3ds.com”. Use semicolon (;) to separate entries.

In Internet Explorer

1. Go in Internet Explorer options: Tools>Internet Options. In Connections tab, Local Area Network(LAN)Settings click on LAN settings button.

 



2. As Chrome open Internet Explorer settings, next step is similar to step 3-4 from Chrome proxy configuration above.

 

 

 

In Mozilla Firefox

1. Go on Firefox Options in Tools>Options>Advanced and then choose the Network tab>Connection >Settings button

2. In Connection Settings windows choose Use system proxy settings

Note: It is recommended to set Chrome or Internet Explorer configuration before setting Mozilla Firefox.
 
Click on OK to validate settings modifications for each browser.

F- The port number changed

During the installation, the 3 defaults port numbers were in use and the installer has been forced to choose a random one.
If the port number used by the 3DEXPERIENCE Launcher is not among: 20300, 33200, 40600 then enter the port number in the Troubleshoot panel.

G- Internet Explorer settings

If you are using Internet Explorer 11 on Windows 8, make sure that the “Enable Enhanced Protected Mode” option is deactivated. To do this, you can go to Internet Options, Advanced tab.

Still not working? Open a Service Request with 3DEXPERIENCE Launcher logs
If after these steps, you still face an issue, open a Service Request to support with 3DEXPERIENCE Launcher logs which can be found in this folder in R2016x: C:\ProgramData\DassaultSystemes\3DEXPERIENCELauncher\logs
If there is nothing in 3DEXPERIENCE Launcher logs, Dassault Systèmes Support will need msi traces. For this, please refer to the article QA00000035710 in the Knowledge Base below:


MSI file installation failure
MSI file type is used to install the 3DEXPERIENCE  Launcher.
This file may encounter installation failure and file corruption. So trace of the MSI installation needs to be generated for analysis.


Trace setup
Inside a command window (cmd), type the following sentence:
msiexec /i "the_directory_where_you_have_downloaded_the_msi>\3DExperienceLauncher.msi" /L*v c:\temp\installlog.txt
 
Change the highlighted sentence by your own directory
Then get the traces generated inside c:\temp\installlog.txt

What is a MSI file?

Files that contain the .msi file extension store installer files for the Microsoft Windows operating system.
When a user installs a Microsoft application onto his computer, the software uses a Windows Installer package to install the software onto their hard drive. The MSI file is what tells the computer which files to install and where to install the files on the user's system.

The MSI file format is actually structured like a miniature database that is laid out in a structured storage file.


Application launch and use

In case that you experience issues while using the application please consider the following steps:

Empty the working cache– Make sure to empty all Browser/Java cache, CATTemp and CATSettings before launching new setup

Browser / Java Cache:

Clear the Cache using the Java Control Panel available from Windows Control Panel >Java

For all other problems

If, despite all previously provided troubleshooting, you are still facing issues, we propose you to go forward in your troubleshooting experience through the following support experiences.

1. You can first consult our Dassault Systèmes Knowledge Base and cloud support resources either from our Cloud Support Communities or directly from our knowledge base.

Our Cloud Support Communities and Knowledge Base contains contents such as Q&A, Bug Reports, Documentation references, White Papers that may answer your questions.
Most of the troubleshooting information provided in previous paragraph has been extracted from this support resource.
Also from the Cloud Support Communities you will be able to ask your questions to your peers and share with others your own knowledge.
If you don’t find your answers navigating through the shared knowledge, you can report us a problem description and it will be handled by our Support teams.

2. You can also contact the Online User Excellence Center by call or chat (a pop up will appear if an agent is available) on the Could Support section.

Bandwidth and Latency considerations

When receiving a Service Request, DS will determine if this is due to an issue specific to network round trip latency or available bandwidth between Customer’s location of access of the DS Offering and DS’s data center. If the round trip latency is above one hundred twenty (120) milliseconds, and/or if the available bandwidth is below two (2) MBytes/sec, DS reserves the right not to provide Support Services.

Such round trip latency / bandwidth tests shall be performed following the procedure described here.