R800D Release Instructions
R800D Release Instructions
Release 8.00D
Release Instructions
Fourth Shift 8.00D Release Instructions
Important Notices
The material contained in this publication (including any supplementary information) constitutes
and contains confidential and proprietary information of Infor.
By gaining access to the attached, you acknowledge and agree that the material (including any
modification, translation or adaptation of the material) and all copyright, trade secrets and all
other right, title and interest therein, are the sole property of Infor and that you shall not gain right,
title or interest in the material (including any modification, translation or adaptation of the material)
by virtue of your review thereof other than the non-exclusive right to use the material solely in
connection with and the furtherance of your license and use of software made available to your
company from Infor pursuant to a separate agreement, the terms of which separate agreement
shall govern your use of this material and all supplemental related materials ("Purpose").
In addition, by accessing the enclosed material, you acknowledge and agree that you are
required to maintain such material in strict confidence and that your use of such material is limited
to the Purpose described above. Although Infor has taken due care to ensure that the material
included in this publication is accurate and complete, Infor cannot warrant that the information
contained in this publication is complete, does not contain typographical or other errors, or will
meet your specific requirements. As such, Infor does not assume and hereby disclaims all
liability, consequential or otherwise, for any loss or damage to any person or entity which is
caused by or relates to errors or omissions in this publication (including any supplementary
information), whether such errors or omissions result from negligence, accident or any other
cause.
Without limitation, U.S. export control laws and other applicable export and import laws govern
your use of this material and you will neither export or re-export, directly or indirectly, this material
nor any related materials or supplemental information in violation of such laws, or use such
materials for any purpose prohibited by such laws.
Trademark Acknowledgements
The word and design marks set forth herein are trademarks and/or registered trademarks of Infor
and/or related affiliates and subsidiaries. All rights reserved. All other company, product, trade or
service names referenced may be registered trademarks or trademarks of their respective
owners.
Contents
These Release Instructions contain directions to upgrade your existing Fourth Shift Release 7.50,
8.00, 8.00A, 8.00B, 8.00C system to Release 8.00D. You must have 7.50F, 8.00, 8.00A, 8.00B,
8.00C installed to upgrade to 8.00D.
Review the supported platform considerations and update your system as required by the Fourth
Shift Release 8.00D Release Notes document before upgrading to Fourth Shift 8.00D.
If you are running multiple Fourth Shift systems on the same server, all systems must be
upgraded to the same release before users access the system or data is processed. All traditional
GUI (FAT) client systems on a workstation must also be upgraded to the same release, even if
they access systems on different servers. For example, if you use two FAT client installations on
one workstation to access a test server and a live server, both servers and both clients on the
workstation must be upgraded to the same Fourth Shift release.
For detailed information on new features, enhancements, and important changes included in this
release, refer to the Fourth Shift Release 8.00D Release Notes.
During installation, the Fourth Shift database services are brought down on the Fourth Shift
server machine. This affects all applications that use the Fourth Shift database services on the
server you are updating.
If you are installing Fourth Shift on new server hardware, be sure to follow the instructions for
preparing and setting up the new server, which is included in this document.
• To successfully complete Fourth Shift installations on a Fourth Shift supported platform, the
local System account must be able to modify files in the directory. The System user account
must have security set to Full Control on the physical drive where Fourth Shift is installed,
such as C:\fshift or D:\fshift. The security is not specified at the mapped or alias drive such as
M:\.
• Verify that you are running Microsoft Windows Server 2012 R2 or Windows Server 2016 or
Windows Server 2019 or Windows Server 2020.
• Verify that you are running Microsoft SQL Server 2022, Microsoft SQL Server 2019, Microsoft
SQL Server 2017, Microsoft SQL Server 2016 with Service Pack 1, SQL Server 2014 with
Service Pack 2 or SQL Server 2012 with Service Pack 4. If you have not yet applied the
required Service Pack, follow the instructions for SQL Server provided by Microsoft before
beginning this upgrade.
• Verify the platform considerations sections in the document Fourth Shift 8.00D Release
Notes
• Note: that a Fourth Shift server can support up to ten installations of Fourth Shift.
If you are adding new server hardware to your Fourth Shift system with this release, follow these
instructions to prepare and configure the new environment.
If you are using existing Fourth Shift servers for this upgrade, skip this section and begin the
upgrade instructions for “Upgrading to Release 8.00D” on page 14 .
Creating the Fourth Shift Directory and Copying Fourth Shift Files to New Server
2. Create a folder on the new server that will contain the Fourth Shift system files, for example
C:\FSHIFT.
4. Share the folder just created, giving Full Control to the Everyone account.
6. On the General tab, click the Advanced button, Advanced Attributes and verify the
following:
• Checked: Allow files in this folder to have contents indexed in addition to file properties
7. On the old Fourth Shift server, stop the MAINXX, FINXX, Fourth Shift Lock Server, Fourth
Shift Remoting services and all other Fourth Shift applications.
8. Copy all files and folders from the root of your current Fourth Shift server machine’s mapped
drive (for example, M:) and paste to the newly created shared directory on the new server
machine.
9. On the new server, open the Mfgsys\Systems folder, right click on the FSAliaser.exe and
chose “Run as Administrator”.
10. Select the Drive: letter you wish to map. For simplicity, we recommend that you select the
same drive letter used for your previous Fourth Shift directory. The following instructions use
M: as the example drive letter.
11. From the “Aliased to:” field, browse for the new folder you just created, click Add, and click
Close.
12. If the Mapped drive, Server name, SystemIdentChar and SystemName on the new server are
different than the Mapped drive, Server name, SystemIdentChar and SystemName of the old
server, review the FS.CFG file (usually in the M:\Mfgsys folder) and edit the file using
Notepad or another text editor to change all instances of Mapped drive, Server name,
SystemIdentChar and SystemName in the file. Save the file.
Note: Use the “Run as Administrator” option to open a text editor such as Notepad to edit
the FS.CFG file.
13. Ensure the following configuration variables are set appropriately for your new server:
If you already have SQL Server installed on your database server, skip this step. Continue your
upgrade with “SQL Server Surface Area or Facet Configuration” on page 8.
Before installing SQL Server, ensure Microsoft .NET 3.5 SP1 or .NET 4.0 is installed on your
database server.
Complete the following procedure to install SQL Server on the new server if it is not yet installed
on the server.
Fourth Shift 8.00D has not utilized any new feature or function provided by Microsoft SQL Server
2022. To this point, compatibility with the Azure Extension for SQL Server is not provided by
Fourth Shift 8.00D.
For SQL 2022 or 2019 or 2017, on the Feature Selection screen, verify the following are selected:
Once the above features are installed, download SQL 2022 or 2019 or 2017 Reporting Services
and SQL Server Management Tools from Microsoft’s website and Install and Configure it
according to Microsoft’s instructions.
Fourth Shift 8.00D Release Instructions Page 7 of 33
Fourth Shift 8.00D Release Instructions
Install SQL Server and SQL Server Management Studio according to Microsoft’s instructions.
Make sure that the following options are selected during the installation:
3. In the Server Configuration window, Collation tab, verify the following is selected:
Note: Fourth Shift-specific settings are identified later in the installation when the empty
database is created.
After SQL Server is installed, it is important to ensure that SQL Server is configured to enable
features used by Fourth Shift. This is done using Microsoft SQL Server Management Studio to
configure facets.
2. Select server type Database Engine and the current server name (or “.” for local) along with
appropriate credentials and click Connect.
7. Click OK.
The following SQL Server configuration option should be updated to match the Fourth Shift year
range.
4. Select Advanced.
5. Change the ending year for Two Digit Year Cutoff to 2079 under the Miscellaneous group.
If you are using a new SQL Server database server, your current database must now be copied
over to the new server.
2. Verify that the MAINXX, FINXX, Fourth Shift Lock Server, Fourth Shift Remoting services
are not running.
3. Use SQL Server Management Studio to back up the FSDBXX transaction log.
4. Use SQL Server Management Studio to perform the pre-conversion SQL Server backup of
your FSDBXX database.
5. If you have converted your SAAM module to SQL Server and if your Sales Analysis data
resides in the separate SADBXX database, you must back up that database as well.
1. Open SQL Server Management Studio (run as Administrator), Select Server type Database
Engine, and click Connect.
4. Click OK.
6. Copy the database files from your current Fourth Shift database server’s Data folder to the
similar folder on the new database server (where XX is the value of the SystemIdentChar
FourthShift configuration variable):
• FSDBXX.mdf
• FSDBXXLog.ldf
• FSDBXXTemp.mdf
• FSDBXXLOGTemp.ldf
9. Click Add…
13. Repeat steps 8 thru 12 for FSBXXTemp.mdf and SADBXX.mdf (if applicable).
17. Repeat steps 14 thru 16 for FSDBXXTemp and SADBXX (if applicable).
2. Use SQL Server Management Studio to perform the SQL Server backup of your FSDBXX
database.
3. Repeat steps 1 and 2 for FSDBXXTemp and SADBXX databases and logs (if applicable).
If the user installing Fourth Shift is not an administrator of SQL Server and Rules Based Pricing
Module (RBPM) will be installed, a trusted connection between the Fourth Shift server and SQL
Server machine needs to be established before the Fourth Shift installation can be completed. To
set up a Trusted Connection, complete the following steps:
1. On the database server, open SQL Server Management Studio and connect to the
Database Engine.
5. Select the Users and Groups check boxes, then click OK.
6. Enter a unique login name in the Enter the object name... text box and click the Check
Names button.
This User/Group name is the name that must be used when logging into your Fourth Shift
server machine when installing Fourth Shift. Choose an individual or use a group that you
have defined to be granted the system administrator role to perform the install on the SQL
Server machine.
7. Click OK.
Your Fourth Shift system is identified on the network using the SystemIdentChar configuration
variable.
1. On the new server, right-click on the Notepad program and select Run as Administrator. Then
open the FS.CFG file with Notepad.
2. Verify that the configuration variable is defined in your FS.CFG file, for example using the
default SystemIdentChar = MR.
3. To verify that the directory specified by the SystemDir variable (normally M:\Mfgsys\System)
in the FS.CFG file is in the system path, go to Start—Control Panel—System and Security-
System.
a. Select Advanced System Settings and click Environmental Variables…
b. Click Path, under System Variables.
c. Click Edit…
4. If the value of the SystemDir variable (Ex: M:\Mfgsys\System) is not in the PATH variable:
a. Click New and add it to the end.
b. Click OK.
c. Click OK.
d. Click OK.
1. From Windows Control Panel, Region- Region, select the Administrative tab.
3. Make sure your current system locale is appropriate for the language being installed. For
example, if Chinese Fourth Shift is being installed, select “Chinese (Simplified, China)” and
click OK.
The settings for the SQL Server transaction log should be modified from Full to Simple before
starting the upgrade. This prevents the transaction log from becoming too full during the
conversion process and causing processing to slow down or fail.
1. On the database server, open SQL Server Management Studio, select Server type Database
Engine and click Connect.
3. Right-click the database, then click Properties to open the Database Properties dialog box.
The current recovery model is displayed in the Recovery model drop-down list.
This is done to ensure your SQL Server log file does not become too large during conversion.
This setting will be reset to Full later during the “Resetting the Recovery Model for the SQL
Server” procedure.
6. Click OK.
Note: In several locations, these instructions refer to a “Fourth Shift” folder in the Windows
“Start” menu. The actual folder name includes the system name, which is identified
during the installation. It is in the form system name – Fourth Shift (i.e., SystemA –
Fourth Shift).
• Ensure that all modcom transactions in the queues are processed by going to the APEX,
AREX, and GLEX Modcoms To Be Processed screens and verifying that no records
exist.
Fourth Shift 8.00D Release Instructions Page 13 of 33
Fourth Shift 8.00D Release Instructions
• Verify that the Fourth Shift server is running and can be accessed.
• Verify that there are no user connections to the Fourth Shift system from any source.
This includes connections to Fourth Shift databases from Fourth Shift applications with a
GUI, as well as ODBC and FSTM connections.
2. On the Fourth Shift server, copy the Fourth Shift 8.00D installation image (ISO file) onto the
local drive in a temporary folder.
3. From the root of the Fourth Shift installation folder, double-click FSServerSetup.
4. If you are prompted to install SQL Server Shared Management Objects, Command Line
Utilities, or CLR Types, click Install. If you are asked if you want FSServerSetup to make
changes to this computer, click Yes. Wait for SQL Server components to be installed.
5. If you are requested to choose between Install a new instance or Maintain or upgrade an
existing instance, choose according to the considerations below, and click Next.
• If the Fourth Shift system you are upgrading is already at 8.00 or above, select Maintain
or upgrade an existing instance.
• If the Fourth Shift system you are upgrading is still at a 7.50 release, select Install a new
instance.
6. On the Welcome screen, confirm that you are installing to a supported platform as
documented in the Fourth Shift Release Notes for this release, click Accept, and click Next.
7. Select Upgrade an existing Fourth Shift 7.50 installation, or migrate a copied 7.50 or
8.00 installation to this server, and click Next.
8. Browse for the Fourth Shift Configuration File (for example, M:\MFGSYS\FS.CFG)
Note: Make sure the correct configuration file is selected for the installation. The locations
specified in this file are updated by the installation.
9. Click Next.
The Serial Number and Module Access Key screen is displayed. The new Module Access
Key that came with your system is required during this procedure. Retrieve the email that
you received with the Module Access Key, enter your serial number, and browse for the key
file. Then click Next.
13. If you have not enabled CLR Integration for SQL Server, you will be asked to enable it now.
Check the box and click Next to continue.
14. On the Report Administrator Credentials screen, enter or update the user ID (with domain
name) for a domain user that is a member of the Administrators group on the IIS server used
for Fourth Shift reporting. This information is used to connect to the IIS server when a report
is requested by a user in Fourth Shift. Enter Report Administrator User Name in domain\user
or user@domain format, enter Password, and click Next.
15. On the FSTI Remoting Service Credentials screen, enter FSTI Remoting Service User
Name in domain\user or user@domain format, enter Password, and click Next. This user
will be used when the Fourth Shift Remoting Service is started on the Fourth Shift server.
16. On the Email Notification Configuration screen, verify or enter the Sender email address (for
the default FSMail account), email Server name, and Port number for your outgoing SMTP
mail server. Enter your email address as Recipient email address. Select the check box to
Reconfigure SQL Server for database mail by enabling “Database Mail XPs”, if it is
displayed. You may click the Send Test Email button and verify the administrator’s email.
Then click OK, verify that you received the test email, and click Next.
Note: It is strongly recommended to NOT select the Skip email notification setup check
box.
Note: After the installation is complete, you may choose to set up one or more additional
database mail profiles for Fourth Shift functions, for example for automatic emailing
of documents. Database profiles can be created using Microsoft SQL Server
Management Studio.
17. On the Selected Features screen, expand the Fourth Shift Server and make sure the Fourth
Shift modules you wish to install are selected, and click Next.
19. If you are asked to allow this program to make changes to this computer, click Yes.
20. Wait several minutes while files are copied, and your database is upgraded.
21. Click checkboxes to show the Readme and Windows Installer log files.
22. Run FSIntegrate utility, available from Fourth Shift Support Services via KB 1879013.
23. Refer KB 2290868 to Enable Overflow email notification for Supply Demand table
(Mfg_DFSFNSF)
24. Click checkbox to acknowledge that FSClientSetup must be run before Fourth Shift is
functional on the server (this step comes later in these instructions), and click Finish.
25. Review the installer log (INSTALL.HIS) and ReadMe (README.TXT) information files, then
close the Notepad windows.
Note: If you have upgraded from 7.50 on the same Fourth Shift server, you may notice on
Control Panel Programs and Features that entries now exist for both 7.50 and 8.00
Fourth Shift installations. This is expected and is caused by technology differences
between the 7.50 and 8.00 installers. Do not attempt to uninstall the 7.50 entries.
After the conversion process is complete, the transaction log settings must be reset.
1. On the database server, open SQL Server Management Studio.
The current recovery model is displayed in the Recovery model list box.
7. Click OK.
Backing up the Database and Transaction Log on the New SQL Server
Use SQL Server Management Studio to back up the FSDBXX database and transaction log.
1. From the SQL Server machine hosting the Fourth Shift database, map the selected drive
letter for that Fourth Shfit system to the appropriate shared folder on the Fourth Shift server.
2. Make sure that the Windows account that is logged in to perform the upgrade has permission
to install stored procedures in the SQL Server database. Review the server-level roles,
server-level permissions, and database-level roles for this information.
4. Right-click FSSQLSetup.exe file and choose “Run as administrator” to begin the Fourth Shift
Database Components installation.
If you get a message asking if you want to allow the program to make changes to this
computer, click Yes.
8. If you are asked to restart the server, select Yes, I want to restart my computer now.
9. After logging back in, the Setup Complete dialog is displayed. Click Finish.
11. Run FSIntegrate utility, available from Fourth Shift Support Services via KB 1879013.
If a firewall is used to secure your Fourth Shift server, your system administrator should be
managing the accessibility of the port numbers used for server-client connections if these
ports are outside your company’s firewall. The following port numbers are set as defaults in
Fourth Shift and should be made accessible to your users by creating Inbound and Outbound
rules:
Default Use
Port
Number
25 Ledgersoft for the email server and a port named FaxMan for the
fax function.
80 NET UI web port for HTTP traffic.
443 NET UI web page SSL port 443 for HTTPS traffic.
445 Fourth Shift Server for the mapped drive.
1001 Intelligent Night Application Processing (INAP) default port or 1002
1002 as an alternate.
1297 VisiBar port (default).
1433 SQL Server Database for SQL.
2056 Fourth Shift Server port for Lock Server.
2057 Fourth Shift Server for MAINXX database service.
2058 Fourth Shift Server for the FINXX database service.
2383 Business Intelligence Analysis Services port.
4101 VisiBar HTTP web interface port.
5432 Net UI server default port.
7361 Fourth Shift Remoting (on the Application Server).
• The default port numbers were already in use. Then the next sequential port number
will be assigned.
Client installations are required on the Fourth Shift server, My Fourth Shift Workplace server,
Terminal Server machines used to host Fourth Shift clients, and all workstations.
• If applicable, install the client components on the Terminal Server machine used to host
Fourth Shift clients from the Control Panel using Add/Remove Programs.
• Install the client components on the Fourth Shift and My Fourth Shift Workplace server by
running FSClientSetup from the MFGSYS\CLIENT directory.
• If the My Fourth Shift Workplace server is a different machine than the Fourth Shift
server, install the client components on the My Fourth Shift Workplace server by running
FSClientSetup from the MFGSYS\CLIENT directory.
1. From Windows Control Panel - Clock, Language, and Region – Region select the
Administrative tab.
3. Make sure your current system locale is appropriate for the language being installed. For
example, if Chinese Fourth Shift is being installed, select “Chinese (Simplified, China)” and
click OK.
3. Verify that the appropriate drive designator (for example: M:) is mapped to the Fourth Shift
directory on the database server. Make sure that the Reconnect at login box is selected if
you create this drive mapping.
5. If you are prompted to install Microsoft Interop Forms, click Install. When you are asked if
you want FSClientSetup to make changes to this computer, click Yes. Wait for the
components to be installed.
6. If you are presented with a choice of installing a new instance or maintaining an existing
instance, select Maintain or upgrade an existing instance and click Next.
8. If the Fourth Shift Configuration File screen is displayed, browse for your Fourth Shift
Configuration File (e.g., M:\Mfgsys\fs.cfg), and click Next.
If while browsing for the configuration file, the mapped drive for the configuration file is
not displayed, exit setup, apply a change to the registry, and restart setup. For more
information about the registry changes required, please see the following Microsoft
article:
http://technet.microsoft.com/en-us/library/ee844140%28v=ws.10%29.aspx
9. Accept the default destination folder, and click Next. The Select Features screen is
displayed.
10. Expand Fourth Shift Workstation and select the module components you want to update for
this workstation.
13. If you are asked if you want to allow the program to make changes to this computer, click
Yes.
14. On the InstallShield Wizard Completed screen, check Show the Windows Installer log.
16. Review and close the installation history log file for the workstation. If any errors are detected
in the log file, contact Customer Support.
17. Refer KB 2289256 for Reports export functionality issue in Windows 10 Workstation.
Note: If you have upgraded from 7.50 on a Fourth Shift client, you may notice on Control
Panel Programs and Features that entries now exist for both 7.50 and 8.00 Fourth
Shift installations. This is expected and is caused by technology differences between
the 7.50 and 8.00 installers. Do not attempt to uninstall the 7.50 entries.
• /L – Writes logging information to a log file at the specified path. When /L is not
specified, the default log file path for FSClientSetup is:
c:\Users\Public\Public Documents\Install_Workstation.his
• Install Fourth Shift workstation on a machine that is separate from the Fourth Shift server:
FSClientSetup.exe /s /v"/qb FS_CONFIGFILE=M:\Mfgsys\FS.CFG"
Workstation Post-Installation
If these steps were not completed on a previous upgrade of the client workstations, or for each
new workstation, complete the following post-installation steps.
This procedure allows users to generate reports from within Fourth Shift without requiring them to
enter a network ID and password each time a report is requested.
If these settings are not modified, the user will be required to enter a network user ID and
password each time a report is generated. In this case, the user would also need to have security
rights to the report template (RDL) files on the IIS server used for reporting.
You may need to be logged on as the administrator on the computer to complete this
process.
8. Enter the Reporting Services IIS server and domain information (in IE address format) in the
field: Add this website to the zone.
For example, if the IIS server is SERV1 on the CorpCo domain, it would be entered as
follows: http://serv1.corpco.com
9. Click Add.
12. Click on the Local intranet icon in the Internet Options window.
13. If the client will run My Fourth Shift Workplace, uncheck the “Enable Protected Mode”
check box.
14. Click Custom level… in the Security level for this zone section.
You must configure IIS on the server that is running SQL Server Reporting Services before
installing the Fourth Shift Reporting Services components.
1. Ensure Microsoft .NET 3.5 SP1 or .NET 4.0 is installed.
3. Go to Manage > Add Roles and Features. If the “Before You Begin” page is displayed, click
Next.
6. On the Server Roles page, select Web Server (IIS). If it was already selected, skip to step 8.
7. On the pop-up window for Add Roles and Features Wizard, click the Add Features button.
On the Select Features screen, click Next.
- HTTP Errors
- Static Content
- HTTP Redirection
• Performance
- Static Content Compression
• Security
- Request Filtering
- Windows Authentication
• Application Development
- .NET Extensibility (3.5 and 4.5 or 4.6)
- ASP
- ASP.NET (3.5 and 4.5 or 4.6)
- ISAPI Extensions
- ISAPI Filters
• Management Tools
- IIS Management Console
- IIS 6 Management Compatibility
- IIS 6 Metabase Compatibility
- IIS 6 Management Console
- IIS 6 Scripting Tools
- IIS 6 WMI Compatibility
- IIS Management Scripts and Tools
11. If you made any changes, click Install. Otherwise click Cancel.
12. If the Installation Results page indicates that the installation succeeded, click Close.
The Fourth Shift Reporting Services installation must be run to register the new RDL files
delivered with this release. This process must be performed on the server that runs Microsoft
SQL Server Reporting Services, which may or may not be the same as your Fourth Shift server.
Note: Verify that Reporting Services is configured properly before running the
FSReportingSetup.exe. SQL 2022 or 2019 or 2017 requires manual configuration of Reporting
Services.
If the Web server that runs Fourth Shift Reporting Services Components has SSL enabled,
make sure the SecureConnectionLevel setting in the RSReportServer.config file is set to 0
before installing Fourth Shift Reporting Services Components.
If Terminal Server is in use on the Fourth Shift server machine, the installation must be
started from the Control Panel, using Add/Remove Programs.
2. From the MfgSys\FSReporting folder of the drive mapped to the Fourth Shift folder, double-
click on FSReportingSetup.
3. If you are asked to allow this program to make changes to this computer, click Yes.
4. If you are requested to choose between Install a new instance or Maintain or upgrade an
existing instance, select Install a new instance and click Next.
5. The installer checks that the required role services are installed. The Welcome screen is
displayed. Click Next.
6. If you are prompted for the Fourth Shift configuration file (fs.cfg), browse for it, and click Next.
7. Accept the default Destination Folder, confirm your System Name, and click Next.
8. Enter the SQL Server connection information, including the password for the sa user.
11. The Fourth Shift Reporting Services Install screen is displayed with a list of installation
tasks.
• Restore default—to remove any existing report customizations that have been applied
using the Report Configurator.
To change the paper size to A4 (210 x 297 mm), click the Select Paper Size drop-down list.
Note: For more information on the A4 paper size option, see the Publishing RDL Files
topic in the SQL Server Reporting section of the Fourth Shift online help under
System Help.
16. Click Install.
17. When the installation is complete, click Yes to the message Process completed
successfully. Would you like to open the log file?
18. Review the RSInstall log file for any errors that may have occurred during the publishing of
reports. If any errors are detected in the log file, contact Customer Support.
19. Close the log file when you’ve finished viewing it.
20. Click Close on the Fourth Shift Reporting Services Install screen.
24. If the Web server on which you are installing Fourth Shift Reporting Services uses SSL,
change the SecureConnectionLevel setting in the RSReportServer.config file back to the
value used at your site.
26. If the Reporting web server name has changed during this upgrade, you can change it by
running the Fourth Shift Report Configurator on the Fourth Shift server. Click the Mass
Modification tab, select Web Server Name, and make the needed change in the To column.
Click Update and then click OK. Exit Fourth Shift Report Configurator.
If you switched to a new database server and you’ve granted domain users access to the Fourth
Shift databases (FSDBXX and SADBXX, if applicable), consult Microsoft SQL Server
documentation regarding transferring domain user accounts from one SQL Server to another.
If you do not use My Fourth Shift Workplace, you may skip this section. If you are installing My
Fourth Shift Workplace for the first time, open “WEBM.pdf” and follow the instructions in the
section “Installing and Updating My Fourth Shift Workplace.”
During the installation process, the Internet Information Services (IIS) will be stopped. This means
that all applications using IIS on the server, including My Fourth Shift Workplace, will not be able
to connect to the server until the services are restarted.
During the My Fourth Shift Workplace installation, the portals database will be updated. A trusted
connection is used to access the database. The network login ID used to complete the installation
Fourth Shift 8.00D Release Instructions Page 25 of 33
Fourth Shift 8.00D Release Instructions
must have sufficient rights to create tables, alter tables, and grant security permissions in the
portals database.
The WebUI Windows Account is a Windows user login that will be used by WebUI. This is
needed because many users can start WebUI sessions, but a single identity is used to set their
permissions. All WebUI processes and customizations will impersonate this user when accessing
the system.
2. WebUI Finders. The WebUI Finders will impersonate this user when they browse the
database. This will be setup automatically by the Workplace Server installation. If you wish to
modify the WebUI Windows account after Workplace is installed, the Windows Internet
Information Server utility can be used to change the identity of the FSWpAppPool application
pool.
3. Fourth Shift database. Since the WebUI processes run as this user, the WebUI Menu
Explorer and the WebUI Finders connect to the database as this user and therefore need
appropriate database access permissions set up. To accomplish this, assign the WebUI
Windows Account user to the FSUSER role in the Fourth Shift database by performing the
following steps:
a. Open SQL Server Management Studio.
b. Go to Databases > FSDBXX > Security > Users.
c. Right-click Users, click New User...
d. Click Add...
e. Enter a User name.
f. After Login name, click …
g. Enter the user name, click Check Names.
h. Select the User Name, click OK.
i. Click OK on the Select Login window.
j. On the Database User - New screen, click Membership page.
k. Select FSUSER, and click OK.
If you wish to modify the WebUI Windows account after Workplace is installed, run the Workplace
Server installation in repair mode, specifying a new account when prompted. Alternatively, the
account can be updated in IIS Manager by updating the FSWPAppPool identity, and the Physical
path credentials for FSChart, FSPortals and FSWebUI. Also, make sure that the account
specified has access to the FSDBXX and, if applicable, FSUIENU databases.
2. On the Fourth Shift Workplace server, copy the Fourth Shift 8.00D My Fourth Shift Workplace
installation image (ISO file) onto the local drive in a temporary folder.
If Terminal Server is in use on the IIS server machine, the installation must be started from
the Control Panel, using Add/Remove Programs.
3. From the root of the My Fourth Shift Workplace installation folder, double-click
FSWorkplaceSetup.
4. If you are prompted to install pending requirements, click Install. If you are asked if you want
FSWorkplaceSetup to make changes to this computer, click Yes. Wait for the components to
be installed.
5. On the Welcome screen, click Next. The Locate Configuration File screen is displayed.
8. Enter a domain user (in domain\user or user@domain format) and password for which
WebUI applications can run to gain access to the Fourth Shift database, as described in the
WebUI Windows Account section above.
• Database server name (with Instance Name, if applicable) for your FSWorkplace
database
• Password
• If you are installing Workplace for the first time, select Create new database. If you are
upgrading, leave it unchecked.
11. Click Next. The Encryption Warning screen is displayed.
12. Read the encryption warning, check to accept responsibility for encryption
considerations, and click Next. The Serial Number and Module Access Key screen is
displayed.
13. Confirm your serial number, browse for your key file if necessary, and click Next. The
Custom Setup screen is displayed.
15. If Connectivity Toolkit was selected, the Connectivity Toolkit Instance screen is displayed.
16. Enter the sa Password, select the Local SQL Server Instance, and click Next. The Ready
to Install screen is displayed.
18. If you are asked if you want to allow the program to make changes to this computer, click
Yes.
19. When the InstallShield Wizard Complete screen appears, check to Show the readme file
and Show the Windows Installer log, and click Finish.
20. Review and close the FSWP_README file and the FS Workplace installation history log file.
Note: If any errors are detected in the log file, contact Customer Support.
21. If you are prompted to restart your system, click Yes, and log back in to the server when
prompted.
22. Using Windows Server Manager, turn off IE Enhanced Security Configuration (IE ESC) for
both Administrators and Users.
23. Once the My Fourth Shift Workplace server upgrade is complete, each client needs to delete
old, cached internet files in EDGE Brower. On each client, use the EDGE Setting"Privacy,
Search, and Services" and Clear Browsing Data option by deleting these files, a new copy
will be downloaded from the My Fourth Shift Workplace server when needed.
Setup of Workplace server that is on a different machine than the Fourth Shift server requires a
few manual steps. This is mainly because the web sessions are started from a service, so they
do not have a complete user context. On a combined server, the Workplace install automatically
sets up the WebUI Windows Account, so there are no problems. This setup is not quite enough
when the Workplace server is pointing at a remote Fourth Shift server.
1. On the Fourth Shift server, create a Fourth Shift configuration file for Workplace to
access. Copy the fs.cfg file to a new name (possible fswp.cfg) and change its SystemDir
variable to use a UNC path. For example add \\FSservername\FSHIFT\mfgsys\system
right before M:\mfgsys\system.
2. On the Workplace server, from Control Panel > System, select Advanced system
settings, next click on Environment Variables. Edit the Path in the System variables
to add the UNC path right before the Fourth Shift system path. For example, add
\\FServername\FSHIFT\mfgsys\system right before M:\mfgsys\system.
3. Restart the Workplace server so that the new Path will take effect.
If your system includes custom-generated XSL files, you must regenerate the custom XSL files
and test your customizations to make sure they work with the new release.
Note: the below information could impact your existing My Fourth Shift Workplace
Connectivity Toolkit customizations.
• The CustomField and SelectExternal Connectivity Toolkit built-in functions have now
disabled the ability to pass SQL queries as parameters. The preferred method is to
utilize the CustomField.txt and SelectExternal.txt files to execute SQL statements. But if
you choose to pass SQL statements as parameters, instructions for enabling this method
can be found in a WARNING comment of the CustomField.asp and SelectExternal.asp
files in the inetpub\wwwroot\FSWebUI\Builtins folder.
• My Fourth Shift Workplace supports the ability to reference an external web site outside
of the Workplace server (for example, a carrier or vendor web site). This feature
continues to be enabled by default. If you are not using this capability, it can be disabled
by modifying the line for “X-Frame-Options” in the file web.config, which can be found in
the inetpub\wwwroot\FSPortals folder. See specific instructions in that file.
• My Fourth Shift Workplace preventing from XSS (cross-site-scripting) attacks and prevent
MIME types security risk are added in the web.config with instructions. These settings
can be managed by editing web.config file, which can be found in the
inetpub\wwwroot\FSPortals folder.
Install .NET 2.0 or 3.5 or .NET 4.0 Framework and Service Pack Prerequisite
If the Microsoft .NET Framework version 2.0 Service Pack 2 (or a later Service Pack) or .NET 3.5
Service Pack 1 or .NET 4.0 is not installed on the server and the client machines, then it must be
installed before beginning.
The Net UI Module is installed at the Windows server using the same method as all other
modules.
If you installed all modules at once, this step was completed during the module installation for the
rest of the system. This step is needed only if you are adding the Net UI Module to your existing
system.
Note: The Net UI Server application is installed during this process and must be running on
the server for clients to be able to log in. You should use the same user name to
complete the installation as it will be used to run the Net UI Server application. This
guarantees that the installation program sets up the correct user profile. This is
especially important when the server is a Windows Terminal Server, because each
user is assigned a different Windows directory.
1. Use the SETUP program to install the Net UI Module.
See the Installing and Implementing Fourth Shift manual for detailed instructions on installing
a new module.
See "Net UI Security" in the Net UI Concepts section of the Net UI online manual in the
System Help in Fourth Shift for more information.
After completing the Net UI server module installation, several files must be copied to the web
server to access Fourth Shift via the Internet.
Note: These steps represent only one way to set up Internet access to Fourth Shift. You
can implement Internet access differently if desired. For example, you could add the
Fourth Shift access to your company web site. Use your internal resources to modify
these steps accordingly.
Fourth Shift 8.00D Release Instructions Page 29 of 33
Fourth Shift 8.00D Release Instructions
Note: Be sure to use the same drive letter as on the server. For example, M:.
1. Verify that the NET UI server is running. If not, start the server from the Start button, Fourth
Shift, NetUI Server.
2. Go to the setup folder under the location specified by the WebNuimDir configuration
variable.
If you get a message asking if you want to allow the following program to make changes to
this computer, click Yes.
• Net UI Listen Port. Modify the port number if you changed the port number used on the
Fourth Shift database server. The default port number is 5432
Note: You may need to open this port through the server’s Windows Firewall for it to accept
connections from the client.
5. Click Install.
6. If you get a message asking if you want to create the FSWeb directory, click Yes.
2. If there was a Net UI installation from a version of Fourth Shift before the current release,
then select Yes to the message: "The old version of FSWeb has been installed in this
machine. The program will delete the old files and folders. Do you want to continue?"
Final Steps
1. Communicate to your users the URL location so they can begin using the new Web page by
going to Microsoft EDGE (Run as Administrator to do the download), and entering the
following location:
http://ServerName.DomainName/FSWeb
(where ServerName is the name of the Net UI server and DomainName is the name of your
domain.)
Remote client installations use the web page installed in the previous section to create a package
for installation. You should not use the standard SETUP program to install remote clients,
because the configuration would assume that the client was on a local LAN. The Web page is
designed to install only the components not already installed. If a component is installed at the
correct version, no installation is completed.
The following workstation installation options are available from the web page:
• Default installation includes: Fourth Shift Net UI Base System, Fourth Shift Report Viewer,
and Graph Viewer components.
• Fourth Shift Application Help can be included if the check box Include Fourth Shift Application
Online Help is checked.
The Web page will indicate if a download is needed based on a comparison of the current version
of the files on your workstation and the current version of the files on the web server. The
recommendations indicate if more recent files are available on the server or if any required
components are missing.
The package file created from the web page can be saved (rather than opened immediately) and
transferred to a user directly if needed.
If the Microsoft .NET Framework version 2.0 Service Pack 2 (or a later Service Pack) or .NET 3.5
Service Pack 1 or .NET 4.0 is not installed on the server and the client machines, then it must be
installed before beginning.
Security Configuration
In order to complete the installation from the web page, specific security settings are needed.
You may need to be logged on as the administrator on the computer to complete this
process.
8. Enter the website URL for the Fourth Shift web server. For example, you might enter:
http://Server1.MyCompany.com/FSWeb
12. With the Local intranet zone selected, click the Custom level button for Security level for this
zone.
15. Click OK. If shown, click Yes to the confirmation message that you want to change the
settings.
2. Select a NetUI server to download the NetUI thin client you want to install.
3. Check the option Include Fourth Shift Application Online Help if the Fourth Shift Help is
needed on the client.
4. Click Download.
5. Specify whether you want to run the package immediately or save it to a disk location.
• If you choose to open the package immediately, the selected components will be
installed.
• If you choose to save the file to a disk location, the file can be copied to and used by
multiple workstations. You must run the downloaded file before you can use Net UI.
Saving the file will also allow you to right-click the file and choose the “Run as
administrator” function if the operating system requires it (i.e., Windows 7, Windows
Vista, or later).
6. In EDGE, click the “Refresh the web page” button or hit F5 to enable the Run Net UI button.
7. Start Net UI from the web page by clicking the Run Net UI button.
8. Once installed, you can bypass the use of the web page to run Net UI. You can create an
icon shortcut on the Desktop that starts the Net UI thin client. The command line for this icon
may be similar to the following example:
The thin client installation from the network creates a Net UI shortcut in the Fourth Shift folder.
The standard client installation creates a Fourth Shift shortcut to access the main Fourth Shift
program. Both shortcuts can be installed on the same workstation. These shortcuts allow you to
easily switch from one client access method to another. For example, to use the Engineering
Module, the standard client must be used.
This might be useful, for example, if you use the same computer when accessing the network
locally and when traveling remotely. The standard client could be used locally and the thin client
used when traveling.
Both the standard client and the Net UI thin client can be accessed by the Fourth Shift Explorer.
For more information on special considerations for using these two features together, see "Net UI
and Other Startup Options" in the Fourth Shift Basics online manual.