| Oracle® Collaboration Suite Deployment Guide 10g Release 1 (10.1.2) Part Number B25492-04 |
|
|
View PDF |
| Oracle® Collaboration Suite Deployment Guide 10g Release 1 (10.1.2) Part Number B25492-04 |
|
|
View PDF |
This chapter contains the following topics.
Oracle Collaboration Suite Interoperability with Oracle Database
Oracle Collaboration Suite Interoperability with Oracle Application Server
Oracle Collaboration Suite Interoperabilitywith Oracle Enterprise Manager Grid Control
This section contains the following topics.
Using an Existing Oracle Database with Oracle Collaboration Suite
Platform Dependencies of an Existing Oracle Database with Oracle Collaboration Suite
Version Dependencies of an Existing Oracle Database with Oracle Collaboration Suite
Seeding an Existing Oracle Database for Oracle Collaboration Suite
This section provides information for using an existing Oracle database with Oracle Collaboration Suite.
The Oracle Database 10g is supported on all platforms upon which Oracle Collaboration Suite is supported. Oracle Application Server Application Server Repository Creation Assistant (RepCA), however, is not supported on all platforms.
Oracle Collaboration Suite must be installed with version 10.1.0.5 of the Oracle Database 10g.
You can optionally convert an existing Oracle Database 10g into an Oracle Collaboration Suite database. The database must be version 10.1.0.5 or higher and you must already have Oracle Internet Directory since this information is requested by the installer and there is no option to register it later.You can choose the type of storage management you want such as File System, Automatic Storage Management (ASM), or RAW, and Oracle Collaboration Suite creates the tablespaces and Oracle Collaboration Suite schemas on the specified storage type during the installation process.During the configuration phase, if not previously registered, the Oracle9i Database Server is registered in Oracle Internet Directory and executes component configuration assistants. The component configuration assistants create their schemas and register the information in Oracle Internet Directory, which assists with the database selection during the installation of Oracle Collaboration Suite components.Once the installation is completed, the database will only contain Oracle Collaboration Suite-specific schemas. If you require the metadata repository to reside in the same database as the Oracle Collaboration Suite-specific schemas, then you must run RepCA.
This section contains the following topics.
Oracle Collaboration Suite Deployment with Existing Portal Users
Oracle Collaboration Suite Deployment with Existing Oracle Internet Directory Users
This section contains the following topics.
Managing Portlets within an Existing Oracle Collaboration Suite Portal
The Effect of an Oracle Collaboration Suite Deployment on Existing Portal Users
When you deploy Collaborative Portlets on any Applications tier computer, you install Oracle10g Application Server Portal as part of the process. If you have already deployed Oracle10g Application Server Portal, however, you may not wish to override it with a new Portal installation. In such cases, you can deploy Collaborative Portlets without installing Oracle10g Application Server Portal and must manually configure the images later.
Deploying Collaborative Portlets without Installing a New Version of Portal
When you install Oracle Collaboration Suite, the installer allows you to use an existing portal or create a new one. Choose the option to use an existing portal. As a result, a new version of Portal is not installed on the Applications tier. If Collaborative Portlets are configured and a new Portal is not installed, you must fix the images. If you are setting up a high availability environment, you must then run the Configure Component option in Oracle Enterprise Manager for each additional Applications tier computer and ensure that you only do this for Collaborative Portlets.
When you install Oracle Collaboration Suite, the installer replaces the default Portal home page with the most recent version if you have not changed the default settings. If you have customized the default Portal home page, the installer leaves the Portal as is.
This section contains the following topics.
When Oracle Collaboration Suite is installed on a system with existing Oracle Internet Directory users, those users can be bootstrapped into the application and receive, create, and modify events. To enable existing Oracle Internet Directory users to receive Oracle Collaboration Suite accounts once the product is installed, ensure that the bootstrap is turned on. To disable existing Oracle Internet Directory users from receiving Oracle Collaboration Suite accounts once the product is installed, ensure that the bootstrap is turned off.
Oracle Internet Directory includes a special directory administrator with full access to directory information. The default user name of the super user is orcladmin. If you removed orcladmin from your deployment add at least one user with provisioning privileges to the User Provisioning Admin group.
|
Note: Instructions for performing this task can be found in the Oracle Internet Directory Administrator's Guide. Please see Chapter 5, Oracle Directory Server Administration. |
When you install Oracle Collaboration Suite Infrastructure, an account—orclguest—is created that provides access to Oracle Collaboration Suite applications. If you are running Oracle Application Server and you have not installed Oracle Collaboration Suite Infrastructure, you must use another account to provision your applications.
Oracle Enterprise Manager Grid Control uses a central console and management agents to an organization's grid environment including repositories and applications tiers, as well as Web applications, hosts, and the network in between. You can choose to provide your organization with a separate Oracle Enterprise Manager Grid Control deployment for Oracle Collaboration Suite or a site-wide Grid Control deployment that manages the entire environment, including Oracle Collaboration Suite.
This section discusses various options and best practices that you should consider when deploying Oracle Enterprise Manager Grid Control to manage Oracle Collaboration Suite.
When planning your Enterprise Manager deployment, you should keep the Enterprise Manager framework components—such as the Management Service and the Management Repository—separate from your Oracle Collaboration Suite deployment. For example, you should install the Oracle Management Server on a separate host from your Oracle Collaboration Suite Applications tiers. Similarly, you should not use the Oracle Collaboration Suite database for the Management Repository. By keeping these components separate, you can ensure that Enterprise Manager itself will not be affected by any performance problems on Oracle Collaboration Suite or host.
This section discusses installation sequence considerations for Oracle Enterprise Manager Grid Control and Oracle Collaboration Suite. In most cases you can install either Oracle Enterprise Manager Grid Control or Oracle Collaboration Suite first. However, if you are deploying Oracle Voicemail & Fax you must install Oracle Enterprise Manager Grid Control first.
When you install an Oracle Collaboration Suite Applications tier, an administration console is also installed: Oracle Application Server Control for Collaboration Suite. The console enables you to administer the applications tier. Similarly, when you install the infrastructure, an administration console called Application Server Control is also installed to manage that infrastructure instance.
In contrast to the Application Server Control, the Grid Control Management Console provides complete visibility across your entire Oracle Collaboration Suite deployment. Oracle Enterprise Manager Grid Control provides links that allow you to automatically launch the Application Server Control when needed.
You can install Oracle Collaboration Suite before installing Oracle Enterprise Manager Grid Control or the Management Agents, unless you are deploying Voicemail & Fax. In this case, you will then install the Management Agent on the Collaboration Suite host. When the Management Agent is installed it starts up and discovers the Oracle Collaboration Suite components running on that host. The Management Agent also automatically discovers the host itself and any other components or targets that Enterprise Manager recognizes. You will then see this host and its targets in the Grid Control Console. These targets are automatically monitored once they are discovered.
Figure 4-1 Overview of Oracle Enterprise Manager Grid Control Deployment
Figure 4-1 provides an overview of the Oracle Enterprise Manager Grid Control installation. In this figure there are three hosts, each of which represents an element of the organization's grid. An Oracle Enterprise Manager Grid Control management agent is installed on each host and the Oracle Management Console monitors each host through its management agent. The Oracle Management Console stores information on the Enterprise Manager repository.
If you are installing Oracle Collaboration Suite after Oracle Enterprise Manager Grid Control, you must subsequently install the management agent on each Oracle Collaboration Suite host and then discover these hosts in the Oracle Management Console. You can discover the new Collaboration Suite components from either the Grid Control console or the Application Server Control for that Applications tier or infrastructure installation.
Figure 4-2 Oracle Enterprise Manager Grid Control Deployment with Oracle Collaboration Suite Components
Figure 4-2 illustrates an Oracle Enterprise Manager Grid Control deployment across three Oracle Collaboration Suite hosts. The Oracle Management Console communicates with the hosts, each of which is running the Oracle Enterprise Manager Grid Control management agent. The management agent on two of the hosts is configured to run on the Oracle Collaboration Suite Applications tier while the management agent on the third host is configured to run on the Oracle Collaboration Suite Infrastructure tier. The Oracle Management Console stores relevant information in the Enterprise Manager Repository.
Once the Oracle Collaboration Suite installation has been discovered by Grid Control, there are some additional steps to perform in the Grid Control Console. These steps are documented in Oracle Enterprise Manager Managing Collaboration Suite.
You can configure Oracle Enterprise Manager to use Oracle Identity Management. Administrators can login to Enterprise Manager using Single Sign-On and be authenticated and authorized through Oracle Internet Directory.
For information on configuring Enterprise Manager with Identity Management see the Oracle Enterprise Manager Advanced Configuration Guide.
