Try it!

System Requirements

For more information, refer to the Installation Prerequisites User Guide

Server Preparation

The first step is to prepare a new server with DATASCOPE PREMIUM installed. This step can be done without impacting the live site in any way, so that it can be done in parallel with no downtime. For this step, you will need the following:

• Physical or Virtual Server

• Windows Server 2019 installation

• System Manager Agent Install MSI

Software Prerequisites

Operating System

1. Microsoft Windows Server 2019 (or higher)

DATASCOPE PREMIUM will need a freshly installed Windows server as a base before the prerequisites are installed and configured. This can be installed on a Physical or Virtual server. The base default installation can be used as the specific server requirements will be added afterward.

This should be installed and configured on the network and Domain, etc., as required by the site IT department.

System Manager

The next step is to install the DATASCOPE WMS System Manager on the new Server. This will be used to install the prerequisite and, ultimately, the software.

Server Role Prerequisites

Before running the System Manager checks, some Server roles must be configured on the Windows Server under Internet Information Services Roles.

For more information, refer to the Prerequisites Server Roles User Guide.

Installing DATASCOPE PREMIUM

The next step will be configuring the general settings required to install DATASCOPE PREMIUM.

At this point, the following will be required:

• System Manager must be installed.

• The latest Port must be downloaded.

• Servers Roles should be configured.

• The DATASCOPE WMS License file must be uploaded.

• SYSPRO Server and E.Net Integration detail

• SQL Server details.

• A local Administrator User account and password

• A SYSPRO ADMIN Operator and password.

1.1      Software prerequisites

Refer to WMS Software Prerequisites

1.2      Configuration

The next step in the process is to complete the System Manager configuration page; this consists of the SQL Server, SYSPRO Server, and WMS Server details. These details will need to be entered and verified using the System Manager.

• Open System Manager and select 4. Clean Install.

• Click Next on all the screens where you already did the Server Role validation and installation of the software prerequisites.

• If you click Next on the last screen where the License was added, you will start to configure the general settings.

Open

• Starting with SQL Server and SYSPRO Server.

Open

• Start by entering the IP address of the server where SQL Server is installed.

• Next, you must enter the SQL Administrator username and password. This must be a SQL SysAdmin account.

• The next step is to enter the SYSPRO Name/IP address. This might be the same as the SQL Server Name/IP address, but if it is a different server, add the correct IP address.

• Select the correct Integration method. WCF vs. WebServices

• Ensure the Port is set to the correct Port Number. This is located under Services / SYSPRO 8 e.net Communication Load Balancer. If you do not update this port number, you will get an error later.

• To locate the correct Port number:

• Lastly, you can enter the IP address of the WMS Server.

• Select Next.

• The following screen will appear: Core Service Account. These are the details for the account used to run the WebAPI and Core Services DATASCOPE WMS Services on the new Server.

• If no domain is registered, you can select No Domain

• Enter the Username and password of the Local Administrator account used to log into the WMS Server. This account will run the WebAPI and Core Services / DATASCOPE WMS Services on the new Server. It is advised to use a local administrator account to ensure it works correctly.

• Select Verify Credentials to ensure it is correct.

• Select Next to continue.

• In the next screen, enter the Admin SYSPRO Operator username and password. This is required to validate that the SYSPRO E.Net setup is working. This process will do an E.Net login call to the SYSPRO E.Net Business Objects, ensuring all is in working order.

• Enter the applicable Company.

• Select Next to continue.

• The next step is where the new databases will be created.

• Select the tick box next to the WMS Company. A pop-up will appear asking whether a new WMS database must be created.

• Select No

• Then simply select the databases for SYSPRO and WMS based on the Company you selected.

• Select the All Warehouses tick box.

• Select Next to continue.

• If you had a second database for a second Company (i.e., one for PROD and one for TEST), you can just select those on the second screen.

• Select Next to continue.

• Select the version and port that was pre-downloaded.

When doing a DATASCOPE PREMIUM (Docker installation) to DATASCOPE PREMIUM (Server) migration for go-live, any version can be used at this point as the DB is not being used by a live environment.

• Select Next, and it will extract to the file system.

• Let the installation complete.

• During the upgrade process, all the applicable steps must be updated with a green tick mark.

• Once completed and all the steps in the Upgrade Summary are green, you can select Next.

• When you select Next and get to the below screen. Here you can close System Manager. The migration is now completed. Typically, the initial setup of the database will happen next, but in the case of a migration, this can be skipped.

• Select the X to close System Manager.

Persistent Data

The final step is to move the remaining persistent data from the Docker Container to the new install. This is a simple file copy consisting of VBScripts, Triggers, Plugins, and Report Templates.

The following is required:

• On the Docker host machine (this is the machine that is hosting the Docker container), there are a couple of folders called FastTrack on the root/c: drive.

• Copy the Plugins, Reports, and Triggers folders.

• Paste them on the new server in the following location of the WebAPI services folder. C:\Program Files (x86) \DATASCOPE\DATASCOPE WMS WebAPI

• Once copied to the new server, the Report folder must be renamed to rpt, replacing the existing rpt folder.