Hi Ashutosh,

A connection instance is not just associated with one job -- these are pooled and are checked out as needed by whatever code needs a connection instance.  It's not part of the general contract of connection instances that they be associated with specific jobs.  The API structure reflects this.

Access to a job's data for the purposes of modifying how a connector behaves is also a great way to build a connector that will not work properly.  I highly discourage this.

There is access to job information that is appropriate for a connector to see, but it comes in via the I*Activity interface instances that are passed to specific methods implemented by the connector.  These do not include access to the job ID, however.


On Thu, Jun 16, 2016 at 8:26 AM, <ashutosh.rai@wipro.com> wrote:



Is there a way to get the id of the job that a particular connector instance is invoked under? Either via the thread context or some other mechanism?


I looked through the code but I was not able find anything to tie the two together.


Request your inputs/advice on this.







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