Entries from Siebel Essentials tagged with 'Oracle BI Applications'

Oracle BI Applications Upgrade - Part 3

Welcome back, these are the final steps in an Oracle BI Applications upgrade scenario Step 8: Merge the DAC repository After merging the custom folders in the Informatica repository, we have to merge the second (of four) repositories, that is the DAC repository. The new DAC 10.1.3.4 has the unique feature of allowing direct upgrades and merge processes of two existing repositories, even from Siebel Analytics Applications 7.8.4, which had a "non-partioned" repository without containers. Please note that the following steps can only be executed in DAC 10.1.3.4. Previous versions do not support an automated upgrade. Below is a short summary of steps, please see the documentation for more details:Connect to the new standard DAC repository and export the containers you want to upgrade. Connect to the old, customized DAC repository and start the upgrade wizard. Select Refresh Base. This option is recommended when you upgrade from BI Applications 7.9.x Inspect the difference report and resolve conflicts if necessary Click Merge The result is a DAC repository which inherits the modifications made to the standard containers between 7.9.x and 7.9.5 as well as the custom container. However, there might be some additional manual work necessary to complete the DAC upgrade. Step 9: Run test Execution Plans After verifying the Setup view of DAC (registering Informatica servers for 8.1.1 is different) you can rebuild your execution plans and execute test runs to ensure that the ETL works as expected. Step 10: Upgrade and merge the Oracle BI rpd file Number 3... If you have customized the Oracle BI rpd file and you want to benefit from changes made by the Oracle developers, you have to use the equalizerpds utility and the Administration Tool in order to accomplish a merge of the three versionsPrior Customer Repository Prior Standard Repository New Standard Repository into a single New Customer Repository According to the Oracle BI Applications 7.9.5 Upgrade Guide you have to get the original 7.9.x rpd file from the Upgrade folder and copy it to a temporary folder along with your customized rpd and the new standard rpd You then execute the following major stepsuse equalizerpds.exe to resolve minor differences in spelling (such as "Core"."W_DAY_D" is the same as "Core"."W Day D" Compare repositories to find which elements have been created, removed or modified Merge the repositories using the Administration Tools 3-way merge functionality Test the outcome of the merge This concludes the upgrade of repository #3, one more to go... Step 11: Upgrade the Oracle BI Presentation Catalog If you need to combine the changes of Oracle engineering with your customizations (in order to benefit from the new standard list formats for Siebel Marketing, for example) you have to merge the different versions of BI Presentation Catalogs into one. This is supported by the Catalog Manager tool. You have the choice between a simple copy and paste process if you adhered to the best practice of creating your own folders and the merge functionality of Catalog Manager. Conclusion Adhering to best practices and staying "close to the standard" during the development phase is crucial for successful and timely upgrades. Oracle BI Applications get you in touch with 4 different architectures and repositories (Informatica, DAC, rpd and presentation catalog) all of which exist in an original standard, a customized and a new standard version. These are the recommended ways to customize them:Informatica: Only modify objects in custom folders DAC: Only modify objects in the custom container rpd: Trim the original repository and create new presentation catalogs if needed Presentation Catalog: Only modify objects in custom folders Have a nice day...

Oracle BI Applications Upgrade - Part 2

as promised in part 1 of this series, here is part 2 of a summary of steps for an Oracle BI Applications upgrade: Step 5: Import the DAC 7.9.5 repository Use the DAC 7.9.5 client to create a second connection to a new schema and create an empty DAC repository. Import the BI Apps 7.9.5 DAC repository into the new schema using the DAC client. Note: you can not import the 7.9.5 DAC repository using DAC 10.1.3.4 (see below). Optional Step: Install DAC 10.1.3.4 The Data Warehouse Administration Console 10.1.3.4 has been released some time ago. This is an optional step. You can stick with the DAC that comes with Oracle BI Applications 7.9.5 but you might want to look at the new features of DAC 10.1.3.4. However, if you decide to use the new DAC, there is no easy way to revert back (the DAC repository) to 7.9.5, so a good reason to start with taking a backup. Use the new DAC to create connections to the old and new repository and allow DAC 10.1.3.4 to upgrade the schema by logging in to both connections. Quick delta for DAC 7.9.5 to 10.1.3.4 No hibernate libraries required, but make sure you copy the database connectivity .jar file into the lib directory Must create authentication file on first login, then change the Administrator password. For subsequent logins, use the Administrator account. Existing repository (7.9.x) is automatically upgraded to new DAC version upon first login, you can not use earlier DAC versions (this applies to both client and server) after the upgradeStep 6: Upgrade and merge the Informatica Repository Upgrade the old version of the Informatica Repository following the instructions in the Informatica PowerCenter 8.1.1 Installation and Configuration Guide. The process is executed in the web-based Administration Console. Next you can establish connections to both repositories (the one you customized and the new one) in Informatica Repository Manager. You can now compare folders or objects and copy the custom folders to the new repository. If you adhered to the recommendation to do all modifications in custom folders, this is a very safe path. If you made any customizations to objects in standard folders, you most probably have to reapply these changes to the objects in the new repository. Step 7: Upgrade the OBAW Schema According to the OBI Apps 7.9.5 Upgrade Guide you have to run prepared SQL scriptsuse the ddlimp utility to change the schemastart some specialized workflows manually, if you upgraded the Siebel source application to 8.0 or 8.1Reset the sequence generators of Informatica using a scriptImport a specialized repository which contains upgrade workflows and run the respective workflowsNeed a break? All right, see you in a few days for the final. In part 3 we will discuss merging the DAC repository, running test execution plans, upgrade and merge the .rpd file and the presentation catalog....

Oracle BI Applications Upgrade - Part 1

donkey rides Those among you who have undertaken the quest of a Siebel CRM upgrade know what it means to upgrade one (1) repository and merge new standards with old customizations. How does it (look and) feel to upgrade the stunning number of four (4) different repositories, such as in Oracle BI Applications where we currently have 1 Informatica repository1 DAC repository1 BI Server repository1 Presentation Catalog I had the opportunity to do a POC for a custom training and this series of posts tries to point you to the basic steps and pitfalls. The slightly customized BI Application we have to start with consists of the following Oracle BI EE 10.1.3.2Oracle BI Applications 7.9.2 including DACInformatica 7.1.4The target versions are Oracle BI EE 10.1.3.4Oracle BI Applications 7.9.5Informatica 8.1.1 SP4DAC 10.1.3.4 In this first part of the series we cover upgrading the infrastructure basically by installing the new versions of the software packages. However, whenever you undertake an upgrade make sure you read the fabulous manual. And read it before you lay your hands on the keyboard. Step 1: Upgrade the Oracle BI EE Infrastructure This is a straightforward step since you simply install the new version on top of the old version, which is a supported practice even for Siebel Analytics 7.8.4. Of course, you will do a backup of all valuable files and if you modified any standard xml files you better watch out and copy them to the custom folders next time ;-) Step 2: Upgrade Oracle BI Applications Now it's time for another backup, this time you copy the entire DAC directory to a safe place. Next you backup any custom files (scripts, parameter files etc.). We have to uninstall the existing version of Oracle BI Applications and then install Oracle BI Applications 7.9.5. Oracle BI Applications 7.9.5 are "Fusion Edition" Step 3: Upgrade Informatica 7.1.4 to 8.1.1 SP4 Oracle BI Applications 7.9.5 come with exclusive support for Informatica 8.1.1 SP4 which is a bit of a challenge as 8.1.1 has a completely different server architecture (see delta summary below). Best thing is to carefully follow the pre-upgrade steps in the Informatica PowerCenter 8.1.1 Installation and Configuration Guide, especially creating another database (or schema) for the new repository Backup time again. This time we take care of the existing repository and the Repository Agent configuration file (.cfg). Then we uninstall previous versions of Informatica Servers and Clients and install Informatica Services and Clients 8.1.1 and apply SP4 immediately afterwards. The installer creates the new repository service, make sure you name it different than the previous repository. Caveat: Note that the install.exe might not launch if a java-based process such as Oracle's Enterprise Manager Console is running. Quick Delta for Informatica 7.1.4 to 8.1.1 SP 4 (Windows) No separate windows services for Informatica server and Informatica Repository Server New "wrapper" service: "Informatica Services 8.1.1" Server administration now done completely in a web client Repository service and Integration Service (formerly known as Informatica server) are administered from the central web-based administration console New concept of domains, which contain nodes, which host processes such as repository and integration services. The web-based Informatica administration console in version 8.1.1 Step 4: Configure the new Informatica 8.1.1 Services Follow the steps in the Oracle BI Applications 7.9.5 Installation Guide to set up the basic infrastructure. Import the new version of the Informatica Repository provided by the BI Apps 7.9.5 installer into the new Informatica 8.1.1 database. Copy the source and lookup files to the correct directories. Set PowerCenter properties according to the guide. That's it for today, stay tuned for Part 2 where we will install DAC 10.1.3.4, upgrade the Informatica repository and the BAW schema....

