On-prem ETL+ Preinstallation Checklist DRAFT
KB pages to refer to clients to install ETL+ in various situations. Asked for by Lori.
on-prem preinstallation information checklist to assist DS technical support with on-premises/(on-prem) installations. Designed to be emailed to clients.
Most recent version: On-prem ETL+ Preinstallation Checklist - Combined/DRAFT
Various situations described in Generic ETL Install: Elements
Pages in this section
KB Planning Page: On-Premises Installation - KB Project Plan
search words: onprem, on premise, onpremise, preinstall, pre-installation, checklist, form,
Overall Remit
Cortlandt,
Will you help finish the KB pages that we should send to clients who want to:
Install ETL+ onprem for a local Source
And another section if they also have onprem DW
A diff page for those who just want a local ETL+ that isn’t the one that is on a DW server. (see below)
As I see it:
They need to be as simple as possible, with only maybe a few links at the bottom to other pages re weird exceptions.
And have a clear, early, list of requirements in each section. Since our experience is that the IT won’t read it anyway, but the list of requirements might catch their attention so that they are prepared before they start working with Peter. And our folk can copy those requirement lists into an email that there is higher chance of catching their attention.
FROM Peter
These are the steps of a generic ETL install on a client's computer. As opposed to an first time ETL Install on a client's server which will create the refresh process.
Find out the client's IP address. Best if it's a Static IP, if it's not the client should be told that the ETL will stop working when their IP changes.
Download the .msi file from https://kb.dataself.com/ds/dataself-etl-release-history-download-links on the client's computer.
Run the .msi file as Administrator, in this process an option will come up to install the Agent, click the Confirm button.
In this process a series of Wizard screens will come up, keep clicking Next on each screen, till the final screen where you click Close.
Have the client click log into the ETL, they should enter their email for the Login and tab off the Login field, then the client will be prompted to create a password, and then they can log in.
Once logged in, go to the Job page and make sure the right App is picked, it should be the Agent from the server which runs the refresh. If there are many Jobs, you may have to set the App up for each one, or all the Jobs may already be set properly. For example:
App = Agent or WTS