[rm-users] Care to share some details of your implementation?

[Tony Griffin]

We're an ASP and are running Brio.Portal v6.0 along with SQR v6.1 in our
production environment, integrated in our web-enabled application.  The
publishing and rendering of SQR jobs is relatively painless.  The output from
the SQR jobs is HTML and optionally PDF, CSV, etc.  In our case the client
doesn't interact directly with (what is now called) WebClient.  And even if they
did, you can certainly make it user-friendly by customizing portal's template
files.

Are you using ReportMart or Brio.Portal?  If it is ReportMart, there have been
at least two major releases of Brio.Portal since ReportMart was bought from
Sqribe in 1999.  I'm not sure if PeopleSoft is bundled with Brio.Portal, but I
don't see any reason why it couldn't be.

Tony Griffin
Performaworks, Inc.

-----Original Message-----
From: rm-users-admin@sqrug.com [mailto:rm-users-admin@sqrug.com]On
Behalf Of Simon Paul
Sent: Thursday, January 18, 2001 2:04 PM
To: 'rm-users@sqrug.com'
Subject: [rm-users] Care to share some details of your implementation?


Hello to all. I am new to this list and I am looking forward to sharing and
learning with you all.

Thanks to my big mouth I have somewhat "inherited" someone else's Brio
implementation. The way we use Brio is a little unusual (brief explanation
below) and a number issues made me wonder why Brio was implemented this way.
Little issues cause major headache and hardcoding bites us in the A$$
everyday. Is this really what a typical Reportmart install is like? It seems
too wacky to be the best way to do it, so I am hoping some of you will agree
to share to overviews of your implementation and perhaps we could all
benefit from the knowledge.

Here's our overview (what I know so far - very limited).

We are live with PeopleSoft version 7.5 and our business (as far as Brio
technology is concerned) is somewhat alike to an ASP where multiple clients
of ours would like to be able to see their PeopleSoft reports over the web.
We run PS reports to Brio (as files on the server with a particular naming
convention) and these reports are moved to a directory and picked up by
Reportmart. Once the Reportmart has "digested" the report a client can log
in to "HR Passport" a web front end which (amongst other things) imposes
security giving access to only that client's data. The Reportmart reports
appear as links which allow the user to look at lis files (yuk), txt files
(on those reports that are coded to produce txt flat files), SPF files
(better but unreliable) and possible PDF files (these would be the best but
don't always work thanks to crappy programming standards employed in the
past).

Ok... adding a new report is painful. Adding a new client is painful.
Changing the report name is painful. Running the report twice for the same
data results in two links (confusing to the client and therefore painful to
me). Every change we make is a big deal. Security is rightfully a big deal.
It can't be the best way to do this stuff is it?

Any thoughts?

Simon


_______________________________________________
rm-users maillist  -  rm-users@sqrug.com
http://www.sqrug.com/mailman/listinfo/rm-users