IBM Intelligent Operations for Transportation Version 1.6

interim fix

 

About this readme file

This readme provides information about an interim fix release for IBM Intelligent Operations for Transportation that contains fixes for APAR PO03896, APAR PO03741, APAR PO03501, APAR PO03895, APAR PO03877, and PO03730, APAR PO03964, and APAR PO03963.

 

Introduction

The following fixes are contained in this interim fix release for the Traffic Prediction feature of IBM Intelligent Transportation version 1.6.

  1. PO03896 and PO03741: The fix resolves issues related to trace logging in Traffic Prediction batch (estimation) calculation. Some of the trace statements have been moved to INFO level to improve the performance.
  2. PO03501: The fix resolves an issue in the French locale. While inserting status descriptions in the TPTOOL.PROCESS_LOG table, the SQL statement fails with a SqlSyntaxErrorException due to an unescaped apostrophe.
  3. PO03963: The fix optimizes the performance of Traffic Prediction calculation by reducing the CPU consumption
  4. PO03895: The fix resolves an issue related to trace logging in Traffic Prediction calculation. Some of the trace statements have been moved to INFO level to improve the performance.
  5. PO03877: The fix resolves an issue whereby the traffic prediction results are not displayed on the Traffic Prediction map portlet. The portlet displays the message "No Data available" when there is valid data in the database. Additional checks have been put in place to trim the value of the LINKTYPE field while importing link details from the TIH.LINK table. This checking action eliminates any trailing white spaces. The existence of such trailing spaces is the cause of the issue.
  6. PO03730: In the solution administration page, Traffic Prediction: Estimate Calculations, the Off-Peak times and Peak Times values are required in Coordinated Universal Time (UTC). The fix adds a note to the administration page instructing the user to convert the required time values to UTC time, and then to select those values from the list.
  7. PO03964: The fix provides a mechanism for extending the prediction time by a couple of time slots to ensure that 60th minute prediction is available for the user in the Traffic Prediction map portlet.

Installation Instructions

1.    Extract and copy the artifacts

 

·   tpt_common.jar

·   trans_forecast_rest_ear.ear

·   trans_forecaster_portlet_ear.ear

·   trans_portlet_ear.ear

·   trans_tptool_batch_ear.ear

·   trans_tptool_ear.ear

·   TP_Master_Data.sh

·   TP_Update_Prediction_Time_slots.sh

 

2.    Update EAR files

 

    1. Login to the portal server node.
    2. Launch the WebSphere Application Server administration console.
    3. Go to  Applications>Application Types>WebSphere enterprise applications


 

    1. Update the trans_forecast_rest_ear.ear file with the new trans_forecast_rest_ear.ear file accepting default configurations.
    2. Update the trans_forecaster_portlet_ear.ear file with the new trans_forecaster_portlet_ear.ear file accepting default configurations.
    3. Update the trans_portlet_ear.ear file with the new trans_portlet_ear.ear file accepting default configurations.
    4. Update the trans_tptool_batch_ear.ear file with the new  trans_tptool_batch_ear.ear file accepting default configurations.
    5. Update the trans_tptool_forecast_ear.ear file with the new trans_tptool_ear.ear file accepting default configurations.

1.    Replace the JAR file

    1. In the portal server node, go to /opt/IBM/iss/intelligentTransportation/intelligentOperationsTransportation/lib.
    2. Replace tpt_common.jar with the new JAR file.
    3. Restart the WebSphere_Portal server from the administration.

2.    Update Database

    1. Login to the data server as database administrator, db2inst2.
    2. Connect to the TIH_HS database.
    3. Execute the TP_Master_Data.sh script with the following command:

./TP_Master_Data.sh <db_name> <db_user_name> <db_password>

For example: 

./TP_Master_Data.sh TIH_HS db2inst2 password


Note: Use this script only if the issue listed in PO03877 arises after setting up the environment or you are setting up a new environment from the start.

    1. Execute TP_Update_Prediction_Time_slots.sh with the following command:

./ TP_Update_Prediction_Time_slots.sh <db_name> <db_user_name> <db_password> <pred_time_slots>

For example, in case of 5 minutes:

./ TP_Update_Prediction_Time_slots.sh tih_hs db2inst2 password 1,2,3,4,5,6,7,8,9,10,11,12,13,14

 

Note: Use this command with caution. It is not recommended to increase the time slots to more than 14 (in case of 5 minute prediction) or to more than 6 (for 15 minute prediction)