Planning the directory paths for specific SCUs to provide enhanced or unique functionality per user type, thin client, or group, should be well planned. The design scheme for this type of implementation is similar to implementing the same scenario in a traditional environment (non TS) where SCU paths are using a mapped network drive on a file server. Careful planning is needed to prevent multiple users from performing conflicting actions, such as downloading recipes or modifying database values.
Incorporating iFIX security to limit applications and area access in the Remote Desktop Services environment is highly recommended. For more information on setting security options in iFIX, refer to the Configuring Security Features manual.
IMPORTANT: Be aware that if you configure directory level security in NTFS and the Windows operating system, to something other than the default, use caution when doing so. Any enhancement to security that you make at the folder or directory level is not managed within iFIX. You must manage these security settings outside of iFIX.
For each new project, by default, iFIX creates the following directory structure, unless you specify that the project use one or more shared folders instead:
|
Directory |
Description |
|
ALM |
Stores the Alarm file and event log. Share this directory. This allows events from different sessions to be logged to the same .EVT files for simpler troubleshooting of iFIX under Remote Desktop Services. Do not allow more than one iFIX client to use Alarm File Services while sharing the ALM directory. |
|
APP |
Share or do not share this directory depending on user types and rights. |
|
HTR |
Stores Historical collection preferences. If more than one client will collect historical data, give each user a separate directory. |
|
HTRDATA |
Stores collected historical data. If clients view the same historical data charts, share the directory. |
|
LOCAL |
Stores the user-specific files including Toolbars, User preferences, .INI files, and the .SCU file. If your users are restricted to run mode, they can share the same directories. If your users require special user preferences or configure rights, create unique directories. |
|
PDB |
Stores the Database files. Schedules are also saved in this directory. If schedules are shared by clients, share this directory. |
|
PIC |
Stores pictures (.GRF), dynamo sets (.FDS), Global color tables (.FTB), and other files (.FXG). Generally, share this directory. |
|
RCC |
Stores recipe files. For run-time users, share the directories. Create unique directories for developers or restricted nodes. |
|
RCM |
You can share directories outside the project, instead of creating each of these directories within the same project path. For instance, you may want all projects to share the C:\Program Files (x86)\Proficy\iFIX\PIC path, so that all users share the same pictures, but have different project paths for the other folders. For instance, you may create projects for iFIX operators (C:\Program Files (x86)\Proficy\iFIX\Operators) and supervisors (C:\Program Files (x86)\Proficy\iFIX\Supervisors) that share the PIC path in C:\Program Files (x86)\Proficy\iFIX\PIC, but retain separate folders for all other settings.
