To test Smartfacts in your infrastructure, you can perform an internal PoC installation. These pages describe the procedure to perform such an internal PoC installation.

Restrictions of a PoC deployment

To simplify the installation process, the following restrictions apply to a PoC installation:

• The installation will be performed on a single-node Kubernetes cluster using k3s.

• Smartfacts will not connect to any identity provider. In the PoC you will work with dummy usershat are provisioned in advance.

• Smartfacts will not send emails to users.

All other functionality will be usable as in a later production deployment.

General steps

For installing as Smartfacts PoC instance perform the following steps.

1. Prepare your infrastructure

2. Get access to container and chart registry

3. Install Smartfacts

Prepare your infrastructure

Create the appropriate Hardware

Provide a server with the following specifications:

• CPU:

  • minimum: 6 Cores

  • x64 / AMD64 processor - ARM based servers will not work

• RAM: minimum 32 GB

• Hard disk: SSD, minimum 150 GB

Create the DNS entries for Smartfacts Server and Subdomains

Set up DNS entries for the following FQDNs

• <Server-FQDN>

• smartfacts.<Server-FQDN>

• camp.<Server-FQDN>

• identity.<Server-FQDN>

• oslc.<Server-FQDN>

• genoslc.<Server-FQDN>

Create an X.509 Certificate

For creating the necessary certificates, you can use our portal or create certificates manually.

Create the certificate service request (csr)

Create a csr with our portal

We support you with generating an appropriate certificate under this URL: LINK

1. Add your organization data in section 1

2. Define your deployment scenario in section 2
   You must check the Keycloak and Camp option for every PoC

3. Check the altnames in section 3.
   You may manually change them if you want different urls

4. Generate an OpenSSL Config File or a CSR (“Certificate Signing Request”) in section 3.
   Your IT department will be able to generate a certificate using one of these two files. The Open SSL Config File allows to do manual changes if your IT department requires to do so.

   Alternatively, you can generate a CSR (“Certificate Signing Request”) based on your own OpenSSL config file in the upper right box on the same page.

Manually create csr

If you create the certificate manually, make sure they meet the following requirements.

• Hostnames

  • The certificat must be issued on the hostnames

    • smartfacts.<domain-name>

    • camp.<domain-name>

    • identity.<domain-name>

    • genoslc.<domain-name>

    • oslc.<domain-name>

  • Hostnames must also be stored in the "Subject Alternative Name" (SAN) attribute of the certificate

  • All hostnames and subject alternative names must be written in lower case

Create the certificate

Ask your administration division for support in creating a certificate based on your csr. The Certificat must meet the following requirements:

• It is an X.509 certificate which is suitable for server authentication

• Base64-coded in PEM format

• The certificat must be valid (valid from, valid to)

• It is suitable for the provided private key

• The private key may not be password protected

• The certificate should comprise the complete certificate chain where possible

  If this is missing, then an attempt is made to download the missing intermediate and root certificate during installation.

As soon as you have a certificate, you can check it online under the URL: LINK
The tool will provide feedback if the certificate will work.

There is a way to get even more detailed feedback if you switch to the “Resources” tab under LINK.
Here you can download our CertTool and copy it onto the server on which Smartfacts will be running. The CertTool writes a detailed logfile that provides insights if your server and certificate are setup correctly

Get credentials and license

Please contact cops@mid.de. We will send you credentials for accessing our container & chart registry and a PoC license.

Install Smartfacts

We recommend that your server can directly acces our container and chart repository. In this case follow the instructions for a Deployment on Kubernetes with Internet Connection.

If your server does not have internet acces, follow the instracionts for a Deployment on Kubernetes without Internet Connection.