Fix (APAR): JR28876 Status: Fix Release: 6.1.0.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: JR28876 Byte size of APAR: 71019 Date: 2008-04-24 Abstract: If source projects contain a lot of XSD/WSDL files, it takes a long time for serviceDeploy to build it into a EAR file. Description/symptom of problem: JR28876 resolves the following problem: ERROR DESCRIPTION: SericeDeploy command takes too long to validate big projects. An option provided in V6022 -skipXsdValidate needs to be ported. LOCAL FIX: Following work around will disable WSDL and XSD validators. Pleasemake sure validator are run in development environment to avoid potential run time errors Here is a temp Workaround: 1. backup the file /deploytool/itp/plugins/com.ibm.wbit.command.validation_6 .1.0.200 712021308.jar and save this file in some temp directory ( Note that just renaming and leaving it in the samedirectory will not work) 2. Delete the file /deploytool/itp/plugins/com.ibm.wbit.command.validation_6 .1.0.200 712021308.jar PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server and WebSphere Enterprise Service Bus v6.1 users who use serviceDeploy to build source projects. PROBLEM DESCRIPTION: If source projects contain a lot of XSD/WSDL files, it takes a long time for serviceDeploy to build it into a EAR file. RECOMMENDATION: None XSD/WSDL validators will take a long time to validate schemas. PROBLEM CONCLUSION: An option "-skipXsdValidate" is added to skip XSD/WSDL schema validation during serviceDeploy. If true value is specified or not specified true or false to the option, the validator will not run in servicedeploy. If false or not specified -skipXsdValidate, the validator will run as before. Usage example: If we use the following: servicedeploy -keep -skipXsdValidate true servicedeploy -keep -skipXsdValidate the validator will not run in servicedeploy. If we use the following: servicedeploy -keep -skipXsdValidate false servicedeploy -keep the validator will run in servicedeploy. Directions to apply fix: 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 Process Server. 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 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. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Process Server. 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: