Server Installation Guide version 2 - globoplc.com · Server Installation Guide version 2.6...

Server Installation Guide

version 2.6 March 2015

GO!Enterprise GLOBO Plc.

Copyright Notice and Usage Terms This guide is Copyright © 2012 GLOBO. All Rights Reserved. Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.

Disclaimer Information in this document is subject to change without notice and does not represent a commitment on the part of GLOBO.

Server Installation Guide version 2.6 Introduction i

Contents

Introduction 1

Installation Overview 3

Pre-installation requirements and considerations 5

Deployment Topologies and Network Connectivity Requirements.................. 5 General communication requirements ............................................... 5 Compact Mode .................................................................................... 7 Split Mode ........................................................................................... 8 Additional requirements ..................................................................... 9

System requirements ..................................................................................... 12

Installing the configuration utility 15

Running the configuration wizard 19

Selecting Installation Mode ............................................................................ 19 GO!Enterprise Server configuration ............................................................... 23

Step 1: About .................................................................................... 24 Step 2: Operating System .................................................................. 26 Step 3: Web Server............................................................................ 27 Step 4: System Database ................................................................... 28 Step 5: Settings ................................................................................. 37 Step 6: Encryption type ..................................................................... 44 Step 7: Software Update ................................................................... 45 Step 8: Final step ............................................................................... 48

Active – Active scenario ................................................................................. 49 GO!Enterprise Router configuration .............................................................. 50

Step 1: About .................................................................................... 51 Step 2: Prerequisites ......................................................................... 52 Step 3: Settings ................................................................................. 53 Step 4: Software Update ................................................................... 54 Step 5: Final Check ............................................................................ 57

Getting started with GO!Enterprise 59

Uninstalling GO!Enterprise Server 61

Back-up and restore GO!Enterprise Server 64

Appendices 69

Appendix A – Alternative installation topologies ........................................... 69

Server Installation Guide version 2.6 Introduction ii

Appendix B – Installation examples with stand-alone SIG .............................. 70

For More Information 72

Server Installation Guide version 2.6 Introduction 1

Introduction

About This Guide

The purpose of this guide is to help IT personnel to install GO!Enterprise Server.

About GO!Enterprise WorkSpace

GO!Enterprise WorkSpace provides a powerful, secure, easy to use and cost efficient solution to mobilize business operations and deploy mobile applications extensions. GO!Enterprise WorkSpace can act as the middleware between the mobile devices and the corporate back-end applications for satisfying the mobility requirements of a company or organization, covering needs that range from standard and ready-for-use office productivity applications (such as Email) to corporate-specific applications.

A variety of options is offered so that customers have the flexibility to choose the solution that better suits their needs:

GO!Enterprise Office for secure mobile email & PIM, enterprise instant messaging and secure mobile access to company files and intranet.

GO!Enterprise Mobilizer for secure mobilization of business applications and workflows.

GO!Enterprise Reach for rapid development, deployment and management of consumer mobile apps and services.

GO!Enterprise WorkSpace addresses the difficulties of developing, operating and administering mobile applications by managing the diversity of devices, networks, user groups and mobility needs not only at the time of deployment, but throughout the entire mobile application lifecycle.

The main components of the GO!Enterprise WorkSpace solution are:

GO!Enterprise Server, the middleware server, is the solution’s core component that handles all back-end enterprise systems integration, enforces policies, delivers mobile application extensions and provides powerful administration capabilities.

GO!Enterprise WorkSpace app, the mobile client application, is a secure container (running natively at the mobile devices) which provides a single point of interaction for accessing the applications managed by GO!Enterprise, allowing employees to user their own devices for accessing the corporate infrastructure securely and separately from their personal data.

GO!AppZone Studio leverages the solution with the capability to develop mobile applications and upload them to the GO!Enterprise Server.

Server Installation Guide version 2.6 Introduction 2

In addition, GO!Enterprise Secure Intranet Gateway (SIG) enables secure access to web-enabled or other applications within the company network (e.g. company intranet, accounting, customer management, corporate databases) over GO!Enterprise. The SIG is installed as a module embedded in the GO!Enterprise Server but it can also be installed as a stand-alone instance. For more information about the Secure Intranet Gateway (SIG), please refer to the Secure Intranet Gateway (SIG) Installation Guide.

Visit our site www.globoplc.com to learn more about GO!Enterprise WorkSpace and GLOBO’s enterprise mobility solutions.

Mobile devices compatibility

The mobile OS compatibility list of GO!Enterprise WorkSpace includes:

Mobile OS Compatibility

Handsets & tablets version 4.0 or later

iPhone & iPad version 7.0 or later

Version 10

Version 8 and 8.1

Version 8 and 8.1

Server Installation Guide version 2.6 Installation Overview 3

Installation Overview

Solution Components and Installation Modes

The GO!Enterprise solution is flexible enough to allow for different installation scenarios, depending on the requirements and corporate policies that apply per each case. The core component of the solution is the GO!Enterprise Server. For corporate environments where security policies do not allow public-facing servers to directly connect to servers in the corporate LAN, it is possible to perform what is called a “split-mode” installation. In this scenario, the GO!Enterprise Server resides in the corporate LAN and is accessible via another component, the GO!Enterprise Router) which is installed in the corporate DMZ.

In principal, GO!Enterprise Server installation options are based on two determinative parameters:

Whether it is permissible to install GO!Enterprise Server within the Public Corporate Network/DMZ of the enterprise as a Secure Public Server.

o If yes, Compact Mode can be implemented, otherwise Split Mode is more appropriate.

Whether there any corporate resources that will not reside at the same network as the GO!Enterprise Server.

o If yes, then it constitutes reason to use stand-alone instance(s) of SIG. For more information about the Secure Intranet Gateway (SIG), please refer to the Secure Intranet Gateway (SIG) Installation Guide. Examples of installations with stand-alone SIG are presented Appendix B – Installation examples with stand-alone SIG.

Besides the main installation options that cover the most frequent cases, there are other alternative topologies that may also be deployed – see: Appendix A – Alternative installation topologies.

Installation Workflow

