About the Product Architecture

ENOVIA Live Collaboration uses the ENOVIA Studio Customization Toolkit and ENOVIA Business Process Services to develop applications.

The following topics are discussed:

PLM Layers

The Studio Customization Toolkit

The ENOVIA Studio Customization Toolkit is a low level Java API into the system. The ENOVIA Studio Customization Toolkit is responsible for manipulating the atomic object in the system such as Business Objects and Relationships and provides documentation, source code, sample files, and wrapper code that may be used as a reference for custom programming.

You can use the classes available in the applet or servlet jar files that are installed with ENOVIA Live Collaboration software (eMatrixAppletXML.jar and eMatrixServletRMI.jar). When you install the ENOVIA Studio Customization Toolkit, you get the javadoc for every ENOVIA Live Collaboration class that is included in all the .jar files, as well as source code that can be used as examples. For information about installing the ENOVIA Studio Customization Toolkit, see the Studio Modeling Installation Guide.

When you develop and compile against one of the servlet jar files, you can produce applications that use Java servlets, JPOs and JavaServer Pages (JSPs) to communicate with the database. The ENOVIA products (Engineering Central, and so on) are examples of applications that use the ENOVIA Studio Customization Toolkit. To build such an application, you first install the ENOVIA Live Collaboration Server you will run the programs on, and compile your code against the server's jar file. For example, if you are running the ENOVIA Live Collaboration Server, you need to compile against eMatrixServletRMI.jar.

Business Process Services

ENOVIA Business Process Services is a a collection of the defined schema, as well as JPOs and Java Server Pages (JSPs) that can be used with the ENOVIA Studio Customization Toolkit to write your own applications.

ENOVIA Business Process Services is a combination of common UI elements, such as Tables, Forms, Common Search Dialogs, and Type Choosers. The common schema allows all the application to coexists and share data. The schema consists of instances of business objects, relationships, and attributes.

ENOVIA Business Process Services also includes the Java programming code needed to manipulate the pre-defined schema. ENOVIA Business Process Services makes ENOVIA Studio Customization Toolkit calls to work with the kernel.

The ENOVIA products (such as Engineering Central or Library Central) provide out-of-the-box process definitions on which to base your implementations. They consist of JSP pages, JPOs and other application-specific schema. These applications provide flexibility in that they are highly configurable. First, they can be configured by making changes to the underlying schema, such as adding (or removing) a command to a menu or channel, adding (or removing) a column to a table, or adding (or removing) access to a column or command by a user, group, or role. Another way to configure the applications is via standard J2EE mechanisms. XML files define parameters for the applications which are then encompassed during J2EE deployment. If necessary, you can also modify existing JPOs or add new ones to extend the application as required.