PM16895: OSGI GA FEATURE PACK FAILED WHEN ATTEMPTED TO EXPOSE OSGI SERVICES AS SCA COMPONENTS.

APAR status

• Closed as program error.

Error description

• When the eature Pack for OSGi Applications and JPA 2.0 was
  attempted to expose OSGI services as Service Component
  Architecture (SCA) components, it failed.
  
  Getting the error below:
  
  com.ibm.wsspi.management.bla.op.OpExecutionException:
  CWSAM0105E: The following Service Component Architecture (SCA)
  Validation errors caused the CreateScaCodeGen step to fail: 2
  Service not found for component service: Component =
  GatewayEBAComponent
  Service = brokerService
  Service not found for component service: Component =
  GatewayEBAComponent
  Service = brokerService
  at
  com.ibm.ws.soa.sca.admin.cdf.content.operation.CreateScaCodeGen.
  createScaCodeGen(CreateScaCodeGen.java:246)
  at
  com.ibm.ws.soa.sca.admin.cdf.content.operation.CreateScaCodeGen.
  execute(CreateScaCodeGen.java:147)
  at
  com.ibm.wsspi.management.bla.op.compound.Phase.execute(Phase.jav
  a:151)
  

Local fix

• Work around has been provided to the customer to use extended
  version of the app which is application.mf v.1.0.0.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of both IBM WebSphere Application     *
  *                  Server V7 Feature Pack for Service          *
  *                  Component Architecture (SCA                 *
  *                  FeP), and Feature Pack for OSGi             *
  *                  Applications and JPA 2.0.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: When specifying                         *
  *                      implementation.osgiapp attribute        *
  *                      applicationVersion using a              *
  *                      non-normalized form the correct OSGi    *
  *                      application is not found.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Specifying implementation.osgiapp attribute applicationVersion
  using a non-normalized form in .composite file, for example:
  <scafp:implementation.osgiapp
          applicationSymbolicName="com.myosgi.application.eba"
          applicationVersion="1.0"/>
  
  fails, but when using the normalized form succeeds, for example:
  <scafp:implementation.osgiapp
          applicationSymbolicName="com.myosgi.application.eba"
          applicationVersion="1.0.0"/>
  

Problem conclusion

• The Feature Pack for SCA was changed to correctly use the
  normalized lookup method for determining the OSGi
  implementation version. With this fix you can specify the
  normalized or non-normalized applicationVersion.
  
  APAR PM16895 is currently targeted for inclusion in Service
  Level (Fix Pack) 1.0.1.7 of WebSphere Application Server v7
  Feature Pack for Service Component Architecture (SCA).  Please
  refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WAS SCA FEATURE

• Fixed component ID

  5724J0854

Applicable component levels

• R700 PSY

     UP