...
- For the development environments, you may generate a self signed certificate and add to the attached rice.keystore using the following command:
Code Block keytool -keystore rice.keystore -storepass nowUCme_nowUdont -v -alias <your alias> -genkeypair -validity 9999 -dname "CN=<your fully qualified machine name>, OU=<your organization>, O=UC Davis, L=Davis, ST=California, C=US"
- Install the updated rice.keystore in your environment where it will be referenced in the rice configuration files.
- A copy of the updated rice.keystore must also be installed on the Rice Standalone Server.
- For the production environment, an InCommon Certificate is required for the machine(s) which will be connecting to the production Rice Standalone Server. The InCommon cert must be installed in the production keystore as well as the keystore of the client application. For more information on how to request an InCommon certificate, visit the following link and click on the SSL Certificate category: MyUCDavis \> UCD Resources > Software
In Rice 1.0.x, there were only two main jars, rice-api and rice-impl. With the modularity work there are more api jars corresponding to service apis and framework components. Additionally, the implementation module has been split (though there is still a shared implementation module as not all components of the Rice implementation have been fully modularized as of the Rice 2.x.x release). This work was done according to the design outlined at the following page: Modularity Design
...