Post Installation

This topic outlines the checks you need to perform after installing SYSPRO 8 to ensure that the system is functioning correctly.

Exploring

You have just installed SYSPRO 8. There are just a few more things you need to review to ensure that everything functions correctly.

Topics

SYSPRO 8 - Supported Platforms

SYSPRO 8 - Technology Requirements

SYSPRO 8 Readiness Check

Pre-installation: Upgrade

Pre-installation: New

SYSPRO Installer

Data Conversion

Archiving Migration

SYSPRO Hotfixes

Installation-related FAQs

PDF and Video Resources

Install Guides

Starting

  • Install SYSPRO 8 using the SYSPRO Installer.
  • Install SYSPRO 8 using the SYSPRO Installer.

  • Convert your SYSPRO 7 Update 1 data using the Data Conversion program.

Solving

The SYSPRO 8 runtime uses Micro Focus installation software and is therefore listed as Micro Focus COBOL Server within the Program and Features function of your Windows Control Panel application.

Removed:

Direct calls to Encore.dll are no longer available.

Reason:

Directly referencing Encore.dll using COM/DCOM limits applications to 32-bit as well as SYSPRO's future expandability.

In addition, any third party applications referencing the SYSPRO DLL's directly make it difficult for SYSPRO to easily enhance the system without requiring each third party application to also be changed.

Web Services are still supported, so developers who have previously used Web Services will work unchanged.

Replaced by:

Using the SYSPRO 8 e.net Communications Load Balancer service de-couples applications from the e.net 64-bit library and provides excellent scalability and performance.

Additional benefits:

  • No limitation of being tied to a specific technology (e.g. 32-bit, etc.)
  • The system is more robust as any failures don't prevent the system from continuing on the other threads.
  • The system is multi-threaded and has a significantly improved performance under load.
  • Third party applications can reside on any server/computer that has access to the endpoint.

When you upgrade from SYSPRO 7 Update 1 to SYSPRO 8 (using the SYSPRO Installer Application) the process is as follows:

  1. SYSPRO 7 Update 1 installation files are removed.

    There may be some files left behind after this process because of new files added through ports, or third party developer files.

  2. The SYSPRO 8 installation process checks whether there are any remaining legacy files.

    If any are found, they are moved to a newly-created archived folder (Archived_SYSPRO7Files).

  3. The following folders are added to the archived folder in the SYSPRO 8 install location:

    • \Programs
    • \Screens
    • \Base\Bin
    • \Base\UI

Possible scenarios for requiring a reset of your SQL Server credentials include:

  • You can't log into SYSPRO because of a SQL Server credential error (e.g. password expired).
  • You are in a support environment and have been supplied with a database that you cannot access, possibly due to not having the SQL password.

From SYSPRO 8, you can reset your SQL Server credentials:

  1. Open IMPACT.INI (located in the WORK folder) using an editor application such as Notepad.

  2. Change the SQLADM entry to SQLADM=[reset] or change the SQLSTD entry to SQLSTD=[reset]

    Changing either entry enables you to reset the password for both accounts. The word 'reset' is not case sensitive.

  3. Save the file and log into SYSPRO.

    You will be prompted to enter a new SQL Server user name and password for both the administrative and standard logins.

Prior to SYSPRO 8 2019 R1, any customized web view by operator or role surfaced in both SYSPRO and SYSPRO Avanti.

From SYSPRO 8 2019 R1 onwards you must explicitly state whether a web view is targeted for SYSPRO or SYSPRO Avanti.

Because any pre-existing web view is assumed to be for SYSPRO Avanti, if you want existing SYSPRO web views to appear in later versions of SYSPRO, you must rename the .JSON file to include a _SYSPRO extension (e.g. UX_OperatorCode_ProgramLZ_SYSPRO.JSON).

The .JSON file resides in your \Base\Settings folder (or the Role_xxx folder if the user interface is configured by role).

You can also rename the file using the Save as function from within the Visual Designer. You will be prompted to indicate the type of web view you want to save (i.e. Avanti or SYSPRO Client).

