Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------

Find more posts tagged with

English

Monarch

Accepted answers

All comments

Dylan_20833

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200
------------------------------
-------------------------------------------
Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Rebekah

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200
------------------------------
-------------------------------------------
Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
-------------------------------------------
Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200
------------------------------

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Dylan_20833

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
-------------------------------------------
Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200
------------------------------

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200
------------------------------
-------------------------------------------
Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Rebekah

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200
------------------------------
-------------------------------------------
Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
-------------------------------------------
Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200
------------------------------

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Mo Abdolrahim

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
-------------------------------------------
Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200
------------------------------

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Hi Rebekah,
The ODBC that you created on your PC should also exist on the Automator server with the same name, but does not have to have the same account.
The preferred way to connect to a database is using windows authentication (or trusted connection).
For example you will ask the DBA to add your domain account to the database server as well as the Automator service account (all Automator processes run under the Automator service account). You create an ODBC connection on your PC using the trusted connection (per screenshot below)

Ask the Automator administrator to create an ODBC connection on the Automator server with the same ODBC name that you created on your PC with trusted connection. When you run your process in the Automator, the process connects to the database server with trusted connection using the same ODBC connection.
If you connect to the database server using an ODBC connection with a username and password, then ensure that the "Save login credentials in projects" is set to always in the Monarch classic options (per screenshot below):

The ODBC name on your PC should match the ODBC name on the Automator server, however, the account does not need to match.
For example, if you create an ODBC on your pc with username Rebekah and some password, and the ODBC on the server has a different username and password, as long as the credential is saved in the project file, then the Automator process can use the ODBC on the server with your credential.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840
------------------------------
-------------------------------------------
Original Message:
Sent: 05-23-2019 07:13 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------

Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Rebekah

Hi Rebekah,
The ODBC that you created on your PC should also exist on the Automator server with the same name, but does not have to have the same account.
The preferred way to connect to a database is using windows authentication (or trusted connection).
For example you will ask the DBA to add your domain account to the database server as well as the Automator service account (all Automator processes run under the Automator service account). You create an ODBC connection on your PC using the trusted connection (per screenshot below)
Ask the Automator administrator to create an ODBC connection on the Automator server with the same ODBC name that you created on your PC with trusted connection. When you run your process in the Automator, the process connects to the database server with trusted connection using the same ODBC connection.
If you connect to the database server using an ODBC connection with a username and password, then ensure that the "Save login credentials in projects" is set to always in the Monarch classic options (per screenshot below):
The ODBC name on your PC should match the ODBC name on the Automator server, however, the account does not need to match.
For example, if you create an ODBC on your pc with username Rebekah and some password, and the ODBC on the server has a different username and password, as long as the credential is saved in the project file, then the Automator process can use the ODBC on the server with your credential.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840
------------------------------
-------------------------------------------
Original Message:
Sent: 05-23-2019 07:13 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------

Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Thank you, Mo - I wasn't clear. The ODBC connection does have the same name, but the user name and password differ on the server. I will ask our IT staff about using the Windows Authentication method. If they will allow it, I will definitely give that a try. And I hesitate to use my user name and password for the ODBC connection to core, as my PW expires every 90 days. The password that we utilize on our old DataPump server is set to never expire, so we would like to replicate that in the new environment on the Automator server. Since people sometimes move on, it is probably best to avoid using actual user names and passwords to run processes or establish connections.
Thanks much,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
-------------------------------------------
Original Message:
Sent: 05-24-2019 08:56 AM
From: Mahmoud Abdolrahim
Subject: ODBC Connectivity

Hi Rebekah,
The ODBC that you created on your PC should also exist on the Automator server with the same name, but does not have to have the same account.
The preferred way to connect to a database is using windows authentication (or trusted connection).
For example you will ask the DBA to add your domain account to the database server as well as the Automator service account (all Automator processes run under the Automator service account). You create an ODBC connection on your PC using the trusted connection (per screenshot below)

The ODBC name on your PC should match the ODBC name on the Automator server, however, the account does not need to match.
For example, if you create an ODBC on your pc with username Rebekah and some password, and the ODBC on the server has a different username and password, as long as the credential is saved in the project file, then the Automator process can use the ODBC on the server with your credential.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840
------------------------------

Original Message:
Sent: 05-23-2019 07:13 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Rebekah

Hi Rebekah,
The ODBC that you created on your PC should also exist on the Automator server with the same name, but does not have to have the same account.
The preferred way to connect to a database is using windows authentication (or trusted connection).
For example you will ask the DBA to add your domain account to the database server as well as the Automator service account (all Automator processes run under the Automator service account). You create an ODBC connection on your PC using the trusted connection (per screenshot below)
Ask the Automator administrator to create an ODBC connection on the Automator server with the same ODBC name that you created on your PC with trusted connection. When you run your process in the Automator, the process connects to the database server with trusted connection using the same ODBC connection.
If you connect to the database server using an ODBC connection with a username and password, then ensure that the "Save login credentials in projects" is set to always in the Monarch classic options (per screenshot below):
The ODBC name on your PC should match the ODBC name on the Automator server, however, the account does not need to match.
For example, if you create an ODBC on your pc with username Rebekah and some password, and the ODBC on the server has a different username and password, as long as the credential is saved in the project file, then the Automator process can use the ODBC on the server with your credential.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840
------------------------------
-------------------------------------------
Original Message:
Sent: 05-23-2019 07:13 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------

Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Hi Mo,
Quick question related to this - is there a way to reverse this and create a model with the server name and PW embedded in the project rather than my user name and PW? The server PW is configured to be persistent, so expiration is not an issue.
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
-------------------------------------------
Original Message:
Sent: 05-24-2019 08:56 AM
From: Mahmoud Abdolrahim
Subject: ODBC Connectivity

Hi Rebekah,
The ODBC that you created on your PC should also exist on the Automator server with the same name, but does not have to have the same account.
The preferred way to connect to a database is using windows authentication (or trusted connection).
For example you will ask the DBA to add your domain account to the database server as well as the Automator service account (all Automator processes run under the Automator service account). You create an ODBC connection on your PC using the trusted connection (per screenshot below)

The ODBC name on your PC should match the ODBC name on the Automator server, however, the account does not need to match.
For example, if you create an ODBC on your pc with username Rebekah and some password, and the ODBC on the server has a different username and password, as long as the credential is saved in the project file, then the Automator process can use the ODBC on the server with your credential.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840
------------------------------

Original Message:
Sent: 05-23-2019 07:13 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Rebekah

Hi Mo,
Quick question related to this - is there a way to reverse this and create a model with the server name and PW embedded in the project rather than my user name and PW? The server PW is configured to be persistent, so expiration is not an issue.
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
-------------------------------------------
Original Message:
Sent: 05-24-2019 08:56 AM
From: Mahmoud Abdolrahim
Subject: ODBC Connectivity

Hi Rebekah,
The ODBC that you created on your PC should also exist on the Automator server with the same name, but does not have to have the same account.
The preferred way to connect to a database is using windows authentication (or trusted connection).
For example you will ask the DBA to add your domain account to the database server as well as the Automator service account (all Automator processes run under the Automator service account). You create an ODBC connection on your PC using the trusted connection (per screenshot below)
Ask the Automator administrator to create an ODBC connection on the Automator server with the same ODBC name that you created on your PC with trusted connection. When you run your process in the Automator, the process connects to the database server with trusted connection using the same ODBC connection.
If you connect to the database server using an ODBC connection with a username and password, then ensure that the "Save login credentials in projects" is set to always in the Monarch classic options (per screenshot below):
The ODBC name on your PC should match the ODBC name on the Automator server, however, the account does not need to match.
For example, if you create an ODBC on your pc with username Rebekah and some password, and the ODBC on the server has a different username and password, as long as the credential is saved in the project file, then the Automator process can use the ODBC on the server with your credential.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840
------------------------------

Original Message:
Sent: 05-23-2019 07:13 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

One more question - do I need to add my user name and password in the connection definitions in Automator?
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
-------------------------------------------
Original Message:
Sent: 05-29-2019 06:09 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Mo,
Quick question related to this - is there a way to reverse this and create a model with the server name and PW embedded in the project rather than my user name and PW? The server PW is configured to be persistent, so expiration is not an issue.
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------

Original Message:
Sent: 05-24-2019 08:56 AM
From: Mahmoud Abdolrahim
Subject: ODBC Connectivity

Hi Rebekah,
The ODBC that you created on your PC should also exist on the Automator server with the same name, but does not have to have the same account.
The preferred way to connect to a database is using windows authentication (or trusted connection).
For example you will ask the DBA to add your domain account to the database server as well as the Automator service account (all Automator processes run under the Automator service account). You create an ODBC connection on your PC using the trusted connection (per screenshot below)

The ODBC name on your PC should match the ODBC name on the Automator server, however, the account does not need to match.
For example, if you create an ODBC on your pc with username Rebekah and some password, and the ODBC on the server has a different username and password, as long as the credential is saved in the project file, then the Automator process can use the ODBC on the server with your credential.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840

Original Message:
Sent: 05-23-2019 07:13 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Mo Abdolrahim

