![]() ![]() ![]() ![]() ![]() ![]() |
The Virtual Content Repository allows you to connect to non-BEA repositories. When third-party repositories are connected to the Virtual Content Repository, their content can be accessed by portal tools such as content placeholders, content selectors, and so on.
Some third-party content management vendors have built integrations (Content Service Provider Implementations or SPIs) that allow you to connect third-party repositories to the Virtual Content Repository. Contact your third-party repository vendor to find out the details about their implementation.
If the third-party repository you are using is JSR 170 compliant, you can connect to it using BEA's JSR 170 Connector> See Working with a JSR 170-Compatible Repository. For more information about JSR170, see the JSR 170 web site.
Note: | You cannot use BEA's library services with third-party repositories. |
If your third-party repository does not have a written an implementation for the Virtual Content Repository, you can write your own using BEA's Service Provider Interface (SPI).
This chapter includes the following sections:
Configuring a third-party repository to use with WebLogic Portal involves the following three steps:
Note: | You cannot use BEA's library services with third-party repositories. |
After creating an SPI implementation, you can connect your third-party repository to the Virtual Content Repository using the ProductNameShort.
Tip: | If you want to test your repository connection, you can use the IVirtualRepositoryManager API. |
Once you have connected a third-party repository to the Virtual Content Repository, you can use that repository's content within your portal. If the third-party repository implementation includes write capabilities, you can also use the Portal Administration Console to modify content within the repository.
An SPI can be deployed multiple times with different configuration parameters. From the application's perspective, this appears as multiple repositories.
Note: | Library services cannot be used in conjunction with SPI implementations. |
When you connect to a third-party repository, you may need to configure additional properties that match your third-party repository's configuration. Consult your third-party documentation to verify the properties that you need to configure and the connection class you should use.
To connect a repository to the Virtual Content Repository (using the Portal Administration Console):
Use the SPI connection class you have created or that has been provided by your third-party vendor. The connection class is the fully qualified name of the class which implements
com.bea.content.spi.flexspi.Repository . Be sure you have added this class to your application classpath. (x-ref to adding libraries section)
|
|||
If the SPI implementation requires a global password, enter it here. When configuring a BEA repository, you can leave this blank.
|
|||
If the third-party repository connected to BEA's Virtual Content Repository supports multiple user authentication, you can restrict users to specific content. Multiple user authentication lets users log in with global credentials or with unique user credentials. User credentials can control the content individual WebLogic Portal users can view. For example, content contributors could view only the content that they add or edit.
Repositories, such as SharePoint, that support the RepositoryMultipleUsers
capability type can display the Login Options button. Multiple user authentication is available for content repositories that support the RepositoryMultipleUsers
capability type, defined by the RepositoryFeatureCapability.RepositoryMultipleUsers
(which is determined by the ICapabilityManager.checkRepositoryCapability()
method).
The Login Options button appears automatically in the ProductNameShort if you connected the third-party repository to BEA's Virtual Content Repository.
Caution: | Currently there are no third-party repositories that support multiple user authentication. |
Perform the following steps to set up global credentials and log into the repository:
User authentication persists across multiple ProductNameShort sessions until you change it.
WebLogic Portal provides a connector to repositories that implement the JSR 170 specification such as Day Software's CRX. If you want to access a repository using its JSR 170 interface, you do not need to write a custom SPI implementation.
This section assumes you have already installed and configured a JSR 170 repository. For additional documentation about installing and using Day Software's CRX JSR 170 repository, see the WebLogic JSR 170 Adaptor Developer's Guide and the WebLogic JSR 170 Supported Configurations Guide.
When a repository is connected to the Virtual Content Repository, both content contributors and developers can search for content within the repository. However not all metadata provided by the Virtual Content Repository, such as system properties and MIME types, are supported by the JSR 170 specification; subsequently some searches may be invalid.
The following system properties cannot be used when searching JSR 170 repositories:
The following search operators cannot be used:
To connect to a JSR 170 repository, do the following:
|
|||
|
![]() ![]() ![]() |