<< Click to Display Table of Contents >> Navigation:  »No topics above this level« Multiple Site Options

The PrimeCut NE License Service can access multiple databases (datastores) while the STP service can only access a single database.  Most companies and corporates have a single server setup with their Production and tutorial databases with cutting machines connecting to the STP service through to the production database.  The Production database can contain data grouped by site allowing for multiple branches of a company to be setup on the one server.

 

There is sometimes a requirement for completely isolated databases to be setup where there is no interaction between users of different sites and no sharing of part, plate, material or costing data etc.

 

The setup configurations and why you may want them are as follows

 

 

One Server with one License Service, one STP service, one Production Database

The simplest setup for small companies through to large multi location corporations.  Allows for large number of users, multiple sites, multiple cutting machines

Plates can be moved between compatible machines, users have access to data on all sites, reporting can be done across all data.

All users share the total network license count, if you have 10 users then all 10 license can simultaneously be used no matter where the users are.

 

Additional databases may be added, in particular Tutorials databases.  

 

Cons

 

If you are using a WAN and do not have good speed low latency network links that connect the PCs to the PrimeCut server then PrimeCut can be slow.  

In multi-site setups if you do not have enough user licenses then users can be blocked from logging in and it may not be a simple task of asking someone by you to log out to let you in.  This is because as someone logs out another user at another site may then login if they are also trying to get in.

 

Multiple Servers, each with their own License Service, STP Service Production database and optional test/tutorials databases

This setup is often used when either there are different legal entities that need to be kept completely separated or there is no network connection (or very slow connection) between sites.

Users and machines only have access to parts, plates etc of the database they are logged into.

 

Cons

 

Requires a PrimeCut registration per server.  If the corporation has 100 user licenses but all 10 for that server are in use then no one else can log into that server until someone connected to the server logs out.

 

One server with a single License service, multiple STP services, multiple production databases and optional test/tutorials databases

This setup allows for separation of branches/companies while allowing sharing of the total PrimeCut NE user license count between them.
Users and machines only have access to parts, plates etc of the database they are logged into.
Requires PrimeCut NE Release 132 or newer.

Cons

If you are using a WAN and do not have good speed low latency network links that connect the PCs to the PrimeCut server then PrimeCut can be slow.  

In multi-site setups if you do not have enough user licenses then users can be blocked from logging in and it may not be a simple task of asking someone by you to log out to let you in.  This is because as someone logs out another user at another site may then login if they are also trying to get in.

You may need a very high spec'd machine if you have many databases and many users.  At the low end, an estimate for 4 databases and 20 users you could probably get away with 16GB ram, 16 CPU cores and two SSDs.

While it is always HIGHLY recommended to not to run other software on the PrimeCut NE Server, in this configuration due to how memory is managed we REQUIRE the server to be dedicated to only running PrimeCut NE and to not be a shared server - it may be a VM if appropriately provisioned and monitored and the VM's memory does not get swapped out while running.