3DSpace

3DSpace is a standards-based, open and scalable system that is able to support the largest, most complex, product lifecycle management deployments. It provides the flexibility to easily configure business processes, user interfaces, and infrastructure options to ensure that they meet your organization's needs. The system enables you to continually drive business process improvements to operate more efficiently using pre-built metrics reports, while virtual workplace capabilities enable ad-hoc collaboration for cross-functional and geographically dispersed teams to securely share product content. All product development content can be routed for review and managed in repeatable workflow business processes.

This page discusses:

See Also
Tcl Support
Configuring Windows Systems for Tcl

3DSpace provides the backbone for the 3DEXPERIENCE platform. 3DSpace is the underlying support for all ENOVIA apps and other Dassault Systemes apps for Product Lifecycle Management, which include native apps from CATIA, 3DLive, SIMULIA, and DELMIA product lines. It comprises the following end-user software components:

  • 3DSpace Service, which is a Java/RMI-based business object server. The Matrix Query Language (MQL ) command line executable is included with the server for the purpose of system installation and data/file storage setup functions only. If any other schema configurations are needed, Studio Modeling Native Apps must be licensed. Note that if distributed file stores are created with Sites and Locations, one or more ENOVIA File Collaboration Server licenses may also be needed. This is installed from CD 2: 3DSpace - Web Server.
  • Collaboration and Approvals, include the capabilities from the Application Exchange Framework, Common Components, Team Central apps. This is installed from CD 3: 3DSpace - Business Process Services.

The following administrative add-on is also available:

  • Studio Modeling Native Apps (DMP ) provides the development tools for a company to define and test configurations that are needed in their production system.

    Users of Studio Modeling Native Apps must be valid licensees of the apps that are configured and tested. However, a user's production license can also be used with the system installed for Studio Modeling Native Apps. The Studio Modeling Native Apps includes the following primary tool:

    • MQL - the command line interface tool for executing commands and scripts.
  • Studio Federation Toolkit (ADT ), which provides documentation and examples for writing custom programs that use the Adaplet libraries available in 3DSpace.The Studio Federation Toolkit must be licensed for each Studio Modeling Native Apps environment that requires development of custom connectors with the Adaplet APIs.
  • Studio Customization Toolkit (ADV ), which provides documentation and examples for writing custom programs and support web services client development. The Studio Customization Toolkit must be licensed for each Studio Modeling Native Apps environment that requires development of custom programming to change or extend standard ENOVIA capabilities.
  • File Collaboration Server (FCS ), which enables administrators to distribute file data across the enterprise for optimal upload and download performance. A system license is required for each physical site that requires remote file storage. There is no limit to the number of users that can use the File Collaboration Server at a given licensed site, however, all of these users must be licensed to use 3DSpace, which is the prerequisite.

This guide describes how to perform the following administration tasks for customizing your 3DSpace system:

  • Configuring 3DSpace. You can set environment variables according to your system needs. See "Configuring 3DSpace Service".
  • Integrating LDAP with external authentication tools. You can control web user access to the 3DSpace Service. See "Integrating LDAP with External Authentication Tools".
  • Configuring language. You can configure languages settings for these component: Collaboration and Approvals. See "Language Support".
  • Configuring a Japanese Web environment. You can configure and deploy the 3DSpace Service in Japanese. See "Configuring a Japanese Web Environment".

Before You Begin

Review the Program Directory. Each version of 3DSpace comes with media that includes the program directory for that release. The program directory is a website that organizes all the release information for all Dassault Systèmes apps for a given release. It contains information about prerequisites, installation, licensing, app enhancements, general issues, open issues, documentation addenda, and closed issues.

Conventions

When the Linux installation procedure asks for input, it provides the default value in brackets []. Default values for directory paths are based on the environment, so the examples in this book show empty brackets. To use the default, simply press Enter.

Throughout this guide, certain words appear in capital letters, which indicates that you need to enter specific information for your environment. Below is a description of some of the abbreviations that are used in this manner.

  • INSTALL_PATH: directory in which to install the software. Once installed, this may be referred to as one of:
    • ENOVIAHOME (UNIX) or ENOVIA_INSTALL (Windows) for Studio Modeling Platform, or
    • SERVERHOME (UNIX) or SERVER_INSTALL (Windows) for 3DSpace Service
  • PLATFORM : local platform architecture. Must be from the appropriate list in "Prerequisites" in the Program Directory for the given release.
  • HOSTNAME : name of the machine that applies to the current question.

Published examples in this guide, including but not limited to scripts, programs, and related items, are intended to provide some assistance to customers by example. They are for demonstration purposes only. It does not imply an obligation for ENOVIA to provide examples for every published platform, or for every potential permutation of platforms/apps/versions/etc.