Note: The following doesn't apply for you if you are using Cloud.
Your server platform should meet the following minimum resource requirements:
- 16 GB RAM
- Quad core CPU
- 10 GB free disk space.
It doesn't matter if you are running Asset Center on bare metal or in a virtualized environment. Even a private cloud (AWS, Azure etc.) is ok.
OTbase Inventory comes as a Docker image and therefore requires the Docker container platform. If you are not familiar with Docker yet, information on this software can be found at www.docker.com. Cloud services usually provide pre-installed Docker servers.
You can install Docker (and ) on Windows 10 or higher, but a Linux installation is a bit easier and therefore recommended.
The following factors will help you to determine your decision on where to host OTbase Inventory:
- If this is a proof-of-concept, you may place the OTbase Inventory inside a process network, assuming that no external access is desired.
- If you want IT users to be able to access the OTbase Inventory, a good hosting candidate is a computer inside the DMZ that separates process networks from office networks.
- If you want to collect configuration data from multiple sites in a central OTbase Inventory, a hosting candidate would reside in the enterprise network that can be reached by all participating sites.
Summing up, placement of the OTbase Inventory is largely determined by required access paths -- both for users and for configuration data provided by OTbase Discovery nodes. For the latter, you only need to assure that OTbase Discovery nodes can uni-directionally send files to the OTbase Inventory. Such a connection may involve multiple steps with store-and-forward functionality in between. A direct online connection between OTbase Discovery engines and the OTbase Inventory is not required, and the transmission of configuration files is not time critical.