Description:
The hotfix can be downloaded from the TIBCO Support ftp server, mft.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to /AvailableDownloads/ActiveFulfillment/2.0.1/hotfix-05/ to download the hotfix.

Instructions on how to apply the hotfix are provided in the TIB_af_2.0.1_HF-005_readme.txt file.

================================================================================
Closed Issues in 2.0.1_HF-005 (This Release)

AF-4869
Some orders, which were CANCELLED, still had a SUSPENDED status assigned to it
even when two Orchestrator instances were running. The issue has been fixed and
the changes have been committed from the order history before sending the set
plan notification to Orchestrator. This prevented the occasional overriding of
order status made by the order notifications that were sent, immediately after
the set plan notification is sent to the Orchestrator.

AF-4840
In a setup having multiple instances of AOPD, when an Amendment request is
initiated, the AOPD receives the amendment request, but sometimes never replies
to the Orchestrator, keeping the Order or Plan in SUSPENDED status without
triggering the ACTIVATE or REDO events. The issue has been fixed.

AF-4737
When the Orchestrator executes the RETRY on a plan item, having the status
ERROR_HANDLER, the plan item retains the status ERROR_HANDLER during
Orchestrator RETRY instead of changing the status to EXECUTION. The issue
has been fixed.

AF-4363
FOM was allowing an immediate second amendment or cancelation request for an order
which was already being amended or canceled. The error code "TIBCO-AFF-OMS-100016"
and the error message "The order cannot be amended. Amendment already in progress"
were not returned. The issue has been fixed and henceforth an immediate second
amendment or cancelation request will not be allowed when an existing amendment
or cancelation is in progress, and the mentioned error code and error message will
be returned by OMS. Additionally, FOM will return ORDER_NOT_AMENDABLE error if
an amendment or cancelation request is sent for an order that is already
COMPLETE or CANCELLED.

AF-4302
When an amendment was performed, sometimes, the process component did not get
the updated plan using the GetPlan JMS call, or the process component got a
"Not found" exception message as a response to the GetPlanItem JMS call for a
COMP or REDO plan item. The reason was a transaction latency issue in OMS,
which failed to commit the updated plan, into the database, before the
Orchestrator activated the order. The issue has been fixed. The Orchestrator
will now activate the amendment plan only after the plan has been successfully
committed to the OMS database. This ensures that the GetPlan, SetPlan,
GetPlanItem, and SetPlanItem requests, executed by the process components,
do not fail.

AF-3852
The change in sequence of the order lines lead to different plans being
generated for the same order. This behavior lead to inconsistency in plan
generation. The issue has been fixed. If you assign a sequence to the product
during product model loading time in AOPD, and when the order arrives in AOPD,
it will be sorted according to the sequence of numbers assigned for products,
so that whatever is the sequence of orderlines, the order going into plan
generation will have the same sequence orderlines. This resulted in a
consistent plan being generated every time.

AF-3659
When specifying a custom value for AFRE_CDD, and when deploying the
configuration on multiple servers, the change is lost and the field, upon
completion of deployment, is empty. The issue has been fixed and the name
value  pairs have been added to "Runtime" section of "Global Variables" so
that the properties can be configured through deploy tool.

================================================================================
Closed Issues in 2.0.1_HF-004 (This Release)

AF-3837
If an order was amended multiple times, an exception was raised and the order was
removed. The exception occurred because the limit of the column size of
"PLANITEM_UDF_DATA.EVALUATIONPRIORITY" was set to 100, and each amendment
added a "REDO-" prefix, thus increasing the column size. The issue was fixed and
the limit of the column size was increased.

AF-3833
If an execution plan was amended multiple times, the execution plan did not retain
the correct plan item IDs in the evaluationPriority for the shared UDFs. The
issue was fixed and the evaluationPriority now stores the appropriate plan
item ID even after multiple amendment of the execution plan.

AF-3823
The execute request for the REDO-2 plan item in the second amendment, which is
dependent on the already completed REDO-1 plan item from the first amendment, was
not sent out by Orchestrator. The issue was fixed.

AF-3742
The Error Code TIBCO-AFF-OMS-100000 was displayed, instead of TIBCO-AFF-OMS-100003,
if the order with same order reference was submitted twice. The issue was fixed
and the Error Code TIBCO-AFF-OMS-100003 was displayed when the property
"com.tibco.af.oms.webservice.idempotency" was set to FALSE. The Error Code
TIBCO-AFF-OMS-100000 was displayed instead of TIBCO-AFF-OMS-100004,
if the amendment was submitted for a non existent order reference. The issue was
fixed.

================================================================================
Closed Issues in 2.0.1_HF-003

AF-3783
The evaluationPriority element, for the 'Shared' type of UDFs in the plan items,
contained the IDs of the plan items that are not present in the order amendment
plan. The issue has been fixed and the evaluationPriority string now contains the
ID's of the appropriate plan items that are present in the order amendment plan.

