Setting up Directories
The PPS requires some directories for the machines to be able to load patterns or for ex. save loggings at a central location. The PPS itself requires directories, e.g. for obtaining order files or delivering results about the orders development. Some of the directories require a network share, for others establishing an appropriate security setting is sufficient. The PPS installation generates most of the directories and also adapts the permissions. In case that the FTP server delivered with the PPS is to be used, the configuration in the PPS must be adapted.
Transfer directories
If you want to transfer the folders to another path than pre-allocated by the installation, then the paths in the PPS must be changed accordingly, and the releases adapted by the administrator.
If you have allowed the installation to create a local JBoss User, but then, after the installation, you have made up your mind to transfer some or all paths to a file server in the network, you should create the JBoss user either locally on this file server or in the domain. Set up a network share for this file server. Enter the released network path in the PPS.
You can cancel and re-install the main program PPS with the installation program as an option. When re-installing, enter an existing domain user or a local user of your choice. The release must be installed on the file server for this user, if this is not the case yet.
Release for machine users
In order to enable the machines to access networking shares, the permission must be installed for the machine user.
If a local user is used on the machines, it must be created on the file server locally or in the domain. A network share can then be created for this user.
If you want to transfer the folders to another path than pre-allocated by the installation, then the paths in the PPS must be changed accordingly, and the releases adapted by the administrator.
If you have allowed the installation to create a local JBoss User, some or all paths will decide after the installation to transfer to a file server in the network. You should then create the JBoss User either locally on this file server or in the domain, and install a network share for it. Enter the released network path in the PPS.
The drive letter D: which is specified in the table may be different in your case depending on what you have selected when installing the PPS program files.
|
Directory Path |
Meaning |
Required by |
Permission |
To be setup by |
|---|---|---|---|---|
|
D:\PPS\ERP\Input |
Storage of the XML order files that are to be planned. |
JBoss User User who saves the XML file there |
RW RW |
Installer Administrator |
|
D:\PPS\ERP\Output |
Storage of the XML result files that return from the machine |
JBoss User User who retrieves or deletes an XML file there |
RW RW |
Installer Administrator |
|
Directories that are to be made available via network share or FTP server of the PPS. | ||||
|
D:\PPS\FtpRoot\Pattern |
Root directory where the knitting programs are saved. The access of the machines occurs via the FTP server of the PPS or a network share. |
JBoss User The machine user who must get or save patterns there, when FTP is not used If FTP is used, no release will be required for the machines |
RW RW |
Installer Administrator |
|
D:\PPS\FtpRoot\McFiles |
Root directory where the machines save or retrieve specific files |
JBoss User Machine user who is to retrieve or backup patterns there, if sharing via network is used. If FTP is used, no release will be required for the machines |
RW RW |
Installer Administrator |
|
Directories beneath McFiles when working with the network share. Normally, there is no need for action, since the permissions is inherited from the McFiles folder. | ||||
|
McLoggings |
Here, the machines save crash loggings or copies of manually saved logs for ex. on a USB stick |
JBoss User Machine user |
Share RW Share RW |
Installer Administrator |
|
McConfigData |
Here, the machines save their current state in regular time intervals, which can be setup in the PPS. The setting allows a machine to return quickly to an operational state after an IPC exchange |
JBoss User Machine user |
Share RW Share RW |
Installer Administrator |
|
McTemplates |
Here the additional files for the ticket views, as for ex. images, XSL and other file types which are to be synchronized automatically with the machines will be saved. |
JBoss User |
RW |
Installer |
|
McSymbolBarConfigs |
Here, the machines backup or retrieve the configuration of the toolbar. For this purpose, the path must be used for ex. in a service ticket. |
Machine user |
Share RW |
Administrator |
|
McUserProfiles |
Here, the machines backup or retrieve the user profiles. For this purpose, the path must be used for ex. in a service ticket. |
Machine user |
Share RW |
Administrator |
|
McLicenceKeys |
This directory is where the machines save the public key for the pattern encryption. For this purpose, the path must be used for ex. in a service ticket. |
Machine user |
Share RW |
Administrator |
|
Further directories | ||||
|
D:\PPS\ReportTemplates |
Directory which the Birt Report Templates are saved to, and loaded by the PPS |
JBoss User
|
RW |
Installer |
|
D:\PPS\ServerSharedFilesAndFolders |
Directory with links to log files of the PPS system, and further files like Screenshots which are to be used for the Feedback function. |
JBoss User
|
R |
Installer |
|
D:\PPS\Images |
Directory with further subdirectories where are saved floor plans and employee photos. |
JBoss User
|
RW |
Installer |
|
D:\PPS\SampleTickets\PpsTicketTemplate |
Directory, which the template files of the orders are saved to, that can be exchanged in the PPS or loaded afterwards |
JBoss User
|
RW |
Installer |
|
C:\Program Files (x86)\Apache Group\Apache2\htdocs\PpsDocs\CustomerWeb |
Directory, which files (HTML, pictures, further documents) can be saved to, that can be referenced per URL in the order XML or XSL. |
JBoss User Machine user |
The use of the http service on port 80 may not be locked. |
Installer |