Problem with your content server? Test it fully with RSCMST!
In SAP, content repositories are defined in transaction OAC0. When there is a problem storing or retrieving documents and data files, your first thought may be to go to OAC0 and press the Test Connection icon (). If you see a nice green check with “Connection test for content repository xx was successful”, you just assume everything is fine with the content repository, and there must be a problem somewhere else (probably just user error). But is verything really
alright with your content server and that content repository? Does that simple little icon test everything? Actually, no it doesn’t.
All the Test Connection in OAC0 really does is verify that SAP can send commands to the content server, that the content server acknowledges it knows about the content repository you are testing, and that SAP can receive that reply. It doesn’t actually make sure that content repository is properly configured
and that it is really able store and retrieve actual documents or archive files.
To really test a content server, SAP provides a standard report you can run from transaction SE38: RSCMST – “CMS: Test Programs”. RSCMST fully exercises the specified content repository testing all standard SAP HTTP Content Server commands. It actually creates, reads, then deletes real test documents, to be sure that the content server and this content repository are in complete operating order. If the storage system connected to your content server is down, or has a permissions problem, it will probably be obvious in RSCMST (lots of errors in bright red); but in OAC0 Test Connection, as long as the content server itself is responding, all will look to be ‘OK’.
Using RSCMST is simple: in SE38, execute program RSCMST. Enter in the Repository you want to test (say, A1) and hit execute. If you then hit the execute icon at the top (or F8), ALL tests will be run – this can take a few minutes. Or, you might want to execute a couple of the tests individually with the execute icon to the left of each test. For example, if you get errors on the RSCMSTH0 and RSCMSTH1 tests, there really isn’t a point in running the other tests – something is probably really wrong. Note: some content servers haven’t fully implemented all SAP Content Server commands, or some storage systems may not allow documents to be deleted after being created. So certain errors might be OK to ignore. You should press the log icon () next to the test error count to see what the error actually is, and whether it is really a problem before panicking.
If RSCMST returns 0 errors for all of its tests with no numbers in bright red, then you might want to look into user error.