Fix (APAR):  PI28055

Status:  Fix

Release:  8.0.0.7

Operating System:  AIX,HP-UX,IBM i,Inspur K-UX,Linux,Mac OS,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  265613

Date: 2014-10-28

Abstract:  admintask 'setbinding' fails to find installed application

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

ERROR DESCRIPTION:                                              
When there are multiple security domains, AdminTask 'setBinding'
fails with Admin Exception:                                     
                                                                
[8/27/13 13:50:51:995 CEST]     FFDC                            
Exception:com.ibm.websphere.management.exception.AdminException 
SourceId:com.ibm.ws.management.application.EditApplication.listM
odules ProbeId:979 Reporter:java.lang.Class@8de8af78            
com.ibm.websphere.management.exception.AdminException:          
ADMA0017E: The context for <application name> cannot be obtained
at                                                              
com.ibm.ws.management.application.EditApplication.listModules(Ed
at                                                              
com.ibm.ws.management.application.AppManagementImpl.listModules(
...                                                             
com.ibm.ws.policyset.admin.commands.util.PolicySetBindingCommand
at                                                              
com.ibm.ws.policyset.admin.commands.util.PolicySetBindingCommand
at                                                              
com.ibm.ws.policyset.admin.commands.util.PolicySetBindingCommand
at                                                              
com.ibm.ws.policyset.admin.commands.util.PolicySetBindingCommand
at                                                              
com.ibm.ws.policyset.admin.commands.SetBinding.execute(SetBindin
...                                                             

LOCAL FIX:                                                      
None                                                            

PROBLEM SUMMARY

USERS AFFECTED:
 IBM WebSphere Application server users of
JAX-WS web services applications.

PROBLEM DESCRIPTION:
Admin task "SETBINDING" fails to find
installed applications when there are
multiple security domains defined.

RECOMMENDATION:
 Install a fix pack that includes this APAR


When there are multiple security domains defined, setting the
policy set binding for an installed application may fail with
the following error:
ADMA0017E: The context for <application name> cannot be
obtained. The application does not appear to be installed.
at
com.ibm.ws.management.application.EditApplication.listModules(Ed
itApplication.java:882)
at
com.ibm.ws.management.application.AppManagementImpl.listModules(
AppManagementImpl.java:1066)
...
com.ibm.ws.policyset.admin.commands.util.PolicySetBindingCommand
Util.getServersForModule(PolicySetBindingCommandUtil.java:914)
at
com.ibm.ws.policyset.admin.commands.util.PolicySetBindingCommand
Util.getDomainsForModules(PolicySetBindingCommandUtil.java:817)
at
com.ibm.ws.policyset.admin.commands.util.PolicySetBindingCommand
Util.getBindingFile(PolicySetBindingCommandUtil.java:2745)
at
com.ibm.ws.policyset.admin.commands.util.PolicySetBindingCommand
Util.setBinding(PolicySetBindingCommandUtil.java:234)
at
com.ibm.ws.policyset.admin.commands.SetBinding.execute(SetBindin
g.java:300)
...

PROBLEM CONCLUSION:                                             
When there are multiple security domains, the operation to list 
the modules of the installed application failed because it      
couldn't find the corresponding application repository context. 
                                                                
The JAX-WS runtime has been updated to detect this scenario     
and to provide the correct application repository context in    
this scenario.                                                  
                                                                
The fix for this APAR is currently targeted for inclusion in    
fix pack 8.0.0.10.  Please refer to the Recommended Updates     
page for delivery information:                                  
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  
NOTE: Mark with an X the:
1) Release the fix applies to
2) The Editions that apply
3) And then DELETE THIS NOTE

Fix applies to Editions:
Release 8.0
__ Application Server (Express or BASE)
__ Network Deployment (ND)
__ Edge Components
__ Developer

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required.

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before applying the iFixes.  Restart WebSphere Application Server after applying the iFixes.

Directions to remove fix:  

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before removing the iFixes.  Restart WebSphere Application Server after removing the iFixes.

Directions to re-apply fix:  
1) Shutdown WebSphere Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: