Setting Up the Batch Processor Executable Component

The batch processor must be configured before a user can rename designs in batch mode.

This executable component is installed in the directory:

<USER_INSTALLATION_DIR>\server\Apps\DesignerCentral\V6Rxxxx\Modules\
ENODesignerCentral\AppExternal\DSCBatchProcessor

The DSCBatchProcessor directory can be copied to any other system. It contains the DSCBatchProcessorStart.bat script that launches the batch processor component (on UNIX, the script DSCBatchProcessorStart.sh should be run).

The batch processor executable creates report files in the Reports directory and log files in the logs directory during operation.


Before you begin:
  • The integrations for CAD tools must be installed.
  • Shadow Agent group must be assigned to the User.
  • Edit the DSCBatchProcessorStart (.bat or .sh) to specify the installation path of Java on your machine. Edit the line, set JAVA_HOME=<Java Installation directory>. For example, set JAVA_HOME=C:\C:\jdk1.6.0_14.
  1. Open the DSCBatchProcessorConfig.xml for editing. The following is a sample Batch Processor Configuration file:

    <?xml version="1.0" encoding="UTF-8"?>
    
    <batchprocessor>
    
        <loginname>Test Everything</loginname>
    
        <password></password>
    
        <appleturl>http://localhost:8088/enovia/integrations/
    silentief.jsp</appleturl>
    
        <debugflag>true</debugflag>
    
        <multiplereports>true</multiplereports>
    
        <designercenteralversion>R213</designercenteralversion>
    
        <executeoperations>
    
           <operation>BatchRename</operation>
    
        </executeoperations>
    
        <operationlist>
    
           <operation name="BatchRename">
    
              <queuename>RenameQueue</queuename>
    
              <executioninterval>3000</executioninterval>
    
              <appletport>4000</appletport>
    
              <checkoutdirectory>D:\enovia\studio\Apps\Integrations\DesignerCentral_
    V6R2013\DSCBatchProcessor\checkoutdir</checkoutdirectory>
    
              <implementationclass>com.matrixone.MCADIntegration.applications.batchp
    rocessor.DSCBatchProcessorBatchRename</implementationclass>
    
              <integrationslist>
    
                           <integration name="MxCATIAV5" version="R209">
    
                            <implementationclass>com.matrixone.MCADIntegration.applications.batchp
    rocessor.DSCBatchProcessorCATIAV5Instance</implementationclass>
    
                            <configfile>D:\enovia\studio\Apps\Integrations\DesignerCentral_V6R2011
    \DSCBatchProcessor\config\DSCBatchProcessorCATIAV5Config.xml</
    configfile>
    
                           </integration>
    
              </integrationslist>
    
           </operation>
    
           <operation name="BackgroundDerivedOutput">
    
              <queuename>DerivedOutputQueue</queuename>
    
              <executioninterval>30</executioninterval>
    
              <appletport>7770</appletport>
    
              <checkoutdirectory>D:\enovia\studio\Apps\Integrations\DesignerCentral_
    V6R2013\DSCBatchProcessor\checkoutdir</checkoutdirectory>
    
              <implementationclass>com.matrixone.MCADIntegration.applications.batchp
    rocessor.DSCBatchProcessorDerivedOutput</implementationclass>
    
              <integrationslist>
    
                           <integration name="MxPRO" version="V6R2012">
    
                            <implementationclass>com.matrixone.MCADIntegration.applications.batchp
    rocessor.DSCBatchProcessorDerivedOutputProE</implementationclass>
    
                            <configfile>D:\enovia\studio\Apps\Integrations\DesignerCentral_V6R2011
    \DSCBatchProcessor\config\DSCBatchDerivedOutputProEConfig.xml</
    configfile>
    
                           </integration>
    
              </integrationslist>
    
           </operation>
    
        </operationlist>
    
    </batchprocessor>
    

  2. Update these Global Properties required for all batch operations:

    <loginname>--passed with the silent login command to the applet to create context object on server side.

    <password>--passed with the silent login command to the applet to create context object on server side.

    The login name and password must match the values specified in the DSC_GetBatchProcessorDetailsBaseJPO for the particular queue.

    <appleturl>--used by the Batch Processor to load the integration applet by calling the specified URL through the browser.

    <debugflag>--true or false, to enable or disable debug logging.

    <multiplereports>--If each message that is processed should have one report or the results for all messages should go into a single report.

    <executeoperations>--specify the batch operations permitted to run simultaneously. If not entered here, other operators will not be run. Only BatchRename and BatchDerivedOutput operations are currently supported.

  3. Update operation-specific properties:

    <queuename>--used to locate messages from the specified queue object

    <executioninterval>--when there is no Message object in the queue, this property indicates the interval before checking the specified Queue object.

    <appletport>--BatchProcessor passes this port number as a parameter on the URL to the applet. Applet will open server socket using passed port number.

    <checkoutdirectory>--If batch operation business logic requires files to be checkout to the local disk, this property specifies to which directory designs files should be checked-out. Create a directory exclusive for batch processor operations because the processor deletes all the contents of the directory while processing messages.

    <implementationclass>--the full name of the batch operation-specific implementation class. List all collaborative products installed for which you want to enable batch processing.

  4. Update collaborative product (CAD plug-in) specific properties:

    <implementationclass>--The complete name of implementation class specific to collaborative product instance.

    <configfile>--The name of the configuration file specific to the collaborative product. The collaborative product (CAD Plug-ins) define the format of this file.

  5. Enable the batch rename processor by setting the GCO flag for the collaborative product IEF-EnableBatchProcessorForRename to true. See Entering GCO Attribute Values.