Parallel Crystal Version 2.4 Installation Guide Revised August 1, 2000 ---------------------------------------------------------------------- Getting Started Minimum Recommmended System 1. Getting Started 1.1 Minimum Recommended System 1.2 Before Installing Parallel Crystal 2. Server Installation 2.1 Welcome 2.2 Installation Password 2.3 Software License Agreement 2.4 Registration Information 2.5 Choose Destination Location 2.6 Backup Replaced Files 2.7 Select Components 2.8 User Name and Password (for NT Service) 2.9 Program Manager Group 2.10 Start Installation 2.11 Post Installation Configuration 3. Client Installation 3.1 Java 3.2 C 3.3 C++ 3.4 Automation Server 4. Web Application Servers and Parallel Crystal 4.1 WebAS Support 5. Web Application Server Sample Configuration 5.1 SilverStream Sample Configuration 5.2 BEA WebLogic 4.5.1 Sample Configuration 5.3 Allaire Cold Fusion Sample Configuration 5.4 Active Server Pages Sample Configuration 5.5 Other Web Application Servers ---------------------------------------------------------------------- ---------------------------------------------------------------------- 1. Getting Started ---------------------------------------------------------------------- 1.1 Minimum Recommended System The minimum recommended hardware for a Parallel Crystal installation * A dual processor Pentium III server, with 256-512MB of RAM, and two or more high performance Ultra Wide SCSI hard drives. Note: Parallel Crystal will operate on a lesser machine for development purposes, but we do not recommend anything less for a production run environment. Actual requirements depend on report size and user load, which may be unique to each installation. The minimum recommended software for a Parallel Crystal installation * Windows NT version 4.0 with Service Pack 4 or 5 installed. * If you are planning to use Active Server Pages (ASP), you must have IIS 4.0 installed. Adobe Acrobat Reader You will need to download and install Adobe's free Acrobat Reader if you wish to view PDF generated by Parallel Crystal. Acrobat Reader can be installed as part of the Parallel Crystal installation program or it can be downloaded from Adobe's Web Site at http://www.adobe.com/. Java Development Kit (JDK) The Sun JDK is required to compile the sample Parallel Crystal Java applications at installation time. The installation currently requires one of the following JDK 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, and 1.2. (For users of SilverStream, the installation will use the Symantec compiler already on your machine). If you do not already have a JDK, use the following URL to download one from SUN http://java.sun.com/j2se/1.3/download-windows.html ---------------------------------------------------------------------- 1.2 Before Installing Parallel Crystal Some preparations need to be made before beginning the Parallel Crystal installation. This includes making decisions regarding the configuration of the system. NT User Name and Password Parallel Crystal requires a User Account to log itself as a Windows NT Service. The Parallel Crystal Installation program does allow installation as an NT Service. It defaults to the currently logged domain and user name for the installation as a service. The installer must provide the correct password. It is not recommended that the user account for the Parallel Crystal NT Service have administrator rights. While you need administrator rights to install software on a NT system, production servers should not use an administrative account to run Parallel Crystal. The account used for Parallel Crystal should have access to the directories where the report templates are located and to where the generated output will be located. The account will also need access to the system temporary folders. The installer will default to the currently logged in administrator (although this can be changed) for ease of setup for new users. The account for Parallel Crystal should be logged into the server before setting the service to use that account (to create the local registry information for the user to have access to the printer subsystem of the operating system). Data Object Reporting Data Object Reporting is available in Parallel Crystal. Some special installation steps are required to use this feature. Two Microsoft Components must be installed and a special DOR to RPT Utility. Installing MDAC and XML DOR reporting requires the installation of two Microsoft components. These components are installed with Internet Explorer version 5.0 if the dynamic HTML data binding option is selected. However, they may be installed with Internet Explorer version 4, Service Pack 1 or higher. For DOR with Internet Explorer 5, install * Internet Explorer 5.0 with the dynamic HTML data binding option For DOR with Internet Explorer 4, Service Pack 1 or higher, install * Microsoft Data Access Components 2.1 (Mdac_typ.exe) * Microsoft XML parser (xmlredist.exe) The installation program for each component is found in the Microsoft Components folder on the Parallel Crystal Installation CD. Note: Parallel Crystal Automation Server clients require these components to be installed on both the server and client machines. Java clients only require these components on the server machine. Installing the DOR to RPT Utility The DOR to RPT Utility should be installed on the machine that will be used to design DOR reports. This may be a different machine than the one used as a Client to run reports. This utility is installed using an automatic install program called DORReportUtility.exe. This program is placed into the \MobileApps\PCRE\DataObjectReporting folder during a Parallel Crystal installation. Determine which computer will be used to design DOR reports and copy the DORReportUtility.exe onto that machine. Then, run the DORReportUtility.exe install program and the utility will be automatically installed. DOR with Automation Server Parallel Crystal Automation Server clients have specific installation requirements for Data Object Reporting. * The DOR to RPT Utility may not be required if using the Parallel Crystal Automation Server. * Automation Server clients using DOR require the Microsoft components (Mdac and Xml) be installed on both the server and client. That means they should be installed on the web server for ASP or the actual client machine for clients accessing COM directly. * Automation Server clients using DOR require ADO 2.1 be installed on both the server and client. * ADO support requires that the Automation Server have write permission to the C:\Temp directory on the client machine. Note: For more information about creating and running Data Object Reports, consult the Parallel Crystal Developer's Manual. ---------------------------------------------------------------------- ---------------------------------------------------------------------- 2. Server Installation The Parallel Crystal Installation program is an automated Windows InstallShield file called Pcre.exe. The Installation program presents a series of dialog boxes that request input from the installer. This section describes each of the steps involved in completing a Parallel Crystal installation by detailing the information required for each dialog box. It is a good idea to read ahead and prepare for each step of the installation before beginning. The installation dialog boxes appear in the following order * Welcome * Installation Password * Software License Agreement dialog * User Registration Information * Choose Destination Location * Backup * Select Components * User Name and Password * Program Manager Group * Start Installation * Finish * Restart Computer * Post-installation Configuration ---------------------------------------------------------------------- 2.1 Welcome The Welcome dialog appears at the beginning of the installation. As with most installation programs, it is recommended that you exit all other applications before continuing. ---------------------------------------------------------------------- 2.2 Installation Password The Parallel Crystal installation program requires an installation password, or serial number to proceed. This password was sent to you with the Parallel Crystal CD or, in the case of a download, was sent via email. ---------------------------------------------------------------------- 2.3 Software License Agreement The Software License Agreement dialog box asks if you agree with the terms of the license for Parallel Crystal. For more information about the license agreement, visit our website, or contact your Dynalivery Sales Representative. ---------------------------------------------------------------------- 2.4 Registration Information This dialog box records the name and company name of the registered owner. If Parallel Crystal has already been installed on the system, the name and company name are displayed. ---------------------------------------------------------------------- 2.5 Choose Destination Location A default folder name and drive specification are provided. If you want to install Parallel Crystal in a folder or drive other than that specified, click the browse button and select the appropriate path. ---------------------------------------------------------------------- 2.6 Backup Replaced Files This feature makes a backup copy of all overwritten files in a specific directory. This dialog box also allows you to choose the folder name and drive specification for the backup files. The backup files may be manually restored at a later date. ---------------------------------------------------------------------- 2.7 Select Components Choose which components to be installed on the system. Some components may be installed on the same system, or different systems to provide increased performance. Information about installing each component is described in detail below. Report Server This option installs the server binaries for Parallel Crystal. The Report Server must be installed on a machine with Seagate Crystal Reports 7 Maintenance Release 1 or higher loaded to perform properly. Java Client This option installs all components necessary to set up Parallel Crystal access from any Java environment. This may be installed on the same machine as the Report Server or on a separate machine as needed. ActiveX Client This option installs all components necessary to set up Parallel Crystal access from any ActiveX environment. This may be installed on the same machine as the Report Server or on a separate machine as needed. C/C++ Client This option installs all header files and libraries necessary to set up Parallel Crystal access from a C or C++ environment. This may be installed on the same machine as the Report Server or on a separate machine as needed. Sample Reports This option installs several sample report (.rpt) files. These sample files are used by the Parallel Crystal demos and are useful when writing proof-of-concept applications. Web Demos and Samples This option installs several web application server demos as well as samples for each of the different client languages. This option requires the installation of Sample Reports for the demos/samples to operate correctly. However, there is no requirement for the Sample Reports if you simply want to look at the demo/sample code as examples of how to build your own application. Acrobat Reader 4.0 This option installs Adobe's PDF (Portable Document Format) Viewer, which is required to view Parallel Crystal help files presented in the PDF format. Note: Adobe freely distributes this viewer and updates are available from their website. Its inclusion here is simply as a convenience to Parallel Crystal customers. ---------------------------------------------------------------------- 2.8 User Name and Password (for NT Service) The Parallel Crystal Installation program allows installation as an NT Service. Parallel Crystal requires a User Account to log itself as a Windows NT Service. It defaults to the currently logged domain and user name for the installation as a service. The installer must provide the correct password. It is recommended that the user account for the Parallel Crystal NT Service have administrator rights. What this means is that an administrator user account should be created prior to running the Parallel Crystal Installation program. Then, the installer should log in with that account prior to running the Parallel Crystal Installation program. Note: Although the Parallel Crystal Server may be run as an NT Service, it does not automatically start as a service after installation. It is automatically established as a service, but it must be manually started as a service or run from the desktop. It may be set to start automatically in the Services Control Panel. ---------------------------------------------------------------------- 2.9 Program Manager Group The installation program automatically defaults to a program manager group called Parallel Crystal. If you want to put Parallel Crystal in a different a program manager group, select one from the list. ---------------------------------------------------------------------- 2.10 Start Installation The Start Installation dialog box is designed to give you one last chance to change installation parameters prior to the actual installation of Parallel Crystal. Choose Next to continue and the installation program begins copying files. ---------------------------------------------------------------------- 2.11 Post Installation Configuration Parallel Crystal installation requires the system to be restarted after the installation is complete. After the restart, your system should automatically start the Seagate Crystal Reports 7.1 installation program. Installing Seagate Crystal Reports 7.1 * The Seagate installation begins with a Welcome screen (click next and then the installer continues by displaying the license agreement. If you agree with the license, click yes. * The Seagate installer will then ask for the first name, last name and organization of the user. Enter the correct information and click next. The next dialog box includes the important installation options. * Choose Custom and specify the location where you want the files to reside (keep in mind that some files will still be copied to the system folders on your machine) and click next. * The next dialog box is the custom installation options screen. Select everything except the Web Server Setup and Workstation Setup options (the last two options are not used by Parallel Crystal) and click next. * In the Essbase Version dialog box choose Version 5 and click next. * In the Program Group selection box, choose the group where you want Parallel Crystal installed, and click next. The file copy will begin and Crystal Reports will be configured for the Parallel Crystal machine. You do not have to restart the machine after the Crystal Reports installation has completed. Install a PCRE Printer A PCRE printer profile must be installed for Parallel Crystal to work properly. To install a PCRE print driver manually 1. Add a printer to your system, by selecting Add Printer from >>Start >>Settings >>Printers. 2. Choose the HP Color LaserJet PS and select "print to file." 3. Name this printer "PCRE Printer." Note: The WindowsNT/2000 disks may be required to install this printer driver. Start Menu Shortcuts Parallel Crystal installs several shortcuts on your start menu. These shortcuts are provided to ease administration, aid in trouble- shooting and provide access to API references and sample files. Following are descriptions what all the links from the Start Menu actually do. Demos and Tutorials This shortcut starts the sample web page that is set up during a Parallel Crystal installation. This page has links to the Java Applets and Applications as well as the sample ASP pages showing VBScript and JScript. Java Client Application Command Prompt This shortcut takes you directly to the installed location of the Parallel Crystal Java Application clients. From this command prompt you can execute or examine the source code of the sample applications. Log File Viewer This shortcut starts a viewer, which allows you to check the log files generated by the Parallel Crystal Report Engine. This viewer is extremely useful in solving report generation problems. Dynalivery Homepage This shortcut connects you to the Dynalivery homepage, from which you can obtain the latest information concerning Parallel Crystal. Documentation This shortcut lists the online documentation provided with Parallel Crystal. Some of these documents are in HTML format and others are in Adobe PDF format. The online documentation for Parallel Crystal includes * Installation Guide - a copy of this document in PDF format * Release Notes - a listing of the new features, system requirements, bug fixes, interface changes, and know issues with the current version of Parallel Crystal. * Developer's Manual - a copy of the Parallel Crystal Developer's Manual in PDF format. This manual includes introductions to Parallel Crystal concepts and detailed information about developing in each Parallel Crystal client environment. * ActiveX API Quick Reference - ActiveX Automation Server API Quick Reference * C API Quick Reference - a set of web pages that include a description of the methods and properties of the PCRE Automation Server ANSI C Client API * C++ API Quick Reference - a set of web pages that include a description of the classes of the C++ Client API * Java API Quick Reference - a set of web pages that include a description of the classes, interfaces and exceptions in the Java Client API * API Reference Vol's 1-4 - Seagate's API reference for Crystal Reports Developers ---------------------------------------------------------------------- ---------------------------------------------------------------------- 3. Client Installation During a standard installation of Parallel Crystal, the sample Java/J++, ANSI C, C++, and ActiveX Automation Server client examples are all auto-configured for your server. When compiling your clients, the files you need to include are located in the following directories. (The paths indicated here assume a default installation.) * Java - \MobileApps\PCRE\Jars (make sure this directory is included in your classpath). * C/C++ - \MobileApps\PCRE\Cpp Client\Include (make sure this directory is imported into the project or in the include path, depending on the development environment). ---------------------------------------------------------------------- 3.1 Java Java API Quick Reference For the Java API Quick Reference please refer to the index.html file located in the MobileApps\PCRE\Docs\JavaAPIReference directory. Java Application Samples The directory MobileApps\PCRE\JavaApplications has several subdirectories that contain examples of applications, which can be created using the PCRE Java API. The sample applications are examples of how to use parts of the Parallel Crystal Java client. * The MASConcurrency application shows a multi-threaded client making two separate connections to a Parallel Crystal server. * MASFirstApplication is a simple example of how to generate a report with Parallel Crystal. It can be used as an aid in debugging problems with PCRE in other environments (across subnets, inside WAS, etc.). ---------------------------------------------------------------------- 3.2 C Parallel Crystal can use a flat C API. This API can be accessed from virtually any environment that supports C-style linkage, including Cobol and Smalltalk. The C API Quick Reference is installed by default in \MobileApps\PCRE\Docs\CAPIReference. ---------------------------------------------------------------------- 3.3 C++ C++ Client API Quick Reference For C++ API Quick Reference, please see the index.html file located in the MobileApps\PCRE\Docs\CppAPIReference directory. C/C++ Application Samples The C / C++ clients can communicate with a Parallel Crystal server across a network, enabling you to control, format, and print reports locally. If you chose to install the Sample Code, you may want to experiment with it. (If you have not installed it yet, you may at any time by re-running the installation program.) Within the MobileApps\PCRE\CppClient\Sample Code directory you will find some sample applications, which demonstrate the use of the C / C++ client. To use the sample applications it is first necessary to start a Parallel Crystal Server running on your server. The name or IP address of the server will be needed to run the applications. ---------------------------------------------------------------------- 3.4 Automation Server To view the Automation Server API Quick Reference see the index.html file in the MobileApps\PCRE\Docs\AutomationServer\HTMLReference directory. The list of supported calls is also located in this directory (ASSupportList.txt). Sample Code for Visual Basic The Parallel Crystal installation program includes some pre-built projects in the folder: \MobileApps\Pcre\Automation Server Samples\VisualBasic To create your own, remember to select menu item Project/References and select "CPemas1 1.0 type library" for inclusion in your project. Sample Code for Visual C++ The Parallel Crystal installation program includes a sample C++ program in the \MobileApps\Pcre\Automation Server Samples\C++5.0 folder. To build your own, create an "import" statement in your program of the form: #import "Path/cpemas1.dll" no_namespace high_property_prefixes("G","P","P) That is all that is required to gain access to the Automation server. Sample Code for Active Server Pages with VBScript The Parallel Crystal installation program includes sample VBScript applications in the \MobileApps\Pcre\Automation Server Samples\. To create your own, attach to the Automation server in your script by creating an application object. For Example dim PCREApp Set PCREApp = Server.CreateObject("MAS.PCREApplication.1") ---------------------------------------------------------------------- ---------------------------------------------------------------------- 4. Web Application Servers and Parallel Crystal Parallel Crystal supports interfaces to Web Application Server (WebAS) products through a layered CORBA interface. ---------------------------------------------------------------------- 4.1 WebAS Support Dynalivery tests Parallel Crystal with some of the leading WebAS software. Dynalivery has three levels of experience with testing these configurations. * Level 1 - Tested WebAS Configurations * Level 2 - Successful WebAS Configurations - Not Tested In-house * Level 3 - Unverified WebAS Configurations Note: Dynalivery recommends that WebAS developers utilize the set of Sample Applications, included with the Parallel Crystal installation, for initial verification of a configuration. Each Sample configuration is described in detail in the section entitled Web Application Server Sample Configuration Level 1 - Tested WebAS Configurations These WebAS configurations have been tested with Parallel Crystal at Dynalivery and we have had success integrating with them. We have the resources and expertise in-house to re-create these environments to assist in troubleshooting and technical support. * SilverStream 2.5x/3.0 on Windows NT 4/Windows 2000 * BEA WebLogic 4.5x/5.x on Windows NT 4/Windows 2000 * Active Server Pages on Windows NT 4/Windows 2000 * Cold Fusion 4.x on Windows NT 4/Windows 2000 Level 2 - Successful WebAS Configurations - Not Tested In-house Some Web Application Servers are known to work with Parallel Crystal, because of customer success, but have not been tested in-house by Dynalivery. This anecdotal evidence means that you can expect to be successful using Parallel Crystal with a particular configuration, but we may be less able to participate in troubleshooting and technical support. * Lotus Notes on Windows NT 4/Windows 2000 * NetDynamics on Windows NT 4/Windows 2000 * Versata (formerly Vision Jade) on Windows NT 4/Windows 2000 * IBM WebSphere on Windows NT 4/Windows 2000 * Tango2000 on Windows NT 4/Windows 2000 Level 3 - Unverified WebAS Configurations Web Application Servers not listed on this page have not been tested with Parallel Crystal in-house by Dynalivery. However, in many cases, Dynalivery assumes that a configuration should be functional, based on known facts about the Web Application Server. For example, assuming Sun's "write once, run anywhere" statement about Java is accurate, Parallel Crystal's Java Client should work on all platforms that have Java VMs, including some configurations not mentioned here. ---------------------------------------------------------------------- ---------------------------------------------------------------------- 5. Web Application Server Sample Configuration The Parallel Crystal installation includes sample code and report templates designed to assist a developer in configuring their environment. These samples may be used to verify the various components in a configuration are working together properly. The samples also provide examples of code integration known to work in a particular environment. Dynalivery recommends that WebAS developers utilize the set of Sample Applications, included with the Parallel Crystal installation, for initial verification of a configuration. Each Sample configuration is described in detail in the following sections. * SilverStream * BEA WebLogic * Allaire ColdFusion * Active Server Pages ---------------------------------------------------------------------- 5.1 SilverStream Sample Configuration The Parallel Crystal installation includes sample code designed to assist a developer when configuring Parallel Crystal in a SilverStream environment. This sample code helps verify that Parallel Crystal and SilverStream are working together properly, as well as providing a possible example of code integration. The sample code is located in the folder: \WebApplicationServerSamples\SilverStream within the Parallel Crystal folder (Default: C:\MobileApps\Pcre). There are two main steps to configuring the sample code * Setting the classpath(s) * Setting up the SilverStream Environment Setting the Classpath(s) The first step in configuring the SilverStream sample code for Parallel Crystal is to set up the classpath statement(s). The class paths tell SilverStream where to look for classes outside of the SilverStream environment. 1. Open the Windows Control Panel by selecting Control Panel from the Settings menu from the Start Menu. 2. In the control panel, double click the System icon. The System Properties window will open. 3. In the System Properties window, choose the Environment pane. System Variables are displayed. 4. Select the existing variable (such as CLASSPATH or AGCLASSPATH) so that the variable name and value appear in the two text boxes at the bottom of the window. * If the environment includes SilverStream 3.0 or higher, AGCLASSPATH should be set. * If the environment includes SilverStream 2.5 or lower, AGCLASSPATH and CLASSPATH need to be set. 5. Change the value to: #drive#:\#directory#\mobileapps\PCRE\jars\pcrejavaclient.jar #drive# is the letter of the drive where Parallel Crystal is installed #subdirectory# is the subdirectory (possibly none) where Parallel Crystal is installed. For example, if Parallel Crystal is installed on the C drive under the Reporting directory, the value would be: c:\Reporting\mobileapps\PCRE\jars\pcrejavaclient.jar or if installed on the root of the E drive (without a subdirectory), the value would be e:\mobileapps\PCRE\jars\pcrejavaclient.jar 6. Choose the Set button. The new classpath appear under the System Variables list. 7. Choose OK to save your changes and close the System Properties window. Setting up the SilverStream Environment Generally, there are three types of configurations for the sample code * Parallel Crystal with SilverStream Version 2.5 or lower and SQLAnywhere - If Sybase SQLAnywhere database is installed (comes with the SilverStream install); the two databases SSDemo.db and WineDemo2.db may be added to the SilverStream environment. * Parallel Crystal with SilverStream Version 2.5 or lower without SQLAnywhere - If SQLAnywhere is not installed; code may be pasted from the file MASFirstBusinessObject.txt into a SilverStream Business Object. * Parallel Crystal with SilverStream Version 3.0 or higher. SilverStream 3.0 and higher installs with Sybase Adaptive Server (formerly SQLAnywhere). If using Adaptive Server, the database Windemo3 may be added to the SilverStream environment. Sample with SilverStream 2.5 or Lower and SQLAnywhere The Parallel Crystal installation includes two SQLAnywhere databases, which contain sample code. * The SSDemo.db database contains two example business objects, a utility business object and several forms and pages used to run the example objects. * The WineDemo2.db database is the familiar Silver Creek Wine demo that ships with SilverStream, but we have added reporting capability to several sections of the demo to provide an example of how to integrate Parallel Crystal into a SilverStream application. The business objects included in the databases are * PCRESimple - This is a very simple business object, which shows the basics of connecting to a Parallel Crystal report server and running a report. * PCRE - This business object takes the basic functionality of PCRESimple and adds examples of additional API calls such as changing formulas and setting selection criteria. This business object also separates the code into different methods for the different functionality. Although this business object has more API examples than PCRESimple, there are many additional API's that may be used in the running of a report, depending on the functionality required. Please see the PCRE Java Client API Reference for more information. * PCREFileServlet - This business object is a utility object used by the other two for displaying the retrieved report file. In some respects, it acts as a mini web server. There are three steps to set up SilverStream with one of these databases * Create an ODBC data source * Add the database(s) to the SilverStream environment * Configure the demos (if necessary). Setting up the ODBC data source The instructions below describe configuration of the WineDemo2.db database. To set up an ODBC source for the SSDemo.db database, replace WineDemo2 with SSDemo. 1. Open the Windows Control Panel by selecting Control Panel from the Settings menu from the Start Menu. 2. In the control panel, double click the ODBC Data Sources icon. The ODBC Data Sources Administrator window will appear. 3. Choose the System DSN pane. The System Data Sources will appear. 4. Depending on how SilverStream was installed, you may already have a WineDemo2 data source set up. If WineDemo2 data source is present 5. Double click the WineDemo2 item. The SQL Anywhere ODBC Configuration window will appear. 6. Change Server Name under Connection Information to WineDemo2. 7. In the Database Startup section select Browse next to Database File and select the winedemo2.db file. This file will likely be located in the \mobileapps\PCRE\WebApplicationServerSamples\SilverStream directory on the drive which you installed Parallel Crystal. 8. Don't change any of the other fields and choose Ok. If WineDemo2 data source is not present 5. Choose the Add button. The Create New Data Source window appears. 6. Select Sybase SQL Anywhere 5.0 and choose Finish. The SQL Anywhere ODBC Configuration window will appear. 7. Change Data Source Name to WineDemo2. 8. Change Server Name under Connection Information to WineDemo2. 9. In the Database Startup section click Browse next to Database File and select the winedemo2.db file. This file will likely be located in the \mobileapps\PCRE\WebApplicationServerSamples\SilverStream folder on the drive which you installed Parallel Crystal. 10. Don't change any of the other fields and click Ok. 11. Click Ok on the ODBC Data Source Administrator window to accept the changes and to close the window. Adding the database to SilverStream 1. Open the SilverStream Designer. A list of one or more servers appears in the left hand pane. Double click on one of them and a list of databases installed on that server will display. 2. Click the Add Database icon at the top of the Designer window. This will open the Add Database window. 3. Enter either WineDemo2 or SSDemo for the Name of the Database. 4. Enter dba for the User name. 5. Enter sql for the Password. 6. The other items in the window will be set correctly by default. Click Finish. 7. You will notice that a new item has appeared on your task bar (Win 95/NT). Also the database you have just added should be in the list of available databases in the left hand pane. Configuring the Demos The demos, both in SSDemo and in WineDemo2 assume by default that the Parallel Crystal Report Engine and SilverStream Server are installed on the same machine. If this is the case, there are no configuration changes required. If this is not the case, there will be some minor configuration necessary. Configuring SSDemo PCRESimple - The form included to run PCRESimple doesn't allow the user to change the report server name. To change the report server name 1. Open the SilverStream Designer. There should be a list of one if not more servers in the left hand pane. Double click on one of them and a list of databases installed on that server will show. 2. Double click on the SSDemo database. This will cause a list of items such as Tables, Forms, Object, etc to show. 3. Click on Objects. In the right hand pane there might be a list of objects. There should be three items listed, one of which will be CrystalReportsDemo. 4. Double click the CrystalReportsDemo item. This will cause a sub list to show which will include PCRESimple. 5. Double click on PCRESimple. This will show the Business Object Designer with PCRESimple loaded. 6. The invoked method will be displayed in the code pane. Replace the line "reportServerName = evt.getServer().getName();" with "reportServerName = server.yourcompany.com;". So if the report server was on mach1.reporting.com, the line would read "reportServerName = mach1.reporting.com;". 7. Now click Save under the File menu. This will compile the class and save the changes. PCRE - The forms PCREAdvanced and PCRESeminar which both use PCRE have a Server tab which allows the user to specify use the default, or to set a report server name as well as other attributes. The default report server is the server on which SilverStream is installed. If this is not the case, then specify the server in the Server tab. Configuring WineDemo2 The Wine Demo executes a report by the push of a button, so there is no GUI component to allow the user to set the report server such as in the PCREAdvanced demo. To change the report server name 1. Open the SilverStream Designer. There should be a list of one if not more servers in the left hand pane. Double click on one of them and a list of databases installed on that server will show. 2. Double click on the WineDemo2 database. This will cause a list of items such as Tables, Forms, Object, etc to show. 3. Click on Objects. In the right hand pane there might be a list of objects. There should be three items listed, one of which will be CrystalReportsDemo. 4. Double click the CrystalReportsDemo item. This will cause a sub list to show which will include PCRE. 5. Double click on PCRE. This will show the Business Object Designer with PCRE loaded. 6. In the drop down box which is now displaying Invoked, select General. 7. Replace the line "String reportServerName;" with "String reportServerName = server.yourcompany.com;". So for instance if the report server was on mach1.reporting.com, the line would read "String reportServerName = mach1.reporting.com;" 8. Now click Save under the File menu. This will compile the class and save the changes. Sample with SilverStream 2.5 or Lower without SQLAnywhere By following these steps, you are going to be creating a new Business Object and then pasting code into the body of the object. 1. Open the SilverStream Designer. There should be a list of one if not more servers in the left hand pane. Double click on one of them and a list of databases installed on that server will show. 2. Decide which database the new Business Object is going to reside in and double click on that database. This will cause a list of items such as Tables, Forms, Object, etc to show. 3. Click on Objects. In the right hand pane there might be a list of objects. At the bottom of the pane will be action icons, the pointy blue one on the right is the New icon. 4. Click the New icon. This will cause a list of items such as New Package, New Object, etc to show. 5. Click New Object. This will bring up the Business Object Wizard. 6. On the list of triggers, select Invoked. This means that the code in this new business object that you are creating will be executed when this business object is invoked or specifically called. 7. Click Next. 8. In the Object Name field, type the name you wish to give the object. Don't worry about the other fields for now. 9. Click Next. You will now be at a screen asking you to select which interfaces to implement. Don't worry about this for now. 10. Click Finish. This will show the Business Object Designer. 11. In the drop down box which is now displaying UserCode, select Declarations. 12. Type "import com.mobileapps.pcre.*;". This tells your business objects to look in the com.mobileapp.pcre package for classes that it doesn't recognize. 13. In the drop down list which is displaying General, select Invoked. The code screen will show some grayed out code. 14. Without closing the Business Object Designer, go to your Windows Explorer and open a file named MASFirstBusinessObject.txt. It should be located in the directory: \Mobileapps\PCRE\WebApplicationServerSamples\SilverStream 15. Highlight all the code in the file and copy it (usually Ctrl-C). 16. Switch back to the Business Object Designer and paste (Ctrl-V) the code into the invoked method, before the "return;" statement. 17. Go to the File menu and select save. This will save your new business object and compile the code. 18. Now that you have your Parallel Crystal Business Object, you can create a form to invoke it, the only parameter it needs from the invoker is the name of the report file. For instructions on invoking business objects and passing parameters from SilverStream forms, see your SilverStream documentation. Sample with SilverStream Version 3.0 or Higher 1. Create an ODBC data source for the WineDemo3.db database present in the MobileApps/PCRE/WebApplicationServerSamples/SilverStream directory. This WineDemo3.db is an Adaptive Server Anywhere 6.0 database. 2. Add the Database to the SilverStream environment. Enter "dba" for user name and "sql" for password. 3. If the Report server is running on the same machine as the SilverStream server skip to step6. 4. Once you have added the database to the SilverStream environment, you have to provide the name of the machine on which the report server is running. Go to Objects and open the PCREReportGen form in the designer. 5. Double click on the Generate Report button, and SilverStream should open the method handle_btnGenRpt_actionPerformed (ActionEvent evt) in programming editor. 6. You will see that 'parameters.put ("reportServerName", "report.host.com")' is commented out. Uncomment this statement and provide the name of the machine on which the report server is running as string in place of report.host.com. So for instance if the report server is running on mach1.dynalivery.com replace report.host.com with mach1.dynalivery.com. 7. Now you are ready to run the DOR Demo. Go to forms in the WineDemo3 database and run the 'frmOrders' form. 8. Navigate through the records using the '<' and '>' buttons on the form and then click the 'Print' button. 9. A small form pops up showing the sample report name and sample output types. Choose the desired report name and output type and click the generate report button. ---------------------------------------------------------------------- 5.2 BEA WebLogic 4.5.1 Sample Configuration The Parallel Crystal installation includes sample code designed to assist a developer in configuring Parallel Crystal in a BEA WebLogic 4.5.1 environment. This sample code helps verify that Parallel Crystal and WebLogic are working together properly, as well as providing a possible example of code integration. Note: This sample is designed to work with jdk1.2 or higher. General Configuration of the WebLogic 4.5.1 Sample Includes 1. Extracting Sample Code Zip File 2. Editing WebLogic Server Properties file 3. Configuring 1.2 JRE 4. Modifying Demos.jsp 5. Locating PCREJavaClient.jar 6. Modifying WebLogic Server classpath 7. Configuring Paths and File Locations Extract Sample Code Zip File The sample code is located in a file called WebLogic4_5_1Demo.zip in the \WebApplicationServerSamples\WebLogic4_5_1 folder within the Parallel Crystal folder (Default: C:\MobileApps\Pcre). Extract the zip file into the root directory of a disk drive on the WebLogic server machine. As the zip file extracts, it will automatically create a folder, named WebLogicDemo. Edit WebLogic Server Properties File Edit the weblogic.properties file of the WebLogic server by clicking on Start->Programs->WebLogic4.5.1->Utilities->Edit Server Properties. The weblogic.properties file should have the following properties * The WEBLOGIC JSP PROPERTIES section should be uncommented to allow automatic page compilation for java server pages and the compile parameter in this section should point to the path of a jdk1.2 or higher compiler. * The WEBLOGIC EJB DEMO PROPERTIES section should have the following weblogic.ejb.deploy property: weblogic.ejb.deploy=/myserver/sample_ejb.jar Configure 1.2 JRE Configure the WebLogic server to use the 1.2 JRE by clicking on Start->Programs->WebLogic4.5.1->Utilities->Choose 1.2 JRE. Edit the file \setenv.cmd. * The JDK_HOME variable should be edited to point to the path of jdk1.2 or higher home directory (e.g. set JDK_HOME=e:\jdk1.2.2) * The JDK_CLASSES variable should be set to %JDK_HOME%\jre\lib\rt.jar Modify Demos.jsp Edit the file \PCRE\Demos.jsp using an ASCII text editor. * Replace the drive name in the value for OutputName (line 19) with the drive name where you have installed the WebLogic server. * Replace the server name value for WebName (line 20) with the full DNS name of the Web server machine. * Replace the server name value for Server (line 21) with the full DNS name of the PCRE server machine. Locate PCREJavaClient.jar If the WebLogic server and the Parallel Crystal Report server are running on separate machines, the PCREJavaClient.jar file should be copied to a folder on the WebLogic server machine. Make note of the location of this file for specification in the next step. Modify WebLogic Server classpath Add the following files to the classpath of the WebLogic Server using the t3config.exe utility: \ReportTag.jar /PCRE/jars/PCREJavaClient.jar Adding the files to the WebLogic server classpath is done from the command line prompt from the \bin folder by typing the following and pressing enter: t3config -classpath \ReportTag.jar; \PCREJavaClient.jar Configure Paths and File Locations * Edit line 73 of the file \Pcre\JPCREnew.jsp to state the correct path of the \DORDataFile.dat file. * Edit line 99 of the file \Pcre\PCRE_EJB.jsp to state the correct path of the \DORDataFile.dat file. * Move the \PCRE folder and its contents must be moved to the appropriate folder under the WebLogic Home directory (\myserver\public_html ). * Move the \Bike_DB.rpt file to the \Pcre\SampleReports folder on the report server machine. * Copy the \Pcre\jre\lib\orb.properties file on the report server machine to the \jre1_2\lib directory and the \jre1_1\lib directory on the WebLogic server machine. Special DOR Configuration Notes The BikeData data source is used to demonstrate DOR reporting where the data is passed from the WebLogic server to the report server. The Bike_DB.rpt sample/demo requires a WebLogic server machine ODBC setting of a DSN named BikeData, connected to the following MS Access File: \bike.mdb Special EJB Configuration Notes The Parallel Crystal WebLogic sample includes a script called buildMASejb.cmd in the \MASDemoEJB directory. The purpose of this script is to assist in deployment of the EJB. To use the script, edit line 26 to reflect the correct path to PCREJavaClient.jar file and line 27 to reflect the correct path to weblogic's home directory. This demo contains ready-to-deploy EJB source code in the \MASDemoEJB directory. It requires that you run setenv.cmd from the WebLogic root directory and then run buildMAsejb.cmd com\mobileapps\demo\report ejb from the \MASDemoEJB directory. In order to deploy EJB each time WebLogic starts up, you have to add /myserver/sample_ejb.jar to "weblogic.ejb.deploy" property in weblogic.property file in folder. Note: The java source code in the EJB, DeploymentDescriptor.txt and Manifest file may be changed. Use special care when working with Manifest. WebLogic deployment utilities are very sensitive to extra spaces or blank lines. Configuring the NorthWind Demo The NorthWind Demo is a more complex set of reports, implemented through EJB only. These reports require one of two database connections on the report server * An ODBC DSN named Northwind, connected to \PCRE\SampleDatabases\Northwind.mdb MS Access file * The same database from a previous MS Access installation Running the Sample After all the proper configuration steps have been taken, the sample/demo should be tested. To run the sample code/demo 1. Start the WebLogic server and make sure that the sample_ejb.jar deployed properly. 2. Start the Parallel Crystal Report server. 3. Start your browser and point to: http://:7001/Pcre/index.html. Note: The WebLogic web server is case sensitive, so type the URL exactly as shown. ---------------------------------------------------------------------- 5.3 Allaire Cold Fusion Sample Configuration The Parallel Crystal installation includes sample code designed to assist a developer in configuring Parallel Crystal in a Cold Fusion environment. This sample code helps verify that Parallel Crystal and Cold Fusion are working together properly, as well as providing a possible example of code integration. Steps for Installation and Preparation The following steps are for installation of the Cold Fusion Sample, in cases where Parallel Crystal has not already been installed. If Parallel Crystal has already been installed, skip to the next appropriate section for configuration instructions. For Setup of ActiveX demo 1. Extract (if compressed) the Cold Fusion Demo and place the files in a directory on your web server. (example: c:\inetpub\wwwroot\cfdemo). 2. Search for and replace occurrences of the following installation tags in both the contents.cfm and Nwind.cfm files in CFDemo directory: #OUTPUTDIR# This variable refers to the path to webserver's web root directory. It should contain information like "C:\Inetpub\wwwroot\PCREwebdemos" for Internet Information Server. No trailing backslash should be provided. #WEBSERVERDIR# This variable refers to the subdirectory of the webroot where the sample output will be placed. For example, it could be replaced with "PCREwebdemos." No leading or trailing backslashes should be provided. It will be used to build URL, so use forward slashes if needed #REPORTSERVERIP# This should be replaced with the PCRE server's fully qualified domain name (even if it is on the same machine). For Setup of C++ and Java Tags 1. Place the Cpp tag and Java tag folders in a folder on your test machine (for example c:\cfdemo). 2. Enable C++ custom tags on the client has by registering C++ CFX tag dll (in CF2/Release directory) in Cold Fusion Administrator. 3. Enable Java custom tags on the client by installing CFX_J and following the instructions detailed in the section below entitled, Configuring Cold Fusion 4.0 with Parallel Crystal Java API. Configuring Cold Fusion 4.0 with Parallel Crystal C++ API The Parallel Crystal Cold Fusion Sample contains the file \CPPTag\Release\CF2.dll, which has already been built. It must be registered with your Cold Fusion Server. To do this go to Cold Fusion Administrator, go to CFX Tags and create a new one with the name CFX_PCRE. To develop new C++ tags * Use the Visual C++ Cold Fusion Tag Wizard to create a custom tag (CFX). This may be done only if Visual C++ is installed prior to the installation of Cold Fusion 4.0. * Add header files include paths to current environment. Use the Visual C++ menu option Tools->Options->Directories->Include files. Add the following directories: \CppClient\include \Visibroker\include \CFX\include * Add a library to the project settings in Project->Settings->Link->Object/Library modules: \CppClient\lib\cppclient.lib * After building a .DLL for the custom tag, register the tag with the Cold Fusion Server. The .DLL must be accessible to the Cold Fusion Server, meaning it must be on the local to the server drive. Use the Cold Fusion Administrator, CFX Tags option to create a new one with the name CFX_. * In order to update or rebuild this .DLL in the same directory where it is registered, the Cold Fusion Server must be shut down from the Control Panel/Services. Configuring Cold Fusion 4.0 with Parallel Crystal Java API This Demo set contains ready to use CFX_J_PCRE.class file in the \WebApplicationServerSamples\ColdFusion\Java directory. * Install CFX_J components of Cold Fusion. * Register the custom CFX_J tag on the server. This may best be done by editing the following file: /config/jvm.init Ensure that the class path in the first section of the file contains at least: java.class.path=\pcrejavaclient.jar; \JavaTags; \JavaTags\.jar * Copy \JRE\lib\orb.properties file to \Allaire\CFX_J 1.0\bin\Jre\1.2\lib directory. * To compile the .java file, refer to run.bat, adjusting the directory names for your Java configuration. * After recompiling the Java tag, restart the Cold Fusion Server. Configuring Cold Fusion 4.0 with Parallel Crystal Automation Server objects There is no additional setup required in order to use the Automation Server API of Parallel Crystal. The CFOBJECT tag of Cold Fusion creates the object which you will use to communicate with Parallel Crystal. ---------------------------------------------------------------------- 5.4 Active Server Pages Sample Configuration The Parallel Crystal installation includes sample code and report templates designed to assist a developer in configuring Parallel Crystal in an Active Server Pages environment. This sample helps verify that Parallel Crystal and Active Server Pages are working together properly, as well as providing a possible example of code integration. Configuring the ASP Sample includes * Extracting Sample ASP Pages * Extracting Report Files * Configuring Northwind Database * Modifying Global Settings File Extract Sample ASP Pages The Parallel Crystal installation includes a set of Sample ASP pages. These pages are located in a file called ASPDemo.zip in the WebApplicationServerSamples\Active Server Pages folder within the Parallel Crystal folder (default: C:\MobileApps\Pcre). Extract the zip file into a folder in the Web Server machine. The folder name for these files should correspond to a virtual directory created through IIS. In the IIS MMC (Microsoft Management Console) (also called Internet Service Manager) go to the default website. Under the "Action" button Go to "New" and "Virtual Directory". Link this virtual directory to the folder where the ASP files were extracted. Extract Report Files This Parallel Crystal installation includes a set of report templates designed to work with the Sample ASP pages. These templates are located in a file called ASPdemorptfiles.zip in the WebApplicationServerSamples\Active Server Pages folder within the Parallel Crystal folder (default: C:\MobileApps\Pcre). Extract the zip file into a folder on the Report Server machine, making note of the location for future configuration. Configure Northwind Database Northwind.mdb is a Microsoft Access database. It is typically included as part of the MS Access installation. Dynalivery also includes a copy of this database in the installation of Parallel Crystal (default: C:\MobileApps\Pcre\SampleReports). Northwind.mdb should be present on the Report Server machine. The database is accessed through ODBC. The server name and database name should both be "Northwind". No loginid and password are used. Note: The names are case-sensitive. Modify Global Settings File The file Global.asa is a global settings file for the Web Application. After extracting the ASPDemo.zip file, Global.asa will reside in the folder containing the Sample ASP pages. Use a text editor to make the following changes to Global.asa * Session.Timeout =30 : needs to be set to an integer value specifying the time in minutes after which all the session variables expire. This is the time when there is no activity on server side for a session. * Session("ReportServer") = "example.mobileapps.com" : Specify the report server name. Can be changed later directly from the web application. * Session("Outputdir1")= "C:\InetPub\wwwroot\PCREwebdemos\Reports\" The directory where all the generated reports will be placed on the web server. Note: Do not include any files or folders in this directory. This directory should be reserved for keeping generated report documents. Files are routinely deleted from this directory as part of disk management feature of Parallel Crystal. * Session("WebName") = "http://example/PCREWebDemos/Reports/" The WebName should correspond to the web address of OutPutDir1. * Session("FolderDelFreq")= 0.5 : Time in minutes for classifying a directory as old and deleting it. A directory is said as "old" if it has not been modified or accessed in this time. ---------------------------------------------------------------------- 5.5 Other Web Application Servers Please contact your Dynalivery account representative for more information about integrating Parallel Crystal with Web Application Server products not documented in this guide.