Overview

About ENOVIA Library Central and ENOVIA Library Experience

This Administrator's Guide covers these ENOVIA products:

• ENOVIA Library Central
• ENOVIA Library Experience
• Semiconductor Accelerator for IP Management

These products provide an efficient way to store, manage, and access documents and other files within and across applications in a collaborative work environment.

In this Administrator's Guide, "Library Central" refers to all of these products unless explicitly stated otherwise.

ENOVIA Live Collaboration users can access certain details about ENOVIA objects, however, all library-related data is only available to library members through the Library Experience license.

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/products/versions/etc.

Document Migration

Prior to version 10.5, document management was handled independently for each application. As of version 10.5, all ENOVIA products follow a common document model. If you upgrade from a pre-10.5 version of this application, you will need to perform the document migration procedure after installing all applications and integrations.

For information about the document migration procedure, see the Business Process Services Administrator's Guide.

Document migration is mandatory if you are upgrading to version 10.5 from an earlier version. If you do not perform the document migration, documents will not be rendered properly in the UI and/or users will not be able to download document files.

If you are installing an ENOVIA product without having any documents from pre-10.5 applications, you do not need to perform the document migration.

Document Library Migration

For V6R2013, the document library schema has changed to support hierarchical structures. If you upgrade from an earlier release, you must perform the migration procedure. See Migrating Document Libraries.

Library Central Roles

You can use roles to determine who can perform specified tasks in Library Central. The following roles are provided in Library Central:

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.

Business Process Services

Library Central is supported by a database schema called ENOVIA Business Process Services. These services contain all of the administrative objects needed to run Library Central and other ENOVIA products.

ENOVIA Business Process Services must be installed before you can install any ENOVIA product. These sections provide details about using ENOVIA Business Process Services to support Library Central:

• About Schema
• Vaults, Companies, and Users
• Test Persons

About Schema

The schema defines the object types, relationships, attributes, policies, and rules that govern the behavior of individual business objects that you create, modify, or manage using Library Central. Examples of such business objects are Libraries, Document Sheets, Route Templates, Approvals, Owners, and Groups

When you install Library Central, the installation program adds programs and business objects that make the application work with ENOVIA Business Process Services. For example, business objects are added that automatically name some types of business objects, such as Documents, and control trigger programs that automate business processes. The application also includes JavaServer Pages (JSPs). JSPs contain the HTML code that builds the application's user interface, and Java code that dynamically updates page content whenever the page is accessed. These JSPs reside in the application server's file system.

See Working with Schema for details on how you can customize schema for Library Central.

Vaults, Companies, and Users

You need to add create vaults, companies, and users.

For a description of adding vaults, companies, and users, see the Business Process Services Administrator's Guide. After creating the users, add them to the Library Central roles as appropriate.

Test Persons

If you installed the sample database, assign the role of Employee to the person objects listed here.

See Maintaining People Details for details. The Employee role lets these users access and use the Library Central suite:

• Test LibraryUser, Test1 LibraryUser, Test2 LibraryUser
• Test Librarian, Test1 Librarian, Test2 Librarian
• Test Reviewer, Test1 Reviewer, and Test2 Reviewer
• Test ReleaseManager, Test1 ReleaseManager, and Test2 ReleaseManager

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.

ENOVIA Collaboration Products

Library Central supports the integrations listed in this section.

• View/Markup
• Batch Printing
• PDF Rendering

For installing viewer products, such as VueLink and Spicer, refer to the installation guides produced by the individual companies. To register viewers, see "Setting Up 2D and 3D Viewers" in the Business Process Services Administrator's Guide.

For setting up batch printing and PDF rendering, see Installing and Setting Up Batch Printing and PDF Rendering.

Before Reading This Guide

To perform administrative setup and configuration tasks, you need to understand the following:

• The concepts, terminology, processes, and procedures in Library Central, as described in the Library Central User's Guide.
• The concepts, terminology, processes, and procedures of Business Process Services. Refer to the Application Exchange Framework User's Guide and Common Components User's Guide.
• The concepts, terminology, and processes related to ENOVIA Matrix Navigator, Business Modeler, System Manager, and/or MQL. See the following documents: Matrix Navigator Guide, Business Modeler Guide, System Manager Guide, and MQL Guide.

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

Library Central includes this user documentation.

• Online Help. After logging into the application, click the Help (?) tool in the toolbar of any page to access online help.
• The Library Central User's Guide is in .pdf format and requires Acrobat Reader to view.
• The ENOVIA Collaborative Services Help describes features common to ENOVIA products, such as company and user profile management, document management, discussions, issues, and route processing. This is accessible by clicking the Common Components Help link on any Help page and is also available in .pdf format.
• The AEF Help describes common features such as IconMail, generic searching, collections, and preferences. This is accessible by clicking the AEF Help link on any Help page and is also available in .pdf format.

Checklist for Setting Up and Configuring Library Central

To implement Library Central, certain software components must be installed, set up, and configured to match your business processes and environment.

These supporting components include the ENOVIA Studio Modeling Platform, the application server, and ENOVIA Business Process Services. The table below contains a list of supporting components that need to be installed and configured and where to get more information about each. For Library Central tasks, the table provides cross references to the section of this guide that details those steps and options.