How to register the ETL Server data movement service
Hi,
I have an Insight installation with a Report Server and an ETL Server. I chose these options in the Instalation Manager when I installed the ETL Server :
http://i55.tinypic.com/a0hsg9.png
The question is what do I have to do to register the ETL server dispatcher in the Content Manager so then I can disable the data movement service in the Report Server to run the Data Manager Jobs in the ETL Server.
The Cognos Configuration Environment in the ETL server shows these options:
http://i53.tinypic.com/k99g94.png
I wonder if it shouldn't have an External dispatcher URI property in the ETL Server configuration so I could type an URI that allows the ETL Server receive requests from remote servers.
Thank you very much,
Paulo
I have an Insight installation with a Report Server and an ETL Server. I chose these options in the Instalation Manager when I installed the ETL Server :
The question is what do I have to do to register the ETL server dispatcher in the Content Manager so then I can disable the data movement service in the Report Server to run the Data Manager Jobs in the ETL Server.
The Cognos Configuration Environment in the ETL server shows these options:
I wonder if it shouldn't have an External dispatcher URI property in the ETL Server configuration so I could type an URI that allows the ETL Server receive requests from remote servers.
Thank you very much,
Paulo
One answer
Hi Paulo,
When installing an ETL standalone server, you need to include the "Report Server" component in the install. You need this "Report Server" (BI server) component for the ETL server to work as you will use it strictly as a scheduling engine.
The ETL server is just like the regular Report server. The only difference is that you will direct your users to the regular "Report Server" and all of the ETL jobs will be handled by the Data Manager movement service of the BI Server (standalone ETL server).
If you want the dev machines to "publish" their jobs to the ETL machine, they need to change the change the dispatcher settings on the local dev machine to point to the ETL server.
Hope this helps.
-Marc Nehme
When installing an ETL standalone server, you need to include the "Report Server" component in the install. You need this "Report Server" (BI server) component for the ETL server to work as you will use it strictly as a scheduling engine.
The ETL server is just like the regular Report server. The only difference is that you will direct your users to the regular "Report Server" and all of the ETL jobs will be handled by the Data Manager movement service of the BI Server (standalone ETL server).
If you want the dev machines to "publish" their jobs to the ETL machine, they need to change the change the dispatcher settings on the local dev machine to point to the ETL server.
Hope this helps.
-Marc Nehme