Recovering from common problems

This topic describes general recovery procedures.

When reporting server rename problems, include the following information:

General recovery consists of the following steps:

  1. Make sure that the server is shut down.
  2. Restore the databases for all ELM applications to their pre-rename state.
  3. Restore the properties for all ELM applications to their pre-rename state. In most implementations you recover the properties as follows:
    • In conf/jts, conf/ccm, conf/dcc, conf/gc, conf/qm, conf/relm, and conf/rs, find and restore the correct backup version of teamserver.properties. In both conf/lqe and conf/ldx, find and restore the correct backup version of lqe.properties, dbconnection.properties, and lqe.node.id.
    • In conf/rm, find and restore the correct backup versions of fronting.properties and friendsconfig.rdf.
    • In conf/jts/indices, conf/ccm/indices, conf/dcc/indices, conf/gc/indices, conf/qm/indices, conf/relm/indices, and conf/rs/indices, copy and restore the JFS/text indices.
  4. Review the mapping file and correct any problems from the previous rename.
  5. Restart the rename procedure by rerunning the repotools-jts -importURLMappings command with a corrected mappings file.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki