Choosing the Installation Method

Locate the Assembly Media

The software is available on the following assembly media: AM_3DEXP_Platform.AllOS. It comprises several media.

Unzip and copy the contents of each media to a folder on your hard disk, and keep the same file structure. The folder contains directories 1, 2, 3, 4, 5, 6, 7 and 8.

You can install the software:

• using one of the two interactive installation procedures: Graphical User Interface (GUI) mode or Text User Interface (TUI) mode. In an interactive installation, the setup procedure prompts you to answer questions until the installation is complete. Even though the two methods are different, the list and the sequence of the questions are the same in both cases.
• in silent installation mode: you provide a previously generated response file to the setup, and the installation is complete without any interaction.

Choose the Installation Method

Before installing the 3DEXPERIENCE platform services, install the License Control service. For more information, see:

• Installation and Setup - Install - 3DEXPERIENCE Platform - License Control - DS License Server Installation and Configuration: explains how to install and configure the license server.
• Installation and Setup - Install - 3DEXPERIENCE Platform - License Control - DS Licensing Essentials contains more information about license control concepts and native-app side licensing tools.

Then, you have two choices:

• install the services individually by identifying the folder on the media containing the required service for your operating system
• or, use the global 3DEXPERIENCE platform installer by running the setup program in folder 1, that is useful for the reasons described in Deploying the 3DEXPERIENCE platform on a Single Machine

Whichever method you use, the following services are mandatory for an installation from scratch:

• 3DPassport service
• 3DDashboard service
• 3DSearch (Federated Search Foundation)
• 3DSpace service (contains 3DCompass and 6WTags), and 3DSpace Index
• Exalead CloudView
• 3DComment service
• 3DNotification service
• 3DSwym service

and the following service is optional:

• 3D Indexing Server

If you are installing the services one-by-one, we strongly recommend that you install the services in the following order:

Deploying the 3DEXPERIENCE platform on a Single Machine

For some reasons (for example, for training purposes, or on relatively small sites), you may want to deploy the 3DEXPERIENCE platform on a single machine to learn how it works before deploying the platform across your network. In this case, you can use the global 3DEXPERIENCE platform installer.

In this case, you need only one root URL for all the services, and distinguish the different services by their port number and URI. In this case, you need only one certificate for the whole platform (using the common URL).

The URLs could look like this, for example:

• 3DPassport service URL: https://3dpassport.mydomain:443/3dpassport
• 3DDashboard service URL: https://3ddashboard.mydomain:444/3ddashboard
• 3DSearch service URL: https://3dsearch.mydomain:448/federated
• 3DSpace Index configuration URL: http://FulltextSearchServer.mydomain:19000
• 3DSpace service URL: https://3dspace.mydomain:446/3dspace
• 3DCompass service URL: https://3dspace.mydomain:446/3dspace
• 6WTags service URL: https://3dspace.mydomain:446/3dspace
• 3DSwym service URL: https://3dswym.mydomain:447/3dswym
• 3DSwym Index configuration URL (3DSwym CloudView instance) : http://3dswym.fulltextsearch.mydomain:29000
• 3DComment service URL: https://3dcomment.mydomain:449/3dcomment
• 3DNotification service URL: https://3dnotification.mydomain:450/3dnotification

If you also use custom widgets in 3DDashboard, you will still need another URL and certificate.

The use of a reverse proxy is mandatory. You should use the same reverse proxy server (Apache httpd 2.4 is recommended), and database server instance (if possible). If you are not running Oracle DB, you can also use the same administrator and standard database users (which are, however, NOT recommended for production purposes). You can also use the same Java JDK/Server JRE for all services (with different TomEE instances). On Linux, you can also use only one OS user to run all services.

For more information, see the Global 3DEXPERIENCE Platform Installer guide.