TEP Java WebStart Client fails with "The following required field is missing" error

Technote (troubleshooting)


Problem(Abstract)

Attempting to run the TEP Java WebStart client fails with error details showing "The following required field is missing from the launch file ... "

Symptom

First, the error "Unable to launch the application" appears.

After clicking the "Details" button, the information window shows "Error: The following required field is missing from the launch file: <jnlp>(<application-desc>|<applet-desc>|<installer-desc>|<component-desc>)] ".

The "Exception" tab shows the following java stack trace:


MissingFieldException[ The following required field is missing from the launch file: <jnlp>(<application-desc>|<applet-desc>|<installer-desc>|<component-desc>)]
at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Cause

One possibility is that the tep.jnlp and/or tep.jnlpt template files are incorrectly formatted due to manual edits done to the file(s).

Environment

TEP Java WebStart client only

Diagnosing the problem

The error message window also has a "Launch File" tab. The first few lines of the file look similar to the following:

<code>


<!-- JNLP File for Tivoli Enterprise Portal V6.2.3 -->
<?xml version="1.0" encoding="utf-8"?>
<jnlp
spec="1.0+"
codebase="http://hostname123:1920///cnp/kdh/lib/"
<information>

</code>


This is displaying the contents of the tep.jnlp file that is pulled from the TEPS. Notice that after the "codebase" entry there is a missing closing bracket ">" character that is needed to close the "jnlp" section.


Resolving the problem

1. Edit the tep.jnlpt template file.

On Windows, the file is %CANDLE_HOME%\config\tep.jnlpt .
On UNIX/Linux, the file is <InstallDirectory>/config/tep.jnlpt .

2. Verify that the "codebase" line has the closing bracket ">" character, to close the "jnlp" section correctly. If it is missing, add it.

For example, for the TEPS named "hostname123" above, the line would be edited to change it from this:

<code>
codebase="http://hostname123:1920///cnp/kdh/lib/"
</code>
to this new value:
<code>
codebase="http://hostname123:1920///cnp/kdh/lib/">
</code>
3. Edit the tep.jnlp file.
On Windows, the file is %CANDLE_HOME%\CNB\tep.jnlp.
On UNIX/Linux, the file is <InstallDirectory>/<architecture>/cw/tep.jnlp.
Verify that the "codebase" line has the closing bracket ">" character, to close the "jnlp" section correctly. If it is missing, add it, following the same method/example as above.

Retry the TEP Java WebStart client.

The reason both the tep.jnlpt and the tep.jnlp files are edited is that the tep.jnlpt file is used as a template during TEPS reconfiguration to rewrite the tep.jnlp file. Whenever changes need to be made to the tep.jnlp, they should first be made to the tep.jnlpt file, and the TEPS reconfigured, so that it can rewrite the tep.jnlp file. Direct edits to the tep.jnlp file can become lost after the TEPS is reconfigured again. In the example above, changes were made to both files manually, to avoid having to stop, edit the template file, reconfigure, and restart the TEPS.

If another error appears mentioning a missing field, or a parsing error appears in the "Exception" tab, it implies some additional changes need to be made to the format of the tep.jnlpt and/or tep.jnlp file.


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Components
ITM Tivoli Enterprise Portal V6

Software version:

6.2.2, 6.2.2.2, 6.2.2.3, 6.2.2.4, 6.2.2.5, 6.2.2.6, 6.2.2.7, 6.2.3, 6.2.3.1, 6.2.3.2

Operating system(s):

Platform Independent

Reference #:

1606340

Modified date:

2013-05-13

Translate my page

Machine Translation

Content navigation