3D PLM PPR Hub Open Gateway |
ENOVIA VPM V4
|
CATIA V5 and ENOVIA VPM V4 Interoperability
|
| Technical Article | ||
AbstractThis article describes the architecture for interoperability between
CATIA V5 and ENOVIA VPM V4. It first briefly presents the main concepts
of VPM V4.Then it explains how the communication channel between CATIA
V5 and VPM V4 works. Finally it explains how the Unix Long Field
repository can be accessed through the interoperability. |
ENOVIA VPM V4 is a product of the ENOVIA Solutions product line whose objective is to enable companies to achieve quality, time and cost benefits by addressing the requirements for the management of product information throughout the entire product life cycle and across the extended enterprise.
ENOVIA VPM V4 product delivers a Unix client application directly connected to the Database Manager (DB2 or Oracle).
The main modules of ENOVIA VPM V4 are:
The functional highlights of ENOVIA VPM V4 are:
The VPM V4 Unix client proposes a direct connection with CATIA V4 and CATIA V5 enabling create and save new CATIA V4 and CATIA V5 documents in the VPM V4 vault. On Windows, the ENOVIA 3Dcom client coupled with its VPM V4 plugin enables interoperate with CATIA V5
[Top]
CATIA documents are stored in the VPM V4 vault by means of Long Fields accessed by different available methods called Access Methods. The standard access methods are:
Customers can also implement their own access method to store their V4 models and V5 documents in the VPM V4 vault.
[Top]
Any CATIA V5 file type can be stored in the VPM V4 vault. The most usual types are CATProduct, CATPart and CATDrawing. All the CATIA V5 documents are stored in Publication Exposed mode, except the CATProduct that can be stored either in Publication Exposed mode, either in Structure Exploded mode:
The CATIA V4 models are stored in Publication Exposed mode too, except the CATProduct that can be stored either in Publication Exposed mode
[Top]
The purpose of the CATIA V5 interoperability with VPM V4 is to establish a connection between the CATIA V5 application and the VPM V4 application in order to load into the CATIA session existing assemblies and documents that are stored in the ENOVIA VPM V4 vault. Then, the documents that might have been modified by the application can be saved back to the ENOVIA VPM V4 vault. This interoperability capability consists in setting up a communication channel between the CATIA V5 application (batch or interactive) and the ENOVIA VPM V4 application. On Unix, the CATIA application is able to connect to a running VPM V4 client. On Windows, the connection to an existing VPM V4 client on Unix is not possible. In this case, the connection must be established with a specific application running on a remote Unix server called VX0SERV. The VX0SERV application can be launched by the client application itself or can be run as a deamon.
In the next section, we detail the required environment setting to communicate with the VX0SERV application.
|
|
[Top]
[Top]
This section first explains the principles of the communication channel between CATIA V5 and the VX0SERV server application. Then it describes the required environment set up on the Unix remote server and on the Windows or Unix client.
... catcom 7201/tcp |
... catcom stream tcp nowait nobody /EnoviaVPMPathInstallation/JS0TLN JS0TLN -secured /home/data/vpmadm/MySec.txt |
Where “/EnoviaVPMPathInstallation/” is the absolute path of JS0TLN for ENOVIA VPM V4 installation. Besides JS0TLN must have only root read/write access mode. It must have the right to change access right for user and group (setgid bit).
Where MySec.txt file contains the security parameters identifying which userids can submit the process and from which client (IP address). It enables declare under which userid the process is run. For instance, in the next example, the user user27 running on host ip address 128.40.125.149 is authorized to run the process. The process will be run under vpmadm userid.
... HostAddr='128.40.125.149' RemoteUser='user27' LocalUser='vpmadm' |
#!/bin/ksh . /home/data/vpmadm/.profile . /home/data/vpmadm/env/YOUR.env . /home/data/vpmadm/env/VPMWsUser.sh export GlobalVPMServer=1 export VPMServerTimeOut=6000 VX0SERV >>/tmp/VX0SERV.log 2>&1 |
Where GlobalVPMServer variable enables xco connection with a VX0SERV server on a different machine for UNIX/UNIX communication.
Where VPMServerTimeOut variable defines the timeout of the server.
[Top]
set CV5VpmStart=/home/data/vpmadm/code/bin
set CV5_VPM_XCONT=1
[Top]
export CV5VpmStart=/home/data/vpmadm/code/bin
The interoperability between CATIA V5 en ENOVIA VPM V4 enables read the Long Fields stored on the Unix server and load the associated CATIA documents in the CATIA session. For Windows application, the Long Fields can be read either via a HTTP server access, either through a NFS access. Only the NFS access allows write access.
The HTTP server running on a Unix remote server can be used to access the Long Field directory. The HTTP access is activated by setting the HTTP_SERVER environment variable. For instance:
set HTTP_SERVER=arbi2dsy:80
For Unix client, the NFS access consists in mounting the NFS server directory on the client machine.
For Windows client, the NFS access requires the following setup:
[Top]
For Windows client, the CATIPDMUnixNTMapping interface enables convert the syntax of the Long Field path from Unix to Windows.
This User Exit has two methods to implement:
The interface implementation has to retrieve the name of the chosen drive and convert the syntax of the Long Field path.
The interface implementation has to set the full path of a file in a Unix directory in which the new Long Field will be written before ENOVIA vpm application finaly saves it in the ENOVIA vpm vault with the chosen access method.
[Top]
[Top]
| [1] |
| Version: 1 [Sep 2005] | Document created |
| [Top] | |
Copyright © 1994-2005, Dassault Systèmes. All rights reserved.