Nexeed
    • Introduction
    • User manual
      • Concept
        • iFNS MatLabelCheck
        • INTEGMA
          • eASN (Electronic Advanced Shipping Notice)
          • GRTO (Goods Receipt Transfer Order)
          • Pairing
          • Repacking
        • On setup label creation
      • Basic operation
        • Basic interaction elements
        • Filter tables via filter dialog
        • Search for materials
        • Export results table
        • Adjust table columns
        • Configuring a scanner
      • Material info
        • Material details tab
        • Blocks tab
        • MSD Info tab
        • Monitoring tab
        • Material history tab
        • Setup history tab
      • Material search
        • Label by ID tab
        • Material by ID tab
        • Extended search tab
      • MSD handling
        • Dry Box content tab
      • Inbound events
        • Details of an event
      • Material monitoring
        • Start a monitoring process
        • Add materials for monitoring window
        • Monitoring details page
        • State and state changes
          • Single Stage Thawing
          • Dual Stage Thawing
          • Solder paste monitoring
        • Roles and resources for material monitoring
      • Configuration
        • Blocking Rules tab
        • On setup label creation rules tab
        • Displaying and editing the configuration file
        • Monitoring location definitions tab
        • Monitoring process definitions tab
        • Printer settings tab
        • Printer templates tab
      • Desktop clients
        • Material InfoPanel desktop client
        • Mat climate control desktop client
    • Operations manual
      • Introduction
        • Nexeed Material Management
        • Application security
        • API documentation
        • Nexeed IAS Ops team
      • Overview
      • System architecture and interfaces
      • System requirements
        • mat/materialmanagement-backendservice
      • Migration from previous versions
        • Migrate Material Management from version 2.11 to 3.0
        • Migrate Material Management from version 3.0 to 3.1.x
        • Migrate Material Management from version 3.1.x to 3.2.x
        • Migrate Material Management from version 3.2.x to 3.3.x
        • Migrate Material Management from version 3.3.x to 3.4.x
        • Migrate Material Management from version 3.4.x to 3.5.x
        • Migrate Material Management from version 3.5.x to 3.6.x
        • Migrate Material Management from version 3.6.x to 3.7.x
        • Migrate Material Management from version 3.7.x to 3.8.x
        • Migrate Material Management from version 3.8.x to 3.9.x
        • Migrate Material Management from version 3.9.x to 3.10.x
        • Migrate Material Management from version 3.10.x to 3.11.x
        • Resources mapping from MES to IAS
      • Setup and configuration
        • Helm Configuration
          • materialmanagement-backendservice
          • materialmanagement-shared
        • Installation guide
        • Operation in hybrid mode - overview
        • Installing MatClimateControl with MES Installer
        • General information about configuration
        • Installing MaterialInfoPanel with MES Installer
        • General information about configuration
      • Start and shutdown
      • Regular operations
        • MSD Buffer timespan handling
        • Tenant data removal
        • Runtime configuration handling
        • Background jobs
      • Failure handling
        • Authorization troubleshooting
        • Database-migration troubleshooting
      • Backup and Restore
      • Logging and monitoring Material Management
      • Known limitations
        • Multitenancy capability
        • On premise
        • Database support
    • API documentation
      • HTTP API
      • Restricted HTTP API
    • Glossary
Material Management
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • AGV Control Center
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Direct Data Link
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Material Management
  • Operations manual
  • Setup and configuration
  • Installation guide

Installation guide

During the deployment, based on the below described helmchart version the following Material Management components are started as docker container(s):

  • Overview

How to set up the database

The following steps describe how to install or update the Material Management database.

The MES packages for the database have not been renamed from MatControl_<version>_Database to MaterialManagement_<version>_Database, in order to allow them to be recognized by the MES Installer in case of an update scenario.

If you need to install or update a MatControl-Workflow database refer to How to setup the Workflow database chapter.

From the version 3.3.x onwards the database is setup and updated automatically via a kubernetes job.

To install the Workflow database for the Hybrid mode the MES installer has to be used.

Prepare for the database installation or update

The target server has to have the Compression and Partition variables set on their helm charts. Possible values are "TRUE" and "FALSE". The values have to be strings, and also it is mandatory to make them capital.

These variables are:

  • mainDbCompressionEnabled (default: "FALSE")

  • mainDbPartitioningEnabled (default: "FALSE")

config server database

Deploy the new version of the service

