![]() ![]() ![]() ![]() ![]() ![]() |
Each WebLogic Portal is pre-configured with a BEA default BEA repository for you to use. The default BEA repository is library services-enabled which includes content management features such as a customizable content workflows and versioning.
You can use the pre-configured repository, and add additional repositories to suit your needs. If you choose to use a third-party repository, see Connecting to a Third-Party Repository.
This chapter includes the following sections:
When working with BEA repositories, you can choose the default database-based repository or configure a BEA filesystem repository. Both allow you to use BEA's robust library services to manage your content. Table 3-1 lists the features and advantages of both types.
|
The default BEA repository comes pre-configured for your portal application. Before using your BEA repository, you need to ensure that library services are enabled and add any custom properties needed for your environment.
Some examples of repository properties include those needed to enable integration with features such as full-text search. Repository properties can also indicate if your repository can work in a streaming environment.
Note: | Library services allow you to version content and use workflows to manage the content creation process, see Adding Content to a BEA Repository for more information about library services. |
This section discusses the following topics:
WebLogic Portal's library services allow you to version content and use content workflows to route content through an approval and publishing process. If you are using a BEA repository, you should enable library services before organizing your repository. Enabling library services gives you access to content workflows and versioning.
For more information about using library services, see Adding Content to a BEA Repository.
Note: | Once you have enabled library services for a repository, they cannot be disabled. |
You can modify the configuration of a BEA repository to suit your environment. For example, you can add custom properties for third-party repositories.You can also configure advanced BEA repository properties, such as cache and search settings, for your repository.
If you want to use full-text search with your BEA repository, you must add full-text search properties to your repository connection. For more information, see the WebLogic Portal Search Guide.
You can define properties for repositories within the Virtual Content Repository. For example, if you are using a BEA filesystem repository, additional properties should be added. Table 3-2 lists some examples of repository properties.
Note: | After you disconnect a repository or make any changes to repository properties, Portal Administration Console users must log out and log back in to view the changes. |
To add a property to a repository:
A summary of the new repository information is displayed in the Summary tab.
Used when you want to enable a repository to use WebDAV. WebDav allows users to add content to your repository using Internet Explorer and other WebDAV supported applications. For more information about configuring WebDAV, see Using WebDAV with Your BEA Repository.
|
|
Provides the name of the content type to use when adding content to the repository when using WebDAV (Windows Explorer and other WebDAV supported applications). For more information about configuring WebDAV, see Using WebDAV with Your BEA Repository.
|
|
Used to enable events associated with all repository events including content, modifying workflows and modifying content types. For more information about events, see the
WebLogic Portal Interaction Guide.
|
|
Used to enable events associated with content changes. This is used for full-text search. For more information about events, see the
WebLogic Portal Interaction Guide.
|
|
Used to associate a data source with a repository. This property is used when you have more than one BEA repository. For more information, see Configuring Additional BEA Repositories.
|
Advanced repository properties include cache settings and enabling different types of search features. Table 3-3 lists the advanced repository properties and how they are used.
To edit advanced repository properties:
Your modifications display in the Advanced section of the Summary page.
Note: | After you disconnect a repository or make any changes to repository properties, Portal Administration Console users must log out and log back in to view the changes. |
You can disconnect any repository within the Virtual Content Repository. When you disconnect a repository, your portal application can no longer access its content. If you need to delete all content from a repository, you need to delete the content store (database or filesystem). Deleting a datastore or database should be done by a database administrator.
Note: | After you disconnect a repository or make any changes to repository properties, Portal Administration Console users must log out and log back in to view the changes. |
Note: | If a repository was added manually (not through the Portal Administration Console), you cannot disconnect it using the Portal Administration Console. |
Filesystem repositories allow you to use a filesystem in tandem with the BEA database to store your content. When you use a filesystem repository, content binary files are stored in the filesystem you designate, while the metadata associated with the files (content type information) is stored in the BEA database.
Typically, filesystem repositories increases performance for data retrieval within your portal. However, not all content management features are compatible with filesystem repositories, see BEA Filesystem Repository Considerations for more information.
This section discusses the following topics:
When you use a filesystem repository, you must organize and manage content according to the same requirements you would have if storing content in a filesystem. For example, creating a folder in a filesystem repository creates a folder in the shared directory. For this reason, there are content requirements that help maintain the integrity of the repository and its associated filesystem.
ball.gif
must be named ball.gif.When you configure a repository within the Virtual Content Repository, you are creating a connection to the repository's datastore. In the case of a filesystem repository, the datastore is a filesystem on your network. When you add a connection filesystem repository, you also need to add custom properties that direct WebLogic Portal to that filesystem.
The recommended way to implement a filesystem repository is to modify the properties of the default BEA repository.
Using the Portal Administration Console, edit the connection information for the default BEA repository. If you want to create an additional repository, see Configuring Additional BEA Repositories then return to this section.
cm_fileSystem_webpath
property. This enables the repository to access content through the web server that the filesystem uses. To add this property, click Add Property.
cm_fileSystem_webpath
. Note: | For example, your cm_fileSystem_path could be set to /home/myData but the same path could be referred externally as http://mydomain.com/data/myData which can be set using the cm_fileSystem_webpath property. |
Your filesystem repository appears in the resource tree.
You can create multiple content repositories within the Virtual Content Repository to meet your unique business needs. For example, if you need a physical separation of your content data from your portal application data then you can create multiple BEA repositories.
This section includes the following topics:
In this step, you create database objects for your additional content management database. This involves three basic steps:
BEA provides sample scripts which can be copied and used to define the database resources that must be configured prior to running any additional .sql
scripts. For each repository, a separate database/database user must be predefined according to the appropriate sample script, see the
WebLogic Portal Database Administration Guide for more details.
WebLogic_HOME
/portal/db/oracle/admin/create_tablespaces.sql
and create_users.sql
.WebLogic_HOME
/portal/db/sql_server/admin/create_database.sql
WebLogic_HOME
/portal/db/sybase/admin/create_devices.sql
and create_database.sql
Note: | For both SQL Server and Sybase, the WEBLOGIC_INDEX file group must be defined for indexes created via the database-specific cm_create_tables.sql and cm_create_indexes.sql scripts to execute without errors. |
WebLogic_HOME
/portal/db/db2/admin/create_tablespaces.sql
and create_users.sql
Note: | PointBase is not recommended for a production repository. |
cmrepo_database.properties
file.create_db.cmd/sh
file from your domain directory, using the -database.properties
parameter to indicate your content management-specific properties file which is called cmrepo_database.properties
.create_db.cmd -database.properties=cmrepo_database.properties
You can now connect your repository to WebLogic Server.
To connect the new repository to the server, you need to configure the WebLogic Server to point to the new repository. You do this by creating a new data source for the repository you want to use.
To connect a repository to the WebLogic Server:
Note: | The data source name and JNDI name need to be unique to the domain. |
Note: | If you want to use library services, you must select an XA driver. |
After you have configured the new repository, you'll need to connect it to the Virtual Content Repository. Use the Portal Administration Console to connect to a new repository.
After you have created a new data source, (see Connecting the New Repository to the Server) and connected the repository to the Virtual Content Repository (seeConnecting the New BEA Repository to the Virtual Content Repository), you need to associate the connected data source with your new repository.
You do this by adding a data source property to your repository.
To associate your data source with your repository:
Note: | After you disconnect a repository or make any changes to repository properties, Portal Administration Console users must log out and log back in to view the changes. |
To add a property to a repository:
A summary of the new repository information is displayed in the Summary tab.
![]() ![]() ![]() |