One more question - do I need to add my user name and password in the connection definitions in Automator?
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
-------------------------------------------
Original Message:
Sent: 05-29-2019 06:09 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Mo,
Quick question related to this - is there a way to reverse this and create a model with the server name and PW embedded in the project rather than my user name and PW? The server PW is configured to be persistent, so expiration is not an issue.
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------

Original Message:
Sent: 05-24-2019 08:56 AM
From: Mahmoud Abdolrahim
Subject: ODBC Connectivity

Hi Rebekah,
The ODBC that you created on your PC should also exist on the Automator server with the same name, but does not have to have the same account.
The preferred way to connect to a database is using windows authentication (or trusted connection).
For example you will ask the DBA to add your domain account to the database server as well as the Automator service account (all Automator processes run under the Automator service account). You create an ODBC connection on your PC using the trusted connection (per screenshot below)
Ask the Automator administrator to create an ODBC connection on the Automator server with the same ODBC name that you created on your PC with trusted connection. When you run your process in the Automator, the process connects to the database server with trusted connection using the same ODBC connection.
If you connect to the database server using an ODBC connection with a username and password, then ensure that the "Save login credentials in projects" is set to always in the Monarch classic options (per screenshot below):
The ODBC name on your PC should match the ODBC name on the Automator server, however, the account does not need to match.
For example, if you create an ODBC on your pc with username Rebekah and some password, and the ODBC on the server has a different username and password, as long as the credential is saved in the project file, then the Automator process can use the ODBC on the server with your credential.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840

Original Message:
Sent: 05-23-2019 07:13 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Hi Rebekah,
You can add a connection definition with either your username and password, or upload the Monarch project to the Automator.
Edit the project it the project editor. In the project editor, in the input tab modify the database configuration and provide a your username and password, or select the previously configured a connection definition.

Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840
------------------------------
-------------------------------------------
Original Message:
Sent: 05-29-2019 07:16 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

One more question - do I need to add my user name and password in the connection definitions in Automator?
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------

Original Message:
Sent: 05-29-2019 06:09 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Mo,
Quick question related to this - is there a way to reverse this and create a model with the server name and PW embedded in the project rather than my user name and PW? The server PW is configured to be persistent, so expiration is not an issue.
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 05-24-2019 08:56 AM
From: Mahmoud Abdolrahim
Subject: ODBC Connectivity

Hi Rebekah,
The ODBC that you created on your PC should also exist on the Automator server with the same name, but does not have to have the same account.
The preferred way to connect to a database is using windows authentication (or trusted connection).
For example you will ask the DBA to add your domain account to the database server as well as the Automator service account (all Automator processes run under the Automator service account). You create an ODBC connection on your PC using the trusted connection (per screenshot below)

The ODBC name on your PC should match the ODBC name on the Automator server, however, the account does not need to match.
For example, if you create an ODBC on your pc with username Rebekah and some password, and the ODBC on the server has a different username and password, as long as the credential is saved in the project file, then the Automator process can use the ODBC on the server with your credential.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840

Original Message:
Sent: 05-23-2019 07:13 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Mo Abdolrahim

Hi Rebekah,
You can add a connection definition with either your username and password, or upload the Monarch project to the Automator.
Edit the project it the project editor. In the project editor, in the input tab modify the database configuration and provide a your username and password, or select the previously configured a connection definition.

Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840
------------------------------
-------------------------------------------
Original Message:
Sent: 05-29-2019 07:16 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

One more question - do I need to add my user name and password in the connection definitions in Automator?
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------

Original Message:
Sent: 05-29-2019 06:09 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Mo,
Quick question related to this - is there a way to reverse this and create a model with the server name and PW embedded in the project rather than my user name and PW? The server PW is configured to be persistent, so expiration is not an issue.
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 05-24-2019 08:56 AM
From: Mahmoud Abdolrahim
Subject: ODBC Connectivity

Hi Rebekah,
The ODBC that you created on your PC should also exist on the Automator server with the same name, but does not have to have the same account.
The preferred way to connect to a database is using windows authentication (or trusted connection).
For example you will ask the DBA to add your domain account to the database server as well as the Automator service account (all Automator processes run under the Automator service account). You create an ODBC connection on your PC using the trusted connection (per screenshot below)
Ask the Automator administrator to create an ODBC connection on the Automator server with the same ODBC name that you created on your PC with trusted connection. When you run your process in the Automator, the process connects to the database server with trusted connection using the same ODBC connection.
If you connect to the database server using an ODBC connection with a username and password, then ensure that the "Save login credentials in projects" is set to always in the Monarch classic options (per screenshot below):
The ODBC name on your PC should match the ODBC name on the Automator server, however, the account does not need to match.
For example, if you create an ODBC on your pc with username Rebekah and some password, and the ODBC on the server has a different username and password, as long as the credential is saved in the project file, then the Automator process can use the ODBC on the server with your credential.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840

