Creating documents with SCMS_DOC_URL_CREATE in SAP Content Server

Hi there,
I have a Problem here with the Knowledge Provider concerning SCMS_DOC_URL_CREATE and hope anyone could help me out.
For a SAP Records Management document I am calling BAPI_SRM_DOC_CREATE and get a LOIO and a PHIO ID for my new document. The PHIO-ID I pass to SCMS_DOC_URL_CREATE which then creates the URL to put the file on a SAP Content Server with a 3rd party tool. That works totally fine and I can see the file on the Content Server with its metadata,
Unfortunately SAP Records Management doesn't recognize that a file has been uploaded. When I open the file in the transaction ORGANIZER it has no content and no components.
Is there any function call I am missing to tell the Records Management document that I have uploaded something?
All is working fine when I get the uploaded content into NetWeaver with SCMS_GET... and call BAPI_SRM_CHECKIN_DOCUMENT. But of course this is not what I want (transferring the file directly in the local network area where the content server stands, then getting it back to NetWeaver and back again to the content server).
Any help would really be appreciated.
Thank you
Marcus

Answer: because SCMS_DOC_URL_CREATE is not remote enabled by default.

Similar Messages

How to see documents checked-in to SAP Content Server ?

Hi ,
I'm not sure if this is the right forum for this question but I did not find anything more pertinent.
We have a scenario in ECC 5.0 which we are attaching PDF/etc document to SAP DMS Document records in Tcode CV01N/CV02N . Subsequently we check-in those originals to the SAP Content Server. All this is working just fine as the underlying settings for the content repository in Tcode CSADMIN is appropriately set.
Is there a way to monitor how many and which documents have been checked in to the SAP COntent server. In the 46C/47 days, we used to go to Tcode OAAD and get a count & list of all documents that have been shipped to a content repository. In the scenario for SAP Content server, I'm unable to use this tcode to get the information.
Is there another tcode that will give me the information on the documents linked to the Content Server ?
Your help is greatly appreciated.
Thanks,
Vipin

Hi to add more...
On service Market Place....
Go with the below path
Installations and Upgrades --> " SAP Application Components" --> SAP EASY DOCUMENT MANAGEMENT" ---> SAP EASY DOCUMENT MGMT 6.00.
Thanks,
Tanuj

Webi Hyperlink to SAP Content Server

Hi folks,
My customer is trying to use a hyperlink;
http://opentext.samca.net:8080/archive?get&pVersion=0045&contRep=D1&docId=4945274BD42AD25FE10000000AC819E6
in his Webi report to launch a document stored on his SAP Content Server.
However the url will not parse in Webi because the u2018HTTP ver 4.5 for Content Serveru2019 expects a method as a first parameter, whilst in standard HTTP protocol the option of passing a parameter is not covered.
Is there any way around this, the url above has to be specified this way to comply with the SAP Content Server?
Kind regards,
John

John,
In WebI:
Drag and Drop: Free-standing cell, Blank cell, in that paste the URL. And change cell properties of "Read Cell content as" -- Hyperlink.
Thank You!!

Open/edit documents on SAP Content Server from BW?

Hi guys
I have been asked to investigate whether this scenario is possible.
Today we have a SAP Content Server where we save attachments to different kinds of objects. An example could be that we open appropriation request 'S-00123' from IMA11 and attach two different MS Word documents.
In BW I have created several reports that contain these appropriation requests and we would like to be able to attach/edit the files on the content server from the BW report.
Is this somehow possible using RRI or some other functionality?
Might it even be possible by using GoTo --> Documents with the appropriate setup?
BR
Stefan

Hello Friends,
Any luck??
Thank you,
Nikee

Document Migration from CRM to SAP Content Server

We are going live with SAP CRM 7.0 next week. CRM team configured some of applications like ITSM, Change Request Management and Transport Request database also as part of implementation.
We got last minute requirement that CRM team would like to go-live with current configuration with current configuration and eventually they would like to migrate all documents to Content server.
We do not have content server in place yet and planning to implement sometime in Feb. I am trying to explore ways how we can export existing documents created in CRM and migrate to Content server and link it.
Any ideas/Suggestions?
Thanks,
Miral.