Using

Check Description

1. Services

Start up the SYSPRO Services.

2. Licensing

  • Apply the licensing for new modules and users (if any) in the Company Setup program.
  • Update the company settings for any new modules.

3. Data conversion

The upgrade from SYSPRO 7 Update 1 to SYSPRO 8 converts all ISAM data into SQL tables.

Therefore, we recommend that you run the SQL Server Diagnostic program to ensure database integrity.

4. Port numbers

Ensure that all port numbers configured in the System Setup program are correct.

5. Security

  • Review and assign the security features required for all users, including electronic signatures, operator activities and role-based security.

    This is only required for first time installations.

    If you have upgraded from SYSPRO 7 Update 1, your security settings will be retained.

  • If any users require denied access to Custom Form Query business objects, you can enable this now.

6. Web views

Any web views created in SYSPRO 7 Update 1 must be renamed in order for them to appear in SYSPRO 8.

Prior to SYSPRO 8 2019 R1, any customized web view by operator or role surfaced in both SYSPRO and SYSPRO Avanti.

From SYSPRO 8 2019 R1 onwards you must explicitly state whether a web view is targeted for SYSPRO or SYSPRO Avanti.

Because any pre-existing web view is assumed to be for SYSPRO Avanti, if you want existing SYSPRO web views to appear in later versions of SYSPRO, you must rename the .JSON file to include a _SYSPRO extension (e.g. UX_OperatorCode_ProgramLZ_SYSPRO.JSON).

The .JSON file resides in your \Base\Settings folder (or the Role_xxx folder if the user interface is configured by role).

You can also rename the file using the Save as function from within the Visual Designer. You will be prompted to indicate the type of web view you want to save (i.e. Avanti or SYSPRO Client).

7. Custom software

Any previously installed custom software (developed in the same technology as SYSPRO) should be re-installed or verified that it functions as expected in SYSPRO 8.

8. Reports

Ensure that all Report Writer and SYSPRO Reporting Services reports work as required.

9. Confirm software

Verify that the software works as expected.

10. Financial checks

Check all your balances against the balances printed prior to the upgrade and conversion.

11. Operator login

  • Deselect the Prevent further logins setup option in the Company Setup program.

    This allows users to log back into the system.

  • Notify users that they can now use the new software.

12. Third party applications

  • Any previously installed third party applications may need to be re-installed or updated to work with SYSPRO 8.
  • Check with the relevant third party developers for further information.

13. Custom tiles

If you had custom tiles in the SYSPRO 7 Update 1Custom program folder, you need to manually move these to the \Plugin\CustomStore folder in SYSPRO 8.

Custom tiles are named CX_Tile*.SQL.

14. Analytics

If you are an Analytics user (and your existing Analytics site databases are on SYSPRO 7 Update 1) ensure that you manually migrate and update your site databases inside the Analytics program.

15. Archive Migration (Optional)

If during the data migration you elected not to convert your archive data, you have the option of performing this at a later stage using the Archiving Migration program.

16. Bin to Serial Linkage (Optional)

If you want to make use of the new improved Bin to Serial Linkage feature (which enables you to accurately determine where serials reside in a warehouse from the perspective of bins) enable the Associate serials by bin setup option (Setup Options > Configuration > Distribution > Inventory).

For more information on this feature, please refer to the Bin to Serial Linkage reference guide.

A hotfix is the minimum software required to provide a solution for a specific problem experienced by one or more customers. These can also include any relevant dependencies.

SYSPRO provides hotfixes as a way of deploying software updates during the release of SYSPRO 8.

Types of hotfixes available include:

  • Mandatory Hotfix

  • Optional/Customer-specific Hotfix

  • Consolidated Hotfix

  • Diagnostic Hotfix

  • Restricted Hotfix

  • Withdrawn Hotfix

Hotfixes are available from the SYSPRO Installer application.

Please refer to the SYSPRO Hotfixes reference guide for a detailed explanation.

This program lets you complete the migration of data from SYSPRO 7 Update 1 SYSPRO 8, if you elected to defer the conversion/migration of your archived data when running the Data Conversion program.

The archive data that can be converted from this program includes:

  • ECC BOM archive (XML)
  • WIP archive (XML)
  • Sales order archive (XML)
  • Lot archive (ISAM)

Archived data will not be available in SYSPRO 8 until it has been converted using this program.

For more detailed information regarding the Archiving Migration program, please refer to the Archiving Migration reference guide.

Architecture enhancements

Various improvements have been made to the architecture of SYSPRO 8 to future-proof the product and plan for innovative development.

e.net Communication Load Balancer service

As SYSPRO 8 strives towards sophisticated simplicity, we have enhanced how the client-server and e.net environments work:

  • The SYSPRO 8 Communications Service is used for client-server communications, as this is a faster, more secure, 64-bit and firewall-friendly communication method.

  • Specific client components (e.g. VBScript, SRS, Predictive search, etc.) use the SYSPRO 8 e.net Communications Load Balancer service to call the relevant business objects.

    This is a more secure, scalable, robust, 64-bit method of running e.net business objects.

  • All third party apps access SYSPRO via the SYSPRO 8 e.net Communications Load Balancer service.

Prior to SYSPRO 8 2019 R1, any customized web view by operator or role surfaced in both SYSPRO and SYSPRO Avanti.

From SYSPRO 8 2019 R1 onwards you must explicitly state whether a web view is targeted for SYSPRO or SYSPRO Avanti.

Because any pre-existing web view is assumed to be for SYSPRO Avanti, if you want existing SYSPRO web views to appear in later versions of SYSPRO, you must rename the .JSON file to include a _SYSPRO extension (e.g. UX_OperatorCode_ProgramLZ_SYSPRO.JSON).

The .JSON file resides in your \Base\Settings folder (or the Role_xxx folder if the user interface is configured by role).

You can also rename the file using the Save as function from within the Visual Designer. You will be prompted to indicate the type of web view you want to save (i.e. Avanti or SYSPRO Client).

SYSPRO 8 includes major architectural changes to Document Flow Manager (DFM). These include:

  • Services installs
  • Re-architected .Net Services
  • Using Microsoft SQL Server for message queuing

  • Improved user-interfaces for all DFM applications

Description of change:

The options for connecting to SQL Server has changed.

In SYSPRO 7 Update 1, the System Setup program provided 3 options:

  • SQL authentication (Operator login+pass)
  • SQL authentication (ADMIN login+pass)
  • Windows authentication

In SYSPRO 8, this has been simplified to 2 options:

  • SQL authentication

    The SQL Server standard user information entries are used by default.

  • Windows authentication

SYSPRO 8 also lets override this at operator level (using the Operator Maintenance program - which has new options allowing specific operators to have their own SQL Server user name and passwords).

Reason:

Simplified system setup and the ability for customers to trace SQL Server usage by SQL login.

Description of change:

When creating a VBScript in SYSPRO 7 Update 1 and prior versions, a special variable named enetguid was available. This legacy variable was required in older VBScripts to invoke an e.net business object.

This logic was superseded several versions ago, by allowing you to use the simpler CallBo function call to invoke e.net business objects.

So, if you have previously used the enetguid variable, you need to recode your VBScript to use the CallBo function.

Reason:

Simpler process.
Custom Form Query

Description of change:

From SYSPRO 8 onwards, only authorized operators will be able to run direct calls to the COM Custom Form Query (COMQFM) business object.

However, operators who run calls to this business object via another business object (e.g. INVQRY - Inventory Query) are unaffected.

Reason:

Improved security.

The following IMPACT.INI entries are obsolete for SYSPRO 8

