Overview

Application Components

Each ENOVIA application contains the items listed in this table.

Directories for Shared and Common Components

Some applications, such as Materials Compliance Central, install other components that may be shared between applications.

When this is the case there are 2 directories installed under ENOVIA_INSTALL\studio\Apps\, one which includes "base" in the name, such as MaterialsComplianceBase. These base directories are where the doc directories can be found.

The documentation that describes the common components that are installed with Business Process Services can be found in the ENOVIA_INSTALL\studio\doc directory.

Use of General Clients

Some of the instructions in this and other administration guides require the use of a general Matrix client navigator. It is important to restrict the use of these general navigator applications to only a few specially-trained business administrators

These are the general client navigators:

• desktop version of Matrix Navigator (also known as the thick client)
• web version of Matrix Navigator (also known as the thin client, PowerWeb, eMatrixApplet, and the Web Navigator)

It is important to restrict the use of these general navigator applications to only a few specially-trained business administrators and to only the purposes described in the Application Exchange Framework User's Guide and applications' administrator's guides. ENOVIA applications run JavaBean code that requires data to have specific characteristics and conditions. For example, objects may have to have certain relationships defined, have specific values entered for attributes, be in specific lifecycle states, or be in particular vaults. When a person works within the ENOVIA application user interface, these data conditions are met. However, the general navigators are not necessarily aware of these conditions and therefore a person working within the general navigators can easily compromise data integrity.

Another reason to restrict access to the general clients is that certain actions have different results depending on where the action is taken. A command on a JSP page may include options (such as additional MQL clauses) to ensure that the operation is completed as the application expects, but a user in a general client has no guidance on what options should be chosen. For example, when a file is checked into ENOVIA Live Collaboration using a general client, the store set in the policy is used; when using an ENOVIA product to check in a file, the person or company default store is used regardless of the store set by the policy.

The general navigators must or can be used in the following situations:

• ENOVIA application features require data that cannot be created within the ENOVIA application user interface.

For example, some user profile information and template information must be created in a general navigator.

• Automated business rules and processes need to be configured, such as triggers and autonamers.
• Data needs to be investigated for troubleshooting, testing, or data conversion.

The general navigators should only be used in these situations, using the instructions provided in ENOVIA documentation, and only by specially-trained business administrators. Standard users of ENOVIA products should never be allowed to work with their data in a general navigator and external customers should never be given access to a general navigator. Also, using Studio Customization Toolkit applications or any programming interface that does not go through the applications bean layer has the potential to cause undesirable results within the ENOVIA product data.

Administrator Documentation

ENOVIA provides the following administrator documentation:

• Program Directory. Each version of the application comes with media that include the program directory for that release. The program directory is a website that organizes all the release information for all Dassault Systemes products for a given release. It contains information about prerequisites, installation, licensing, product enhancements, general issues, open issues, documentation addenda, and closed issues.
• Live Collaboration Administrator's Guide. This guide explains how Business Administrators can configure Business Process Services. This guide is for people in the host company who will configure the application. Some understanding of Studio Modeling Platform products, such as Matrix Navigator and Business Modeler, is required.
• Live Collaboration Schema Reference guide. This guide describes the schema and data models that underlie the ENOVIA products.
• Studio Modeling Configuration Guide.This guide provides the details required to develop a custom program using the Business Process Services framework.

User Documentation

ENOVIA provides the following user documentation:

• X-BOM Manufacturing User's Guide and online help

This guide is available in HTML format as a context-sensitive online help system. It describes how to use features installed with X-BOM Manufacturing. Access this help system by clicking on any X-BOM Manufacturing-specific application page.

• Engineering Central User's Guide and online help

This guide is available in HTML format as a context-sensitive online help system. It describes how to use features installed with Engineering Central. Access this help system by clicking on any Engineering Central-specific application page.

• Application Exchange Framework User's Guide and online help

This guide describes common features such as IconMail, generic searching, collections, and preferences. Access this help system by clicking on any AEF page.

• Common Components User's Guide and online help

This guide describes features common to ENOVIA products, such as company and user profile management, document management, discussions, issues, and route processing. Access this help system by clicking on any Common Components page.