About SigmafineHub Installation
The installation of SigmafineHub will create:
File system directories under
C:\ProgramData\Pimsoft(default)- Display - Used to store imported displays.
- Runs - Used to store SF Analysis temporary files.
- Attachment - Used to store Messaging files.
- Distribution - Used to store SigmafineHub distribution files.
- Packages\Build - used to store the packages built by SFHub Studio.
- Packages\Upload - used to store the packages uploaded in SFHub Studio.
- Packages\Register - used to store the package registration information.
One IIS application pool
- SFHubAppPool
One Web site with multiple applications and the web service
SFHub website will be created with the following applications:
WebApp Url SFHub Admin `https://{webserver}/sfhub/admin`` SFHub Login `https://{webserver}/sfhub/login`` SFHub Visualizer `https://{webserver}/sfhub/visualizer`` SFHub Visualizer `https://{webserver}/sfhub/studio`` The following web service:
- SFWebApi
The SFHub Application Pool and the Web Service run under a dedicated SFHub Service Account (domain account). This is the account that SFHub uses to discover the SF Servers (PI AF servers), for the client to see SF Servers, the SFHub Service Account needs appropriate access to these servers.
The next section provides more information about their configuration.
SigmafineHub Access Control
Access to the SFHub Applications is controlled through the SFHub Admin application from where you will be able to enable user domain accounts as well as configure their rights.
Access to the SF Servers (PI AF) are controlled through the PI AF security, therefore you will have to configure PI AF security on each SF Server (PI AF) for each user (domain account) you will enable. Moreover, as mentioned before, you'll have to grant read access to all SF Servers (PI AF) to the SFHub Application Service account.
The Hardware & Software requirements topics provide The next section provides more information about these configurations.