TIBCO FOM 2.0.1 Hotfix02 is available
Article ID: KB0104899
Updated On:
| Products | Versions |
|---|---|
| TIBCO Fulfillment Order Management | - |
| Not Applicable | - |
Description
Description:
The hotfix can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to /available_downloads/ActiveFulfillmentFramework/ActiveFulfillment/2.0.1/hotfix-02/ to download the hotfix.
Instructions on how to apply the hotfix are provided in the TIB_af_2.0.1_HF-002_readme.txt file.
================================================================================
Closed Issues in 2.0.1_HF-002 (This Release)
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 i.e. 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 is ignoring CrossLink Affinity
If a plan fragment were associated with products, included in the execution
plan due to ProductRequiredFor relationships, and also configured as
CrossLink Affinity, the CrossLink Affinity did not work.
AF-2918
Amendments using the RESTART action did not works if plan item was completed.
In case of amendments using 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, dude 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
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 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 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.
The hotfix can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to /available_downloads/ActiveFulfillmentFramework/ActiveFulfillment/2.0.1/hotfix-02/ to download the hotfix.
Instructions on how to apply the hotfix are provided in the TIB_af_2.0.1_HF-002_readme.txt file.
================================================================================
Closed Issues in 2.0.1_HF-002 (This Release)
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 i.e. 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 is ignoring CrossLink Affinity
If a plan fragment were associated with products, included in the execution
plan due to ProductRequiredFor relationships, and also configured as
CrossLink Affinity, the CrossLink Affinity did not work.
AF-2918
Amendments using the RESTART action did not works if plan item was completed.
In case of amendments using 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, dude 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
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 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 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.
Issue/Introduction
TIBCO FOM 2.0.1 Hotfix02 is available
Environment
Product: TIBCO Fulfillment Order Management
Version: 2.0.1
OS:
--------------------
Feedback
Yes
No
Powered by