Depending on the installation scenario that applies to your case, you need to install the relevant GO!Enterprise components.

You may consult the following diagram to determine which components must be installed for your installation case and in which order.

Server Installation Guide version 2.6 Installation Overview 4

Procedure Outline

To install the above solution components, you need to:

1 Download the GO!Enterprise Server installer.

2 Install the configuration utility (wizard) of GO!Enterprise Server.

3 Run the configuration wizard and follow the relevant installation instructions.

Note: You need to log in as a user with Administrator Privileges on the Windows Server where the solution’s components will be installed.

Tip: If you have already installed and run the configuration utility and you want to modify a component’s configuration, you can run again the relevant configuration utility. The utility will display the current configuration of the component and will guide you about which settings are allowed to be modified.

Before proceeding with the GO!Enterprise installation procedure, it is highly recommended to check carefully the prerequisites that apply to your installation scenario and make sure that the relevant specifications are fulfilled.

Server Installation Guide version 2.6 Pre-installation requirements and considerations 5

Pre-installation requirements and

considerations

Deployment Topologies and Network Connectivity

Requirements GO!Enterprise Server can be installed in one of the following topologies:

Compact mode: The GO!Enterprise Server is installed in a public/DMZ internet enabled zone.

Split mode: The GO!Enterprise Server is installed behind the DMZ (keeping it protected from free public access) while, additionally, the GO!Enterprise Router is installed in the DMZ.

There are communication requirements that:

Generally apply to all installation scenarios.

Are specific to each deployment topology.

You should also review Additional requirements to check if there are additional requirements that must be fulfilled for your specific case.

Proxy Servers

If proxy servers will be used, you need to configure the relevant proxy settings.

See:

Defining proxy settings for GO!Enterprise Server.

Defining proxy settings for GO!Enterprise Router.

General communication requirements

The following communication requirements generally apply to all installation scenarios.

From GO!Enterprise Server, either directly or via proxy (both during and after the installation):

To (outbound) Ports Description

license.goenterpriseserver.com (Address: 5.11.56.101) 80 and 443

necessary to authenticate GO!Enterprise licenses with Globo


get.goenterpriseserver.com (Address: 5.11.56.100) 80 and 443

necessary to receive GO!Enterprise Server updates and redirect mobile browsers requests to download the appropriate GO!Enterprise WorkSpace

apps.goenterpriseserver.com (Address: 5.11.56.102) 80 and 443

necessary to receive GO!Enterprise Office ready-made apps

goesdns.goenterpriseserver.com (Address: 5.11.56.38) 80 and 443

optional to authenticate Globo’s dns-type subdomains if used to demo GO!Enterprise

monitoring.goenterpriseserver.com (Address: 5.11.56.105)

80 and 443

optional to send status & statistics to Globo from a GO!Enterprise installation

crm.goenterpriseserver.com (Address: 5.11.56.104) 80 and 443

optional to authenticate Globo’s product from CRM

android.googleapis.com/gcm/send 80 and 443

Android Push Notifications

api.parse.com/1/push 80 and 443

optional for Android Push Notifications

This is an alternative, in case it is not possible to use: android.googleapis.com/gcm/send

cp262.pushapi.na.blackberry.com/mss/PD_pushRequest

80 and 443

Blackberry Push Notifications

sn1.notify.live.net 80 and 443

Windows Phone Push Notifications

Note: GO!Enterprise will work only for a limited time, if the required destinations are not accessible from the server where the GO!Enterprise Server is installed.


For communicating with external SQL server:

If you opt to use an SQL server which is not installed at the same machine as the GO!Enterprise Server, then:

GO!Enterprise Server must be able to communicate with the external Microsoft SQL server via the port that the SQL Server is configured to listen to (default is port 1433).

Compact Mode

Compact Mode is a typical GO!Enterprise scenario, where GO!Enterprise Server is installed within the Public Corporate Network/DMZ of the enterprise as a Secure Public Server.

Suitable for:

Simple and quick installations.

Installations where GO!Enterprise Server does not require many ports for its communication with back-end systems (e.g. when using only custom GO!Apps).

Installations which require integration with Active Directory and GO!Enterprise Server resides on the same network.

Example of a compact mode installation of GO!Enterprise Server with embedded SIG.

GO!Enterprise Server communication requirements

Incoming The GO!Enterprise Server should be able to listen from any IP address to ports 80 (HTTP) or 443 (HTTPS), depending on the use of SSL.

If communication with one or more stand-alone SIGs is required, the GO!Enterprise Server should be able to listen from the IP of the SIG(s) to port 22*. An illustration of a compact mode installation with a stand-alone SIG is given in Appendix B – Installation examples with stand-alone SIG.


In case Secure Browsing functionality is required, the GO!Enterprise Server should be able to listen from any IP address to port 22*.

Outgoing The GO!Enterprise Server should be able to reach those backend systems which need to be linked with the GO!Enterprise solution, from the relevant ports. It is highly recommended that the GO!Enterprise Server can access only those corporate resources which are necessary for the GO!Enterprise solution.

*Port 22 is the default but it is possible to use a different port.

Split Mode

In the scenario of Split Mode, GO!Enterprise Server is installed within the corporate network and is accessible via the GO!Enterprise Router, an additional component which is positioned within the Public Corporate Network/DMZ. This mode is preferred for corporate environments where security policies do not allow public-facing servers to directly connect to servers in the corporate LAN.

The GO!Enterprise Router is a secure gateway which acts as a reverse proxy and web application firewall for GO!Enterprise Server. GO!Enterprise Router is a set of Windows processes and hence it is immune to IIS-based attacks.

Suitable for:

Very secure installations with simple configuration.

Installations which require integration with Active Directory and GO!Enterprise Server resides on a different network.

Installations which require access to files on servers or workstations within the corporate network.

Example of a split mode installation of GO!Enterprise Server with embedded SIG.

GO!Enterprise Router communication requirements


Incoming The GO!Enterprise Router should be able to listen from any IP address to ports 80 (HTTP) or 443 (HTTPS), depending on the use of SSL.

