Skip to content

RIOMA in day-to-day M3 operations

M3 keeps sending the print job. RIOMA creates the document and the configured output from it. You maintain templates and rules apart from the engine image.

What the engine takes on in the output process

  1. 01

    Infor M3

  2. 02

    XML intake

  3. 03

    Mapping

  4. 04

    Rendering

  5. 05

    Output

  • Print
  • Email
  • Archive
  • SFTP, when configured

The existing M3 output process stays the entry point. Print, email and archive follow the job. SFTP is added when an archive and routing rule names a target.

Bring a known setup back

For operations, the engine, configuration and templates stay apart. A versioned image can be started again with the configuration that belongs to it. There is no automatic rollback, and no duration is promised.

  1. 01

    Engine image

    The versioned runtime of the output engine.

  2. 02

    Configuration

    Rules, routing and operational settings, apart from the image.

  3. 03

    Document templates

    Layouts per document type, also outside the image.

Configuration and templates can be tracked in the customer's own Git repository.

What applies at once, and what needs a restart

Effective on the next job

  • .tex document templates
  • documents.yaml
  • Division rules from rules.yaml
  • Field labels and translations

Process restart required

  • steering.yaml
  • sftp_routing.yaml
  • output.yaml
  • SMTP environment variables
  • Cached Swiss QR rule

Keep areas apart

Different departments can change documents without sharing one configuration. One M3 environment can call several containers for that. Routing stays in the M3 output configuration. How many instances run follows the infrastructure. RIOMA does not add a licence per container.

Infor M3

  • Instance A

    Its own documents and templates.

  • Instance B

    A separate configuration.

  • Instance C

    Another container when you need it.

Operational notes

  • An OK back to M3 confirms document creation. Later delivery can still be in progress or fail.
  • Failed deliveries are not retried automatically.
  • SFTP is off by default and needs an archive job plus a routing rule.
  • Template changes apply on the next job. Not every setting is picked up without a restart.
  • Several containers are configured independently. The infrastructure underneath may be shared.

Where RIOMA fits your M3 output