JR42914: SERVICEDEPLOY PRODUCES INCOMPLETE WAR FILE WHEN CUSTOM DIRECTORY LAYOUT IS USED

Version 7.5.1 Fix Pack 1 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• ServiceDeploy produces incomplete war file when custom directory
  layout is used
  

Local fix

• use IID to export EAR
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of ServiceDeploy deploying            *
  *                  applications                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: ServiceDeploy produces incomplete war   *
  *                      file when custom directory              *
  *                      layout is used                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Customer migrated their application from WPS 6.2.0.2 to BPM
  7.5.1, and they're trying to build application from command
  line using the WPS serviceDeploy tool. This is the way that
  customer have done unattended overnight builds ever since they
  started using WPS.
  The application can not be built via serviceDeploy.
  The customer need an automated process for their builds, hence
  the desire to use serviceDeploy.
  

Problem conclusion

• A program fix has been provided.
  Please also check the guidance based on how serviceDeploy is
  made to perform:
  .
  Binary libraries should be packaged as a BPM Library and added
  as a dependency of the module whenever possible. If a
  dependency is limited to use by a web module, it can be
  included in the web module's WEB-INF/lib directory. Using BPM
  Libraries has an added benefit of allowing flexibility in the
  way these binaries are deployed. For example, if this library
  is set to "global" the binary dependency jars will not be
  included in the EAR file and can instead by added as a
  shared library. This potentially improves deployment time as
  less bytes are moved on disk, but also saves on memory
  footprint at runtime. Changing the value to away from "global"
  will result the jar files being packaged with the module.
  .
  The preferred method of adding project dependencies is using
  the BPM dependency editor. The Eclipse project editor should be
  avoided for BPM project dependencies. This includes adding
  project references or external jar dependencies.
  .
  As a convenience, Web modules can be included in the produced
  ear file using the BPM dependency editor. As mentioned above,
  web module dependencies should be included in the WEB-INF/lib
  directory, but the BPM Library mechanism is preferred.
  .
  Based upon this general advice, the binary dependencies of the
  adaptivedesktop war should be moved to a BPM Library if
  possible. If these dependencies only apply to the
  adaptivedesktop web application, they should instead be
  included in the WEB-INF/lib directory of that project. Since
  the core project is also a binary dependency of the web
  application, it too should be packaged either into a BPM
  library or the WEB-INF/lib directory of the adaptivedesktop
  web application.
  .
  

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

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R750 PSY

     UP