If communication with one or more stand-alone SIGs is required, the GO!Enterprise Router should be able to listen from the IP of the SIG(s) to port 22*. An illustration of a compact mode installation with a stand-alone SIG is given in Appendix B – Installation examples with stand-alone SIG.

In case Secure Browsing functionality is required, the GO!Enterprise Router should be able to listen from any IP address to port 22*. There is no need to arrange forwarding of secure browsing traffic, since this is managed by GO!Enterprise Router.

Outgoing The GO!Enterprise Router should be able to reach the GO!Enterprise Server from ports 80 (HTTP) or 443 (HTTPS), depending on the use of SSL, and from port 22* if secure browsing has been enabled.

If SSL is used for communication with GO!Enterprise WorkSpace (i.e. the mobile clients), it is strongly suggested to terminate the SSL connection before GO!Enterprise Router using any appliance that can provide SSL acceleration services. In this way, the GO!Enterprise Router can filter inbound traffic and reject non-GO!Enterprise compatible connection requests.

GO!Enterprise Server communication requirements

Incoming The GO!Enterprise Server should be able to listen from the GO!Enterprise Router to ports 80 (HTTP) or 443 (HTTPS), depending on the use of SSL.

In case Secure Browsing functionality is required, the GO!Enterprise Server should be able to listen from the GO!Enterprise Router to port 22*.

Outgoing The GO!Enterprise Server should be able to reach those backend systems which need to be linked with the GO!Enterprise solution, from the relevant ports. It is highly recommended that the GO!Enterprise Server can access only those corporate resources which are necessary for the GO!Enterprise solution.

*Port 22 is the default but it is possible to use a different port.

Additional requirements

This section includes additional requirements that must be fulfilled depending on the specifics of your deployment.

Supporting the GO!Enterprise Office solution

When implementing GO!Enterprise in the context of a GO!Enterprise Office solution for Microsoft Exchange, the following are required:


Microsoft Exchange Server 2007 Service Pack 1 or later, with Exchange Web Services (EWS) enabled (to support the GO!Email & PIM app).

Access to the Windows Domain Controller (or LDAP) (to support the Contacts and GO!Files apps).

Note: After the initial installation of GO!Enterprise Server, you should log in the Administration Environment and revise the settings for synchronizing with the Exchange Server as per the guidelines given below.

Synchronizing with the Exchange Server

After logging in the Administration Environment of GO!Enterprise (see: Getting started with GO!Enterprise), navigate to Options>Applications. Expand the GO!Mail&PIM application and select Edit next to the version you want to configure. Navigate to GO!Mail&PIM application parameters>Syncronization Settings. At Push notifications server URL, you can specify the address (as “seen” by the Mail server) of the server used for pushing notifications.

The Push notifications server URL parameter of GO!Email&PIM app is very critical to correctly support GO!Enterprise Office with Exchange.

Upon the initial installation, this parameter is blank by default and, thus, GO!Enterprise uses polling to synchronize Exchange items (emails, calendar events, tasks etc.). Although synchronization is achieved, this approach is resources hungry and it typically results in slow delivery of emails and other items to the mobile devices.

To optimize the Exchange items (emails, calendar events, tasks etc.) synchronization, the use of Exchange push notifications is recommended. So, you should set in this parameter the GO!Enterprise IP or Server name that the Exchange use either through HTTP or HTTPS to send the Exchange push notifications. Therefore, based on the network topology between GO!Enterprise and Exchange, it is recommended to set this parameter according to the following table.

Network topology between GO!Enterprise and Exchange

SSL certificate on GO!Enterprise

GO!Enterprise Port

GO!Email&PIM parameter (The server to receive Exchange push notifications)

Internal connection

No Port 80 (HTTP) Set GO!Enterprise internal IP or internal Server name in the form of http://xxx.xxx.x.xxx

External (public) connection

Yes Port 80 (HTTP) Set GO!Enterprise public domain name in the form of http://mygoenterprise.com

Port 443 (HTTPS)

Set GO!Enterprise public domain name in the form of https://mygoenterprise.com

No Port 80 (HTTP) Set GO!Enterprise public domain name in the form of http://mygoenterprise.com


Connecting with the Domain server

The following are required for LDAP connectivity:

Protocol and Port

AD and AD DS Usage Type of traffic

TCP and UDP 389

Directory, Replication, User and Computer Authentication, Group Policy, Trusts

LDAP

TCP 636 Directory, Replication, User and Computer Authentication, Group Policy, Trusts

LDAP SSL


LDAP GC


LDAP GC SSL

TCP and UDP 53

User and Computer Authentication, Name Resolution, Trusts DNS

Connecting with the File server

The following are required for connecting with the file server in order to utilize the “Files & Folders” functionality:

Protocol and Port Service Type of traffic

TCP 139 Session service for connection-oriented communication NetBIOS

TCP 445 Server Message Block SMB

UDP 137 Name service for name registration and resolution NetBIOS

UDP 138 Datagram distribution service for connectionless communication

NetBIOS

Supporting the GO!Enterprise Mobilizer solution

When implementing GO!Enterprise in the context of a GO!Enterprise Mobilizer solution, you must ensure:

Accessibility to the back-end applications/systems that are used from the GO!Apps (developed by the GO!AppZone Studio)


System requirements This section describes the system requirements for each component of the solution.

System requirements for GO!Enterprise Server

It is highly recommended to run GO!Enterprise Server on its own Windows Server.

The system on which GO!Enterprise Server will be installed should have the following specifications:

GO!Enterprise Server specifications

Minimum hardware requirements

Intel® Pentium® IV, at least 2 GHz

At least 4GB RAM

At least 250GB HDD

Operating system requirements

Microsoft Windows Server 2003, 2008 (including R2) or 2012 (including R2)

Software requirements

Microsoft .NET framework 3.5 SP1 and .NET Framework 4.0 (ASPNET, ASPNET 4.0)

IIS7, with ASP.NET enabled (although compatibility is achieved with IIS6 or later, to avoid IIS6 registry issue, IIS7 is highly recommended)

Note: The GO!Enterprise Server Web Components will be installed in the IIS Default Web Site. Any custom IIS setting could cause installation issues, therefore it is highly recommended to keep the standard settings of the IIS Default Web Site.