If the evaluationPriority in the original plan contained the IDs of plan
items which now have REDO plan items in the amendment plan,
the evaluationPriority will contain the IDs of the corresponding REDO plan
items instead of the original plan items. It is logical because the original plan
items are activated and cancelled after the amendment plan is
activated. However, the REDO plan items are executed to perform the tasks that
were supposed to be done by the original plan item before the amendment.

AF-3782
Some of the intermediate milestone dependencies, that were present in the
original plan, were lost in the order amendment plan. The issue has been fixed
and the expected intermediate milestone dependencies are present in the order
amendment plan.

If the original plan has a milestone dependency on a plan item which now has
a REDO plan item in the amendment plan, the milestone dependency is shifted
to the corresponding REDO plan item instead of the original plan item.
It is logical because the original plan items are activated and cancelled
after the amendment plan is activated. However, the REDO plan items are
executed to perform the tasks that were supposed to be done by the original
plan item before the amendment.

AF-3463
The OMSServer was not able to connect to the secondary EMS server, when the
primary EMS Server went down. The issue has been fixed and the OMSServer is now
able to connect to the secondary EMS server in the fault tolerance EMS setup
without any warnings or errors.

================================================================================
Closed Issues in 2.0.1_HF-002

AF-3756
Shared attribute values no longer disappear after an amendment request.

AF-3748
An intermediate milestone expected to come into the plan item every time was
disappearing in the execution plan that was generated for the order amendment
request. The plan item now contains the expected intermediate milestone and it
no longer disappears in the generated execution plan.

AF-3726
The only value supported for "Operation Data Store Type" is "activespace".
Replication policy and replication count can be configured from the configurator.

AF-3725
No matching section was specified in the plan for the section XXX:XXX: START-END
java.lang.NullPointerException. This issue has been fixed.

AF-3724
Enriched plans for cancelled orders were being received incorrectly. This issue
has been fixed.

AF-3723
Milestone data was not populated in plan item details, which are saved in the
Jeopardy header. This issue has been fixed.

AF-3722
Some of the plan and plan item Jeopardy notifications were sent multiple times
for the same plan and plan item. This issue has been fixed.

AF-3721
No data was available in the activespace cache to delete so it was not able to
get a lock on the required object. This issue has been fixed.

AF-3720
Process component information was not properly populated in the activespace
cache. This information is now properly maintained in the activespace cache for
later use.

AF-3719
Orders were not deleted from the Jeopardy Management component (JeOMS) cache
when such orders were withdrawn. Orders are now deleted from the JeOMS cache
when they are withdrawn.

AF-3712
Plans wouldn't start when the first plan item in a plan to execute was
non-executing. The completed non-executing plan item didn't satisfy the
dependencies of dependent plan items because the condition plan.started = true
was missing.

This condition has been added to the rule, which satisfies the dependencies.
Plans now start when the first plan item is non-executing.

AF-3357
The sequenceDirection is now taken into consideration by Fulfillment Order
Management for ProductDependsOn (PDO) relationships. Previously, this did not
happen, which resulted in order modification actions being executed in the
incorrect order.

AF-3305
Unexpected Attribute Decomposition no longer leads to extra plan items in
the execution plan.

The decomposition expression is now checked only against the
orderline of the specific product and its parents. A new global variable has
been added to enable this functionality. The value of the
AFF/OfferConfigurationValidation/Flags/AOPD/ABDProductOrderline variable should
be set to true. By default it is set to false.

The decomposition expression now also considers the product model
characteristics of the parent product and its parents if any. A new Global
variable has been added to enable this functionality. The value of the
AFF/OfferConfigurationValidation/Flags/AOPD/ABDIncludeCharacteristics variable
should be set to true. By default it is set to false.  

AF-3287
The logging in the routing functionality for Suspend and Activate requests on
the basis of 'owner' field in planFragment model has been corrected.

AF-3266
The PlanItemFailedRequest message (sent from the Orchestrator to the error
handler component) is now always sent on the default queue, which is
"tibco.aff.orchestrator.provider.planItem.failed.request". This message will be
sent to the default queue regardless of the value of the "owner" field in plan
fragment models.  

AF-3247
The orderPriority value passed in the order amendment request is propagated as
"JMSPriority" in the four event messages (OPDRequestEvent,
ExecutionPlanAmendRequest, ExecutionPlanAmendResponse, and OPDResponseEvent)
that are exchanged between the Orchestrator and AOPD components for plan
generation. After the amendment plan is generated and activated, the same value
is propagated as "JMSPriority" in the following messages:
 o PlanItemActivateRequestEvent messages for plan items that were suspended for
   amendment.
 o PlanItemExecuteRequestEvent messages for newly added plan items.
 o PlanItemSuspendRequestEvent messages if the plan is suspended further either
   explicitly or due to a new amendment request.    

AF-3201
Previously, if a source product had ProductComprisedOf (PCO) children, then its
children depended on a ProductDependsOn (PDO) product. If there were no PCO
products then there was a dependency on the source product.

A global variable AFF/OfferConfigurationValidation/Flags/AOPD/IgnorePDOFirstChildDependency
has been added that indicates whether PDO must take care of the children or only
the source and target product. The value of this variable should be set to true to
enable the functionality, by default it is set to false.