In which repository are the documents currently stored in CRM? Please see if Note 688241 on 'Relocating large SAP Content Server Repositories' could be of any assistance to you.
Regards,
Pradeepkumar Haragoldavar

Https access to Sap Content Server 620 with R/3 46C

We are trying to access the Sap Content Server 620 via Https.
We do not want to administer it via HTTPS, (as we know CSADMIN doesn't support Https in rel. 46C as for note 712332). We want to do in way that the users when do check-in/out of originals these go across the
network using Https instead Http.
According note 712330 it should be possible.
Anyone already did it ?
Any suggestions ?
NOte 506314 is not clear. We are in doubt how we applyed it.
What we did:
0)activate the SSL on the Sap COntent Server Web Site, requiring and installing a CA certificate.
1)On the R/3 server in tx OAC0 with %HTTPS filled up the
two boxes with "%HHTPS
required"
1)unpacked the Sap criptolibrary and copied all the files (including those in ntintel subdirectory created during the unpacking) under c:\Programmi\Sap\Frontend\Sapgui on a frontend PC.
2)set the env. variable SAPHTTP=c:\Programmi\Sap\Frontend\Sapgui on
Frontend PC
3) from c:\Programmi\Sap\Frontend\Sapgui we created both the SAPSSLC.pse and the SAPSSLS.pse file with the command :
3) from c:\Programmi\Sap\Frontend\Sapgui we created both the
SAPSSLC.pse and the SAPSSLS.pse file with the command :
sapgenpse get_pse -noreq -p C:\Programmi\SAP\FrontEnd\SAPgui\<PSE-NAME>
CN=localhost
4) we run the test: saphttp https://itmif069
from the frontend to the server where the Content Server is (itmif069). We recive the error:
trc file: "dev_http", trc level: 2, release: "620"
Fri Oct 08 12:26:46 2004
[2256] sccsid: @(#) $Id: //bas/620/src/krn/ftp/http.c#26 $ SAP
[2256] HTTP Start : argc - 2 a0 - saphttp
[2256] https//itmif069
[2256] SECUDIR=C:\Programmi\SAP\FrontEnd\SAPgui
<<- SapSSLSetTraceFile()==SAP_O_K
=================================================
= SSL Initialization
SapISSLComposeFilename(ssl_lib): using default "sapcrypto.dll"
SapISSLComposeFilename(server_pse): using default "SAPSSLS.pse"
SapISSLComposeFilename(client_pse): using default "SAPSSLC.pse"
SapISSLComposeFilename(anon_pse): using default "SAPSSLA.pse"
= found SAPCRYPTOLIB 5.5.5C pl16 (Jun 10 2004) MT-safe
= found SECUDIR environment variable
= using SECUDIR=C:\Programmi\SAP\FrontEnd\SAPgui
= secudessl_Create_SSL_CTX(): PSE "SAPSSLA.pse" not found,
=      using PSE "SAPSSLC.pse" as fallback
= The Server SSL_CTX
=    provides this ordered list of 9 ciphersuites:
=       1. SSL_RSA_WITH_RC4_128_SHA
=       2. SSL_RSA_WITH_RC4_128_MD5
=       3. SSL_RSA_WITH_3DES_EDE_CBC_SHA
=       4. SSL_RSA_WITH_DES_CBC_SHA
=       5. SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
=       6. SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5
=       7. SSL_RSA_EXPORT_WITH_RC4_40_MD5
=       8. SSL_RSA_WITH_NULL_SHA
=       9. SSL_RSA_WITH_NULL_MD5
= Success -- SapCryptoLib SSL ready!
=================================================
<<- SapSSLInit(, read_profile=0)==SAP_O_K
ERROR => [2256] URI https//itmif069 [http.c       774]
ERROR => [2256] Connect to Host Port 443 error: NIECONN_REFUSED
[http.c       777]
We do not know if the criptolibrary ha to be instyalled to the R/3 server to.
We do not know if the CA certificate instalelled on the Sap COntent Server web site has to be installed on the R/3 server too.
Any suggestion ?
Regards

Caro Mauro,
I'm more or less in the same situation right now.
Taking into account that you ask for help on this subject last 2004 Oct. I suppose that you have probably solved the problem.
Please can you help me with the solution implemented.
Find below my current work e-mail adress
[email protected]
Thanks in advance,
Best regards, Xavier Grau.

Storing Documents on SAP Content Server

Dear Support,
We are configured the ERP 2005 server to store the attachments onto the SAP Content Server.
Unfortunately,the attachments are not storing on the content server . don't know where they were storing.
We have configure the system using the OAC0 and OAC2, and OAC3 to use the "S1" repository. The repository conected to the SAP Content Server over HTTP connection and the connection test is successful.
We have also, configured and exchanged the tickets with SAP Content server and the SAP ERP 2005 system.
Kindly let us know the issue...
Thank you,
Nikee

Hello Friends,
Any luck??
Thank you,
Nikee

Integrate DMS / SAP Content Server 6.40 with EP

Hello ,
With reference to [DMS Installation |DMS Installation; integrate DMS / SAP Content Server 6.40 with EP to access EP PCD .
Regards ,
Santosh

You can integrate the portal with DMS/CMS by using the DMS connector or DMS repository manager. The DMS repository manager can be dowloaded from sap service marketplace
See threads for more information
DMS Integration in EP
Content Server 6.3 integrate with Portal 6.0 possible?
Points are welcome if it is useful
Koti Reddy

Storing of MSDS in SAP Content Server - Part2

Hi Friends,
I already raised this issue in link given below.
Storing of MSDS in SAP Content Server
Ealier I did not tried this as we did not received the hardaware,
Now I did configuration as per the note " 1408009 - Settings for EH&S Product Safety documents" for SAP EHS document Type.
But when I try to generate report, its giving me error as given below.
Check Document Type SBR
Internal error in function C14SX_DOCUMENT_ORIGINAL_PUT (exception 0)
Saving document data has failed
Error while checking in and storing: report.rtf
Can you guys help me if any more configurations are needed or am I missing something. The content Server is of OpenText and not SAP Content Server.
Thanks.
With Warm Regards
Mangesh Pande

HI Mangesh,
Try to figure out if it is only DMS related - or if it is something wrong with the EH&S part of the setup:
Create an SBR Document manually via CV01n.
If this fails - at least the DMS Setup is wrong.
If this works - DMS settings should be fine and the problem is on EH&S side.
Check the Application log for errors as well - there might be more details in there.
Greets
Mark

FMX2 - earmarked funds and SAP Content server

Hello all,
Need a help to find solution for the following issue.
Customer would like to have earmarked funds attachments save on SAP Content server u201Eout of databaseu201C.
So in detail, customer run FMX2 change document and from menu choose Environment > Object list > create attachments
Attachment is save on DB, so question is how to change this to save attachments on SAP Content server. And what is need to set up at transaction OAC3 to which Object type and document type is for attachment at FMX2.
SAP Content server is up and running also we have repositories u2013 this is not issue. Issue is only to fill in data at OAC3 with correct object type and doc. Type.
Thanks for any help
Peter

Hi, it's better to ask from basis team. In table maintained link between Document type and 'place' where you want to save your documents, it's not FM customizing

SAP Content Server error

Hello colleagues,
I have this error when start the Content Server,
host:(/directory/apache/bin)(root)#./apachectl start
httpd: Syntax error on line 66 of /directory/apache/conf/httpd.conf: Cannot load modules/mod_sapcs22.so into
server: /directory/apache/modules/mod_sapcs22.so: undefined symbol: ap_log_error
Can you help me?
Thanks

Hi Reagan,
Execute the first parameter,
rgqaserp:(/sapcontreps/apache/modules)(root)#cat /sapcontreps/apache/conf/httpd.conf
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
# for a discussion of each configuration directive.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/access_log"
# with ServerRoot set to "/usr/local/apache2" will be interpreted by the
# server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log"
# will be interpreted as '/logs/access_log'.
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used. If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
ServerRoot "/sapcontreps/apache"
# Mutex: Allows you to set the mutex mechanism and mutex file directory
# for individual mutexes, or change the global defaults
# Uncomment and change the directory if mutexes are file-based and the default
# mutex file directory is not on a local disk or is not appropriate for some
# other reason.
# Mutex default:logs
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#Listen 12.34.56.78:80
Listen 1090
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule sapcs_module modules/mod_sapcs22.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_socache_module modules/mod_authn_socache.so
LoadModule authn_core_module modules/mod_authn_core.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
#LoadModule authz_dbd_module modules/mod_authz_dbd.so
LoadModule authz_core_module modules/mod_authz_core.so
LoadModule access_compat_module modules/mod_access_compat.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_form_module modules/mod_auth_form.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule allowmethods_module modules/mod_allowmethods.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cache_disk_module modules/mod_cache_disk.so
#LoadModule cache_socache_module modules/mod_cache_socache.so
#LoadModule socache_shmcb_module modules/mod_socache_shmcb.so
#LoadModule socache_dbm_module modules/mod_socache_dbm.so
#LoadModule socache_memcache_module modules/mod_socache_memcache.so
#LoadModule macro_module modules/mod_macro.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule dumpio_module modules/mod_dumpio.so
#LoadModule buffer_module modules/mod_buffer.so
#LoadModule ratelimit_module modules/mod_ratelimit.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule request_module modules/mod_request.so
#LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule sed_module modules/mod_sed.so
LoadModule mime_module modules/mod_mime.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_debug_module modules/mod_log_debug.so
#LoadModule logio_module modules/mod_logio.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
#LoadModule remoteip_module modules/mod_remoteip.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
#LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_express_module modules/mod_proxy_express.so
#LoadModule session_module modules/mod_session.so
#LoadModule session_cookie_module modules/mod_session_cookie.so
#LoadModule session_dbd_module modules/mod_session_dbd.so
#LoadModule slotmem_shm_module modules/mod_slotmem_shm.so
#LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so
#LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so
#LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so
#LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so
LoadModule unixd_module modules/mod_unixd.so
#LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule info_module modules/mod_info.so
#LoadModule cgid_module modules/mod_cgid.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
#LoadModule actions_module modules/mod_actions.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
#LoadModule rewrite_module modules/mod_rewrite.so
<IfModule unixd_module>
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
User daemon
Group daemon
</IfModule>
# 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin [email protected]
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If your host doesn't have a registered DNS name, enter its IP address here.
#ServerName www.example.com:80
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
<Directory />
    AllowOverride none
    Require all denied
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "/sapcontreps/apache/htdocs"
<Directory "/sapcontreps/apache/htdocs">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   AllowOverride FileInfo AuthConfig Limit
    AllowOverride None
    # Controls who can get stuff from this server.
    Require all granted
</Directory>
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
<IfModule dir_module>
    DirectoryIndex index.html
</IfModule>
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<Files ".ht*">
    Require all denied
</Files>
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "logs/error_log"
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
<IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "logs/access_log" common
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "logs/access_log" combined
</IfModule>
<IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL. You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client. The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "/sapcontreps/apache/cgi-bin/"
</IfModule>
<IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock cgisock
</IfModule>
# "/sapcontreps/apache/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/sapcontreps/apache/cgi-bin">
    AllowOverride None
    Options None
    Require all granted
</Directory>
<IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For type maps (negotiated resources):
    #AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#MIMEMagicFile conf/magic
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults: EnableMMAP On, EnableSendfile Off
#EnableMMAP off
#EnableSendfile on
# Supplemental configuration
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.
# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf
# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf
# Language settings
#Include conf/extra/httpd-languages.conf
# User home directories
#Include conf/extra/httpd-userdir.conf
# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
# Virtual hosts
#Include conf/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
# Various default settings
#Include conf/extra/httpd-default.conf
# Configure mod_proxy_html to understand HTML4/XHTML1
<IfModule proxy_html_module>
Include conf/extra/proxy-html.conf
</IfModule>
# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
# uncomment out the below to deal with user agents that deliberately
# violate open standards by misusing DNT (DNT *must* be a specific
# end-user choice)
#<IfModule setenvif_module>
#BrowserMatch "MSIE 10.0;" bad_DNT
#</IfModule>
#<IfModule headers_module>
#RequestHeader unset DNT env=bad_DNT
#</IfModule>
<IfModule mod_sapcs.cpp>
AddModuleInfo ContentServer "SAP Content Server 640/0 (Prototype) (C) SAP AG 1998, 2001"
CSConfigPath /sapcontreps/conf/cs.conf
<Location /sapcs>
SetHandler sapcs_module
Allow from all
</Location>
<Location /ContentServer/ContentServer.dll>
SetHandler sapcs_module
Allow from all
</Location>
<Location /contentserver/contentserver.dll>
SetHandler sapcs_module
Allow from all
</Location>
</IfModule>
Second parameter,
rgdeverp:(/sapcontreps/apache/modules)(root)#ls -la /sapcontreps/apache/modules
total 5544
drwxrwxrwx 2 sapcs sapsys   4096 Jun 12 15:46 .
drwxrwxrwx 15 sapcs sapsys   4096 Jun 12 14:56 ..
-rwxrwxrwx 1 sapcs sapsys 13836 Jun 12 14:54 httpd.exp
lrwxrwxrwx 1 sapcs sapsys     34 Jun 12 15:46 libsapsecu.so -> /sapcontreps/modules/libsapsecu.so
-rwxrwxrwx 1 sapcs sapsys 34756 Jun 12 14:56 mod_access_compat.so
-rwxrwxrwx 1 sapcs sapsys 31861 Jun 12 14:56 mod_actions.so
-rwxrwxrwx 1 sapcs sapsys 44418 Jun 12 14:56 mod_alias.so
-rwxrwxrwx 1 sapcs sapsys 30426 Jun 12 14:56 mod_allowmethods.so
-rwxrwxrwx 1 sapcs sapsys 41605 Jun 12 14:56 mod_auth_basic.so
-rwxrwxrwx 1 sapcs sapsys 84126 Jun 12 14:56 mod_auth_digest.so
-rwxrwxrwx 1 sapcs sapsys 68399 Jun 12 14:56 mod_auth_form.so
-rwxrwxrwx 1 sapcs sapsys 30531 Jun 12 14:56 mod_authn_anon.so
-rwxrwxrwx 1 sapcs sapsys 36079 Jun 12 14:56 mod_authn_core.so
-rwxrwxrwx 1 sapcs sapsys 40100 Jun 12 14:56 mod_authn_dbd.so
-rwxrwxrwx 1 sapcs sapsys 32532 Jun 12 14:56 mod_authn_dbm.so
-rwxrwxrwx 1 sapcs sapsys 32359 Jun 12 14:56 mod_authn_file.so
-rwxrwxrwx 1 sapcs sapsys 49757 Jun 12 14:56 mod_authn_socache.so
-rwxrwxrwx 1 sapcs sapsys 61854 Jun 12 14:56 mod_authz_core.so
-rwxrwxrwx 1 sapcs sapsys 42581 Jun 12 14:56 mod_authz_dbd.so
-rwxrwxrwx 1 sapcs sapsys 35071 Jun 12 14:56 mod_authz_dbm.so
-rwxrwxrwx 1 sapcs sapsys 34704 Jun 12 14:56 mod_authz_groupfile.so
-rwxrwxrwx 1 sapcs sapsys 35256 Jun 12 14:56 mod_authz_host.so
-rwxrwxrwx 1 sapcs sapsys 30435 Jun 12 14:56 mod_authz_owner.so
-rwxrwxrwx 1 sapcs sapsys 30802 Jun 12 14:56 mod_authz_user.so
-rwxrwxrwx 1 sapcs sapsys 105072 Jun 12 14:56 mod_autoindex.so
-rwxrwxrwx 1 sapcs sapsys 34253 Jun 12 14:56 mod_buffer.so
-rwxrwxrwx 1 sapcs sapsys 192292 Jun 12 14:56 mod_cache.so
-rwxrwxrwx 1 sapcs sapsys 84567 Jun 12 14:56 mod_cache_disk.so
-rwxrwxrwx 1 sapcs sapsys 88616 Jun 12 14:56 mod_cache_socache.so
-rwxrwxrwx 1 sapcs sapsys 98717 Jun 12 14:56 mod_cgid.so
-rwxrwxrwx 1 sapcs sapsys 354271 Jun 12 14:56 mod_dav.so
-rwxrwxrwx 1 sapcs sapsys 189761 Jun 12 14:56 mod_dav_fs.so
-rwxrwxrwx 1 sapcs sapsys 59275 Jun 12 14:56 mod_dbd.so
-rwxrwxrwx 1 sapcs sapsys 35504 Jun 12 14:56 mod_dir.so
-rwxrwxrwx 1 sapcs sapsys 33559 Jun 12 14:56 mod_dumpio.so
-rwxrwxrwx 1 sapcs sapsys 31544 Jun 12 14:56 mod_env.so
-rwxrwxrwx 1 sapcs sapsys 40037 Jun 12 14:56 mod_expires.so
-rwxrwxrwx 1 sapcs sapsys 63988 Jun 12 14:56 mod_ext_filter.so
-rwxrwxrwx 1 sapcs sapsys 39211 Jun 12 14:56 mod_file_cache.so
-rwxrwxrwx 1 sapcs sapsys 52811 Jun 12 14:56 mod_filter.so
-rwxrwxrwx 1 sapcs sapsys 60936 Jun 12 14:56 mod_headers.so
-rwxrwxrwx 1 sapcs sapsys 158790 Jun 12 14:56 mod_include.so
-rwxrwxrwx 1 sapcs sapsys 66838 Jun 12 14:56 mod_info.so
-rwxrwxrwx 1 sapcs sapsys 36196 Jun 12 14:56 mod_lbmethod_bybusyness.so
-rwxrwxrwx 1 sapcs sapsys 36188 Jun 12 14:56 mod_lbmethod_byrequests.so
-rwxrwxrwx 1 sapcs sapsys 36192 Jun 12 14:56 mod_lbmethod_bytraffic.so
-rwxrwxrwx 1 sapcs sapsys 48496 Jun 12 14:56 mod_lbmethod_heartbeat.so
-rwxrwxrwx 1 sapcs sapsys 86665 Jun 12 14:56 mod_log_config.so
-rwxrwxrwx 1 sapcs sapsys 40163 Jun 12 14:56 mod_log_debug.so
-rwxrwxrwx 1 sapcs sapsys 31797 Jun 12 14:56 mod_logio.so
-rwxrwxrwx 1 sapcs sapsys 48254 Jun 12 14:56 mod_macro.so
-rwxrwxrwx 1 sapcs sapsys 54195 Jun 12 14:56 mod_mime.so
-rwxrwxrwx 1 sapcs sapsys 106526 Jun 12 14:56 mod_negotiation.so
-rwxrwxrwx 1 sapcs sapsys 291551 Jun 12 14:56 mod_proxy.so
-rwxrwxrwx 1 sapcs sapsys 171766 Jun 12 14:56 mod_proxy_ajp.so
-rwxrwxrwx 1 sapcs sapsys 108144 Jun 12 14:56 mod_proxy_balancer.so
-rwxrwxrwx 1 sapcs sapsys 54249 Jun 12 14:56 mod_proxy_connect.so
-rwxrwxrwx 1 sapcs sapsys 38536 Jun 12 14:56 mod_proxy_express.so
-rwxrwxrwx 1 sapcs sapsys 61607 Jun 12 14:56 mod_proxy_fcgi.so
-rwxrwxrwx 1 sapcs sapsys 112538 Jun 12 14:56 mod_proxy_ftp.so
-rwxrwxrwx 1 sapcs sapsys 114424 Jun 12 14:56 mod_proxy_http.so
-rwxrwxrwx 1 sapcs sapsys 56400 Jun 12 14:56 mod_proxy_scgi.so
-rwxrwxrwx 1 sapcs sapsys 55514 Jun 12 14:56 mod_proxy_wstunnel.so
-rwxrwxrwx 1 sapcs sapsys 32760 Jun 12 14:56 mod_ratelimit.so
-rwxrwxrwx 1 sapcs sapsys 40376 Jun 12 14:56 mod_remoteip.so
-rwxrwxrwx 1 sapcs sapsys 45091 Jun 12 14:56 mod_reqtimeout.so
-rwxrwxrwx 1 sapcs sapsys 37224 Jun 12 14:56 mod_request.so
-rwxrwxrwx 1 sapcs sapsys 171049 Jun 12 14:56 mod_rewrite.so
lrwxrwxrwx 1 sapcs sapsys     35 Jun 12 15:46 mod_sapcs22.so -> /sapcontreps/modules/mod_sapcs22.so
-rwxrwxrwx 1 sapcs sapsys 119242 Jun 12 14:56 mod_sed.so
-rwxrwxrwx 1 sapcs sapsys 57944 Jun 12 14:56 mod_session.so
-rwxrwxrwx 1 sapcs sapsys 32806 Jun 12 14:56 mod_session_cookie.so
-rwxrwxrwx 1 sapcs sapsys 47023 Jun 12 14:56 mod_session_dbd.so
-rwxrwxrwx 1 sapcs sapsys 44102 Jun 12 14:56 mod_setenvif.so
-rwxrwxrwx 1 sapcs sapsys 53976 Jun 12 14:56 mod_slotmem_shm.so
-rwxrwxrwx 1 sapcs sapsys 45214 Jun 12 14:56 mod_socache_dbm.so
-rwxrwxrwx 1 sapcs sapsys 35686 Jun 12 14:56 mod_socache_memcache.so
-rwxrwxrwx 1 sapcs sapsys 68519 Jun 12 14:56 mod_socache_shmcb.so
-rwxrwxrwx 1 sapcs sapsys 39669 Jun 12 14:56 mod_speling.so
-rwxrwxrwx 1 sapcs sapsys 63924 Jun 12 14:56 mod_status.so
-rwxrwxrwx 1 sapcs sapsys 43320 Jun 12 14:56 mod_substitute.so
-rwxrwxrwx 1 sapcs sapsys 33237 Jun 12 14:56 mod_unique_id.so
-rwxrwxrwx 1 sapcs sapsys 33466 Jun 12 14:56 mod_unixd.so
-rwxrwxrwx 1 sapcs sapsys 33615 Jun 12 14:56 mod_userdir.so
-rwxrwxrwx 1 sapcs sapsys 25961 Jun 12 14:56 mod_version.so
-rwxrwxrwx 1 sapcs sapsys 37707 Jun 12 14:56 mod_vhost_alias.so
But when stop or stat I have the error,
rgqaserp:(/sapcontreps/apache/bin)(root)#./apachectl start
httpd: Syntax error on line 66 of /sapcontreps/apache/conf/httpd.conf: Cannot load modules/mod_sapcs22.so into server: /sapcontreps/apache/modules/mod_sapcs22.so: ELF file data encoding not little-endian
Can you help me?
Thanks

WebDAV Access: SAP Content Server

Hello everyone,
I would like to use SAP Content Server to store the courses created in LSO Authoring Environment. (Client wants it this way...i have no clue why). Now in order to use SAP Content Server here, the content server must support WebDAV access. So does the content server support WebDAV, if yes -- how to enable it and how to browse it.
Thanks,
GLM

If the documents are stored in DMS with Content Server as the repository, you should be able to access them using the DMS connector to KM. This is a business package which, when installed, exposes document stored in DMS to KM as a KM repository. Then you can browse it like any other KM repository. There are a lot of posts in this forum and others about the DMS connector.
You can also try to enable WebDAV if you Content Server is using a MaxDB database.
http://help.sap.com/saphelp_nw04s/helpdata/en/42/068edfba705415e10000000a114cbd/frameset.htm
Andrew

How to migrate from SAP content server to OPENTEXT?

We have been using SAP content server as our storage for archived data for years.
Now we plan to start using OPENTEXT to admin our archived data.
How can we use OPENTEXT together with existing SAP content server?
My idea is to treat content server as any other media as as DVD, WORM, etc.
However, I do not see that OPENTEXT can be configured to admin content server .
If so, how to transfer whatever on the content server to IXOS?
We are at Opentext 9.5.x
Please share your experience. Thanks!

hi,
Please refere SNote 1043676.
Also, need to understand the following,
How to move an entire content repository from one content server to another
Sometimes you may need to move a content repository - but not necessarily all the content repositories from one content server to another. This can be done without much drama. Here is a means that I've used in the past:
Use report RSCMSEX to export the repository from the source content server.
Create a repository of the same name on the target content server.
Use Report RSCMSIM to import the repository into the target content server.
Delete the repository from the source content server (if desired!).
The SAP progrm sapkprotp controls the import and export. The ABAP reports allow you to specify the RFC destinations where sapkrpotp runs.
For lager repositories
The programs listed above cannot deal with the whole content repository at the same time. For a slower migration, try using the program RSIRPIRL. This approach allows you to do the migation on a live system.
Create the new content repository on your new content server.
Create the new content category.
If using distribution, distribute the new documents to the new category. otherwise change redirected category for DMS_C1_ST
Relocate using the program.
benaakraja

SAP Content Server Configuration (CSADMIN) error in connection

Dear Colleagues
I have installed SAP Content Server 6.40 on Windows 2008 R2 server (64 bit) using IIS 7.5 with MaxDB 7.8.02, Installation completed successfully.
URL testing Information on both Content Server and an Instance which we need to connect to it.
http://cs460:1090/ContentServer/ContentServer.dll?serverInfo
serverType="SAP HTTP Content Server";serverVendorId="Copyright SAP AG, All rights reserved 1998, 2001 ";serverVersion="6400";serverPatch="9";serverBuild="201";pVersion="0046";serverStatus=
"running";serverStatusDescription="";serverDate="2014-05-11";serverTime="02:03:08";startUpDate="2014-05-11";startUpTime="02:03:08";lastAccessDate="2014-05-11";lastAccessTime="02:03:08";
However, when I try to create repository with CSADMIN tcode, I am getting error ''HTTP error: 500 (Internal Server Error)'.
database host is up or down and the web server up
My settings are as follows
1- On Content server I give full permission to content Rep directory
2- On IIS I have allowed Unspecified ISAPI& CGI & modules.
3-odbcreg as the following:-
C:\sapdb\SDB\db\pgm>odbcreg -g
List of installed drivers
1.      SQL Server;     %WINDIR%\system32\SQLSRV32.dll
2.      SAP MaxDB SDB (Unicode);        C:\sapdb\SDB\db\pgm\sdbodbcw.dll
3.      SAP MaxDB SDB; C:\sapdb\SDB\db\pgm\sdbodbc.dll
      C:\sapdb\SDB\db\pgm>odbcreg MaxDB -i -p c:\sapdb\SDB\db\pgm -d sdbodbcw.dll
ODBC Driver for 'MaxDB' has been successfully registered.
     C:\sapdb\SDB\db\pgm>odbcreg MaxDB -i -p c:\sapdb\SDB\db\pgm -d sdbodbc.dll
ODBC Driver for 'MaxDB' has been successfully registered.
4- under settings tab for the repository I set the parameter (driver = MaxDB) as per SAP note 977091
Please suggest, how to resolve this issue.
Thanks

HI Hany Zahran,
Hope that your issue resolved? if so please close this thread with updated answer and make sure mark assumed answered (see top of the screen).
All the best my dear fnd.
Regards,
chandu.

Delay viewing archivelink images held in SAP content server

Hi,
We have implemented an indexing solution utilising SAP Archivelink and Content server. We are noting considerable delays when viewing documents, this only happens for the first document in a transaction and can take up to 6 minutes to display a document. As our users have a person on the telephone at the time this results in alot of smalltalk which is not desireable.
Does anyone know of any performance issues related to document storage in content server?
Many Thanks,
Pete White

hi,
The SAP Content Server is the server at the core of SAPu2019s document storage and management concept. It provides the technical infrastructure for all document-centric applications and business scenarios that do not require long-term document archivingu201D
SAP Integration points
SAP Document Management system (DMS), and SAP Knowledge Warehouse.
U could achieve your requirement easily
SAP Content Server u2013 Features
Ability to create file system and database repositories.
Support for security certificates (secure key).
Ability to lock down the files on the content repositories.
Images can be displayed using the ECL viewer or desktop applications via Internet Explore.
Benakaraj
??P

Creating documents with SCMS_DOC_URL_CREATE in SAP Content Server

Similar Messages

Maybe you are looking for