PAC System Requirements
PAC System Requirements
PAC System Requirements
Notes
When using the following features, you can lower your User Account Control settings and/or set up
PAC Machine Edition Engineering to always "Run As Administrator":
Notes
a. When using multiple instances, each instance will consume the resources required
for a single instance. Running too many instances may cause your system to
become unstable. You can run more instances with small projects than with medium
or large projects. In general, more than 5 instances of small projects, 3 instances of
medium projects or 2 instances of a large project will likely impact performance on
most systems.
b. A large project is one that exceeds 125,000 variables, 128 blocks, 10 targets, or
combinations of each that would exceed these values.
Miscellaneous Requirements
• Internet Explorer Version: 11.0 or newer with current updates.
Note: Install Internet Explorer before installing Machine Edition.
• TCP/IP Network protocol-based computer (if you use an Ethernet connection).
• .NET Framework 4.6 Full. If the Microsoft .NET Framework is not yet installed, it is
automatically included during the installation of Machine Edition and may require a reboot to
complete the installation. This installation requires a minimum of Windows 7 SP1.
• 2 GB of hard disk space. Additional space is required for your projects and temporary files.
• The Development Environment is supported on VMware Player or VMware Workstation
Operating System
Machine Edition Product Windows 7SP1 Windows 8 and 8.1 Windows 10
QP+ View Developer √ - √
QP+ Logic Developer – PC √ - √
The following table describes the minimum requirements needed for the range of variables
defined in your projects.
Requirements Variables
< 500 500 - 10000 > 10000
CPU 233 MHz 1 GHz 2 GHz
Disk Space 200 MB 200 MB 200 MB
RAM 128 MB 512 MB 1 GB
System Components
PAC Productivity Suite is made up of several products, more details are available within the
documentation of those products.
Engineering Workstation √
Operator Console √ √
Application Server √ √
System Server √ √
Regional Settings
PPS Product Regional English OS German/French Simplified Russian OS
Setting OS (Single-Byte) Chinese OS (Cyrillic)
(Double-Byte)
Engineering Workstation U.S. √ √ √ √
LOCAL
Notes
For the PCM Thin Client, including the Scheduler and Scheduler Editor used with the Thin Client:
Miscellaneous Requirements
• Internet Explorer Version: 11.0, 10.0, 9.0, 8.0, or 7.0, with current updates.
Note: Install Internet Explorer before installing Change Management.
• Ethernet Network Adapter and the TCP/IP Network Protocol (100 Mbit).
• .NET Framework 4.6 Full for the PCM Server, Thick Client, and Scheduler Engine. If the
Microsoft .NET Framework is not yet installed, it is automatically included during the
installation of Change Management and may require a reboot to complete the installation.
• .NET Framework 2.0 for the PCM Thin Client.
• PCM Thick Client for the PCM Scheduler Engine.
• Free hard disk space:
o 20 GB, plus storage space for project files, for the PCM Server.
o 50 MB, plus storage space for project files, for the PCM Thick or Thin Client (500 MB
recommended to start with).
o 50 MB (in addition to hard disk space required for the PCM Thick Client) for the PCM
Scheduler Engine.
• One of the following version control systems (VCS) for the PCM Server:
▪ Apache Subversion version 1.8.3 (or greater). For more details, visit Apache’s web site
at http://subversion.apache.org/packages.html and download any binary installer
package for Windows 32-bit that is based on version 1.8.3 (or greater).
Notes
▪ You can choose to download and compile the source files rather than downloading the
binary installer files. For more details, visit Apache's web site
at http://subversion.apache.org/download/.
▪ Subversion with PAC Change Management is supported only on Windows operating
systems.
▪ Only 32-bit Subversion is supported or compatible in PAC Change Management.
▪ Microsoft Visual SourceSafe 6.0d Build 31222 or later (Server installation), or Visual
SourceSafe 2005.
Notes
▪ The 6.0d version can be acquired by installing the Microsoft Visual Studio 6 SP6 update.
For more details, visit Microsoft's web site at www.microsoft.com.
▪ If Visual SourceSafe 6.0 is installed and you want to upgrade to Visual SourceSafe 2005,
you must first uninstall PAC Machine Edition, restart your computer to avoid potential
operating system corruption, and then uninstall Visual SourceSafe 6.0. You can then
install Visual SourceSafe 2005, and then reinstall Machine Edition. Uninstalling only Visual
SourceSafe 6.0 does not remove it from the computer because Machine Edition retains a
copy.
Subversion Repository
• The migration of PAC Change Management Visual SourceSafe (VSS) repository data to
Subversion is NOT supported. If you want to migrate your data and retain the revision/history
information, please contact Emerson.
• Microsoft retired Visual SourceSafe from mainstream support on July 10, 2012 with extended
support ending on July 11, 2017. If you are currently using VSS, you can continue to do so,
and can use this DVD to install the latest SIMs for PAC Change Management. Support of
Subversion (SVN) as a repository is new to this version of PAC Change Management. Below is
a set of steps detailing a sample install and setup of SVN as the PAC Change Management
repository.
2. Install the PAC Change Management Server with SVN as your repository. For more
information, see "To install the PAC Change Management Server" in the Getting Started
Guide.
3. Create a new SVN repository by opening a Windows command prompt, and then
running svnadmin create [chosen path]; where [chosen path] is the location of the
SVN repository. We recommend: C:\Program Files (x86)\Emerson\PAC Machine
Edition\fxManager\Server\SVN.
NOTE: When you try to use an MS-DOS command that contains a path statement, you may receive an
error message if you use a path statement that contains spaces. To resolve this issue, place quotation
marks around each path parameter that contains a space. For example, svnadmin create
"c:\Program Files (x86)\TestDirectory".
4. Perform the following steps to configure the newly created SVN repository. For example,
please see the Example_Config_SVN.zip file.
a. Configure the authz file to add a user account with the following
entry: fxMgrServer = rw. This file is located in the C:\Program Files
(x86)\Emerson\PAC Machine Edition\fxManager\Server\SVN\conf folder.
NOTE: Make sure that the conf folder has read/write privileges. Also, be sure to include the
[/] syntax to designate a new section.
b. Configure the passwd file to add a password for the account you just created with
the entry, fxMgrServer = fxMgr. This file is located in the C:\Program Files
(x86)\Emerson\PAC Machine Edition\fxManager\Server\SVN\conf folder.
c. To set the SVN system location for username and password information, configure
the svnserve.conf file to specify the location of the authorization and password
files. The svnserve.conf file is located in the C:\Program Files
(x86)\Emerson\PAC Machine Edition\fxManager\Server\SVN\conf folder.
Under the [general]section, remove the comments marker from the following lines:
▪ anon-access = none
▪ password-db = passwd
▪ authz-db = authz
d. Create a batch file named pre-revprop-change.bat containing the text exit 0,
and then add the batch file to the C:\Program Files (x86)\Emerson\PAC
Machine Edition\fxManager\Server\SVN\hooks folder.
5. In the Windows command prompt, create a Windows service for svnserve with the following
command line:
NOTES:
NOTE: The user name and password can be changed in the SVN repository. They are located in
the conf/authz and conf/passwd files.
e. In the Root Project field, enter:/SVN. (This is the last directory of the chosen path in step
3.)
f. In the Working Folder field, select c:\. The working directory will be c:\FX. If this
directory already exists, remove it first.
7. Configure the PAC Change Management Server service to depend on the SVN Server service,
in addition to the standard RPCSS service using the following command.