One thing to recognize is that if your using XCC (or any tool that uses it) the "connection string" can end with a /database This took me a while to notice ... but it means you only need ONE XDBC server. e.g xcc://host:8888/database
Will connect to "database" as the default db reguardless of the database specified to XDBC server at port 8888 ( providing you have rights). If your looking for other tooling .. may I humbly suggest the xmlsh marklogic extensions http://developer.marklogic.com/code/xmlsh-ext http://www.xmlsh.org/ModuleMarkLogic This is what I, myself, use 99% of the time if I want to script anything to/from MarkLogic from any kind of scripting language that can handle java. Of course I am biased. ----------------------------------------------------------------------------- David Lee Lead Engineer MarkLogic Corporation [email protected] Phone: +1 812-482-5224 Cell: +1 812-630-7622 www.marklogic.com -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Blakeley Sent: Tuesday, November 19, 2013 11:36 AM To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] Basic MLCP question and feature request I don't have an answer on mlcp. But as I see it, there is no pressing need to migrate from older tools if they do what you need. If you have any problems with XQSync, I still pay attention to https://github.com/marklogic/xqsync/issues -- Mike On 19 Nov 2013, at 07:54 , David Sewell <[email protected]> wrote: > Since forever I've used cqsh and XQSynch as my main command-line tools for > moving things around from filesystem to MarkLogic database or from DB to DB. > Since those tools are both aging and no longer in development I'm looking at > shifting my workflows to Content Pump. > > Question: with MLCP, is there really no way to load content into a database > other than the target database for the XDBC server? In other words, it is > necessary to have one XDBC App Server for every database with which you want > to > use MLCP? > > That is a somewhat bothersome limitation. With cqsh, all you need is a single > XDBC server on a host, because there is a "--database" flag you can use to > specify the database for import. Likewise, with XQSych you can select any > database on the host via the INPUT_CONNECTION_STRING and > OUTPUT_CONNECTION_STRING parameters. If this flexibility is missing from > MLCP, > is that a design decision? > > Feature request: tweak the shell scripts (at least the Bash one) to allow the > password to be prompted for, instead of passed on the command line (for > security > reasons). (This is an easy do-it-yourself modification to mlcp.sh but it > seems > like it should be part of the distribution.) > > David S. > > > -- > David Sewell, Editorial and Technical Manager > ROTUNDA, The University of Virginia Press > PO Box 400314, Charlottesville, VA 22904-4314 USA > Email: [email protected] Tel: +1 434 924 9973 > Web: http://rotunda.upress.virginia.edu/ > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
