Running the Extractor

Before running the extractor users may have to customize the
curam.dynamicevidence.generated.business.object.tabs.sections
curam.dynamicevidence.generated.business.object.tabs.sections application property. It can be found in the 'Dynamic Evidence - configuration' section of the administration application. This property is used to specify a list of sections to which generated Dynamic Evidence tabs are added. The list must contain a comma separated list of section IDs. This list is used to generate section contribution ('.sec') configuration files (written to the 'tab' folder). The default section list is:

DefaultAppSection,SUPERAPPSection,AUDITORAPPSection,AUDITCOAPPSection,
INVESTRAPPSection,FINAPPSection

The extractor can be run in two ways:

• Running the extractor from the command line:
  • Set SERVER_DIR and CURAMSDEJ variables if not already set. Depending on the project setup, PRE_CLASSPATH variable may have to be set to include any referenced libraries.
  • From the EJBServer folder call
    ./components/DynamicEvidence/script/extractDynamicEvidenceConfiguration.bat file passing all input parameters using the -D option, for example:
    

    ./components/DynamicEvidence/script/extractDynamicEvidenceConfiguration -Dcomponent=MyComponent -DlowerKey=20000 -DupperKey=20999
    -DetExtractionList="etLogicalName1;etLogicalName2;etLogicalName3"

  • Alternatively from the 'EJBServer' folder call
    components/DynamicEvidence/script/extractDynamicEvidenceConfiguration.xml ant script using the -D option to pass input parameters, for example:

    ant -f ./components/DynamicEvidence/script/extractDynamicEvidenceConfiguration.xml -Dcomponent=MyComponent - DlowerKey=20000 -DupperKey=20999 –DextractAll=true

• Running the extractor from the Eclipse development environment:
  • In Eclipse create a new Java Application Run Configuration.
  • Specify the main class to be curam.util.impl.BatchLauncher.
  • Two program arguments must be specified (in the 'Arguments' tab of the run configuration set up): the first argument is the batch operation to be run by the batch launcher, the second argument is the list of all input parameters to the extractor:

    
    curam.dynamicevidence.sl.util.configextractor.intf.
    DynamicEvidenceConfiguration
    Extractor.extractConfigArtefacts

    
    serverDir=D:\CC\DynamicProductWS\DynamicProductMain\EJBServer,component=
    MyComponent,lowerKey=20000,upperKey=20999,etCodePrefix=DET

    The class path will have to be set to include all referenced libraries (depending on the project setup).

    Note the serverDir parameter. It contains the location of the 'EJBServer' folder. The list of input parameters is comma separated and should not contain any spaces.