Report Bursting with SAP Crystal Reports Server 2008

Visit www.sapdiary.com

Report Bursting with SAP Crystal Reports Server 2008

(Post #3 of 3 for Reportapalooza – Focused on SAP Crystal Reports Server 2008).

The idea to write about Report Bursting in SAP Crystal Reports Server 2008 came to me on the shuttle bus on the way to the airport in Orlando after a very successful (and one shiny iPad later) ASUG SAP BusinessObjects User Conference. The idea came by way of friend and fellow Reportapalooza expert – Brian Durning.

We were having a conversation about the “Reporting Remix” challenge and I asked his opinion on topics to discuss when writing about SAP Crystal Reports Server 2008. Brian is a highly accomplished SAP Crystal solutions expert and his immediate recommendation was Report Bursting. After some investigation, I now know why he made this suggestion. Report Bursting is a really powerful, convenient, and efficient process that minimizes the need for excessive individual report scheduling.

As the previous paragraph suggests, the inclusion of Report Bursting is one of the most anticipated enhancements to SAP Crystal Reports Server 2008. If setup correctly, this elusive feature is an SAP Crystal and BOE administrator’s dream. But if setup incorrectly, it will quickly become a DBA’s nightmare.  That’s why Report Bursting should be carefully researched and tested before implementing in a production environment. Once you’re ready, scheduling reports will never be the same (in a GOOD way).

What is Report Bursting?

Report Bursting in SAP Crystal Reports Server 2008 allows multiple groups of reports (known as Publications) to be scheduled and distributed to personalized groups of recipients with each group receiving reports containing data filtered differently. This is accomplished when the SQL statement is submitted to the database by the individual SAP Crystal Reports multiple times with different filtered values fetching different data values for each group.

This process provides the most efficient way of scheduling and distributing reports to a large number of users who require the same or similar reports but filtered by different parameters.

The reason that Report Bursting should be entered into cautiously is because of the potential impact on system resources. If the option “One database fetch per recipient” is selected when creating a Publication, the SQL statement of each report will query the database one time for each recipient. This option will almost definitely catch the eye of the DBAs if the recipient list is of significant size. But one database fetch per “batch” of recipients might be much less expensive and fly well below the DBA’s radar.

Creating a New Publication for Report Scheduling

To create a new Publication, begin by selecting a folder from the file menu in InfoView. Once you’ve done this, click New in the default toolbar and select Publication. This is displayed in the screenshot below.

Once “Publication” is selected from the list of choices, you’ll have three options when the “New Publication” window opens.

SummaryGeneral PropertiesSource Documents

In the General Properties section, give your new Publication a name, description (optional), keywords (optional), and then select the Source Documents option. Next click Add to select the reports that will become a part of the Publication that will “Refresh at Runtime”. Multiple reports can be selected as part of a single Publication.

As soon as reports are added, six new options are made available. The “New Publication” now has the following property sections.

SummaryGeneral PropertiesSource DocumentsEnterprise RecipientsDynamic RecipientsPersonalizationFormatsDestinationsAdditional Options

The “Additional Options” section contains eight different options:

Print SettingsDelivery RulesMerged PDF OptionsDatabase LogonRecurrenceEventsScheduling Server GroupAdvanced

Select the Advanced category and you’ll see settings in three different groups:

Profile ResolutionPersonalizationReport Bursting Method

The Report Bursting Methods section provides three choices for bursting:

One database fetch for all recipients (recommended for minimizing the number of database queries)One database fetch for each batch of recipients (recommended for high-volume scenarios)One database fetch per recipient (recommended when using row level security within Universes or Business Views)

Report Bursting Methods Described

One database fetch for all recipients – This option will submit the SQL statement of each report to the database once per report then deliver the data in the specified format to each recipient.  This method uses the database logon credentials of the publisher.One database fetch for each batch of recipients – This is the default option when scheduling Crystal Reports. Batches can run concurrently on different servers to reduce the load on the system (keeping the DBAs happy). The size of the batches depends on the specified personalization. This method uses the database logon credentials of the publisher.One database fetch per recipient – This method uses the data source logon credentials of each recipient as the query is submitted to the database once per report for each recipient in the publication. This option provides the greatest level of security but also produces the greatest load on the system if the recipient list is large.

Publications

In addition to Report Bursting, Publications provide an extensive set of options. Among the options that you’ll want to pay special attention to are the: Print Settings, Delivery Rules, Database Logon Credentials, Recurrence, and Events. Settings such as: Personalization, Formats, and Destinations should also be configured completely before saving and implementing a Publication.

Be sure to view the Summary option and review your selections before finalizing your Publication. You should also test your Publication before making it live. Refer to official SAP documentation for a more in-depth discussion of Publications and information regarding the various other options to configure, save, schedule, and view publication results.

Summary

After finally experiencing SAP Crystal Reports Server 2008, I am surprised at the great deal of sophisticated methods of delivering reports to users across the enterprise. Whether through the convenience of the portal , the use of automated report scheduling, or the use of personalized Publications for Report Bursting, SAP Crystal Reports Server 2008 is an excellent product for sharing information with users.

Questions? Please contact me.
Jim.Brogden@daugherty.com

If you enjoyed this post, make sure you subscribe to my RSS feed!

Sharing Reports in SAP Crystal Reports Server

In this post, the 2nd in a three part series for the Reportapalooza “Reporting Remix” challenge, I will describe my observations of SAP Crystal Reports Server after logging on with Internet Explorer into the Java Infoview portal.

I logged into SAP Crystal Reports Server as the Administrator and was given two categories of options: Navigate and Personalize. Beneath the Personalize category was a Preferences selection. I’ve never been the type of person to pass on the opportunity to tweak a couple settings, so I clicked Preferences. Below is a screenshot of the initial screen displayed after I logged into the system.

Preferences are available in four categories:

GeneralChange PasswordCrystal ReportsDashboard and Analytics

The General section was expanded by default and the first setting provides the option to change the InfoView Start Page. I modified this selection by clicking the option button beside Folder then browsing to the “Report Samples” folder. By making this selection, all of my subsequent logons to the SAP Crystal Reports Server will no longer display the Navigate and Personalize categories as previously described. Instead, I would be taken directly to the Report Sample folder. 
This option saves time and allows me to get right to the folder that contains the reports I’m most interested in analyzing.

Browsing BusinessObjects InfoView
The contents of the Java Infoview portal, (or BUSINESSOBJECTS INFOVIEW as it’s titled in the upper left corner of the page header), delivers Crystal Reports and other local document types to users in a similar format as Windows Explorer. Users have the ease of navigating through a folder structure on the left side of the page while viewing the contents of the selected folder on the right side of the page.
This basic style should be very familiar to anyone that has spent any time working with a PC. The simplicity in navigation seems like it would lead to a very productive user experience.

Adding Reports to the Portal
To begin sharing reports with other users, I will need to add them to the portal. Will this be difficult or easy? Should I right-click or look for something like “Add”? The answer is: either.
If you want to add a report to the portal, just click Add in the toolbar located across the top of the folder structure. After clicking Add, two choices will be available – Crystal Reports and Local Document. If Local Document is selected, you’ll have the opportunity to browse for a Microsoft Office document (Excel, Word, or PowerPoint), PDF, Text file, or other file type. If Crystal Reports is selected, you’ll be taken to a screen prompting you to select a Crystal Report. The screenshot below shows the Add button in action.

Another way of adding a report to the portal is by right-clicking on a folder and selecting Add. This option is available in the tree of folders on the left side of the screen. You can also right-click on a folders displayed on the right side of the screen to add a Crystal Report to the portal. Picture below is this example.

Sharing Reports with Folders and Categories
Reports can be shared or delivered to authorized users in either folders, categories, or both. Folders are the primary structure for storing published report objects while categories seem to work as custom views that may contain reports from different folders.

My Favorites and Inbox
The My Favorites folder in the Java Infoview portal allows users to save their own personal copies of reports. This is a great place for storing report variations or reports that are still in the development and verification phase.

The Inbox is an extremely useful feature for passing around instances of reports to other authorized users. Also, the Infoview Inbox is a common destination for sending the results of scheduled report instances. Any user with Schedule rights can send refreshed report instances to other users with a valid logon by selecting “Business Objects Inbox” as the scheduled destination while scheduling a report to refresh.

Enterprise Convenience
After spending a short amount of time with SAP Crystal Reports Server, it has become very obvious how powerful this product can be to an organization. A report developer in Mobile can create a report, publish it to the portal, and then have users in Portland, New York, and Atlanta all view it within seconds of publishing it. With this type of collaborative environment, someone in another city can see a report quicker than someone four cubicles away can walk to your desk. Now that is cool!

Please feel free to email me if you have any questions. Thank you!

Jim Brogden

jim.brogden@daugherty.com

If you enjoyed this post, make sure you subscribe to my RSS feed!

Getting Started with SAP Crystal Reports Server

In the fifth and final challenge of Reportapalooza, I’ll be writing a three part series of blog posts about the product at the heart of the SAP Crystal product line – SAP Crystal Reports Server.

My experience with BusinessObjects software goes back to versions 6.1 and 6.5 and the days of Application Foundation and the BOMain.key. Then in 2006, I had the good fortune of being introduced to BusinessObjects XI and the new CORBA architecture. This led to an ongoing string of (mostly) enjoyable experiences installing, deploying, migrating to, and administering BusinessObjects XI R2, XI 3.0, and XI 3.1. These experiences also included many years of developing Universes, building Desktop Intelligence reports, Web Intelligence documents, and finally Xcelsius 4.5 and 2008 dashboards. But my experience with SAP Crystal Reports only goes back to version XI and I’ve never had the opportunity to even see SAP Crystal Reports Server. So I jumped at the opportunity to install and peruse SAP Crystal Reports Server as part of the “Reporting Remix” and Reportapalooza.

Diving right in, I installed “SAP Crystal Reports Server 2008 V1” on my favorite box. My first attempt failed though because I tried to install it on a machine that already had SAP BusinessObjects XI 3.1 installed. My mistake, I should’ve known better.   Not a problem, I moved to another PC.

As the installation began, I started noticing some very familiar screens. These were some of the same exact windows and options that are offered when SAP BusinessObjects XI 3.x is installed. Below is a description of a few of the dialog screens presented during installation.

Install Type selection – Provides the option to install a MySQL Database Server.Server Component Configuration – CMS Port selection and administrator account setup.Server Intelligence Agent – An “umbrella” service that helps manage services (or servers) by automating starting, restarting, and stopping of servers.Web Application Server selection – Java Web Application Server is the default and “WACS” is recommended deployment type. However, the option to install a Tomcat server and deploy to it is provided.  Additional options are also provided, such as:Allowing you to deploy to a pre-installed Web App ServerThe option to manually deploy the WAR file web components after installationInstall an IIS Web App Server (assuming ASP.NET v1.1 already exists)MySQL Database Configuration – Used for storing system data.Web Application Container Server Configuration – HTTP port setting. 6405 is the default.

After making it through the initial series of settings, installation is ready to begin. The screens continue to remind me of installing BOE but they all say “Crystal Reports Server 2008 V1 Setup”. Pictured below is the Server Intelligence Agent dialog screen showing the option to rename the Node Name and manually adjust the Port number. I changed the Node Name but kept the default Port #.

The screenshot below shows the Web Application Server deployment options.

The two screen shots below show the installation in progress. Expect installation to take from 30 minutes to 1 hour.

As my installation moved very close to completion, I was prompted (on Vista) by my Windows Firewall to either Keep Blocking or Unblock “BusinessObjects Enterprise”. “BusinessObjects Enterprise”? Wow, so far, it’s almost exactly like BOE!

Suddenly I remembered the driving force behind the architecture change from BusinessObjects 6.5 to the smooth, elegant, and .WAR filled CORBA architecture in XI. It was because of the powerful and stable SAP Crystal Reports Server.

Installation complete! It’s time to click Start and have a look at what was installed. The screen shot below shows full list of tools installed. The items that jumped out to me are:

Central Configuration Manger (CCM) – Windows based server management utilityCentral Management Console (CMC) – Web based administrative consoleImport Wizard – Tool for migrating objects from one environment to anotherJava Infoview – The reporting portal (and same favicon used by InfoView in BusinessObjects)

The first thing I did was click “Java Infoview” and logon as the administrator. At first glance, it’s identical to SAP BusinessObjects Enterprise XI 3.1. But within minutes I began to notice a couple subtle differences. For one, there were a couple key products missing that I’m used to seeing. Such as:

Universe DesignerWeb Intelligence

Then I realized how long Crystal Reports has been around. And how many clients use Crystal Reports to develop highly refined pixel perfect reports. What is the best method for delivering reports to users in a zero-client environment and not requiring the installation of Crystal Reports on every users PC? The answer is SAP Crystal Reports Server.

In my next two posts I will begin describing some of the common features and primary functions in SAP Crystal Reports and how it relates to an enhanced user experience.

Thank you,
Jim Brogden
jim.brogden@daugherty.com

If you enjoyed this post, make sure you subscribe to my RSS feed!

Report Bursting with SAP Crystal Reports Server 2008

(Post #3 of 3 for Reportapalooza – Focused on SAP Crystal Reports Server 2008).

The idea to write about Report Bursting in SAP Crystal Reports Server 2008 came to me on the shuttle bus on the way to the airport in Orlando after a very successful (and one shiny iPad later) ASUG SAP BusinessObjects User Conference. The idea came by way of friend and fellow Reportapalooza expert – Brian Durning.

We were having a conversation about the “Reporting Remix” challenge and I asked his opinion on topics to discuss when writing about SAP Crystal Reports Server 2008. Brian is a highly accomplished SAP Crystal solutions expert and his immediate recommendation was Report Bursting. After some investigation, I now know why he made this suggestion. Report Bursting is a really powerful, convenient, and efficient process that minimizes the need for excessive individual report scheduling.

As the previous paragraph suggests, the inclusion of Report Bursting is one of the most anticipated enhancements to SAP Crystal Reports Server 2008. If setup correctly, this elusive feature is an SAP Crystal and BOE administrator’s dream. But if setup incorrectly, it will quickly become a DBA’s nightmare.  That’s why Report Bursting should be carefully researched and tested before implementing in a production environment. Once you’re ready, scheduling reports will never be the same (in a GOOD way).

What is Report Bursting?

Report Bursting in SAP Crystal Reports Server 2008 allows multiple groups of reports (known as Publications) to be scheduled and distributed to personalized groups of recipients with each group receiving reports containing data filtered differently. This is accomplished when the SQL statement is submitted to the database by the individual SAP Crystal Reports multiple times with different filtered values fetching different data values for each group.

This process provides the most efficient way of scheduling and distributing reports to a large number of users who require the same or similar reports but filtered by different parameters.

The reason that Report Bursting should be entered into cautiously is because of the potential impact on system resources. If the option “One database fetch per recipient” is selected when creating a Publication, the SQL statement of each report will query the database one time for each recipient. This option will almost definitely catch the eye of the DBAs if the recipient list is of significant size. But one database fetch per “batch” of recipients might be much less expensive and fly well below the DBA’s radar.

Creating a New Publication for Report Scheduling

To create a new Publication, begin by selecting a folder from the file menu in InfoView. Once you’ve done this, click New in the default toolbar and select Publication. This is displayed in the screenshot below.

Once “Publication” is selected from the list of choices, you’ll have three options when the “New Publication” window opens.

SummaryGeneral PropertiesSource Documents

In the General Properties section, give your new Publication a name, description (optional), keywords (optional), and then select the Source Documents option. Next click Add to select the reports that will become a part of the Publication that will “Refresh at Runtime”. Multiple reports can be selected as part of a single Publication.

As soon as reports are added, six new options are made available. The “New Publication” now has the following property sections.

SummaryGeneral PropertiesSource DocumentsEnterprise RecipientsDynamic RecipientsPersonalizationFormatsDestinationsAdditional Options

The “Additional Options” section contains eight different options:

Print SettingsDelivery RulesMerged PDF OptionsDatabase LogonRecurrenceEventsScheduling Server GroupAdvanced

Select the Advanced category and you’ll see settings in three different groups:

Profile ResolutionPersonalizationReport Bursting Method

The Report Bursting Methods section provides three choices for bursting:

One database fetch for all recipients (recommended for minimizing the number of database queries)One database fetch for each batch of recipients (recommended for high-volume scenarios)One database fetch per recipient (recommended when using row level security within Universes or Business Views)

Report Bursting Methods Described

One database fetch for all recipients – This option will submit the SQL statement of each report to the database once per report then deliver the data in the specified format to each recipient.  This method uses the database logon credentials of the publisher.One database fetch for each batch of recipients – This is the default option when scheduling Crystal Reports. Batches can run concurrently on different servers to reduce the load on the system (keeping the DBAs happy). The size of the batches depends on the specified personalization. This method uses the database logon credentials of the publisher.One database fetch per recipient – This method uses the data source logon credentials of each recipient as the query is submitted to the database once per report for each recipient in the publication. This option provides the greatest level of security but also produces the greatest load on the system if the recipient list is large.

Publications

In addition to Report Bursting, Publications provide an extensive set of options. Among the options that you’ll want to pay special attention to are the: Print Settings, Delivery Rules, Database Logon Credentials, Recurrence, and Events. Settings such as: Personalization, Formats, and Destinations should also be configured completely before saving and implementing a Publication.

Be sure to view the Summary option and review your selections before finalizing your Publication. You should also test your Publication before making it live. Refer to official SAP documentation for a more in-depth discussion of Publications and information regarding the various other options to configure, save, schedule, and view publication results.

Summary

After finally experiencing SAP Crystal Reports Server 2008, I am surprised at the great deal of sophisticated methods of delivering reports to users across the enterprise. Whether through the convenience of the portal , the use of automated report scheduling, or the use of personalized Publications for Report Bursting, SAP Crystal Reports Server 2008 is an excellent product for sharing information with users.

Questions? Please contact me.
Jim.Brogden@daugherty.com

If you enjoyed this post, make sure you subscribe to my RSS feed!

Sharing Reports in SAP Crystal Reports Server

In this post, the 2nd in a three part series for the Reportapalooza “Reporting Remix” challenge, I will describe my observations of SAP Crystal Reports Server after logging on with Internet Explorer into the Java Infoview portal.

I logged into SAP Crystal Reports Server as the Administrator and was given two categories of options: Navigate and Personalize. Beneath the Personalize category was a Preferences selection. I’ve never been the type of person to pass on the opportunity to tweak a couple settings, so I clicked Preferences. Below is a screenshot of the initial screen displayed after I logged into the system.

Preferences are available in four categories:

GeneralChange PasswordCrystal ReportsDashboard and Analytics

The General section was expanded by default and the first setting provides the option to change the InfoView Start Page. I modified this selection by clicking the option button beside Folder then browsing to the “Report Samples” folder. By making this selection, all of my subsequent logons to the SAP Crystal Reports Server will no longer display the Navigate and Personalize categories as previously described. Instead, I would be taken directly to the Report Sample folder. 
This option saves time and allows me to get right to the folder that contains the reports I’m most interested in analyzing.

Browsing BusinessObjects InfoView
The contents of the Java Infoview portal, (or BUSINESSOBJECTS INFOVIEW as it’s titled in the upper left corner of the page header), delivers Crystal Reports and other local document types to users in a similar format as Windows Explorer. Users have the ease of navigating through a folder structure on the left side of the page while viewing the contents of the selected folder on the right side of the page.
This basic style should be very familiar to anyone that has spent any time working with a PC. The simplicity in navigation seems like it would lead to a very productive user experience.

Adding Reports to the Portal
To begin sharing reports with other users, I will need to add them to the portal. Will this be difficult or easy? Should I right-click or look for something like “Add”? The answer is: either.
If you want to add a report to the portal, just click Add in the toolbar located across the top of the folder structure. After clicking Add, two choices will be available – Crystal Reports and Local Document. If Local Document is selected, you’ll have the opportunity to browse for a Microsoft Office document (Excel, Word, or PowerPoint), PDF, Text file, or other file type. If Crystal Reports is selected, you’ll be taken to a screen prompting you to select a Crystal Report. The screenshot below shows the Add button in action.

Another way of adding a report to the portal is by right-clicking on a folder and selecting Add. This option is available in the tree of folders on the left side of the screen. You can also right-click on a folders displayed on the right side of the screen to add a Crystal Report to the portal. Picture below is this example.

Sharing Reports with Folders and Categories
Reports can be shared or delivered to authorized users in either folders, categories, or both. Folders are the primary structure for storing published report objects while categories seem to work as custom views that may contain reports from different folders.

My Favorites and Inbox
The My Favorites folder in the Java Infoview portal allows users to save their own personal copies of reports. This is a great place for storing report variations or reports that are still in the development and verification phase.

The Inbox is an extremely useful feature for passing around instances of reports to other authorized users. Also, the Infoview Inbox is a common destination for sending the results of scheduled report instances. Any user with Schedule rights can send refreshed report instances to other users with a valid logon by selecting “Business Objects Inbox” as the scheduled destination while scheduling a report to refresh.

Enterprise Convenience
After spending a short amount of time with SAP Crystal Reports Server, it has become very obvious how powerful this product can be to an organization. A report developer in Mobile can create a report, publish it to the portal, and then have users in Portland, New York, and Atlanta all view it within seconds of publishing it. With this type of collaborative environment, someone in another city can see a report quicker than someone four cubicles away can walk to your desk. Now that is cool!

Please feel free to email me if you have any questions. Thank you!

Jim Brogden

jim.brogden@daugherty.com

If you enjoyed this post, make sure you subscribe to my RSS feed!

Getting Started with SAP Crystal Reports Server

In the fifth and final challenge of Reportapalooza, I’ll be writing a three part series of blog posts about the product at the heart of the SAP Crystal product line – SAP Crystal Reports Server.

My experience with BusinessObjects software goes back to versions 6.1 and 6.5 and the days of Application Foundation and the BOMain.key. Then in 2006, I had the good fortune of being introduced to BusinessObjects XI and the new CORBA architecture. This led to an ongoing string of (mostly) enjoyable experiences installing, deploying, migrating to, and administering BusinessObjects XI R2, XI 3.0, and XI 3.1. These experiences also included many years of developing Universes, building Desktop Intelligence reports, Web Intelligence documents, and finally Xcelsius 4.5 and 2008 dashboards. But my experience with SAP Crystal Reports only goes back to version XI and I’ve never had the opportunity to even see SAP Crystal Reports Server. So I jumped at the opportunity to install and peruse SAP Crystal Reports Server as part of the “Reporting Remix” and Reportapalooza.

Diving right in, I installed “SAP Crystal Reports Server 2008 V1” on my favorite box. My first attempt failed though because I tried to install it on a machine that already had SAP BusinessObjects XI 3.1 installed. My mistake, I should’ve known better.   Not a problem, I moved to another PC.

As the installation began, I started noticing some very familiar screens. These were some of the same exact windows and options that are offered when SAP BusinessObjects XI 3.x is installed. Below is a description of a few of the dialog screens presented during installation.

Install Type selection – Provides the option to install a MySQL Database Server.Server Component Configuration – CMS Port selection and administrator account setup.Server Intelligence Agent – An “umbrella” service that helps manage services (or servers) by automating starting, restarting, and stopping of servers.Web Application Server selection – Java Web Application Server is the default and “WACS” is recommended deployment type. However, the option to install a Tomcat server and deploy to it is provided.  Additional options are also provided, such as:Allowing you to deploy to a pre-installed Web App ServerThe option to manually deploy the WAR file web components after installationInstall an IIS Web App Server (assuming ASP.NET v1.1 already exists)MySQL Database Configuration – Used for storing system data.Web Application Container Server Configuration – HTTP port setting. 6405 is the default.

After making it through the initial series of settings, installation is ready to begin. The screens continue to remind me of installing BOE but they all say “Crystal Reports Server 2008 V1 Setup”. Pictured below is the Server Intelligence Agent dialog screen showing the option to rename the Node Name and manually adjust the Port number. I changed the Node Name but kept the default Port #.

The screenshot below shows the Web Application Server deployment options.

The two screen shots below show the installation in progress. Expect installation to take from 30 minutes to 1 hour.

As my installation moved very close to completion, I was prompted (on Vista) by my Windows Firewall to either Keep Blocking or Unblock “BusinessObjects Enterprise”. “BusinessObjects Enterprise”? Wow, so far, it’s almost exactly like BOE!

Suddenly I remembered the driving force behind the architecture change from BusinessObjects 6.5 to the smooth, elegant, and .WAR filled CORBA architecture in XI. It was because of the powerful and stable SAP Crystal Reports Server.

Installation complete! It’s time to click Start and have a look at what was installed. The screen shot below shows full list of tools installed. The items that jumped out to me are:

Central Configuration Manger (CCM) – Windows based server management utilityCentral Management Console (CMC) – Web based administrative consoleImport Wizard – Tool for migrating objects from one environment to anotherJava Infoview – The reporting portal (and same favicon used by InfoView in BusinessObjects)

The first thing I did was click “Java Infoview” and logon as the administrator. At first glance, it’s identical to SAP BusinessObjects Enterprise XI 3.1. But within minutes I began to notice a couple subtle differences. For one, there were a couple key products missing that I’m used to seeing. Such as:

Universe DesignerWeb Intelligence

Then I realized how long Crystal Reports has been around. And how many clients use Crystal Reports to develop highly refined pixel perfect reports. What is the best method for delivering reports to users in a zero-client environment and not requiring the installation of Crystal Reports on every users PC? The answer is SAP Crystal Reports Server.

In my next two posts I will begin describing some of the common features and primary functions in SAP Crystal Reports and how it relates to an enhanced user experience.

Thank you,
Jim Brogden
jim.brogden@daugherty.com

If you enjoyed this post, make sure you subscribe to my RSS feed!

Getting Started with SAP Crystal Reports Server

In the fifth and final challenge of Reportapalooza, I’ll be writing a three part series of blog posts about the product at the heart of the SAP Crystal product line – SAP Crystal Reports Server.

My experience with BusinessObjects software goes back to versions 6.1 and 6.5 and the days of Application Foundation and the BOMain.key. Then in 2006, I had the good fortune of being introduced to BusinessObjects XI and the new CORBA architecture. This led to an ongoing string of (mostly) enjoyable experiences installing, deploying, migrating to, and administering BusinessObjects XI R2, XI 3.0, and XI 3.1. These experiences also included many years of developing Universes, building Desktop Intelligence reports, Web Intelligence documents, and finally Xcelsius 4.5 and 2008 dashboards. But my experience with SAP Crystal Reports only goes back to version XI and I’ve never had the opportunity to even see SAP Crystal Reports Server. So I jumped at the opportunity to install and peruse SAP Crystal Reports Server as part of the “Reporting Remix” and Reportapalooza.

Diving right in, I installed “SAP Crystal Reports Server 2008 V1” on my favorite box. My first attempt failed though because I tried to install it on a machine that already had SAP BusinessObjects XI 3.1 installed. My mistake, I should’ve known better.   Not a problem, I moved to another PC.

As the installation began, I started noticing some very familiar screens. These were some of the same exact windows and options that are offered when SAP BusinessObjects XI 3.x is installed. Below is a description of a few of the dialog screens presented during installation.

Install Type selection – Provides the option to install a MySQL Database Server.Server Component Configuration – CMS Port selection and administrator account setup.Server Intelligence Agent – An “umbrella” service that helps manage services (or servers) by automating starting, restarting, and stopping of servers.Web Application Server selection – Java Web Application Server is the default and “WACS” is recommended deployment type. However, the option to install a Tomcat server and deploy to it is provided.  Additional options are also provided, such as:Allowing you to deploy to a pre-installed Web App ServerThe option to manually deploy the WAR file web components after installationInstall an IIS Web App Server (assuming ASP.NET v1.1 already exists)MySQL Database Configuration – Used for storing system data.Web Application Container Server Configuration – HTTP port setting. 6405 is the default.

After making it through the initial series of settings, installation is ready to begin. The screens continue to remind me of installing BOE but they all say “Crystal Reports Server 2008 V1 Setup”. Pictured below is the Server Intelligence Agent dialog screen showing the option to rename the Node Name and manually adjust the Port number. I changed the Node Name but kept the default Port #.

The screenshot below shows the Web Application Server deployment options.

The two screen shots below show the installation in progress. Expect installation to take from 30 minutes to 1 hour.

As my installation moved very close to completion, I was prompted (on Vista) by my Windows Firewall to either Keep Blocking or Unblock “BusinessObjects Enterprise”. “BusinessObjects Enterprise”? Wow, so far, it’s almost exactly like BOE!

Suddenly I remembered the driving force behind the architecture change from BusinessObjects 6.5 to the smooth, elegant, and .WAR filled CORBA architecture in XI. It was because of the powerful and stable SAP Crystal Reports Server.

Installation complete! It’s time to click Start and have a look at what was installed. The screen shot below shows full list of tools installed. The items that jumped out to me are:

Central Configuration Manger (CCM) – Windows based server management utilityCentral Management Console (CMC) – Web based administrative consoleImport Wizard – Tool for migrating objects from one environment to anotherJava Infoview – The reporting portal (and same favicon used by InfoView in BusinessObjects)

The first thing I did was click “Java Infoview” and logon as the administrator. At first glance, it’s identical to SAP BusinessObjects Enterprise XI 3.1. But within minutes I began to notice a couple subtle differences. For one, there were a couple key products missing that I’m used to seeing. Such as:

Universe DesignerWeb Intelligence

Then I realized how long Crystal Reports has been around. And how many clients use Crystal Reports to develop highly refined pixel perfect reports. What is the best method for delivering reports to users in a zero-client environment and not requiring the installation of Crystal Reports on every users PC? The answer is SAP Crystal Reports Server.

In my next two posts I will begin describing some of the common features and primary functions in SAP Crystal Reports and how it relates to an enhanced user experience.

Thank you,
Jim Brogden
jim.brogden@daugherty.com

If you enjoyed this post, make sure you subscribe to my RSS feed!

Sharing Reports in SAP Crystal Reports Server

In this post, the 2nd in a three part series for the Reportapalooza “Reporting Remix” challenge, I will describe my observations of SAP Crystal Reports Server after logging on with Internet Explorer into the Java Infoview portal.

I logged into SAP Crystal Reports Server as the Administrator and was given two categories of options: Navigate and Personalize. Beneath the Personalize category was a Preferences selection. I’ve never been the type of person to pass on the opportunity to tweak a couple settings, so I clicked Preferences. Below is a screenshot of the initial screen displayed after I logged into the system.

Preferences are available in four categories:

GeneralChange PasswordCrystal ReportsDashboard and Analytics

The General section was expanded by default and the first setting provides the option to change the InfoView Start Page. I modified this selection by clicking the option button beside Folder then browsing to the “Report Samples” folder. By making this selection, all of my subsequent logons to the SAP Crystal Reports Server will no longer display the Navigate and Personalize categories as previously described. Instead, I would be taken directly to the Report Sample folder. 
This option saves time and allows me to get right to the folder that contains the reports I’m most interested in analyzing.

Browsing BusinessObjects InfoView
The contents of the Java Infoview portal, (or BUSINESSOBJECTS INFOVIEW as it’s titled in the upper left corner of the page header), delivers Crystal Reports and other local document types to users in a similar format as Windows Explorer. Users have the ease of navigating through a folder structure on the left side of the page while viewing the contents of the selected folder on the right side of the page.
This basic style should be very familiar to anyone that has spent any time working with a PC. The simplicity in navigation seems like it would lead to a very productive user experience.

Adding Reports to the Portal
To begin sharing reports with other users, I will need to add them to the portal. Will this be difficult or easy? Should I right-click or look for something like “Add”? The answer is: either.
If you want to add a report to the portal, just click Add in the toolbar located across the top of the folder structure. After clicking Add, two choices will be available – Crystal Reports and Local Document. If Local Document is selected, you’ll have the opportunity to browse for a Microsoft Office document (Excel, Word, or PowerPoint), PDF, Text file, or other file type. If Crystal Reports is selected, you’ll be taken to a screen prompting you to select a Crystal Report. The screenshot below shows the Add button in action.

Another way of adding a report to the portal is by right-clicking on a folder and selecting Add. This option is available in the tree of folders on the left side of the screen. You can also right-click on a folders displayed on the right side of the screen to add a Crystal Report to the portal. Picture below is this example.

Sharing Reports with Folders and Categories
Reports can be shared or delivered to authorized users in either folders, categories, or both. Folders are the primary structure for storing published report objects while categories seem to work as custom views that may contain reports from different folders.

My Favorites and Inbox
The My Favorites folder in the Java Infoview portal allows users to save their own personal copies of reports. This is a great place for storing report variations or reports that are still in the development and verification phase.

The Inbox is an extremely useful feature for passing around instances of reports to other authorized users. Also, the Infoview Inbox is a common destination for sending the results of scheduled report instances. Any user with Schedule rights can send refreshed report instances to other users with a valid logon by selecting “Business Objects Inbox” as the scheduled destination while scheduling a report to refresh.

Enterprise Convenience
After spending a short amount of time with SAP Crystal Reports Server, it has become very obvious how powerful this product can be to an organization. A report developer in Mobile can create a report, publish it to the portal, and then have users in Portland, New York, and Atlanta all view it within seconds of publishing it. With this type of collaborative environment, someone in another city can see a report quicker than someone four cubicles away can walk to your desk. Now that is cool!

Please feel free to email me if you have any questions. Thank you!

Jim Brogden

jim.brogden@daugherty.com

If you enjoyed this post, make sure you subscribe to my RSS feed!

Report Bursting with SAP Crystal Reports Server 2008

(Post #3 of 3 for Reportapalooza – Focused on SAP Crystal Reports Server 2008).

The idea to write about Report Bursting in SAP Crystal Reports Server 2008 came to me on the shuttle bus on the way to the airport in Orlando after a very successful (and one shiny iPad later) ASUG SAP BusinessObjects User Conference. The idea came by way of friend and fellow Reportapalooza expert – Brian Durning.

We were having a conversation about the “Reporting Remix” challenge and I asked his opinion on topics to discuss when writing about SAP Crystal Reports Server 2008. Brian is a highly accomplished SAP Crystal solutions expert and his immediate recommendation was Report Bursting. After some investigation, I now know why he made this suggestion. Report Bursting is a really powerful, convenient, and efficient process that minimizes the need for excessive individual report scheduling.

As the previous paragraph suggests, the inclusion of Report Bursting is one of the most anticipated enhancements to SAP Crystal Reports Server 2008. If setup correctly, this elusive feature is an SAP Crystal and BOE administrator’s dream. But if setup incorrectly, it will quickly become a DBA’s nightmare.  That’s why Report Bursting should be carefully researched and tested before implementing in a production environment. Once you’re ready, scheduling reports will never be the same (in a GOOD way).

What is Report Bursting?

Report Bursting in SAP Crystal Reports Server 2008 allows multiple groups of reports (known as Publications) to be scheduled and distributed to personalized groups of recipients with each group receiving reports containing data filtered differently. This is accomplished when the SQL statement is submitted to the database by the individual SAP Crystal Reports multiple times with different filtered values fetching different data values for each group.

This process provides the most efficient way of scheduling and distributing reports to a large number of users who require the same or similar reports but filtered by different parameters.

The reason that Report Bursting should be entered into cautiously is because of the potential impact on system resources. If the option “One database fetch per recipient” is selected when creating a Publication, the SQL statement of each report will query the database one time for each recipient. This option will almost definitely catch the eye of the DBAs if the recipient list is of significant size. But one database fetch per “batch” of recipients might be much less expensive and fly well below the DBA’s radar.

Creating a New Publication for Report Scheduling

To create a new Publication, begin by selecting a folder from the file menu in InfoView. Once you’ve done this, click New in the default toolbar and select Publication. This is displayed in the screenshot below.

Once “Publication” is selected from the list of choices, you’ll have three options when the “New Publication” window opens.

SummaryGeneral PropertiesSource Documents

In the General Properties section, give your new Publication a name, description (optional), keywords (optional), and then select the Source Documents option. Next click Add to select the reports that will become a part of the Publication that will “Refresh at Runtime”. Multiple reports can be selected as part of a single Publication.

As soon as reports are added, six new options are made available. The “New Publication” now has the following property sections.

SummaryGeneral PropertiesSource DocumentsEnterprise RecipientsDynamic RecipientsPersonalizationFormatsDestinationsAdditional Options

The “Additional Options” section contains eight different options:

Print SettingsDelivery RulesMerged PDF OptionsDatabase LogonRecurrenceEventsScheduling Server GroupAdvanced

Select the Advanced category and you’ll see settings in three different groups:

Profile ResolutionPersonalizationReport Bursting Method

The Report Bursting Methods section provides three choices for bursting:

One database fetch for all recipients (recommended for minimizing the number of database queries)One database fetch for each batch of recipients (recommended for high-volume scenarios)One database fetch per recipient (recommended when using row level security within Universes or Business Views)

Report Bursting Methods Described

One database fetch for all recipients – This option will submit the SQL statement of each report to the database once per report then deliver the data in the specified format to each recipient.  This method uses the database logon credentials of the publisher.One database fetch for each batch of recipients – This is the default option when scheduling Crystal Reports. Batches can run concurrently on different servers to reduce the load on the system (keeping the DBAs happy). The size of the batches depends on the specified personalization. This method uses the database logon credentials of the publisher.One database fetch per recipient – This method uses the data source logon credentials of each recipient as the query is submitted to the database once per report for each recipient in the publication. This option provides the greatest level of security but also produces the greatest load on the system if the recipient list is large.

Publications

In addition to Report Bursting, Publications provide an extensive set of options. Among the options that you’ll want to pay special attention to are the: Print Settings, Delivery Rules, Database Logon Credentials, Recurrence, and Events. Settings such as: Personalization, Formats, and Destinations should also be configured completely before saving and implementing a Publication.

Be sure to view the Summary option and review your selections before finalizing your Publication. You should also test your Publication before making it live. Refer to official SAP documentation for a more in-depth discussion of Publications and information regarding the various other options to configure, save, schedule, and view publication results.

Summary

After finally experiencing SAP Crystal Reports Server 2008, I am surprised at the great deal of sophisticated methods of delivering reports to users across the enterprise. Whether through the convenience of the portal , the use of automated report scheduling, or the use of personalized Publications for Report Bursting, SAP Crystal Reports Server 2008 is an excellent product for sharing information with users.

Questions? Please contact me.
Jim.Brogden@daugherty.com

If you enjoyed this post, make sure you subscribe to my RSS feed!

Report Bursting with SAP Crystal Reports Server 2008

(Post #3 of 3 for Reportapalooza – Focused on SAP Crystal Reports Server 2008).

The idea to write about Report Bursting in SAP Crystal Reports Server 2008 came to me on the shuttle bus on the way to the airport in Orlando after a very successful (and one shiny iPad later) ASUG SAP BusinessObjects User Conference. The idea came by way of friend and fellow Reportapalooza expert – Brian Durning.

We were having a conversation about the “Reporting Remix” challenge and I asked his opinion on topics to discuss when writing about SAP Crystal Reports Server 2008. Brian is a highly accomplished SAP Crystal solutions expert and his immediate recommendation was Report Bursting. After some investigation, I now know why he made this suggestion. Report Bursting is a really powerful, convenient, and efficient process that minimizes the need for excessive individual report scheduling.

As the previous paragraph suggests, the inclusion of Report Bursting is one of the most anticipated enhancements to SAP Crystal Reports Server 2008. If setup correctly, this elusive feature is an SAP Crystal and BOE administrator’s dream. But if setup incorrectly, it will quickly become a DBA’s nightmare.  That’s why Report Bursting should be carefully researched and tested before implementing in a production environment. Once you’re ready, scheduling reports will never be the same (in a GOOD way).

What is Report Bursting?

Report Bursting in SAP Crystal Reports Server 2008 allows multiple groups of reports (known as Publications) to be scheduled and distributed to personalized groups of recipients with each group receiving reports containing data filtered differently. This is accomplished when the SQL statement is submitted to the database by the individual SAP Crystal Reports multiple times with different filtered values fetching different data values for each group.

This process provides the most efficient way of scheduling and distributing reports to a large number of users who require the same or similar reports but filtered by different parameters.

The reason that Report Bursting should be entered into cautiously is because of the potential impact on system resources. If the option “One database fetch per recipient” is selected when creating a Publication, the SQL statement of each report will query the database one time for each recipient. This option will almost definitely catch the eye of the DBAs if the recipient list is of significant size. But one database fetch per “batch” of recipients might be much less expensive and fly well below the DBA’s radar.

Creating a New Publication for Report Scheduling

To create a new Publication, begin by selecting a folder from the file menu in InfoView. Once you’ve done this, click New in the default toolbar and select Publication. This is displayed in the screenshot below.

Once “Publication” is selected from the list of choices, you’ll have three options when the “New Publication” window opens.

SummaryGeneral PropertiesSource Documents

In the General Properties section, give your new Publication a name, description (optional), keywords (optional), and then select the Source Documents option. Next click Add to select the reports that will become a part of the Publication that will “Refresh at Runtime”. Multiple reports can be selected as part of a single Publication.

As soon as reports are added, six new options are made available. The “New Publication” now has the following property sections.

SummaryGeneral PropertiesSource DocumentsEnterprise RecipientsDynamic RecipientsPersonalizationFormatsDestinationsAdditional Options

The “Additional Options” section contains eight different options:

Print SettingsDelivery RulesMerged PDF OptionsDatabase LogonRecurrenceEventsScheduling Server GroupAdvanced

Select the Advanced category and you’ll see settings in three different groups:

Profile ResolutionPersonalizationReport Bursting Method

The Report Bursting Methods section provides three choices for bursting:

One database fetch for all recipients (recommended for minimizing the number of database queries)One database fetch for each batch of recipients (recommended for high-volume scenarios)One database fetch per recipient (recommended when using row level security within Universes or Business Views)

Report Bursting Methods Described

One database fetch for all recipients – This option will submit the SQL statement of each report to the database once per report then deliver the data in the specified format to each recipient.  This method uses the database logon credentials of the publisher.One database fetch for each batch of recipients – This is the default option when scheduling Crystal Reports. Batches can run concurrently on different servers to reduce the load on the system (keeping the DBAs happy). The size of the batches depends on the specified personalization. This method uses the database logon credentials of the publisher.One database fetch per recipient – This method uses the data source logon credentials of each recipient as the query is submitted to the database once per report for each recipient in the publication. This option provides the greatest level of security but also produces the greatest load on the system if the recipient list is large.

Publications

In addition to Report Bursting, Publications provide an extensive set of options. Among the options that you’ll want to pay special attention to are the: Print Settings, Delivery Rules, Database Logon Credentials, Recurrence, and Events. Settings such as: Personalization, Formats, and Destinations should also be configured completely before saving and implementing a Publication.

Be sure to view the Summary option and review your selections before finalizing your Publication. You should also test your Publication before making it live. Refer to official SAP documentation for a more in-depth discussion of Publications and information regarding the various other options to configure, save, schedule, and view publication results.

Summary

After finally experiencing SAP Crystal Reports Server 2008, I am surprised at the great deal of sophisticated methods of delivering reports to users across the enterprise. Whether through the convenience of the portal , the use of automated report scheduling, or the use of personalized Publications for Report Bursting, SAP Crystal Reports Server 2008 is an excellent product for sharing information with users.

Questions? Please contact me.
Jim.Brogden@daugherty.com

If you enjoyed this post, make sure you subscribe to my RSS feed!