Corporate SSL certificate (Highly recommended to enhance communication security between GO!Enterprise Server and GO!Enterprise WorkSpaces running on mobile devices)

Microsoft Internet Explorer version 6.0 or later, Adobe Reader and WinZip

Database requirements

Microsoft SQL Server 2005, 2008 or 2012 Standard, Enterprise or Express editions. Note: Express editions are not recommended to be used in production environments but they can be used for proof of concept trials.

SQL needs Mixed Mode authentication

SQLBROWSER, Named Pipes and TCP Sockets must be all enabled for remote SQL server access


Note: In production environments where it is expected to have considerable volume of performance metrics collected, it is not recommended to co-install the SQL server on the same system where GO!Enterprise Server is installed. Instead, it is better to use enterprise-grade SQL systems.

Login requirements & permissions

Log on locally with local permissions

Log on as a service

Local Administrator

Valid Domain user account

SQL requirements & permissions

During installation you have the choice to use an existing Microsoft SQL Server or create a new Microsoft SQL Server (Express edition) within the same Server that the GO!Enterprise is going to be installed.

If you choose to use an existing Microsoft SQL Server:

To create a new database, you need to have an SQL Login (for performing administrative actions to the existing SQL server instance) with SQL Server role: Server Administrators, Database Creators

To connect to an existing GO!Enterprise Server system database during install:

o For performing administrative actions to the existing SQL server instance, you need to have an SQL Login with SQL Server role: Server Administrators.

o For the database user that will be used by GO!Enterprise Server Web and Windows services for querying the system database, you need to have a Database User and another SQL Login which both have the same name. The SQL Login needs to have the existing system database as Default and the Database User needs to have Database role: db_owner

In addition:

The Windows Server should have a Public Static IP and public internet access on 80 Port, along with access on 443 Port if SSL certification is installed. Its Public Static IP should be tied with the established domain name. Optional, the relevant port for secure communications (default port is 22) should be free if Secure Browsing functionality is required. See also: Deployment Topologies and Network Connectivity Requirements.

GO!Enterprise Server requires internet access and depending on the installation, it should have access (internet or LAN) to those back-end systems (e.g. Microsoft Exchange, IBM Lotus Domino, Microsoft Dynamics etc.) which is going to communicate. See also: Deployment Topologies and Network Connectivity Requirements.

You should also review Additional requirements to check if there are additional requirements that must be fulfilled for your specific case.


System requirements for GO!Enterprise Router

The system on which GO!Enterprise Router will be installed should have the following specifications:

GO!Enterprise Router specifications

Minimum requirements

Intel® Pentium® IV, at least 2 GHz

At least 2GB RAM

At least 300MB HDD

Microsoft Windows Server 2003, 2008 (including R2) or 2012 (including R2)

IIS or other web server SHOULD NOT EXIST or at least port 80, 443 SHOULD BE free. In case Secure Browsing functionality is required, the port defined for secure communications (default port is 22) should also be free.

Microsoft .NET framework 3.5

SSL certificate is required, but it is going to be installed on GO!Enterprise Server, issued for the same domain name that points to GO!Enterprise Router

Note: GO!Enterprise Server should be installed before GO!Enterprise Router.

Server Installation Guide version 2.6 Installing the configuration utility 15

Installing the configuration utility

Step 1: Initiate the setup procedure

Initiating the executable installer file displays a wizard which will guide you through the required actions.

Throughout the procedure, clicking:

Next advances you to the next step,

Back takes you to the previous step

Cancel aborts the procedure.

Step 2: Accept License Agreement

This screen details the License Agreement and it is advised that you carefully read the relevant EULA terms & conditions to check that you agree with them.

You must accept the License Agreement, otherwise you cannot proceed to the next step of the installation procedure.


Step 3: Select installation folder

The default location where the GO!Enterprise Server will be installed is displayed, but you can specify an alternative location.


Step 4: Set off the installation

Select Install to proceed with the installation.


Step 5: Conclude the installation procedure

Wait while the GO!Enterprise Server is being installed and when the installation is completed, the following screen is displayed.

If you want the GO!Enterprise Server Configurator to start automatically right after clicking Finish, leave the Launch GO!Enterprise Server Configuration checkbox selected. Otherwise, clear the checkbox. In any case, you can manually launch the configurator from the applications menu (see: Running the configuration wizard).

Server Installation Guide version 2.6 Running the configuration wizard 19

Running the configuration wizard

If, during the installation procedure, you have selected to launch the configurator after the installation is completed, it will start automatically. Otherwise you can activate the GO!Enterprise Server Configurator from the applications menu. For example:

Selecting Installation Mode Once the configuration is initiated, you are requested to choose the installation mode (for information about the installation modes, see: Deployment Topologies and Network Connectivity Requirements).


Important notifications, if any, are displayed at the lower part of the window (e.g. for downloading a newer version of GO!Enterprise).

Select Compact Mode or Split Mode to initiate the corresponding configuration process.

Compact Mode

Selecting Compact Mode initiates the corresponding configuration process.


For the relevant configuration instructions, see: GO!Enterprise Server configuration.

Split Mode

Selecting Split Mode initiates the corresponding configuration process.


In Split mode, you have to execute separate installations on different systems:

GO!Enterprise Server installation where GO!Enterprise Server is installed within the corporate network. Selecting GO!Enterprise Server initiates the corresponding configuration process.


The configuration procedure comprises the same steps as in the case of Compact Mode.

For the relevant configuration instructions, see: GO!Enterprise Server configuration.

GO!Enterprise Router installation where the router is positioned within the DMZ.

For the relevant configuration instructions, see: GO!Enterprise Router configuration.

Note: GO!Enterprise Server should be installed before GO!Enterprise Router.

GO!Enterprise Server configuration The configuration process entails several steps which are described in the following sections. At the start and at the end of the configuration certain checks are executed for facilitating and safeguarding the configuration process.

Note that during the installation GO!Enterprise Server will need to communicate via the internet to the destinations mentioned in General communication requirements.

See also: Selecting Installation Mode.


Step 1: About

This is the welcome screen of the GO!Enterprise Configuration wizard where a brief description of the product is provided.

Select Start to continue or Cancel to abort the GO!Enterprise Configuration.





Notifications, if any, are displayed at the lower part of the window, e.g. for downloading a newer version of GO!Enterprise or if an error is detected.


Defining proxy settings for GO!Enterprise Server

At this step, you are also prompted with the following message: If you are using proxy server, please click here. By selecting click here, a window is displayed where you can specify proxy settings.

To retrieve the System Proxy Settings (i.e. the proxy settings that are displayed in Internet Explore at Internet Options > Connections > LAN settings), select Restore Default Proxy. The System Proxy Settings are retrieved and displayed at the relevant fields. If necessary, make any further modifications and then continue to the next step.


About Proxy Servers

In order to meet an organization’s network infrastructure security policies, there are three potentially different proxy servers that can independently be configured for each of the following:

The configuration utility (wizard) of GO!Enterprise Server. This is configured here (i.e. at Step 1: About) and is the proxy server which is used by the configuration utility of GO!Enterprise Server for accessing the necessary internet/intranet resources, in order to properly set up and update the relevant components of GO!Enterprise Server.

The GO!Enterprise Server. This is configured at Proxy Settings and is the proxy server which is used by GO!Enterprise Server for accessing the necessary internet/intranet resources, in order to run properly.

The secure browsing functionality. This is configured at More Settings and is the proxy server which is used by the Secure browsing functionality which is embedded in the GO!Enterprise Server for properly accessing the necessary internet/intranet resources.

Step 2: Operating System

At this step, a check is performed to verify the Operating System’s compatibility (see: System requirements for GO!Enterprise Server).


Step 3: Web Server

At this step, the compatibility of the Web Server is checked.

In case the GO!Enterprise Configuration detects incompatibility or absence of Web Server Software, it prompts for the appropriate corrective action. Click on the corresponding links to resolve the issues. Clicking the here link at the bottom of the page reruns the checks and updates their results.


Step 4: System Database

For the system’s database, you have the following options:

Install a new MS SQL Server Express (on the local server) to create the system database.

Create the system database on an existing SQL Server (on the local or a remote server).

Select an existing GO!Enterprise Server database to use as system database (on the local or a remote server).


During setting up the system database you will need to have the necessary credentials for the following two distinct cases:

For performing administrative actions to the SQL server instance that will host the system database, such as: Create database or Create database user

For the database user that will be used by GO!Enterprise Server Web and Windows services for querying the system database

There are two options for providing these credentials:

SQL Server Authentication: i.e. specifying a database user

Windows Authentication: i.e. specifying a windows user

SQL Server Authentication versus Windows Authentication

Especially regarding the case of specifying credentials for the database user, it is important that you are aware of the differences between the two options.


If you opt for:

SQL Server Authentication, the user you specify will be created as database owner and will be used by the GO!Enterprise Server Web and Windows services for querying the system database

Windows Authentication, the NetworkService Account will be used by the GO!Enterprise Server Web and Windows services for querying the system database.

Attention: By default, the NetworkService Account is not permitted to connect to the SQL Server.

When Windows Authentication is used by GO!Enterprise Server for accessing the system database then ensure the following:

a) if the SQL server database is hosted locally, the local Network Service account (NT AUTHORITY\NETWORK SERVICE) will be used for accessing the system database. So, it is necessary to manually assign the local Network Service account as the owner of the GO!Enterprise Server database.

b) if the database is hosted on a remote SQL Server machine, this computer network user ({DOMAIN}\{COMPUTERNAME}$) must be manually assigned as the owner of the remote GO!Enterprise system database.

Install a new MS SQL Server Express to create the system database

To install a new instance of MS SQL Server 2005 Express and create the database on it:

1 Select Create Database on a new Microsoft SQL Server 2005 Express Instance.

2 You may specify an installation path different than the default.


3 Select Create database to initiate the installation of a new SQL Server 2005 Express instance at the local system.

This initiates the process for downloading and installing a new Microsoft SQL Server 2005 Express instance.


Note: The credentials of the existing windows user (who currently performs the installation of the GO!Enterprise Server to the local system) are used in order to create the new SQL Server instance, i.e. Windows Authentication is automatically (and silently) used for performing administrative actions to the SQL server instance.

4 Once the Microsoft SQL Server 2005 Express Instance is installed, you are requested to specify the credentials of the GO!Enterprise Server database user, either SQL Server Authentication or Windows Authentication.

Attention: Before making your choice, make sure that you read the section SQL Server Authentication versus Windows Authentication and that you understand the differences between the two options.

Once the database creation is completed, a notification is displayed.

Create the system database on an existing SQL Server

To create the database on an existing SQL Server:


1 Select Create Database on an existing Microsoft SQL Server.

2 At Server, specify an existing SQL Server or click on the button to select from a list.

Note: If you cannot see an expected SQL Server name, check and ensure that the SQL Server Browser service is running.

3 Provide the SQL Server Administrator credentials.

Note: These are the credentials that are necessary for performing administrative actions the SQL server and the system (local or remote) that hosts the SQL Server.

4 Select Create database to initiate the creation of the database on the selected SQL server.

This initiates the process for creating the system’s database on the selected existing SQL Server.


5 Once the database is created, you are requested to specify the credentials of the GO!Enterprise Server database user, either SQL Server Authentication or Windows Authentication.


Once the database creation is completed, a notification is displayed.

Select an existing GO!Enterprise Server database to use as system database

To select an existing GO!Enterprise Server database as the system’s database:


1 Choose Select an existing GO!Enterprise Server.

2 At Server, specify an existing SQL Server or click on the button to select from a list.

Note: If you cannot see an expected SQL Server name, check and ensure that the SQL Server Browser service is running.

3 Provide the SQL Server Administrator credentials.

Note: These are the credentials that are necessary for performing administrative actions the SQL server and the system (local or remote) that hosts the SQL Server.

4 Select Connect, expand the list and select one of the existing databases and then click Select Database.


