Wednesday 4 September 2013

Snapshot install error

Wow, has it really been a year since my last blog post!

I have recently been having issues on my BPM 8.0.1.1 environment with some snapshot installs.
I had set up my Process server environment and initially set up a single Process server environment, using http ports and direct (not via a LB).  In this scenario everything worked as expected.

I then extended my Process server environment to a second node, and fronted it all with a webserver that was only enabled for https.

I followed the instructions in this useful infocenter document to ensure I was making the correct changes in the xml files:

http://pic.dhe.ibm.com/infocenter/dmndhelp/v8r0mx/index.jsp?topic=%2Fcom.ibm.wbpm.imuc.sbpm.doc%2Ftopics%2Ftconfig_custom_cluster_env.html&resultof%3D%2522%2577%2565%2562%2522%2520%2522%2573%2565%2572%2576%2565%2572%2522%2520

However, when I tried an install of the snapshot it failed and the SystemOut.log for Process center wasn't exactly bursting at the seams with useful information.

The only messages in the log were:
CWLLG0151I:  Standard hiring sample v801 Beginning login to remote server
CWLLG0152E:  Standard hiring sample v801 Remote login failed

I had a suspicion that despite setting <deploy-snapshot-using-https>true</deploy-snapshot-using-https>  in the Process server 10custom.xml that Process Center was still using http.  The reason I suspected this, was that in the ProcessCenter console, on the servers tab, when I clicked "Configure server" it tried to open a window to http://my-process-server:443/ProcessAdmin   i.e.   using an ssl port but on http.

A quick check in the LSW_SERVER table showed that the host name and port were correct  my-process-server:443  but there was no column in there that specified to use http or https.

So how could I prove what was happening?   I found the details of the trace that I need to set on the Process Center JVM:

com.ibm.bpm.fds.*=all:ProcessApplicationLifecycle=all:com.ibm.bpm.fds.repo.util.ContributionHelper=off:WLE.*=all

The trace output showed the following message:

com.lombardisoftware.server.ejb.repositoryservices.DeploytoServerSupport  deploySnapshot  Deploy Snapshot using :  http://

So it appears my suspicions were correct.  However, I had followed IBMs documents to the letter but PCenter was still not deploying using https.

One last thing to try was to update the 100custom.xml in Process Center so that now contained  <deploy-snapshot-using-https>true</deploy-snapshot-using-https>

A quick resynch of the node and restart of the JVMs and suddenly the deploy using https worked!

Whilst this works for me, the only downside I can see is that if you have Process Center talking to a mix of environments, they all need to be deployed to using http or all using https and doesn't appear as though you can have a mix

2 comments:

  1. It was very nice article and it is very useful to Cognos learners.We also provide Cub training software online training.

    ReplyDelete
  2. Hi,

    The bigger issue that we need to concern ourselves with is whether or not we have the need for an email database in order to become effective IBM Websphere Email Database in our email marketing

    ReplyDelete