JR49156: BLANK PAGE IN INTEGRETION SOLUTION CONSOLE ON DEPLOYMENT ENVIRONMENT PAGE AFTER MIGRATION FROM WPS 7 TO BPM 8.0

Download Version 8.0.1 Fix Pack 3 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• Blank page in Integretion Solution Console on Deployment
  Environment page after migration from WPS 7 to BPM 8.0.
  
  The log shows a NullPointerException with following stacktrace:
  
  
  [1/8/14 15:03:56:401 EET] 00000045 servlet       E
  com.ibm.ws.webcontainer.servlet.ServletWrapper service
  SRVE0068E: An
  exception was thrown by one of the service methods of the
  servlet
  [action] in application [isclite]. Exception created :
  [java.lang.NullPointerException
   at
  com.ibm.wbiserver.db.forms.impl.DbProviderFormImpl.getImplementa
  tionType
  (DbProviderFormImpl.java:207)
   at
  com.ibm.wbiserver.db.forms.impl.FactoryHelper.updateProviderDbTy
  pe(Facto
  ryHelper.java:137)
   at
  com.ibm.wbiserver.nd.topology.forms.WBIDataSourceHelper.create(W
  BIDataSo
  urceHelper.java:376)
   at
  com.ibm.wbiserver.nd.topology.forms.WBIDataSourceHelper.create(W
  BIDataSo
  urceHelper.java:341)
   at
  com.ibm.wbiserver.nd.topology.forms.WBIDataSourceHelper.getAllDa
  taSrcs(W
  BIDataSourceHelper.java:326)
   at
  com.ibm.ws.console.wbi.dbconfig.DBCDataSourceRTHelper.hasDatasou
  rceCreat
  eTableInstructions(DBCDataSourceRTHelper.java:1139)
   at
  com.ibm.ws.console.wbi.ndtopology.config.TopologyConfigDetailCon
  troller.
  perform(TopologyConfigDetailController.java:90)
   at
  org.apache.struts.tiles.TilesRequestProcessor.processTilesDefini
  tion(Unk
  nown Source)
   at
  org.apache.struts.tiles.TilesRequestProcessor.processForwardConf
  ig(Unkno
  wn Source)
   at org.apache.struts.action.RequestProcessor.process(Unknown
  Source)
   at org.apache.struts.action.ActionServlet.process(Unknown
  Source)
   at org.apache.struts.action.ActionServlet.doGet(Unknown Source)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
   at
  com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
  apper.ja
  va:1230)
   at
  com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
  vletWrap
  per.java:775)
   at
  com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
  vletWrap
  per.java:457)
   at
  com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest
  (Servlet
  WrapperImpl.java:178)
   at
  com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(We
  bAppFilt
  erChain.java:136)
   at
  com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp
  FilterCh
  ain.java:97)
   at
  com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssista
  nce(WSCU
  rlFilter.java:950)
   at
  com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringTask
  State(WS
  CUrlFilter.java:499)
   at
  com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter(WSCUrlFilt
  er.java:
  320)
   at
  com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(Fi
  lterInst
  anceWrapper.java:195)
   at
  com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp
  FilterCh
  ain.java:91)
   at
  com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebA
  ppFilter
  Manager.java:928)
   at
  com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters
  (WebAppF
  ilterManager.java:1025)
   at
  com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:
  3763)
   at
  com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.j
  ava:304)
   at
  com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.
  java:975
  )
   at
  com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContai
  ner.java
  :1662)
   at
  com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLin
  k.java:1
  95)
   at
  com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscr
  iminatio
  n(HttpInboundLink.java:453)
   at
  com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRe
  quest(Ht
  tpInboundLink.java:515)
   at
  com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequ
  est(Http
  InboundLink.java:306)
   at
  com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complet
  e(HttpIC
  LReadCallback.java:83)
   at
  com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadComplet
  edCallba
  ck.complete(SSLReadServiceContext.java:1784)
   at
  com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureComp
  leted(Ai
  oReadCompletionListener.java:166)
   at
  com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyn
  cFuture.
  java:217)
   at
  com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncC
  hannelFu
  ture.java:161)
   at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
   at
  com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
   at
  com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHand
  ler.java
  :775)
   at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
   at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1691)
  ]
  

Local fix

• 1.Stop whole environment
  2. Navigate to
  <Dmgr_profile>/config/cells/<cell_name>/wbi-topologies.xml
  3. Modify  the "databaseType" attribute in all <provider>
  elements from
  "DB2_UNIVERSAL"
  to be "DB2_DATASERVER" like
  
  <provider xmi:id="WBIDBProvider_1297261191072"
  scope="Cell=Cell02"
  databaseType="DB2_DATASERVER" providerType="DB2 Universal JDBC
  Driver
  Provider" implementationType="XA data source"
   dbcomponent="WBI_BPCEventCollector"/>
  
  4.Start environment and try again.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM Business Process Manager Advanced       *
  ****************************************************************
  * PROBLEM DESCRIPTION: The problem occurred because the value  *
  *                      of the databaseType attribute for IBM   *
  *                      DB2 in the                              *
  *                      <Dmgr_Profile>/config/cells/<cell_name> *
  *                      /wbi-topologies.xml file is still       *
  *                      DB2_UNIVERSAL. It must be updated to    *
  *                      DB2_DATASERVER.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  After you migrate a profile from IBM WebSphere Process Server
  V7.0.0.x to IBM Business Process Manager (BPM) V8.0.1.1, log in
  to the administrative console, go to Servers >
  Deployment Environment, and click the deployment environment
  name on the left panel, you see that the linked page is blank.
  

Problem conclusion

• A fix for IBM BPM V8.0.1.1 and V8.0.1.2 is available that
  resolves the blank Deployment En-vironment page in the
  administrative console because the value of the databaseType
  attribute for DB2 in the
  <Dmgr_Profile>/config/cells/<cell_name>/wbi-topologies.xml file
  is changed to DB2_DATASERVER during the migration process. With
  the fix installed, the Deployment Envi-ronment page correctly
  displays with deployment environment configuration information.
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR49156:
  1. Select IBM Business Process Manager with your edition
  from the product selector, the installed version to the fix pack
  level, and your platform, and then click Continue.
  2. Select APAR or SPR, enter JR49156, and click Continue.
  When you download fix packages, ensure that you also download
  the readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  

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

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R800 PSY

     UP