Home » IBM Manuals » Computer Software » IBM AH0QIKO » Manual Viewer

IBM AH0QIKO Upgrade Guide - Page 67

Configuring support for new attachments

Add to My Manuals
Save this manual to your list of manuals

Page 67 highlights

Upgrade Guide Configuring support for new attachments • Configure the application servers to use a list of IP addresses to find an available central push server. If a central push server does not respond to a request, the application can try to connect to another central push server. • Configure a hardware load balancer. The load balancer accepts all requests from the application servers, and distributes the traffic to the various central push servers. If a central push server does not respond, the load balancer redistributes the requests to the remaining central push servers. • Configure the application to use the new HTTP response header x-rim-push-gateways. Configuring support for new attachments Configure an upgraded BlackBerry Enterprise Server to support new attachment extensions When you upgrade a BlackBerry® Enterprise Server instance, the upgrade process does not automatically add the new attachment extensions that the latest BlackBerry Enterprise Server version supports. You must add the new attachment extensions after the upgrade process completes so that the BlackBerry Enterprise Server can recognize the new attachment extensions and send them to a BlackBerry Attachment Service instance for processing. The following list of supported file formats were added to versions later than BlackBerry Enterprise Server version 4.1 SP3: .amr*, .wma, .pptx, .docx, .xlsx, .odp, .ods, .odt, and .ott files. 1. In the BlackBerry Administration Service, on the Servers and components menu, expand BlackBerry Solution topology > BlackBerry Domain > Component view > Attachment > Connector. 2. Click the BlackBerry Attachment Connector instance for the BlackBerry Enterprise Server. 3. Click Edit instance. 4. Click Supported Attachment Server instances. 5. For the BlackBerry Attachment Service instance that you want the BlackBerry Enterprise Server to send new attachments to, click the Edit icon. 6. Add the new attachment extensions to the attachment extensions list. 7. Click Save all. Configure an upgraded BlackBerry Attachment Service to support new attachment distillers During the upgrade process for a BlackBerry® Attachment Service instance, the setup application does not turn on the new attachment distillers automatically. If you want the BlackBerry Attachment Service to process new attachments, you must turn on the attachment distillers for these file formats. The following supported file formats were added to versions later than BlackBerry Enterprise Server version 4.1 SP3: .amr*, .wma, .pptx, .docx, .xlsx, .odp, .ods, .odt, and .ott files. 1. In the BlackBerry Administration Service, on the Servers and components menu, expand BlackBerry Solution topology > BlackBerry Domain > Component view > Attachment > Server. 2. Click the instance that you upgraded. 65