Values in square brackets [ ] indicate the names when running in development mode:

  • IMPPRG=

    For SYSPRO 8 there are fixed locations for 32-bit and 64-bit programs:

    • \Programs [\PRG]
    • \Programs64 [\PRG64]

  • IMPGUI=

    For SYSPRO 8 there are fixed locations for client screensets:

    • \Screens [\GUI]

  • CUSPRG=

    For SYSPRO 8 there are fixed locations for custom 32-bit and 64-bit programs:

    • \Plugin\CustomPrograms
    • \Plugin\CustomPrograms64

    CUS*.IMP files previously located in the custom program folder are now located in:

    • \Plugin\CustomStore

  • CUSGUI=

    For SYSPRO 8 there are now fixed locations for custom client screensets:

    • \Plugin\CustomScreens

In addition to focusing on SQL Server for improved scalability and availability and future-proofing your systems, SYSPRO 8 is also about simplifying the system where possible. For this reason, some options have been simplified and/or removed as part of this process. In all cases the options that remain provide for improved scalability, performance, availability and/or security.

The SYSPRO 8 Readiness Check program (run from within SYSPRO 7 Update 1) performs a number of validation checks when determining if your system is ready to be upgraded and will advise on some of the technologies that are no longer supported.

SQL Connections

Removed:

Connecting to Microsoft SQL Server using an ODBC DSN

Reason:

Prevents setup requirements and resulting issues with native ODBC drivers

Replaced by:

SQL Server connection strings

Already the preferred option in SYSPRO 7 Update 1.
Custom Form data format

Removed:

Support for a single table storing all custom form data

Reason:

Poor scalability, poor data accessibility and poor performance as data grows

Replaced by:

Separate tables per master table

Already the preferred option in SYSPRO 7 Update 1.
Client-Server communication technology

Removed:

Client-server communication using legacy CCI technology

Reason:

Inappropriate port handling over a firewall, and poor resilience when reduced network stability

Replaced by:

SYSPRO 8 Communications Service using Microsoft WCF technology

Already the preferred option in SYSPRO 7 Update 1.
Web-based applications

Removed:

Web-based applications using the legacy HTML interface

Reason:

Very limited functionality and no customization available, based on legacy technologies

Replaced by:

SYSPRO Espresso mobile solutions provides functionality available in the web-based applications, is highly customizable, provides off-line functionality, etc.
SAP Crystal 2008

Removed:

Support for SAP Crystal 2008

Reason:

Crystal 2008 is no longer supported by the OEM vendor

Replaced by:

The new version to use is SAP Crystal 2013

From SYSPRO 8 2020 R2, server-side reporting requires SAP Crystal Reports 2016.
ISAM

Removed:

Support for ISAM data format

Reason:

Lower performance, increased file system usage, poor data integrity, etc.

Replaced by:

Microsoft SQL Server provides enterprise-strength Data Integrity, Security, Scalability, Availability, Simplicity and Performance that can be accessed by all popular querying and reporting tools.
Preactor integration

Removed:

Preactor integration is no longer supported in SYSPRO 8.

Replaced by:

SYSPRO's Manufacturing Operations Management (SYSPRO MOM) is a complete solution for manufacturing companies that includes:

  • Scheduling
  • Planning
  • Equipment
  • Employees
  • Dashboards
Encore.dll via e.net Communications Service
For more information, please read the SYSPRO e.net Solutions article.

Removed:

Direct calls to Encore.dll are no longer available.

Reason:

Directly referencing Encore.dll using COM/DCOM limits applications to 32-bit as well as SYSPRO's future expandability.

In addition, any third party applications referencing the SYSPRO DLL's directly make it difficult for SYSPRO to easily enhance the system without requiring each third party application to also be changed.

Web Services are still supported, so developers who have previously used Web Services will work unchanged.

Replaced by:

Using the SYSPRO 8 e.net Communications Load Balancer service de-couples applications from the e.net 64-bit library and provides excellent scalability and performance.

Additional benefits:

  • No limitation of being tied to a specific technology (e.g. 32-bit, etc.)
  • The system is more robust as any failures don't prevent the system from continuing on the other threads.
  • The system is multi-threaded and has a significantly improved performance under load.
  • Third party applications can reside on any server/computer that has access to the endpoint.