3 Installing the BDSS Components

3.1 Overview of Installation

BDSS consists of the following independently installed components, each with their own installation prerequisites (listed in Table 3-1):

• The BDSS Hub components

• The BDSS connectors:

  • Oracle BDSS Connector for Microsoft Exchange 2007

  • The Oracle BPEL Task Connector

The companion CD includes BDSS.zip. This file contains the installer file, bdss_template.jar, the template file that creates the data source and queues. In addition, it contains the EAR files for the Oracle BDSS Connector For Exchange 2007 (the Exchange 2007 Connector), the Oracle BPEL Task Connector, the Engine (BDSSHub.ear), and the Dispatcher (BDSSDispatcher.ear). BDSS.zip also includes XSL transformation files and SQL scripts.

3.1.1 Prerequisites

This section describes the minimum hardware and software requirements for deployment that would enable synchronization between different PIM servers. Figure 3-1 is an example of such a scenario.

Note:

Hardware requirements for a deployment vary depending on the complexity and scale of the deployment.

The minimum set of hardware for the BDSS Hub and Dispatcher is as follows:

• The Oracle Enterprise Manager

• Oracle WebLogic Application Server 11g (the minimum for the Oracle BPEL Task Connector) for the Hub components and the Oracle BPEL Task Connector deployment.

• A server for the data store with the Oracle Database 11g. For very small deployments, this database may reside on the same server as the other components.

This environment is sufficient for installing the Exchange 2007 Connector.

Note:

Although installing most of the components on separate application servers results in improved scalability support, you can install all of them on the same application server. However, installation on a single application server affects performance and port settings.

Figure 3-1 Basic Installation of BDSS

3.2 Deploying the Hub Components

The Dispatcher, Engine, and Exchange 2007 connector are packaged in bdss_template.jar. You can deploy the Dispatcher and the Engine on the same application server or on separate application servers. Because the Dispatcher communicates with the Engine through a remote MBean interface, it can be deployed to a separate application server if needed.

3.3 Overview of Installing and Configuring BDSS

Tasks include:

1. Creating a Domain

2. Extending the Domain with the BDSS Templates

3. Adding Security Credentials

4. Setting SSL

5. Enabling Data Transformation and Filtering for Exchange 2007 Connector

6. Configuring the Exchange 2007 Connector

7. Configuring the Hub

8. Configuring BDSS Server Instances

9. Configuring Connector Instances

10. Adding Users

3.4 Creating a Domain

To create a domain using Fusion Middleware Configuration Wizard:

1. In the Welcome screen, select Create a new WebLogic domain and then click Next. The Select Domain Source screen appears.

2. Select Oracle Enterprise Manager and then click Next. You use Oracle Enterprise Manager to configure the security credentials used by the Exchange 2007 Connector (described in Section 3.6, "Adding Security Credentials"). You can also configure the Hub and Dispatcher using Oracle Enterprise Manager. For more information, see Chapter 5, "Configuring the BDSS Hub Services."

   Note:

   Select Oracle JRF -11.1.1.0[jdeveloper] if it is not selected by default. See also Section 3.4.1.1, "Installing the JRF Extension."

3. In the Configure Administrator User Name and Password screen, enter the user name and password and then click Next. The Configure Server Start Mode and JDK screen appears.

4. If needed, change the JDK; otherwise, navigate to the Create WebLogic Domain screen by clicking Next.

5. In the Create WebLogic Domain screen, enter a domain name and then click Create.

6. When the progress indicator completes, click Done.

3.5 Extending the Domain with the BDSS Templates

The BDSS template (bdss_template.jar) creates a queue on Integrated WebLogic Server and the data source used by the Run-Time Configuration Manager. It can also deploy the BDSS Hub, Dispatcher and Exchange 2007 Connector applications.

You install these BDSS components by using the Fusion Middleware Configuration Wizard to extend a domain with BDSS templates.

To install the components:

1. Start Configuration Wizard and then select Extend an existing WebLogic Domain in the Welcome screen (Figure 3-3). Click Next. The Select a WebLogic Domain Directory screen appears.

   Figure 3-3 Extending the WebLogic Server Domain

   
   

