VisualJVM and WebSphere

1) On the admin console (Click on Servers->Server types->WebSphere application servers->server1->Process definition->Java Virtual Machine), add the following line into the field of
Generic JVM Argument (note that the first system property is equal to
nothing and no equal sign for the second system property):

2) Add or uncomment the following three lines in file /opt/IBM/ WebSphere/AppServer/java/jre/lib/management/ (or / lib/management/

3) Connect to JMX

File -> Add JMX Connection
URL: <IP>:<JMX Remote Port>
Leave a comment

Posted by on April 25, 2013 in WebSphere


How to switch Case Analyzer to point to another Content Engine/Process Engine?

If you have multiple Content Engines/Process Engines but only one Case Analyzer and want it to point to a specific  Content Engine/Process Engine at some point, here are steps that could archive that goal

  1. Follow these steps to reinitialize Case Analyzer database
  2. Make sure Case Analyzer is stopped. If not STOP it.
  3. Clean up shared folder. You should be able to find it from PTM -> General tab -> Temp Directory (UNC)
  4. Update Content Engine URI, Service Username and Service Password under General Tab
  5. Update Process Engine database information under Process Engine Tab -> Process Engine Database’
  6. Refresh event logs in Event Logs tab
  7. Restart Process Task Manager
  8. Start Case Analyzer
  9. Observe the published event in Status Tab. Process Cubes

There are several OOTB report which come along with Case Analyzer Client. They can be used to verify result.

I was able to proceed this successfully. Good luck.

Leave a comment

Posted by on June 6, 2012 in FileNet


How to reinitialize FileNet Process Analyzer/Case Analyzer database?

I had run into the situation that the Process Analyzer or Case Analyzer could not synchronize Process Engine events properly. So I had to reset Case Analyzer database.

Here is very simple step to archive that on Case Analyzer (FileNet 5.1)

  1. Stop Case Analyzer
  2. Stop Process Task Manager on Case Analyzer environment
  3. Go to Case Analyzer Engine folder which is Case Analyzer installation folder
  4. Go to “jpa” folder
  5. Execute “SetupDB” script
  6. Done. It will drop existing database and recreate properly
1 Comment

Posted by on June 6, 2012 in FileNet



See this

Leave a comment

Posted by on April 17, 2011 in Uncategorized


BPMN Modeling Tool

See this link

Leave a comment

Posted by on April 8, 2011 in Uncategorized


About How to create a WSDL-first SOAP client in Java with CXF and Maven

This is a great post from Logic Sector Blog

* CDney weather service (for testing purposes)

Leave a comment

Posted by on March 31, 2011 in Java, Software Development, Webservice


How to setup messaging with Gmail SMTP

This post is generated from IBM website


How do I setup and use the Gmail SMTP server for WebSphere Commerce outbound e-mail messaging?


In general, the configuration depends on the SMTP server and as per the documentation of “Configuration of transport services used for a message” for the “E-mail adapter”, where:

Host: Specify the fully qualified hostname or IP address of the SMTP server used to send the message.
Port: The SMTP port used to send the message. (In most systems this is 25)

Furthermore, initially after setting messaging with Gmail SMTP, you might receive SSL HANDSHAKE FAILURE errors resembling the following snippet:

[8/13/10 14:00:54:583 EDT] 00000032 WSX509TrustMa E CWPKI0022E: SSL HANDSHAKE FAILURE: A signer with SubjectDN “, O=Google Inc, L=Mountain View, ST=California, C=US” was sent from target host:port “null:null”. The signer may need to be added to local trust store
“C:/IBM/WebSphere/AppServer/profiles/demo/config/cells/WC_demo_cell/nodes/WC_demo_node/trust.p12” located in SSL configuration alias “NodeDefaultSSLSettings” loaded from SSL configuration file “security.xml”. The extended error message from the SSL handshake exception is:
“PKIX path building failed: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: The certificate issued by OU=Equifax Secure Certificate Authority, O=Equifax, C=US is not trusted; internal cause is: Certificate chaining error”.


Using the WebSphere Commerce Administration console, you can setup the e-mail messaging Transport to use the following configuration settings for the SMTP server as per Gmail documentation:
Port: 465 to use TCP (SSL)

In case of SSL HANDSHAKE FAILURE, use the WebSphere Application Server Administration console to resolve the CWPKI0022E error and SSL HANDSHAKE FAILURE from the following location:

Security > SSL certificate and key management > Key stores and certificates > NodeDefaultTrustStore > Signer certificates > Retrieve from Port

Enter the Host and Port of the Gmail SMTP server. The wizard registers the certificate for you.


Posted by on February 25, 2011 in Java, WebSphere