I recently published two new technotes related to some common issues that I have encountered in Support. Both of these issues are common issues that multiple IBM WebSphere Process Server users have come across. If you are encountering delays with WebSphere Process Server start-up, or WS-AT headers in your web services, then these publications might help you solve your problem. Check them out!
- Delays during WebSphere Process Server start-up and other activities when users have Spring components but limited network access to the Spring website URL. This occurs even if the Spring components are not used within a WebSphere Process Server scenario: WebSphere Process Server (WPS) might be slow to start up when using schemas, such as Spring components, in a limited network
- WS-Addressing (WS-AT) headers appear in users' web services causing errors if their web service does not understand these errors. Sometimes this consistently occurs with all web service calls in a scenario, sometimes it is intermittent:
A destination service might not understand WS-Addressing headers with WebSphere Process Server (WPS) Version 6.2 and later