manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <daddy...@gmail.com>
Subject Re: Get Repository connection on Job Save.
Date Mon, 05 May 2014 11:58:50 GMT
Hi Pankaj,

Other folks have done something similar.  The typical way to do it seems to
be the following:

(1) Extend the SolrConnector class, and override the pertinent methods to
modify the database as well.
(2) Register your new class as a different connector type, e.g.
"DatabaseSolr"
(3) Add a method to your extended SolrConnector class which copies from the
database into Solr (in case the client wants to do that).  Hook that up to
the requestInfo() method invocation, and then you can call it via the REST
API, and all the right environment, handles, etc. should be all set for you
to use.

There are plenty of other ways to do this, including making it the
responsibility of the Solr side to record the info to your database, but I
think this is the fastest/easiest.

Karl



On Mon, May 5, 2014 at 7:39 AM, <pankaj.pandey4@wipro.com> wrote:

>  Hi Karl,
>
>
>
> Thanks for your quick response!
>
>
>
> I am working on a POC where customer wants the data pushed to Solr to be
> pushed to a database as well. For this, on save of the job, I want to get
> the newly selected attributes, their names, their labels and their
> data-types(int, float, date etc) from DCTM repository and send it to
> another application for type table creation. Then, when a document is
> pushed via RestAPI to Solr, I will also be pushing that to that another
> application. Seems like, they want to have a search repository on Solr, but
> in case for some reason if they have to re-build the index, they would do
> it from database, instead of Documentum Repository. There might be other
> reasons as well, but this is one of them, that came in the discussion.
>
>
>
>
>
> Thanks!
>
>
>
> Regards,
>
> Pankaj Pandey
>
>
>
>
>
> *From:* Karl Wright [mailto:daddywri@gmail.com]
> *Sent:* Monday, May 05, 2014 4:53 PM
> *To:* user@manifoldcf.apache.org
> *Subject:* Re: Get Repository connection on Job Save.
>
>
>
> Hi Pankaj,
>
> This is not a supported model for using ManifoldCF, and it sounds like you
> are digging a pretty deep hole here.  Can you back up and explain what your
> requirements are and why you feel you need take this approach?
>
> Karl
>
>
>
> On Mon, May 5, 2014 at 7:11 AM, <pankaj.pandey4@wipro.com> wrote:
>
> Hi,
>
>
>
> I am working on customizing the ManifoldCF job with Documentum Repository
> connection and Solr Output connection. After selecting the various job
> parameters(such as Document Types, Paths, Content Types etc.), when a user
> clicks on save, I need to establish a Documentum Repository connection, get
> additional info from repository and then post it to another
> application(invoking RestAPI). This needs to happen every time a change is
> made to the Job.
>
>
>
> Now, so far I am able to figure out that mcf-pull-agents is called on save
> of Job and it makes connection with DCTM connector(DCTM.java) for getting
> data out of Documentum repository. What I cannot figure out is how can I
> get hold of the repository session from DCTM connector in Jobs.java or
> JobManager.java(of mcf-pull-agents) on save of the Job.  I would prefer for
> this happen on server side, as I can see that Job page JSP can fetch the
> data from Manifold server(using Repository connection), which I can then
> post back to the RestAPI. Howerver, as both the applications would be
> hosted on the same server, so it doesn’t seem like a good coding to
> un-necessary fetch the data in JSP(client-side) and send back to server.
>  Alternatively, I can add Documentum DFC code to get the info, but that
> seems like overkill and bad practice, as we already have a batch file
> running for connecting to DCTM repository and getting the info.
>
>
>
> It would be really helpful, if someone can explain how to make DCTM
> connection in mcf-pull-agent.
>
>
>
>
>
> Thanks!
>
>
>
> Regards,
>
> Pankaj Pandey
>
>
>
> 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
>

Mime
View raw message