CUSTOMER Upgrading SAP Afaria

Transcription

1 SAP Afaria Document Version: 7 SP CUSTOMER

2 Table of Contents 1 Upgrading Afaria to SP Supported Upgrade Paths Upgrade Considerations Preparing to Upgrade Afaria Upgrading an Afaria Component Afaria Single-Server Upgrade Afaria Server Farm Upgrade Afaria Self-Service Portal Upgrade SAP SE or an SAP affiliate company. All rights reserved. Table of Contents

3 1 Upgrading Afaria to SP5 To upgrade Afaria to SP5, download Afaria 7 SP5 software and run the Afaria Setup program for each Afaria Server and component in your installation. Do not upgrade the Afaria Server without upgrading all other components including all farm servers, the Enrollment Server, and the Package Server. To complete the upgrade, ensure all managed devices upgrade to the latest version of the Afaria client application. Before you continue, ensure that all servers and network devices hosting or interacting with Afaria meet the system requirements. See Preparing to Install Afaria. You should also ensure your installation is on the supported upgrade path. You may need to upgrade to an intermediate service pack before you can upgrade to SP Supported Upgrade Paths Upgrade to Afaria 7 SP5 is supported from Afaria 7 SP3 and Afaria 7 SP Upgrade Considerations SP5 includes a number of new features as well as changes to existing features that may affect your installation during or after an upgrade. Review the following feature changes to determine if any action is required. Android Scheduling Improvements in SP4 Android scheduling improvements allow you to set a schedule based on a rate, date range, repetition, and randomization. During upgrade from SP3 to SP5, the Afaria Setup program creates a default Android schedule based on your existing heartbeat settings. After upgrading to SP5, it is recommended that you review Android scheduling settings to determine if changes are required. Authentication Changes in SP4 When upgrading from SP3 to SP5, Afaria automatically enables authentication in the server configuration for each tenant. This authentication requires that users provide credentials when devices connect to Afaria. This might cause devices to prompt users for credentials in situations when devices did not prompt for credentials in SP3. You can configure the authentication settings on the Server Configuration Security page in the Afaria Administration console. Enrollment and package servers that required authentication in SP3, still require authentication after the upgrade. Upgrading Afaria to SP SAP SE or an SAP affiliate company. All rights reserved. 3

4 The upgrade should not affect authentication for the clients that connect to the Afaria Server because authentication is configured at the policy level in addition to on the server. For example, if an administrator does not want Android xcomms sessions authenticated and the administrator did not previously have any channels configured for authentication, then enabling the authentication setting will not change this. If an administrator configured a channel to require authentication and enabled authentication at the server, but later disabled the authentication on the server prior to upgrading from SP3, Afaria automatically enables authentication at the server configuration. As a result, Afaria starts authenticating after the upgrade. Discontinued Support for BlackBerry in SP5 BlackBerry support has been dropped in SP5. Before upgrading to SP5, it is recommended that you delete BlackBerry devices and configuration policies from Afaria. Database Schema Changes in SP5 Afaria introduces database changes in SP5 to improve performance, scalability, and usability. User intervention is not required to update the database; the Afaria Server Setup program handles the changes to the Afaria database. Depending on the size of your database, data conversion during an upgrade can take more than 30 minutes. During this time, the setup program displays a "Data Conversion in progress" message. Do not interrupt the upgrade process during data conversion. Doing so may result in a corrupted database and an inoperable system. If the server installer upgrade is interrupted, restore your database and restart the upgrade. If you must roll the entire system back to a previous version of Afaria after interrupting the server installation process, you will need to restore both your database as well as your Afaria server file system and registry. All database changes made to your Afaria database during the upgrade process are stored in the Afaria database table A_LOG_DB_UPGRADE. Refer to the contents of this table to view details regarding all database changes performed during upgrade. In addition, any orphaned data purged from the database tables during the upgrade process is stored in a corresponding backup table in the database with the B_ prefix in front of the affected table name SAP SE or an SAP affiliate company. All rights reserved. Upgrading Afaria to SP5

