Miscellaneous

Owned by Saurabh Gupta (Unlicensed)
Last updated: Oct 17, 2017 by Nitin Beri (Unlicensed)Version comment
2 min read

Process Flow

  • If a large number of concurrent process flows are executing in the Adeptia Server, then ensure that number of concurrent connections to the backend and log databases are set to appropriate values. You can configure this in the ...<AdeptiaInstallFolder>/ServerKernel/etc/server-configure.properties file.

    Here are the properties that need to be modified: 

    abpm.jdo.maxActive (for backend database) 
    abpm.logdb.pool.maxActive (for log database) 

    Restart Adeptia Services after changing these properties.

  • Running a large number of concurrent process flows requires more memory to be assigned to Adeptia Kernel. You need to assign sufficient memory to Adeptia Kernel to execute the process flows. To configure memory assigned to Adeptia Kernel, you need to change the following in 
    ...<AdeptiaInstallFolder>/ServerKernel/etc/launcher.properties file.
    #Kernel JVM parameters KN:JVM: -Xms512M –Xmx1024M -Xrs -XX:PermSize=64M -XX:MaxPermSize=128ds

    where,

              -Xms represents initial memory assigned to Adeptia Kernel at startup.

              -Xmx represents the maximum memory assigned to Adeptia Kernel (if available).

  • There may be a need to increase the Operating System (OS) configuration for the maximum allowed open file handles. Please check the help for your OS to see how to increase this parameter.

Data Mapping

  • If the Data Mapper needs to process a large file (more than 50 MB) then always use splitting inside the Data Mapper activity. You can enable splitting in Advanced Properties of the Data Mapper activity and set the Splitter/Merger x-path inside the Data Mapper Applet. For information on how to apply splitting in Data Mapper, click here.
  • Always try to implement database caching inside the Data Mapper. This can be achieved by making a DBQuery at the root node, storing the results in the global variable, and then for each record in the input, use the global variable value to get the results from the database. It would reduce the number of database interactions, probably one for whole Data Mapping and hence optimizing the performance of the Data Mapper.

Data Cleanup

  • Inside the Adeptia Server, data and log clean up should be enabled and properly configured. The retain time (number of days for which data and logs would be retained) shall be properly configured according to the requirement. Please note that data clean up means cleaning of repository files only.
  • For data clean up, the retain time (in days) is configured in the abpm.appmanagement.retainTime property at Administer > Setup > Application Settings > Update System Properties > Maintenance > Data Cleanup Properties.

  • For log clean up, the retain time (in days) for different tables can be configured in the ...<AdeptiaInstallFolder>/ServerKernel/etc/log-cleanup.properties file. The default value for retain time (in days) is 5.

    For information on log cleanup, click here. 

Database

The number of objects and processes within the backend database governs the performance of the user interface. Therefore, when the backend database becomes large, you may need to increase the memory setting to this database:

  1. Administer > Setup > Application Settings > Update System Properties> Embedded Database Settings.
  2. Increase the abpm.embedded.indigo.memory value as well as the Adeptia WebRunner within etc/launcher.properties file:

 #Webrunner JVM parameters WB:JVM: -Xms128M -Xmx512M -Xrs -XX:PermSize=64M -XX:MaxPermSize=128M 

Â