Retrieve ACLs from a Netware File System

This section describes how to retrieve Netware ACLs for files retrieved from a Netware file system.

Requirements

  • To retrieve files from a Netware file system, the connector must be installed on a machine running Windows. You must also install the Novell client on the connector machine. This allows the connector to access the Netware server.
  • Run the connector's Windows service as a user who has administrative permissions on the connector machine.

  • It is possible to retrieve files from an NT file system and a Netware file system using the same fetch task. However, to retrieve Access Control Lists for the documents you must use separate fetch tasks. For example:

    [FetchTasks]
    Number=2
    0=MyTask
    1=Netware
    MappedSecurity=True
    
    [MyTask]
    // Task for extracting files from an NT file system
    DirectoryPathCSVs=\\server.domain.com\folder,\\server.domain.com\anotherfolder
    				
    [Netware]
    // Task for extracting files from Netware
    DirectoryPathCSVs=\\netware\sys\public
    NetwareServer=10.0.0.7
    NetwareUsername=CN=ADMIN.O=ORG
    NetwarePassword=password			
  • The NetwareUsername parameter must be set and must contain a distinguished name, for example:

    NetwareUsername=CN=ADMIN.O=ORG

  • The DirectoryPathCSVs configuration parameter must be configured using a full path, for example:

    DirectoryPathCSVs=\\netware\sys\public

  • To ensure that CFS has access to the files retrieved from a Netware file system, it might be necessary to make a temporary copy of the files by setting the IngestSharedPath parameter. For example:

    [Ingestion]
    IngestSharedPath=\\server\IngestShared\

Troubleshooting

If the connector fails with the following error, this usually indicates that the value specified for the NetwareUsername configuration parameter is not known or is not a valid distinguished name:

<TASK>: Netware error 889a (NWDSLogin)
Failed to complete <ACTION> for task '<TASK>' [<TOKEN>]: Netware initialization or logon failed