Populate W_DAY_D correctly

2011 is near... Oracle BI Applications come with a predefined Informatica Repository and a pre-built DAC (Datawarehouse Administration Console) repository. When loading the BAW (Business Analysis Warehouse, the predefined schema) for the first time, this is called a full load. One table is of particular interest: w_DAY_D, implementing the time dimension, storing one record for each day between 1st of January 1980 and 31st of December 2010. The end day of this period is now raising concerns (and eyebrows) among admins and analysts over the globe as they see that date coming soon. So how is W_DAY_D populated? Using the DAC Client this question is easily answered. There are four tasks that take care of W_DAY_D. click to enlarge The main task SIL_DayDimension has two parameters which are passed to the Informatica workflow. $$START_DATE has a default value of 1980-01-01 and $$END_DATE one of 2010-12-31. Before you can update these parameters, you have to create a custom container using the functionality in the DAC File menu. Once the container is created, go to the SIL_DayDimension task, click the Parameters tab and update the parameters according to your needs. When a referenced object in the DAC repository is changed, it will be cloned and you have to commit that in a dialog box. click to enlarge Now we have to enforce a full load on the W_DAY_D table, which means setting the table's refresh date to NULL. This is standard behavior of the DAC. It will start the task in full mode when the refresh date of the target table(s) are set to NULL. To do this, navigate to Setup > Physical Data Sources > DataWarehouse and click the Refresh Dates tab. Here you query for the table and set the refresh date to NULL. When the next execution plan (you will have to create a new one once you have created a custom container) is run, W_DAY_D will be loaded with the new range of dates. Please keep in mind that you should only extend the date range and never narrow it, so if you have those dates of 1980 already in W_DAY_D, they should stay there for the sake of referential integrity....

