PK92713: USERS SHOULD BE ABLE TO SPECIFY CLASSPATH WITH THE ENDPTENABLER TOOL.

Fixes are available

APAR status

Closed as program error.

Error description

When running endptEnabler, the user might see that it fails
with error messages like the following:

WSWS2004I: IBM WebSphere Application Server Version 7.0
WSWS2005I: Web services Enterprise Archive Endpoint Enabler.
WSWS2007I: (C) COPYRIGHT International Business Machines Corp.
1997, 2008.
WSWS2006I: Enter the name of your enterprise archive (EAR)
file: HelloWorld.ear

WSWS2003I: Backing up the enterprise archive (EAR) file to:
HelloWorld.ear~

WSWS2012I: The endpoint enabler is using the following
properties:
        verbose: true

WSWS2016I: Loading enterprise archive (EAR) file: HelloWorld.ear
WSWS2017I: Found enterprise bean module: HelloEJB.jar
C:\was70\WebSphere\AppServer\profiles\AppSrv01\temp\wscache\
HelloWorld\HelloEJB.jar\module\hello\world\HelloBeanBean.java:6:
package com.ibm.test does not exist
import com.ibm.test.Greeting;
                   ^

C:\was70\WebSphere\AppServer\profiles\AppSrv01\temp\wscache\
HelloWorld\HelloEJB.jar\module\hello\world\HelloBeanBean.java:11
:cannot find symbol
symbol: class Greeting
Greeting hello;
^

2 errors
WSWS2021I: Skipping the enterprise bean module HelloEJB.jar
because it contains no Web services.
WSWS2018I: Finished processing enterprise archive (EAR) file
HelloWorld.ear

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the WebSphere Application Server   *
*                  V7 endptEnabler tool                        *
****************************************************************
* PROBLEM DESCRIPTION: If an EJB references Java types that    *
*                      are packaged in a JAR that is not       *
*                      included in the EAR, endptEnabler       *
*                      might fail.                             *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR.     *
****************************************************************
Users wishing to enable their EJB's as web services need to
run the endptEnabler command on the EAR file. They might
observe an error similar to the following:

WSWS2004I: IBM WebSphere Application Server Version 7.0
WSWS2005I: Web services Enterprise Archive Endpoint Enabler.
WSWS2007I: (C) COPYRIGHT International Business Machines Corp.
1997, 2008.
WSWS2006I: Enter the name of your enterprise archive (EAR)
file: HelloWorld.ear

WSWS2003I: Backing up the enterprise archive (EAR) file to:
HelloWorld.ear~

WSWS2012I: The endpoint enabler is using the following
properties:
        verbose: true

WSWS2016I: Loading enterprise archive (EAR) file: HelloWorld.ear
WSWS2017I: Found enterprise bean module: HelloEJB.jar
C:\was70\WebSphere\AppServer\profiles\AppSrv01\temp\wscache\
HelloWorld\HelloEJB.jar\module\hello\world\HelloBeanBean.java:6:
package com.ibm.test does not exist
import com.ibm.test.Greeting;
                   ^

C:\was70\WebSphere\AppServer\profiles\AppSrv01\temp\wscache\
HelloWorld\HelloEJB.jar\module\hello\world\HelloBeanBean.java:11
:cannot find symbol
symbol: class Greeting
Greeting hello;
^

2 errors
WSWS2021I: Skipping the enterprise bean module HelloEJB.jar
because it contains no Web services.
WSWS2018I: Finished processing enterprise archive (EAR) file
HelloWorld.ear

This can occur if the EJB references Java types in separate
JAR files that do not exist in the EAR file.  Users need a way
to specify separate JAR files in the classpath to endptEnabler.

Problem conclusion

The endptEnabler was fixed to take a user-defined classpath
when trying to resolve all the referenced Java types found in
the application. The custom classpath should be specified with
the new option, -classpath (-cp). For example:

endptEnabler -classpath C:\MyWork\Utility.jar ...

Separate multiple entries with the file separator path
appropriate for your operating system. For example:

endptEnabler -classpath
C:\MyWork\Utility.jar;D:\SharedFiles\Hello.zip;HelloWorld.jar
...

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK92713
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-30
Closed date
2009-09-17
Last modified date
2009-09-17

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK92713: USERS SHOULD BE ABLE TO SPECIFY CLASSPATH WITH THE ENDPTENABLER TOOL.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?