5 Once the database is selected, you are requested to specify the credentials of the GO!Enterprise Server database user, either SQL Server Authentication or Windows Authentication.


See also:

The SQL permissions requirements listed at System requirements for GO!Enterprise Server.

When the setting up of the system database has been completed, you can proceed to the next step.


Step 5: Settings

At the top of the window, you may specify the Server directories, if other than the default ones. Specifically, the:

Installation path

Data storage path


The other settings are grouped as follows:

1 Server URL

2 Email Notification Settings

3 SMS Notification Settings

4 Accessible Networks

5 Default Admin User

6 Proxy Settings

7 Owner Info

8 More Settings

The descriptions of the settings for each one are given in the following sections.

Server URL

Specify the Web Domain Name of the server, without specifying the protocol (i.e. the http).For example, GOES.myCompany.com.


If there is currently no available Web Domain Name, which is something common in product evaluation or trial installation cases, select the Click here link to insert the requested info, together with a valid email. Then a verification code is sent which you must insert in the New Domain Creation form to gain a DNS-type of a web domain name.

The Change Web Domain name option is available only after you have previously performed the configuration procedure. It is used for modifying the Web Domain Name that has already been specified.


Email Notification Settings

Here you can specify the settings for the email system that will handle the user email notifications, e.g. for service activation and credentials distribution.

Note: In case the System Administrator does not want to use this method to inform users, you can skip the configuration of these settings.

The available options are:

MS Exchange (2007 SP1 or later). In this case, enter the Server (IP or domain) and the Email & Password of the system administrator.

SMTP. In this case, enter the Server (IP or Domain), the Email & Password of the system administrator and the Port number that will be used for the service.

IBM Lotus Domino. In this case, apart from Server (IP or Domain), Username and Password, you should enter the User Database Name as well.

SMS Notification Settings

Here you can specify the SMS system that will handle the user SMS notifications, e.g. for service activation and credentials distribution.

Note: In case the System Administrator does not want to use SMS notifications to inform users, you can skip the configuration of these settings.

The options are:

to use the Embedded SMS notification service

to setup Custom SMS notification service. In this case, you need to set up the URL which the post request will be sent.


Accessible Networks

Here you can see a list with all the accessible networks.

Default Admin User

Here you can set the username and password of the administrator, which will be used for logging in the GO!Enterprise Server administration console.

Note: If you are reconfiguring the GO!Enterprise Server installation and you want to modify the administrator’s password, the new password will not be put to effect unless it meets any defined policies regarding the password’s strength.


Proxy Settings

Here you can choose whether a proxy server will be used for GO!Enterprise server. If so, you need to specify the settings of the proxy connection. If you have specified proxy settings for the configurator utility of GO!Enterprise Server at Step 1: About, these settings are conveyed here but you can specify different ones.

See: Defining proxy settings for GO!Enterprise Server for more information about the proxy servers.

Owner Info

Here you need to enter information about the main contact person or the owner of the company where the GO!Enterprise system is installed.


More Settings

Here you can specify additional settings regarding secure communication as well as the mail server type.

The Mail Server Type is the type of mail server that will be used for GO!Enterprise applications, such as the GO!Mail. The available options are:

None (blank)

Microsoft Exchange

IBM Lotus Domino

Note: Especially in the case when IBM Lotus Domino will be used, it is mandatory to specify this setting during the installation procedure.

Disable embedded Secure Intranet Gateway: Normally, you can leave this option unchecked. If selected, it disables the Secure Intranet Gateway components that are embedded in the GO!Enterprise Server. This frees up the relevant system resources while it is no longer necessary to open the secure browsing port (typically, port 22). By disabling the embedded Secure Intranet Gateway:

The embedded Secure Intranet Gateway does not self-register to the GO!Enterprise Server.


You cannot use the embedded Secure Intranet Gateway for accessing resources (such as secure browsing, LDAP, etc.) through it. If you want to access such resources, you need to set up stand-alone SIG(s).

The following settings are mandatory in case Secure Browsing needs to be supported.

The Secure connection port is the port which GO!Enterprise Server uses for secure communications (i.e. the port to which GO!Enterprise Server listens for secure browsing requests).

Secure Browsing Settings

Secure Browsing Port is the port (of the system where GO!Enterpise server is installed) which is used for supporting Secure Browsing. It is required to specify a port that is not used by another application or process. Subsequently, the specified port should not be used by another application or process.

Proxy Server

If you will not use a proxy server for secure communications, leave the Use Proxy Server option unselected. Otherwise, select it and specify the relevant proxy settings, which can be the same or different than the ones specified at Proxy Settings.

See: Defining proxy settings for GO!Enterprise Server for more information about the proxy servers.

Step 6: Encryption type

Here you can specify the encryption settings. AES encryption is pre-selected as default.

The SSL option is available only if a verified certificate is already installed on IIS.


Step 7: Software Update

The system checks to determine if there are software updates. If so, the Install option becomes available. Select Install to update the installation with the latest software.


The relevant updates are downloaded and installed.


Selecting the Click here link, you can select individual components and force their updating.

Tip: Forcing components to be updated is particularly useful in case the Admin Console has crushed during an update.


Step 8: Final step

In the final step of the configurator, the following checks are executed:

If IIS runs and responds locally

If GO!Enterprise administration web site is running

If IIS is listening to the domain name, when called from the Internet. Note: If you are implementing a Split Mode installation, this check cannot be successful until you also complete the installation of the GO!Enterprise Router. In this case, after you complete the GO!Enterprise Router installation, you can run the GO!Enterprise Server configuration wizard again and repeat this check.


If you want to repeat all checks, select Recheck. Otherwise, select Finish to conclude the configuration.

Active – Active scenario If you are implementing an active – active scenario, then you should note the following:

At Step 4: System Database, you must setup each and every installation of GO!Enterprise Server to use the same database.

At Step 5: Settings, you must specify the same Data Storage Path to each and every installation of GO!Enterprise Server.

In addition, all servers must have the same system locale (location settings).


GO!Enterprise Router configuration Selecting GO!Enterprise Router initiates the corresponding configuration process.


See also: Selecting Installation Mode.

Step 1: About

This is the welcome screen of the GO!Enterprise Router configuration.





Important notifications, if any, are displayed at the lower part of the window (e.g. for downloading a newer version of GO!Enterprise).

Defining proxy settings for GO!Enterprise Router

At this step, you are also prompted with the following message: If you are using proxy server, please click here. By selecting click here, a window is displayed where you can specify proxy settings.

To retrieve the System Proxy Settings (i.e. the proxy settings that are displayed in Internet Explore at Internet Options > Connections > LAN settings), select Restore Default Proxy. The System Proxy


Settings are retrieved and displayed at the relevant fields. If necessary, make any further modifications and then continue to the next step.

This proxy server which is configured here is used by the configuration utility of GO!Enterprise Router for accessing the necessary internet/intranet resources, in order to properly set up and update the relevant components of GO!Enterprise Router.

Step 2: Prerequisites

At this step, a check is performed to verify the Operating System’s compatibility (see: System requirements for GO!Enterprise Router).


The availability of TCP ports 80 and 443 is verified; i.e. that they are not blocked by a firewall and that no other software is bound to any of them.

Step 3: Settings

Here, you need to provide the GO!Enterprise Server name or IP Address and select whether Secure Browsing functionality must be supported or not.

Note: Selecting the Secure Browsing option does not require to specify a port for secure connections. GO!Enterprise Router will automatically use the Secure Connection Port that has been set at the configuration of the GO!Enterprise Server (see: More Settings).


Step 4: Software Update

The system checks to determine if there are software updates. If so, the Install option becomes available. Select Install to update the installation with the latest software.


The relevant updates are downloaded and installed.


Selecting the Click here link, you can select individual components and force their updating.


Step 5: Final Check

In the final step of the configurator, the following checks are executed:

If the Routing Service is listening on the required ports (i.e. 80, 443)

If Secure Browsing has been activated

If the Routing Service is listening to the domain name, when called from the Internet


If you want to repeat all checks, select Recheck. Otherwise, select Finish to conclude the configuration.

Server Installation Guide version 2.6 Getting started with GO!Enterprise 59

Getting started with GO!Enterprise

An Administrator can access the GO!Enterprise Administration Environment through a web-browser by typing the GO!Enterprise Server domain name followed by /admin.

For example: http://goes.mycompany.com/Admin

When signing in for the first time after successfully installing GO!Enterprise Server, the credentials for logging in are the ones that were specified during the installation of GO!Enterprise Server at Default Admin User.

Navigate through the application’s user interface and perform the necessary tasks to configure the system in order to provide the relevant services to the users.

For information about using the GO!Enterprise Administration Environment, refer to the “GO!Enterprise Server Administration Guide”.

http://goes.mycompany.com/Admin

Server Installation Guide version 2.6 Getting started with GO!Enterprise 60

GO!Enterprise Server health check monitoring

You can verify that the service is up and running by making an http or https request to the following URL: http://GOES_Server_Name/Admin/f_HealthCheck.aspx

If the service is up, the response will be: HTTP 200 OK

Provision of GO!Enterprise WorkSpace

GO!Enterprise WorkSpace, the mobile client application, is available for free on the relevant online app stores/marketplaces. For example, Apple App Store for iPhone & iPad, Google Play for Android devices and Windows Phone Marketplace for Windows Phone handsets.

Alternatively, typing the GO!Enterprise Server domain name followed by /get at the web-browser of your mobile device will direct you to download the GO!Enterprise WorkSpace app for the type of your mobile device.

For example: http://goes.mycompany.com/Get

Thus, after having assigned the appropriate licenses to users, the Administrator can send SMS or Email invitations to them through the GO!Enterprise Administration Environment, where the invitations will include this link for prompting the users to download and install the GO!Enterprise WorkSpace.

http://goes_server_name/Admin/f_HealthCheck.aspx

http://goes.mycompany.com/Get

Server Installation Guide version 2.6 Uninstalling GO!Enterprise Server 61

Uninstalling GO!Enterprise Server

Ensure that you have a logged in as a user with Administrator Privileges on the Windows Server where the GO!Enterprise component is installed.

To uninstall the component, go to the Windows applications menu (e.g. Start > All Programs > GO!Enterprise Configurator) and select Uninstall GO!Enterprise Server Configurator.

For example:

You can partially remove the software by selecting Custom, or completely remove all components including the GO!ES SQL database (GOES_Admin.mdf), by selecting Complete.


Custom Uninstall

Selecting Custom displays a window, in which you can specify the components that you want to uninstall.

Click Next. At the window that is displayed, review the components that will be removed and click Uninstall to remove them.


Complete Uninstall

To uninstall all components, select Complete. At the window that is displayed, review the components that will be removed and click Uninstall to remove them.

Server Installation Guide version 2.6 Back-up and restore GO!Enterprise Server 64

Back-up and restore GO!Enterprise

Server

This section describes the procedure for moving an existing GO!Enterprise Server installation to a new server.

The procedure covers the necessary actions that must be performed on the GO!Enterprise Server and its components and which typically apply in all cases. However, depending on the specifics of each deployment, further actions at your infrastructure may be required.

In case (planned or unforeseen) you need to move an existing GO!Enterprise Server installation to a new server, you must manually:

Back-up the existing GO!Enterprise Server installation.

Restore the GO!Enterprise Server to a new system.

During this procedure, there will be downtime of the services provided by the GO!Enterprise Server.

Unregistering stand-alone Secure Intranet Gateways

If this is a planned operation, you should first unregister any stand-alone Secure Intranet Gateway instances from GO!Enterprise Server before backing up the server.

This action is performed though the Administration Console of the GO!Enterprise Server that will be backed up (see: GO!Enterprise Server Administration Guide for information about how to perform this action).

Backing up GO!Enterprise Server

The following actions need to be performed from the Operating System’s and the Database’s environments:

1 Stop GOES site in IIS.

2 Stop the CitronGO.services.manager service on server.

3 After stopping the CitronGO.services.manager service, stop all other CitronGO and Globo services on server, namely:

CitronGO.Admin.SLL,

