Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: "Webhelp.jar file is corrupted" during deployment

Updated on December 9, 2008

Symptom

When preparing for, or during, deployment of Process Commander, WebSphere or J2EE security software reports that the webhelp.jar file (within the prhelp.jar file) is corrupt and should not be deployed.

 

Solution

This webhelp.jar file is supplied by Adobe Systems as part of Adobe Robohelp 7.

The file is automatically included in every help system produced in the WebHelp format. Under certain configuration options — not used by Process Commander — this jar file powers a client-side Java applet that displays the help topics.

The "corrupt webhelp.jar file" issue is reported in Adobe Systems support forums, in some cases when deploying in WebSphere. See:

The issue occurs with Process Commander V5.4, V5.4SP1, and V5.4SP2.

Workaround

The webhelp.jar file is not required by any Process Commander facilities. The display of help topics by Process Commander does not use this Java applet.

As a workaround:

  1. Unzip prhelp.jar into a temporary directory.
  2. Delete webhelp.jar.
  3. Repackage prhelp.jar.
  4. Continue with installation and deployment.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us