Once the Docbase is ready, we can install Web Publisher Server Files on the new Docbase so that Documentum WebPublisher DocApp is installed and available for our use.
Note
Many people confuse 'Web Publisher Server Files' installation with an application server installation. Please note that Web Publisher install contains two components:
- Web Publisher installation
- Web Publisher Server Files installation
Web Publisher installation is typically done on a separate machine hosting the application server. On the other hand, Web Publisher Server Files are installed on the Content Server machine.
Please note that Web Publisher Server Files installation is required since we are going to use Web Publisher web client for entering content and need default Web Publisher objects to work with. The default Web Publisher objects are available from WebPublisher DocApp, which is configured when we install Web Publisher Server Files on the Content Server host.
Documentum recommends installing Web Publisher Server Files and DocApp as the Content Server installation owner. On Windows, the Web Publisher Server Files are installed at the following location on the Content Server:
%DM_HOME%, for example: C:Documentumproduct<product version>
'Web Publisher Server Files' contains wcm and WcmMethods JAR files containing some Java methods that are run on the Content Server by Documentum Java method server. These methods call classes that are required to be executed from Web Publisher workflow activities.
'WebPublisher DocApp' contains some base Web Publisher objects required by Web Publisher to work with the Docbase in question.
For example:
- Web Publisher jobs and methods
- Web Publisher workflow templates
- Web Publisher lifecycles
- Web Publisher object types
- WebPublisher User Default ACL
- Web Publisher groups: content author, content manager, web developer, and administrator
- Web Publisher roles:
wcm_content_author_role, wcm_content_manager_role, wcm_web_developer_role, andwcm_administrator_role