In order to initiate the update, the new version of the service will have to be deployed. Whenever a new deployment happens a Kubernetes job will be created with the target version of the database, and will initiate the database update.

If there was a job already deployed with the same name, and there is a necessity to start the job again(or with a bugfix release), the job has to be deleted manually, and then redeployed.

Whenever the job is executing the pod can be checked to see the logs. After the job ran through the status will be marked as completed:

database install kubernetes job completed

Check the logs of the job

The job will create a new versioning table, which is initially grabbing information from the MES_VERSION table in case it exists. The new table is called DATABASE_VERSION.

In this table, we can see the version history, the status of the updates, the timestamp, and also the whole log of the install/update. In case there was an unsuccessful update, make sure to check the Log column of this table, copy the content out and verify what failed.

database install dbversion table

How to setup the workflow database

Prepare the MES Installer

The latest mespkg file has to be downloaded. Then it has to be placed in the Executables folder of the MES installer. A few examples, how it generally looks like:

  • "MatControl_3.2.23058.01_Database.mespkg"

  • "MatControl_3.2.22265.02_Service.mespkg[]"

mes installer executables

Then start the installer, and choose install:

mes installer install

Choose the Material Management Database:

mes installer matcontrol db

Then simply click next & install.

After the installation is complete, go back to the home page of the installer, and click 'Publish Databases':

mes installer publish db

Now, create a new database instance if the instance you want to install on was not already created in your MES Installer installation. Click 'Add Instance', then select 'Oracle' as Server Type, and provide a name. Fill in the connection details for the database you want to install on. If you want to perform a full install including the tablespaces and schema user, you need to provide the password for the sys user in the corresponding input field.

mes installer addinstance
mes installer addinstance naming

After adding the new instance, the next step is to create a new schema with the '+' - 'Add Database' button on the instance:

mes installer add database button

Select the desired one (installing the workflow version is not required), then 'Add':

mes installer add database after selection

Fill the credentials, then click next:

mes installer add database creds

Make sure the connection’s state is 'Connected', click next.

On the next 'Configuration' page unselect the unnecessary scripts (if applicable) and provide the neccessary settings depending on the type of installation you are performing.

Full install

A full install on the database is only performed if the MES Installer does not detect a previous version of the database on the selected schema. Otherwise the MES Installer will try to perform an update of the existing database version. In order to full install the Material Management Workflow database, you need to provide the password for the sys user in the selected instance. A Full Install will create the Tablespaces, Schema User and all the Schema Objects.

For a full install you have to provide:

  1. The data tablespace name

  2. The index tablespace name

  3. The path where the data tablespace should be created on the filesystem

  4. The path where the index tablespace should be created on the filesystem

  5. The tablespace configuration values for both DATA and IDX tablespaces

mes installer full install settings
mes installer full install settings tablespace

Full install - existing tablespaces and schema user

If your database already has existing tablespaces and schema user you want to re-use, but no schema objects, you can perform a full install of the schema objects without creating new tablespaces and schema user.

To do this please de-select the Create_tbspace_user_as_sys script as shown in the image below.

In this case you only have to provide:

  1. The data tablespace name

  2. The index tablespace name

It is possible to use the same tablespace name for both data and index if you want to use only one tablespace for both data and indexes.
mes installer full install  without ts user settings

Update an existing database

If the database you selected already has a previous version of the database installed, the MES Installer will perform an update.

In this case you only have to provide:

  1. The data tablespace name

  2. The index tablespace name

Before version 3.2[] of the MatControl-Workflow database, the tablespace names were predefined with the following values.

MatControl database:

  • <SchemaName>DATA_MATCTRL

  • <SchemaName>INDX_MATCTRL

So for example if you had a schema called “123” then the tablespaces would have been: “123DATA_MATCTRL” and “123INDX_MATCTRL”.

MatControl-Workflow database:

  • <SchemaName>_DATA

  • <SchemaName>_INDX

Please make sure to check the tablespace names which are used in this database and provide the correct names.

mes installer update settings

Finishing the installation / update

On the final page, click "Install All" and wait for it to complete:

mes installer add database finish

A successful installation will have all items marked with a green flag on the right side of the screen, or a red mark that means there was an error.

How to update to a newer version of the database

For updating a database, some steps have to be done again:

  • copy the new mespkg in the Executables folder

  • install the new mespkg

  • publish database → the old instance can be reused if needed

  • configure-update it again as necessary (the installer should automatically pick the right items to update based on the current and new versions)

  • update

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2025, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses