Our 3D CAD supplier models have been moved to 3Dfindit.com, the new visual search engine for 3D CAD, CAE & BIM models.
You can log in there with your existing account of this site.
The content remains free of charge.
The settings are
performed in the configuration file $CADENAS_SETUP/ifvault.cfg
.
Comments on the single setting options are found in the configuration file itself. In the following only an overview on the most important settings is given.
Determine locale library folder (Inventor project):
ROOTFOLDER_LOCAL=C:/CadData/CADENAS
Determine ROOT-VAULT-(library) folder[63]
In this folder the CADENAS parts are checked in.
The folder is mapped to ROOTFOLDER_LOCAL.
ROOTFOLDER=$/CADENAS
Selection of the local work directory - (Subfolder Yes/No?)
Especially important is the correct selection of the local work directory (corresponds to the pool path).
At a client server installation ensure that the local work directory of the CADENAS library is always to be found at the same location (e.g. C:\workdir\CADENAS)
|
When defining the local work directory = Pool path at the same time it is determined, whether for CADENAS parts subfolders have to be created:
Either a flat directory can be used (the definition always applies for both Vault and for "Local" likewise) or directory structure with subfolders (automatically created) can be used.
For the pool path directly "ROOTFOLDER_LOCAL" is used and for the VAULT folder directly "ROOTFOLDER".
poolpath=?context.getGlobalOption("CreationOptions","ROOTFOLDER_LOCAL")
VAULTFOLDER=?context.getGlobalOption("CreationOptions","ROOTFOLDER")
The above specification is enhanced by a slash "/" and other catalog folder names.
poolpath=?context.getGlobalOption("CreationOptions","ROOTFOLDER_LOCAL")&"/" &GetObject("iface.calcnameservice").start(0).Format("<CATALOGFOLDERNAME(1)>").value()
VAULTFOLDER=?context.getGlobalOption("CreationOptions","ROOTFOLDER")&"/" &GetObject("iface.calcnameservice").start(0).Format("<CATALOGFOLDERNAME(1)>").value()
Determine login data (compare Fig. „VAULT login“)
password=
user=Administrator
vault=Vault
Detailed information is found in the configuration file itself.
Therefor you have to create one category per vault in the section [CATEGORIES].
[CATEGORIES] ISTresor1=getObject("ifvault.service").GetVault()="Vault1"
Here the currently used vault is read from the interface (selection happened at login).
Furthermore the following keys have to be created for each vault:
ROOTFOLDER_LOCAL(ISTresor1)=
ROOTFOLDER(ISTresor1)=
poolpath(ISTresor1)=
VAULTFOLDER(ISTresor1)=
PLM_AdditionalColumn(ISTresor1)=?getObject("ifvault.service").GetVault()
If native parts are used, then the respective keys also have to be created for each vault. (See example in the configuration file itself.)
Store standard parts in PARTsolutions:
If native parts, which are already checked into Vault, shall be administered in PARTsolutions (PARTsolutions menu -> User library -> Insert), then the below listed keys have to be configured.
Analogously to the CADENAS parts directories there has to exist a Vault directory or local directory, where all “native” parts are saved respectively in which the "native" parts are downloaded.
ROOTFOLDER(isNat OR isNatCheckin)=
ROOTFOLDER_LOCAL(isNat OR isNatCheckin)=C:/CADDATA/StdTeile
VAULTFOLDER(isNat OR isNatCheckin)=?context.getGlobalOption("CreationOptions","ROOTFOLDER")
The pool path for "native" parts "/$RELNATPATH" is replaced by the subfolder structure read from Vault (if available).
poolpath(isNat OR isNatCheckin)=?context.getGlobalOption("CreationOptions", "ROOTFOLDER_LOCAL")&"/$RELNATPATH"
Checkout latest or old version?
With the key
checkout_newest_version
you
can control, whether the old or the latest version shall be checked
out.
checkout_newest_version=0/1
1 -> The latest version of a file is checked out. 0 -> The first version of a file is checked out - if there is an entry in PLMTABLE2.