Oracle BI EE 10.1.3.4 has arrived

A new release of Oracle BI EE, formerly known as Siebel Analytics has been made available for download last week. There are several new features and interesting points about the product direction. My personal highlights are: Integration with EPM Workspace and Smart SpaceDiscoverer .eex to .rpd migration toolNew sample application with support for marketing segmentationEnhanced wsdl support for BI PublisherEnhanced DAC Client (released independently) that supports upgrades from Analytics 7.8.4 But let's discuss each feature in detail. Most of this information is taken from the documentation and while the product is still hot from the oven, I was lucky to try a few things. As with all new features, they will have to prove their practicability in real life. We'll see... General New Features Integration with Oracle EPM Workspace, Fusion Edition Oracle Enterprise Performance Management Workspace (EPM Workspace) is a component of Oracle's Hyperion Foundation Services. It is the central Web interface for users to access all Performance Management content and tools. In the new release, the following Oracle BI EE applications have been integrated into EPM Workspace: Oracle BI AnswersInteractive DashboardsDeliversBI Publisher Integration with Oracle Smart Space, Fusion Edition Oracle Smart Space is a personalized information delivery solution for Business Intelligence and Enterprise Performance Management that uses configurable desktop gadgets to deliver BI and EPM to every user in the enterprise, utilizing the Windows desktop. In addition, Oracle Smart Space includes a development toolkit for creating additional gadgets that employs common development languages and methodologies and a secure instant messaging system for shared decision making. You can launch and interact with Oracle BI Interactive Dashboards, Answers requests and BI Publisher reports in the Smart Space Content Viewer and Smart Book gadget and add them to the Favorites gadget. You can use Smart Space Collaborator to share Oracle BI content with other Smart Space users. You can also configure iBot results to be sent as Smart Space notifications and view these in the Notification gadget. You can set up for users to download Oracle Smart Space and Oracle Smart View for Microsoft Office from within Oracle BI. Once Smart Space is connected to Oracle BI, you can use Windows Explorer to browse the Oracle BI Presentation Catalog and see the folders (Shared Folders and My Folders) and documents (Dashboard and Answers request) that are available to you. Migrate Discoverer eex files to rpd files The new release includes a utility to accelerate the migration of Oracle BI Discoverer metadata (in the form of an EEX file, version 10.1.2 or higher) to Oracle BI EE metadata (in the form of an RPD file). The utility is a command line executable (MigrateEUL.exe) and accompanying properties file that can be found in the \OracleBI\Server\bin directory. An instruction document can be found in the \OracleBI\Server\Document directory. Reading the document, you find a chapter named "Why migrate to Oracle BI EE?" and the answer is given as a summary of the Oracle BI EE functionality and benefits. The rest is up to you... The screenshots below show a first encounter with the utility. I have converted a simple Discoverer EUL into an rpd file. It completed the task without errors, however there is additional manual work to be expected within the rpd file. migrateEUL.exe command line utility, click to enlarge rpd file generated by migrateEUL.exe, click to enlarge Time-aware line charts A new type of line chart (Line Time Series) is available to plot time series data. The chart automatically scales the X-axis based on the time that has elapsed between data points. The chart requires a single date or date-time data column to be selected on the X-axis. It has a single Y-axis, but supports multiple data series. There are several formatting restrictions for this chart type. New line time series chart, click to enlarge Support for Oracle WebLogic Server 10.x. (formerly known as BEA WebLogic Server) You can use Oracle BI EE and Oracle BI Publisher with the Oracle WebLogic Server New Sample Oracle BI Application and Data Set A new sample Oracle BI application and data set called "Sample Sales" has been designed to better and more fully illustrate the capabilities of Oracle BI 10.1.3.4. It showcases presentation (Answers formula building, resentation Variables, Filtering, Layouts, Navigations, and so on) and modeling techniques. The content is designed to demonstrate as much as possible of OBI EE capabilities and is primarily meant to help customers who want examples and templates to extract ideas from. This new set is meant to replace the former Paint sample content. The new Sample Sales application includes numerous reports organized in 20 dashboard pages around the following: Rankings and ToppersTrends and HistoryTiering and DistributionDetailed ReportsLists and Segmentation (Marketing) Particularly nice features of the new sample application are the detailed help and the good quality of sample data. I am also positively surprised about the presence of marketing metadata, because the marketing segmentation functionality is something that probably only a few people using Siebel Marketing are aware of, yet it can be used standalone as well. Sample Sales comes with a detailed online help, click to enlarge. The Rankings and Toppers dashboard of the new sample sales application Marketing Segmentation: Prompted Segmentation and Contact Planning Rules The segment designer now supports the "is prompted" operator as filter criteria which enables passing of values (such as a list of customer Ids) into the segment, thus enabling dynamic segments for so-called event triggered campaigns (also referred to as inbound campaigns). Contact planning rules allow a company to place volume, frequency and recency rules on all forms of communication across customer, channel, and program dimensions. Rules are created as special segments which act as a filter for other segments. Segment Tree Designer New Features for Oracle BI Publisher Besides the integration with EPM and Smart Space, which we have discussed above, there are the following notable new features for BI Publisher: Support for multidimensional data sources Oracle BI Publisher can now access the following multidimensional data sources: Oracle's Hyperion EssbaseMicrosoft SQL Server 2000...

Student Favorites

one-stop shop This is a somewhat structured list of websites which are related to Oracle, the Siebel CRM and Oracle BI EE product lines as well as training and documentation links. Please also consider the list of favorite blogs on this site. Oracle Website Siebel Product Site Business Intelligence Product Site Oracle Technology Network Siebel Bookshelf download and online library Oracle BI EE documentation download and online library Oracle BI Applications documentation download and online library Oracle Education Oracle Certification Certification Upgrade Information Page ilearning - web based training for Siebel (login required) Oracle BI EE Tutorials (free) Oracle Software Download - edelivery (registration required) License Codes metalink3 - support portal (login required) Special Links: Siebel Query Language online reference (Personalization Administration Guide) Ospace - Oracle Applications Business Community...