close

Filter

Importer Manual / Version 2204

Table Of Contents

3.3 Deployment and Operation of a Standalone Importer

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:

  1. Take the importer-template example module and integrate it into your workspace. If you want, you can merge importer and importer-config into a single coremedia-application module (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”.

  2. Replace the cm prefix of cm-xmlimport.jpif and cm-xmlimport.properties with your own one, for example, my-xmlimport.jpif. The configuration file must be located in the directory properties/corem.

    Example: The configuration file properties/corem/my-xmlimport.properties belongs to the file bin/my-xmlimport.jpif.

  3. Configure the importer in the my-xmlimport.properties file as described in Section 3.1, “General Configuration”.

  4. 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”.

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.