Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-2764

Deploy Rice standalone server to our test environments


    • Similar issues:
      KULRICE-13134Create Rice 2.5 environments for testing client/server deployments
      KULRICE-2815 Deploy CAS-enabled Rice standalone server to test environment
      KULRICE-2816Deploy Rice standalone server with Recipe sample app to test environments
      KULRICE-2932rice-config.xml for deployment of standalone server
      KULRICE-1475Deploy a test Rice Standalone application to a test environment
      KULRICE-5665Implement the ability to run rice sample app as a seperate application integrated with the Rice Standalone Server, put process in place to automatically deploy to a test environment using CI
      KULRICE-11774Create performance test environment: Standalone Server Oracle, Rice Sample App Client Oracle, KRAD Client Oracle
      KULRICE-11775Create performance test environment: Standalone Server MySQL, KRAD Client MySQL, Rice Sample App Client MySQL
      KULRICE-4656Maintenance/Transactional screen's images are being served from standalone rice server
      KULRICE-3157Deploy new kuali-cas server to test environments


      Here are the notes from our meeting today regarding this:

      • Update the build.xml in rice and add dist-external and dist-war
        • generated war file from dist-war will get automatically deployed to wsa131 via the j2ee_deploy_war script on wsa123
      • We need to update do-daily-updates.sh in kul-cfg-envs to add "kupdate" statements in our script so that we execute the daily update
        • Initially, let's start with just the STG environment and use the RICESTG database
        • part of the kupdate script should be able to create the RICESTG database using our nightly database export
        • so our first environments will use the STG database
      • Update /usr/local/rice/rice-config.xml to reflect configuration changes in rice 1.0, verify files in /usr/local/rice/stg/...
      • at any point during the day we can probably just run do-daily-updates.sh to test an initial deployment
        • IMPORTANT: no two projects can run their updates scripts at the same time
      • We also need to update (and move to KULRICE) the documentation at the following location:

        Issue Links


          No work has yet been logged on this issue.


            • Assignee:
              Casey Boettcher (Inactive)
              Eric Westfall
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created:

                Time Tracking

                Original Estimate - 2 days, 4 hours
                2d 4h
                Remaining Estimate - 2 days, 4 hours
                2d 4h
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel