IBM Support

JR41393: DOCSTORE_MOUNT.XML INBOUND PARAMETER DOES NOT WORK AS EXPECTED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • inbound parameter in the docstore_mount.xml file is not working
    as expected.
    
    When set inbound to no, according to infoCenter, files are
    exported to the file system from the docstore. However, when new
    files are added to the filesystem, they also appear in docStore.
    
    Steps to reproduce:
    
    1. Create 3 directory as show below
    
    /dir1/dir2/dir3
    
    2. Edit docstore_mount.xml file to add additonal lines as below
    
    <?xml version="1.0"?>
    <mnts>
        <mnt doc_path="/public_html/"
    real_path="$supplier_base_dir/" inbound="no" />
        <mnt doc_path="/ftp/" real_path="$supplier_ftp_dir/"
    inbound="yes" />
        <mnt doc_path="/dir1/"
    real_path="/usr/local/envs/sup3/dir1/" inbound="yes" />
        <mnt doc_path="/dir1/dir2/"
    real_path="/usr/local/envs/sup3/dir1/dir2/" inbound="yes" />
        <mnt doc_path="/dir1/dir2/dir3/"
    real_path="/usr/local/envs/sup3/dir1/dir2/dir3/" inbound="no" />
    </mnts>
    
    3. Enable mount manager in the common.properties file
    
    4. Start InfoSphere MDM Server for PIM and log in.
    
    5. Run a script to create a file under dir3.
    
    var writer = createOtherOut("/dir1/dir2/dir3/out.log");
    writer.println("This is test");
    writer.save("/dir1/dir2/dir3/out.log");
    writer.close("/dir1/dir2/dir3/out.log");
    
    6. This out.log file shows up in docStore and this file also
    synchronized to file system under the real_path.
    
    7. In the file system under dir3 folder, create a new file.
    
    8. Check the DocStore again in PIM and this newly created file
    is also reflected in DocStore, which is not working as expected.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Master Data Management Server for Product Information    *
    * Management implementations are affected by this issue.       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * inbound parameter in the docstore_mount.xml file is not      *
    * working                                                      *
    * as expected.                                                 *
    *                                                              *
    * When set inbound to no, according to infoCenter, files are   *
    * exported to the file system from the docstore. However, when *
    * new                                                          *
    * files are added to the filesystem, they also appear in       *
    * docStore.                                                    *
    *                                                              *
    * Steps to reproduce:                                          *
    *                                                              *
    * 1. Create 3 directory as show below                          *
    *                                                              *
    * /dir1/dir2/dir3                                              *
    *                                                              *
    * 2. Edit docstore_mount.xml file to add additonal lines as    *
    * below                                                        *
    *                                                              *
    * <?xml version="1.0"?>                                        *
    * <mnts>                                                       *
    *     <mnt doc_path="/public_html/"                            *
    * real_path="$supplier_base_dir/" inbound="no" />              *
    *     <mnt doc_path="/ftp/" real_path="$supplier_ftp_dir/"     *
    * inbound="yes" />                                             *
    *     <mnt doc_path="/dir1/"                                   *
    * real_path="/usr/local/envs/sup3/dir1/" inbound="yes" />      *
    *     <mnt doc_path="/dir1/dir2/"                              *
    * real_path="/usr/local/envs/sup3/dir1/dir2/" inbound="yes" /> *
    *     <mnt doc_path="/dir1/dir2/dir3/"                         *
    * real_path="/usr/local/envs/sup3/dir1/dir2/dir3/"             *
    * inbound="no" />                                              *
    * </mnts>                                                      *
    *                                                              *
    * 3. Enable mount manager in the common.properties file        *
    *                                                              *
    * 4. Start InfoSphere MDM Server for PIM and log in.           *
    *                                                              *
    * 5. Run a script to create a file under dir3.                 *
    *                                                              *
    * var writer = createOtherOut("/dir1/dir2/dir3/out.log");      *
    * writer.println("This is test");                              *
    * writer.save("/dir1/dir2/dir3/out.log");                      *
    * writer.close("/dir1/dir2/dir3/out.log");                     *
    *                                                              *
    * 6. This out.log file shows up in docStore and this file also *
    * synchronized to file system under the real_path.             *
    *                                                              *
    * 7. In the file system under dir3 folder, create a new file.  *
    *                                                              *
    * 8. Check the DocStore again in PIM and this newly created    *
    * file                                                         *
    * is also reflected in DocStore, which is not working as       *
    * expected.                                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * IBM recommends that customers facing the issue reported by   *
    * this APAR apply Master Data Management Collaboration Server  *
    * version 9.1.0-FP009 to gain resolution to this problem.      *
    ****************************************************************
    

Problem conclusion

  • A fix for this problem has been included in Master Data
    Management Collaboration Server version 9.1.0-FP009.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR41393

  • Reported component name

    MDM SERVER FOR

  • Reported component ID

    5724V5100

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-06

  • Closed date

    2013-06-19

  • Last modified date

    2013-06-19

  • 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

    MDM SERVER FOR

  • Fixed component ID

    5724V5100

Applicable component levels

  • R910 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS2U2U","label":"InfoSphere Master Data Management Collaboration Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
19 June 2013