You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@manifoldcf.apache.org by Karl Wright <da...@gmail.com> on 2016/05/25 16:20:25 UTC
Re: Correct way to provide static config data to a connector
Hi Ashutosh,
We don't usually recommend configuring anything via files, because in a
multi-process cluster there's no guarantee that those files will be
present. In addition, connection-specific configuration should generally
be done using the UI with the standard connector mechanisms provided, so
that we can track changes etc.
If you have a number of parameters that are *not* connection specific, you
can put these into properties.xml or global-properties.xml. The latter is
cross-cluster-member, and the latter is specific to each cluster process
and is intended to be individual.
If you have other data that just hard-wired, then yes, you will probably do
best building it into your connector jar as a resource.
Karl
On Wed, May 25, 2016 at 12:02 PM, <as...@wipro.com> wrote:
>
>
> Hello,
>
>
>
> I want to provide some static configuration data to my connector through a
> property/xml file.
>
>
>
> As I understand, this can be achieved by: a) bundling the property/xml
> file into the connector jar and reading it in the connector or, b) placing
> the property/xml file in the file-resources folder and loading the
> properties file in the connector
>
>
>
> Am I on the right track? Is this the correct way to use file-resources or
> should I look at a different approach?
>
>
>
> Pls note that I only have key value pair type static data.
>
>
>
> Regards
>
> -Ashutosh Rai
>
>
>
>
>
>
>
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
>
RE: Correct way to provide static config data to a connector
Posted by as...@wipro.com.
Okay. Thanks Karl.
Will explore it and revert if I need any further clarification.
Regards
-Ashutosh Rai
From: Karl Wright<ma...@gmail.com>
Sent: 25 May 2016 18:01
To: Ashutosh Rai (Securities)<ma...@wipro.com>
Cc: user@manifoldcf.apache.org<ma...@manifoldcf.apache.org>
Subject: Re: Correct way to provide static config data to a connector
** This mail has been sent from an external source **
Hi Ashutosh,
I would then use global properties for this.
Karl
On Wed, May 25, 2016 at 12:43 PM, <as...@wipro.com>> wrote:
Hi Karl,
Thanks for the reply.
The properties I am referring to are static across a cluster/within an environment.
The properties might be *connector* specific but will be common across all connection instances - e.g. All sharepoint repository connectors share the same value for the property but all documentum connectors will share a different value.
Would it be okay to use properties.xml or global-properties.xml for such cases as well?
Bundling the property file with the jar is not an option as the properties will change between environments (e.g.: Dev instances will carry a different set from uat and uat will carry a different set from prod).
Regards
-Ashutosh Rai
From: Karl Wright<ma...@gmail.com>
Sent: 25 May 2016 17:20
To: user@manifoldcf.apache.org<ma...@manifoldcf.apache.org>
Subject: Re: Correct way to provide static config data to a connector
** This mail has been sent from an external source **
Hi Ashutosh,
We don't usually recommend configuring anything via files, because in a multi-process cluster there's no guarantee that those files will be present. In addition, connection-specific configuration should generally be done using the UI with the standard connector mechanisms provided, so that we can track changes etc.
If you have a number of parameters that are *not* connection specific, you can put these into properties.xml or global-properties.xml. The latter is cross-cluster-member, and the latter is specific to each cluster process and is intended to be individual.
If you have other data that just hard-wired, then yes, you will probably do best building it into your connector jar as a resource.
Karl
On Wed, May 25, 2016 at 12:02 PM, <as...@wipro.com>> wrote:
Hello,
I want to provide some static configuration data to my connector through a property/xml file.
As I understand, this can be achieved by: a) bundling the property/xml file into the connector jar and reading it in the connector or, b) placing the property/xml file in the file-resources folder and loading the properties file in the connector
Am I on the right track? Is this the correct way to use file-resources or should I look at a different approach?
Pls note that I only have key value pair type static data.
Regards
-Ashutosh Rai
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
Re: Correct way to provide static config data to a connector
Posted by Karl Wright <da...@gmail.com>.
Hi Ashutosh,
I would then use global properties for this.
Karl
On Wed, May 25, 2016 at 12:43 PM, <as...@wipro.com> wrote:
> Hi Karl,
>
>
>
> Thanks for the reply.
>
>
>
> The properties I am referring to are static across a cluster/within an
> environment.
>
>
>
> The properties might be *connector* specific but will be common across all
> connection instances – e.g. All sharepoint repository connectors share the
> same value for the property but all documentum connectors will share a
> different value.
>
>
>
> Would it be okay to use properties.xml or global-properties.xml for such
> cases as well?
>
>
>
> Bundling the property file with the jar is not an option as the properties
> will change between environments (e.g.: Dev instances will carry a
> different set from uat and uat will carry a different set from prod).
>
>
>
> Regards
>
> -Ashutosh Rai
>
>
>
>
>
>
>
>
>
> *From: *Karl Wright <da...@gmail.com>
> *Sent: *25 May 2016 17:20
> *To: *user@manifoldcf.apache.org
> *Subject: *Re: Correct way to provide static config data to a connector
>
>
>
> ** This mail has been sent from an external source **
> Hi Ashutosh,
>
> We don't usually recommend configuring anything via files, because in a
> multi-process cluster there's no guarantee that those files will be
> present. In addition, connection-specific configuration should generally
> be done using the UI with the standard connector mechanisms provided, so
> that we can track changes etc.
>
> If you have a number of parameters that are *not* connection specific, you
> can put these into properties.xml or global-properties.xml. The latter is
> cross-cluster-member, and the latter is specific to each cluster process
> and is intended to be individual.
>
> If you have other data that just hard-wired, then yes, you will probably
> do best building it into your connector jar as a resource.
>
> Karl
>
>
> On Wed, May 25, 2016 at 12:02 PM, <as...@wipro.com> wrote:
>
>>
>>
>> Hello,
>>
>>
>>
>> I want to provide some static configuration data to my connector through
>> a property/xml file.
>>
>>
>>
>> As I understand, this can be achieved by: a) bundling the property/xml
>> file into the connector jar and reading it in the connector or, b) placing
>> the property/xml file in the file-resources folder and loading the
>> properties file in the connector
>>
>>
>>
>> Am I on the right track? Is this the correct way to use file-resources or
>> should I look at a different approach?
>>
>>
>>
>> Pls note that I only have key value pair type static data.
>>
>>
>>
>> Regards
>>
>> -Ashutosh Rai
>>
>>
>>
>>
>>
>>
>>
>>
>> The information contained in this electronic message and any attachments
>> to this message are intended for the exclusive use of the addressee(s) and
>> may contain proprietary, confidential or privileged information. If you are
>> not the intended recipient, you should not disseminate, distribute or copy
>> this e-mail. Please notify the sender immediately and destroy all copies of
>> this message and any attachments. WARNING: Computer viruses can be
>> transmitted via email. The recipient should check this email and any
>> attachments for the presence of viruses. The company accepts no liability
>> for any damage caused by any virus transmitted by this email.
>> www.wipro.com
>>
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> www.wipro.com
>
RE: Correct way to provide static config data to a connector
Posted by as...@wipro.com.
Hi Karl,
Thanks for the reply.
The properties I am referring to are static across a cluster/within an environment.
The properties might be *connector* specific but will be common across all connection instances – e.g. All sharepoint repository connectors share the same value for the property but all documentum connectors will share a different value.
Would it be okay to use properties.xml or global-properties.xml for such cases as well?
Bundling the property file with the jar is not an option as the properties will change between environments (e.g.: Dev instances will carry a different set from uat and uat will carry a different set from prod).
Regards
-Ashutosh Rai
From: Karl Wright<ma...@gmail.com>
Sent: 25 May 2016 17:20
To: user@manifoldcf.apache.org<ma...@manifoldcf.apache.org>
Subject: Re: Correct way to provide static config data to a connector
** This mail has been sent from an external source **
Hi Ashutosh,
We don't usually recommend configuring anything via files, because in a multi-process cluster there's no guarantee that those files will be present. In addition, connection-specific configuration should generally be done using the UI with the standard connector mechanisms provided, so that we can track changes etc.
If you have a number of parameters that are *not* connection specific, you can put these into properties.xml or global-properties.xml. The latter is cross-cluster-member, and the latter is specific to each cluster process and is intended to be individual.
If you have other data that just hard-wired, then yes, you will probably do best building it into your connector jar as a resource.
Karl
On Wed, May 25, 2016 at 12:02 PM, <as...@wipro.com>> wrote:
Hello,
I want to provide some static configuration data to my connector through a property/xml file.
As I understand, this can be achieved by: a) bundling the property/xml file into the connector jar and reading it in the connector or, b) placing the property/xml file in the file-resources folder and loading the properties file in the connector
Am I on the right track? Is this the correct way to use file-resources or should I look at a different approach?
Pls note that I only have key value pair type static data.
Regards
-Ashutosh Rai
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com