RS03701: DEPLOYMENT CONFIGURATIONS CREATED IN A SUB-PROJECT USING RULE DESIGNER CANNOT BE USED IN THE BUSINESS CONSOLE

Operational Decision Manager V8.10.5.0: Interim Fix 12 for Decision Center
IBM Operational Decision Manager V8.10.5 Download Document
IBM Operational Decision Manager V8.10.5 Refresh Pack
Operational Decision Manager V8.9.2.3: Interim Fix 7 for Decision Center
Operational Decision Manager V8.9.2.3: Interim Fix 8 for Decision Center
Operational Decision Manager V8.9.2.3: Interim Fix 9 for Decision Center

APAR status

• Closed as program error.

Error description

• In a Decision Service containing at least a dependent project,
  if you create using Rule Designer a deployment configuration
  within a dependent project and then publish it into Decision
  Center, then the Business Console fails to run this deployment
  configuration.
  
  This problem is not happening if the deployment
  configuration is created
  - using Rule Designer in the main
  project
  - or using the Business Console.
  
  This problem affects
  all versions at least since 8.9.2 with two different symptoms
  depending on the version:
  - either the error message "There is
  already a baseline for which the property 'name' is
  '<suffix><timestamp>' in project '<the dependent project>'
  within decision service '<the Decision Service>'" is displayed
  and the deployment continues endlessly,
  - or the deployment
  fails and the exception below is displayed in the
  report:
  ilog.rules.teamserver.model.IlrInvalidElementException:
  There is already an item for which the property 'name' is
  'scoring_2020-10-29T09_19_41Z'
   at ilog.rules.teamserver.ejb.se
  rvice.dao.IlrElementDAOJDBC.checkElementBeforeCommit(IlrElementD
  AOJDBC.java:6434)
   at ilog.rules.teamserver.ejb.service.dao.Ilr
  ElementDAOJDBC.updateElement(IlrElementDAOJDBC.java:8254)
   at i
  log.rules.teamserver.ejb.service.dao.IlrElementDAOJDBC.updateAgg
  regateElement(IlrElementDAOJDBC.java:8148)
   at ilog.rules.teams
  erver.ejb.service.IlrSessionFacadeImpl.updateElementDetails(IlrS
  essionFacadeImpl.java:2921)
   at ilog.rules.teamserver.ejb.servi
  ce.IlrSessionFacadeImpl.commitAggregatedElementDetails(IlrSessio
  nFacadeImpl.java:751)
   at ilog.rules.teamserver.ejb.service.Ilr
  SessionFacadeImpl.commit(IlrSessionFacadeImpl.java:1510)
   at ilo
  g.rules.teamserver.ejb.service.IlrSessionFacadeImpl.commit(IlrSe
  ssionFacadeImpl.java:1039)
   at
  sun.reflect.GeneratedMethodAccessor190.invoke(Unknown Source)
  
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
  hodAccessorImpl.java:55)
   at
  java.lang.reflect.Method.invoke(Method.java:508)
   at ilog.rules.
  teamserver.transaction.IlrTransactionalInvocationHandler.invoke(
  IlrTransactionalInvocationHandler.java:107)
   at
  com.sun.proxy.$Proxy361.commit(Unknown Source)
  

Local fix

• To avoid this problem, either (re)create the deployment
  configuration using the Business console or in the main project
  when using Rule Designer.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users creating deployment configurations in subprojects from *
  * rule designer.                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * This problem affects all versions at least since 8.9.2 with  *
  * two different symptoms depending on the version:             *
  * 1) either the error message "There is already a baseline for *
  * which the property 'name' is '<suffix><timestamp>' in        *
  * project '<the dependent project>' within decision service    *
  * '<the Decision Service>'" is displayed and the deployment    *
  * continues endlessly,                                         *
  *                                                              *
  * 2) or the deployment fails and the exception below is        *
  * displayed in the report:                                     *
  * ilog.rules.teamserver.model.IlrInvalidElementException:      *
  * There is already an item for which the property 'name' is    *
  * '<suffix><timestamp>'                                        *
  *   at                                                         *
  * ilog.rules.teamserver.ejb.service.dao.IlrElementDAOJDBC.chec *
  * kElementBeforeCommit(IlrElementDAOJDBC.java:6434)            *
  *   at                                                         *
  * ilog.rules.teamserver.ejb.service.dao.IlrElementDAOJDBC.upda *
  * teElement(IlrElementDAOJDBC.java:8254)                       *
  *   at                                                         *
  * ilog.rules.teamserver.ejb.service.dao.IlrElementDAOJDBC.upda *
  * teAggregateElement(IlrElementDAOJDBC.java:8148)              *
  *   at                                                         *
  * ilog.rules.teamserver.ejb.service.IlrSessionFacadeImpl.updat *
  * eElementDetails(IlrSessionFacadeImpl.java:2921)              *
  *   at                                                         *
  * ilog.rules.teamserver.ejb.service.IlrSessionFacadeImpl.commi *
  * tAggregatedElementDetails(IlrSessionFacadeImpl.java:751)     *
  *   at                                                         *
  * ilog.rules.teamserver.ejb.service.IlrSessionFacadeImpl.commi *
  * t(IlrSessionFacadeImpl.java:1510)                            *
  *   at                                                         *
  * ilog.rules.teamserver.ejb.service.IlrSessionFacadeImpl.commi *
  * t(IlrSessionFacadeImpl.java:1039)                            *
  *   at sun.reflect.GeneratedMethodAccessor190.invoke(Unknown   *
  * Source)                                                      *
  *   at                                                         *
  * sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe *
  * thodAccessorImpl.java:55)                                    *
  *   at java.lang.reflect.Method.invoke(Method.java:508)        *
  *   at                                                         *
  * ilog.rules.teamserver.transaction.IlrTransactionalInvocation *
  * Handler.invoke(IlrTransactionalInvocationHandler.java:107)   *
  *   at com.sun.proxy.$Proxy361.commit(Unknown Source)          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The code is fixed on Decision Center.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WS DECISION CTR

• Fixed component ID

  5725B6900

Applicable component levels

• R8A0 PSY

     UP