Customizing › Web Interface Customization › How to Customize Schema Using Web Screen Painter › Publish Schema Modifications › Recover WSP Changes During Background Server Failure

Recover WSP Changes During Background Server Failure

You can recover the MDB schema changes when the background server fails during the publishing activity.

Important! We recommend you not to perform the recovery steps directly on the production environment. Ensure that you first validate them on the test or development environment.

Follow these steps:

• If the background server has crashed before publishing, the last saved schema changes are preserved in MDB. You log in to the new background server and resume your publishing tasks.
• If the background server crashed after publishing, perform the following actions:
  1. Stop CA SDM services on the crashed background server.
  2. Choose a standby server that you want to promote as the new background server.
  3. Copy the following files from crashed background server to the same location on the standby server:
     • "$NX_ROOT$/site/mods/majic/wsp.mods"
     • "$NX_ROOT$/site/mods/wsp.altertbl"
     • "$NX_ROOT$/site/mods/wsp.altercol"
     • "$NX_ROOT$/site/mods/wsp_index.sch"
     • "$NX_ROOT$/site/mods/wsp_schema.sch
  4. Run the following command on the standby server to publish the schema changes and to perform the automatic fail-over:

     pdm_publish
     

  5. Select Y on the message prompt that appears after successful publishing of schema changes.

     The CA SDM services are started on the standby server.

     Note: If automatic fail-over does not occur, run the pdm_server_control -b command from the standby server to promote it as the new background server.

  6. Quiesce and recycle each application server. Restart all standby servers. For more information, see the Publish Schema Modifications topic.