1. For best security, select a Linux server that is inside your DMZ as the location for your Synchronizer system.

2. Make sure that the Linux server where you plan to install the Mobility Pack meets the system requirements listed in Section 1.2, Data Synchronizer System Requirements.

3. Make sure that the Synchronizer server has a static IP address.

4. Make sure that the Linux operating system media is available.

   The Mobility Pack Installation program might need to install additional operating system RPMs that are required by the Mobility Pack. The Mobility Pack Installation program can access the operating system files on a DVD or in a repository that is available from an FTP site or a Web server.

5. Continue with Preparing the Network.

1. Make sure that any firewalls between the Synchronizer server and other applications have been configured to allow communication on the following ports:

   Port Number	On Server	Description
   636/389	LDAP	LDAP server secure or non-secure port
   7191	POA	GroupWise Post Office Agent (POA) SOAP port
   4500	Synchronizer	GroupWise Connector listening port for event notifications
   443/80	Synchronizer	Mobile device secure or non-secure port
   8120	Synchronizer	Synchronizer Web Admin port

   

   The GroupWise Connector initially communicates with the POA that you specify during Mobility Pack installation on the SOAP port that you specify. As users connect their mobile devices, the GroupWise Connector determines from the initial POA the IP addresses and port numbers of all POAs where mobile device users have their mailboxes. Therefore, the GroupWise Connector can communicate with multiple POAs throughout your GroupWise system.

2. Continue with Disabling an Existing Web Server.

For example, to stop the Apache Web server and its associated instance of Tomcat:

1. In a terminal window, become root by entering su - and the root password.

2. Enter the following commands to stop Apache and Tomcat:

   /etc/init.d/tomcat6 stop
   /etc/init.d/apache2 stop
   

3. Enter the following commands to make sure that Apache and Tomcat do not start again when you reboot the Synchronizer server:

   chkconfig --del apache2
   chkconfig --del tomcat6
   

4. Continue with Verifying GroupWise System Availability.

1. Make sure that the GroupWise trusted application key for the GroupWise Connector is accessible to the Mobility Pack Installation program on the Synchronizer server.

   For more information, see GroupWise Trusted Application.

2. Make sure that the GroupWise POA that the GroupWise Connector will communicate with is currently running.

3. Continue with Verifying Certificate Availability.

1. (Conditional) If you have a signed certificate from a certificate authority (CA) as required for configuring secure HTTP connections with mobile devices:

   1. Make sure that the certificate file is accessible to the Mobility Pack Installation program on the Synchronizer server.

   2. (Conditional) If the key file that you received with the certificate included a password, make sure that the password has been removed.

   3. (Conditional) If you received the certificate as multiple files, make sure that you have combined the files into one certificate file.

2. (Conditional) If you chose to use YaST to generate a self-signed certificate, make sure that it was created to include the specific DNS hostname of the Synchronizer server.

3. If possible, do not use a wildcard certificate.

   For best results, use a certificate that is created specifically for the Synchronizer server.

4. Continue with Installing and Setting Up a Data Synchronizer System.