IBM BPM, V8.0.1, All platforms > Tuning > Advanced tuning > Integration Designer tuning

Processing Java files in Integration Designer

When you need to import a very large number of Java files into Integration Designer, those Java files can cause build performance issues.

There are four major tasks that Integration Designer performs when you import Java files into the workspace for the first time:

1. Importing the Java files into the workspace.
2. Compiling the Java files.
3. JDT indexing to gather basic information from the Java files for validation and search purposes.

4. Integration Designer indexing and validation to identify Java sources that use the business object API for better validation and refactoring.

These four steps can take a large amount of time in your build process if you have hundreds or thousands of Java files in your processes.

Procedure

• To improve performance in this situation, bundle Java classes into Java Archive (JAR) files and reference the JAR files instead of individual Java files. By compiling all the Java source files into a JAR file, you save Java compilation time (which is actually quite significant), and you save time on the Java indexing and validation as well.

• To support source-level debugging, bundle the Java source files together with the Java classes in the same JAR.

• If the Java code is not likely to be changed, or will be changed infrequently, create the JAR file, import the classes, and then use the JAR export wizard.

What to do next

See "Using binary JAR files with Integration Developer and Process Server" in the related links for more information about this subject.

Performance tuning for IBM Integration Designer

Related information:
Integration Designer tuning
Use binary JAR files with Integration Developer and Process Server