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

Set up clustering for the Rice standalone servers

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 1.0
    • Component/s: Application Server
    • Labels:
      None
    • Similar issues:
      KULRICE-9272Instructions to setting up a Rice cluster are incorrect (installation guide)
      KULRICE-4656Maintenance/Transactional screen's images are being served from standalone rice server
      KULRICE-6578Make it so the standalone server will start up without having to specify the web.bootstrap.spring.file parameter
      KULRICE-6993KNS Infrastructure not supporting quickfinder lookups against standalone Rice server
      KULRICE-2855Document Kuali Rice Standalone Server installation and configuration
      KULRICE-2932rice-config.xml for deployment of standalone server
      KULRICE-9899Add documentation to IG on how to configure an application to work with Rice standalone server
      KULRICE-6749Configure rice sample app as a client app running against a standalone server
      KULRICE-2011Work with KFS team to setup KFS to run with Standalone Rice 1.0
      KULRICE-2810Rice standalone server startup throws a CXF error

      Description

      We need to set up Standalone Rice in a clustered environment. Farooq had mentioned previously that we could use the server that's been set up for materials management for this temporarily.

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment -

          Based on the linked jira wsa137.uits.indiana.edu is the machine we'll use. Here's what we need to do:

          1) get kuali6 set up on wsa137, will need to request from esa
          2) have esa set up deployment infrastructure so that it deploys the kuali6 apps (kr-cnv and kr-stg currently) to both wsa131 and wsa137
          3) on wsa137, we will need to get /usr/local/rice/rice-config.xml and related files set up, in an older version of workflow, ESA set up a script that allowed us to maintain these configuration files on wsa123 and then just run a script to rsync to the other machines (so we didn't have to manually maintain them on all machines). This would be cool if we could get this, the old script was called workflow_sync (they will probably recognize it from our IU deployments of Rice)
          4) We need to set things up for unique KSB endpoint urls. We need to request from esa is to pass in a system parameter to jvm startup so that we can properly construct these urls. Here's a summary of how we have done this in the past:

          We have ESA pass a system parameter to our JVM's, something like:

          -Dhttp.url=10.1.2.3:44881

          and then we just construct our serviceServletUrl appropriately:

          <param name="serviceServletUrl"
          value="http://$

          {http.url}

          /en-$

          {environment}

          /remoting/"</param>

          That way you give the service bus a unique url for each machine in the
          cluster.

          Show
          Eric Westfall added a comment - Based on the linked jira wsa137.uits.indiana.edu is the machine we'll use. Here's what we need to do: 1) get kuali6 set up on wsa137, will need to request from esa 2) have esa set up deployment infrastructure so that it deploys the kuali6 apps (kr-cnv and kr-stg currently) to both wsa131 and wsa137 3) on wsa137, we will need to get /usr/local/rice/rice-config.xml and related files set up, in an older version of workflow, ESA set up a script that allowed us to maintain these configuration files on wsa123 and then just run a script to rsync to the other machines (so we didn't have to manually maintain them on all machines). This would be cool if we could get this, the old script was called workflow_sync (they will probably recognize it from our IU deployments of Rice) 4) We need to set things up for unique KSB endpoint urls. We need to request from esa is to pass in a system parameter to jvm startup so that we can properly construct these urls. Here's a summary of how we have done this in the past: We have ESA pass a system parameter to our JVM's, something like: -Dhttp.url=10.1.2.3:44881 and then we just construct our serviceServletUrl appropriately: <param name="serviceServletUrl" value="http://$ {http.url} /en-$ {environment} /remoting/"</param> That way you give the service bus a unique url for each machine in the cluster.
          Hide
          Casey Boettcher (Inactive) added a comment -

          Waiting for permissions to be granted to j2eemgr for starting of tomcat instance kuali6

          Show
          Casey Boettcher (Inactive) added a comment - Waiting for permissions to be granted to j2eemgr for starting of tomcat instance kuali6
          Hide
          Eric Westfall added a comment -

          Bulk change of all Rice 1.0 issues to closed after public release.

          Show
          Eric Westfall added a comment - Bulk change of all Rice 1.0 issues to closed after public release.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 day
                1d
                Remaining:
                Remaining Estimate - 1 day
                1d
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel