Data warehouses are becoming increasingly common as businesses have realized the need to be able to mine the information they have stored in the electronic form in order to provide a valuable insight into the operation of their business and how best to improve it. Organizations need to monitor these processes, define policies, and—at a more strategic level—define the visions and goals that will move the company forward in the future. The Warehouse Builder provides a couple of ways to create a dimension. One way is to use the wizards that it provides, which will automatically create a dimension for us. The other way is to manually create it.
In this article by Bob Griesemer, author of Oracle Warehouse Builder 11g R2: Getting Started 2011, we will create:
- The Product dimension
- The Store dimension
In this article by Bob Griesemer, author of Oracle Warehouse Builder 11g R2: Getting Started 2011, we will define our cube, which is where our measures will be stored—the facts that users will want to query. There is a wizard available to us for creating a cube that we will make use of to ease our task. So let's start designing the cube with the wizard. We'll create the objects using the wizards that the Warehouse Builder provides for us to simplify the task of building cubes and dimensions.
We will cover:
- Creating a cube with the wizard
- Using the data object editors
Sometimes we can use a preexisting theme, as a good base for our site, and modify it a bit. In this article by Jose Argudo Blanco, author of Magento 1.4 Theming Cookbook, we will see how we can find a theme, install it, and make some tiny modifications to it, a good and easy way of getting a Magento installation up and running.
The topics covered in this article are:
- Installing a theme through Magento Connect
- Installing a theme manually
- Selecting the recently installed theme
- Enabling template path hints
- Simple modifications, changing a logo, and header info
- Simple modifications, linking to CMS pages from our theme
Magento is a popular open source e-commerce project. While it comes with a number of 'default' themes to change the look and feel of your store, many people both new and old to Magento struggle with even the more basic aspects of customizing Magento themes.
Magento can be a complex platform to customize, so this article by Richard Carter, author of Magento 1.4 Themes Design, will help you to explore Magento themes, including the following:
- Magento terminology
- What a Magento theme is: the elements that comprise a Magento theme
- Theme hierarchy in Magento
- Magento's Blank theme
- Installing and activating a Magento theme
NPM is a package management and distribution system for Node. It has become the de-facto standard for distributing modules (packages) for use with Node. Conceptually it's similar to tools like apt-get (Debian), rpm/yum (Redhat/Fedora), MacPorts (Mac OS X), CPAN (Perl), or PEAR (PHP). It's purpose is publishing and distributing Node packages over the Internet using a simple command-line interface. With npm you can quickly find packages to serve specific purposes, download them, install them, and manage packages you've already installed. npm defines a package format for Node largely based on the CommonJS Package spec.
In this article by David Herron, author of Node Web Development, we will take a look at the npm package management system.Read An Overview of the Node Package Manager in full
The generic term "tuning security … " some say, it's an oxymoron. Why so? Well, in many cases, tightening up security is normally reflected in poor performance. So, if a portion of your environment is performing poorly, it may need a review of the security configuration in order to see if loosening it a bit does not compromise the environment itself. This article by Omar Siliceo, author of IBM WebSphere Application Server v7.0 Security, briefly describes tuning in three major areas:
- General security configuration
- CSIv2 connectivity
- LDAP and Web authentication
The default configuration for Windows Azure Diagnostics captures some data but does not persist it. Consequently, the diagnostics configuration should be modified at role startup. In this article by Neil Mackenzie, author of Microsoft Windows Azure Development Cookbook, the Initializing the configuration of Windows Azure Diagnostics recipe, shows us how to do this programmatically, which is the normal way to do it. In the Using a configuration file with Windows Azure Diagnostics recipe, we see how to use a configuration file to do this, which is necessary in a VM role.Read Windows Azure Diagnostics: Initializing the Configuration and Using a Configuration File in full
It is not uncommon to run into issues when global security is first enabled in a WebSphere environment. Some of those situations may occur due to performing tasks out of order. Other problematic conditions related to security configuration may take place due to inadvertently omitting one or more steps in a set up process. Moreover, a third category of errors that may happen due to security configuration is caused by using the wrong values to one or more parameters.
In the previous article by Omar Siliceo, author of IBM WebSphere Application Server v7.0 Security, we took a look at tuning websphere security. In this article we will be presented by a set of some conditions that may appear in a WebSphere Application Server ND version 7 (WAS ND7) when global security is first enabled. The first subsection covers circumstances that may come about during the configuration phase. Next, a subsection is included that presents circumstances that may happen at runtime.Read Troubleshooting WebSphere Security-related Issues in full
A Windows Azure hosted service may comprise multiple instances of multiple roles. These instances all run in a remote Windows Azure data center—typically 24*7. The ability to monitor these instances non-intrusively is essential both in detecting failure and in capacity planning.
However, there are times, especially early in the development process, when non-intrusive diagnostics monitoring is not sufficient. In this article by Neil Mackenzie, author of Microsoft Windows Azure Development Cookbook, we will see the benefits of intrusive monitoring of a Windows Azure role instance using IntelliTrace.Read Using IntelliTrace to Diagnose Problems with a Hosted Service in full
In this article by David Herron, author of Node Web Development, we shall:
- Learn what a module is
- Learn about the CommonJS module specification
- Learn how Node finds modules
A Windows Azure hosted service may comprise multiple instances of multiple roles. These instances all run in a remote Windows Azure data center—typically 24*7. The ability to monitor these instances non-intrusively is essential both in detecting failure and in capacity planning. This article by Neil Mackenzie, author of Microsoft Windows Azure Development Cookbook, shows how Windows Azure Diagnostics provides for the non-intrusive capture of diagnostic data and its subsequent persistence to the Windows Azure Storage Service. Windows Azure Diagnostics supports various standard sources, allowing for their extensibility where appropriate. The topics covered in this article include:
- Using the Windows Azure Diagnostics trace listener
- Performing an on-demand transfer
- Implementing custom logging
- Accessing data persisted to Windows Azure Storage
- Using the Windows Azure Platform
- PowerShell cmdlets to configure Windows Azure Diagnostics
Fragment shaders can make use of the discard keyword to "throw away" fragments. Use of this keyword causes the fragment shader to stop execution, without writing anything (including depth) to the output buffer. This provides a way to create holes in polygons without using blending. In fact, since fragments are completely discarded, there is no dependence on the order in which objects are drawn, saving us the trouble of doing any depth sorting that might have been necessary if blending was used. In this recipe by David Wolff, author of OpenGL 4.0 Shading Language Cookbook, we'll draw a teapot, and use the discard keyword to remove fragments selectively based on texture coordinates.Read GLSL 4.0: Discarding Fragments to Create a Perforated Look in full
Shaders give us the power to implement alternative rendering algorithms and a greater degree of flexibility in the implementation of those techniques. With shaders, we can run custom code directly on the GPU, providing us with the opportunity to leverage the high degree of parallelism available with modern GPUs.
This article by David Wolff, author of OpenGL 4.0 Shading Language Cookbook, provides examples of basic shading techniques such as diffuse shading, two-sided shading, and flat shading. Specifically, we will cover:
- Implementing diffuse, per-vertex shading with a single point light source
- Implementing per-vertex ambient, diffuse, and, specular (ADS) shading
- Using functions in shaders
- Implementing two sided shading
- Implementing flat shading
In GLSL, a subroutine is a mechanism for binding a function call to one of a set of possible function definitions based on the value of a variable. Subroutines therefore provide a way to select alternate implementations at runtime without swapping shader programs and/or recompiling, or using if statements along with a uniform variable.
In this article by David Wolff, author of OpenGL 4.0 Shading Language Cookbook, we'll demonstrate the use of subroutines by rendering a teapot twice. The first teapot will be rendered with the full ADS shading model described earlier. The second teapot will be rendered with diffuse shading only. A subroutine uniform will be used to choose between the two shading techniques.Read GLSL 4.0: Using Subroutines to Select Shader Functionality in full
In early 2010, when you went to the Oracle Technology Network (OTN) website, it had just one link called Information Integration. This link led you to a simple web page that had information on Oracle-to-Oracle database-centric migration and integration tools such as SQL Loader, Data Pump, Oracle Streams, and Oracle Data Guard. The OTN website has been updated, but still lacks comprehensive coverage of the Oracle Information Integration stack.
In the previous article by Tom Laszewski, co-author of Oracle Information Integration, Migration, and Consolidation, we took a look at some oracle tools and products. In this article we will take a look at data services, data consolidation, data grid, information lifecycle management, oracle-to-oracle data integration, and application integration.Read Oracle Integration and Consolidation Products in full