| Oracle® Real-Time Collaboration Administrator's Guide 10g Release 1 (10.1.2) Part Number B25460-03 |
|
|
View PDF |
| Oracle® Real-Time Collaboration Administrator's Guide 10g Release 1 (10.1.2) Part Number B25460-03 |
|
|
View PDF |
This chapter discusses postinstallation steps to configure commonly used options of your Oracle Real-Time Collaboration system. It also provides an overview of the ways in which you can stop and start Oracle Real-Time Collaboration components. This chapter provides a brief overview about the configuration tool used to install Oracle Real-Time Collaboration if it was not installed during original installation of Oracle Collaboration Suite; please see the Oracle Collaboration Suite Installation Guide for your operating system for all details about installation. This chapter contains the following sections:
Postinstallation Configuration for Oracle Real-Time Collaboration
Recommended Postinstallation Checks for Oracle Real-Time Collaboration
Starting and Stopping Oracle Real-Time Collaboration Components
Using the Configuration Wizard for Oracle Real-Time Collaboration
When performing the tasks described in this chapter, you will set various Oracle Real-Time Collaboration properties. For more details about properties, see Chapter 3.
You will run rtcctl commands while setting properties. For more details about the rtcctl utility, see Chapter 4.
After you install the Oracle Real-Time Collaboration system, you may want to set up one of the following common configurations, outlined in the following sections:
If you want to open Oracle Real-Time Collaboration for HTTPS connections from outside the intranet, follow the steps described in "Setting Up an Oracle Real-Time Collaboration SSL Listening Point".
The minimum postconfiguration steps are described in "Setting Up Oracle Real-Time Collaboration E-mail and Administration".
If you plan to use Oracle Calendar with Oracle Real-Time Collaboration, follow the steps in "Setting Properties Required for Use with Oracle Calendar".
If you plan to hold conferences with streaming audio over a PSTN phone line, and you have installed the Voice Conversion Server, follow the steps in "Setting Up Voice Conversion Servers for Oracle Real-Time Collaboration".
You can verify Oracle Real-Time Collaboration installation using the runTests command. See "Verifying Configuration" for details.
In addition to these setup steps, you may also want to set up or review the following options:
To create clusters for different geographic locations: You must set properties to identify the location of each of your Oracle Real-Time Collaboration instances. See "Configuring Clusters" for details.
To use SSL encryption for conference and message data: You must set Oracle Real-Time Collaboration to use SSL encryption. See "Enabling SSL in Oracle Real-Time Collaboration" in Oracle Collaboration Suite Security Guide for details about setting up security for Oracle Real-Time Collaboration. See "ConfiguringSSL Security" for details about the properties used to set SSL encryption for Oracle Real-Time Collaboration.
To monitor Oracle Real-Time Collaboration components: You can set your third-party monitoring system to periodically ping a set of service availability tests. See "Monitoring Service Availability" for details.
To review the default behavior for commonly used Oracle Web Conferencing features: Commonly used Oracle Web Conferencing features are enabled by default. For security reasons, you may want to disable some of these features. See "Commonly Used Properties for Oracle Web Conferencing" for details.
To review the default settings for properties that control Integration Services: By default, most of the Integration Services that let you programmatically access any of the Oracle Real-Time Collaboration features are enabled. For security reasons, you may want to disable some of these services. See "Configuring Integration Services Using Properties" for details.
You must set up an Oracle Real-Time Collaboration SSL listening point if you want to allow HTTPS connections from outside the intranet. The machine on which Oracle Collaboration Suite is installed must be accessible from the Internet, and the HTTPS port must be open through the firewall (port 443 is recommended).
To set up an SSL listening point, follow these steps:
Log in to Web Cache Administration by using the following URL:
http://<mid-tiermachine>:<port number>/webcacheadmin
The default web cache port number is 9400. The port number can be obtained from the value of the Web Cache Administration port found in <$ORACLE_HOME>/install/portlist.ini.
Click Listen Ports under Ports to add an entry for the HTTPS protocol.
Click Add and enter the following values:
IP Address: ANY
Port Number: Value of Oracle HTTP Server SSL port found in <$ORACLE_HOME>/install/portlist.ini
Protocol: HTTPS
Require Client Side Certificate: Do not enable
Wallet: <$ORACLE_HOME>/webcache/wallets/default
Click Submit.
Click Apply Changes.
|
Note: Adding an SSL listening point does not make Oracle Real-Time Collaboration secure. See "ConfiguringSSL Security" for information on configuring Oracle Real-Time Collaboration for SSL. |
You perform the following steps once so that you can use Oracle Real-Time Collaboration to hold conferences and send messages.
Step 1 Integrate with existing e-mail.
The Oracle Real-Time Collaboration system can generate outbound e-mail for various purposes, such as inviting users to a conference, and allowing users to send feedback. Depending on how you installed Oracle Collaboration Suite, you may need to configure the Oracle Real-Time Collaboration system with information about your SMTP host and administrator email account. If you need to perform this step, you only do it once. This e-mail feature is specifically for use by Oracle Real-Time Collaboration and is separate from the e-mail capabilities offered by Oracle Mail.
On a system containing a Oracle Real-Time Collaboration core component instance, enter the following commands:
$ORACLE_HOME/imeeting/bin/rtcctl rtcctl> setProperty -system true -pname SmtpHost -pvalue mailhost.mycompany.com rtcctl> setProperty -system true -pname SmtpPort -pvalue 25 rtcctl> setProperty -system true -pname EmailEnabled -pvalue true rtcctl> setProperty -system true -pname AdminEmail -pvalue administrator@mycompany.com rtcctl> setProperty -system true -pname ContactFromEmail -pvalue support@mycompany.com
SmtpHost and SmtpPort identify your SMTP mail server and the port it listens on. EmailEnabled is a toggle to enable sending e-mail for conference invitations. AdminEmail is the e-mail account that receives mail from the "Contact Us" link on the Oracle Real-Time Collaboration Web Client pages. ContactFromEmail is the e-mail account used to send the mail from "Contact Us" submissions.
See "Configuring E-mail Invitations" and "Configuring Customer Feedback E-Mail Accounts" for more details about these properties.
Step 2 Set up the administrator role.
You must have at least one user with full business administrator privileges. The business administrator can monitor the system, view reports, create and maintain any custom sites, and check system status. To set this user, you use the modifyRole command within rtcctl. You do this step once.
On a system containing an Oracle Real-Time Collaboration instance, enter the following command. Substitute the appropriate user name for the sample shown.
$ORACLE_HOME/imeeting/bin/rtcctl modifyRole -username joe.smith -rolename businessadmin
See "Setting User Roles" for more details about this command.
There are two properties that affect interactions between Oracle Real-Time Collaboration processes and Oracle Calendar. Depending on how you choose to use these components together, you may need to set the properties described in this section.
If your company uses both Oracle Calendar and Oracle Web Conferencing, you may require users to schedule conferences solely through the calendar. To do so, you set the IsCalendarOCSInstalled property to prevent the Schedule tab from appearing on the Oracle Real-Time Collaboration Web Client pages.
Setting this property means that the Schedule tab is not available to any users. Any references to the Schedule tab in this manual will no longer apply.
See "Suppressing the Schedule Tab if Oracle Calendar is Used" for more details about this property.
Oracle Real-Time Collaboration can allow access to conferences and instant messages from nonregistered users (users not in your Oracle Internet Directory). You may decide to prevent this, by setting the GuestUserAccessEnabled property to false.
If you prevent access in this way, you must be certain to set the allowguestusers parameter in Oracle Calendar to false as well. If allowguestusers is true, and your users schedule a conference in Oracle Calendar and invite users who are not in your Oracle Internet Directory, the conference will be scheduled but the nonregistered users will not get the invitation.
On a system containing an Oracle Real-Time Collaboration instance, enter the following command:
rtcctl> setProperty -system true -pname GuestUserAccessEnabled -pvalue false
This will prevent guest user access at the syste level. You can also set this property for a specific site to prevent guest user access for just that site.
See "Preventing Guest User Access" for details about setting the GuestUserAccessEnabled property. See Chapter 3, "Calendar Server Parameters" of Oracle Calendar Reference Manual for details about setting the allowguestusers parameter.
If you use streaming voice over a PSTN phone line in Web conferences, you should configure the dial-in information for your Voice Conversion Server as described in the following steps:
Set the VoiceDialInPrefix property. This property provides the dial-in prefix for any voice calls made through Oracle Real-Time Collaboration. For example, many companies require users to enter a 9 before dialing out; you can enter that value into the dial-in prefix property. On the Voice Conversion Server, you would enter:
$ORACLE_HOME/imeeting/bin/rtcctl setProperty -i instance-name -pname VoiceDialInPrefix -pvalue 9
See "Configuring Voice Conversion Servers" for details about this property.
Set up system dial-ins.
System dial-ins are available to all Oracle Web Conferencing users. Typically, system administrators create system dial-ins for phone conference vendors that are used commonly by the users of the system.
Enter the system dial-in using the AddSysDialin command in rtcctl.
$ORACLE_HOME/imeeting/bin/rtcctl addSysDialin -name Name_for_Dial-in -sequence dial-in sequence
When entering a dialing sequence, remember:
Include whatever prefix your country requires for dialing between regions, or from one country to another.
For example, users dialing inside the U.S. must enter a 1 followed by the area code number. Users dialing from the U.S. to countries outside the U.S. must enter 011 followed by the country code, then the area code and number.
To have the dialing pause for 1 second, insert a comma (,).
If users must press the hash sign (#) or asterisk (*) keys after entering a number, include the # or * in the dialing sequence.
System dial-ins serve as examples for users; they may be missing information such as the specific user Personal Identification Number (PIN) or conference ID. For example, a system administrator might create a systemwide dial-in for a particular conference vendor that contains the toll-free number for the vendor, followed by a placeholder for the PIN and Conference ID and the required entry keys (# or *), with pauses (,). Users would then modify the system dial-in by selecting it when starting a voice-streaming conference, and adding their PIN and Conference ID. Table 2-1 shows sample dial-in sequences.
Table 2-1 Example Dial-Ins
| Dial-in Name | Dial-in Sequence |
|---|---|
|
Audio Conferencing Vendor (US) |
18005555555,<ADD PIN HERE>#,,,,,,,,,,#,,,,,,,,,# |
|
Joe's account with Audio Conferencing Vendor |
18005555555,8282828#,,,,,,,,,, #,,,,,,,,,# |
See "Setting Conference Dial-In Information" for details about the syntax of the addSysDialIn command.
Optional: If you have set up clusters using the InstanceLocation property to identify different groups of Oracle Real-Time Collaboration components, you can assign InstanceLocation properties to your Voice Conversion Server to have it support a specific group of components. See "Configuring Clusters" for details about how to set this property.
Run the following test to verify that the Oracle Real-Time Collaboration core components have been configured correctly.
$ORACLE_HOME/imeeting/bin/rtcctl runTests -system true
You can also run individual tests on various services and components of the system using the runTests command. See "Monitoring Service Availability" and "Running Configuration Tests" for details about these tests.
To verify that any Voice Conversion Server is set up correctly, shut down any other Voice Conversion Servers that are assigned to serve the same Oracle Real-Time Collaboration core components. Then, on a core component system, enter:
$ORACLE_HOME/imeeting/bin/rtcctl runtests -testlist voiceconvtest
Do the same for the Document Conversion Server:
$ORACLE_HOME/imeeting/bin/rtcctl runtests -testlist docconvtest
See "Testing and Monitoring the System" for more information about the runTests command.
|
Note: If you use clusters, the Voice Conversion Server availability test and the Document Conversion Server availability test will fail on the core components instance if the Document Conversion and Voice Conversion Servers do not have InstanceLocation properties that match the InstanceLocation of the Oracle Real-Time Collaboration core components instance. See "Configuring Clusters" for information about setting the property. |
After you have installed Oracle Real-Time Collaboration and performed the configuration tasks outlined in this chapter as necessary, you can determine whether the system is running properly by performing any of the optional tasks shown in Table 2-2.
Table 2-2 Recommended Checks for Oracle Real-Time Collaboration System
| Item to Test | Task | Expected Result |
|---|---|---|
|
Provisioning Pages |
Create several users by accessing the User Provisioning pages in the Oracle Internet Directory. |
Users should be created as expected. The RTC component should be listed on one of the pages as an available component. User is able to sign in to the Oracle Real-Time Collaboration Web Client. |
|
Log In |
Log in as an administrator user and verify the change in the Web Client. |
A total of 8 tabs should appear at the top of the page: Home, Schedule, Materials, Archive, Monitor, Site, Reports, System. |
|
UI Check |
Click each of the administrative tabs (right four tabs). |
All the administrative pages should appear with no reported errors. |
|
Materials |
Click the Material tab and upload Microsoft PowerPoint, Word, and Excel documents, and an HTML document. If possible, upload one PowerPoint document with Multibyte type characters present. |
The documents should be uploaded successfully. Appropriate confirmation messages should display. Documents can be opened for preview. |
|
Schedule |
Schedule a conference. Set the Audience type set to All Users. In the Attendees section include the login names of both registered and nonregistered participants. |
The conference should be scheduled successfully and confirmation messages received by the attendees. This conference should be visible in the conference tables from the home page, and it can be joined directly from the e-mail invitation. |
|
Schedule |
Schedule another conference. Set the Audience to Registered Users. Choose any other options you want to test. |
The conference should be scheduled successfully and confirmation messages received by any attendees. Other settings applied during the scheduling process should appear. Nonregistered users should receive an error message if they attempt to attend. |
|
Instant conference |
Start an instant conference from the home page. |
An instant conference should start. |
|
Join an instant conference |
Join the same conference from another computer as a guest (do not log in). |
Guest should be able to join the conference by entering the conference ID as a guest. |
|
Document Presentation |
While in a conference, click the Document Presentation icon. Select each type of document uploaded previously. Pass shared control and presenter's rights to one of the participants. |
Every uploaded document can be viewed with conference participants. Once an attendee receives granted control, he should be able to control the current document or display one of his own as a presenter. |
|
Whiteboard |
While in a conference, click the Whiteboard icon and draw on the whiteboard. Do the same as an attendee. |
Both users should be able to draw at the same time. Content should be passed to all screens simultaneously. |
|
Desktop Sharing |
While in a conference, click the Desktop Sharing icon and use the pull-down menu to share the entire desktop. Share just an application. Share a part of the screen. Check Stop All Sharing. Pass shared control and presenter's rights to one of the participants. |
Shared content should be passed to every participant in the conference. All available share tools should work as expected. Presenters with shared control should be able to browse presented materials. Those granted presenter's rights should be able to present and share their desktops. |
|
Chat |
While in a conference, click to send a chat message from the host to the attendee and vice versa. Check private chat options. |
Message should be sent and received as expected. Private chat should work correctly. |
|
Polling |
While in a conference, click Create a New Poll or select a poll from the list. Send the Poll and let the attendee respond. |
Polls are created and sent to host and participants. All graphs appear as expected. Results appear as users enter responses. |
|
Voice: PSTN Dial-In |
While in a conference, click the Voice icon on the top of the screen. Dial in to your local phone. Make sure participants can hear the stream. |
Voice stream should be initiated. Participants should be able to hear a voice stream to their PC speakers. |
|
Voice: Computer Microphone |
While in a conference, click the Voice icon on the top of the screen. Choose Computer Microphone for the input. Click the Microphone button in the Web Conferencing console, and begin speaking. |
Participants should be able to hear the voice stream through their PC speakers. |
|
Recording |
While in a conference, click the Record (tape) icon. Test both Voice and Data Only options. |
Conference should have been recorded. Playback options for this conference are available for selection in the Archive pages, after the conference has ended. (The host must make playback available to other users before others can see the playback option.) |
|
Playback |
Go to the Archive tab. Play back one of your recorded conferences. Make sure Data and Voice are consistent and quality is acceptable. Test playback tools (Play, Stop, FF, RW). |
Conference playback should work correctly. |
|
Download Oracle Messenger Console |
Choose New User from the home page. Choose to download the Oracle Messenger console. |
File Download dialog box should appear. Options are: Open, Save, Cancel and More Info. Use the Save option to save the oimsetup.exe file. |
|
Install Oracle Messenger |
Execute the downloaded oimsetup.exe file. |
Oracle Messenger icon should appear on the desktop. Double-clicking starts Oracle Messenger sign-in window; user can sign in. |
|
Oracle Messenger File Menu |
Sign out of Oracle Messenger by choosing File and then Sign Out. |
User should be signed out from the system. |
|
Add a contact to Oracle Messenger |
Choose Add and then Contact by ID and create a new contact by entering a valid e-mail address. |
Contact should be created. |
|
Add a group to Oracle Messenger |
Choose Add and then Group and create a new group. |
Group should be created. You should be able to drag contacts to the group. |
|
Send a file using Oracle Messenger |
Select an available contact and choose Send a File. |
A dialog box should appear. You should be able to select a file and send it. Recipient should see a dialog asking him to accept. |
|
Send a message in Oracle Messenger |
Double-click an available contact. Type in a message and press enter. |
Message should be received; recipient should be able to reply. |
|
Leave an Oracle Messenger chat |
While in a chat window, click the Leave Chat button. |
If a chat window has only one participant, clicking Leave Chat should close the window completely. If you are holding multiple chat sessions, clicking Leave Chat should close the chat channel to only that contact. |
|
Voice chat in Oracle Messenger |
Right click an available contact and choose Start Voice Chat. |
Recipient should receive an invitation. If accepted, both parties should be able to speak into their PC microphones and hear each other from their PC speakers. |
|
Start a Web conference from Oracle Messenger window |
Right click an available contact and choose Start Web Conference. |
The invitation window should appear. Can select more online users to invite, enter conference title and password, invitation text message. Web conference should start, and invitations should be received. |
|
Remove a contact from Oracle Messenger |
Right click a contact and choose Remove Contact. |
A delete contact dialog box appears. Clicking OK should remove the contact from the roster or from the selected group. Pressing Cancel or Esc should cancel the process. |
|
Start a Web conference from a chat session |
While in a chat window, click the Start Web Conference button. |
A Web conference should start on the host's computer. Participants should receive an invitation. |
|
Start a chat conference from the Oracle Messenger window |
Click the Chat Conference icon in the Oracle Messenger window. |
A new chat conference window should appear; you should be able to choose participants, send an invitation, and start the chat conference. |
|
Join an existing chat conference |
Click the Chat Conference icon and choose Actions and then Join Existing Chat Conference. Enter the chat conference ID. |
You should be able to join the chat conference. |
|
Download the Oracle Real-Time Collaboration Add-In for Microsoft Office |
Choose New User from the home page. Choose to download the Oracle Real-Time Collaboration Add-In for Microsoft Office. |
File Download dialog box should appear. Options are: Open, Save, Cancel and More Info. Use the Save option to save the addin_setup.exe file. |
|
Install Oracle Real-Time Collaboration Add-In for Microsoft Office |
Execute the downloaded addin_setup.exe file. |
When installation is complete, a help page explaining how to use the add-in will appear. Open Microsoft Outlook and confirm that the Oracle RTC toolbar is visible. |
|
Log in to Oracle Real-Time Collaboration Add-In for Microsoft Office |
From the Oracle RTC menu in the toolbar, choose Preferences. Enter your username and password, and click OK. |
You should be signed in to Oracle Real-Time Collaboration. |
|
Create an instant conference using the Oracle Real-Time Collaboration Add-In for Microsoft Office |
In the Oracle Real-Time Collaboration Add-In for Microsoft Office toolbar, click Instant Conference. |
In the Oracle RTC Instant Conference dialog box, you are prompted to enter a conference title and conference key. After clicking Start Conference, an instant conference should start. |
The Oracle Real-Time Collaboration components and related Oracle Application Server components are started during installation. To start or stop these components, you can do so either using the opmnctl and rtcctl utilities or by using the Oracle Enterprise Manager Application Server Control for Oracle Collaboration Suite.
In addition to using the commands described in the following sections, it is possible to stop specific instance processes using the Diagnostics reports available under the Monitor tab by choosing Conference Details and then Diagnostics. See "Monitoring Current Conferences" for more information.
The following commands should be used only with great caution. They stop all of the following processes on an instance.
opmnctl stopall
This command shuts down all of the following processes:
Oracle HTTP Server Oracle Real-Time Collaboration Application for J2EE (OC4J_imeeting) Oracle Internet DirectoryOracle Real-Time Collaboration process manager (rtcpm) All Oracle Real-Time Collaboration processes running on this instance
rtcctl stop
This command stops every Oracle Real-Time Collaboration process running on the current instance.
The opmnctl startall command starts all processes on an instance, including all Oracle Real-Time Collaboration processes.
You can enter a second start command after a process is already started. For example, you can enter rtcctl start on an instance after you have already entered opmnctl startall.
The following list shows the order in which you can stop and restart ("bounce") Oracle Real-Time Collaboration processes.
Bounce the Oracle HTTP Server:
$ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server
Bounce OC4J_imeeting (Oracle Real-Time Collaboration Application for J2EE):
$ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OC4J process-type=OC4J_imeeting $ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OC4J process-type=OC4J_imeeting
Bounce the Oracle Real-Time Collaboration Applications tier:
$ORACLE_HOME/imeeting/bin/rtcctl rtcctl> stop rtcctl> start rtcctl> getState
|
Note: Stopping and restarting an Oracle Real-Time Collaboration Applications tier halts all active conferences. Do not stop and restart without giving your users sufficient warning to end their current conferences. |
Bounce the Document Conversion Server (installed on a Windows system):
%ORACLE_HOME%\imeeting\bin\rtcctl rtcctl> stop -ct docconv rtcctl> start -ct docconv rtcctl> getState
Bounce the Voice Conversion Server (installed on a Windows system):
%ORACLE_HOME%\imeeting\bin\rtcctl rtcctl> stop -ct voiceconv rtcctl> start -ct voiceconv rtcctl> getState
You can also use the Oracle Enterprise Manager Application Server Control for Oracle Collaboration Suite if you need to stop or start any components, as follows:
On the computer running the instance you want to start or stop, open the Application Server Control page for Oracle Collaboration Suite tools.
Click RTC.
Click the Start or Stop buttons.
This will stop all Oracle Real-Time Collaboration components running on this instance.
To determine which components are running on a particular instance, use the Status report under the System tab in the Oracle Real-Time Collaboration Web Client to view a list.
The Oracle Universal Installer lets you install selected Oracle Collaboration Suite components. If you did not choose to install Oracle Real-Time Collaboration when you first ran the installer, or if you need to change some of the entries in the configuration, you can run the configuration wizard for just Oracle Real-Time Collaboration, as follows.
|
Note: Follow these steps only if you did not install Oracle Real-Time Collaboration when you originally ran the Oracle Universal Installer. Refer to the Oracle Collaboration Suite Installation Guide for your operating system for instructions on starting the Oracle Universal Installer. |
On the computer system where you want to configure the Oracle Real-Time Collaboration core components, open the Application Server Control page for Collaboration Suite tools.
Click Configure Component and select RTC.
Choose the directory in which you want to install the Oracle Real-Time Collaboration core components.
A series of screens will prompt you for the following information:
The directory into which you want to install Oracle Real-Time Collaboration. This will become the Oracle home for Oracle Real-Time Collaboration.
Information about the SMTP server used to email conference announcements to attendees.
The user name and password for the account that Oracle Real-Time Collaboration will use to connect to the Oracle Internet Directory. (The Oracle Internet Directory is used to identify those users who are allowed to participate in Web conferences as registered users, and to identify available contacts for Oracle Messenger.) This user must be an Oracle Application Server administrator.
The database you will use to store the Oracle Real-Time Collaboration data.
You can review your entries and click Back to edit them. When you are satisfied they are correct, click Finish to start the configuration process.
After you have clicked Finish, you cannot cancel the configuration process. If you realize there is an error, return to the Oracle Application Server Control for Collaboration Suite home page and click Configure Component to start configuration again.
As described in "Oracle Real-Time Collaboration Components and Processes", Oracle Real-Time Collaboration uses a Document Conversion Server to let users load Microsoft Office documents and images into their personal materials repository and convert those documents to HTML or text, and convert images to PNG, for display during a conference. Oracle Real-Time Collaboration also uses a Voice Conversion Server to support voice streaming over a PSTN line during a conference (for example, dialing into a teleconference service during a Web conference).
These servers can be installed on the same Applications tier. The computer must be a Windows system, running Windows 2000 Server SP4 or later. To support the Voice Conversion Server, the computer must also have an Intel Dialogic System software 5.1.1 SP1 or later. See "Deploying Oracle Real-Time Collaboration"in Oracle Collaboration Suite Deployment Guide for more details about required hardware.
If you did not install the Document and Voice Conversion Servers during the initial installation process, read the Oracle Collaboration Suite Installation Guide for your operating system for instructions about how to install them.
The following steps show how to reassociate Oracle Real-Time Collaboration 10g Release 1 (10.1.2) with an existing Release 9.0.4.1 Oracle Internet Directory.
|
Note: This procedure is not supported by other Oracle Collaboration Suite components on the same Applications tier. |
Go to the existing Oracle Internet Directory page (http://oid_hostname:port/pls/orasso) and create a new partner application, with the following parameters:
Name: http://applications_tier_hostname
Home URL: http://applications_tier_hostname:port
Success URL: http://applications_tier_hostname:port/osso_login_success
Logout URL; http://applications_tier_hostname:port/osso_logout_success
Change to the $ORACLE_HOME/Apache/Apache/conf/osso/ directory on the Applications tier.
cd $ORACLE_HOME/Apache/Apache/conf/osso
Using the information you set up for the partner application, create a text file named my_file.conf.clr with the following contents:
sso_server_version=v1.2 cipher_key=cipher_key site_id=site_id site_token=site_token login_url=http://hostname:port/pls/orasso/orasso.wwsso_app_admin.ls_login logout_url=http://hostname:port/pls/orasso/orasso.wwsso_app_admin.ls_logout cancel_url=http://hostname
Enter the following command:
$ORACLE_HOME/Apache/Apache/bin/apobfuscate my_file.conf.clr my_obfuscated_file.conf root
Use a text editor to open the mod_osso.conf file.
Change the following entries:
Original text:
<IfModule mod_osso.c>
OssoIpCheck off
OssoIdleTimeout off
OssoConfigFile /rtc/m8e/apps/Apache/Apache/conf/osso/osso.conf
...
New text:
<IfModule mod_osso.c>
OssoIpCheck off
OssoIdleTimeout off
OssoConfigFile /rtc/m8e/apps/Apache/Apache/conf/osso/<SomeName>.conf
...
Use the rtcctl utility to set the following properties on the Application tier.
rtcctl> setProperty -system true -pname ldaphost -pvalue old_release_hostname rtcctl> setProperty -system true -pname ldapport -pvalue old_release_port rtcctl> setProperty -system true -pname ldappassword -pvalue old_release_password rtcctl> setProperty -system true -pname UserProvisioningEnabled -pvalue false
Change to the $ORACLE_HOME/j2ee/OC4J_imeeting/application-deployments/imeeting directory.
Use a text editor to open the orion-application.xml file.
Comment out the following section by adding the <!-- and --> opening and closing markers, as follows:
<!-- <jazn provider="LDAP" >
<property name="s2s.auth.support" value="true" />
</jazn>
-->
Stop and restart applications on the Applications tier:
$ORACLE_HOME/opmn/bin/opmnctl stopall $ORACLE_HOME/opmn/bin/opmnctl startall
Enter the following sqlplus commands:
sqlplus rtc_app/rtc_app_password@dbname SQL> create table rtc_persons_bak as select * from rtc_persons; SQL> create table rtc_users_bak as select * from rtc_users; SQL> delete from rtc_persons where person_id > 9999; SQL> delete from rtc_users where user_id > 9999; SQL> commit;
