Infor EAM 11.0 201602 Jira Report

Jira Report

Date 29-Feb-2016

Fix For Version 11.0 Patch

Build 201602

Infor EAM 11.0 201602 Jira Report

Jira Summary

Jira # Title

EAM-17274 CLONE - Base - Microsoft SQL Server JDBC driver upgrade

EAM-18111 Systems | Costs - Error "The SQL Statement is invalid..." when using any of the Cost fields in the Dataspy Filter

EAM-18559 CLONE - Work Orders | Calibration - For multiple equipment WO, header field values are not coming from correct equipment

EAM-18638 CLONE - CLONE - Customer Surveys | Questions - Question Text is getting updated when the Translated Description is updated in Long Translations tab.

EAM-19267 Alerts | WO Alert - unable to select organization when MULTIORG=OFF

EAM-19346 Upload Utility - Unable to update equipment records if records exist in r5objectsurvey

EAM-19419 Systems | Costs - Refresh Costs Data results in error 'The system cannot process your request."

EAM-19719 REPORTS - Change the function of emailing reports to use install parameter SMTPSEND instead of Userid email address.

EAM-19910 CLONE - Generate WOs - system error when processing time > transaction timeout

EAM-20208 Work Orders - EVT_DURATION is incorrect if Scheduled End Data of Work Order is on the weekend.

EAM-20270 SR-Service Request - Description is not being carried over to the Work Order when created. Coming from Std. WO instead.

EAM-20399 Blanket Orders - Problem with rounding formula between blanket Order PO Header and Blanket Order Lines

EAM-20527 Base - Performance Issue caused by infinite loop when duplicate custom fields are encountered.

EAM-20773 Base - Update AppConfig.java for 11.0 201602 patch

EAM-20814 CLONE - Databridge | Receive PO - Error for direct material when TOENT is EVNT

EAM-20995 Databridge - Message Archive/Purge Process Enhancement

EAM-21060 Databridge/ION - MaintenanceOrder BOD fails due to security rights

EAM-21086 CLONE - Alert Management | WO Alerts - new wo created from alert with std wo does not copy Equipment Location on the work order

EAM-21102 Databridge: Retry processor enhancement

EAM-21131 Barcode - error No active sessions error when printing on Cloud Ops environments

EAM-21224 CLONE - Work | Process | Generate WOs - 'The system failed to carry out this function because of environment or configuration problems' when using Generate WOs to

change status of duplicate PM work orders.

Infor EAM 11.0 201602 Jira Report

Installation Instructions for Infor 11.0 201602 Patch In an effort to ensure that your Infor EAM environment continues to operate with maximum efficiency and minimal problems, Infor Global Solutions strongly recommends that you: Note: This patch can only be applied to an Infor EAM environment that has v11.0 201512 build installed. Back-up your current Infor EAM database before installing this patch. Let only a qualified Infor EAM Integrator/ Administrator install this patch. Apply this patch to a test environment and perform your own user acceptance testing before applying this patch to your production environment. For Infor EAM, on the Administration | Security | Install Parameters form, the Install Parameters: FORMDATE and FORMDATI must have 4-digit year format, i.e. DD-MON-RRRR. " To determine if the Infor EAM 11.0 201512 is installed, login to Infor EAM, click on About and verify version is 11.0 201512

Important Note: If you are using Databridge, please carefully review those JIRAs that come with DATABRIDGE IMPACT NOTE and evaluate potential patch impact on your interface before installing this patch. Please search JIRA description for DATABRIDGE IMPACT NOTE to identify those JIRAs.

Installation Instructions for Infor EAM Database Installations: Installing on an Oracle Server Database: 1. Log all users out of the application. 2. Stop the Infor EAM application as mentioned in the Infor EAM Administration Guide. 3. Copy the DB110201602ORA.sql and EAMcomp.sql to a local directory that can be called directly from SQL Plus. 4. In SQL Plus, run DB110201602ORA.sql. 5. In SQL PLUS run EAMcomp.sql to validate any invalid objects. 6. Exit SQL Plus. 7. Restart the application server. Installing on an MS SQL Server Database: 1. Log all users out of the application. 2. Stop the Infor EAM application as mentioned in the Infor EAM Administration Guide. 3. Copy the DB110201602SQL.sql file to a local directory that can be called directly from Query Analyzer. 4. Login to Query Analyzer as SA user. 5. In Query Analyzer, select the database you need to apply the patch and run DB110201602SQL.sql 6. Exit Query Analyzer. 7. Restart the application server.

Application Server Installations: Installation steps for Linux Jboss/Weblogic app server environments for Infor EAM:

1. Log all users out of the application. 2. Make sure you are logged in as the same user that installed Infor EAM. 3. Open a shell session and stop the Infor EAM application as mentioned in the Infor EAM Administration Guide. NOTE: A bourne-derivative shell must be used in order to run the patch

Infor EAM 11.0 201602 Jira Report

4. Ensure that a proper backup of the Infor EAM installation is available, in the event of any problems that arise during the patch process. 5. Copy the patch file EAM110LN201602.sh to a temporary directory like /tmp 6. Navigate to the temporary directory then execute the shell script file like #./EAM110LN201602.sh, type yes, and press enter to unzip. (It will create and unzip files to an EAM110LN201602 folder) 7. Navigate to the EAM110LN201602 directory and set the variable APPSRV_HOME to the location where Infor EAM is installed. 8. Apply the patch by executing this command at the prompt, substituting a value for {logging_level}: ./patch.sh {logging_level} NOTE: The brackets on logging_level denotes that this value is optional The default value for {logging_level} is info. The available logging levels are as follows from least to greatest: error warn info verbose debug 9. Go to the depconfig directory and execute this command at the prompt: ./deploy.sh NOTE: For WebLogic Application Server, all application servers must be running before deploying Infor EAM 10. Once the process is complete, close the command prompt and start the Infor EAM Application daemons. NOTE: For WebLogic Application Server, all application servers must be restarted 11. Infor EAM Application and daemons should now be up. NOTE: During processing, the patch status will be echoed to the console. A patch log will also be created identified by having the current patch execution date and time as part of the filename in the patch directory. One common error is "java.io.IOException: Error in writing existing jar file" which is produced if the Infor EAM daemons were not stopped before patch installation (step 3). To correct, ensure that the Infor EAM daemons are stopped, and repeat the patch installation process. Depending on the specifications of the underlying hardware, the patch process may require up to an hour to perform all necessary updates. Please be patient to allow the patch process to fully complete before halting the patch script or exiting the current shell.

Installation steps for Windows Jboss app server environments for Infor EAM:

1. Log all users out of the application. 2. Make sure you are logged in as the same user that installed Infor EAM. 3. Stop the Infor EAM application as mentioned in the Infor EAM Administration Guide. 4. Ensure that a proper backup of the Infor EAM installation is available, in the event of any problems that arise during the patch process. 5. Copy the patch file EAM110WN201602.exe to a temporary folder like c:\temp 6. Double click on the self-extractor file to execute it 7. Press 'Unzip' to create and unzip files to an EAM110WN201602 folder 8. Open a command prompt (cmd.exe) and change the directory to EAM110WN201602 9. Apply the patch by executing ths command at the prompt, substituting values for destination_of_server_root and {logging_level}: patch.bat destination_of_server_root {logging_level} NOTE: The brackets on logging_level denotes that this value is optional destination_of_server_root is the root location of where Infor EAM is installed. (E.g. c:\InforEAM) The default value for {logging_level} is info. The available logging levels are as follows from least to greatest: error warn info verbose debug 10. The patch will automatically redeploy the application components. 11. Once the process is complete, close the command prompt and start the Infor EAM Application services. 12. Infor EAM Application and services should now be up.

Infor EAM 11.0 201602 Jira Report

NOTE: During processing, the patch status will be echoed to the console. A patch log will also be created identified by having the current patch execution date and time as part of the filename in the patch directory. One common error is "java.io.IOException: Error in writing existing jar file" which is produced if the Infor EAM services were not stopped before patch installation (step 3). To correct, ensure that the Infor EAM services are stopped, and repeat the patch installation process. Depending on the specifications of the underlying hardware, the patch process may require up to an hour to perform all necessary updates. Please be patient to allow the patch process to fully complete before halting the patch script or exiting the current shell.

Installation steps for Advanced repor