Section	Page
Revision history	7
Overview: BlackBerry Enterprise Server	8
Planning a BlackBerry Enterprise Server upgrade	9
Supported BlackBerry Enterprise Server versions that you can upgrade	9
Replacing the BlackBerry Manager with the BlackBerry Administration Service	9
Upgrade implications for the BlackBerry Configuration Database	10
Synchronizing data over the wireless network automatically	10
Upgrade application for BlackBerry Enterprise Server	10
Upgrading the BlackBerry Enterprise Server if your organization's environment includes BlackBerry Mobile Voice System 4.6	11
Hardware requirements: BlackBerry Enterprise Server	12
System requirements	14
System requirements: BlackBerry Enterprise Server	14
System requirements: BlackBerry Administration Service and BlackBerry Web Desktop Manager	15
System requirements: BlackBerry Enterprise Server databases	16
System requirements: BlackBerry Attachment Service	17
System requirements: BlackBerry Collaboration Service	18
System requirements: BlackBerry MDS Connection Service	20
System requirements: BlackBerry Monitoring Service	21
System requirements: BlackBerry Router	21
System requirements for your organization's environment	22
System requirements: Browsers for BlackBerry Web Desktop Manager, BlackBerry Administration Service, and BlackBerry Monitoring Service users	22
System requirements: Messaging server	23
System requirements: Email applications for users	24
System requirements: Firewall	24
System requirements: Instant messaging server	24
Supported features and environments	25
Unsupported environments	25
Preupgrade tasks	27
Configuring a messaging environment	27
Configure a group for the BlackBerry Enterprise Server	27
Configure the Server document to permit the BlackBerry Enterprise Server to move user accounts within a BlackBerry Domain	27
Configuring connections for the BlackBerry Enterprise Server databases	27
Specifying permissions when you connect to the BlackBerry Enterprise Server databases using Windows authentication or Microsoft SQL Server authentication	28
Configuring the local system account in an IBM Lotus Domino environment	29
Resolving IT policy and application control policy conflicts in a mixed version environment	29
Resolve IT policy and application control policy conflicts in a mixed version environment	30
Backing up the BlackBerry Enterprise Server databases	30
Back up the BlackBerry Enterprise Server databases	30
Removing the BlackBerry MDS Integration Service	31
Run the CreateDB executable to remove the BlackBerry MDS Integration Service	33
Upgrade implications for VoIP profiles	35
Delete a VoIP profile	36
Install the SNMP service for monitoring by the BlackBerry Monitoring Service	36
Creating a BlackBerry Administration Service pool using DNS round robin that includes the BlackBerry Web Desktop Manager	36
Create the DNS record for a BlackBerry Administration Service instance	37
Preparing the computer that hosts the BlackBerry Collaboration Service for use with Microsoft Office Communications Server 2007 R2	38
Preparing the computer that hosts the BlackBerry Collaboration Service for use with Microsoft Lync Server 2010	39
Applications that are installed with the BlackBerry Enterprise Server components	40
Prerequisites: Upgrading the BlackBerry Enterprise Server software	40
Performing a test upgrade of the BlackBerry Configuration Database	42
Perform a test upgrade of the BlackBerry Configuration Database	42
Upgrading the BlackBerry Enterprise Server software by using the in-place upgrade process	44
Upgrade the BlackBerry Enterprise Server software by overwriting the existing version and using the existing BlackBerry Configuration Database	44
Specifying a name for the BlackBerry Administration Service pool during the installation process	46
Upgrade the BlackBerry Enterprise Server instances that you configured for disaster recovery	47
Upgrading the BlackBerry Enterprise Server using the cutover upgrade process and upgrade the existing BlackBerry Configuration Database	48
Upgrade a BlackBerry Configuration Database	48
BESMgmt.cfg properties	49
Install the BlackBerry Enterprise Server on a new computer and upgrade the existing BlackBerry Configuration Database	50
Specifying a name for the BlackBerry Administration Service pool during the installation process	52
Move user accounts to a new BlackBerry Enterprise Server using the BlackBerry Administration Service	52
Prevent the previous BlackBerry Enterprise Server from connecting to the BlackBerry Infrastructure	53
Start the new BlackBerry Enterprise Server	53
Upgrading the BlackBerry Enterprise Server using the cutover upgrade process and create a BlackBerry Configuration Database	54
Create a BlackBerry Configuration Database	54
BESMgmt.cfg properties	55
Install the BlackBerry Enterprise Server on a new computer and create a new BlackBerry Configuration Database	56
Specifying a name for the BlackBerry Administration Service pool during the installation process	58
Upgrading the BlackBerry Enterprise Server software in phases	59
Upgrade multiple BlackBerry Enterprise Server instances in phases	59
Upgrade a standalone BlackBerry Router	60
Test the connection from the BlackBerry Router to the BlackBerry Infrastructure	61
Postupgrade tasks	62
Resend the database mirroring parameters to BlackBerry Enterprise Server components	62
Restore the BlackBerry MDS Connection Service configuration files	62
Upgrade the BlackBerry database notification system	63
Best practice: Running the BlackBerry Enterprise Server	64
Configure the BlackBerry Administration Service instances in a pool to communicate across network subnets	65
Log in to the BlackBerry Administration Service for the first time	65
There is a problem with this website's security certificate	65
Change applications to support BlackBerry MDS Connection Service failover	66
Configuring support for new attachments	67
Configure an upgraded BlackBerry Enterprise Server to support new attachment extensions	67
Configure an upgraded BlackBerry Attachment Service to support new attachment distillers	67
Assigning an IT policy to a group	68
Remove an IT policy from a user account	68
Restrict database permissions for the BlackBerry Attachment Service	68
Configuring minimum Microsoft SQL Server permissions for the Windows account	69
Configure minimum Microsoft SQL Server permissions for the Windows account	70
Configuring a computer for monitoring	70
Configure the SNMP service for monitoring	70
Configure the BlackBerry Monitoring Service to monitor a BlackBerry Enterprise Server	71
Configure the BlackBerry Mail Store Service to use a local system account	71
Store database credentials for the local system account	72
Provisioning the BlackBerry Collaboration Service as a trusted application	72
Manually provision the BlackBerry Collaboration Service as a trusted application	73
Turn off automatic provisioning of the BlackBerry Collaboration Service as a trusted application	73
Troubleshooting the BlackBerry Enterprise Server upgrade process	75
Failed to write License Key to the Database	75
Previous version detected but no database available	75
Could not open ID file	75
Attempt to establish connection failed with security reason \	76
You encounter errors when you try to upgrade the BlackBerry Configuration Database	76
You cannot resolve errors that occur when you move users	76
A third-party tool did not install and the BlackBerry Enterprise Server setup application closed	76
The BlackBerry Monitoring Service cannot monitor events	77
Restore a BlackBerry Configuration Database	77
Various BlackBerry Enterprise Server components do not start	78
You cannot access the BlackBerry Administration Service	78
You cannot create a user account in the BlackBerry Administration Service	79
The BlackBerry Administration Service pool name is the same as the FQDN of the host computer	79
IBM Lotus Domino takes a long time to complete cluster replication	80
Some web services do not function correctly after upgrading the BlackBerry Enterprise Server for IBM Lotus Domino	80
Glossary	81
Provide feedback	85

Match case Limit results 1 per page

•

Configure the application servers to use a list of IP addresses to find an available central push server. If a

central push server does not respond to a request, the application can try to connect to another central push

server.

•

Configure a hardware load balancer. The load balancer accepts all requests from the application servers, and

distributes the traffic to the various central push servers. If a central push server does not respond, the load

balancer redistributes the requests to the remaining central push servers.

•

Configure the application to use the new HTTP response header x-rim-push-gateways.

Configuring support for new attachments

Configure an upgraded BlackBerry Enterprise Server to support new

attachment extensions

When you upgrade a BlackBerry® Enterprise Server instance, the upgrade process does not automatically add the

new attachment extensions that the latest BlackBerry Enterprise Server version supports. You must add the new

attachment extensions after the upgrade process completes so that the BlackBerry Enterprise Server can recognize

the new attachment extensions and send them to a BlackBerry Attachment Service instance for processing. The

following list of supported file formats were added to versions later than BlackBerry Enterprise Server version 4.1

SP3: .amr*, .wma, .pptx, .docx, .xlsx, .odp, .ods, .odt, and .ott files.

In the BlackBerry Administration Service, on the

Servers and components

menu, expand

BlackBerry Solution

topology > BlackBerry Domain > Component view > Attachment > Connector

Click the BlackBerry Attachment Connector instance for the BlackBerry Enterprise Server.

Click

Edit instance

Click

Supported Attachment Server instances

For the BlackBerry Attachment Service instance that you want the BlackBerry Enterprise Server to send new

attachments to, click the

Edit

icon.

Add the new attachment extensions to the attachment extensions list.

Click

Save all

Configure an upgraded BlackBerry Attachment Service to support new

attachment distillers

During the upgrade process for a BlackBerry® Attachment Service instance, the setup application does not turn on

the new attachment distillers automatically. If you want the BlackBerry Attachment Service to process new

attachments, you must turn on the attachment distillers for these file formats. The following supported file formats

were added to versions later than BlackBerry Enterprise Server version 4.1

SP3: .amr*, .wma, .pptx, .docx, .xlsx, .odp, .ods, .odt, and .ott files.

In the BlackBerry Administration Service, on the

Servers and components

menu, expand

BlackBerry Solution

topology > BlackBerry Domain > Component view > Attachment > Server

Click the instance that you upgraded.

Upgrade Guide

Configuring support for new attachments