on 11-07-2006 3:24 PM
Hi everyone
I'm currently involved in a SAP Enterprise Portal project where we among other things are utilizing KM.
One of my customer's requirements are that we integrate an existing fileshare into KM. This fileshare is currently at ~200 GB and is still growing.
Since this is an existing fileshare we are planning on creating a file system repository manager for integrating it into KM.
To verify that this will actually work I have been trying to find any information regarding limitations of file system repositories in KM, but thus far without any luck. It would be greatly appreciated if anyone could point me in the direction of such documentation.
Additionally it would be great if anyone could share their experiences with large file system repositories.
Thanks in advance
Best regards,
Svein Gunnar Standnes
Hello Svein,
Namespace Restrictions for Resource Names
· Maximum length of resource names:
FSDB: Restrictions of the file system are valid (Windows: 255 characters)
DBFS and DB: 448 characters
· Maximum length of path (URI without prefix):
FSDB: Restrictions of the file system are valid (Windows: 255 characters)
DBFS and DB: No restriction
· Permitted characters in resource names:
FSDB: Restrictions of the file system are valid (Unicode or Windows)
DBFS and DB: All Unicode characters, but restrictions may exist for some components of the repository framework.
Do not put a full stop/period at the end of the resource name.
Database Restrictions
There are the following restrictions for the databases used:
● Maximum number of resources (folders, documents) in a repository instance:
FSDB: No restriction (possibly limited by file system restrictions)
DBFS and DB: 2,147,483,648
● Maximum size of an individual resource:
FSDB: No restriction (possibly limited by file system restrictions
DBFS: 8 exabytes (MS SQL Server 2000), 2 GB (Oracle)
DB: 2 GB
Maximum length of large property values (string type): 2,147,583,647 bytes (2 GB).
Hope this helps,
Axel
-
-
please keep rewarding points to helpful answers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Svein,
Hm - Axel's info is not about FS repositories, but about CM repositories of different types (FSDB/DBFS/DB).
@Axel: In general I personally prefer pasting the link to the documentation - that makes it easier for the questionner to gather further information once he has found the help.sap.com source (and at the same time, it doesn't look like somebody has typed a novel... and the original layout also often is much more readable). No offence!
Hope it helps
Detlev
Hi Svein,
Check out http://help.sap.com/saphelp_nw04/helpdata/en/e3/92322ab24e11d5993800508b6b8b11/frameset.htm and around - there the prerequisites as well as some restrictions are listed, like:
+The following functions are not supported:
· Locking documents
· Creating links
· Using predefined properties
· Versioning+
Hope it helps
Detlev
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Detlev
Thank you for your prompt reply.
help.sap.com has been very helpful when starting out creating repositories, but unfortunately I have not been able to find any information about limitations regarding things like file repository size, the number of files in a folder, nor general experiences/best practices for working with large file-based repositories.
If you could point me in the direction of such information it would be greatly appreciated.
Best regards
Svein Gunnar Standnes
Hi Svein,
> limitations regarding things like file repository size,
> the number of files in a folder,
As Julian wrote:
> whatever the filesystem supports
There are no further restrictions on KM side.
Hope it helps
Detlev
PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.