This section will cover the integration and technical aspects of the Configuration Option within the System Manager. This option configures the settings required for DATASCOPE WMS to function.
This option allows the configuration options for the DATASCOPE WMS to be added or edited. It is typically used on new installations or where changes are made to Databases/Servers or login credentials; otherwise, this section remains unchanged.
...
The first screen in this option looks as follows, and the integration here is mentioned below in some detail:
When the operator clicks the Next button after entering the details in the above fields, the system will validate several things and then save this information to the registry.
| Info |
|---|
Note: To view the Registry, search for Registry Editor |
...
in your Windows Explorer. |
...
The following settings are typically required:
SQL Server
...
SQL Name/IP |
...
The name or IP address where the primary SQL Server is installed. (The port number can be included in this field. If left out, the standard SWL port 1433 will be used.) |
...
SQL Username |
...
This refers to the SQL Administrator username. (This must be a dedicated user and not a general account) |
...
SQL Password |
...
This refers to the SQL Administrator password. (This will be encrypted when stored within the Registry) |
SYSPRO Server
...
SYSPRO Name/IP |
...
This might be the same as the SQL Server Name/IP address, but if it is a different server, add the correct IP address. (This is used for the communication to the SYSPRO WebServices, WCF or WCF Load Balancer) |
...
Integration |
...
Select an Integration method – WCF vs. WebServices. (This option allows the system to integrate with one of the supported platforms. Legacy WebServices or WCF. The WCF option should be used for both WCF or WCF Load Balancer) |
...
Site Name |
...
You must 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. |
...
SYSPRO Version |
...
Select the current SYSPRO version. |
...
License Type |
...
This will depend on the type of licensing. It indicates if the site is running a SYSPRO Runtime or Standard License. |
WMS Server
...
WMS Name / IP Port |
...
The server's name or IP address where DATASCOPE WMS is installed. The port must also be included, which is the port number on which the DATASCOPE WMS WebAPI will operate. |
Validation Steps
A standard PING command will be fired to the SQL Name/IP server to validate that it exists.
A standard SQL Connection will then be made to the SQL Name/IP server to validate that the SQL Username and SQL Password are correct.
A standard PING command will be fired to the SYSPRO Name/IP server to validate that it exists.
A standard PING command will be fired to the WMS Name/IP server to validate that it exists
...
.
Save Steps
Once the validation is successful, a registry entry will be created as follows:
HKEY_LOCAL_MACHING\SOFTWARE\WOW632Node\DATASCOPEWMS\
The following string entries, shown in BLUE, will be made. These are all the values entered on the above-mentioned form.
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 Single Sign-On (SSO) is required, the following Settings must be configured.
| Info |
|---|
Release 25.3 supports Single Sign-On (SSO). To use Active Directory (AD) or an Identity Provider (IdP) for SSO, make sure the required settings are configured correctly. Incorrect settings will prevent SSO login. If SSO is not required, you can leave these settings empty. The latest version of System Manager (v2.1.58) must be installed - Downloading and Installing the System Manager Agent |
An SSO Settings Information pop-up will appear. If SSO is not required, these fields can be left empty.
Ensure the SSO is captured correctly:
The user must be logged into a machine that is joined to an AD, and SYSPRO must be configured for ADSYNC. The user must be linked to the AD account.
| Info |
|---|
Note: The Azure Tenant fields required can be left blank. This is necessary for SSO using Identity Provider Integration. This is future development. |
AD Sync Username | This ADSYNC Operator or user must be configured in System Manager to sign in the Operator to the AD user. SYSPRO: The __ADSYNC service operator is used by the SYSPRO 8 Active Directory Sync Service to push Microsoft Active Directory (AD) information into SYSPRO for Active Directory managed operators. |
AD Sync Password | This is the ADSYNC Password. |
Azure Tenant ID | Enter your Azure Tenant ID. A globally unique identifier (GUID) that represents your organization's dedicated instance of Azure Active Directory (Azure AD). |
Azure Client ID | Enter your Azure Client ID. An Azure client ID, also known as an Application ID, is a unique identifier for an application registered within Azure Active Directory (Azure AD). |
Azure Client Secret | Enter your Azure Client Secret. A confidential string used to authenticate an application when it requests an access token from the Azure AD authorization service. |
Redirect URI | A redirect URI, or reply URL, is the location where the Microsoft Entra authentication server redirects the user after they successfully authorize and receive an access token. To sign in a user, your application must send a login request with a redirect URI parameter. After the user successfully signs in, the authentication server will redirect the user to the redirect URI specified in the login request and issue an access token. |
Scope | Microsoft.Identity.Client (MSAL.NET), scopes define the specific permissions or access levels that your application requests when acquiring an access token from the Microsoft identity platform (such as Microsoft Entra ID, formerly Azure AD) |
Authority URL | This will refer to the Microsoft login URL - https://login.microsoftonline.com |
| Info |
|---|
For more information on where to find your Azure Tenant ID, Azure Client ID, and Secret, refer to the official Microsoft Azure documentation. |
The next screen in this option appears as follows, and the integration is described in more detail below. This refers to the linked databases.
When this screen is loaded, a query is made to the following database table to obtain a list of the SYSPRO Companies that are set up.
Database Name | Sysprodb |
Table Name | SysproAdmin |
If the standard Sysprodb does not exist, the operator will be asked to specify it. When this happens, a query is made as follows.
Database Name | master |
Table Name | sysdatabases |
When selecting Next, the next SYSPRO Company Databases can be configured.
The option also exists to create a third and fourth SYSPRO company.
Once the list of SYSPRO Companies has been obtained, the operator can loop through each company and configure the SYSPRO and WMS Databases, respectively. Each drop-down will be loaded by querying the following:
Database Name | master |
Table Name | sysdatabases |
Once the operator moves to the next company, the following entries will be added to the registry:
HKEY_LOCAL_MACHING\SOFTWARE\WOW632Node\DATASCOPEWMS\
The following entries in BLUE will be added/updated.
| Info |
|---|
NOTE: Each company will have the entries prefixed with the SYSPRO Company Letter in this case TMS_ |
Once completed, System Manager will revert to the menu screen.
