Combining multiple Lawson reports into one with one line of code

, ,

You’re running an audit for Lawson security and are generating user, object, profile, security class/role reports left and right. It can be tiresome to review each individual one. With a simple batch command, you can save lots of time combining multiple Lawson reports that are in CSV format.

  1. Place all similarly generated reports into the same directory
  2. Open windows command line and change directory where Lawson CSV reports exist
  3. Type command: copy *.csv Lawson_reports_combined.csv
  4. Open your newly combined report and send away!

 

TIP: Reports may contain header info that will have to be removed via excel or text editor

Lawson Server File Maintenance

, ,

Between batch job files, temporary files, and core dumps, file storage can quickly get out of hand on your LSF server.  Here are some recommendations for cleaning up your server:

  1. Download a tool like windirstat to scan your directories and quickly find “problem” areas.
  2. Run a perl script to list out all the files recursively in a directory, and save to CSV. Here is a sample script that traverses the print directory and gets all the file stats within.  This will help you make a more informed decision on what to delete.
  3. Run the deljobhst command with the “r” and “c” parameters to delete completed jobs up to a specific date, including the print files. Make sure you supply a date that meets your company’s archive policy, and/or back up the directory to a separate location.  For more on the deljobhst command, click here.

Using Lawson jobinteg Command to Clean up Batch Jobs

, ,

The jobinteg command identifies orphaned jobs and allows you to delete them to clean up your job server.

The parameters for jobinteg are

  • v (Verbose) – prints the bad records
  • t (Terse) – prints totals only
  • P – validate parameters
  • U – print usage/syntax
  • d – deletes bad records

It is recommended that you run a jobinteg -v first to see how many (if any) jobs are orphaned or missing.  Then, run a jobinteg -d to delete the orphaned jobs.  Here is an example of the output:

IP Designer Series – Lawson Transaction Node

, ,

The Lawson Transaction Node can be used to add/edit/delete records in Lawson forms using AGS calls.

After you drag the node to your process, you can enter the AGS call manually, import it, or select “Build” in the properties to open a wizard.  In the Wizard, select all your system values.  When you are selecting the fields to update, also be sure to include all the key fields so that Lawson can find your record.  The field values can be hard-coded, or you can use variables.  Once you’re done building your call, click Finish, and the AGS call will be displayed in the properties window.

IP Designer Series – Resource Update Node

, ,

The Resource Update node is used to add/edit/delete resources in Lawson Security (Resource Manager).  This node is extremely useful for automating onboarding and offboarding.

In the properties of the node, click “Build” to build your resource update action.

Select your action and the type of object you are updating (People or Thing).  The selection criteria and the updated values can be IPA variables.

After you click “OK” on the build, you will be able to see what is being updated in the properties window.

LBI Ancestors Error

, ,

If your LBI instance is installed with Crystal Report Application Server 2011, you may see a recurring error in your LBI WebSphere logs, referencing “JSONOBject[“ancestors”] is not a JSONArray”.

This is a known defect in CRAS 2011, and will be resolved with an update to CRAS 2011 SP4.  You can safely ignore this error, or you can configure the logger to ignore it.  To configure the logger to ignore the error, add the following to the LBI_HOME\Reporting Services….\erswar-x.x.war\WEB-INF\classes\log4j.xml:

<!– Workaround to supress com.businessobjects.report.web.json.JSONException: JSONObject [“ancestors”] is not a JSONArray. error–>

<logger name=”com.businessobjects.report.web”>

<level value=”FATAL”/>

</logger>

 

Then, restart WebSphere and verify that the errors are no longer being logged.

 

ADFS Login Failed in Rich Client

, ,

If you are logging into Rich Client and getting a “login failed error”, check the security_authen.log file located on the Landmark server at LASYSDIR/security_authen.log.  If this file contains the error “ADFS login failed. The call to ADFS Login page was not successful”, you can configure your Rich Client installation to use an ADFS login.

These steps can be performed in the LPA Web App, or you can get to Rich Client using the command line utility.  To do this, log into the Landmark server as the Lawson user.  Open a Landmark command window, and type the command “canvas64 gen”.  This task is performed in the GEN data area.

In the search window, type “IRC” and select “IRC Install Specifications.”

The default specifications for Rich Client 64 should look something like this:

Modify the specifications to:

  1. -s
  2. $specfile.href.url$:$specfile.version$
  3. -iw
  4. -m
  5. $com.lawson.url.protocol$://$com.lawson.url.host$:$com.lawson.url.port$
  6. <your data area>
  7. -q
  8. $com.lawson.url.protocol$://$com.lawson.url.host$:$com.lawson.url.port$

Download Rich Client again, and you will be presented with a new style of login page:

Document Express error 52 – Bad file name or number

, ,

You may be running Document Express with Lawson and Citrix Storefront and encountering this error. Before you jump to conclusions that this issue is related to Lawson or Citrix security, check these steps below.

 

The user is likely experiencing this error when trying to import invoices into Document express.

  1. Make sure that all application related access is set in MHC.
  2. Verify the user has Active Directory access to the import routine folder on the server where the invoices are loaded in from Lawson.
  3. Lastly, verify the user has access to the import routine directly from Windows folder explorer. This path can be found in the import routine itself in document express.
  4. Copy the import routine path, paste it into Windows folder explorer to verify access.

Conclusion: When the user imports the invoice in doc express, it downloads the file locally and opens it. Verify both channels are open for the user.

Certificate Error When Loading Rich Client

, ,

If you launch Rich Client and get a certificate error (particularly after a new Landmark install or update), here are the steps to update your IRC certificate.

Here is a sample error message that you might receive before you are even presented with a login screen:

You can resolve this issue either in the LPA web administration tool, or you can log into your IPA server as the lawson user, open a Landmark command window, and type the command “canvas64 gen”.  These tasks are performed in the GEN data area.

In the search box, type “IRC” and select “IRC Trusted Certificates”

Go to Actions > Create

Add the certificate by file.  Browse to a previously exported certificate (Base 64 cer format) and click the save button.  The certificate details will be displayed if the certificate is valid.

Database File Space Issues That Manifest in IPA Errors

, ,

We recently noticed some strange behavior in IPA. All of our work units were stuck in “Ready” status, and the few Work Units that actually had errors indicated a java heap space issue. Some of the work units weren’t showing that a log was being created. We were also getting a generic error when uploading IPA processes.

It did seem like there was some kind of space or memory error. A reboot of the server didn’t address the issue. We were investigating and just happened to look at the command line window that opens up with IP Designer. That was the only place where saw a useful error message. It indicated that the database file had run out of space.

The resolution was to increase the “Maxsize” property on the IPA database file. In SQL Server, this is in the Database properties, Files tab.