CitronGO.Push.Engine,

Globo.Admin,

Globo.SecureBrowsingService,

Globo.SharedFolders,


Globo.SSH.Server,

Globo.SSH.Registry,

Globo.SSH.Runtime.

4 Back up GOES_Admin database on the SQL Server used by GO!Enterprise Server.

Restoring GO!Enterprise Server

The following actions need to be performed from the Operating System’s and the Database’s environments:

1 Restore the GOES_Admin database on the SQL Server.

2 In the imported database, it is necessary to create the database user that will be used by GO!Enterprise Server Web and Windows services for querying the system database.

You need to create: a) an SQL Login. and b) a Database User. They must both have the same name (note that by creating a new SQL Login, a Database User with the same name is automatically created).

The SQL Login needs to have the restored database as Default and the Database User needs to have Database role: db_owner.

In the following example:

a) an SQL Login named GO!ESuser is created. The database GOES_Admin is set as Default database.


b) A Database User named GO!ESuser (the same name as the new SQL Login) has been automatically created and mapped to the GOES_Admin database. The Database role db_owner has been assigned to Database User GO!ESuser for the GOES_Admin database.


3 Install GO!Enterprise Server and when the Configuration reaches the System Database step (see: Step 4: System Database):

Choose Select an existing database.

Select the SQL Server where you restored the GOES_Admin database.

Provide the credentials for connecting to the SQL Server.

Click Connect and then select GOES_Admin from the drop-down list.

Then click Select database and provide the credentials for the database user that you have created in the previous step.

4 Choose Next and progress through the subsequent screens, keeping the existing settings, until you reach the software update screen.

5 Apply all the updates by selecting Install.

If the Install action is not enabled (e.g. in case of the software of this GO!Enterprise Server installation has already been updated recently), select the Click here link to display the installed components and select them all to force their updating. Wait until all the updates are completed and then press Next.

6 At the final screen ensure all the checks completed successfully and press finish.


If your deployment included stand-alone Secure Intranet Gateway instances, you must run the configuration utility of each Secure Intranet Gateway and at the Registration Step (see screenshot below) you need to register them to the restored GO!Enterprise Server (see also: Secure Intranet Gateway (SIG) Installation Guide, for more information about the configuration of stand-alone Secure Intranet Gateway instances).

It is recommended that you connect to the GO!Enterprise Server from a mobile device via GO!Enterprise Workspace and ensure that all functionality is preserved.

Server Installation Guide version 2.6 Appendices 69

Appendices

Appendix A – Alternative installation topologies

GO!Enterprise may also deployed in alternative topologies to address more specific needs.

Compact Mode with Reverse Proxy

In this scenario, GO!Enterprise Server is installed within the corporate network and is accessible via a reverse proxy server residing in the company’s DMZ.

Suitable for:

Secure, high-performance installations.

Installations which require integration with Active Directory.

Installations which require access to files on servers or workstations within the corporate network.

This scenario has the following communications requirements:

External firewall: Should allow inbound connections to port 80 or 443, depending on the use of SSL, for typical GO!Enterprise traffic. If secure browsing has been enabled, the relevant port for secure communications (default port is 22) inbound should also be open and all relevant traffic should be forwarded to GO!Enterprise within the corporate network.

Internal firewall: Should allow inbound connections to port 80 or 443 (and the relevant port for secure communications – default port is 22 – if secure browsing has been enabled). If SSL is used for communication with GO!Mobile Clients, it is suggested to terminate the SSL


connection before or at the reverse proxy server to offload GO!Enterprise Server from SSL connection management.

Compact Mode with VPN Server

In this scenario, GO!Enterprise Server is installed within the corporate network and is accessible via a VPN server residing in the company’s DMZ.

Suitable for:

Highly secure, purely B2E (business to employee) installations.

Environments which have a robust VPN infrastructure already in place.

Need to consider:

Possible delays in performance.

Use of GO!Enterprise secure browsing becomes redundant.

Complex deployment on mobile devices due to the need for VPN configuration.

VPN Server should connect only to GO!Enterprise Server (otherwise any “rogue” mobile app can potentially access the corporate network).

This scenario has the following communications requirements:

External firewall: Should allow inbound connections to the VPN server.

Internal firewall: Should allow inbound connections to port 80 or 443. The use of SSL is discouraged, since it will have a negative performance impact on the already encrypted connections.

Appendix B – Installation examples with stand-alone SIG The following figures present typical topologies where a stand-alone instance of the Secure Intranet Gateway (SIG) is deployed.

Example of an installation of GO!Enterprise Server in compact mode with a stand-alone SIG in compact mode.


Example of an installation of GO!Enterprise Server in split mode with stand-alone SIG in split mode.

For more information about the Secure Intranet Gateway (SIG), please refer to the Secure Intranet Gateway (SIG) Installation Guide.

Server Installation Guide version 2.6 For More Information 72

For More Information

Visit our site www.globoplc.com to learn more about GO!Enterprise and GLOBO’s Enterprise Mobility solutions.

About GLOBO plc

As a leading provider of mobile services to the enterprise GLOBO is pioneering a new era in mobilizing business. Its revolutionary products enable businesses to become more competitive by giving staff secure access to critical applications whilst on the go using their mobile phone or a tablet PC. Founded in 1997, the company is listed on the London Stock Exchange (GBO.LN). GLOBO is widely regarded as one of the most innovative companies due to its ongoing investment in research and development.

Contact Information

New York

247, West 35th Street

11th Floor Front, New York 10001

Tel.: +1 646 307 1614

London

41, Lothbury

EC2R 7HG, U.K.

Tel.: +44 (0) 207 378 8828

Athens

67, E. Antistaseos Street

152 31 Halandri, Greece

Tel.: +30 21 21 21 7000

Email

[email protected]

Website

www.globoplc.com

All brands, products, service names and logos used herein are trademarks and/or registered trademarks of their respective manufacturers and companies.

Server Installation Guide version 2 - globoplc.com · Server Installation Guide version 2.6...

Documents

Transcript of Server Installation Guide version 2 - globoplc.com · Server Installation Guide version 2.6...