The process also creates a modules database for the app server. Having completed the previous step, you have an HTTP app server set up with the REST API. On the Database Settings page that comes up, scroll down and you’ll see a button to create a new REST API Instance.
In order to make sure the app server gets initialized correctly, we’ll tell MarkLogic to create a REST API app server. output_port 8008 Create a REST app server input_port 8006 -output_username admin -output_password admin -output_host server2 \ $ bin/mlcp.sh COPY -input_username admin -input_password admin -input_host server1 \ You will probably need to create the XDBC app server on server2. server1 has an XDBC app server on port 8006 pointing to the old content database, and server2 has an XDBC app server on port 8008 pointing to the new content database.
In this example I’m using the admin user, with password “admin” on both hosts (bad, bad).
Use mlcp to copy the content from the original server to the new one. Click the Apply button to have it create your content database.
The reason turned out to be the way that I had migrated the options for the REST app server. The first couple times I tried it, the application failed when it made calls back to the server to get search results. I build an app on my laptop, then deploy it to one or more servers for others to review and use. There is one aspect that’s a bit tricky, however - migrating the application from one server to another. I really like the result - you can now get some interesting charts and maps set up just by clicking through the wizard, and the source code it deploys is easier to work with. In MarkLogic 6, Application Builder has gotten an overhaul.