Moves stores runtime config changes in a file called $\user.home}/sais-moves-web.properties. This is to manage properties which change at runtime. Moves also creates a folder called $\user.home}/sais-moves-web/ when interacting with subversion and maven. This page assumes that you're starting from scratch, so if these exist, stop OC4J, and rename these to $\user.home}/sais-moves-web.properties.backup and $\user.home}/sais-moves-web.backup respectively. That way you can be sure you are running in the most pristine state possible, and your screens should match those below.
It is assumed that you have been able to build and deploy moves, and can access the page http://localhost:8888/moves/admin/index.htm as outlined in Building and deploying moves locally.
The Build Configuration page
Click on the Build Configuration icon on http://localhost:8888/moves/admin/index.htm. There are 3 tabs on there.... one for Maven configuration, one for Subversion configuration and one for OC4J configuration. Let's start with each tab from simplest to most complex.
Build Configuration - OC4J tab
The only thing we need to know about oc4j is where the j2ee home folder is. This is so moves can find admin_client.jar, which it uses to deploy applications to containers. Below is a screenshot that I use on windows.