Original Message:
Sent: 05-23-2019 07:13 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"

Hi Rebekah,
Yes you do need to add your username and password when you create an ODBC connection definition and the trusted connection is false.
In the screenshot below the DNS name (DemoDB-ODBC-SQLAuth) must already exist on the Automator server.

You can create an Automator project (or upload a Monarch project in server library, and edit it) and configure the input tab to use database and use the connection definition.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840
------------------------------
-------------------------------------------
Original Message:
Sent: 05-31-2019 08:36 AM
From: Mahmoud Abdolrahim
Subject: ODBC Connectivity

Hi Rebekah,
You can add a connection definition with either your username and password, or upload the Monarch project to the Automator.
Edit the project it the project editor. In the project editor, in the input tab modify the database configuration and provide a your username and password, or select the previously configured a connection definition.

Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840
------------------------------

Original Message:
Sent: 05-29-2019 07:16 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

One more question - do I need to add my user name and password in the connection definitions in Automator?
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 05-29-2019 06:09 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Mo,
Quick question related to this - is there a way to reverse this and create a model with the server name and PW embedded in the project rather than my user name and PW? The server PW is configured to be persistent, so expiration is not an issue.
Thanks!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 05-24-2019 08:56 AM
From: Mahmoud Abdolrahim
Subject: ODBC Connectivity

Hi Rebekah,
The ODBC that you created on your PC should also exist on the Automator server with the same name, but does not have to have the same account.
The preferred way to connect to a database is using windows authentication (or trusted connection).
For example you will ask the DBA to add your domain account to the database server as well as the Automator service account (all Automator processes run under the Automator service account). You create an ODBC connection on your PC using the trusted connection (per screenshot below)

The ODBC name on your PC should match the ODBC name on the Automator server, however, the account does not need to match.
For example, if you create an ODBC on your pc with username Rebekah and some password, and the ODBC on the server has a different username and password, as long as the credential is saved in the project file, then the Automator process can use the ODBC on the server with your credential.
Regards
Mo

------------------------------
Mahmoud Abdolrahim
Senior Implementation & Integration Engineer
Datawatch Corporation
MA
(978) 935-3840

Original Message:
Sent: 05-23-2019 07:13 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Adding to my original question - what is the best way to create a model that has password protected ODBC connectivity when it is being created to run on Automator? Because models are not portable from user to user once those credentials are established pending a fix in the summer release, do I need to create the model on the server in order to establish the ODBC?
I have always created models on my workstation and then promoted them to the DataPump server, where I could open and update the model through the DataPump interface, but Automator doesn't have that same capability. It would be helpful to know if anyone is running a model with password protected ODBC connectivity via Automator and how they went about establishing that.
Thank you!
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 04:06 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

If there is a fix so this operates in Classic v14 the way it did in v10.5, I'm sure we'll get that response on your ticket. However, I can tell you that I know Data Prep Studio will save the ODBC connection in a workspace file. Since you are licensed for Monarch Complete (Data Prep Studio + Classic), we can show you how to do this if you like. I will send you an e-mail.

Best,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-26-2019 02:14 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

Hi Dylan,
We are using Classic. A support ticket has been opened (ID 53034).
Thank you,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)

Original Message:
Sent: 04-26-2019 02:03 PM
From: Dylan Tancill
Subject: ODBC Connectivity

Hi Rebekah,

Are you doing this in Monarch Classic or Data Prep Studio within v14?

Thanks,
Dylan

------------------------------
Dylan Tancill
Outside Sales Account Manager
Datawatch Corporation
Bedford MA
(978) 441-2200

Original Message:
Sent: 04-25-2019 07:01 PM
From: Rebekah Tyrrell
Subject: ODBC Connectivity

We sometimes share models among our users, and we are encountering an issue with models that utilize an ODBC connection to our core system. In Monarch 10.5 we would receive a prompt for a user name/password, but now it seems that we need to recreate the ODBC connection for each user who utilizes that model (now we are saving the models with the user's name in the model name). If someone opened a model with an ODBC connection set up by another user, they would immediately receive an error, and the person who initially created the model would then be locked out of the core system. Has anyone run into this? Any tips/tricks that you are using to address this?
Is there a place in Monarch 14 where we can either specify "prompt for user name/password" and/or set it to allow for additional PW attempts prior to locking a user out?
Thanks,
Rebekah

------------------------------
Rebekah
Operational Risk Analyst
Exchange Bank (CA)
------------------------------
"