2. Select any domain that has JMS installed and then click Next. The Select Extension Source screen appears.

3. Select Extend my domain using an existing extension template.

4. Using the Select a Template dialog, locate bdss_template.jar (Figure 3-4) and then click OK.

   Figure 3-4 Selecting bdss_template.jar

   
   

5. In the Select Extension Source dialog, select BDSS template.jar and then click Next.

   Figure 3-5 Selecting bdss_template.jar

   
   

6. In the Configure JDBC DataSource page (Figure 3-6), enter the connection information. The user name must be bdss. Click Next. The Test JDBC Data sources screen appears.

   Figure 3-6 Configuring the JDBC Data Source

   
   

7. Click Test Connections. Click Next after Configuration Wizard generates a Test Successful! message (Figure 3-7). The Run Database Scripts screen appears.

   Figure 3-7 Testing the JDBC Connections

   
   

8. In the Run Database Scripts page (Figure 3-8), click Run Scripts.The CreateBDSSDataModel.sql script creates the database tables and triggers and the BDSSSeedData.sql script populates the database with sample data for the domains.

   Figure 3-8 Creating the Database Tables and Seeding Data

   
   

9. Continue to the Target Deployments to Clusters and Servers screen (Figure 3-9).

   Note:

   The Dispatcher, the Hub, and the Exchange 2007 Connector are deployed by default. If needed, select Deployments and Services in the Select Optional Configuration screen that follows the Run Database Scripts screen. After you select this option, you then select the applications to deploy. This optional configuration enables scalability by allowing you to deploy each component on a different WebLogic Server.

   Figure 3-9 Selecting BDSS Components

   
   

10. Select the BDSS components to deploy and then click Next. By default, the wizard deploys the Dispatcher, the Hub, and the Exchange 2007 Connector. The Configuration Summary screen appears (Figure 3-10).

    Figure 3-10 The Configuration Summary Screen

    
    

11. Review the installed components. Click Previous to return to the Target Deployments to Clusters or Services and change your selection.

12. Click Next. The Configuration Manager creates the domain. When the progress indicator on the Creating Domain screen completes (Figure 3-11). Click Done.

    Figure 3-11 The Create Domain Screen

    
    

3.6 Adding Security Credentials

The Exchange 2007 Connector requires the three sets of credentials listed in Table 3-2.

Table 3-3 lists the credentials needed by the BPEL Task Connector.

