|Bookshelf Home | Contents | Index | PDF|
A content staging environment is similar to a test environment, except that you use it to test content rather than application configuration. This allows you to develop and test new content without affecting your production applications.
After content is approved, Content Center uses workflows and the Content Project business service to send it to the production environment. For general information about Siebel workflows, see Siebel Business Process Designer Administration Guide.
Content Center requires a separate Siebel Business Applications installation for your content staging environment. The physical hardware for this environment should be the appropriate size for supporting the number of content center administrators, contributors, and approvers who manage your business content.
The most important element to keep synchronized is the Siebel repository (SRF) file. This file defines the structure of the application data, for example, the business components and the integration objects.
Keeping the data synchronized is not relevant, with the exception of content and related data. For example, if you use Content Center to manage product literature, then Content Center synchronizes the content by publishing it from staging to the production environment. In this case, products could be related data that also need to be kept synchronized. Although you may have chosen not to manage products through Content Center, nevertheless you must have a user key, such as product ID, that exists in both the staging and production environments so that the association of a piece of literature to a product can be made in the staging area and reproduced in the production environment.
|Siebel Content Publishing Guide|