Clarity

  • 1.  Error while uploading document using XOG

    Posted Mar 12, 2012 11:48 PM
    Hi ,

    I am getting an error when I try to XOG the documents.
    Error is "com.niku.union.odf.exception.ODFException: com.niku.dms.util.DMSException: Could not retrieve file from file store.
    We have Clarity 12.0.5 , it is running under local system account,

    We create a document in the file store first "/niku/clarity/filestore" and then read the document from there and upload it using xog (check the XOG input file).

    I have provided the input and output XOG xml. It is surprising that sometimes the file does get attached but it fails most of the time.

    XOG INPUT

    [XOG] PSR XOG Write: <?xml version="1.0" encoding="UTF-8"?>
    <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_customObjectInstance.xsd">
    <Header action="write" externalSource="NIKU"
    objectType="customObjectInstance" version="8.1.1"/>
    <customObjectInstances objectCode="ep_prj_statusrep">
    <instance instanceCode="PSR00937" objectCode="ep_prj_statusrep" parentObjectCode="project">
    <CustomInformation>
    <ColumnValue name="code">PSR00937</ColumnValue>
    <ColumnValue name="name">PSR @1</ColumnValue>
    <ColumnValue name="rpt_last_updated">2012-03-13T14:28:30</ColumnValue>
    <ColumnValue name="include_bulk_pdf">1</ColumnValue>
    <ColumnValue name="ep_report_history">
    <Documents>
    <Parent documentLocation="/niku/clarity/filestore">
    <Document name="PSR-14-Mar-2012-PR000462.pdf">
    <Version id="-1" versionNumber="1"/>
    </Document>
    </Parent>
    </Documents>
    </ColumnValue>
    </CustomInformation>
    <OBSAssocs completed="false"/>
    <Security/>
    </instance>
    </customObjectInstances>
    </NikuDataBus>

    XOG OUTPUT

    [XOG] PSR XOG Output: <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Header/>
    <soapenv:Body>
    <XOGOutput xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/status.xsd">
    <Object type="customObjectInstance"/>
    <Status state="SUCCESS"/>
    <Statistics failureRecords="1" insertedRecords="0"
    totalNumberOfRecords="1" updatedRecords="0"/>
    <Records>
    <Record>
    <KeyInformation>
    <column name="ep_prj_statusrep">PSR00937</column>
    </KeyInformation>
    <ErrorInformation>
    <Severity>FATAL</Severity>
    <Description>com.niku.union.odf.exception.ODFException: com.niku.dms.util.DMSException: Could not retrieve file from file store.</Description>
    </ErrorInformation>
    </Record>
    </Records>
    </XOGOutput>
    </soapenv:Body>
    </soapenv:Envelope>


  • 2.  RE: Error while uploading document using XOG

    Posted Mar 13, 2012 01:34 AM
    1. can you check the nsa settings for the two servers. they should be synchronised.
    2. also, check if you can create an nfs mount. this way, even if the doc is stored on one server, and the user is logged on the other one, when accessing the doc, the user will be pointed to where the doc is stored

    NJ


  • 3.  RE: Error while uploading document using XOG

    Posted Mar 13, 2012 02:09 AM
    Hi There is just one application server. The file store is a default one /niku/clarity/filestore set in NSA.
    Clarity runs using the local system account and this account has access to all system resources.


  • 4.  RE: Error while uploading document using XOG

    Posted Mar 13, 2012 03:48 AM
    how often do u run "Index contents and documents for searches" job ? (Purpose - Index contents (activities, events, discussions and action items) and documents into search collections)

    also, can u run the below commands ?

    nikuadmin search recreate-index-files -verbose

    nikuadmin search recreate-index-data -verbose


    NJ


  • 5.  RE: Error while uploading document using XOG
    Best Answer

    Posted Mar 13, 2012 12:30 PM
    You should not be manually writing or changing any files in the Clarity filestore location, instead you should have a separate staging location/folder on the server where the bg service is running and for the document to be consumed from there instead, and it will then create the file appropriately (with a different name and folder structure) in the filestore when it succeeds.

    Take a look at the sample files in the XOG client /xml folder which provide some examples that show this:
    C:\ProjectX\xog\xml>findstr /i /n /c:"parent doc" *
    change_write.xml:15:            <Parent documentLocation="/niku/xog/test/documentXogLocation/change">
    documents_write.xml:5:    <Parent documentLocation="E:\niku\8.1\build/xog/test/documentXogLocation" parentObjectId="1010" parentObjectType="KS">
    
    C:\ProjectX\xog\xml>
    The location and files chosen should have no permission issues for the user running the bg service to read from either.


  • 6.  RE: Error while uploading document using XOG

    Posted Mar 13, 2012 11:12 PM
    Hi ,

    As suggested we did the following:
    1) Ran Recreate index command and index synchrnisation job
    2) Changed the document location to a separate staging folder within the server (D:\Apps\Clarity\Temp). We now read the file from that staging area and try to xog it in.

    However both of these options do not work.

    NOTE: We are doing this on non production env. When we restore non prod with production database we do not copy the physical documents from production filestore to non production filestore. As a result documents are never copied. Due do think this might have a role to play?

    INPUT XML
    <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_customObjectInstance.xsd">
    <Header action="write" externalSource="NIKU"
    objectType="customObjectInstance" version="8.1.1"/>
    <customObjectInstances objectCode="ep_prj_statusrep">
    <instance instanceCode="PSR00950" objectCode="ep_prj_statusrep" parentObjectCode="project">
    <CustomInformation>
    <ColumnValue name="code">PSR00950</ColumnValue>
    <ColumnValue name="name">psr0001</ColumnValue>
    <ColumnValue name="rpt_last_updated">2012-03-14T12:00:02</ColumnValue>
    <ColumnValue name="include_bulk_pdf">1</ColumnValue>
    <ColumnValue name="psr_attachment">
    <Documents>
    <Parent documentLocation="D:\Apps\Clarity\Temp">
    <Document name="Walkthrough.doc">
    <Version id="1" versionNumber="1"/>
    </Document>
    </Parent>
    </Documents>
    </ColumnValue>
    </CustomInformation>
    <OBSAssocs completed="false"/>
    <Security/>
    </instance>
    </customObjectInstances>
    </NikuDataBus>


    OUTPUTXML

    <?xml version="1.0" encoding="UTF-8"?>
    <XOGOutput xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/status.xsd">
    <Object type="customObjectInstance"/>
    <Status state="SUCCESS"/>
    <Statistics failureRecords="1" insertedRecords="0"
    totalNumberOfRecords="1" updatedRecords="0"/>
    <Records>
    <Record>
    <KeyInformation>
    <column name="ep_prj_statusrep">PSR00950</column>
    </KeyInformation>
    <ErrorInformation>
    <Severity>FATAL</Severity>
    <Description>com.niku.union.odf.exception.ODFException: com.niku.dms.util.DMSException: Could not retrieve file from file store.</Description>
    </ErrorInformation>
    </Record>
    </Records>
    </XOGOutput>


    Regards,
    Sonali


  • 7.  RE: Error while uploading document using XOG

     
    Posted Apr 05, 2012 04:53 PM
    Hi All,

    Anyone have more input for Sonali?

    Thanks!
    Chris


  • 8.  RE: Error while uploading document using XOG

    Posted Apr 13, 2012 06:50 AM

    sonali1 wrote:

    NOTE: We are doing this on non production env. When we restore non prod with production database we do not copy the physical documents from production filestore to non production filestore. As a result documents are never copied. Due do think this might have a role to play?
    It may do, you're essentially running part of the system in a way it was never intended to handle, so the exact behaviour to expect in this case is going to be undefined and could alter from one version to another.

    A sql trace file (which works for XOG requests as much as it does for logging in through the UI) may shed some more light on the reason for it refusing to process, but existing documents being missing when they were expected to be present seems plausible, and it would be preferred if your refresh process would retain the expected levels of system integrity that your production system has.


  • 9.  Moving to XOG/GEL/WSDL Board

     
    Posted Mar 13, 2012 12:56 PM
    Moving to XOG/GEL/WSDL Board