| Oracle® Beehive Integration Guide Release 2 (2.0.1.8) Part Number E16650-06 |
|
|
PDF · Mobi · ePub |
| Oracle® Beehive Integration Guide Release 2 (2.0.1.8) Part Number E16650-06 |
|
|
PDF · Mobi · ePub |
This module describes integrating IBM Lotus Domino with Oracle Beehive. This module contains the following sections:
Overview of Integrating IBM Lotus Domino with Oracle Beehive
Procedure for Integrating IBM Lotus Domino with Oracle Beehive
Administering Your IBM Lotus Domino and Oracle Beehive Integration
Oracle Collaboration Coexistence Gateway is an Oracle proprietary solution that allows the Oracle Beehive users to collaborate with the IBM Lotus Domino users. Additionally, this solution allows the IBM Lotus Domino users to use Oracle Beehive features such as Team Collaboration, and Synchronous Collaboration without having to migrate from IBM Lotus Domino.
Note:
The IBM Lotus Domino coexistence solution supports the
Meeting data type only.The Oracle Coexistence Gateway must be deployed on a dedicated Domino server or an existing Domino server.
Oracle Collaboration Coexistence Gateway includes the following services:
Oracle Connector for Domino
Oracle Free Busy Client
Coexistence Connector Domino Databases
Oracle Beehive Coexistence Service
The first three services run on the computer where Oracle Connector for Domino is installed. The last service is on Oracle Beehive. These services update and propagate data between the two coexisting systems.
You can centrally manage Oracle Beehive Coexistence using the beectl command and Oracle Beekeeper. This includes managing components of Collaboration Coexistence Gateway Coexistence that are installed on the remote servers.
Note:
Prior to integrating IBM Lotus Domino with Oracle Beehive, Oracle recommends that you become familiar with the concepts associated with this integration. To learn more about the associated concepts, including the Oracle Collaboration Coexistence Gateway, see "Oracle Beehive Integration with IBM Lotus Domino Server" in Oracle Beehive Concepts.This section describes the procedure for integrating IBM Lotus Domino with Oracle Beehive. This section contains the following topics:
The Oracle Beehive Installation Guide for Microsoft Windows consists of the following information that you will need to install the components of the Oracle Collaboration Coexistence Gateway solution:
For information about what you will require before beginning the installation, see "Oracle Collaboration Coexistence Gateway" in Module 3 of the Oracle Beehive Installation Guide for Microsoft Windows.
For information about the installation sequence, and installation of the Oracle Collaboration Coexistence Gateway, see "Oracle Collaboration Coexistence Gateway Install Help" in Module 6 of the Oracle Beehive Installation Guide for Microsoft Windows.
For information about the installation sequence for Oracle Coexistence Connector for IBM Lotus Domino Server, see "Oracle Coexistence Connector for IBM Lotus Domino Server Sequence of Screens" in Module 6 of the Oracle Beehive Installation Guide for Microsoft Windows.
This section includes information that is necessary to configure the Oracle Collaboration Coexistence Gateway. This section contains the following topics:
After installing Oracle Beehive and Oracle Connector for IBM Lotus Domino, and configuring a coexistence system on Oracle Beehive, you must perform additional post installation configuration tasks before the Oracle Collaboration Coexistence Gateway is fully functional.
To run the Oracle Collaboration Coexistence Gateway:
If your IBM Lotus Domino deployment does not allow users to receive e-mails from external addresses, the IBM Lotus Domino administrator must reconfigure IBM Lotus Domino to allow incoming external e-mails.
Configure a relay server on Oracle Beehive. For additional information about this task, see "Setting Up E-mail Relay Routing" in the Oracle Beehive Administrator's Guide.
Ensure that your local domains are configured in the Oracle Beehive E-mail Service. You can do this by using Oracle Beekeeper or by running the following beectl command:
append_value --component _EmailService --name LocalEmailPatterns --value "*@<yourdomain>"
Where <yourdomain> represents your local domain.
For the configuration changes to take effect, run the beectl command, activate_configuration.
If your IBM Lotus Domino and Oracle Beehive deployments have local users with the same e-mail domain, set the AcceptInvalidLocalUsers E-mail Service property to TRUE. You can do this using Oracle Beekeeper or by using the following beectl command:
modify_property --component _EmailService:TransportProperties --nameAcceptInvalidLocalUsers --value TRUE
For the configuration changes to take effect, run the beectl command activate_configuration.
After configuring pre-resolution rules, and applying the changes in Oracle Beehive, run the following commands for each Oracle Beehive primary e-mail domain on each Coexistence Connector system:
$ORACLE_HOME\beehive\collabcoex_domino_connector\coexctl_domino.exe set_property --file $ORACLE_HOME\beehive\collabcoex_domino_connector\conf\OGLOConfiguration.xml --section smtpRedirection --property <example.com> --value <special.example.com>
Note that you must also configure the pre-resolution rules Oracle Beehive for the rules to take effect. For information about configuring rules in Oracle Beehive, see "Configuring Complex Rule-Based E-mail Parameters using Oracle Beekeeper" in the "Managing Oracle Beehive E-mail" module of the Oracle Beehive Administrator's Guide.
This section includes information about adding a coexistence system, by using the add_coexistence_system command.
The add_coexistence_system command takes either the --url parameter or both --host_name and -port parameters. Use the --url option if you need to customize the URI portion of the URL. Otherwise, you can use either of the methods of specifying the host. Optionally, the --use_https parameter can be used along with the --host_name and --port parameters to specify that the HTTPS protocol is used.
The following examples show how to specify the host by using the different methods described in the preceding paragraphs:
Example 1:
beectl> add_coexistence_system --name COEX --product_name DOMINO --host_name example.com --port 80 --partnership_key
The preceding command generates a URL of the following type:
http://example.com:80/coexConnector/CoexMLPort
Example 2:
beectl> add_coexistence_system --name COEX --product_name DOMINO --host_name example.com --port 80 --use_https --partnership_key
The command in Example 2 generates a URL of the following type:
https://example.com:80/coexConnector/CoexMLPort
Example 3:
beectl> add_coexistence_system --name COEX --product_name DOMINO --url http://example.com -- partnership_key
The command in Example 3 generates a URL of the following type:
http://example.com:80/coexConnector/CoexMLPort
To add a coexistence system to your Oracle Beehive deployment:
Determine the fully qualified domain name and port of your Oracle Connector for the IBM Lotus Domino installation.
Navigate to the ORACLE_HOME/beehive/bin directory on the system hosting the Oracle Beehive deployment.
Run the following command:
beectl> add_coexistence_system --name <name> --product_name <product_name> {--url <url>|--host_name <host_name> --port <port_number> {--use_http|--use_https}} --partnership_key [--timezone_alias_namespace <timezone_alias_namespace>]
Note:
The argument passed to the-partnership_key option is the password defined during the installation of the Oracle Connector for IBM Lotus Domino.The argument passed to the --url option is displayed in the summary screen of the Oracle Connector for Domino installation, where:
<host_name> represents the fully qualified domain name of the system hosting Oracle Coexistence gateway for IBM Lotus Domino.
<port> represents the HTTP port of your Oracle Coexistence Gateway for the IBM Lotus Domino installation.
<name> represents the name that you want to give to the Remote Coexistence System.
<partnership_key> represents the password defined during the installation of the Oracle Coexistence Gateway for IBM Lotus Domino.
<timezone_alias_namespace> is a string that corresponds to a time zone namespace in Oracle Beehive and is used to map time zones from IBM Lotus Domino to Oracle Beehive, and vice versa. By default this is set to JAVA. Do not change this value, unless advised to do so by Oracle support.
Example 1: Configuring a Coexistence Remote System
In this example, you configure a Coexistence Remote System with the name test against a IBM Lotus Domino residing on a server host named, servertest.ca.oracle.com, by using the following command:
beectl> add_coexistence_system --name test --product_name domino --use_http --host_name servertest.ca.oracle.com --port 7777 --partnership_key Welcome1
This command produces the following result:
Coexisting remote system has been successfully created. ---------------------------------------------------------------------------------- General Name : TEST Product Name : DOMINO URL : http://servertest.ca.oracle.com:7777/coexConnector/CoexMLPort Timezone alias namespace: JAVA
This section describes some of the behaviors that you may encounter while installing the Oracle Beehive Collaboration Coexistence Gateway.
This section includes the following topics:
Both Oracle Beehive and IBM Lotus Domino support the concept of repeating meetings with no recurrence rules, which makes it possible to maintain a link between instances even if the particular system does not understand the recurrence rule provided.
However, Lotus Notes does not allow a user to modify the parent information of a recurring meeting. Therefore, a user cannot change the recurrence pattern of a meeting once it has been created. If a recurrence has been modified in Oracle Beehive, then the Coexistence Connector may have to cancel the previous recurrence and invite the participants to a new recurring meeting, which would mean that their participation status is reset.
Additionally, Lotus Notes is unable to modify multiple recurring instances differently with a single message if the changes made are not identical for each instance. As such, the Coexistence Connector will have to send an e-mail for each modified instance to the invited Domino participants. However, Lotus Notes is capable of detecting a set of related e-mail invitations and ask the users whether they wish to automatically apply the changes to all related meeting e-mails, which improves the usability.
Also note that the IBM Lotus Domino server and the Notes client do not allow unbounded recurrences. However, using the IBM Lotus Domino Outlook Connector, a user can create unbounded recurrences, which the IBM Lotus Domino server would limit to a certain number of instances. For more information, see your IBM Lotus Domino documentation.
Additionally, when modifications are made to a recurring meeting in IBM Lotus Domino, in Oracle Beehive the meetings show every occurrence as an exception.
The following e-mail messages are sent to Oracle Beehive with an ICS attachment, where applicable:
Tasks assignments to Oracle Beehive are sent as e-mail messages.
Meetings that Domino attendees delegate to Oracle Beehive attendees are sent as e-mail messages, because this feature is not supported by Oracle Beehive.
Comments or requests for comments when responding to meetings that are accepted are sent to Oracle Beehive as e-mail messages.
When an Oracle Beehive user proposes a new meeting date, time, or location, the participant Status of the user is set to Tentative in Oracle Beehive and the meeting organizer receives the counter proposal through e-mail.
IBM Lotus Domino only supports personal day events (there is no support for Day Event invitations.) Therefore, as day events are handled differently in IBM Lotus Domino and Oracle Beehive, the following behaviors are expected:
Day Events Created in IBM Lotus Domino
Day events that are created in IBM Lotus Domino appear in Oracle Beehive as meetings that occur from 4 a.m to 8 p.m. For more information about importing data from IBM Lotus Domino, see "Manually Importing User Data".Day events created in IBM Lotus Domino by the Outlook Connector appear in Oracle Beehive as meetings that occur from 4 a.m. to 8 p.m.As a day event is a personal event in IBM Lotus Domino, no free/busy information is sent to Oracle Beehive, and the user's time appears as free for that specific day in Oracle Beehive.
Day Events Created in Oracle Beehive
When a Coexistence Oracle Beehive user invites a Coexistence Remote User to a day event, the day event is displayed in the Coexistence Remote User's agenda on IBM Lotus Domino as a blocking meeting that occurs from 4 a.m. to 8 p.m.The Coexistence Domino user should then select the Mark As Available option while accepting the event so that the user's free/busy status remains unchanged.
It is recommended to include coexlotusfb as part of the IBM Lotus Domino Server Task, so when coexistence starts, the free/busy process stars automatically. To do this, include coexlotusfb under the ServerTask parameter list of the IBM Lotus Domino configuration file notes.ini.
When free/busy information is sent from IBM Lotus Domino to Oracle Beehive, it is always for a 3 months range, starting from the current time, in 15 min interval. Therefore, one hour long meeting created in Lotus Domino occupies four fifteen minute interval, and a five minute meeting occupies an entire interval of fifteen minutes in Oracle Beehive.
Oracle recommends that the maximum attachment size (configured by default to be 2 MB) not be increased beyond 10 MB. Any cross-scheduling messages greater than 10 MB will not be transferred from Oracle Connector for Exchange to Oracle Beehive.
Note:
The same restrictions apply to files attached to meetings created in Oracle Beehive. You must modify the value of the maximum size for attachments in Oracle Beehive so that the configuration changes are automatically sent to the Oracle Connector for Domino. If the configuration changes are made on Oracle Connector for Domino first, then the same modifications must be made in Oracle Beehive as the changes will not be propagated.Holidays imported within Domino by end users are not imported to Oracle Beehive while provisioning a user as an Coexistence Remote User or as an Coexistence Beehive user. These holidays are not imported by the import_coexistence_data option, either.
As Oracle Beehive does not support counter proposals on meeting or delegation on the basis of each meeting, both these options are enforced by default when a Coexistence Beehive User invites a Coexistence Remote user.
This section describes how to troubleshoot issues that you might encounter while installing and configuring Oracle Collaboration Coexistence Gateway.
You can, at any time, modify the logging properties for the Coexistence Service from beectl. This will include additional trace in the BEEAPP log itself along with all the other services. Note that only the Coexistence Service logging will then be included in the log.xml file. There is no need to bounce the BEEAPP container, changes will take effect immediately. For additional logging, contact support.
Example 7 Enabling CoexistenceService logging
Find your BEEAPP instance name using:
beectl> status
The preceding command returns a result similar to the following:
BEEAPP_site1.stamm01.us.oracle.com
Modify the Coexistence Service logging using the following command:
beectl> modify_property --component <beeapp_name>:LoggingProperties --name ModuleLogLevel --value "oracle.ocs.collabcoex.service.coexistence.task:FINER" --activate_configuration
For example:
beectl> modify_property --component BEEAPP_site1.stamm01.us.oracle.com:LoggingProperties --name ModuleLogLevel --value "oracle.ocs.collabcoex.service.coexistence.task:FINER" --activate_configuration
Enabling Coexistence Gateway Logs
The Coexistence Gateway generates different log files based on the tasks executed, including:
Generic communication service log
Requests coming in from Oracle Beehive
Requests going out to Oracle Beehive
Free/busy requests
Import requests
All log files can be found in the following location (assuming the default installation path):
ORACLE_HOME\beehive\collabcoex_domino_connector\logs
To modify the log level, navigate to conf and edit the OGLOConfiguration.xml file and then add the following fragment:
<Section Name="loglevel"> <Property Name="default" Value="FINEST" /> </Section>
This section describes how to perform the administrative tasks related to Oracle Collaboration Coexistence Gateway. This section includes the following topics:
This section describes how to perform the administrative tasks related to the Oracle Beehive Coexistence Service. The instructions in this section are based on beectl shell.
For more information about the beectl commands used in this section, see "Oracle Beehive Command-Line Utility" in the Oracle Beehive Administrator's Reference Guide.
This section includes the following topics:
Oracle Beehive administrators may require details about the Oracle Beehive Remote Coexistence Systems configured on their deployment.
This section includes information about listing all configured Remote Coexistence Systems, by using the list_coexistence_systems command. Run the following command to list the configured Remote Coexistence Systems on your Oracle Beehive deployment:
beectl> list_coexistence_systems
This command produces the following result:
---------------------------------------------------------------------------------- Coexisting remote systems: ---------------------------------------------------------------------------------- General ------------------------ Name : TEST Product Name : DOMINO URL : http://servertest.ca.oracle.com:7777/coexConnector/CoexMLPort Timezone alias namespace: JAVA
To view additional details, use the --show_more option, as shown in the following command:
beectl> list_coexistence_systems --show more
This command produces the following result:
---------------------------------------------------------------------------------- Coexisting remote systems: ---------------------------------------------------------------------------------- General ------------------------ Name : TEST Product Name : DOMINO URL : http://servertest.ca.oracle.com:7777/coexConnector/CoexMLPort Timezone alias namespace: JAVA Configuration ------------------------ State : IN-SYNC Modified On : 8/19/09 10:05 AM Capabilities ------------------------ State : IN-SYNC Expertise : None Cross-scheduling : Meeting
In addition to the information provided by the list_coexistence_systems command, you can use the beectl command list_coexistence_connectors to display information about individual coexistence connectors within a Remote Coexistence System, as shown in the following example:
beectl> list_coexistence_connectors --name TEST
This command produces the following result:
---------------------------------------------------------------------------------- List of coexistence connectors for a coexisting remote system. ---------------------------------------------------------------------------------- Connector Name : Beehive Routing List : null Relay Address Type : null ----------------------------------------------------------------------------------
Oracle Beehive administrators may need to modify certain properties of an Oracle Beehive Remote Coexistence System.
This section includes information about modifying a Remote Coexistence System, by using the modify_coexistence_system command. Different options are used with this command depending on the properties that must be modified.
In the following example, the Remote Coexistence System listed in the "Listing Oracle Beehive Remote Coexistence Systems" section, named TEST, is assigned a new port:
beectl> modify_coexistence_system --select_by_name TEST --port 80
You can also update the partnership_key option of the Remote Coexistence System.
For more information about the modify_coexistence_system command, including available options and syntax, use the following command:
beectl modify_coexistence_system --help
Before users can take advantage of the Oracle Collaboration Coexistence Gateway, Oracle Beehive administrators must provision users for coexistence with a Remote Coexistence System.
This section includes information about provisioning users for coexistence with a Remote Coexistence System, by using the modify_coexistence_profile command.
The following are the prerequisites for provisioning users for coexistence with a Remote Coexistence System using the modify_coexistence_profile command:
The user account must exist on Oracle Beehive.
Oracle recommends that Oracle Beehive and IBM Lotus Domino users have the same primary e-mail address. Ensure that the IBM Lotus Domino SMTP address property of every user is set to the Oracle Beehive e-mail address. This address should be set as primary.
Example 2: Provisioning a User for Coexistence
In this example, buser7 is being provisioned for coexistence with Remote Coexistence System TEST.
Use the BEEHIVE argument for the --accessible_system option to indicate an Oracle Beehive user who is coexisting. In addition, Oracle Beehive deployment supports multiple Oracle Coexistence Systems. The --system_affinity parameter is mandatory while provisioning Oracle Beehive users, as shown in the following example:
beectl> modify_coexistence_profile --accessible_system BEEHIVE --system_affinity TEST --user loginid=buser7
The command produces the following result:
Coexistence profile has been created and processing is initiated. =================================================================== User Name: beehive7 Affinity with system: TEST Accessible systems: BEEHIVE Last Modification: 8/20/09 8:19:51 AM State: CREATED Request Status: No Request Submitted Next Attempt After: 8/20/09 8:19:51 AM ===================================================================
Example 3: Provisioning a Domino User for Coexistence
In this example, duser8 is provisioned for coexistence with Remote Coexistence System TEST.
Use the Coexistence system name (as defined when creating the Coexistence Remote System) argument for the --accessible_system option to indicate that the user is a Coexisting Domino User, as shown in the following example:
beectl> modify_coexistence_profile --accessible_system TEST --user loginid=duser8
This command produces the following result:
Coexistence profile has been created and processing is initiated. =================================================================== User Name: domino8 Affinity with system: TEST Accessible systems: TEST Last Modification: 8/20/09 9:47:08 AM State: CREATED Request Status: No Request Submitted Next Attempt After: 8/20/09 9:47:08 AM ===================================================================
Using Gather Stats() after Bulk Provisioning User Accounts
The first time you bulk load users, during the upload, the database statistics will quickly become out of date. This can lead to poor system performance, both during and after the upload process. If you are loading a large number of users, consider using the gather stats() function in the Oracle Beehive database.
To improve performance, you can use the following SQL*plus command (as either the SYS or BEE_DATA user) to force the database to refresh statistics:
exec dbms_stats.gather_schema_stats('BEE_DATA',GRANULARITY=>'ALL');
Consider gathering statistics in one of the following ways:
Split the load into two files, with one small batch and one large. Run the small batch, then use the function gather stats(), and then do the larger batch
Run gather stats() while doing the bulk load all at once. This option will slow performance of the bulk load while gather stats() is running.
In either case, if you are loading a large amount of users, then this should provide a significant performance improvement after the database command completes.
After running the modify_coexistence_profile command, the registration process begins. To verify if the registration process has completed, refer to the "Viewing the Registration State of Coexisting Users" section.
To avoid or delay the data import process of coexistence users (which normally occurs automatically), run the modify_coexistence_profile command with the --no_data_import option. You can then use the import_coexistence_data command to manually trigger user data import.The following are the reasons for manually importing user data:
To customize date ranges and data types for a subset of users.
To trigger the import at a later time, and not immediately when users are registered for coexistence.
To reattempt the import manually if the automated data import has failed or partially succeeded.
To extend the date ranges to get more data in the past.
To register a coexistence user without importing the user data into Oracle Beehive, use the --no_data_import option, as shown in the following example:
beectl> modify_coexistence_profile --accessible_system BEEHIVE --no_data_import --system_affinity TEST --user loginid=buser7
To manually import coexistence user data into Oracle Beehive, use the beectl command import_coexistence_data, as shown in the following example:
beectl> import_coexistence_data {--user <user_cen> | --email <user_email> } --data_type <type> [--data_type <type> ...] [--timerange_start <start>] [--relative_timerange_start <relative_start>] [--timerange_end <end>] [--relative_timerange_end <relative_end>]
To specify one or more types of user data to import, use the --data_type option. The valid types of user are: MEETING, TASK, CONTACT or MESSAGE.
Note:
For coexistence with IBM Lotus Domino, Oracle Beehive currently supports theMEETING data type only.To specify an absolute range of time for which all data must be imported, use the --timerange_start and --timerange_end options. You can use a timestamp, for example, 2007-10-01T12:00:00Z.
You can also use the keywords NOW (to specify a time range beginning or ending with the current time) or INFINITY (to specify that there should be no limit).
To specify a relative range of time (in days) for which all data must be imported, use the --relative_timerange_start and --relative_timerange_end options. Specify an integer for each option. A negative integer represents the number of days prior to the current date, while a positive integer represents the number of days from the current date to the value of the positive integer.
For more information about the import_coexistence_data command, including available options and syntax, see "import_coexistence_data" in the Oracle Beehive Administrator's Reference Guide.
Example 4: Manually Importing User Data
In this example, the MEETING data type is imported for user duser3 from the Remote Coexistence System TEST using the following command.
beectl> import_coexistence_data --data_type MEETING --user user=duser3 --timerange_start=-INFINITY --timerange_end INFINITY
The command produces the following result:
The following data import requests were created: -------------+----------------------+------------------------------------------- Data type | Time range start | Time range end -------------+----------------------+------------------------------------------- MEETING | -INFINITY | INFINITY -------------+----------------------+-------------------------------------------
After a user has been provisioned for coexistence, Oracle Beehive attempts to register the user. The user must be registered for coexistence before being able to coexist. Although this occurs automatically, it may take some time to take effect. To view the registration state of coexisting users, use the list_coexistence_profiles command, as shown in the following example:
beectl> list_coexistence_profiles
This command produces the following result:
----------+----------------------+--------------------+-----------+------------- User Name | Affinity with system | Accessible systems | State | Import state ----------+----------------------+--------------------+-----------+------------- domino2 | TEST | TEST | COMPLETED | NONE ----------+----------------------+--------------------+-----------+------------- beehive2 | TEST | BEEHIVE | COMPLETED | NONE ------------+----------------------+--------------------+-----------+------------
The following are the five possible values that can appear in the State column:
CREATED: Indicates that the registration request has been created.
IN-PROGRESS: Indicates that the registration request has been sent to the Oracle Beehive Remote Coexistence System, however, the Oracle Beehive Coexistence service is waiting for a response.
COMPLETED: Indicates that the registration request acknowledgement has been received from the Oracle Beehive Remote Coexistence System and the provisioning, and registration process has completed.
DELETED: Indicates that the user was once provisioned for coexistence, but no longer is.
REJECTED: Indicates that the specified systems are not available for a given user. For example, if you specify Coexistence Remote System name (TEST in our example) as the system for a user that does not exist in the IBM Lotus Domino server, then the registration process will fail and the profile will be set to REJECTED.
Note that the value in the State column must be COMPLETED before a user is fully provisioned for coexistence.
To view the additional information about the registration state of coexisting users, use the list_coexistence_profiles command with the -show more option, as shown in the following example:
beectl> list_coexistence_profiles -show more
The following columns will be displayed when you run the preceding command:
User Name
Accessible systems
State
Last Modification
Import State
Last import
To view the complete information about coexisting users, use the list_coexistence_profiles command with the --show_all option, as shown in the following example:
beectl> list_coexistence_profiles --show all
A result similar to one of the following examples is displayed for each user:
User Name: domino1 Affinity with system: TEST Accessible systems: TEST Last Modification: 8/19/09 10:54:09 AM State: COMPLETED =================================================================== User Name: domino3 Affinity with system: TEST Accessible systems: BEEHIVE Last Modification: 8/20/09 10:15:24 AM State: COMPLETED Data Type: MEETING GUID: guid-71758457AEB9DF61E040578CF7142BEF0000000188DF State: CREATED Latest process time: NOT-STARTED Received entity: 0 Expected entity: 0 Time range start: -INFINITY Time range end: INFINITY
After a user data is imported from the Coexistence Remote System, Oracle Beehive attempts to import the data type specified for the user.
Although the user data is imported automatically, it may sometimes be delayed. To view the Import state of coexisting users, use the list_coexistence_profiles command, as shown in the following example:
beectl> list_coexistence_profiles
This command produces the following result:
----------+----------------------+--------------------+-----------+------------- User Name | Affinity with system | Accessible systems | State |Import state ----------+----------------------+--------------------+-----------+------------- domino3 | TEST | BEEHIVE | COMPLETED | CREATED----------+----------------------+--------------------+-----------+-------------
The following four possible values can appear in the Import State column:
NONE: Indicates that no import request is raised.
CREATED: Indicates that the import request is created.
IN-PROGRESS: Indicates that the import request is sent to the Oracle Beehive Remote Coexistence System, however, the Oracle Beehive Coexistence service is waiting for a response.
COMPLETED: Indicates that the import request acknowledgement has been received from the Oracle Beehive Remote Coexistence System and the data import process has completed.
If a user has been provisioned for coexistence, and coexistence is no longer required thereafter, then the user can be deprovisioned.
This section includes information about provisioning users for coexistence with a Remote Coexistence System, by using the delete_coexistence_profile command.
Example 5: Deprovisioning a User for Coexistence
In this example, buser1 is deprovisioned for coexistence from Remote Coexistence System TEST, by using the following command:
beectl> delete_coexistence_profile --user user=buser1
The following result is displayed:
Coexistence profile has been deleted and processing is started
For more information about the delete_coexistence_profile command, see "delete_coexistence_profile" in Module 2 of the Oracle Beehive Administrator's Reference Guide.
After running the delete_coexistence_profile command, the deprovisioning process begins.
To view the state of the coexistence profile, refer to "Viewing the Registration State of Coexisting Users".
This section explains how to stop and start Oracle Connector for IBM Lotus Domino. The section includes the following topics:
Oracle Connector for IBM Lotus Domino works in tandem with the BeehiveConnectorForDomino OC4J instance. Both are fully integrated and installed on the computer where Oracle Connector for IBM Lotus Domino was deployed.
The BeehiveConnectorForDomino OC4J instance works in tandem with the Oracle Connector for IBM Lotus Domino. It is installed on the same computer as Oracle Connector for IBM Lotus Domino.
To stop the Oracle Connector for IBM Lotus Domino:
Click the Start button on the task bar in the computer hosting Oracle Connector for IBM Lotus Domino Server.
Select Programs.
Select Oracle - domino.
Click Stop SOA suite.
The BeehiveConnectorForDomino OC4J instance works in tandem with the Oracle Connector for IBM Lotus Domino. The BeehiveConnectorForDomino OC4J instance is installed on the same computer as Oracle Connector for IBM Lotus Domino.
To start the Oracle Connector for IBM Lotus Domino:
Click the Start button on the task bar in the computer hosting Oracle Connector for IBM Lotus Domino Server.
Select Programs.
Select Oracle - domino.
Click Start SOA suite.
The Oracle Free Busy Client works in tandem with the Oracle Connector for IBM Lotus Domino. It is installed on the same computer as Oracle Connector for IBM Lotus Domino.
To stop the Oracle Free Busy Client:
From the Domino Lotus Console, run the following command:
tell coexlotusfb quit
To verify the Oracle Free Busy Client status, run the show tasks command and look for the Oracle FB Client tasks.
The Oracle Free Busy Client works in tandem with the Oracle Connector for IBM Lotus Domino. It is installed on the same computer as Oracle Connector for IBM Lotus Domino.
To stop the Oracle Free Busy Client:
From the IBM Lotus Domino Console, run the load coexlotusfb command.
To verify the Oracle free Busy Client status, run the show tasks command and then look for the Oracle FB Client tasks.
You can also configure the Oracle Free Busy Client to start automatically by adding the task in the notes.ini file. To do so, include coexlotusfb under the ServerTask parameter list of the IBM Lotus Domino configuration file notes.ini.
|
 Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|