PJ40988: ENABLING SSI TRACING REQUIRES CREATING A TRIGGER FILE ON THE CE APP SERVER RATHER THAN USING FEM

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Customer had issues with Image Services (IS) server which caused
    CFS-IS to hang.  This problem was later determined to be caused
    by a hardware failure.
    
    However, to troubleshoot this issue, the SSI subsystem tracing
    was modified such that enabling/disabling SSI trace would not
    require a CE restart and could be done via FileNet Enterprise
    Manager. This makes it easier to collect SSI debug data.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Customers diagnosing connection issues between Content       *
    * Engine and Image Services                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Customers diagnosing connection issues between Content       *
    * Engine and Image services that required enabling SSI tracing *
    * were required to create a trigger file on the Content Engine *
    * application server's file system and restart the Content     *
    * Engine server.  This was not consistent with the tracing     *
    * mechanism used by other Content Engine subsystems, which was *
    * done through FileNet Enterprise Manager and did not require  *
    * an application server restart to take affect.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Content Engine 4.5.1.8-P8CE-FP008 or later.       *
    ****************************************************************
    

Problem conclusion

  • Content Engine 4.5.1.8-P8CE-FP008 and later enables the Content
    Engine SSI subsystem tracing to be enabled by FileNet Enterprise
    Manager without an application server restart.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ40988

  • Reported component name

    CONTENT ENGINE

  • Reported component ID

    5724R8101

  • Reported release

    450

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-13

  • Closed date

    2014-04-21

  • Last modified date

    2014-04-21

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

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

    PJ40990 PJ40991 PJ41076

Fix information

  • Fixed component name

    CONTENT ENGINE

  • Fixed component ID

    5724R8101

Applicable component levels

  • R451 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

FileNet P8 Platform
Content Engine

Software version:

450

Reference #:

PJ40988

Modified date:

2014-04-21

Translate my page

Machine Translation

Content navigation