Overview

About ENOVIA Business Process Services

ENOVIA Business Process Services provides the configurable user interface and schema for all the ENOVIA products, creating a framework or foundation for those products. It allows internal and external (such as suppliers) users to collaborate while maintaining access controls to data and provides a Metrics reporting capability to assess performance based on product data.

ENOVIA Business Process Services includes:

programs, such as triggers, to execute user tasks and business process logic
schema, such as routes, discussions, document management, used in multiple ENOVIA products
Java Server Pages needed to construct the user interface shared by all the applications

It can also be used as the basis for creating your own applications. See the ENOVIA Live Collaboration Schema Reference Guide for details about the installed schema; see the Studio Modeling Configuration Guide for information on creating your own applications or for customizing the installed applications.

ENOVIA Business Process Services must be installed before you can install any ENOVIA product. When an application is installed, it updates these items as needed for its features.

ENOVIA Business Process Services supports the entire ENOVIA suite of products.

An application can use common components to implement a feature or it can use its own programs. Most components are configurable so each application can tailor it as needed. For example, the checkin pages can be configured to show specific fields and attributes. If an application has requirements that are not included in the common component, it uses its own programs.

Published examples in this document, 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 and products and versions, and so on.

About Working with Schema

The administrative objects installed with ENOVIA Business Process Services control many aspects of functionality. For example, the policy that governs a business object type controls who can work with that kind of business object, what they can do, and during which states.

Configuring Using Schema describes some common configuration changes that you may want to make. All these changes can be made using Business Modeler or MQL.

When making changes to schema, remember these important points:

When changing names of administrative objects, change only the administrative object name, not the symbolic name. For more details on administrative and symbolic names, see the About Configuring.
If you remove the Originator attribute from a type, make sure you turn off the trigger that populates that attribute by removing the Create and Revision triggers from the type.
The application uses a string resource properties file to internationalize all onscreen text, including schema names. Changing schema names does not change the names displayed onscreen. For instructions on how to change the onscreen names for internationalized schema, including policy states and attributes ranges, see the Changing Onscreen Text.

Administrative Object Names

When you look at the administrative objects installed with ENOVIA Business Process Services, you may find that some object names are prefixed with "eService" and the version number of the installation. The installation program adds this prefix to prevent name collisions between objects in ENOVIA Business Process Services and objects in the existing database.

For example, if you install version 10.7.0.0 onto a database that contains a Part type, the installation program renames the Part type within ENOVIA Business Process Services to "eService10700~Part". Other administrative objects within ENOVIA Business Process Services that refer to the type--such as attributes for the type, relationships that connect the type, and policies that govern the type--refer to the framework Part type, now named "eService107000~Part." The installation makes no change to the existing Part type.

To see a list of the name collisions the system found during installation, open the file called "installFrameworkVERSION.log", where VERISON is the software version number. This file is in ENOVIA_INSTALL\studio\Apps\Framework\VERSION. The file also lists all the administrative objects installed or modified during installation. For instructions on configuring objects, using existing objects instead of the objects installed with ENOVIA Business Process Services, see About Configuring.

Application Components

Each ENOVIA application contains the items listed in this table.

Application Components
Item	For information, refer to:
Web pages used by the application's users	The user guide that accompanies the application.
Programs specific to the application	To configure programs and for descriptions of utility trigger programs, see "Configuring Using Schema" and "Triggers" in the Studio Modeling - BPS Administration Guide. For application-specific trigger programs, see the Administrator's Guide that accompanies the application. The Administrator's Guides are in PDF format and are located in `ENOVIAHOME\studio\Apps\APP_NAME\VERSION\pdf` For information on how to call the included JavaBeans in your custom applications, see the Javadocs located at: `ENOVIA_INSTALL\studio\Apps\APP_NAME\VERSION\Doc\javadoc`
Other administrative objects specific to the application, such as formats	The Administrator Guide for the application.
Business objects that accomplish system-related tasks, such as objects for automatically-naming objects and for executing trigger programs	For general information on how the objects function and how to configure them, see "Configuring BPS Functions" and "Configuring Using Schema" in the Studio Modeling - BPS Administration Guide. For a list of the objects included in the application, see the Administrator's Guide that accompanies the application.

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.

User External Authentication

If you are using a Single Sign On (SSO) application for user authentication, custom JPOs and special APIs must be set up in order to authenticate users accessing lifecycles, routes, and FDA approvals.

To set up external authentication for users accessing ENOVIA products, see "Login Behavior When External Authentication is Used" in the ENOVIA Live Collaboration Server Installation Guide.

To enable custom JPO authentication, see "Enabling External Authentication" in the ENOVIA Live Collaboration Server Installation Guide.

Getting the Most Out of This Guide

To get the most out of this guide, ENOVIA suggests that you review the table of contents. You only need to configure the objects/functions required by your company's business process needs.