IBM Support

JR47823: ABSTRACT: MIGRATING INFLIGHT DATA WITH POLICY FILE FAILS ON UNIX

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Problem Description: When migrating running process instances
    using policy files on Unix systems, the xml validation will show
    success but will fail when attempting migrating the data.  The
    temporary file location which stores the policy file is
    incorrect during the migration. Hence, causing a failure as the
    policy file cannot be read.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of process instance migration using   *
    *                  BPM on AIX, UNIX or Linux.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: When trying to migrate active process   *
    *                      instances on AIX, UNIX or Linux, the    *
    *                      validation of the Orphan Token Policy   *
    *                      file will appear to be successful,      *
    *                      but the migration will fail.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When performing an instance migration using an orphan token
    policy file, the policy is first uploaded and stored in the
    temporary file store, then consulted later during the actual
    instance migration process. If the file is deleted or
    otherwise unavailable at the time the instance migration
    procedure actually executes, the instance migration process
    will not be successful. This is usually acceptable because
    users generally upload the policy file and immediately perform
    a migration.
    On Windows, System.getProperty("java.io.tmpdir") always seems
    to return a trailing slash, whereas UNIX-like operating
    systems can sometimes return a path without the trailing file
    component separator (slash or backslash).
    The root cause of this APAR is improper construction of the
    path string (using concatenation instead of the Java File API)
    and poor error handling (if the policy file is not found, no
    error is reported or logged, but the migration will be
    skipped).
    

Problem conclusion

  • Code changes have been made to properly construct the file
    paths, as it should in a cross-platform manner. An interim fix
    is available on v8.0.1.1. The fix will be integrated into the
    next fix pack.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR47823

  • Reported component name

    BPM EXPRESS

  • Reported component ID

    5725C9600

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-09-17

  • Closed date

    2013-10-10

  • Last modified date

    2013-10-10

  • 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 EXPRESS

  • Fixed component ID

    5725C9600

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTBX","label":"IBM Business Process Manager Express"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
10 October 2013