Error when after creating My Documents and shared repositories

[Former Member]

Hi all,

after setting up a fresh SAP Mobile Documents installation on NW 7.4 and creating the My Documents and shared repositories we see the message "repository not available" when logging in to the MCM User web interface. The NWA log shows the following errors:

Connection failed: Cannot access http://localhost:50000/cmis/json: Connection refused: connect

org.apache.chemistry.opencmis.commons.exceptions.CmisConnectionException: Cannot access http://localhost:50000/cmis/json: Connection refused: connect

Creating sharing home folder for user svcmcm failed: org.apache.chemistry.opencmis.commons.exceptions.CmisRuntimeException: org.apache.chemistry.opencmis.commons.exceptions.CmisConnectionException: Cannot access http://localhost:50000/cmis/json: Connection refused: connect

Testing the connection to http://localhost:50000/cmis/json in the destination sometimes yields a negative initial result, followed by consistently positive results.

Do you have any ideas or suggestions?

Regards

Daniel

[former_member192447 · Accepted solution]

Hi Daniel,

is there anything in the log file that might indicate what is the problem? Also can you check that what role the users has that you used for the destination in the connection configuration. The user need to have the Content Administrator Role.

Also you can check out this Quick Setup Guide to see if you missed some configuration step:

Best regards

Alex

[Former Member · Accepted solution]

Hi Alex,

thanks a lot; we are now able to connect and access Windows network shares after assigning the Content Admin Role to the MCM Users Group. We now however have the issue that our AD users can access all of the share's folders that the service user (assigned to the file system repository) has rights to. How can we enforce the individual user rights from the AD?

Regards

Daniel

P.S.: We are trying to use assertion tickets in this approach.

P.P.S.: We followed the preparatory steps under Integrating Documents from a Windows System into KM - Knowledge Management - SAP Library

Message was edited by: Daniel Hügelmann

[former_member192447 · Accepted solution]

Hi Daniel,

the Users Group of Mobile Documents should not have the Content Admin Role, only the User which is Used in the Destination need to have this role. If you use Assertion tickets you should have two destinations. One with <name> and one with <name>_User the one without the _User has a basic authentication and this user is the one that needs the content Admin Role.

How did you connect the Windows Network share to Mobile Documents? Which Connection Type did you use?

Best regards

Alex

[Former Member · Accepted solution]

Hi Alex,

our users cannot access the shares in Mobile Docs (Error in MCM User Web: "permissionDenied, undefined", Error in NWA log: "Problem while executing method: getChildren!") once we unassign the Content Admin Role from the Users Group. The service user still has that role, and is now the only one who can access the shares in Mobile Docs. It seems to us that all users require the Content Admin role. We used the two destinations as described by you, as well as the connection type "SAP Assertion Ticket Connection".

Best regards

Daniel

[former_member192447 · Accepted solution]

Hi Daniel,

just to understand you're setup. You have two repositories of type DBFS for MyDocuments and Sharing. and you have a corporate repository conected which is a windows file share?

Is that correct?

Best regards

Alex

[Former Member · Accepted solution]

Hi Alex,

yes, that is correct, we have the standard DBFS repositories and have connected several File System repositories. All can be accessed via web interface and app.

Regards

Daniel

[former_member192447 · Accepted solution]

Hi Daniel,

And the problem is only with the File System repositories right? The others are working if the users don't have the Content Admin Role right?

Best regards

Alex

[Former Member · Accepted solution]

Hi Daniel.

Assertion Ticket Connection does not make sense when you connect local KM repositories. Please use the local connection type. Ticket connections are useful for connecting remote KM servers.

Regards, Karsten

[Former Member · Accepted solution]

Hi Alex,

yes, that is correct.

Best regards,

Daniel

[Former Member · Accepted solution]

Hi Karsten,

thanks for your answer! So the assertion tickets are only necessary for SAP<->SAP and not for SAP<->Windows? How can we then set the sharing up so that each user can only access those directories in the share that he has the rights to?

Best regards,

Daniel

[Former Member · Accepted solution]

The application does that for you. When you create a DBFS repository, your content is on the file system and the metadata is in the database. Part of the metadata are also the ACL entries which the application sets. Of course when you work with windows fileshares, you should take care that only the application has access to the connected drives or folders and no other regular users.

When a user connects any Mobile Documents client for the first time, the server tries to create a folder for the user and sets the ACL so that only the user has permissions to access it. Therefore you use a Content Admin in the destination. This is the user that the application uses for the folder creation.

[Former Member · Accepted solution]

We do want to access normal Windows shared directories, with the possibility of their contents being altered by regular users. How would you suggest we connect those, as I assume that we cannot use the dbfs repository type?

[Former Member]

Ok, a CM Repository and FSB Mode seems to be the way to go here:

1. Create a network share or use an existing one
2. Create a directory on the Mobile Docs server for the versioning (if the share is on the server then do not place this directory inside it!)
3. Create the CM repository. Our settings:

Lastly, connect the share as a corporate repository in the MCM admin. We just reused the existing local connection here. Note that your share is on the Mobile Docs server; we are going to test connecting to a remote server using a network path next.

[Former Member]

Ok, we tested the connection of a remotely located share and the component monitor states:

Startup Error: folder '\\10.10.77.70\share' does not exist

We already entered the path as a network path with appropriate user credentials. We also created a local folder for the versioning.Apart from the paths and naming we used settings identical to those in my last post. Any ideas? Are we missing something?