Page History

Section 1 - Step 3: The Moves Development Environment Setup

1. Download the following files:

   Warning
   The following 2 properties files are the be used solely and exclusively in the software development environment on an Educational Systems VM.  They are NOT to be deployed to the development, test or production servers.

   1. Download and install the sais-moves-web.properties file (right click on this link then select Save target/link as....  Navigate to the ${user.home} directory and click Save)
   2. Download and install the sais-moves-web-build.properties file (right click on this link then select Save target/link as....  Navigate to the ${user.home} directory and click Save)
      
   3. Open the sais-moves-web-build.properties file for editing and change the following properties:
      
      • mit.maven.release.plugin.version=2.0.21  Change the version number (2.0.21) to the mit-release-plugin version number that you selected in section 1.
      • maven.system.property.cargo.hostname=esvm-1xx.mit.edu  Change the hostname (esvm-1xx.mit.edu) to your vm's hostname.
        
        
2. Configure your moves build directories
   
   1. Create the following directories:
      
      • C:\tmp\movesbuild\build\sais-common-conf\.m2\repository
      • C:\tmp\movesbuild\build\sais-common-conf\servers\oc4j

        Note
        Please note that the .m2 directory cannot be created using Windows Explorer.  To create the .m2 directory, you must open a cmd window, cd to the sais-common-conf directory and use mkdir to create the .m2 directory.

   2. Open a cmd window and cd to the C:\tmp\movesbuild\build\sais-common-conf\.m2 directory.  Execute the following command:

      Code Block
      linkd repository c:\Users\esuser\.m2\repository

      The above command will link your local maven repository to the directory C:\tmp\movesbuild\build\sais-common-conf\.m2\repository.

      Warning
      Do not delete or rename the repository directory.  Deleting or Renaming the repository directory will delete your local maven repository.  Unlink the repository directory before you delete or rename.

      Tip
      You can unlink the repostory directory with the following command: Code Block linkd repository /D You must be in the .m2 directory when you execute the above command.

   3. Download and install the settings.xml (right click on this link then select Save target/link as....  Navigate to the .m2 directory you've just created and click Save)
      
      Open the settings.xml for editing and change the following:
      
      
      • Change the property value for <oc4j.j2eeHome> to:

        Code Block
        /oracle-oc4j-10.1.3.5.0-server/j2ee/home

      • Change the property value for <oc4j.password> to:

        Code Block
        oc4jadmin

   4. In a cmd window, cd to the C:\tmp\movesbuild\build\sais-common-conf\servers directory.  Execute the following command:

      Code Block
      linkd oc4j c:\oracle-oc4j-10.1.3.5.0-server

      The above command will link your local oracle server to the directory C:\tmp\movesbuild\build\sais-common-conf\servers\oc4j.

      Warning
      Do not delete or rename the oc4j directory.  Deleting or Renaming the oc4j directory will delete your local oracle server.  Unlink the oc4j directory before you delete or rename.

      Tip
      You can unlink the oc4j directory with the following command: Code Block linkd oc4j /D You must be in the servers directory when you execute the above command.

3. Configure your moves ui directories
   
   1. Create the following directories:
      
      • C:\tmp\movesbuild\ui\sais-common-conf\.m2\repository
      • C:\tmp\movesbuild\ui\sais-common-conf\servers\oc4j

        Note
        Please note that the .m2 directory cannot be created using Windows Explorer.  To create the .m2 directory, you must open a cmd window, cd to the sais-common-conf directory and use mkdir to create the .m2 directory.

   2. Open a cmd window and cd to the C:\tmp\movesbuild\ui\sais-common-conf\.m2 directory.  Execute the following command:

      Code Block
      linkd repository c:\Users\esuser\.m2\repository

      The above command will link your local maven repository to the directory C:\tmp\movesbuild\ui\sais-common-conf\.m2\repository.

      Warning
      Do not delete or rename the repository directory.  Deleting or Renaming the repository directory will delete your local maven repository.  Unlink the repository directory before you delete or rename.

      Tip
      You can unlink the repostory directory with the following command: Code Block linkd repository /D You must be in the .m2 directory when you execute the above command.

   3. Download and install the settings.xml (right click on this link then select Save target/link as....  Navigate to the .m2 directory you've just created and click Save)
      
      Open the settings.xml for editing and change the following:
      
      
      • Change the property value for <oc4j.j2eeHome> to:

        Code Block
        /oracle-oc4j-10.1.3.5.0-server/j2ee/home

      • Change the property value for <oc4j.password> to:

        Code Block
        oc4jadmin

   4. In a cmd window, cd to the C:\tmp\movesbuild\ui\sais-common-conf\servers directory.  Execute the following command:

      Code Block
      linkd oc4j c:\oracle-oc4j-10.1.3.5.0-server

      The above command will link your local oracle server to the directory C:\tmp\movesbuild\ui\sais-common-conf\servers\oc4j.

      Warning
      Do not delete or rename the oc4j directory.  Deleting or Renaming the oc4j directory will delete your local oracle server.  Unlink the oc4j directory before you delete or rename.

      Tip
      You can unlink the oc4j directory with the following command: Code Block linkd oc4j /D You must be in the servers directory when you execute the above command.

The Moves Development Environment Setup is now complete.

Section 1 is

now complete.

Section

3: Debugging the mit-release-plugin

1. Build and install mit-release-plugin-parent.
2. Build, install and deploy sais-moves-web to your oracle server.
3. Setting break points.
4. Attaching the IDE's debugger.