Kbase 21155: RB. How to Deploy Report Builder in a Shared Windows Environment
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/06/2003 |
|
Status: Unverified
GOAL:
How to Deploy Report Builder in a Shared Windows Environment
FACT(s) (Environment):
Report Builder
CAUSE:
You might want users without a Progress installation on their local CPUs to be able to spawn Report Builder reports.
By designing some simple standards you can create an application that is accessible to any of the users on your LAN. This will also allow you to alter all reports from a central location.
Using the functionality provided by NetSetup and creating some rules for your application to follow, Report Builder reports can be spawned from any CPU on your LAN.
FIX:
Before beginning this process you need to create standards for how your applications will be designed.
First, and most important you will need to designate a fixed, specific drive letter where your Progress DLC and work folders will reside.
This Letter MUST be the same for all of your clients.
If they cannot be the same, then there must be a separate copy of all of the .p's, each with the proper drive letter for each user's instance incorporated into each one. Choose a drive letter low on the list of those available so that hard drives or CD-ROMs won't already populate this letter.
-- The Server
1) On the Server machine you must have Progress installed. The directory where Progress is installed should also contain your work directory.
2) Share this shell directory that contains these directories.
3) Start your Database in multi-user mode.
4) Add the work directory in the shell directory to your Propath.
-- The Client
1) Map the shell directory to the appropriate drive letter.
2) Run dlc\netsetup\setup.exe from this mapped drive.
3) Create a shortcut for prowin32.exe on your desktop.
4) In any directory on the Client create a tempwork folder.
5) Open the Properties Sheet for the shortcut.
6) In the target field after prowin32.exe, enter -p then the name of the Report Builder Engine calling program.
7) In the 'Start in' Fill-in, enter the path to the tempwork directory.
8) Click OK and you're done.
NOTE: When designing reports make sure you connect to the database using the -H, -S, and -N parameters.
NOTE: When designing the calling program make sure you reference the .PRL file relative to the path on the client.
NOTE: If you do not have a tempwork directory on the client, each user running this application will write over the previous users' tempfiles. The result is that you will see reports this user did not generate.
References to Written Documentation:
Report Builder Deployment Guide