> Content Management Guide > Content Deployment Descriptor

Content Management Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Content Deployment Descriptor

The basic deployment configuration for an application is defined in a deployment plan. A deployment plan is a collection of deployment descriptors, which are XML documents. The deployment descriptors for content management are defined in the content-config.xml file.

Caution: WebLogic Server imposes no restrictions on the configuration properties that a user can modify using the Portal Administration Console. Changes made in the administration console can override the settings made in the content-config.xml file. Therefore, if you use this method, be sure to follow the recommendations made in Configuring Applications for Production Deployment in Deploying Applications to WebLogic Server. It is recommended that you use the content management API's or administration tools to change your repository configuration.

This chapter contains the following topics:

 

Enabling Library Services in content-config.xml

You can enable library services in content-config.xml. This is useful when you want to add a custom workflow that you want propagated in a production environment or when you want to share library services across a team of developers.

To enable library services using a deployment descriptor from WorkSpace Studio:

  1. Follow the steps in Editing the content-config.xml File to access the content-config.xml file.
  2. Using the WorkSpace Studio editor or other editor, add the following repository property to the content-config.xml file:
    3. <repository-property>
       <name>MANAGEMENT_ENABLED</name>
       <value>true</value>
    </repository-property>

 

Setting User Credentials for an External Repository in content-config.xml

This section provides information about setting a cleartext password in content-config.xml when using a third-party repository.

To set a cleartext password in content-config.xml:

  1. Follow the steps in Editing the content-config.xml File to access the content-config.xml file.
  2. Using the WorkSpace Studio editor or other editor, add the following repository property to the content-config.xml file:
    3. <content-store>
       <name>BEA_ExtendedRepository</name>
       <description>Portal Test Extended Repository
          Configuration</description>
       <class-name>com.bea.content.spi.internal.ExtendedRepositoryImpl
          </class-name>
       <password></password>
    </content-store>
  3. Start the server for the domain, if it is not already running.
  4. Run the weblogic.security.Encrypt utility. For information on how to do this, see Using the WebLogic Server Java Utilities in WebLogic Server Command Reference.
  5. Copy the generated domain-secret-encrypted-password into the password element. For example:
    6. <password>{3DES}85Kmho5Uphc=</password>
    Note: Password must begin with a {3DES} and end with =.
    Note: The password is specific to the given domain and must be run as a command line utility from that domain directory. This password will not work with another domain.
  6. Restart the server.

 

Editing the content-config.xml File

To edit the content-config.xml file from WorkSpace Studio:

  1. In the Project Explorer, navigate to the <PortalEARProject>/EarContent/META-INF folder.
  2. If content-config.xml is not in this folder, otherwise go to step 3:
    1. Select Window > Show View > Other.
    2. Expand the WebLogic Portal node in the tree and click to select Merged Projects View.
      3. Tip: Some items listed in the Merged Projects view are italicized. The italicized items represent entities that are stored in shared J2EE libraries. All entities that are stored on your file system are shown in regular type.
    3. Click OK.
    4. In the Merged Projects View, right-click the <PortalEARProject>/EarContent/META-INF/content-config.xml file and select Copy To Project from the context menu.
  3. Double-click the content-config.xml file.
  4. Using the WorkSpace Studio editor or other editor, edit the content-config.xml file.

  Back to Top       Previous  Next