Fix (APAR):  JR26573

Status:  Fix

Release:  6.0.2.1,6.0.2

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR26573

Byte size of APAR:  5513

Date: 2007-05-24

Abstract:  If module workspace path or wsdl file name contains space, serviceDeploy will fail to build the module.

Description/symptom of problem:  
JR26573 resolves the following problem:

ERROR DESCRIPTION:                                              
Validation errors occur in WID if the workspace name contains   
spaces.                                                         

LOCAL FIX:                                                      
use workspace path with no spaces                               

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.0.2.x users

PROBLEM DESCRIPTION:
If module workspace path or wsdl file
name contains space, serviceDeploy
will fail to build the module.

RECOMMENDATION:
None

When module workspace path or WSDL file name contains space,
it will fail to build the module with serviceDeploy.


PROBLEM CONCLUSION:                                             
The problem in WebSphere Process Server v6.0.2.0/1 will be      
resolved by the 6.0.2 interim fix below.                        
                                                                
The following error message might occur:                        
                                                                
com.ibm.ws.sca.deploy.port.webservice.                          
WebServiceDeploymentBuilder#004                                 
                                                                
Exception:                                                      
                                                                
org.eclipse.core.runtime.CoreException: Error messages          
were issued.                                                    
   at                                                           
                                                                
com.ibm.ws.sca.deploy.port.webservice.                          
WebServiceDeploymentBuilder.finish (Unknown Source)             
                                                                
                                                                
Or it's reported that WSDL files generated are marked invalid.  
                                                                


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system.
Also download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS  ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed

1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server

Additional Information: