Publishing in LBI a Crystal Report reading LTM Database via LAWSON OLEDB Connector

Hi ric9d,

The datasource type within the Crystal report needs to be identical to the Reporting Services datasource type if you want to be able to select it under the Data Settings screen.

I think thats where my problem lies. I have done Lawson OLEDB Dataources and had no problems with it. The only difference with this one is that it is from LTM. I have checked and double checked my (LTM) datasource and tested it too. I am thinking there should be something special I have to do since it is pointing to LTM database?

if you right click on your data source connection in the Crystal Report Designer and select "Set Datasource Location", in the upper pane expand your datasource, then expand "Properties", what value does it say for Provider?

Provider: Lawson.LawOLEDBC.4

And what is the Provider value for the Override Data Source that you have set up (Reporting Services Administration > Server Settings > Modify Data Sources > Edit associated data source)?

It is EXACTLY the same:--> Lawson.LawOLEDBC.4

And youre not seeing it in the drop down? If not then it seems youve got the correct setup in RS and Crystal and I would say it is an environmental setup/issue.

A few things to look at:

Issue Isolation
1. Create a Crystal Report with a data connection to several other data source types (MS SQL, Oracle, non-LTM Lawson, ODBC, etc) and see if you are able to set any Override Data Sources.
2. Dont use Override data source, enter username and password of your LTM report, do you get a looping login or does the report run
3. Be sure youve installed the verbose logger for Reporting Services (seach InfoXtreme for log4j.jar for details)

Diagnose
1. Confirm Lawson Object Services is installed on the server that the RAS engine is installed on
2. Check WebSphere log files for any error messages related to Reporting Services
3. Check RAS log files for errors

Resolutions
1. If you have recently upgraded the RAS server and you didnt copy all the JAR files into your RS root you may want to do this. The most simplistic way of doing this is reapplying or applying the latest patch to Reporting Services (it will copy the necessary files automatically)
2. Unistall/Reinstall Lawson Object Services on the RAS Server
3. Recreate your Override Data Source


Report back with any additional info.

Mat, Here are my responses:
Correct. I am not seeing it in the dropdown.

1. I have written and publish reports and Overridden Datasources (all non LTM) ane they all worked. (In prod)
2. I tried not using Override Data Source and yes, I get a looping login and report doesnt run.
3. Not sure about this.

Diagnose
1. Im assuming Lawson Object Services is installed since other reports are working.
2. Check WebSphere log files for any error messages related to Reporting Services --> will do
3. Check RAS log files for errors --> will do

Resolutions
1. If you have recently upgraded the RAS server and you didnt copy all the JAR files into your RS root you may want to do this. The most simplistic way of doing this is reapplying or applying the latest patch to Reporting Services (it will copy the necessary files automatically) -- No recent upgrade was done.
2. Unistall/Reinstall Lawson Object Services on the RAS Server --> will do
3. Recreate your Override Data Source -- will do


Report back with any additional info.

[quote]
Posted By ric9d on 01/21/2013 09:25 AM

1. I have written and publish reports and Overridden Datasources (all non LTM) ane they all worked. (In prod)
.....
Diagnose
1. Im assuming Lawson Object Services is installed since other reports are working.
[/quote]

Were these other reports using Lawson OLEDB data connections? If so perhaps just to isolate further, create a new report that connects to LTM but only takes one simple piece of data. Im not familiar with the LTM database but in the GL system I would use something like CUCODES which only has 2 records, typically. Put nothing else in the report, save, publish and see if the issue is replicated.

I just published a report (not very simple) and it is using LTM database and it worked fine.

The difference is: The DataSource I created (for this "not very simple" report) is Pointing to a different port. It is pointing to port 80 and the datasource obviously is showing in the drop down. I was able to run the report successfully.

The datasource having problems is using port 85. I also notice that in the Crystal Report itself, when running it standalone (not in lbi) the relationships and other objects are visible.

For the the datasource with port 80, I can only see the tables.

I opened up a ticket with Infor Xtreme Support. I am awaiting their response.

[quote]
Posted By ric9d on 01/21/2013 10:55 AM
The datasource having problems is using port 85. I also notice that in the Crystal Report itself, when running it standalone (not in lbi) the relationships and other objects are visible.

For the the datasource with port 80, I can only see the tables.
[/quote]

Excuse me if this is a stupid question but that statement made me think of something. By any chance, do you use the Database Expert to create your query for the non-working report? As in, did you select the tables and move them over to the right pane and then use the Crystal Linker to link them together? If so this would definitely be a problem as you would need to use the OLE DB Query Builder to create the query.

No. The report uses the pre-defined "relation" in LTM Database.

Once access to LTM database objects is granted (in crystal), The Lawson OLEDB query builder pops up and the objects (e.g. relations) are available.

Support got me the answer.

First if its LTM database: when creating a Lawson OLED DB datasource, you would need to pick "Lawson Landmark Connection" instead of "Lawson Data Connection".

Second. depending on your set up you would need to make sure you put the right "IOS Communication Protocol" which is either http or https. (This is the last box on the LBI DataSource Maintenance screen)

UPDATE:
I published 5 reports (using Lawson OLEDB reading LTM Database).
Only one of them is working properly in LBI. (They all run in Crystal Reports).
The only difference for the running report is that it is ONLY using 1 business object. The rest are using 2.
I have read about the "relationship" limitation of Lawson OLEDB, is this it? Does anybody know or have encountered the same? (The reports will post succesfully and will run prompting for credentials, then gives out user error)

I have posted the question to Infor Support, however they have not responded yet. I would be glad to know if anyone here had the same problem before.

Official Response from Support :

Crystal Reports published in LBI with 2 or more objects WILL NOT WORK.

There is a request to fix this bug.
KB 1374767 Defect#388899 JT-424847