| Oracle® Web Conferencing Administrator's Guide Release 2 (2.0.4) Part Number B10877-01 |
|
|
View PDF |
| Oracle® Web Conferencing Administrator's Guide Release 2 (2.0.4) Part Number B10877-01 |
|
|
View PDF |
This chapter discusses some sample deployment scenarios, ranging from a basic deployment to a sophisticated one spanning multiple geographical regions. It also explains what an administrator should do to set them up. The best way to review this chapter is to go through each example, because each example builds on the previous.
|
Note: In Chapter 4, "Post-Installation" Oracle Web Conferencing properties are set using .imt files. The examples use the setProperty command in imtctl (the command used by the .imt files) to set Web Conferencing properties. It is important to remember that when the option "-system true" is used in setProperty, the setting of the property has a global scope and affects not just the instance on which imtctl is being invoked. If the |
See Chapter 4, "Post-Installation" for basic information about the following:
For all examples, one Oracle9iAS instance is on the machine with the Real-Time Collaboration Core Components and only one Real-Time Collaboration instance is on this machine. For these examples, it is assumed that Oracle9iAS Web Cache is disabled on the mid-tier.
This is the simplest deployment and is generally used to create a pilot deployment. In this deployment, users can access Oracle Web Conferencing from the Internet, through their proxy across the Internet, and through the intranet.
Text description of the illustration basicdep.gif
In Figure 6-1, "Web Conferencing Basic Deployment", Host 1 and Host 2 are deployed in the same DMZ, while Host 3 and Host 4 are deployed in the corporate intranet.
These are the mandatory associations that must be made for the various parts of Oracle Web Conferencing to work:
Additional configuration issues are discussed in the rest of the chapter.
Host 1: Oracle9iAS plus Real-Time Collaboration Core Components set up and configured to use the Oracle9iAS Infrastructure on Host 4.
Host 4: Oracle9iAS Infrastructure needs to be set up on this machine.
Host 2: A Windows NT computer with specialized telephony hardware and software.
Host 3: Oracle9i Database (9.2.0.1) for the Real-Time Collaboration Repository.
| See Also:
Oracle Collaboration Suite Installation and Configuration Guide for Solaris for additional information on the prerequisites |
Configure Oracle Web Conferencing to leverage existing enterprise e-mail and proxy servers for its functionality. Assume that the settings are as follows:
You must configure the settings in Table 6-1 and Table 6-2 every time you install Web Conferencing.
In addition, you must configure Host 2 as follows:
On Host 1, install the Real-Time Collaboration Core Components, and provide the required port numbers. On Host 2, install the Document and Voice Conversion Servers, and provide the required port numbers.
| See Also:
Oracle Collaboration Suite Installation and Configuration Guide for Solaris for details |
Invoke the imtctl commands in this section, while setting Web Conferencing properties. The commands in this section are based on the data in the Settings tables in Section 6.1.3, "Settings".
imtctl> setProperty -system true -pname SmtpHost -pvalue "mail-net.company.com"
Because the port is 25 (which is default), there is no need to set the port.
imtctl> setProperty -system true -pname UserAgentProxyHost -pvalue "www-proxy.company.com" imtctl> setProperty -system true -pname UserAgentProxySSLHost -pvalue "www-proxy.company.com" imtctl> setProperty -system true -pname UserAgentProxyExclusions -pvalue "[\".company.com\"]"
|
Note: Because the default proxy port for HTTP is 80 and HTTPS is 443, there is no need to set these ports. |
Make the necessary configuration changes to the Oracle HTTP Server in which mod_imeeting is configured. mod_imeeting is included through the
$ORACLE_HOME/imeeting/conf/mod_imeeting.conf file, which in turn gets included in $ORACLE_HOME/Apache/Apache/conf/oracle_apache.conf file for Oracle HTTP Server.
Add the following include line for mod_imeeting.conf in oracle_apache.conf:
Include "$ORACLE_HOME/imeeting/conf/mod_imeeting.conf"
Replace $ORACLE_HOME with the actual Oracle home.
$ORACLE_HOME/dcm/bin/dcmctl -v updateConfig -ct ohs
$ORACLE_HOME/dcm/bin/dcmctl -v restart -ct ohs
For one mx process (installer default), invoke:
imtctl> setProperty -ct mxcomm -pname MxRedirectPort -pvalue "[\"2420\"]"
imtctl> setProperty -pname ApacheWebHost -pvalue "imeeting1.company.com"
Because 80 and 443 are defaults, no additional steps are required for setting the ports.
Web Conferencing reports can be generated and sent via e-mail using the imtreport script. The script is located at $ORACLE_HOME/imeeting/bin and is invoked as "imtreport" on all platforms. The actual script file is "imtreport" for UNIX and Linux and "imtreport.cmd" for Microsoft Windows. Mandatory report options such as the recipient list are set by editing variables at the top of the report script. The script contains comments on the options provided. Be sure to edit the proper script for the platform you are using. You may want to send out automated weekly reports by using some operating system provided mechanism for invoking the script on a weekly basis (for example, cron job on UNIX or the Task Scheduler on Windows).
Set up your monitoring infrastructure to periodically ping the following URLs:
http://imeeting1.company.com/imtapp/servlet/ImtTestServlet?mtgtest=true
http://imeeting1.company.com/imtapp/servlet/ImtTestServlet?voiceconvtest=true
http://imeeting1.company.com/imtapp/servlet/ImtTestServlet?docconvtest=true
See Section 7.6, "Real-Time Collaboration Interfaces" for more information.
No post-installation configuration is required.
Invoke imtctl> runTests. This runs the full verification test.
Typically, all tests succeed. However, if this command is run before Host 2 is set up, the Voice Conversion Server test and the Document Conversion Server test will fail.
Run this test as described in Section 6.1.1, "Sequence of Steps".
Invoke imtctl> getState to verify that the processes are up, but the real test needs to be invoked on Host 1 (imtctl> runTests) to make sure that the document and voice conversion services provided by Host 2 are available.
In this deployment, Host 1, Host 2, and Host 5 are deployed in the DMZ, while Host 3 and Host 4 are deployed in the corporate intranet.
Text description of the illustration multimid.gif
Host 1: Oracle9iAS mid-tier set up and configured to use the Oracle9iAS Infrastructure on Host 4
Host 5: Oracle9iAS mid-tier set up and configured to use the Oracle9iAS Infrastructure on Host 4
Host 4: Oracle9iAS Infrastructure needs to be set up on this machine.
Host 2: A Windows NT computer with specialized hardware and software
Host 3: Oracle9i Database for the Real-Time Collaboration Repository
Using the instructions in the Advanced Configuration document at http://otn.oracle.com/products/webconferencing/, configure the LBR/Oracle9iAS Single Sign-On for multiple sets of Real-Time Collaboration Core Components. The URL used to access Oracle Web Conferencing will now be "imeeting.company.com," and "imeeting1.company.com" and "imeeting2.company.com" will be behind the LBR. Users will access "imeeting.company.com" and the request will automatically be routed to either imeeting1.company.com or imeeting2.company.com.
| See Also:
Oracle Collaboration Suite Installation and Configuration Guide for Solaris for additional information on the prerequisites |
Configure Web Conferencing to leverage existing enterprise e-mail and proxy servers for its functionality. Assume that the settings are as follows:
Host 1 settings are the same as described as in Table 6-2, "Instance on Host 1".
Configure Host 5 as follows:
On Host 1 and Host 5, install the Real-Time Collaboration Core Components, and provide the required port numbers.
Invoke the imtctl commands in this section, while setting Web Conferencing properties. The commands in this section are based on the data in the Settings tables in Section 6.2.3, "Settings".
imtctl> setProperty -system true -pname GlobalWebHost -pvalue "imeeting.company.com"
Follow steps 2-7 as defined in Section 6.1.5, "Post-Installation".
It is not necessary to set up e-mail, proxy, or global Web host, because they are global settings and will apply to this instance, as well.
Follow the step as defined in Section 6.1.5, "Post-Installation".
Follow the step as defined in Section 6.1.5, "Post-Installation".
No post-installation steps are required.
Invoke imtctl> runTests. This runs the full verification test.
Typically, all tests succeed. However, if you run this command before setting up Host 2, the Voice Conversion Server test and the Document Conversion Server test will fail.
Run this as described in the Section 6.2.1, "Sequence of Steps".
Invoke imtctl> runTests. This runs the full verification test.
Typically, all tests succeed. However, if you run this command before setting up Host 2, the Voice Conversion Server test and the Document Conversion Server test will fail.
Run this as described in Section 6.2.1, "Sequence of Steps".
Invoke imtctl> getState to verify that the processes are up, but the real test needs to be invoked on Host 1 and Host 5 (imtctl> runTests) to make sure that the services provided by Host 2 are available.
Text description of the illustration disprdep.gif
In this deployment, Host 1, Host 2, Host 5, and Host 6 are deployed in the DMZ. Host 3 and Host 4 are deployed in the corporate intranet.
This is almost identical to the previous example (Section 6.2, "Multiple Real-Time Collaboration Core Components and Load Balancer") with the following key differences:
Refer to Table 6-5 and Table 6-5 in the previous section for all the values for Host 1 through Host 5 and system settings. The changes are as follows:
| Setting Name | Value | Comments | Web Conferencing Property |
|---|---|---|---|
|
Location of Host 5 |
"UK" |
Post-installation step. |
InstanceLocation |
| Setting Name | Value | Comments | Web Conferencing Property |
|---|---|---|---|
|
Location |
"US" |
Post-installation step. |
InstanceLocation |
Follow all installation, prerequisite, and post-installation instructions from Section 6.2, "Multiple Real-Time Collaboration Core Components and Load Balancer" in addition to the following:
imtctl> setProperty -pname InstanceLocation -pvalue "US"
Set this up to serve the Real-Time Collaboration Core Components on Host 1.
imtctl> setProperty -pname InstanceLocation -pvalue "[\"US\"]"
imtctl> setProperty -pname InstanceLocation -pvalue "UK"
Set this up to serve the Real-Time Collaboration Core Components on Host 5.
imtctl> setProperty -pname InstanceLocation -pvalue "[\"UK\"]"
Text description of the illustration newmtier.gif
Existing Web Conferencing Deployment with Additional Core ComponentsThis example shows the addition of a machine, Host 7, to the configuration shown in the previous example. The changes are as follows:
Host 7: Oracle9iAS mid-tier set up and configured to use the Oracle9iAS Infrastructure on Host 4.
| See Also:
Oracle Collaboration Suite Installation and Configuration Guide for Solaris for details |
Configure Host 7 as follows:
On Host 1 and Host 5, install the Real-Time Collaboration Core Components, and provide the required port numbers.
Invoke the imtctl commands in this section, while setting Web Conferencing properties. The commands in this section are based on the data in the Settings tables in Section 6.4.3, "Settings".
It is not necessary to set up e-mail, proxy, or global Web host, because they are global settings and will apply to this instance, as well.
Follow the step as defined in Section 6.1.5, "Post-Installation".
imtctl> setProperty -pname InstanceLocation -pvalue "US"
Follow the step as defined in Section 6.1.5, "Post-Installation".
Restart Host 2 so that it recognizes the Real-Time Collaboration Core Components on Host 7.
Invoke imtctl> runTests. This runs the full verification test.
All tests succeed.
Text description of the illustration newspsvc.gif
Another machine with Document and Voice Conversion Servers is added (Host 8).
See the Oracle Collaboration Suite Installation and Configuration Guide for Solaris for additional information on the prerequisites.
| Setting Name | Value | Comments | Web Conferencing Property |
|---|---|---|---|
|
HTTP listening port for the Voice Conversion Server |
2460 |
Set during installation |
|
|
Location |
"US" |
Post-installation step |
InstanceLocation |
On Host 8, install the Document and Voice Conversion Servers, and provide the required port numbers.
imtctl> setProperty -pname InstanceLocation -pvalue "[\"US\"]"
imtctl> stop and then imtctl> start.Invoke imtctl> getState to verify that the processes are up, but the real test needs to be invoked on Host 1 (imtctl> runTests) to make sure that the services provided by Host 8 are available.
Shut down Host 2.
Invoke imtctl> runTests. This runs the full verification test.
All tests succeed.
The topology is identical to the basic deployment, but the Document and Voice Conversion Servers are deployed in a different DMZ.
Text description of the illustration spsvcdmz.gif
The following additional configuration is required:
|
 Copyright © 2002, 2003 Oracle Corporation All Rights Reserved. |
|