Social Media Manager Release Notes

Transcription

1 Social Media Manager Release Notes Released On: September 20, 2012 Introduction This document provides information such as new features, enhancements, defects fixed and known defects in this release. This document also provides late breaking information to supplement Social Media Manager software and documentation. For updated documentation, product support notices, and service pack information, go to the Avaya Support Web site at The release is available on PLDS. Please contact Rich LeGrand before downloading/installing. Supported Platforms Avaya SMM Release is supported on the Microsoft Windows Server bit R2 platform. The minimum hardware requirements are: 2.0Ghz or faster quad-core CPU 250GB hard drive space for the application and database storage of posts 8 GB RAM Installation Required patches None Installing and troubleshooting the release For assistance installing the release or troubleshooting any issues encountered, please contact the Avaya Professional Services consultant that is engaged. Copyright 2012 Avaya Inc. All rights reserved. 1

2 Release Contents This section lists the resolved Defects and modifications Avaya Social Media Manager ID Name DE9682 RespondUI does not show a post/comment if it has the word "Error" in any part of it DE9754 Facebook Posted Link as Admin are not updated on DB DE9809 AvSocialRespond must state "Original Post Retrieved" DE9740 Add new channel - Facebook : Error initializing facebook gateway when adding a new channel DE9692 Sample DD applications templates contain images with wrong URL DE9687 Agent unabled to respond to tweet/@mention and responsehistory table is not updated US5826 Remove "Share_story" from SMM Obtaining Application Support If you are having trouble with Avaya Social Media Manager, you should: 1. Retry the action. Carefully follow the instructions in written or online documentation. 2. Check the documentation that came with your hardware for maintenance or hardware-related problems. 3. Note the sequence of events that led to the problem and the exact messages displayed. Have the Avaya documentation available. If you continue to have a problem, contact Avaya Technical Support by: 4. Logging in to the Avaya Technical Support Web site 5. Calling Avaya Technical Support at one of the telephone numbers in the Support Directory listings on the Avaya support Web site. You may be asked to one or more files to Technical Support for analysis of your application and its environment. The Social Media Manager application is not covered under a standard product maintenance contract. The process to get support varies based on whether you have purchased a custom application support agreement or not. Please follow one of the two processes below. Copyright 2012 Avaya Inc. All rights reserved. 2

3 With A Custom Application Support Agreement Customers that have purchased a Custom Application Support Agreement can follow this process to get Avaya remote support: Call the local Avaya Global Services Support Center the same way for requesting support under a current maintenance contract. In the US this number is Avaya will take the call and open a ticket, providing the case number to the customer. Avaya will work the case to determine the source of the issue. If the problem lies with the SMM application, details will be forwarded to APS Custom Application Support Group (CSISUPP work group) for case Management. (Note: A Special Handling note is already added in the ticketing system, providing overall instructions about the Custom Application and describing how to route the case for Avaya associates). Once the issue is resolved, Avaya will close case with the customer. Without A Custom Application Support Agreement Customers that have not purchased a Custom Application Support Agreement can follow this process to get Avaya remote support: Send an to proservices@avaya.com or call Note that charges will need to be authorized if the APS package s 60 day warranty period has expired. How to Upgrade > Backup First of all you need to backup your current installation, for example by copying the C:\AvayaSocialMM into a new folder C:\AvayaSocialMM-6_2_3 Also backup the database content just as a safety measure. 2 - Install Install using the given installer as a normal installation but be sure to select the option not to generate the database in case you want to keep the configuration and historical data. 3 - Apply database changes As you are going to keep your current database you'll need to perform some changes to it that are documented and delivered as part as the installer, in the file located at: C:\AvayaSocialMM\workspace\DBScripts\changelog.sql Use pgadmin or any DB client software to run all the SQL there. Be sure to execute them in reverse order, starting from the bottom up to the top in order to follow the chronological order of the changes. 4 - Restore customized modules Copyright 2012 Avaya Inc. All rights reserved. 3

4 There are three parts that you might have customized: The configuration files The D.D. Apps The RespondUI (agentui) Configuration Files Here we mean the following files: AvayaSocialMM\conf smm.properties AvayaSocialMM\bin config.xml To restore them into the new installation, just copy those files from your backup to the new installation. Respond UI This is in case you have changed the RespondUI webapp look and feel. This application has changed as part of delivery, so you cannot just overwrite the whole webapp with your backed-up version. Instead you must just overwrite the static content files. To do that copy the files from: C:\AvayaSocialMM-6_2_3\css\* C:\AvayaSocialMM-6_2_3\img\* C:\AvayaSocialMM-6_2_3\scripts\* To the same location but now in the new installation, meaning C:\AvayaSocialMM\ folder. IMPORTANT: Be careful just to copy those files mentioned above. You MUST NOT copy the old C:\AvayaSocialMM-6_2_1\WEB-INF\ content If you have customized any other file, like a jsp or js file, then you must perform the changes again to the new files. Probably you will need to compare both versions to see what has changed. DD applications There were no changes done to the DD application. Neither backward incompatibility. So you can just copy them for example from: C:\AvayaSocialMM-6_2_3\workspace\SocialAirlineFB To: C:\AvayaSocialMM\workspace\SocialAirlineFB Affected modules The following modules of the solution where affected by the changes: AvSMMAdmin AvSMMCommons AvSMMContextWS AvSMMCore AvSMMGateway AvSMMRespond Copyright 2012 Avaya Inc. All rights reserved. 4

5 AvSocialMMAdminUI AvSocialPluginAPI AvSocialPluginAtom AvSocialPluginFoursquare AvSocialPluginRSS AvSocialPluginYouTube com.avaya.sce.pdc.we. connector smm-contextws-core smm-installer smm-parent-installer smm-parent-project smm-tomcat-filter TestAutomation Copyright 2012 Avaya Inc. All rights reserved. 5