Multiple ODBC data sources on LBI server

Hi Nick,

We have a similar situation, and needed four DSNs for four different data areas: version 8 test and prod, and version 9 test and prod. The LBI server administrator created them as four system DSNs on the LBI server.

When writing CRs, we created system DSNs with the exact same names on our development workstations and used those. In LBI, I created LBI datasources using the DSNs created by the sysadmin. When reports are published, you can select any of the LBI data sources to override the report's internal datasource, so we could point them at test or prod for either v8 or v9. I can send details on creating the LBI data sources if you like. We're on AS400.

Thanks for the info Mike. I'm pretty sure my issue is that the different system DSNs aren't on the LBI server, and the server admins are telling me that there can't be that many. I thought that was odd, so I'm glad to know someone has done it.

I've heard that using the datasource overrides in LBI don't always work, have you had any issues using them?

I think our LBI server is a Windows box, I'm not sure if that's the only platform in use. At any rate, Windows doens't have a practical limit to the number of system DSNs that can be created, and our sysadmin didn't balk at creating four. In fact, before they upgraded hardware, our provider was supporting multiple organizatins on the same box, each with multiple DSNs.

We initially had problems with data overrides. They have to be configured just so, and the published report needs to be based on a system DSN. Prior to using overrides, we had done all our development, not just CRs, using file DSNs, as they are easier to copy to a client machine.

Here's my notes on LBI datasource creation. This process was developed after talking with Lawson support. The main issue was that I was creating CRs based on file DSNs, changing to system DSNs worked. This is for the AS400 platform.

Data sources in LBI administration
Data sources can be created in LBI administration which can override the data source stored in the CR when it was created.

To create a data source, log in to LBI and click Report Administration to open the Reporting Services Administration form, then click Maintain Data Sources in the Server Administration section in the left margin menu to display data sources.

Click the New button at the top of the form to start the creation process. Fill in the fields on the first page:

NAME
This is the name that appears in the list of override data sources in a report’s Data Setting options. I used the same name as the DSN on the LBI server that will be used in the datasource, e.g. "Lawson9Prod". The sysadmin must provide the system DSN name.

DESCRIPTION
This appears in the Maintain Data Sources form, and provides administrators with a description of the data source. E.g.: "Lawson production data v9 (lawapp9dbl)"

TYPE
Select Generic ODBC connection.

USER,ROLES,GROUPS
IMPORTANT, if you do not select a group you’re in, you will not be able to see this data source after you save it!!!

Click on the people icon to get a dialog from which you must select [yourgroup]. James thinks that if all users don’t have access to this, they won’t be able to run the report with that source even if you configure it to do so.


DRILL AROUND SECTION
Leave these empty


Click next to move to the next page and fill in the fields:

DESCRIPTION
This value is taken from the previous page


DRILL AROUND SECTION
Leave these empty

DSN
This must the name of an existing system DSN on the LBI server.
E.g.: Lawson9Prod. The sysadmin must provide the system DSN name.


DATABASE TYPE
DB2

DATABASE
The data area to be accessed by this data source, e.g. LAWAPP9DBL

SCHEMA
"dbo" without the quotes. Must be in lower case.


USER NAME
[the Lawson user name for reporting]

PASSWORDS
[your password]