Here's what we do in markmail to add a new node. We use puppet to drive, but you could do this in a scripting language and/or installer tool of your choice.
0) checkout (svn co) our application code on to the box 1) copy marklogic rpm to the box and install 2) wget a few URLs within the ML Admin app to do a few things, including install our license 3) copy a setup-markmail.xqy script to the Admin app filesystem 4) wget the url of the setup script * this script wipes out default dbs, forests, and app servers we don't want * set up app-servers, dbs, forests, index settings, and the like. * setup security users, roles, amps, etc... If you're interested in details, I can share more. It's a little tricky as some of the admin ops result in the server restarting. -Eric ________________________________________ From: [email protected] [[email protected]] On Behalf Of Karl Erisman [[email protected]] Sent: Tuesday, March 02, 2010 9:35 AM To: General Mark Logic Developer Discussion Subject: Re: [MarkLogic Dev General] user installation using a query If your customer does not yet have MarkLogic installed, they'll have to use the administrative interface to configure MarkLogic itself, so the procedure you've outlined seems straightforward enough as long as your install.xqy itself is "user-friendly" (which should probably mean that it presents a simple interface, does not ask questions that are excessively technical, and shows clear confirmation or error messages based on what happens). I've been wondering about a broader, but closely-related topic: release management of production MarkLogic applications in general. How do others package code for system admins (customers themselves in Andrew's case; but probably developers or an internal team of specialists at most organizations) to deploy? This applies to new releases or upgrades. Do you create, for each version of your application, an XQuery install script (much like the one Andrew plans to use) that performs steps such as manipulation of app servers, databases, etc. to bring the configuration up to date with respect to source code changes? Any other hints on streamlining the process? Karl On Tue, Mar 2, 2010 at 10:41 AM, Andrew Welch <[email protected]> wrote: > Hi, > > It seems that everything you can do through the admin screen you can > do through a query... so rather give the customer a list of steps to > follow (create http server, create webdav server etc), I can shield > them from the admin screens and give them a query to run instead. > > The question is, what is the user-friendliest way for them to run that > xquery, when the person installing the application is likely to know > very little about MarkLogic? > > Is using the Docs dir the best way: > > 1) Install MarkLogic > 2) copy the "install.xqy" to [install dir]/Docs > 2) navigate to [hostname]:8000/install.xqy > > ...or is there another way? > > > > thanks > -- > Andrew Welch > http://andrewjwelch.com > Kernow: http://kernowforsaxon.sf.net/ > _______________________________________________ > General mailing list > [email protected] > http://xqzone.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general_______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
