Changes between Version 85 and Version 86 of instructions

Show
Ignore:
Timestamp:
11/17/10 17:58:35 (8 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • instructions

    v85 v86  
    134134Before packaging the webapp, the webapp config directory should be populated with configuration files for ORCA_LOCAL, as described above.  Before deploying the webapp, the tomcat container should be configured with a proper ORCA_HOME populated with configuration files as described above.   
    135135 
    136 3. Wait until the actors start ticking before you log into the portal. Check in the log file (tomcat/logs/log) or just wait 30-45 seconds. Tomcat has an annoying race condition during webapp initialization. If you try to log in too early, ORCA will fail to start up correctly. 
    137  
    138 4. Log into the portal at http://localhost:11080/orca ~~with username "admin" and no password~~, unless you changed the defaults. 
     1363. Log into the portal at http://localhost:11080/orca ~~with username "admin" and no password~~, unless you changed the defaults. 
    139137 
    140138'''NOTE:''' as of Bella 2.0 container administrator login/password credentials are located in [https://geni-orca.renci.org/orca-doc/current/guides/container-configuration/properties.html container.properties]. 
    141139 
    142 5. If the app did not come up as expected, then the container (ORCA_HOME) and actors (ORCA_LOCAL) are likely misconfigured.  There is no easy way to debug configuration errors.  Check the container logs in tomcat/logs/orca*.log.   You can add more information to these logs by editing the log4j properties in ORCA_HOME/config/container.properties, e.g., to add "%C %M %L" to the ConversionPattern to print the class, method, and line number for each log message.  It is also possible to load config.xml directives into the running web GUI, under the admin tab, which gives additional error reporting through the GUI.  Config processing is not atomic or idempotent: if config processing fails, some directives may have completed successfully. 
     1404. If the app did not come up as expected, then the container (ORCA_HOME) and actors (ORCA_LOCAL) are likely misconfigured.  There is no easy way to debug configuration errors.  Check the container logs in tomcat/logs/orca*.log.   You can add more information to these logs by editing the log4j properties in ORCA_HOME/config/container.properties, e.g., to add "%C %M %L" to the ConversionPattern to print the class, method, and line number for each log message.  It is also possible to load config.xml directives into the running web GUI, under the admin tab, which gives additional error reporting through the GUI.  Config processing is not atomic or idempotent: if config processing fails, some directives may have completed successfully. 
    143141 
    144142'''Feature:''' in multi-container configurations claim processing for exported tickets (advertisements/delegations) must be done manually after the container stands up, since it requires inter-actor communication.  Go to the broker tab, create an inventory slice, and claim the delegation, using the GUID for the exported ticket, which is visible under the site tab (view exported resources). '''This does not apply to emulation mode example'''