E1:BSSV WAS - Getting 404 Error for All WSDL and Endpoints After New Package Build/deploy
Last updated on FEBRUARY 04, 2016
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
Using Websphere 8.5.5 on Windows 2012 to build JAX-WS business services. Using Jdeveloper 18.104.22.168 on the build machine.
Able to build and deploy packages successfully for any packages built before a certain date. When using a browser to view the WSDL, do not get any errors and WSDL displays correctly. However, after a certain date, can still build and deploy a business service package successfully with no errors, but when trying to view the WSDL in a browser, getting an error: HTTP 404 error. Then if re-deploy the old package from before a certain date, everything works again. Nothing has changed configuration wise.
The browser displays a HTTP 404 error when trying to go to the WSDL using a browser. Also, getting the below when going to an endpoint in the Websphere server logs:
In the Business Server log can see an error that the *.ear was not successfully built because of a java exception in a custom business service (J55XXX).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms