This chapter describes the hardware, operating system, and software requirements for installing Oracle Communications Mobile Synchronization Gateway.
You install Mobile Synchronization Gateway in an Oracle GlassFish Server domain.
Table 3-1 lists operating systems that support Mobile Synchronization Gateway.
Table 3-1 Supported Operating Systems
| Operating System | CPU | Required Patches |
|---|---|---|
|
Oracle Solaris 11 |
SPARC, x64 |
See the Oracle Solaris 11 documentation for patch information. |
|
Oracle Linux 6 and Red Hat Enterprise Linux 6 64-bit |
x64 |
See the Oracle Linux documentation and Red Hat Enterprise Linux documentation for patch information. |
Table 3-2 lists software required for installing and running Mobile Synchronization Gateway.
Table 3-2 Software Requirements
| Product | Version | Notes |
|---|---|---|
|
Oracle Directory Server Enterprise Edition |
11.x |
For a fresh installation, use the latest version of Directory Server 11gR1. |
|
Oracle GlassFish Server |
3.1.2.8 (patch 147913-11) |
Required as the web container. Download the patch from My Oracle Support at: |
|
Java |
7 |
Be sure to install the latest security update. |
|
Oracle Communications Convergence |
3.0.0.2.0 |
Optional. |
|
Oracle Communications Messaging Server |
8.0 |
You must use at least Messaging Server 8.0 for a Mobile Synchronization Gateway deployment. |
|
Oracle Communications Calendar Server |
7.0.5.17.0 |
Optional. |
|
Oracle Communications Contacts Server |
8.0.0.1.0 |
Optional. |
|
comms_dssetup.pl |
6.4.0.27.0 |
You must use at least comms_dssetup.pl 6.4.0.27.0 for a Mobile Synchronization Gateway deployment. |
The number and configuration of the systems that you employ for your Mobile Synchronization Gateway installation depends on the scale and the kind of deployment you have planned.
Note:
The sizing estimates in this section assume proper application configuration and tuning, in a manner consistent with leading practices of Oracle Communications consulting and performance engineering. This information is provided for informational purposes only and is not intended to be, nor shall it be construed as a commitment to deliver Oracle programs or services. This document shall not form the basis for any type of binding representation by Oracle and shall not be construed as containing express or implied warranties of any kind. You understand that information contained in this document will not be a part of any agreement for Oracle programs and services. Business parameters and operating environments vary substantially from customer to customer and as such not all factors, which may impact sizing, have been accounted for in this documentation.Table 3-4 provides the minimum hardware requirements for Mobile Synchronization Gateway installed on a single managed server in a GlassFish Server domain.
During Mobile Synchronization Gateway installation, you must enter values for configuration items such as host names and port numbers. This section describes the information that you must provide during the installation and initial configuration process.
Table 3-5 lists the Mobile Synchronization Gateway information that you provide during initial configuration.
Table 3-5 Mobile Synchronization Gateway Information
| Information Type | Default Value | Comments |
|---|---|---|
|
Directory to store configuration and data files. |
/var/opt/sun/comms/mobile |
No comments. |
|
Runtime user ID under which Mobile Synchronization Gateway runs |
root |
This user must match the user that runs the Glassfish Server instance. It is also the owner of the application data and configuration directory. |
|
Runtime group to contain Mobile Synchronization Gateway runtime user ID |
bin |
This group must match the group of the user that runs the Glassfish Server instance. It is also the owner of the application data and configuration directory. |
|
Fully qualified host name of this system |
FQDN of the host |
No comments. |
Table 3-6 lists the GlassFish Server information that you provide during initial configuration.
Table 3-6 GlassFish Server Information
| Information Type | Default Value |
|---|---|
|
GlassFish Server installation directory |
/opt/glassfish3/glassfish |
|
GlassFish Server domain directory |
/opt/glassfish3/glassfish/domains/domain1 |
|
GlassFish Server document root directory |
/opt/glassfish3/glassfish/domains/domain1/docroot |
|
GlassFish Server target instance name |
server |
|
GlassFish Server virtual server |
server |
|
GlassFish Server access host |
FQDN of the host |
|
GlassFish Server access port |
80 |
|
GlassFish Server administration server host |
FQDN of the host |
|
GlassFish Server administration server port |
4848 |
|
Is administration server port secure |
true (yes) |
|
GlassFish Server administrative user |
admin |
|
GlassFish Server administrative user password |
No default value. |
|
URI path of the deployed server |
/ |
Table 3-7 lists the LDAP information that you provide during initial configuration.
| Information Type | Default Value |
|---|---|
|
User/Group LDAP URL |
ldaps://FQDN_of_ host:636 Specify to use LDAP over SSL (ldaps://) if you want Mobile Synchronization Gateway to communicate by using SSL with Directory Server in the runtime configuration. You must also put the certificate database containing the Directory Server certificate in the MobileSyncGateway_home/lib directory. This setup works only for Solaris. See the openldap documentation for the required SSL setup on Linux. If you use LDAP in the URL specification, you do not need to perform any SSL setup for the initial configuration. However, you can enable LDAP SSL communication in the runtime configuration as described in Mobile Synchronization Gateway Security Guide. |
|
User/Group directory manager distinguished name (DN) |
cn=Directory Manager |
|
Directory manager password |
No default value. |
|
User/Group default domain |
The name of the domain in the directory user/group tree where user and group objects reside. |
|
Default organization distinguished name (DN) |
This value is generated based on the previous value and the user/group suffix of the Directory Server. |
Table 3-8 lists the Messaging Server information that you provide during initial configuration.
Table 3-8 Messaging Server Information
| Information Type | Default Value |
|---|---|
|
Default IMAP server host |
FQDN of the host |
|
IMAP server port number |
993 |
|
Is IMAP server port secure |
true |
|
IMAP server administrative user |
admin |
|
IMAP server administrative password |
No default value. |
|
SMTP server host |
FQDN of the host |
|
SMTP server port |
465 |
|
Is SMTP server port secure |
true |
|
SMTP server administrative user |
admin |
|
SMTP server administrative password |
No default value. |
Table 3-9 lists the Convergence (WABP) address book information you provide during initial configuration.
Table 3-10 lists the Contacts Server (CardDAV) and Convergence (WABP) address book information you provide during initial configuration.
Table 3-10 Contacts Server Information
| Information Type | Default Value |
|---|---|
|
Do you want to configure CardDAV? |
yes |
|
Contacts Server host name |
FQDN of the host |
|
Contacts Server port number |
443 |
|
Contacts Server Message Queue broker port |
7676 |
|
Is Contacts Server port secure |
true |
|
Contacts Server administrative user |
nabmaster |
|
Contacts Server administrative user password |
No default value. |
|
Do you want to configure WABP? |
yes |
Table 3-11 lists the Calendar Server information that you provide during initial configuration.
Table 3-11 Calendar Server Information
| Information Type | Default Value |
|---|---|
|
Do you want to configure CalDAV? |
yes |
|
Calendar Server host |
FQDN of the host |
|
Calendar Server port number |
443 |
|
Calendar Server Message Queue broker port |
7676 |
|
Is Calendar Server port secure |
true |
|
Calendar Server administrative user |
calmaster |
|
Calendar Server administrative user password |
No default value. |