LANSA Commerce Edition troubleshooting guide

Date:Archived
Product/Release:LANSA Commerce Edition
Abstract:Some things to check if you experience a Commerce Edition problem
Submitted By:LANSA Technical Support

If you experience a problem while creating your B2B or B2C application using LANSA's Commerce Edition, there are some things that you should check before contacting LANSA Technical Support. 

Commerce Edition helps you to rapidly build an application. It has been extensively tested to ensure that it generates an application correctly based on the users input. However, in the unlikely event that some part of the application doesn't work perfectly or as expected, the most important thing to bear in mind is that there is probably a workaround to get it to work as you want. The workaround could be anything from manually compiling a function to reimporting the LW3CED save file. First point of call is to review the manual for any information.  Some specific issues and possible workarounds are listed below.

  1. Your generated function doesn't compile successfully.

    Go into the function editor and take option C to Full Function Check (FCC) and compile. If the FFC or compile fails, review the error message(s) and try to remedy the problem. For example, it may occur that a field defined in the function is also defined in the repository. In which case you can either rename one of the fields or comment out the field in the function (if the fields are the same length, type etc.) and send the function for compile again.

    If the function has an error on a line that says  - Fetch fields(*all) from_file(____)  Check to see if your files have more than 99 fields in them.  If they do then simply change the fetch to retrieve just the fields that you require.  

    If you don't understand why your function will not compile then you should send the RDML source to LANSA Technical Support.
     
  2. Your component doesn't build.

    Check to see if the component was defined in the components section of the LANSA HTML Editor (or the LANSA Web administrator if appropriate).  Should it not be there then define it as a page component.  Also check to see if the HTML page was created in the HTML Editor.  If it isn't then copy the skeleton of that component to create your own.
     
  3. Your file doesn't compile.

    Again, same as in 1, manually recompile the file. Review the error messages, try to rectify the problem and resubmit the file for compile. If you cannot resolve the problem, then send the error messages to LANSA Technical Support.
     
  4. If you seem to be missing various necessary pieces of Commerce Edition.

    Are there any missing images, etc?  This indicates that there was a problem with the import or you have imported the wrong file (see point 6).  View the job log of the import (import.log) and check for warning and fatal messages.  If there is not an obvious error, then send this job log to LANSA Technical Support.
     
  5. Problem with the Integrator.

    The Integrator co-ordinates the existing back end files with LANSA's files.  There can be authority issues when attempting to run the Integrator, so ensure that you are signed on with a high authority (eg.QSECOFR) or the profile of the security officer for that partition.

    Should you have problems whilst running the Integrator, you cannot run it again immediately. The file LW3CEDDB must be imported before you run the Integrator again.  This file resets the integrator.

    Alternatively, the incorrect name for one of the files could have been entered.
     
  6. Importing LW3CEDDB, LW3CEDTB, and LW3CEDTA - Which one?

    There are two imports used by the Commerce Edition tutorial. One LANSA import (LW3CEDTA) includes a completed Commerce Edition demonstration application. The second import (LW3CEDTB) includes sample files and data required to complete the tutorials.

    LW3CEDTB is an import that resets the training environment for the Commerce Edition tutorials.  When the tutorials from the Commerce Edition CD have been completed, LW3CEDDB is imported so that the tutorials can be used again.
     
  7. Yes, No or Prompt for Answers?

    When the BOTs (Business Objects) are run, they will ask the user a series of questions to enable LANSA to build the function.  Many of these questions are the same between templates (i.e. What is the name of your Login Page?) so LANSA has the facility to either... 1) Automatically use the answer if the question has been asked before.  2) Ask for the answer every time, or  3) Enter the answer in but still prompt on the screen.  It is recommended that the P (Prompt) be used.
     
  8. You don't have a Ship-to file.

    You require a ship-to file with your Commerce Edition Application.  If you do not have a shipping file, you should either create one or use the Shipping file in the demonstration system.
     
  9. One Commerce Edition application is allowed per partition.

    Each partition may only have Commerce Edition installed once.  If you have more than one application that uses Commerce Edition, then you must a use a separate partition for every application.
     
  10. Answered all questions correctly but the integrator fails to compile.

    If you have checked that all your answers are correct and the Integrator still fails, view the job log (import.log).  If there are no obvious errors then send LANSA Technical Support, the job log and the file LW3FRM04.
     
  11. Before you run the integrator.

    Make sure that the LW3* files have not had the integrator run over them already.  Make sure that if you have run the Integrator before, that you have re-imported the file LW3CEDDB. If in doubt, re-import first before running the Integrator again.