If the Windows domain is required, it can be prepended to the user name and a backslash ("\") is used to separate the domain and user name as in domain\username.

Add the credentials listed in Table 3-2 using Fusion Middleware Control, as illustrated in Figure 3-12. For more information on credentials, see "Configuring the Credential Store" in Oracle Containers for J2EE Security Guide.

Figure 3-12 Creating Credentials in Oracle Enterprise Manager

The following steps describe how you enter in the credentials using Oracle Enterprise Manager.

1. Log in to Oracle Enterprise Manager.

2. Expand the WebLogic Domain node in the navigation pane and then right-click your domain.

3. From the context menu, select Security and then Credentials. The Security Page appears.

4. Create the exchange2007pimtransport credential map by clicking Create Map. The Create Map dialog appears.

5. Enter exchange2007pimtransport in the Map Name field and then click OK.

6. For each JPS key listed in Table 3-2, perform the following:

   1. Click Create Key. The Create Key dialog appears.

   2. Select exchange2007pimtransport from the Select Map list.

   3. Enter the JPS key. For example, enter activeDirectoryAdminCredential.

   4. In the User Name field, enter in the user name (ensuring to prefix the domain if needed)

   5. In the Password field, enter the password.

7. Click OK.

Note:

You can access the System MBean Browser from the context menu that appears when you right-click a domain in the Navigation pane. Using the System MBean browser, you can invoke some operations on the JPS MBean, but not all of them. The steps described in Section 3.6 are the correct method for entering credentials. You can also use the System MBean browser to manage the BDSS MBeans, which you use to configure BDSS Hub components and server and connector instances.

3.7 Setting SSL

If the configuration of the Exchange 2007 servers require secure communications, then you must configure the Exchange 2007 Connector to support SSL to enable it to communicate securely with the Microsoft Autodiscovery and Exchange Web Service (EWS). The Certificate Authority (CA) that issued and signed the certificate bound to the EWS server must be installed as a trusted CA in the trust store used by the connector. By default, the application deployed to WebLogic Server use a trust store called DemoTrust.jks, which is located in the %WL_HOME%\lib directory.

To configure SSL, you must first obtain the X.509 certificate bound to the IIS Web Server hosting the Exchange Web Services and then update DemoTrust.jks with this certificate.

To install the certificate:

1. Obtain the X.509 certificate bound to the IIS Web Server hosting the Exchange Web Services and save it as a file on the file system on the same box the connector is being deployed on. For the purposes of this document, the file is saved at c:\temp\exchangecacert.cer.

2. Log in to the Exchange 2007 server.

3. Start IIS Manager.

4. Right click the Exchange virtual directory (typically at Web Sites > Default Web Site > Exchange) and select Properties.

5. Navigate to the Directory Security.

6. Click View Certificate.

7. Click the Details tab and then select Copy to File.

8. In the wizard, select the defaults on each page until you are prompted for the file name. Specify the name and location for the file. For example, enter c:\temp\exchangecacert.cer.

To update DemoTrust.jks with the certificate:

1. Open a command window and change the current directory to the location of DemoTrust.jks. For example, enter the following command:

   cd c:\WL_HOME\wlserver_10.3\server\lib

2. Use the Java keytool utility to import the certificate.

   Assuming your JDK is installed at c:\program files\java\jdk1.6.0_11, issue the following command:

3. "C:\Program Files\Java\jdk1.6.0_11\bin\keytool" -importcert -trustcacerts -file "C:\temp\exchangecacert.cer" -keystore DemoTrust.jks -storepass DemoTrustKeyStorePassPhrase -alias XXX
   

3.8 Enabling Data Transformation and Filtering for Exchange 2007 Connector

The Exchange 2007 Connector uses XSD and XSLT files to transform records to and from the Hub XML and PIM XML forms and XML files to filter unwanted records. These files must be located on a database file system and the location must be configured in BDSS. The seed data script provides you with a default location of c:/fusion_sync <root>. For example, the seed data script populates the database with such strings as c:/fusion_sync/Exchange2007/....

To set up the various XSLT and XSD files on the file system and configure the XSL and XSD files in BDSS, you can copy the transform and filter directories from where you extracted BDSS.zip to your preferred location. For example, the directory structure may be in the following form:

<MY DIRECTORY>/exchange2007/task/transform/exchange2007task.xsd

To set up the files:

1. Copy the Exchange 2007 XSD and XSL files to a local directory having the following hierarchy:

   • <root>/exchange—This directory should contain a contact and task subdirectory and the exchange2007typelibrary.xsd file.

   • <root>/exchange/contact/transform—This directory should contain the following three files:

     exchange2007contact.xsd
     exchange2007contacttohubcontact.xsl
     hubcontacttoexchange2007contact.xsl
     

   • <root>/exchange/task/transform—This directory should contain the following three files:

     exchange2007task.xsd
     exchange2007tasktohubtask.xsl
     hubtasktoexchange2007task.xsl
     

   • <root>/exchange/calendar/transform—This directory should contain the following three files.

     pimicalbody.xsd
     exchange2007calendartohubcalendar.xsl
     hubcalendartoexchange2007calendar.xsl
     

   • <root>/exchange/calendar/transform/intermediatetranslation—the directory should contain the following six files

     calendaritemtype.xsd
     calendaritemtypetoveventasxml.xsl
     timezoneregistry.xml
     timezoneregistryschema.xsd
     veventasxml.xsd
     veventasxmltocalendaritemtype.xsl
     

2. Copy the Exchange 2007 XML filter files to a local directory having the following hierarchy:

   • <root>/exchange—This directory should contain a contact a task subdirectory and the exchange2007typelibrary.xsd file.

   • <root>/exchange/contact/filter—This directory should contain contactfilter.xml file.

   • <root>/exchange/task/filter—This directory should contain the taskfilter.xml file.

   • <root>/exchange/calendar/filter—This directory should contain the calendarfilter.xml file.

3. Copy the Hub XSD and XSL files to a local directory having the following hierarchy:

   1. <root>/hub—This directory should contain a contact and task subdirectory and the HubTypeLibrary.xsd file.

   2. <root>/hub/contact/transform—This directory should contain the following eight files:

      hubaddress.xsd
      hubcontact.xsd
      hubcountry.xsd
      hubemailaddress.xsd
      hubnameprefix.xsd
      hubnamesuffix.xsd
      hubphone.xsd
      hubstate.xsd
      

   3. <root>/hub/task/transform—This directory should contain the HubTask.xsd file.

   4. <root>/hub/calendar/transform— This directory should contain the HubCalendar.xsd file.

4. Copy the following BPEL Task XSDs and XML file to a new directory called <root>/webcenter/tasks/transform:

   • BPELTask.xsd

   • BPELTask2HubTask.xsl

   • HubTask2BPELTask.xsl

3.9 Configuring the Exchange 2007 Connector

This section describes the following tasks.

• Configuring the Exchange 2007 Connector for Record Transformation

• Configuring the Exchange 2007 Connector to the Active Directory Service

• Configuring Exchange 2007 Connector to Use the Auto Discovery Service

These tasks involve only the parameters that you must configure. Table 3-4 lists all of the configuration options for the Exchange 2007 Connector, both mandatory and optional. Although the environment dictates which of these parameters you define, you must define the following in all circumstances:

• Active Directory Server

• Auto Discovery Service Connection Point (SCP)

• Event Receiver

This configuration resides in the PROFILES table. You configure the Exchange 2007 Connector using the BDSS MBeans that are deployed to a JMX console. You can also configure the Exchange 2007 Connector using such tools as JDeveloper or SQL Developer. See also Chapter 6, "Configuring the BDSS Connector for Microsoft Exchange 2007."

Configuring Parameters to Use URIs for Transformation Files

When configuring such parameters as Pim Xsd, PimToHubUrl, HubToPimUrl, and Calendar Item Type xsd, to use URIs for the transformation files, do not enter the URI in the format of file:///./. Instead, enter the URI in the following format:

C:/directory1/directory2.../file.NNN

For example, if c:/fusion_sync is the <root> directory for transformer files, enter the following URI:

c:/fusion_sync/transform/exchange/task/exchange2007task.xsd

3.10 Configuring the BPEL Task Connector

Table 3-5 lists the configuration options for the BPEL Task Connector.

3.11 Configuring the Hub

The attributes of the Engine are exposed through the EngineSettings MBean and the attributes for the Dispatcher are exposed through the DispatcherSettings MBean that are described in Chapter 5, "Configuring the BDSS Hub Services."

To configure the Dispatcher, you must set the URL used by the Dispatcher to connect to the DispatcherHub Web service on the server that hosts the Hub. You configure this URL through the HubEndPointURL parameter of the DispatcherSettings MBean. For more information, see Section 5.2, "Configuring the Dispatcher."

For the Engine, you must configure the EngineSettings MBean's EngineEndpointURL attribute, which provides the URL used by the Engine to enable the connectors to extract requests and data update request responses to the Engine. In addition, you must set the URL for the RunTimeLibraryURL attribute. The Engine sends this URL to the connectors to enable them to communicate with the Connector Run-Time Library. For information on how to set these attributes, see Section 5.3, "Configuring the Engine."

3.12 Configuring BDSS Server Instances

Use the ServerDomainConfigMBean's updatePIMServerInstance operation to add the name of the Connector to a BDSS instance as described in Section 4.3.1, "Adding and Updating BDSS Instances."

3.13 Configuring Connector Instances

You must configure the instances of the connectors and the PIM servers with the URLs of the connector web service. To add this URL to a connector instance, use the Connector Configuration MBean's updateConnectorInstance operation as described in Section 4.4.1, "Adding and Updating Connector Instances."

3.14 Adding Users

Use the addConnectorUser operation of the User Configuration MBean to create users. Create one user for each configured connector per Hub user. For more information, see Section 4.7.2, "Creating Connector Users."

3.15 Postinstallation Configuration

To enable the proper functioning of the components, perform the following postinstallation tasks:

• Configuring the Dispatcher

• Configuring the Engine

• Configuring PIM Server Instances Using MBeans