Link to the DSP Secure Portal -https://datascopedsp.com/resources/prerequisites-installation/ (request login details from Admin)
The following guidelines can be used when selecting or reviewing the software prerequisites.
If you don’t like reading, you can watch the video.
Try it!
Operating System
Microsoft Windows Server 2016 (or higher) - DATASCOPE PREMIUM will need a freshly installed Windows server as a base before the prerequisites are installed and configured. Microsoft Windows Server 2016 – 2019 is supported, but we recommend installing Microsoft Windows Server 2019
Microsoft Windows 10 (or higher) - DATASCOPE PREMIUM will need Microsoft Windows 10 installed. Microsoft Windows 10 is supported, but we recommend installing Microsoft Windows 11.
Databases
Microsoft SQL Server 2016 (or higher) - DATASCOPE PREMIUM will require access to the SYSPRO SQL server to access SYSPRO data and create a dedicated DATASCOPE PREMIUM database for the DATASCOPE PREMIUM company data. Microsoft SQL Server 2016 – 2019 is supported, but we recommend installing Microsoft SQL Server 2019
SYSPRO
SYSPRO Version 7 or 8 - DATASCOPE PREMIUM supports both SYSRO 7 and 8, and it should already be installed, configured, and working within the environment.
SYSPRO E.Net WCF Service (or WebServices) - The DATASCOPE PREMIUM system will integrate with SYSPRO using the standard E.Net Business Objects. Thus, the SYSPRO WCF Services or WebServices will be installed and working on the SYSPRO Server.
Install Users – SQL & SYSPRO
A dedicated SYSPRO Operator and SQL User will be required for the DATASCOPE PREMIUM installation. These should have full access to the respective systems as they will be used to create databases and validate the SYSPRO setup.
Browsers
Desktop browsers
Google Chrome
Mobile Browsers
Chrome
Mobile operating systems
Android 6.0 (Marshmallow)
Android 9 (Pie)
License File
A DATASCOPE PREMIUM License or Temp License file will be required.
PLEASE NOTE: It should be noted that the SYSPRO Database and DATASCOPE WMS Database need to exist on the same SQL Server instance. The reason for this is the system uses cross databases joins for optimal performance and to achieve this the physical databases need to be running on the same SQL Instance.