Topic
11 replies Latest Post - ‏2013-09-24T16:51:46Z by ChrisGloe
2KK0_Mathieu_Bernier
6 Posts
ACCEPTED ANSWER

Pinned topic Mixing Windows and Linux for Docs component ?

‏2013-09-19T09:13:44Z |

One quick question :

It possible to mix Operating Systems for Docs components ? For example, can we have the Conversion node on Windows and the others on Linux, or does everything has to be on either Linux or Windows ?

 

  • Alexey-Zimarev
    Alexey-Zimarev
    7 Posts
    ACCEPTED ANSWER

    Re: Mixing Windows and Linux for Docs component ?

    ‏2013-09-19T10:20:20Z  in response to 2KK0_Mathieu_Bernier

    Technically there are no obsticles to have hybrid environment. The only thing that is required in this case is NSF file share. But it is the same as for pure Linux deployment. In pure Windows you can live with Windows share (despite the documentation says otherwise).

    • OliverRegelmann
      OliverRegelmann
      3 Posts
      ACCEPTED ANSWER

      Re: Mixing Windows and Linux for Docs component ?

      ‏2013-09-19T22:47:55Z  in response to Alexey-Zimarev

      Did you manage to create a non-hybrid environment? According to the system requirements for example the conversion is only supported on Windows while Docs itself is only supported on RHEL.

      I wonder why there are install.bats for the Linux-only components, though.

      • Alexey-Zimarev
        Alexey-Zimarev
        7 Posts
        ACCEPTED ANSWER

        Re: Mixing Windows and Linux for Docs component ?

        ‏2013-09-20T07:00:59Z  in response to OliverRegelmann

        Yes, I did. Actually, Doc 1.0.3 has install.bat for all components. I also had Docs 1.0.2 on Windows only, I made install.bat myself. I had no Viewer though. Now I have everything.

  • 2KK0_Mathieu_Bernier
    6 Posts
    ACCEPTED ANSWER

    Re: Mixing Windows and Linux for Docs component ?

    ‏2013-09-19T10:29:35Z  in response to 2KK0_Mathieu_Bernier

    Ok thanks, now, knwoing that I have a strange behavior while trying to edit a PPT. On my Conversion server I get :

     

    [19/09/13 11:45:40:771 CEST] 00000067 ConversionSer I   CLFAE1221I: Submit conversion job: the sourceFilePath after transform: \data\IBMDocs\docsappdraft\default_org\draft\467\990\31e22adf-9120-4713-a238-c96def901e18\temp\upload\7b6ff12067ad1176ba6500ece2d31d72\contentfile.pptx
    [19/09/13 11:45:40:771 CEST] 00000067 ConversionSer I   CLFAE1221I: Submit conversion job: the targetFolderPath after transform: \data\IBMDocs\docsappdraft\default_org\draft\467\990\31e22adf-9120-4713-a238-c96def901e18\temp\upload\7b6ff12067ad1176ba6500ece2d31d72\concord
    [19/09/13 11:45:41:817 CEST] 00000068 ConversionSer I   CLFAE1221I: Submit conversion job: the sourceFilePath after transform: \data\IBMDocsViewerdefault_org\685\523\31e22adf-9120-4713-a238-c96def901e18\31e22adf-9120-4713-a238-c96def901e18\contentfile
    [19/09/13 11:45:41:817 CEST] 00000068 ConversionSer I   CLFAE1221I: Submit conversion job: the targetFolderPath after transform: \data\IBMDocsViewerdefault_org\685\523\31e22adf-9120-4713-a238-c96def901e18\31e22adf-9120-4713-a238-c96def901e18\pictures
    [19/09/13 11:45:44:047 CEST] 0000006c NFSFileUtil   I   failed to check directory existence by retry: 20 file: C:\data\IBMDocs\docsappdraft\default_org\draft\467\990\31e22adf-9120-4713-a238-c96def901e18\temp\upload\7b6ff12067ad1176ba6500ece2d31d72\concord
    [19/09/13 11:45:46:231 CEST] 0000006c NFSFileUtil   I   failed to check directory existence by retry: 20 file: C:\data\IBMDocsViewerdefault_org\685\523\31e22adf-9120-4713-a238-c96def901e18\31e22adf-9120-4713-a238-c96def901e18\pictures
     

     

    Path are wrong.

    Connections, Docs server, Viewer and Proxy are installed on Linux with 2 NFS shares (/data/IBMDocs and /data/IBMDocsViewer) hosted by the Connections server, and the Conversion on Windows 2008 R2.

    Viewer, Proxy, Docs server have the NFS shares correctly mapped

    Conversion server is able to map the NFS shares to Y: and Z:

     

    So I don't understand why he is trying to access files on this kind of path : \data\IBMDocsViewer

    which obviously won't work on a Windows systems.

     

    I've checked WebSphere variables, all json config files, nothing came up.

    • ChrisGloe
      ChrisGloe
      60 Posts
      ACCEPTED ANSWER

      Re: Mixing Windows and Linux for Docs component ?

      ‏2013-09-19T14:00:35Z  in response to 2KK0_Mathieu_Bernier

      1) Per the defined system requirements, a mixed environment is required: http://www-01.ibm.com/support/docview.wss?uid=swg27036813

      2) Couple things to check for this issue:

      - This type of error is usually caused by an incorrect setting in the cfg.properties for the path and/or systems as you were defining the location of the shared directories.  After the install, these are stored in the storage sections of the <CONVERSION_INSTALL_PATH>/config/conversion-config.json and are used to do the mount at application startup and to access the share.  Check those values and also review the conversion server's JVM SystemOut.log at startup to verify the mount is successful.  The fact that the NFSFileUtil log entries are showing c:\data\IBMDocs is also obviously wrong because it should be accessing them via Y or Z.

      - I'm noticing a missing backslash on the path to the source and target directories (for example, between IBMDocsViewer and default_org.  Verify that you aren't missing a slash in the path - this could be a bug in the logging but again something to check.   

      - If you want to provide your Storage section of the conversion-config.json if it doesn't jump out at you what is wrong, you can provide that here.

      • 2KK0_Mathieu_Bernier
        6 Posts
        ACCEPTED ANSWER

        Re: Mixing Windows and Linux for Docs component ?

        ‏2013-09-19T14:05:35Z  in response to ChrisGloe

        He is the content of my conversion-config.json :

         

        "shared_storage" :
        {
        "storage_server" : "lcn45-prod.intranet.novaliance.com",
        "shared_from" : "/data/IBMDocs",
        "shared_to" : "y:",
        "shared_from_viewer" : "/data/IBMDocsViewer",
        "shared_to_viewer" : "z:",
        "retry" : "-1",
        "timeo" : "-1"
        }
        • ChrisGloe
          ChrisGloe
          60 Posts
          ACCEPTED ANSWER

          Re: Mixing Windows and Linux for Docs component ?

          ‏2013-09-20T18:56:47Z  in response to 2KK0_Mathieu_Bernier

          Those look good based on what you've shown as your topology.  Couple of other items.

          1) What is the value for "repositoryPath" in the conversion-config.json file?

          2) What is the value for "folder" within the "concord-storage" section of the concord-config.json file?

          • 2KK0_Mathieu_Bernier
            6 Posts
            ACCEPTED ANSWER

            Re: Mixing Windows and Linux for Docs component ?

            ‏2013-09-23T12:24:19Z  in response to ChrisGloe

            Here are the answers :

             

            1) "repositoryPath": "C:/IBM/IBMConversion/data",

             

            2) "folder" : "/data/IBMDocs/docsapp/fake_filer"

             

            Regards

            • ChrisGloe
              ChrisGloe
              60 Posts
              ACCEPTED ANSWER

              Re: Mixing Windows and Linux for Docs component ?

              ‏2013-09-23T17:00:59Z  in response to 2KK0_Mathieu_Bernier

              Those look good.  So the remainder of items I can think of which you could have misconfigured (or got messed up during an earlier deployment attempt or something are):

              WebSphere Environment Variables:

              DOCS_SHARE

              DOCS_SHARED_DATA_NAME

              DOCS_SHARED_DATA_ROOT

              VIEWER_SHARE

              VIEWER_SHARED_DATA_NAME

              VIEWER_SHARED_DATA_ROOT

              Also, the log you provided appears to be from an attempt to do a View on the document as opposed to an Edit.  You should check the following values from your Viewer deployment (from cfg.properties and then updated during the deployment in viewer-config.json):

              shared_data_dir (needs to point to your viewer share as accessed from the viewer node)

              Also, all owner and authority information has to be correct on the docs and viewer shares as documented in the installation guide:

              http://www-10.lotus.com/ldd/docswiki.nsf/xpDocViewer.xsp?lookupName=Installing+and+deploying+IBM+Docs+1.0.3+documentation#action=openDocument&res_title=Configuring_a_shared_data_folder_id103&content=pdcontent

              If this does not help you find the error, you will likely need to work through your channel rep to get assistance from IBM support.

              • 2KK0_Mathieu_Bernier
                6 Posts
                ACCEPTED ANSWER

                Re: Mixing Windows and Linux for Docs component ?

                ‏2013-09-24T16:06:23Z  in response to ChrisGloe

                I have these :

                DOCS_SHARE = /data/IBMDocs/docsapp 

                DOCS_SHARED_DATA_NAME = DOCS_SHARE  

                DOCS_SHARED_DATA_ROOT = //10.96.31.12/data/IBMDocs  

                VIEWER_SHARE = /data/IBMDocsViewer  

                VIEWER_SHARED_DATA_NAME = VIEWER_SHARE  

                VIEWER_SHARED_DATA_ROOT = //10.96.31.12/data/IBMDocsViewer  

                 

                Does it look good to you regarding what I have sent to you already ?

                 

                • ChrisGloe
                  ChrisGloe
                  60 Posts
                  ACCEPTED ANSWER

                  Re: Mixing Windows and Linux for Docs component ?

                  ‏2013-09-24T16:51:46Z  in response to 2KK0_Mathieu_Bernier

                  No that does not look correct.  I would expect something like the following:

                  DOCS_SHARE = y:

                  DOCS_SHARED_DATA_NAME = DOCS_SHARE  

                  DOCS_SHARED_DATA_ROOT =/data/IBMDocs  

                  VIEWER_SHARE = z: 

                  VIEWER_SHARED_DATA_NAME = VIEWER_SHARE  

                  VIEWER_SHARED_DATA_ROOT = /data/IBMDocsViewer 

                  (Assuming you are using IBM Docs 1.0.3)