Bookshelf Home | Contents | Index | PDF |
Siebel Content Publishing Guide > Content Asset Management > About Configuring Content Asset ManagementContent assets can be added to the Content Center repository by specifying a filename on a shared directory or by specifying a URL. In both cases, files that are linked-to from the specified file or URL can be imported by selecting to Follow Links. When shared network files are imported to the Content Center repository in this way, the permissions for the directory access are those of the server process account. Because the server process account typically has more extensive privileges than the user, there is a security risk of users importing content from directories to which they do not have access. To prevent this, importing from shared directories has been disabled except for those directories that are listed in the contentbase.ini file. It is recommended that you limit this list of allowed directories to a set that you can easily monitor and manage. On the Windows platform, the contentbase.ini file can be found in ImportFilePath=SiebelContentShare For example, if the ImportFilePath parameter is set to However, you cannot import files from the following directories: NOTE: The network path is interpreted relative to the server machine, not the client machine. Therefore, local paths like If you use the default (out-of-the-box) contentbase.ini file, the administrator or individual users need to set up one or more shared directories named SiebelContentShare to contain those files (and those files that are referenced by the specified files) that they want to import as content assets. When downloading some file types, Internet Explorer looks at the extension .swe and is not able to invoke the correct application even though the Content Type headers being passed to Internet Explorer are correct. Set the values of those MIME types here as true. The name/ext in the Internet Explorer pop-up will show up correctly. |
Siebel Content Publishing Guide |