Changes between Version 37 and Version 38 of deploy-sm

Show
Ignore:
Timestamp:
12/03/11 23:53:44 (8 years ago)
Author:
ibaldin (IP: 152.54.15.223)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • deploy-sm

    v37 v38  
    1616 * Place the file under $ORCA_HOME/config/config.xml 
    1717 * Create a configuration file for the controller based on this [source:orca/trunk/controllers/xmlrpc/xmlrpc.controller.sample.properties sample] and place it under $ORCA_HOME/config/xmlrpc.controller.properties 
    18   * Place the truststore file [attachment:geni-trusted.jks geni-trusted.jks] attached to this page under $ORCA_HOME/config/ and be sure xmlrpc.controller.properties points to it. Truststore password is 'orcaorca'.  
     18  * Place the truststore file [attachment:geni-trusted.jks geni-trusted.jks] attached to this page under $ORCA_HOME/config/ and be sure xmlrpc.controller.properties points to it. Truststore password is 'orcaorca'. At deployment you should change the password (and put the new password into xmlrpc.controller.properties) using the command 
     19{{{ 
     20$ keytool -storepasswd -new newpassword -keystore geni-trusted.jks 
     21}}} 
    1922  * Alternatively you can create your own JKS truststore by importing selected certificates from [http://boss.pgeni.gpolab.bbn.com/ca-cert/pgeni.gpolab.bbn.com.pem GPO] and [http://boss.emulab.net/genica.bundle Emulab]. Only include CA certificates from authorities you want your controller to be able to accept certificates from.   
    2023 * [wiki:orca-tomcat Download and configure Tomcat] (with SSL if you plan to use ProtoGENI AM API).