Skip to content

Preparation#

Critical Manufacturing provides you with the following checklist that serves as a quick guide and helps determine the preliminary procedures and requirements for the installation to take place. This checklist can be printed out and used to check and collect all the necessary information before the installation is initiated.

Containerized installations#

If the installation should be performed under a containerized environment, visit the following sites for more information:

Servers#

This section contains a list of the computer, server and client roles required to run Critical Manufacturing MES. Generically, we recommend that you deploy each of the application tiers on separate machines. For development environments, you can deploy all tiers on a single machine. If a machine is hosting several tiers, it must fulfill all the requirements of the current tier.

Item Description Planning and installation guides Checked
Hardware infrastructure Plan the number of servers and the compute, storage and memory requirements for each one Application Layer - Traditional deployment
Application Layer - Containerized deployment
Database Servers The database servers will host Critical Manufacturing data tier components Planning and installing database servers
Application Servers The application servers will host Critical Manufacturing business tier components Planning and installing the application servers
Application Clients The application clients will run Critical Manufacturing presentation tier components in a browser Planning and preparing application clients

Table: Servers

Storage and Network Shares#

In this section, we summarize what must be prepared in terms of storage resources.

Note

Although you might not use all the product features, we recommend doing a full system preparation. This means that although some storage resources might not be used, they should be created anyway at the minimal storage size, for systems to be uniform. This also applies to drives and drive letters.

Item Description Planning and installation guide Checked
Server Operating System Drives (C:) The normal operating system and applications' installation drive Planning the infrastructure
Database Data Drive (G:) To store the databases' data files Planning and installing database servers
Database Log Drive (L:) To store the databases' log files Planning and installing database servers
Database Backup Drive (H:) To store the databases' backup files Planning and installing database servers
Database tempdb Drive (T:) To store the Microsoft SQL Server tempdb files Planning and installing database servers
Database Deployment Network Share To store temporary backup files during installation File Shares
Document Management Permanent Share To store documents managed by Critical Manufacturing File Shares
Document Management Archive Share To store documents archived by Critical Manufacturing File Shares
Document Management Temporary Share To store temporary copies of the documents managed by Critical Manufacturing File Shares
Electronic Failure Catalog Share For images to be displayed by Critical Manufacturing on the Electronic Failure Catalog File Shares
Application Logs Network Share To store the application diagnostic logs in a central location File Shares

Table: Storage and Network Shares

Accounts, Permissions and Active Directory Objects#

In this section, we summarize what must be prepared in terms of account configurations:

Item Description Planning and installation guide Checked
Deployment Account The account that will be used to deploy Critical Manufacturing Accounts and security
Critical Manufacturing Windows Services Account The account that will be used to run the Critical Manufacturing Windows Service applications Accounts and security
Microsoft SQL Server User Account The account that will be used to connect to the Microsoft SQL Server instance Accounts and security
Microsoft SQL Server Analysis Service User Account The account that will be used to connect to the OLAP cubes created by Critical Manufacturing Accounts and security
Microsoft SQL Server Reporting Services User Account The account that will be used in Reporting Services to host Critical Manufacturing reports Accounts and security
Active Directory Domain Services FQDN The FQDN for the Active Directory domain services server Accounts and security
Active Directory Domain Name The shorter domain name that is used to prefix user accounts Accounts and security

Table: Accounts, Permissions and Active Directory Objects

DNS Entries, Network Ports and Firewall Configurations#

In this section, we summarize what must be prepared in terms of network configurations:

Item Description Planning and installation guide Checked
Critical Manufacturing Host WebApi Port Standard TCP port that application clients use to connect to the application server Network
Critical Manufacturing Message Bus Gateway Port Standard TCP port that application clients and servers use to connect to the Message Bus Gateway Network
Critical Manufacturing Discovery Service HTTP Port Standard TCP port that application clients and servers use to connect to the Discovery Service Network
Critical Manufacturing Discovery Service Host Link Port Standard TCP port that application servers use to connect to the Discovery Service for internal communication Network
Critical Manufacturing Discovery Service Gateway Link Port Standard TCP port that Message Gateway applications use to connect to the Discovery Service for internal communication Network
Critical Manufacturing Legacy User Interface IIS Binding Port Standard TCP port that application clients use to fetch application files Network
Critical Manufacturing User Interface IIS Binding Port Standard TCP port that application clients use to fetch application files Network
Critical Manufacturing Documentation IIS Binding Port Standard TCP port that application clients use to fetch documentation files Network

Table: DNS Entries, Network Ports and Firewall Configurations

SAP Connection Setup#

This section outlines the configuration required to support SAP integration when using the Theobald ERP Connector. If the integration is implemented via web services or other protocols, this setup is not required.

Item Description Planning and installation guide Checked
SAP Host Critical Manufacturing will connect to this SAP instance to receive inbound messages and to send outbound messages SAP Integration ⧉
SAP System Number The SAP system name to connect to SAP Integration ⧉
SAP Service The SAP RFC gateway hostname SAP Integration ⧉
SAP Program Id The name of the Remote Server Program that will be used for IDOC exchange SAP Integration ⧉
SAP User Name The user name used to authenticate in SAP SAP Integration ⧉
SAP Password The password used to authenticate in SAP SAP Integration ⧉
SAP Client The SAP Client number SAP Integration ⧉
ERP ConnectorLicense Key The Theobald ERP Connect license required to communicate with SAP SAP Integration ⧉

Table: SAP Connection Setup

Other infrastructure requirements#

In this section, we summarize the configurations for the email infrastructure required for notifications:

Item Description Planning and installation guide Checked
SMTP Server Address Critical Manufacturing requires an email server to send notifications through email (SSL is both supported and recommended) Email
SMTP Server User Name The account used to authenticate at the email server Email
SMTP Server Password The password used to authenticate at the email server Email
Support Email Address Critical Manufacturing will send email messages to this destination Email
Support Email From Name Critical Manufacturing will send email messages using this text to identify the email sender Email

Table: Other infrastructure requirements