将BDS文件存储到CONTENTSERVER的设置.doc

SAPTechnoExtra Large Large Normal Contact AccueilTop of FormRechercher Bottom of FormVous tes ici : Home SAP Top Notes Note 782614Note 782614 - Using external Content Server in the BDSTop of FormHeaderVersion / Date1 / 2004-10-29PriorityRecommendations/additional infoCategoryConsultingPrimary ComponentBC-SRV-BDS Business Document ServiceSecondary ComponentsSummarySymptomDocuments of the Business Document Service (BDS) are stored in a Database Repository by default, and are therefore located in the OLTP database of the system. However, for reasons of capacity, it may be useful to use an external content server.This note explains which aspects to consider, and how to set up Customizing to achieve this.SolutionPrerequisitesWhen using a Content Server Repository instead of a database repository, note the following: Transport: BDS documents in a Content Server cannot be transported. (To transport BDS documents, see Note 551451) Separate databases:In the event of a recovery of the OLTB database, synchronization with the Content Server can cause problems. Documents deleted after the recovery point, whose administrative information can be retrieved by the recovery, are deleted on the Content Server. For a Content Server with an underlying database that works exclusively for the relevant SAP system, the delta can be minimized by resetting to the recovery point. In the event of a recovery of the Content Server, synchronization with the SAP system causes problems, since the SAP system is generally not supposed to be reset to the recovery point. Client-specific applications:For client-specific applications, the repositories on the Content Server should be addressed via a logical repository, in order to disconnect the clients (see Note 423141) Steps in Customizing:The following steps are described in the IMG under the directories SAP Web Application Server - Basis Service - Knowledge Provider - Content Management Service orSAP Web Application Server - Basis Service - Business Document Service Create a repository on the external HTTP Content Server (for an SAP Content Server: Transaction csadmin, IMG node Content Server Administration ) Create an entry in R/3 or SAP Web Application Server for the repository (Transaction OAC0, IMG node Define Content Repositories) Create Content Category (Transaction OACT, IMG node Define Content Categories) Assign the object type to the new category (Transaction sbdsv2, IMG node Maintain Storage Categories)After these steps all newly created documents that are assigned to objects of the relevant object type are stored in the new repository.Use of stock dataThe stock data can still be accessed from their previous folders. It is not necessary to convert the stock data. If you wish to convert the data, however, (relocation), this is possible by using the report RSIRPIRL ( see Note 389366). This report was written for Knowledge Provider applications. This means that you can use the document class and the source category as selection criteria, and not object name, which is more usual in the BDS. In this way, there is a risk of relocating documents with other object names (in particularly in the standard modelssee Note 551451). If you do not want this to happen, do not relocate using report RSIRPIRL.Related Notes551451BDS documents can not be transported.423141Client-specific Customizing for http repositories389366Relocation of documentsBottom