7 Configuring Security for BDSS

This chapter describes how to configure security between the Engine and the connectors.

This chapter includes the following topics:

7.1 Overview of Communication Security

Because the connector interface is a web service, you can use a web-based security protocol such as SSL to secure communications between the Engine and a connector. The connector implementation is solely responsible for the security between itself and the PIM server with which it communicates.

After you install BDSS, you can modify its configuration to secure the web services exposed by both its Hub and connectors by completing the following tasks:

7.2 Securing the Web Services Exposed by the Hub

To secure the web services exposed by Hub components running on Integrated WebLogic Server, see Oracle Fusion Middleware Securing Web Services for Oracle WebLogic Server.

Tip:

After you configure BDSS for SSL, first deploy BDSS and then open a web browser. Enter the HTTPS URLs for the connector Runtime Library and the Hub Callback Library web services to verify that they can accept secure requests.

7.3 Configuring BDSS for HTTPS

After the web services are configured to use SSL, you must modify the URLs identifying the Connector Runtime Library, Hub Callback, and Exchange 2007 Connector to reflect the secure protocol (HTTPS) and secure port, as described in the following steps:

  1. Start JConsole (or any other MBean-compliant application) and then log in.

  2. Navigate to the EngineSettings MBean.

    1. Change the EngineEndPointURL attribute. Specify https:// as the protocol and set the port as the SSL port used by Integrated WebLogic Server. For example:

      https://<system>:<secureport>/BDSSHubWebServices/EngineCallbackInterface?wsdl

    2. Change the RuntimeLibraryURL attribute. Specify https:// as the protocol and the SSL port used by Integrated WebLogic Server. For example:

      https://<system>:<secureport>/BDSSHubWebServices/ConnectorRuntimeInterface?wsdl

  3. Navigate to the ServerDomainConfigMBean.

    1. In the showAllConnectorsForPim operation, specify Exchange 2007 as the pimServerType parameter value and click showAllConnectorsForPim.

    2. Note the PIM Server Name and Connector Identification values.

    3. In the updateConnectorForPim operation, for the pimServerInstance value, specify the value for PIM Server Name obtained in Step 3b. For the connectorName value, specify the value for Connector Identification obtained in Step 3b. For the URL, enter the HTTPS URL for the Exchange 2007 Connector.

    Note:

    You also perform these steps if you create two Exchange users to test connector domain synchronization, but you specify BPEL Tasks as the value for the pimServerType attribute instead of Exchange 2007.