For background information about GroupWise trusted applications, see Trusted Applications
in System
in the GroupWise 8 Administration Guide. When you set up a trusted application, you must register GroupWise Mobile Server as a GroupWise trusted application. When GroupWise Mobile Server has been registered, a trusted application key is assigned to GroupWise Mobile Server for accessing GroupWise.
From your Windows server, map a drive to the primary domain directory in your GroupWise system.
On the GroupWise Mobile Server machine, open a command window.
Change to the following directory:
C:\Program Files\Intellisync Mobile Suite\PIM
Enter the following command to register GroupWise Mobile Server as a GroupWise trusted application and generate the trusted application key:
GWTrustedApp.exe “path_to_primary_domain”
A message displays, stating that trusted application was successfully registered. It also displays your trusted application key.
Copy the key to the Windows clipboard.
In the Admin Console, click to connect the console to GroupWise Mobile Server.
Expand
> > .Right-click
, then click .Select
, then paste the trusted application key into the field.Click
, then specify a valid GroupWise username and password of a user on the POA.Click
.By default, the key allows GroupWise Mobile Server to authenticate to your GroupWise system from any network address. For higher security, you can configure the trusted application so that it must be running at a specified network address in order to authenticate. This higher level of security is obtained by configuring the trusted application in ConsoleOne®.
In ConsoleOne, configure GroupWise Mobile Server as a GroupWise trusted application, as described in Trusted Applications
in System
in the GroupWise 8 Administration Guide.
To apply the settings, reboot the GroupWise Mobile Server machine.
By default, you can access the WebAdmin Console only from the Admin Console. If you want to be able to access the WebAdmin Console directly from your Web browser, you must create an administrative user for this purpose.
Access the WebAdmin Console from the Admin Console.
Click
to connect the console to GroupWise Mobile Server.Click the WebAdmin object, then click
.In the WebAdmin Console, click
.By default, the Admin Console uses the sysadmin user to connect to the WebAdmin console.
To create your own administrative account, click
.Specify the administrative username and password, change other settings as needed, then click
.The new administrative user is added to the list. You can now use this username and password to access the WebAdmin Console directly from your Web browser.
The default HTTP ports for the Secure Gateway are port 80 for non-secure connections and port 443 for secure SSL connections. You might not want to open port 80 or port 443 to your demilitarized zone (DMZ).Therefore, you might want to change the port for the Secure Gateway from the default port to another port.
On the Secure Gateway machine, use a text editor to edit the securegateway.properties file.
By default, the securegateway.properties file is located in the following directory:
C:\Program Files\Secure Gateway\CommSvr\conf
Locate the #HttpPort=80 line, remove the comment character (#), and replace 80 with the port you want the Secure Gateway to listen on.
or
If you are using an SSL connection, locate the #HttpSSLPort=443 line, remove the comment character (#), and replace 443 with the port you want the Secure Gateway to listen on.
Save the securegateway.properties file.
On the GroupWise Mobile Server machine, start the Admin Console.
Update the Secure Gateway port information:
Right-click the Intellisync Mobile Suite object, then click
.Click the
tab.If a Secure Gateway server is already listed, select it, then click
.Click
.Specify the IP address or DNS hostname and port number, then click
; for example:http://www.corporate.net:8888 https://www.corporate.net:4433
Click
to save the updated list of Secure Gateway servers.Update the Web server and sync server information:
Click the
tab.In the
field, add the new port number to the existing DNS hostname with a colon (:) between them.In the
field, add the new port number to the existing DNS hostname with a colon (:) between them.Click
to save the changes.Restart the GroupWise Mobile Server machine.
Restart the Secure Gateway machine.
Notify existing mobile device users to add the port number to the server that their devices use for synchronization.
For instructions, see the device-specific User Guides at the GroupWise Mobile Server 3 Documentation Web site.
By default, GroupWise Mobile Server uses Network Push by way of TCP/IP over port 3102 to push GroupWise PIM data from your mailbox to your mobile device. Instructions for configuring Network Push are provided in the Intellisync Mobile Server Administrator’s Guide.
As a backup to Network Push, you can enable SMS Push, which allows your mobile device to receive update notifications even when the permanent connection to GroupWise Mobile Server is not available. Before configuring the SMS Push feature, you must configure the GroupWise Internet Agent as a relay host, as described in Section 2.5, Configuring the Internet Agent for SMTP Relay to Support SMS Push.
IMPORTANT:Before you implement SMS Push, make sure that your phone carrier supports it. Also be aware that with SMS Push, update notifications arrive to your mobile device as SMS messages, which can be quite expensive on some phone plans, especially if you travel abroad.
To configure the SMS Push feature:
In the Admin Console, expand .
To enable/disable Push, and to configure synchronization settings:
Expand
.Right-click
, then click .Click
for information about the Push/ReadySync settings.Set the Push/ReadySync settings as needed for your mobile users.
Click
to save the Push/ReadySync settings.To configure the types of items that are pushed to mobile devices:
Expand
.Right-click
, then click .Click
for information about the Push settings.Set the Push settings as needed for your mobile users.
Click
to save the Push settings.