Importer Manual / Version 2301
Table Of Contents
In the CoreMedia Blueprint workspace in global/examples you
will find a coremedia-application module importer-template with
two submodules importer and importer-config.
Building and Deploying the Importer
Before you can start the importer, you have to configure and build your own importer application as follows:
Take the
importer-templateexample module and integrate it into your workspace. If you want, you can mergeimporterandimporter-configinto a singlecoremedia-applicationmodule (like the theme-importer-application does). The separation of the template modules is only related to the web application deployment as shown in Section 3.4, “Deployment and Operation of a Web Application Importer”.Replace the
cmprefix ofcm-xmlimport.jpifandcm-xmlimport.propertieswith your own one, for example,my-xmlimport.jpif. The configuration file must be located in the directoryproperties/corem.Example: The configuration file
properties/corem/my-xmlimport.propertiesbelongs to the filebin/my-xmlimport.jpif.Configure the importer in the
my-xmlimport.propertiesfile as described in Section 3.1, “General Configuration”.Build your importer with
mvn install.
Starting the Importer
When you have build the importer, you can start it with the following command,
where <ImporterName> corresponds to the name of the importer JPIF file,
my-xmlimporter, for example:
bin/cm <ImporterName>
The importer will check the inbox once and then terminates. To constantly check the inbox the importer can be deployed as web application instead. See Section 3.4, “Deployment and Operation of a Web Application Importer”.
