29 Configuring Oracle Beehive Integration for Zimbra

Oracle Beehive Integration for Zimbra is available for Oracle Beehive Release 1 (1.3) and later.

Oracle Beehive Integration for Zimbra is installed in an Oracle home separate from Oracle Beehive. As a result, Oracle Beehive Integration for Zimbra acts like an application tier and should be configured as such.

If you have not configured TLS or SSL for your Oracle Beehive deployment, you do not need to perform any post-installation steps; simply install Oracle Beehive Integration for Zimbra as described in "Installing Oracle Beehive Integration for Zimbra".

This section covers the following topics:

Configuring Oracle Beehive Integration for Zimbra for SSL-Enabled Oracle Beehive Deployment
Changing HTTP Port for Oracle Beehive Integration for Zimbra

Configuring Oracle Beehive Integration for Zimbra for SSL-Enabled Oracle Beehive Deployment

If you have configured TLS or SSL for your Oracle Beehive deployment, follow these steps to configure Oracle Beehive Integration for Zimbra (these steps are similar to "Configuring SSL with Self-Signed Certificates During Installation of Oracle Beehive"):

If you have configured SSL for your Oracle Beehive deployment, ensure that all your Oracle Beehive application tiers are configured for SSL, including DMZ instances. Refer to "Configuring SSL".
Perform a software only install for Oracle Beehive Integration for Zimbra.
Replace orapki and Oracle Wallet Manager (owm) binaries of Oracle Beehive Integration for Zimbra with those from your Oracle Beehive instance. Create a new wallet located in <Oracle Beehive Integration for Zimbra home>/Apache/Apache/conf/ssl.wlt/default. Refer to "Step 1: Creating Auto-Login Oracle Wallet" for directions to create a wallet.
If you are using self-signed (CA-signed) certificates for your application tier wallets, perform this step.

Remove the test certificates using Oracle Wallet Manager from the wallets in <Oracle Beehive Integration for Zimbra home>/opmn/conf/ssl.wlt/default and <Oracle Beehive Integration for Zimbra home>/Apache/Apache/conf/ssl.wlt/default, if any. The order of removal should be (1) user certificate, (2) certificate request, and (3) trusted certificate. Refer to "Creating CA-Signed Certificate and Importing it into Wallet" for information about CA-signed certificates.
Run the Config Wizard for Oracle Beehive Integration for Zimbra and complete the configuration.
Configure TLS for Oracle Beehive Integration for Zimbra. Perform "Step 2: Configuring Oracle Beehive Instance to Use Oracle Wallet". (Note that you already created an auto-login wallet for Oracle Beehive Integration for Zimbra in a previous step.
If you are using self-signed (CA-signed) certificates for your application tier wallets, perform this step.

Remove the test certificates using Oracle Wallet Manager from the wallets in <Oracle Beehive Integration for Zimbra home>/Apache/Apache/conf/ssl.wlt/default, if any.

Note:

Oracle Beehive Integration for Zimbra installation will fail if the default test certificates are still in the wallets of your Oracle Beehive instances. Configure TLS on the failed Oracle Beehive Integration for Zimbra home, as described in "Configuring TLS with Oracle Wallet", and click Retry from the Install Wizard.

Changing HTTP Port for Oracle Beehive Integration for Zimbra

If Oracle Beehive Integration for Zimbra and your Oracle Beehive instance are on different hosts, then use the command beectl modify_port --protocol HTTP to change the HTTP port. However, do not use this command if Oracle Beehive Integration for Zimbra and your Oracle Beehive instance are on the same host; this will configure all your Oracle Beehive instances to use the same port, which will create a port conflict.

If Oracle Beehive Integration for Zimbra and your Oracle Beehive instance are on the same host, change the HTTP port for Oracle Beehive Integration for Zimbra by changing the HTTP port of your Oracle Beehive instance.

Note:

If you want to change the HTTP port number of your Oracle Beehive instance to a value less than 1024, refer to "Changing HTTP Port" in "Oracle Beehive Post-Installation Procedures".

Determine the name of the listening component and property name of the port you want to change. Run the beectl list_ports command to list all available ports (the --format option is optional):

beectl list_ports --format xml

...
   <row>
      <column name="Protocol">HTTP</column>
      <column name="Listening Port">7777</column>
      <column name="Virtual Port">7777</column>
      <column name="Defining Component">ohs_site1.example.com</column>
      <column name="Property Name">HttpListenPort</column>
      <column name="Listening Component">ohs_site1.example.com</column>
   </row>
   <row>
      <column name="Protocol">HTTPS</column>
      <column name="Listening Port">4443</column>
      <column name="Virtual Port">4443</column>
      <column name="Defining Component">ohs_site1.example.com</column>
      <column name="Property Name">HttpSslListenPort</column>
      <column name="Listening Component">ohs_site1.example.com</column>
   </row>

In the previous example, the HTTP (and HTTPS) listening component is ohs_site1.example.com. The property name of the HTTP port is HttpListenPort, and the property name of the HTTPS port is HttpSslListenPort.

Change the listening port with the beectl modify_property command with the appropriate listening component and property name. The following example changes the HTTP port to 7779:
```
beectl modify_property
  --component ohs_site1.example.com --name HttpListenPort --value 7779
```
Change the HTTP (or HTTPS) port number in the _VIRTUAL_SERVER component. The following example changes the HTTP port number. (Use the property name HttpSslPort to change the HTTPS port number):
```
beectl modify_property --component _VIRTUAL_SERVER --name HttpPort --value 7779
```
Activate configuration and commit changes:
```
beectl activate_configuration
beectl modify_local_configuration_files
```
Note:
The beectl modify_local_configuration_files command will ask you to run this command on all your other instances. Do not run this command on all your other instances at this time. For each instance, perform steps 1 to 3 before running the beectl modify_local_configuration_files command.