Files & Folder Location
The Nathean Analytics services should be deployed to the “Clientfolder” on the Store’s server. This is usually located on D:
Create a “Logix” folder there. For this document, the location of the folder is assumed to be:
D:\Clientfolder\Logix
This will be referred to as the “Nathean Analytics folder”.
Download the LogixScheduleServiceFullDeploy.zip file to the Nathean Analytics folder. Unzip the file.
You should have the following folder structure:

Create Nathean Analytics SQL Database User on the remote server

Open SQL Server Management Studio. (SSMS)
Sign into as an SQL administrator user
Set and record the password and run this SQL

USE MASTER
GO
CREATE LOGIN LGX_AGENT WITH PASSWORD = ‘PASSWORD’;
USE DATA_MART

CREATE USER LGX_AGENT FOR LOGIN LGX_AGENT
WITH DEFAULT_SCHEMA = DBO;

EXEC sp_addrolemember N’db_datareader’, N’LGX_AGENT’;

GRANT EXECUTE ON SCHEMA :: DBO TO LGX_AGENT;

Site IP address. We require a fixed public IP address in Azure to lock the site to the the central Azure instance.

If using a fixed pubic IP address from the source site the following step is not required and can be achieved in other ways. This is one approach and we’ve used DynDns to solve this issue.

Add Site to Nathean Analytics as new data connector

Go to the DataConnector of the site you are installing to and enter the DynDns URL into the “Public Domain Name” field.

If the server is using a Fixed IP, enter that value into the ”Public IP Address” field.

After adding or editing either the “Public IP Address” or “Public Domain Name” fields, you need to refresh the object which is set up for pushing changes to Azure firewall.

Add New Site to Nathean Analytics & Schedule Job Refresh

Click the “Edit” button to edit the multisource data connection.
Place a check in the box beside the store you are deploying to. If you plan to deploy to multiple sites on the same day, you can add these in at this time also. There’s no harm in adding in a site that hasn’t been deployed to yet. However, it’s harder to troubleshoot issues if there are a lot of stores in this list that do not have the scheduler installed. A couple extra won’t matter too much.

Modify Nathean Schedule Service Configuration File

Each site has a unique “ConnectionID”. You can also see the ID in the Data Connector page in Nathean Analytics and
MultiSourceMode =“RemoteScheduler”.

Edit the “D:\Clientfolder\Logix\LogixScheduler\LogixScheduleService.exe.config” file and set the “MultiSourceRemoteConnectionID” key to the ConnectionID from the document:

Deploy Nathean Schedule Service

Troubleshooting

Ensure Local Username is correct.
If you cannot resolve the issue, email support@nathean.com with the details from the Event Viewer or the CMD window.

Enable Logging
To enable Trace Logging, edit the LogixScheduleService.exe.config file located in the Scheduler folder. Usually D:\Clientfolder\Logix\LogixScheduleService
Nathean Schedule Service needs to be restarted once logging is enabled.The “trace.log” file will be in the Logs directory.
Switch off logging by commenting out the line again once issue has been resolved.

Revision: 4
Last modified: Jun 22, 2020

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment