This article provides a summary of the high level steps involved with building a SAP BI 4 Demo System and provides guidance on hardware and software requirements and links to where software can be downloaded from. The Demo System will host SAP Business Objects 4.0 and SAP Data Services 4.0
A common issue found when starting SAP Business Objects BI4 is that the system cannot logon to the CMS database repository. Troubleshooting this can be tricky but the following command can be used on a Linux deployment to check connectivity to an Oracle database and capture error messages in a log file,
/opt/sapboe/sap_bobj/ccm.sh -isdbempty -dbdriver "oracledatabasesubsystem" -connect "DSN=<tnsname>;UID=<username>;PWD=<password>" -logfile logfile.out
where <tnsname>, <username> and <password> are the appropriate Oracle logon credentials for the database.
What this command actually does is to check that the target database is or is not an empty database schema. However if there is a database connection error then this will be captured in the logfile.out and from there we can troubleshoot connection issues.
Correlation Analysis is a well-known analytical technique used to test if there is a relation between two quantities, for example did a marketing campaign lead to an increase in sales or as the price of one stock rises and falls does the price of another stock also rise or fall in synch.
Determining if there is a correlation can be exploited:
- a marketing campaign that isn’t impacting sales can be cancelled to save costs or if it is successful it can then be extended or
- ensuring that a portfolio has good diversity so that if one investment suddenly drops it is less likely that all other investments will also drop.
The aim of this article is to review what correlation analysis is and then use a worked example to understand how to implement correlation analysis using SAP Business Objects Web Intelligence.
The previous article provided an introduction to unit testing in general covering the purpose and benefits of unit testing. This article now looks at a method of unit testing that can be utilised in a SAP DataServices project. First we’ll discuss what objects are candidates for unit testing and then look at how we implement the unit testing of these objects.
One of the key drivers of this article is that although there are many articles on unit testing in general on internet there are hardly any on unit testing with SAP DataServices. Unit testing has been accepted as a key part of the software development lifecycle for projects building applications in languages such as Java or C++ however I have rarely come across a SAP DataServices project where unit testing is treated as a fundamental part of the software development life cycle. As a result projects without rigorous unit testing spend longer than planned in system testing, identifying trivial defects, and as a result suffer from delays and cost overruns.
This article first explains what is unit testing and what benefits it brings to a project and then looks at how to implementing automated unit testing in a SAP DataServices project.