PowerTools Documentation: Index | Troubleshooting

## 1 DSP Install page (debugging dsp.xml)

Following instructions will help in ensuring that dsp.xml contains all the elements required for rendering DSP install screen(one used by SA to deploy Powertools).

    cd lwp_si_packages
    # Replace DSP and DSP-Version in following command with your DSP paths
    # eg. gallery/1.4.1
    xsltproc ./util/dsp_options.xsl <DSP>/<DSP-Version>/dsp.xml > test_dsp.xml
    # Something is wrong if you see errors in following commands output
    xmllint --dtdvalid util/dsp.dtd test_dsp.xml
    xsltproc /usr/lib/ensim/deployables/lib/themes/default.xsl test_dsp.xml > test_dsp.htm

Now view the test_dsp.htm page in browser. This should be enough close to desired Install page of your DSP.

## 2 Build(make) problems

Try removing build directory and os.mk. Rebuild.

    rm -rf build ok.mk

If you do not find DSP rpm created then make sure that the DSP entry is added to dirs.mk

## 3 DSP Logo problem

If you do not see DSP logo on Webppliance pages make sure logo file is named as <DSPNAME>.gif.

## 4 Debugging dAPI.py on development box

One can install Ensim Pro on a test box which may save some time. Install DSP rpm on development box. Debug dAPI.py by directly editing /usr/lib/ensim/deployables/<DSPNAME-DSPVERSION>/lib/dAPI.py . Followed by

    service webppliance restart

to see the changes in Webppliance-GUI (Web interface).

Developer do not need a service restart if he tries CLI.

    InstallAddon site<N> <DSPNAME-DSPVERSION> -h

Retrieved from "wiki/index.php/Troubleshooting"