500 Error in DSP Applications

If you update your LSF core technology, and subsequently find that your SSO applications (such as LBI or MSCM) produce a 500 service error, you probably need to update your DSP install on the host server for the SSO application.  Please see our article archive for instructions on how to update and reconfigure DSP.

If you get a “NoClassFoundError”, you may need to add a new class path to your JVM properties in WebSphere.  Figure out which class is missing and add the path to the JVM properties, then restart your application server and check to see if the issue is resolved.

MSCM Scheduler Crash

MSCM uses a Quartz scheduler to bring transactions from Lawson into the MSCM database.  Sometimes on of these events will crash and cause the entire scheduler to crash.  If you notice that details are not making it into MSCM from Lawson, here are some troubleshooting steps:

  1. Check the mscm_server.log located at <WAS_HOME>\profiles\<appserver>\logs
  2. Search for the word “outbound” and start looking for error messages such as “AbortRecoveryException” around the outbound scheduler informational messages.
  3. If you see an aborted recovery, check the EVENT_HEADER and EVENT_DETAIL tables in your database for threads that may be hung (they might have a relatively old HH timestamp or create/last modified date)
  4. If you suspect any threads may be hung, one way to bypass them would be to se the RETRY_COUNT to 99 in the EVENT_HEADER and EVENT_DETAIL tables for that EVENT_HEADER_ID. Then restart MSCM and watch to see if your items start coming over into MSCM.

MSCM Data Migration

If you are upgrading MSCM and need to test against production data, you may want to have multiple testing passes.  This article will help you to refresh your MSCM database, even if the versions differ.  (The MSCM install procedure updates the database for you when an older version is found).

Uninstall MSCM

  1. Log into the server as Lawson (or as the install user)
  2. Open a command prompt as administrator
  3. Navigate to <installdir>/config
  4. Run the following commands
    1. uninstallmscm
    2. undeploymscm
    3. Verify services as prompted
  5. Verify that the MSCM application has been removed from WebSphere

Restore Database

  • Overwrite the destination database with the desired data set

Re-install MSCM

  1. Log into the server as Lawson (or as the install user)
  2. Open a command prompt as administrator
  3. Navigate to <installdir>/config
  4. Run the following commands
    1. webspheregraft
    2. installschedulertableprefix
    3. installmscm
    4. deploy
    5. Verify services as prompted
  5. Start the mscm application in WebSphere

How to Apply a Hotfix for MSCM

WFM Hot Fix – Deploy .ear file

To prepare for applying the Hot Fix

  1. Backup the appropriate databases
  2. Backup important application files (ex. lsfprod/law/system) app server:
    1. ssokeystore
    2. ssotruststore
    3. authen.dat
    4. install.cfg
  3. Backup Ldap
    1. Get the instance name (ex. lsfprod-389)
    2. At the command prompt, browse to C:\
    3. Type: dsdbutil enter
    4. Type: active instance lsfprod-389 enter
    5. Type: ifm enter
    6. Type: create full D:/lsfprod/TEMP/ldapbackup/20160428

How to Apply a Hotfix for MSCM_1


  1. Logon as an administrator WEBLOGIC server.
  2. Backup your current directory where the application is deployed (ex. workbrain_20160502)
  3. Since you backed up the current Weblogic deployment directory, create a directory with the original name (ex. workbrain)
  4. Open a command prompt and browse to the directory where the application is deployed
    ex. cd $WB_HOME/deployments/production/workbrain
  5. Copy the EAR File to deployment directory (ex. $WB_HOME/deployments/production/workbrain
  6. Expand the EAR file in the deployment directory, using the jar tool:
    jar xvf workbrain.ear
  7. Delete the EAR File
    rm workbrain.ear
  8. Create a directory named war
    mkdir war
  9. Move the workbrain.war file into the war directory:
    mv workbrain.war war
  10. Select the war directory and expand the war file:
    cd war
    jar xvf workbrain.war
  11. Delete the war file:
    rm workbrain.war
  12. Edit the application.xml file found in the deployment_directory/workbrain/META-INF
  13. Change the line from:
  14. For the process of deploying as non-root context, select the deployment_directory/workbrain/META-INF directory, edit the application.xml file, and modify for the application non-root context:

<module id=”WebModule_1066144042227″>
<module id=”WebModule_1066144042228″>

NOTE: Make sure that you copy over any custom .jar files. Compare your previously deployed directories (the directory you backed up in step 5) to the new deployment for any custom .jar files.

  1. In the Administration Console, select Deployments in the left panel, and click Install in the right panel.The Install Application Assistant – Locate deployment to install and prepare for deployment page is displayed.
  2. Select the folder where the application was exploded.
  3. Click Next The Install Application Assistant – Choose targeting style page is displayed.
  4. Leave the default Install this deployment as an application option selected.
  5. Click NextThe Install Application Assistant – Select deployment targets page is displayed.
  6. Select the managed server.
  7. Click Next. The Install Application Assistant – Optional Settings page is displayed.
  8. Select Copy this application onto every target for me.
  9. Click Next. The Install Application Assistant – Review your choices and click Finish page is displayed.
  10. Leave the default Yes, take me to the deployment’s configuration screen option selected.
  11. Click Finish. The Install Application Assistant – Settings for My App page is displayed.
  12. Confirm that all settings are correct.
  13. Click Save.
  14. Click Activate Changes in the left panel.
  15. Click Deployment in the left panel.
  16. In the right panel, select the deployed application check box.

The Start Application Assistant page is displayed


  1. Click Yes.Note:Before you start your deployment, make sure that your managed server is running (<domain_name>/Environment/Servers/<managed_server>/control).