Page Comparison

• If Data Mapper needs to process large file (more than 50 MB), then always use splitting inside Data Mapper activity. You can enable splitting in Advanced Properties of Data Mapper activity and set Splitter/Merger x-path inside Data Mapper Applet. For more details on how to apply splitting in Data Mapper, please refer to Adeptia User manual.
• Always try to implement database caching inside Data Mapper. This can be achieved by making a DBQuery at Root node, storing the results in global variable and then for each record in input, using the global variable value to get the results from database. It would reduce the number of database interactions, probably one for whole Data Mapping and hence optimizing the performance of Data Mapper.
• There may be a need to increase the Operating System configuration for maximum allowed open file handles. Please check the help for your OS to see how to increase this parameter.
• If large number of concurrent process flows are executing in Adeptia Server, then make sure that number of concurrent connections to backend and log database are set to appropriate values. You can configure this in 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)

You need to re-start Adeptia Services after changing these properties

• Running large number of concurrent process flows require more memory to be assigned to Adeptia Kernel. You need to assign sufficient memory to Adeptia Kernel so that it can execute the process flows without any hassle. To configure memory assigned to Adeptia Kernel, you need to change following in etc/launcher.properties file:

#Kernel JVM parameters
KN:JVM: -Xms512M –Xmx1024M -Xrs -XX:PermSize=64M -XX:MaxPermSize=128M

-Xms represents initial memory assigned to Adeptia Kernel at start

...

up 

-Xmx represents the maximum memory that can be assigned to Adeptia Kernel (if available)

You need to re-start Adeptia Services after making this change.

...

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

• To reduce the number of repositories inside Adeptia Server, all the process flows shall be deployed with Repository File Retention as "DELETE ON SUCCESS".

...

• For log clean up, retain time (in days) for different tables can be configured through etc/ log-cleanup.properties file. Default value for retain time (in days) is 14.
  _Toc112820718

  Anchor
  _Toc112820718
  Anchor
  _Toc114635259 _Toc114635259

  Anchor
  _Toc134848200 _Toc134848200

  Anchor
  _Toc144314341 _Toc144314341

  Anchor
  _Toc177977244 _Toc177977244

  Anchor
  _Toc226191143 _Toc226191143

  Anchor
  _Creating_Notification_Activity _Creating_Notification_Activity

  Anchor
  _Creating_Polling_Service _Creating_Polling_Service

  .

  Anchor
  _Toc396748751 _Toc396748751

  Table of Figures
  Figure 1: Process Flow Configuration Page
  Figure 2: Process Flow Advanced Properties
  Figure 3: Edit jetty.xml

  Anchor
  _Toc112820718 _Toc112820718