5 2 Preparing to Upgrade Afaria Before beginning an upgrade, validate all prerequisite and system requirements, create a system backup, and close all browsers that are currently logged in to the Afaria Administration console. If you are using a relay server, shut down the relay server (rsoe) before beginning an upgrade. Context A system backup includes the database, application software, and application data. Afaria only stores data in the database and on the Windows server hosting the Afaria Server. It is not necessary to back up data on servers hosting other Afaria components such as an Enrollment Server and Package Server. Note You may also want to delete devices, policies, and server settings for a platform for platforms and features no longer supported by Afaria. For example, support for BlackBerry was dropped in SP5. It is recommended that you delete BlackBerry devices and configuration policies prior to upgrading. Procedure 1. Back up your Afaria database. 2. Stop the Afaria Server services on each Windows server hosting an Afaria Server using the following commands: net stop Afaria Server /y net stop AfariaIPhoneServer /y net stop Afaria Backend Portal Package Server /y net stop Afaria API /y net stop Afaria Client Service /y 3. Stop any Relay Server Outbound Enabler services. The names of these services are customized by the installer and may vary by environment. 4. Record the installed Afaria hot fixes and services packs listed in the registry at the following locations: HKEY_LOCAL_MACHINE\SOFTWARE\AFARIA\AFARIA\PATCH\ 5. Export all Afaria Channels. Ensure that the option to include the content and assignments for each channel are selected: c:\program files (x86)\afaria\bin\xaexport.exe \ c:\backup.cmx /r This process can be accomplished by executing the following command through a Session Manager channel or by using a simple batch file. Optional automation of channel export can be done by creating a Windows Task Scheduler task that executes the Channel Exports on a daily basis. More information about the xaexport and xaimport tools can be found by using the /? option. 6. Export HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Afaria to a registry file (.reg). This preserves the unique Server ID (Transmitter ID) and server settings that stored in the registry. 7. Back up the following directories: Preparing to Upgrade Afaria 2014 SAP SE or an SAP affiliate company. All rights reserved. 5

6 C:\PROGRAM FILES(X86)\AFARIA C:\PROGRAM FILES(X86)\AFARIAAPISERVICE C:\PROGRAM FILES(X86)\AFARIA COMMON C:\PROGRAM FILES(X86)\AFARIAEUSSP C:\PROGRAM FILES\AIPS C:\PROGRAM FILES\PACKAGESERVER Backing up the Afaria server installation directory preserves all Channel IDs, Channel worklists, any worklist assignments, worklist priorities, an so on. 8. Restart the Afaria Server service by running the following commands: net start Afaria Server /y net start AfariaIPhoneServer /y net start Afaria Backend Portal Package Server /y net start Afaria API /y net start Afaria Client Service /y 9. If required, log in to the Afaria Administration console and delete devices, policies, and settings for discontinued platforms and features SAP SE or an SAP affiliate company. All rights reserved. Preparing to Upgrade Afaria

7 3 Upgrading an Afaria Component Upgrade Afaria using the Afaria Setup program. When you run a setup wizard on a Windows server hosting an Afaria component, the wizard displays your current settings in the wizard screens. Click Next on each screen to accept the settings or make changes to the settings as required. Context Extract Afaria software files and launch the Afaria Setup program to upgrade Afaria components. Procedure 1. Copy the Afaria software package to a location that is accessible from your Windows Server and extract the files to the server. 2. Launch the Afaria Setup program (setup.exe) which is located in the root directory. 3. From the Afaria Setup menu, select the appropriate option to launch the required wizard. The wizard displays your current Afaria settings. 4. Make any changes to the selections and settings as required. See Installing Afaria for descriptions of the Afaria Setup wizards. 5. Select Install on the Ready to Start Installation screen to begin the upgrade. The Afaria Server upgrade process may take more than 30 minutes to complete. Caution Do not interrupt the upgrade process. Doing so may result in a corrupted database and an inoperable system. If the upgrade is interrupted, restore your database and restart the Afaria Server setup. Upgrading an Afaria Component 2014 SAP SE or an SAP affiliate company. All rights reserved. 7

8 4 Afaria Single-Server Upgrade Upgrade an installation with one Afaria Server. Procedure 1. Stop all Afaria services including Afaria Server, iphone, back-end portal, and API services. 2. Upgrade the Afaria Server, but do not start the service. 3. Upgrade the Afaria Administration console application. 4. Start Afaria Server service. 5. Upgrade additional servers, such as the Enrollment Server. 6. Connect devices for upgrade SAP SE or an SAP affiliate company. All rights reserved. Afaria Single-Server Upgrade

9 5 Afaria Server Farm Upgrade Upgrade a farm installation with a master Afaria server and one or more farm servers. Procedure 1. Stop all Afaria services on the master (main) Afaria Server and on all farm servers. Do not start the master and farm servers until after you have upgraded all components. 2. Upgrade the main Afaria server, but do not start the Afaria Server service. 3. Upgrade the farm servers. Do not start the Afaria Server service. 4. Upgrade the Afaria API and the Afaria Administration console application. 5. Upgrade additional servers, such as the Enrollment Server, Package Server, and Self-Service Portal. 6. Start Afaria Server service on the master server, then start the server service on the farm servers. 7. Start the remaining services on all servers. 8. Verify Afaria Client Service is running on all farm servers and replication is successful. 9. Connect devices for upgrade. Afaria Server Farm Upgrade 2014 SAP SE or an SAP affiliate company. All rights reserved. 9

10 6 Afaria Self-Service Portal Upgrade There is no direct upgrade path from earlier versions of Afaria Self-Service Portal to SP5. Instead, you must migrate each Afaria SP4 Self-Service Portal to the new SP5 Self-Service Portal model by running the SP5 Self- Service Portal installation once, then applying some migration steps to existing Self-Service Portal records. Context Beginning with SP5, there is only one Afaria Self-Service Portal Web site installation in IIS to serve all portals in the Afaria system. In earlier versions of Afaria, each Self-Service Portal had its own Web site installed in IIS. Due to these changes, you cannot perform an in-place upgrade of an SP4 or earlier Self-Service Portal to SP5; instead, the SP5 Self-Service Portal Web site is installed once, in a single new virtual directory in IIS, and this one installation then serves all Self-Service Portals in Afaria. After installing SP5, perform a one-time migration process to convert SP3 and SP4 Self-Service Portal records to the new SP5 SSP format. Note Upgrading to SP5 is not supported for Afaria versions earlier than SP3. Afaria SP5 also introduces a new attribute for each Self-Service Portal called the Relative URL. The Relative URL value is how one Self-Service Portal is distinguished from another in Afaria, and replaces the old model of installing separate Self-Service Portal Websites. This value is used as the new tail end of the full URL that is used to browse to the Self-Service Portal record, and comes after the [ssp root dir] that was specified when running the SP5 SSP installation. The new SSP URL format is root dir]/[relative URL]. For more information on the use of the new "Relative URL" value and how to configure Afaria Self-Service Portals in the Afaria Administrator, refer to Self-Service Portal section in the Configuring Afaria Guide. Procedure 1. Upgrade Afaria SP5 components (server, API, and so on). 2. Install the SP5 SSP component as a fresh installation, specifying the [ssp root dir] value. You cannot install the SP5 Self-Service Portal on top of a preexisting IIS virtual directory, including any SP4 or earlier SSP virtual directories. If you install SP5 Self-Service Portal on top of a preexisting IIS virtual directory, an error message "The virtual directory name you chose is already in use by another service. Please use a different name." will be displayed. 3. For migrating from SP4 Self-Service Portal: In the Afaria Administrator Self-Service Portal management page ( Server Configuration Self-Service Portal ), edit each pre-existing SSP record to add a new Relative URL value that is unique for each Self-Service Portal. For more information on the use of the new "Relative URL" value and how to configure Afaria Self-Service Portals in the Afaria Administrator, refer to Self-Service Portal section in the Configuring Afaria Guide. For migrating from SP3 Self-Service Portal: In the Afaria Administrator Self-Service Portal management page ( Server Configuration Self-Service Portal ), create a new Self-Service Portal record to match SAP SE or an SAP affiliate company. All rights reserved. Afaria Self-Service Portal Upgrade

11 each pre-existing SP3 Self-Service Portal. For this record, specify the description, choose the desired enrollment codes, and specify the new Relative URL value that will uniquely identify each Self-Service Portal. 4. Communicate the new SSP URL to end users for access to the SP5 SSP. Users should immediately begin using the new SP5 SSP URL format, instead of the older SSP URL. 5. Prevent users from accessing the old SP4 SSP URLs. At this point, the old SP4 or earlier Self-Service Portal still exists, and could still be accessible with the old SSP URL. Older versions of the Self-Service Portal are not supported with an SP5 system. To prevent access to older versions of the Self-Service Portal installations, perform one of the following changes: a) Redirect the old SSP URL to the new SP5 SSP URL using IIS URL Rewrite or virtual directory HTTP Redirection. b) Alternatively, from the Windows Control Panel, uninstall the old Self-Service Portal installations. However, without adding a URL rewrite redirection in IIS, the old SSP URL now shows error 404, page not found. Afaria Self-Service Portal Upgrade 2014 SAP SE or an SAP affiliate company. All rights reserved. 11

12 Important Disclaimers on Legal Aspects This document is for informational purposes only. Its content is subject to change without notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. Coding Samples Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence. Accessibility The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP specifically disclaims any liability with respect to this document and no contractual obligations or commitments are formed either directly or indirectly by this document. Gender-Neutral Language As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible. Internet Hyperlinks The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. Regarding link classification, see: help.sap.com/disclaimer SAP SE or an SAP affiliate company. All rights reserved. Important Disclaimers on Legal Aspects

13 Important Disclaimers on Legal Aspects 2014 SAP SE or an SAP affiliate company. All rights reserved. 13

14 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see index.epx for additional trademark information and notices.