IBM Support



You can track all active APARs for this component.


APAR status

  • Closed as program error.

Error description

  • When there is a subprocesses in a business process definition
    (BPD) and the process application is brought into IBM
    Integration Designer, refreshing and publishing fails with

Local fix

  • To avoid this issue, keep Advanced Integration services (AISs)
    in a toolkit, separate from projects that contain BPDs. That
    way, if BPDs are not called from advanced projects, only AIS
    projects must be imported into Integration Designer.
    Also, if projects contain BPDs must be imported into Integration
    Designer, such as when an SCA import is required to call a BPD,
    import the project into Integration Designer before creating

Problem summary

  • If a BPD contains a subprocess and is imported into Integration
    Designer before the advanced content has been generated, a
    duplicate WSDL error occurs during deployment.
    A change was made to generate WSDL files for subprocesses and
    the name of the WSDL was set to the same as the top-level BPD.
    As a result, the same WSDL file was generated more than once.
    The duplicate generation occurs only when advanced content is
    first added to a process app or toolkit.

Problem conclusion

  • A fix will be provided for IBM BPM V8.5.5 that prevents WSDL
    files from being created for subprocesses when advanced content
    is created first.
    On Fix Central (, search
    for JR51434:
     1. Select IBM Business Process Manager with your edition from
    the product selector, the installed version to the fix pack
    level, and your platform, and then click Continue.
     2. Select APAR or SPR, enter JR51434, and click Continue.
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    Note: For the duplicate WSDLs fix to work, all modules and
    libraries need to be disassociated from the Process Application,
    then re-imported into Integration Designer. This is so that the
    existing duplicate WSDLs will be deleted.
    To disassociate a project,
    1. In Integration Designer, in the Business Integration view,
    right-click the module and library projects associated with the
    Process Application (these steps can apply to a toolkit as
    well), and select Disassociate from Process Center. When all
    associated projects are disassociated, they will remain in the
    Integration Designer workspace, and the Process Application will
    be automatically published to the Process Center. The projects
    will no longer be contained in the Process Application in the
    2. If no artifacts were created and no generated artifacts were
    edited in the default projects, then this step can be skipped.
    The default projects are named <process_app_name>_Implementation
    and <process_app_name>_Library. If a Process Application is
    re-imported into Integration Designer in the future, keep in
    mind that these projects will be overwritten with newly created
    projects. Therefore, if you have added or modified any content
    in the default projects, then the changed or added artifacts
    must be saved to a separate location outside the Integration
    Designer workspace before re-importing the Process Application
    or toolkit. After importing (see step 5), the saved artifacts
    can be merged with the newly generated projects.
    3. Import the Process Application into Integration Designer. You
    will notice that there is an indication that the default
    projects will be recreated. When the Process Application is
    re-imported, WSDL and XSD files will be regenerated in the
    library project for each BPD and AIS interface.
    4. If there were other non-default projects associated with the
    Process Application that were left behind in the workspace, they
    can be reassociated now. Right click any previously
    disassociated module or library in the Business Integration
    view, and then select Associate with Process Center. The
    Associate with Process Center dialogue will open where you can
    select all modules that need to be re-associated with the
    Process Application.
    5. If no artifacts were created and no generated artifacts were
    edited in the previous default projects, then this step can be
    skipped. Merge the default projects that were saved outside the
    workspace in step 2 with the current default projects. This can
    be done manually or use a compare tool if available. To merge,
    copy the project root folders from the workspace to another
    folder in the file system. You can then compare the old and new
    projects to see what files were in the old projects and copy
    them back to the new ones eg: If you created a BPEL, the files
    for that would be missing from the generated project, and on
    comparing the projects, you will see a few BPEL-related files
    that need to be copied back. After merging, publish to the
    Process Center. The new projects will have the re-generated WSDL
     and XSD files (and other generated system files).

Temporary fix


APAR Information

  • APAR number


  • Reported component name


  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention


  • Submitted date


  • Closed date


  • Last modified date


  • 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


  • Fixed component ID


Applicable component levels

  • R855 PSY


  • R856 PSY


[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 October 2021