Content

Environment: Windows 2008 R2

Sympton:

The following error occurs on the Process Simulator Designer applet:

java.lang.Exception: some long string ....
Trace message truncated for length over 10k
at filenet.sim.appserver.VWSIMSPOAPUtils.invoke(VWSIMSOAPUtils.java:183)

at filenet.sim.appserver.VWSIMCommand.startSimulation(VWSIMCommand.java:66)

at filenet.sim.api.VWSIMSimulation.start(VWSIMSimulation.java:388)

....

When fnlog4j.properties are deployed, they provide following additional information.

A. Snippet of fnlog4j output from WorkplaceXT

2012/02/20 11:10:28 [WebContainer : 9] DEBUG filenet.sim.appserver VWSIMSOAPService startSimulation orig. user=username
...
2012/02/20 11:10:28 [WebContainer : 9] DEBUG filenet.sim.appserver VWSIMSOAPService newScenario ENTER

2012/02/20 11:10:28 [WebContainer : 9] INFO filenet.sim.appserver Sample Simulation

2012/02/20 11:10:28 [WebContainer : 9] FATAL filenet.sim.appserver Got: simulator.util.VWSIMException, msg=simulator.core.SimException: Error retrieving exposed fields.

2012/02/20 11:10:28 [WebContainer : 9] DEBUG filenet.sim.soap invoke0startSimulation:THROWING

[SOAPException: faultCode=SOAP-ENV:Server; msg=rO0A...(very long string)...zg==]]

at filenet.sim.appserver.VWSIMSOAPServiceProvider.invoke(VWSIMSOAPServiceProvider.java:159)

at filenet.sim.appserver.VWSIMSOAPServiceProvider.invoke(VWSIMSOAPServiceProvider.java:104)

at filenet.sim.appserver.VWSIMServlet.doPost(VWSIMServlet.java:359)
...

B. Snippet of fnlog4j output from the Process Simulator server.

