powered by CADENAS

Manual

Manual

3.3.11.6. Configuration within PARTsolutions

The settings are performed in the configuration file $CADENAS_SETUP/ifvault.cfg.

[Important] Important

Generally applies that no settings should be performed at the configuration files during current operation (that means when there have been already exported and checked in some parts). Some parameters have extensive influence on the integration. In case of doubt please always contact the CADENAS support!

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):

    Key: ROOTFOLDER_LOCAL

    Default:

    ROOTFOLDER_LOCAL=C:/CadData/CADENAS

  • Determine ROOT-VAULT-(library) folder[54]

    Key: ROOTFOLDER

    In this folder the CADENAS parts are checked in.

    The folder is mapped to ROOTFOLDER_LOCAL.

    Default:

    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)

    [Important] Important

    The CADENAS pool folder, where CADENAS creates all ipt/iam files, has to be configured at two places:

    1. in the file %CADENAS_SETUP%\ifvault.cfg (poolpath)

    2. at the assignment of the CADENAS folder within the Inventor project file (see Fig. „Enter library path“)

    When defining the local work directory = Pool path at the same time it is determined, whether for CADENAS parts subfolders have to be created:

    Create subfolders: Yes/No?

    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.

    • Without subfolders (default)

      For the pool path directly "ROOTFOLDER_LOCAL" is used and for the VAULT folder directly "ROOTFOLDER".

      Key Poolpath:

      poolpath=?context.getGlobalOption("CreationOptions","ROOTFOLDER_LOCAL")

      Key VAULTFOLDER:

      VAULTFOLDER=?context.getGlobalOption("CreationOptions","ROOTFOLDER")

    • With subfolders

      The above specification is enhanced by a slash "/" and other catalog folder names.

      Key Poolpath:

      poolpath=?context.getGlobalOption("CreationOptions","ROOTFOLDER_LOCAL")&"/"
       &GetObject("iface.calcnameservice").start(0).Format("<CATALOGFOLDERNAME(1)>").value()

      Key VAULTFOLDER:

      VAULTFOLDER=?context.getGlobalOption("CreationOptions","ROOTFOLDER")&"/"
       &GetObject("iface.calcnameservice").start(0).Format("<CATALOGFOLDERNAME(1)>").value()

  • Determine login data (compare Fig. „VAULT login“)

    Password:

    Key password:

    password=

    User:

    Key user:

    user=Administrator

    Database name:

    Key vault:

    vault=Vault

    Detailed information is found in the configuration file itself.

  • Support for several vaults:

    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"

    [Note] Note

    Files have to be stored in Vault before the function under PARTsolutions menu -> User library -> Insert is used. All standard parts have to be stored under ONE Vault root folder. Any subfolder structures are possible.

  • 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.

    Value range 0/1:

    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.



[54] also non-library folder are possible