AF-3146
In cases of amendment, the plan, plan item, and status elements did not match
the Jeopardy header, plan item, status elements for the enriched plan.

Jeopardy header information is now updated with the most recent information for
plan and plan item elements.

AF-3145
Previously, data was only partially populated for the plan
:XXXX com.tibco.aff.jeoms.processor.PartialDataException. Missing information in
plan item data is now saved in the jeopardy header.

AF-3006
Two components, AFI and TDS, were rewritten into Java in Fulfillment Order
Management version 2.0.0. Because of this change, messages corresponding to the
in-process orders in ActiveFulfillment version 1.2.0 are not permitted to be
pending on their respective queues in Fulfillment Order Management version
2.0.0. Such messages must be processed using ActiveFulfillment 1.2.0 before
migration. See TIB_af_2.0.1_HF-002_readme_addendum.pdf for complete, detailed
instructions about clearing queues before migration.

================================================================================
Closed Issues in 2.0.1_HF-001

AF-3095
Empty characteristics in product model had "null" as strings values in the
execution plan.

AF-3094
ProductRequiredFor threw exception error for certain cases of characteristics
while logging them.

AF-2999
It was not possible to have multiple required products from PRF relationships if
they had the same LinkID. However, it is now possible to have multiple required
products with the same LinkID in plan only if they have different order line
numbers that is, they are decomposed from different orderlines. A new Global
variable has been added to enable this functionality. The value of the
AFF/OfferConfigurationValidation/Flags/AOPD/AllowMultipleRequiredProducts variable
should be set to true, by default it is set to false to maintain backward
compatibility.

AF-2986
ProductRequiredFor was ignoring CrossLink Affinity
If a plan fragment was associated with products, included in the execution
plan due to the ProductRequiredFor relationships, and also configured as
CrossLink Affinity, the CrossLink Affinity did not work.

AF-2918
Amendments using the RESTART action did not work if the plan item was completed.
In case of amendments using the RESTART EPMR action, Orchestrator failed to
trigger PlanItemExecuteRequestEvent for a newly created REDO plan item
corresponding to a plan item that was already COMPLETE before the amendment.

AF-2654
AOPD did not load the newly published action models, if any other action models
were already loaded.

AOPD, on its startup, correctly loaded all the action models published.
However, due to incorrect implementation logic, any subsequent action model
published was not loaded properly.  

AF-2653
IOException error occurred while copying the offline catalog file to
SUCCESS or FAILURE directory in case of using offline 'Master'
(engine startup) mode.

AF-2635
The script error was thrown when accessing Gantt chart in case some data is
missing in JeopardyHeader.

AF-2634
The jeopardy header data in the enriched plan was not populated correctly
due to latency.

AF-2623
Unable to view Gantt charts for orders having execution status.

AF-2610
Orchestrator tried to process pending messages after restarting the engines.
NOTE: This defect occurred due to AF-2605

AF-2605
Messages are pending on tibco.aff.orchestrator.planItem.execute.reply and
tibco.aff.orchestrator.planItem.suspend.reply queue.

Orchestrator was not to able handle the duplicate or invalid event messages
corresponding to PlanItemExecuteResponseEvent, PlanItemSuspendResponseEvent
and PlanItemMilestoneNotifyRequestEvent coming from process components.
Such messages would not be processed by Orchestrator and would remain
pending on the respective JMS queues forever. This issue has been fixed
now and Orchestrator is now able to handle the corresponding duplicate or
invalid messages. Three new error codes and messages have been added to log
the corresponding exceptions. The sample log statement for each duplicate or
invalid message are given below for reference.

[AFF-ORCH-PLAN-0700] PlanItem EP_TEST0.0281755 in Plan
61f0e938-a4e3-4491-b2fa-1d79398fa1fd is already COMPLETE.
Cannot process this invalid or duplicate PlanItemExecuteResponseEvent
from process component.

[AFF-ORCH-PLAN-0701] PlanItem EP_TEST0.7239272 in Plan
03fad0f7-ea01-4e3a-8430-37192775c141 is already SUSPENDED.
Cannot process this invalid or duplicate PlanItemSuspendResponseEvent
from process component.

[AFF-ORCH-PLAN-0702] Milestone MILE1 in planItem EP_TEST_PROVIDE_100.4179139 of
plan 0df75857-e45d-47fd-8bca-507a4d6944cc is already notified, ready and COMPLETE.
Cannot process this invalid or duplicate PlanItemMilestoneNotifyRequestEvent
from the process component.

NOTE: The project libraries - AF_Orchestrator.projlib and
AF_Orchestrator_ForDesigner.projlib - are modified and shipped in 2.0.1 HF1.
It is because of the addition of the above three error codes and messages
under global variables. There are no changes in the interfaces or schemas
in 2.0.1 HF1. If you do not want to use these error codes in the process component
implementation, use the two project libraries shipped in FOM 2.0.0 GA.

TIBCO FOM 2.0.1 Hotfix05 is available

Product: TIBCO Fulfillment Order Management Version: 2.0.1