2012/02/20 11:10:29 [RMI TCP Connection(5713)-###.###.###.###] DEBUG simulator FileNETOptions <init> lifespan = 7200000.0
...

2012/02/20 11:10:29 [RMI TCP Connection(5713)-###.###.###.###] DEBUG filenet.sim.api VWSIMXMLOptions getRealPsServer:rmi://###.###.###.###:32771/WorkflowSimulator ###.###.###.###:32771

2012/02/20 11:10:29 [RMI TCP Connection(5713)-###.###.###.###] DEBUG simulator FileNETOptions setOptions:username::Sample Simulation::1329757829511 name=username
...

2012/02/20 11:10:29 [RMI TCP Connection(5713)-###.###.###.###] DEBUG simulator FileNETOptions setOptions:username::Sample Simulation::1329757829511 docId=3:3:{GUID}:{GUID}:{GUID}, lifespan=7200000.0, webApp=WORKPLACE, servletUrl=http://xtservername:9081/WorkplaceXT/P8BPMWSBroker/, psServerUrl=10.66.12.138:32771, psSimServletUrl =
<link to xtservername:9081/WorkplaceXT/P8BPMWSBroker/pssim/>
...

2012/02/20 11:10:29 [RMI TCP Connection(5713)-###.###.###.###] DEBUG simulator Scenario startPublishing:username::Sample Simulation::1329757829511 ENTER

2012/02/20 11:10:29 [RMI TCP Connection(5713)-###.###.###.###] DEBUG simulator Scenario startPublishing:username::Sample Simulation::1329757829511 Starting publisher..

2012/02/20 11:10:29 [RMI TCP Connection(5713)-###.###.###.###] DEBUG simulator.publisher DBExposedFIelds fetchFields(true) ENTER

2012/02/20 11:10:29 [RMI TCP Connection(5713)-###.###.###.###] DEBUG simulator DBConnection getDBConnection(true) jdbc:sqlserver://dbservername;port=1433;User=sa;DatabaseName=CADB

2012/02/20 11:10:29 [RMI TCP Connection(5713)-###.###.###.###] DEBUG simulator.publisher DBExposedFIelds fetchFields(true) EXIT

2012/02/20 11:10:29 [RMI TCP Connection(5713)-###.###.###.###] DEBUG simulator Scenario start:username::Sample Simulation::1329757829511 EXIT

Cause:

Process Simulator can not connect to the Case Analyzer database if an incorrect database user name and password are used.

On Windows 2008, you must start the Process Simulator Process Task Manager as the Administrator.

If you do not start the Process Simulator Process Task Manager as Administrator, the values are stored in an incorrect location:

C:\Program Files(x86)\ibm\FileNet\ProcessSimulator\cvsim\properties.txt.

When you start the Process Simulator Process Task Manager as the Administrator, the values are stored in the correct location in the Windows user temp directory.

2012/02/20 11:10:29 [RMI TCP Connection(5713)-10.66.12.135] DEBUG simulator.publisher DBExposedFIelds fetchFields(true) ENTER
2012/02/20 11:10:29 [RMI TCP Connection(5713)-10.66.12.135] DEBUG simulator DBConnection getDBConnection(true) jdbc:sqlserver://ecmdevdbv1;port=1433;User=sa;DatabaseName=CADB

Diagnosing the problem:

Enable fnlog4j logging on both the Workplace XT server and on the Process Simulator server.

A. Deploy fnlog4j.properties file WorkplaceXT

1. Copy the fnlog4j.properties.sample from the Process Engine server C:\Program Files (x86)\ibm\FileNet\ProcessEngine\data directory to the WebSphere application server that is hosting WorkplaceXT under
   WebSphere_directory\AppServer\java\jre\lib
2. Rename the file from fnlog4j.properties.sample to fnlog4j.properties
3. Use a text editor such as Notepad to edit the file and change the following lines.

From:
#log4j.debug=true
#log4j.rootLogger=ERROR, CON, TXT

To:
log4j.debug=true
log4j.rootLogger=DEBUG, CON, TXT

Also, verify that the log4j.logger.filenet.sim is set to DEBUG and not ERROR

# ---------------------- filenet.sim.* loggers -------------------

log4j.logger.filenet.sim=DEBUG, CON, TXT

# ----------------------------------------------------------------

5. Change the location to a valid path in the Workplace XT server. The location of the output file is specified in the following line.

For example:
log4j.appender.TXT.File=C:\\pe_XT.txt

6. Exit from the text editor and save the changes.

B. Deploy the fnlog4j.properties file on the Process Simulator server

1. Copy the fnlog4j.properties.sample from the Process Engine server
C:\Program Files (x86)\ibm\FileNet\ProcessEngine\data directory to:

C:\Program Files (x86)\ibm\FileNet\ProcessSimulator\cvsim\java\jre\lib

2. Rename the file fnlog4j.properties.sample to fnlog4j.properties

3. Use a text editor such as Notepad to edit the file and change the following
lines.

From:
#log4j.debug=true
#log4j.rootLogger=ERROR, CON, TXT

To:
log4j.debug=true
log4j.rootLogger=DEBUG, CON, TXT

5. The location of the output file is specified in the following line. Change
the location to a valid path on the Process Simulator server

For example:
log4j.appender.TXT.File=C:\\pe_PS.txt

6. Exit from the text editor and save the changes.

C. Test the JDBC connection from Process Simulator server to the Case Analyzer database.

Use the sample code provided by Microsoft in the article, "HOW TO: Get Started with Microsoft JDBC" on the support.microsoft.com website. To use the sample and view the sample output, complete the following steps:

1. Use the sample code to create a file named Connect.class

2. On the Process Simulator server, copy the attached Connect.class file to:

C:\Program Files (x86)\ibm\FileNet\ProcessSimulator\cvsim

3. Open a DOS prompt to:

cd C:\Program Files (x86)\ibm\FileNet\ProcessSimulator\cvsim

4. Within the C:\Program Files (x86)\ibm\FileNet\ProcessSimulator\cvsim folder, run the following command:

"C:\Program Files (x86)\ibm\FileNet\ProcessSimulator\cvsim\java\jre\bin\java" -cp .;sqljdbc4.jar
Connect CADBServerName PortNumber CADBName user password

Replace the CADBServerName PortNumber CADBName user password values with the ones on your environment.

For example:

"C:\Program Files (x86)\ibm\FileNet\ProcessSimulator\cvsim\java\jre\bin\java" -cp .;sqljdbc4.jar Connect ecmdemo1 1433 CADB sa filenet

Example output:

Connection Successful!

Driver Information


Driver Name: Microsoft SQL Server JDBC Driver 3.0
Driver Version: 3.0.1301.101

Database Information

Database Name: Microsoft SQL Server
Database Version: 10.50.1600

Avalilable Catalogs

catalog: CADB
catalog: master
catalog: model
catalog: msdb
catalog: tempdb

Resolving the problem:

1. Select Start > Programs > IBM FileNet P8 Platform > Process Simulator > Right-click Process Task Manager and Run As Administrator.
2. Select Process Simulator from the node on the left panel and click Stop.
3. Select the Case Analyzer tab and re-enter values for the Production or Simulation tab, making sure to re-enter the correct user name and password to connect to the Case Analyzer database.
4. Click Apply to save changes.
5. Start Process Simulator.