Fix (APAR): JR30528 Status: Fix Release: 6.1.2,6.1.0.2,6.1.0.1,6.0.2.4,6.0.2.3 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 205586 Date: 2008-11-24 Abstract: If there is unmanaged node(s) in a ND environment, when deploying Service Component Architecture applications, there can be exceptions thrown out and the deployment will be failed. Description/symptom of problem: JR30528 resolves the following problem: ERROR DESCRIPTION:? This scenario has a Network Deployment topology. This topology also has unmanaged nodes, specifically webservers. When installing an application .EAR using wsadmin script, the install fails. Installing the same application using AdminConsole is successful. An interim fix will be created for this issue. =========== Explanation: The unmanaged node has no nodeagent. So there should be a defect in WPS during SCA app installation. It does not consider the situation that the node maybe unmanaged node and have no servers at all. In fact, if a SCA app is being installed a cluster, it will find a node randomly and read its server info. I is actually unnecessary. In this case, it just selected the webservr02 which is a unmanaged node and have no server. So the installation failed. LOCAL FIX:? A)Install using admin console instead of wsadmin B) remove webservr01 and webservr02 from the ND env, then install the ear file. After the installation finished, create the two unmanaged nodes again. C) Create a dummy server under the webservr02 node so that the installation can continue. Below are the steps to create the dummy server: 1) In the deploy manager profile dir, create dir named servers under WPSRoot/Profiles/DMGRNODE01/config/cells/ift2wps3Cell01/nodes/we bservr0 2) create a dir named nodeagent under the servers dir created in step 1); 3) copy the server.xml file under the nodeagent dir of another node to the nodeagent dir created in step 2); 5) re-enter the wsadmin and run the $AdminApp install command, it should be fine this time. 6) remove the servers dir and its subdirs created in the workaround. PROBLEM SUMMARY:? USERS AFFECTED: WebSphere Process Server 6.0.2 users PROBLEM DESCRIPTION: If there is unmanaged node(s) in a ND environment, when deploying Service Component Architecture applications, there can be exceptions thrown out and the deployment will be failed. RECOMMENDATION: None If there is unmanaged node(s) in ND environment, when deploying Service Component Architecture applications, there can be exceptions thrown out and the deployment will fail. Because, the deployment process will try to read the configrations of the unmanaged nodes, but they are unvailable. Following exceptions occur java.lang.IllegalArgumentException at com.ibm.ws.sca.internal.deployment.management.AdminBase. showAttribute(AdminBase.java:266) at com.ibm.ws.sca.internal.deployment.management.AdminCommand. (AdminCommand.java:61) at com.ibm.ws.sca.internal.deployment.eis.EISAdmin. (EISAdmin.java:81) at com.ibm.ws.sca.internal.deployment.eis.EISArchiveTask. install(EISArchiveTask.java:119) at com.ibm.ws.sca.internal.deployment.SCAInstallTask. performInstallTasks(SCAInstallTask.java:117) at com.ibm.ws.sca.internal.deployment.SCAInstallTask. performTask(SCAInstallTask.java:61) at com.ibm.ws.management.application.SchedulerImpl. run(SchedulerImpl.java:253) at java.lang.Thread.run(Thread.java:570) PROBLEM CONCLUSION:? The problem has been fixed. Apply the Interim Fix, deploy the Service Component Architecture applications, the deployment will be successful. 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: