| Oracle® Life Sciences Data Hub Release Content Document Release 2.1.4 Revision A Part Number E18330-01 |
|
| View PDF |
| Oracle® Life Sciences Data Hub Release Content Document Release 2.1.4 Revision A Part Number E18330-01 |
|
| View PDF |
Release Content Document
Release 2.1.4 Revision A
E18330-01
August 2010
This Release Content Document (RCD) describes the product features that are included in the 2.1.4 release of the Oracle Life Sciences Data Hub (LSH).
This RCD in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle Corporation.
The information provided in this document is intended to outline our general product direction and is intended for information purposes. The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.
LSH 2.1.4 includes a number of enhancements.
Import Export Utility (IEU) - Source Independence
OBIEE Adapter Enhancements
Usability Enhancements
In this release we have focused on improving the usability of the system. This has been achieved by reducing the number of steps/clicks required to perform some of the most common operations and by making those common operations more accessible to the user. The loading and transforming of data using LSH requires the user to perform several activities many of which have been improved or streamlined.
Developers who use LSH IEU to deliver code need to be able to use multiple environments for shipping patches and new versions of their code to their customers. In previous versions the IEU utility matched imported objects based upon their exported ID, which is different if the same object is exported from two different LSH instances. The IEU utility has been enhanced to support source-independent export by tracking the original ID of objects exported and imported on the source and target environments. IEU users will observe no change in behavior unless they use multiple LSH environments to perform exports.
Support for multiple Business Areas using the same OBIEE Presentation Services server. Previous versions required each Business Area to have its own Presentation Services instance, each on a different computer. The LSH OBIEE adapter has been modified to allow multiple Business Areas from one or more Work Areas to be presented using the same Presentation Services instance, which must have a corresponding Service Location defined. When two BAs share the same value for the OBIEE Service Location Name attribute the system will deploy an RPD file for the BA being installed and merge this onto the default RPD file for the Presentation Services instance on the associated BI Server.
Tracking uploaded/customized RPD files - The OBIEE adapter has been enhanced to better support users who are customizing their LSH Business Areas using the OBIEE Admin tool. When LSH creates an RPD file during installation the File Reference Name is populated with "System" and when a user uploads a customized RPD file the File Reference Name is populated with "uploaded". Uploaded RPD files will not be overwritten by LSH during installation.
The container hierarchy is displayed on each object's properties page. For example if you looking at a Work Area then you can see its owning Domain and Application Area in the object hierarchy region. In this release we have enabled these as hyperlinks, allowing the user to navigate from the properties page of objects to the container that owns them without navigating back to the Applications Hgrid page.
The table that displays Instances Objects Under a Work Area has been expanded to provide additional columns. Some of these columns provide useful information about the instances in that Work Area and other columns provide action buttons.
Technology - The technology type or table type of the instance.
Created TS - Timestamp when the instance was first created.
Created by - User who created the first version of the instance.
Last Modified TS - Timestamp when the latest instance version was last modified.
Last Modified by - User who made the last modification to the latest version of the instance.
Installed TS - Timestamp when the installed version of the instance was installed. If the instance was never installed then this field will be null.
Last Submit TS - Timestamp when the installed version of the instance was last submitted.
Latest Refresh TS - Timestamp for the table instance.
Action Buttons
Install - Perform an Upgrade Install for the selected instance, including all mapped source and target Table instances if required.
Launch - Perform a launch for the selected instance
Submit - Display the Submit screen for the default Execution Setup for that executable instance.
The following operations--Copy, Clone, Remove, Default Execution Setup, Execution Setup, View Output, View All Outputs and Add Source--have been added to an action drop down on the Work Area. After selecting a specific instance in the Work Area Table one of these operations can be performed on that selected instance.
Remove - the currently selected instances with warning
Copy - the currently selected instances
Clone - the currently selected instances
Default Execution Setup - Display the modify screen for the default Execution Setup for that instance
Execution Setup - Display all Execution Setups owned by the selected instance
View Output - Display the most recent outputs produced by the default Execution Setup for that instance
View All Outputs - Display a list of all outputs produced by that instance
Add Source Table - Will open the Create Table Descriptor from Table Instance screen for that instance
With the addition of new columns to the Instance Objects Under a Work Area table it is necessary to give users the ability to configure the instance attribute columns that they want to display. When a new user logs into LSH for the first time they will see all columns displayed. However they will have the option to create personalized views. Users will be able to configure the following:
The number of rows displayed
Columns shown and column order - Object Name is mandatory and will always be shown.
The columns' sort order
These views can be saved with a custom name and one view can be defined as the default view for that user. These views are only available to the user that created them. However all of that user's views can be used for any Work Area that they have access to. Views can be copied and removed as needed by the user and customized as required over time.
The Table Descriptors tab has been modified to increase the number of rows displayed from 10 to 25 and additional buttons have been added to this region for adding Table Descriptors. The Add Source button provides a shortcut to the Create TD from TI option and buttons have been added for creating target Table Descriptors from a SAS File and from an existing Library Table as well as for creating a New Table descriptor and definition.
In order to reduce the number of steps/clicks required to create LSH objects, an Install button has been added to the instance property page of all instances. This will perform an upgrade install for that instance and any target Tables that the object has.
3.1.2.8.1. Autocreate mapped Table instances
It is extremely common for a user to create target Table instances that are identical to the Table descriptors that are writing to them. The Create Table Instance from Table Descriptor option can be used to induce those Table instances to be created more quickly; however in most cases this is a series of extra steps/clicks that could be avoided. In this release the rules that control when an instance can be installed have been changed so that instances that have unmapped target Table Descriptors can still be installed. If a Load Set or Program an instance has target Table Descriptors that are unmapped then the install will attempt to use the Automap by Name feature to create and map target Table instances automatically. For all practical purposes this means that a user can create Table Descriptors in a Load Set, for example, and install without any target Table instances. The installation process will assume you need matching Table instances and automatically create them for you.
3.1.2.8.2. Autocreate Table Descriptors and mapped Table instances
This behavior has been further simplified when creating an Oracle Clinical Data Extract Load Set. In this special case a Load Set instance will be installable even if there are no Table descriptors. If an Oracle Clinical Data Extract Load Set containing no Table descriptors is installed then all existing DX Views from that study will be added automatically to the Load Set during installation. Target Table instances will also be created and mapped if required.
The automatic creation of Table descriptors, Table instances and associated mappings are potentially time consuming operations. For performance and scalability reasons these installations will be performed as a batch job. The job ID will be provided in a message when the installation is initiated so that the user can monitor the batch installation.
In this release there is no option to control the Table type of these automatically created Table instances and will use the default type of Staging with Audit.
A new tab has been added to the properties page of all executable instances. The Jobs tab displays a list of all Jobs ever executed for any version of that instance. This means that the user does not need to go to the My Home page in order to monitor the progress of a submission and makes it much easier to review previous Jobs submitted for the current instance.
It is now possible to hide all of the submission parameters on the submission page. The Execution Setup submission parameters page has been updated to allow all submission parameters including the ones below to be hidden:
Timeout Value - including default value and units
Apply Snapshot Label - including default Label
The following are now a show hide region on the Submission Screen and are hidden by default.
Output Title Suffix - including default value
Output Description Suffix - including default value
The Source Data Currency tab will be represented as a tree. The tree will be grouped by Work Area and will show each Work Area as the parent and then each mapped Table from that Work Area as its children. By default the tree will not be expanded. This will make it much easier for users to see the location / study of the Table in use by the current Program.
In order to improve the flexibility to use Snapshot Labels more effectively the current functionality related to Select Shared Snapshot label has been extended to so that when a user chooses a Snapshot Label the system can choose all Tables that share that Snapshot Label. The Use Snapshot Action drop down can be used to select Source Data Currency at three levels:
All Tables referenced by that Program
All Tables in a Work Area from the new tree
Individual Tables
In all cases the Snapshot Label list of values displays a list of any available Snapshot Labels and the standard options of Most Current Label, Most Current Data, Clear Currency and No Change if applicable. In all cases the option for No Change will be displayed without any text.
It will also be possible to limit Snapshot Labels by a Cut-Off Date. By default the Cut-Off date will be set to the current date. The user will be able to pick any date from a calendar (time can be manually entered if required). When a date is selected it will be used by all snapshot label LOVs on the Source Data Currency tab to reduce the list of available Snapshot Labels by the cut-off date.
The following components were certified with LSH 2.1.4.
| Component | Version | Dependency | Required? |
|---|---|---|---|
| eBusiness Suite | 11i10 CU2 | Install, Runtime | Required |
| eBusiness Suite RUP | ATG RUP 7 | Runtime | Required |
| XML Publisher | 5.6.3 | Runtime | Required |
| Oracle Database 11g | 11.2.0.1 | Install, Runtime | Required |
| Oracle Warehouse Builder 11g | 11.2.0.1 | Runtime | Required |
| Oracle TMS | 4.6.1 | Runtime | Required |
| Oracle Reports | 6.0.8.24 | Runtime | Optional |
| OBIEE | 10.1.3.4.1 | Runtime | Optional |
| OBIP | 10.1.3.4.1 | Runtime | Optional |
| Oracle Discoverer | 10.1.2.3 | Runtime | Optional |
| SAS | 8.2, 9.1.3, 9.2 | Runtime | Optional |
| Informatica | 8.6.1 HF10 | Runtime | Optional |
The following platform configurations were certified with LSH 2.1.4.
| Platform | Required? |
| Client |
|
| Application Server |
|
| Database Server |
|
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
To reach AT&T Customer Assistants, dial 711 or 1.800.855.2880. An AT&T Customer Assistant will relay information between the customer and Oracle Support Services at 1.800.223.1711. Complete instructions for using the AT&T relay services are available at http://www.consumer.att.com/relay/tty/standard2.html. After the AT&T Customer Assistant contacts Oracle Support Services, an Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process.
Oracle Life Sciences Data Hub Release Contents Document
E18330-01
Copyright © 2010 Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.