How to Configure the Import Processor Type Window in iDempiere
The Import Processor Type window in iDempiere defines the Java class a retail deployment uses to receive replicated data, such as a JMS Topic listener.
Correct configuration keeps store and HQ transactions synchronized, which directly affects the accuracy of consolidated sales reporting and stock visibility.
Process Flow
Business Rules
- Only Active Import Processor Type records are available for Import Processor configuration.
- Search Key must be unique per Tenant to avoid conflicting processor definitions.
- Java Class must reference a valid, deployed implementation of the import interface.
- Description and Comment/Help guide administrators setting up store-to-HQ replication.
- Durable subscription parameters are only required when the Java Class supports JMS Topics.
Prerequisites
- JMS broker (e.g., ActiveMQ) configured and reachable from the iDempiere server.
- System Administrator role access to the System Admin menu.
- Target Java Class deployed in the iDempiere server classpath.
- Replication Processor and Import Processor windows available for follow-up setup.
Navigation
Menu → Data → Replication Data → Import Processor Type
Configuration Steps
Step 1: Define Identification Fields
Enter a short, unique Search Key and a descriptive Name that identifies the replication method, for example JMS Topic Import Processor Type.
| Field | Sample Value | Description |
| Search Key | JMS Topic Import Processor Type | Unique identifier used in lookups |
| Name | Human Readable name for – JMS Topic Import Processor Type | Display name shown in selection lists |
Step 2: Add Description and Comment/Help
Summarize the purpose in Description, and add setup notes or usage context in Comment/Help for future reference.
| Field | Sample Value | Description |
| Description | Adempiere JMS Topic Import Processor Type | Short summary of the processor’s function |
| Comment/Help | JMS Topic Import Processor Type | Extended notes for administrators |
Step 3: Set Active Status
Tick the Active checkbox once the record is ready for use in store or HQ replication setups.
| Field | Sample Value | Description |
| Active | Checked | Makes the processor type selectable |
Step 4: Assign the Java Class Implementation
Enter the fully qualified Java Class name matching the deployed listener implementation on the server.
| Field | Sample Value | Description |
| Java Class | org.adempiere.server.rpl.imp.TopicImportProcessor | Class that starts the JMS Topic listener |
Note: Import Processor Type only registers the Java Class. Broker host, port, topic name, and durable subscription settings are entered on the related Import Processor window.
Common Issues and Resolutions
| Issue | Cause | Resolution |
| Processor type not listed in Import Processor window | Active checkbox is unticked | Activate the Import Processor Type record |
| Duplicate Search Key error on save | Search Key already exists for the Tenant | Use a unique Search Key value |
| Import Processor fails to start the listener | Import Processor not linked to a valid Type | Confirm the Import Processor references this record |
| Store receives unrelated replication messages | topicName differs between export and import sides | Match topicName exactly across export and import configs |
Next Steps
- Configure the Import Processor window using this Import Processor Type.
- Set up the Replication Processor to trigger scheduled imports.
- Define the Replication Strategy and Tables for the tenant.
- Review Trx Organization settings for store-to-HQ data targets.