Data Management

Information that must be shared from 3DEXPERIENCE to TechCenter or the ERP is managed at least temporarily by the Bridge tool.

By default, this data is stored in the folder <install_dir>\VISBridge\data

The size of this folder depends on the amount of messages exchanged between Bridge and other systems (minimum size 1GB).

Configuration:

  • Change file <install_dir>\VISBridge\zookeeper-3.4.11\conf\zoo.cfg

dataDir= C:\\App\\VISBridge\\data\\zoo-data


  • Change file <install_dir>\VISBridge\kafka_2.11-1.1.0\config\server.properties

log.dirs=C:/App/VISBridge/data/kafka-logs


Techcenter specific

An exchange folder for heavy data (files) is used and must be visible by Bridge and TechCenter.

  • Change file <install_dir>\VISBridge\config\VISWorker.properties

visbridge.config.checkout.temp.path = \\\\VSOL-DEV2017X/visbridge-temp


Specific ERP

  • Change file <install_dir>\VISBridge\config\VISWorker.properties

# Location of the root elements exported from the 3DEXPERIapplication

# This is a UNC path

visbridge.config.checkout.erp.path = \\\\VSOL-DEV2017X/visbridge-temp/erp/export


# Location of the temporary folder for the files during the export

# Relative to the erp export path

visbridge.config.checkout.erp.path.files.folder = export


# Location of the root elements to import in the 3DEXPERIENCE application

# This is a UNC path

visbridge.erp.checkreponse.path = \\\\VSOL-DEV2017X/visbridge-temp/erp/import


# Location of the elements really imported to the 3DEXPERIENCE application

# They are named "archive elements"

# This is a UNC path

visbridge.erp.checkreponse.path.pending = \\\\VSOL-DEV2017X/visbridge-temp/erp/import/archive


# Location of the XSL transformation file for the EXPORT process

# This is a UNC path

visbridge.erp.xsl.stylesheet = \\\VSOL-DEV2017X/visbridge-temp/erp/export/xsl/sample.xsl


# Location of the XSL transformation file for the IMPORT process

# This is a UNC path

visbridge.erp.import.xsl.stylesheet = \\\VSOL-DEV2017X/visbridge-temp/erp/import/xsl/sample.xsl


Managing Temporary folders

Workers need a temporary folder to function properly.

It is configured in the configuration file <install_dir>\VISBridge\config\VISWorker.properties

visbridge.config.bridge.state.dir.config=C:\\temp\\visbridge


Trace Management

Bridge application complete logs are set and enabled by default when creating Windows services.

They include:

  • Traces of the Bridge server
    • VISBridgeKServer.err
    • VISBridgeKServer.log
    • VISBridgeZServer.err
    • VISBridgeZServer.log
  • Traces of Workers
    • VISBridgeEventStream.err
    • VISBridgeEventStream.log
    • VISBridgeDataStream.err
    • VISBridgeDataStream.log
    • VISBridgeOutputStream.err
    • VISBridgeOutputStream.log
    • VISBridgeScannerStream.err
    • VISBridgeScannerStream.log

By default they are in the folder <install_dir>\VISBridge\log.


Advanced Traces for Kafka

  • Change file <install_dir>\VISBridge\bin\setenv.bat

set LOG_DIR=%BRIDGE_LOG%\kafka-system-logs


The traces of the Workers  can be enabled/disabled using configuration files <install_dir>\VISBridge\config\VISWorker*Log4j.xml

Example file:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE log4j:configuring SYSTEM "log4j.dtd">

<log4j:configuring xmlns:log4j="http://jakarta.apache.org/log4j/">

    <appender name="file" class="org.apache.log4j.RollingFileAppendix">

        <param name="File" value="c:/temp/logs/worker-event.log"/>

        <param name="MaxBackupIndex" value="10"/>

        <param name="MaxFileSize" value="5MB"/>

        <layout class="org.apache.log4j.PatternLayout">

            <param name="ConversionPattern" value="%d{yyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n"/>

        </layout>

    </appender>

    <appender name="stdout '' class="org.apache.log4j.ConsoleAppendix">

        <param name="Target" value="System.out"/>

        <layout class="org.apache.log4j.PatternLayout">

            <param name="ConversionPattern" value="%d{yyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n"/>

        </layout>

    </appender>

    <root>

        <level value="INFO"/>

        <appender-ref ref="stdout ''/>

        <appender-ref ref="file"/>

    </root>

</log4j:configuring>


Purge logs

Add a scheduled task to stop and restart services:

  • Once a week
  • A every server start


This task serves:

  • Purge logs
  • Start Bridge application


Creating the planned task



  • 2 triggers: